Chapter 4. Use Cases
A recurring problem in systems development is getting started with the requirements and organizing them into some comprehensible framework. In this chapter we will see how to gather the requirements for the system and organize them into separate domains.
Use cases view a system from the outside—they take an external view of the system in terms of what happens. Executable UML models, on the other hand, take an internal view of a domain in terms what the conceptual entities are and how they behave.
Use cases, then, are a useful tool for gathering requirements, but they do not immediately yield classes. Figuring out the classes requires abstraction based upon the requirements.
Once we have built the executable UML models, we ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access