Print book
Print this chapterUse Case Concepts in Object-Oriented Analysis
Use cases are a powerful way of modeling what the system needs to do. Read this section to learn about use case diagrams and how they capture functional requirements.
5. Why use cases?
The reasons why use cases are good for requirement capture include:
1. They answer what the system should do for each user or actor question.
2. Use Cases define the scope of the system. They enable to visualize size and scope of the entire development.
3. They facilitate communication means between the customer and developers (use case diagram is so simple, anyone can understand it)
4. They represent system functions and the relationship among the system functions in a narrative way.
5. They extent the identification of concepts and objects involved in the application domain.
6. Use Cases are very similar to requirements, but whilst requirement tend to be vague, confusing, ambiguous and poorly written, the tighter structure of Use Case tend to make them far more focused
7. The "sum" of the use cases is the whole system. Anything not covered by a use case is outside the boundary of the system to be developed. So the Use Case diagram is complete with no holes
8.Use Cases guide the development teams through the development process. They give the summary of what is needed to be done by the system
9.Use Cases provide a method for planning development work, and allow to estimate how long the development will take
10. Use Cases provide the basis for creating system tests
11. Use cases help with the creation of user guides
12. Use cases can be a source of information during validation and verification of a software