Tool Mentor: Managing the Design Model
Purpose
This tool mentor describes how to represent the design model and related artifacts in Rational Rose®. The 'Rational Unified Process' Rose model template, provided with Rational Rose, provides the structure described below.
Related Rational Unified Process Activities:
- Activity: Identify Design Mechanisms
- Activity: Subsystem Design
- Activity: Use-Case Analysis
- Activity: Use-Case Design,
Overview
The following steps are performed to manage the Artifact: Design Model:
- Creating Packages in the Design Model
- Creating Layers in the Design Model
- Document the Model Organization
1. Creating the Design
Model 
The Artifact: Design Model can be represented in Rational Rose™ using a package within the Logical View Named "Design Model". The design model represents a level of abstraction close to the source code. For example, classes in the design model typically have a language and model properties assigned, which define the mapping to code.
2. Creating
Packages in the Design Model
A package is a general-purpose model element that organizes model elements into groups. A system may be thought of as a single, high-level package, with everything else in the system contained in it.
For
more information about packages, refer to the Package
topic in the Rational Rose online help.
3. Create Layers
within the Design Model
A model may contain several layers, which you visualize as packages, one package per layer. Layers may be nested. To distinguish packages as layers you should add the stereotype "layer" to each package. In addition, you should use the Documentation field in the Package Specification to describe the package.
4. Document the Model
Organization
Every model needs a class diagram showing the layer and subsystem organization of the model. This should be the Main diagram. Consider renaming the diagram "Model Organization." Drag and drop the packages that represent the layers or subsystems into the diagram.
