Artifacts > Implementation Artifact Set > Implementation Model... > Implementation Model
Artifact:
|
Implementation Model |
The implementation model is a collection of components, and the implementation subsystems that contain them. Components include both deliverable components, such as executables, and components from which the deliverables are produced, such as source code files. |
UML representation: | Model, stereotyped as «implementation model». |
Role: | Software Architect |
Reports: | As part of the Artifact: Software Architecture Document |
More information: | |
Input to Activities:
|
Output from Activities: |
The implementation model is a composite, comprehensive artifact which encompasses all artifacts needed to build and manage the system in the run-time environment.
Property Name |
Brief Description |
UML Representation |
Introduction | A textual description that serves as a brief introduction to the model | Tagged value, of type "short text" |
Implementation Subsystems | The subsystems in the model, representing a hierarchy | Owned via the meta-association "represents", or recursively via the meta-aggregation "owns" |
Components | The components in the model, owned by the subsystems | Owned recursively via the meta-aggregation "owns" |
Relationships | The relationships in the model, owned by the subsystems | - " - |
Diagrams | The diagrams in the model, owned by the subsystems | - " - |
Implementation View | The implementation view of the model, which is an architectural view showing the subsystems and layers | Elements and diagrams in the view are owned recursively via the meta-aggregation "owns" |
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:
Note that the software architect is not responsible for the implementation subsystems and components, instead, these are under the corresponding implementer's responsibilities.
You have to decide how to map the classes and packages in design model to
components and subsystems in the implementation model.
Rational Unified Process |