UML Weekend Crash Course™ - To Parent Directory

68
Saturday Morning
REVIEW
The goal of the Use Case diagram is to define the expectations of the users. Those users may
be people, systems, or devices that need to interact with the system. Their interactions may
be to provide input, to receive output, or to dialog with the system in order to cooperate in
the completion of a task. All these interactions are focused through a set of specific features
of the system called Use Cases. Each Use Case defines one specific goal that the system can
achieve.
The construction of a Use Case diagram requires the following steps:
1. Identifying the context of the system
2. Identifying the actors and their responsibilities
3. Identifying the Use Cases, the features of the system, in terms of specific goals
4. Evaluating the actors and Use Cases to find opportunities for refinement
5. Evaluating the Use Cases to find type dependencies
6. Evaluating the Use Cases to find type dependency
7. Evaluating the actors and Use Cases for generalization (shared properties)
QUIZ YOURSELF
1. What is an actor (See “Step 2: Identify the actors.”)
2. How do you identify a Use Case (See “Step 3: Identify the Use Cases.”)
3. What is the notation for an dependency (See “Step 6: Evaluate the
Use Cases for dependencies.”)
4. What is another name for a Use Case (See “Step 3: Identify the Use Cases.”)
5. What does it mean when you place the stereotype on a dependency
(See “Step 7: Evaluate the Use Cases for dependencies.”)