The implementation model is a composite, comprehensive artifact which
encompasses all artifacts needed to build and manage the system in the run-time
textual description that serves as a brief introduction to the model
value, of type "short text"
subsystems in the model, representing a hierarchy
via the meta-association "represents", or recursively via the
components in the model, owned by the subsystems
recursively via the meta-aggregation "owns"
relationships in the model, owned by the subsystems
diagrams in the model, owned by the subsystems
implementation view of the model, which is an architectural view showing the
subsystems and layers
and diagrams in the view are owned recursively via the meta-aggregation
The Implementation Model structure is established in the Elaboration Phase,
and is refined as needed in the Construction Phase.
A software architect is responsible for the integrity of the implementation model,
and ensures that:
- The implementation model as a whole is correct, consistent, and readable.
The implementation model is correct when it realizes the functionality
described in the use-case model.
- The architecture in the implementation model, described in the
implementation view, fulfills its purpose. The implementation view is
described in a separate artifact, refer to the Artifact:
Software Architecture Document.
Note that the software architect is not responsible for the implementation subsystems
and components, instead, these are under the corresponding implementer's
You have to decide how to map the classes and packages in design model to
components and subsystems in the implementation model.
© 1987 - 2001 Rational Software Corporation