Use case diagram
From Wikipedia, the free encyclopedia
 |
This article may require cleanup to meet Wikipedia's quality standards. Please improve this article if you can. (November 2006) |
A use case diagram is a type of behavioral diagram defined by the Unified Modeling Language (UML) created from a Use-case analysis. Its purpose is to present a graphical overview of the functionality provided by a system in terms of actors, their goals—represented as use cases—and any dependencies between those use cases.
The main purpose of a use case diagram is to show what functions are performed by which actors.what are the roles of an actor in the system (e.g. in the diagram below, Wait staff can order food and serve food).
While SysML uses the same notation as UML for use cases, system engineers model at the system or systems-of-systems level.
Contents |
[edit] UML Use Case Diagram
OMG's UML standard defines a graphical notation for modeling use cases with diagrams, but no format for describing these use cases. While the graphical notation and descriptions are important, they are documentation of the use case—a purpose that the actor can use the system for—
The true value of a use case lies in two areas:
- The written description of system behavior regarding a business task or requirement. This description focuses on the value provided by the system to external entities such as human users or other systems.
- The position or context of the use case among other use cases. As an organizing mechanism, a set of consistent, coherent use cases promotes a useful picture of system behavior, a common understanding between the customer/owner/user and the development team.
This diagram describes the functionality of a simplistic Restaurant System. Use cases are represented by ovals and the actors are represented by stick figures. The Patron actor can Eat Food, Pay for Food, or Drink Wine. Only the Chef actor can Prepare Food. Note that both the Patron and the Cashier are involved in the Pay for Food use case. The box defines the boundaries of the Restaurant System, i.e., the use cases shown are part of the system being modelled, the actors are not.
Interaction among actors is not shown on the use case diagram. If this interaction is essential to a coherent description of the desired behavior, perhaps the system or use case boundaries should be re-examined. Alternatively, interaction among actors can be part of the assumptions used in the use case.
[edit] Actor Generalization
The only relationship allowed between actors is generalization. This is useful in defining overlapping roles between actors. The notation is a solid line ending in a hollow triangle drawn from the specialized to the more general actor.
[edit] Use Case Relationships
Three (3) relationships among use cases are supported by the UML standard, which describes graphical notation for these relationships.
[edit] Uses
In one form of interaction, a given use case uses another. The first use case often depends on the outcome of the included use case. This is useful for extracting truly common behaviors from multiple use cases into a single description. The notation is a dashed arrow from the including to the included use case, with the label "«include»". This usage resembles a macro expansion where the included use case behavior is placed inline in the base use case behavior. There are no parameters or return the values.
[edit] Extend
In another form of interaction, a given use case (the extension) may extend another. This relationship indicates that the behavior of the extension use case may be inserted in the extended use case under some conditions. The notation is a dashed arrow from the extension to the extended use case, with the label "«extend»". This can be useful for dealing with special cases (when A extends B, A is a special case of B), or in accommodating new requirements during system maintenance and extension.
To make the points at which extension may occur explicit extension points may be defined in a use case which are listed in a compartment below the use case.
[edit] Generalization
In the third form of relationship among use cases, a generalization/specialization relationship exists. A given use case may be a specialized form of an existing use case. The notation is a solid line ending in a hollow triangle drawn from the specialized to the more general use case. This resembles the object-oriented concept of sub-classing, in practice it can be both useful and effective to factor common behaviors, constraints and assumptions to the general use case, describe them once, and deal same as except details in the specialized cases.
[edit] External links
- Creating Use Case Diagrams shows a common mistake about use case extension
- Introduction to Use Cases & Use Case Diagrams
- UML Use Case Diagrams: Tips
