| Work Product: Implementation Model |
|
 |
| The Implementation Model represents the physical composition of the implementation in terms of Implementation Subsystems, and Implementation Elements (directories and files, including source code, data, and executable files). |
|
Purpose
|
The Implementation Model identifies the physical parts of the implementation so that they can be better understood and
managed. The Implementation Model defines the major units of integration around which teams are organized, as well as
the units that can be separately versioned, deployed, and replaced.
A more detailed Implementation Model may also include low level source code and derived files, and their relationship
to the Design Model. Such detail is recommended only if you have automated synchronization between the model and the
files.
|
Relationships
| Roles | Responsible:
| Modified By:
|
| Input To | Mandatory:
| Optional:
| External:
|
| Output From |
|
Properties
| Optional |  |
| Planned |  |
Tailoring
| Representation Options |
UML Representation: Model, stereotyped as <<implementation model>>.
The Implementation Model may have the following properties:
-
Introduction: A textual description that serves as a brief introduction to the model.
-
Implementation Subsystems: The subsystems in the model, representing a hierarchy.
-
Implementation Elements: The elements in the model, owned by the subsystems.
-
Relationships: The relationships in the model, owned by the Implementation
Subsystems.
-
Diagrams: The diagrams in the model, owned by the Implementation Subsystems.
-
Implementation View: The implementation view of the model, which is an architectural view showing
the Implementation Subsystems and layers.
An Implementation Model is optional. If you choose to create an Implementation Model, the key tailoring decisions are
how to relate between the Implementation Model and Design Model, and which Implementation Elements are important enough
to model. Guidance on how to make these decisions is covered in Guideline: Implementation Model. Also see Concept: Mapping from Design to Code.
|
More Information
© Copyright IBM Corp. 1987, 2006. All Rights Reserved.
|
|
