Artifacts >
Implementation Artifact Set >
Implementation Model
Artifact:
Implementation Model
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.
The Word template can be bought through a template package. Case studies and reports are freely available in the table below.
Word Template
Case Study
Report
---
---
Purpose
The implementation model is a composite, comprehensive artifact which
encompasses all artifacts needed to build and manage the system in the run-time
environment.
Properties
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"
Timing
The Implementation Model structure is established in the Elaboration Phase,
and is refined as needed in the Construction Phase.
Responsibility
An integrator 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 designer is not responsible for the implementation subsystems
and components, instead, these are under the corresponding implementer's
responsibilities.
Tailoring
You have to decide how to map the classes and packages in the design model to
components and subsystems in the implementation model.