OOPortal OOPortal


Use Case View  «Prev

Steps in building a use case diagram

Correct order of steps for building a use case diagram.
  1. Set the context of the target system. Context always comes first. Without it, there is no frame of reference for the information you are evaluating.
  2. Identify the actors. Find the people, systems, or devices that communicate with the system. These users will become your source for finding and validating the required features of the system. This should be a first-draft effort only.
  3. Identify the use cases. Find the features that the system provides. What does the system help the actor(s) do? What does the system tell the actor? What does the actor help the system do? This should be a first-draft effort only.
  4. Define the associations between actors and use cases. Identify which actors need access to which features. This should be a first-draft effort only.
  5. Evaluate the actors and use cases to find opportunities for refinement. Rename, merge, and split actors and use cases as needed. Update the related associations.
  6. Evaluate the use cases to find opportunities for delegation. Apply the <<Uses>> association stereotype between the use cases.
  7. Evaluate the actors and use cases for special cases. Apply the <<Extends>> association stereotype.

Use Case diagram example

  1. Use Case diagram: A diagram that shows the relationships among actors and use cases (features) within a system.
  2. use case instance: The performance of a sequence of actions being specified in a use case.
  3. use case model: A model that describes a system's functional requirements in terms of use cases, use case narratives, and scenarios.

Use Case diagram Example