Templates, Case-Study, Report..
The Word template can be bought through a template package. Case studies and reports are freely available in the table below.
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 collaboration and
sequence diagrams which express the behavior of the use case in terms of
of Events Design
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 cases itself; this is
value, of type "formatted text".
diagrams (sequence and collaboration diagrams) describing how the use case
is realized in terms of collaborating objects.
are owned via aggregation "behaviors".
diagrams describing the classes and relationships that participate in the
realization of the use case.
are owned via aggregation "types" and "relationships".
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.
value, of type "short text".
stereotyped dependency to the use case in the use-case model that is
A template is provided
for a use-case realization specification, which contains the textual properties
of the use-case realization. This document is used with a requirements
management tool, such as Rational RequisitePro, for specifying and marking the
requirements within the use-case realization properties.
The diagrams of the use-case realization can be developed in a visual
modeling tool, such as Rational Rose. A use-case realization report
(with all properties) may be generated with Rational SoDA.
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.
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
- The diagrams describing the use-case realization are readable and suit
- The Derived Requirements are readable and suit their
- The trace dependency to the corresponding use case in the use-case model
- 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
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.