Is my use case diagram correct?
NOTE: I am self studying UML so I have nobody to verify my diagrams and hence I am posting here, so please bear with me. This is the problem I got from some PDF available on Google that simply had the following problem statement:
Problem Statement:
A library contains books and journals. The task is to develop a
computer system for borrowing books. In order to borrow a book
the borrower must be a member of the library. There is a limit on the
number of books that can be borrowed by each member of the library.
The library may have several copies of a given book.
It is possible to reserve a book.
Some books are for short term loans only. Other books may be
borrowed for 3 weeks. Users can extend the loans.
1. Draw a use case diagram for a library.
2. Give a use case description for two use cases:
• Borrow copy of book
• Extend loan
Diagram:
When is a Use Case layer needed?
In his blog post The Clean Architecture Uncle Bob suggests a 4-layer architecture. I understand the separation between business rules, interfaces and infrastructure, but I wonder if/when it’s necessary to have separate layers for domain objects and use cases. What added value will it bring, compared to just having the uses cases as “domain services” in the domain layer?
Is this usage of extend relationship in a use case diagram correct?
On this picture:
Behavior-Driven Development / Use case diagram
Regarding growing of Behavior-Driven Development imposing acceptance testing, are use cases diagram useful or do they lead to an “over-documentation”?
Describing requirements in SRS – use cases?
I do not have the access to the IEEE standard and information on the net are contradictory. Can I capture user requirements in SRS using use cases? Or I should keep use cases separate as they are more like scenarios than separate requirements?
When are RPC-ish approaches more appropriate than REST?
After watching this talk on REST, Reuse and Serendipity by Steve Vinoski, I wonder if there are business cases in greenfield projects for (XML-)RPC-ish setups, that REST could not solve in a better way.
Use Cases with respect to downstream systems
Use cases are primarily meant for interaction between user and a system. It could be used for interaction between system and another system. The actors are primarily roles.
What can be used in lieu of use cases to gather requirements?
I’m a programmer currently working in rounds of meetings along with BAs and PM to gather/describe modules and functionality of our case management system; after a few meetings I saw that using ‘use cases’ would be a very very good fit to document many of the things and functions discuessed and/or proposed for the new system. When I suggested we needed to create ‘use cases’ so that we don’t forget what we said/concluded and also to have programers know what they should code, the leading BA mentioned don’t like ‘use cases’.
Applications of heapsort [closed]
Closed 8 years ago.
Use case decomposition for class registration system
I am currently working on refactoring a summer camp registration system to include some new features and will also be using it as the basis for a new after-school class registration system.