|
Use Case Diagram Sample
|
|
Creating Use Case Diagram for describing the behavior of the target system from an external point of view.
|
|
| |
|
Actor
|
|
An Actor models a type of role played by an entity that interacts with the subject (e.g., by exchanging signals and data), but which is external to the subject (i.e., in the sense that an instance of an actor is not a part of the instance of its corresponding subject). Actors may represent roles played by human users, external hardware, or other subjects.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 643)
|
|
| |
|
Extend
|
|
This relationship specifies that the behavior of a use case may be extended by the behavior of another (usually supplementary) use case. The extension takes place at one or more specific extension points defined in the extended use case.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 646)
|
|
| |
|
ExtensionPoint
|
|
An ExtensionPoint is a feature of a use case that identifies a point where the behavior of a use case can be augmented with elements of another (extending) use case.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 648)
|
|
| |
|
Include
|
|
Include is a DirectedRelationship between two use cases, implying that the behavior of the included use case is inserted into the behavior of the including use case. It is also a kind of NamedElement so that it can have a name in the context of its owning use case. The including use case may only depend on the result (value) of the included use case. This value is obtained as a result of the execution of the included use case.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 649)
|
|
| |
|
UseCase
|
|
A UseCase is a kind of behaviored classifier that represents a declaration of an offered behavior. Each use case specifies some behavior, possibly including variants, that the subject can perform in collaboration with one or more actors. Use cases define the offered behavior of the subject without reference to its internal structure. These behaviors, involving interactions between the actor and the subject, may result in changes to the state of the subject and communications with its environment. A use case can include possible variations of its basic behavior, including exceptional behavior and error handling.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 651)
|
|
| |
