CHAPTER 12
Modeling the Use of a System with the Use Case Diagram
In This Chapter
- Using the Use Case diagram
- Modeling use cases
- Modeling actors
- Modeling associations
- Modeling generalizations
- Modeling use case relationships: include and extend
- Defining and writing a use case description
- Defining and finding use case scenarios
The Use Case diagram is a unique graphical element, in that it is a diagram used to model how people expect to use a system. The diagram describes who the relevant users will be, the services they require of the system, and the services they need to provide to the system.
The Use Case diagram can be applied to many types of development, including manual systems, but it is most commonly used for systems and subsystems.
The Use Case diagram is the key element of the Object-Oriented Software Engineering (OOSE) method, also known as Objectory (short for object factory), published in 1992 by Ivar Jacobson and his associates. The technique had a proven track record with large-scale object-oriented projects at Ericsson, HP, and other companies. Its success garnered the attention of authors of other popular methods that lacked a means to document system requirements ...
Get UML™ Bible now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
