As you see in Figure 1, the use cases that typically occur first are shown above those that appear later.įigure 1. Imply Timing Considerations By Stacking Use Cases.

Name Use Cases Using Domain Terminology.Use Case Names Begin With a Strong Verb.A use case is drawn as a horizontal ellipse on a UML use case diagram, as you see in Figure 1. There are guidelines for:Ī use case describes a sequence of actions that provide a measurable value to an actor. Use case models should be developed from the point of view of your stakeholders and not from the (often technical) point of view of developers. Within most use case models the use case specifications tend to be the primary artifact with use case diagrams filling a supporting role as the “glue” that keeps your requirements model together. Model your analysis of your usage requirements in the form of a system use case model>Ī use case model is comprised of one or more use case diagrams and any supporting documentation such as use case specifications and actor definitions.Communicate the scope of a development initiative.Provide an overview of all or part of the usage requirements for a system or organization in the form of an essential model or a business model.A use case diagram is “a diagram that shows the relationships among actors and use cases within a system.