Artifact: Use-Case Realization
|
| A use-case realization describes how a particular use case is realized within the design model, in terms of collaborating objects. | |
| Other Relationships: |
Part Of Design Model
| |
|---|---|---|
| Role: | Designer | |
| Optionality/Occurrence: | Depending if use cases are used. Created in the Elaboration phase for the architecturally significant ones. The remaining are addressed in the Construction phase. | |
| Templates and Reports: |
| |
| Examples: |
| |
| UML Representation: | Collaboration or CollaborationInstanceSet, stereotyped as <<use-case realization>>. | |
| More Information: |
| |
|
| ||
Input to Activities:
| Output from Activities:
|
Purpose
The purpose of the use-case realization is to separate the concerns of the specifiers of the system (as represented by the use-case model and the requirements of the system) from the concerns of the designers of the system. The use-case realization provides a construct in the design model which organizes artifacts related to the use case but which belong to the design model. These related artifacts consist typically of the communication and sequence diagrams which express the behavior of the use case in terms of collaborating objects.
Properties
Property Name | Brief Description | UML Representation |
|---|---|---|
| Flow of Events Design | A textual description of how the use case is realized in terms of collaborating objects. Its main purpose is to summarize the diagrams connected to the use case (see below), and to explain how they are related. Optional - created only if there is additional information needed for analysis or design which is not appropriate in the use case itself; this is very rare. | Tagged value, of type "formatted text". |
| Interaction Diagrams | The diagrams (sequence and communication diagrams) describing how the use case is realized in terms of collaborating objects. | Participants are owned via aggregation "behaviors". |
| Class Diagrams | The diagrams describing the classes and relationships that participate in the realization of the use case. | Participants are owned via aggregation "types" and "relationships". |
| Derived Requirements | A textual description that collects all requirements, such as non-functional requirements, on the use-case realization that are not considered in the design model, but that need to be taken care of during implementation. | Tagged value, of type "short text". |
| Realization Association | A stereotyped dependency to the use case in the use-case model that is realized. | dependency |
Timing
Use-case realizations are created in the Elaboration Phase for architecturally significant use cases. Use-case realizations for the remaining Use cases are created in the Construction Phase.
Responsibility
A use-case designer is responsible for the integrity of the use-case realization, and ensures that:
- The use-case realization fulfills the requirements made on it; that it correctly realizes the behavior of its corresponding use case in the use-case model, and only this behavior.
- The Flow of Events Design is readable and suits its purpose.
- The diagrams describing the use-case realization are readable and suit their purpose.
- The Derived Requirements are readable and suit their purpose.
- The trace dependency to the corresponding use case in the use-case model is correct.
- The relationships, such as communicates-associations, include- and extend-relationships, of the corresponding use case in the use-case model are handled correctly within the use-case realization.
The use-case designer is not responsible for the classes and relationships employed in the use-case realization; instead, these are under the corresponding designer's responsibilities.
Tailoring
Use-case realizations express the behavior of a set of model elements performing some or all of an Artifact: Use Case. As a result, there should be a use-case realization for each use case which needs to be expressed in the design model. Similarly, if use cases are not used, then use-case realizations will also be omitted.
