Use Case Diagram

From PlugIT Wiki

Jump to: navigation, search



Name

Use Case Diagram

Management Summary

Use case diagrams are used to specify required usage of a system and are therefore typically used to capture the requirements of a system. The key concepts are actors, uses cases, and subject. Actors represent users or any other system that may interact with the system. The system itself is described as the subject. The required behavior of the subject is specified by one or more use cases, which are defined according to the needs of actors.

Dimensions of the language:

Perspective (Role of End user):

Strategy

Aspects:

Process

Semantics:

semi-formal

Framework:

OMG/UML.

Relevance for Use Case:

iTG, HLRS

Maturity Level:

established

Semantics:

The meaning of the model's concept and their relations is specified. However, additional textual description are possible.

Syntax:

Modelling concepts and functionalities, level of formalism, graphical notation
Actor specifies a role played by a user or any other system that interacts with the subject. An actor is represented by a "stick man" icon. The name of the actor must be added usually above or below the icon.

Subject: Extending a classifier, with the capability to own use cases. Usually, it is represented as a rectangle. The name of the system is added within the rectangle.

Use Case is the specification of a set of actions performed by a system. Usually, a use case is represented as an ellipse containing the name of the use case in the middle.

Associations between actors and use cases show the communication.

Using the extend-association shows that a use case is extended by another use case.

Using the include-association shows that a use case contains the behavior defined in another use case.

References

OMG Unified Modeling LanguageTM (OMG UML), Infrastructure


Navigate

Overview modelling languages