Tool Mentor: Structuring the Implementation Model Using Rational Rose
Purpose
This tool mentor describes how to create and structure the model elements that represent the implementation model of a system.
This section provides links to additional information related to this tool mentor.
Overview
Component diagrams provide a physical view of the current model. A component diagram shows the organizations and dependencies among implementation elements, including source code files, binary code files, and executable files, modeled as components.
For
more information about Component Diagrams, see the Component
Diagrams (Overview) topic in the Rational Rose online help.
The following is a summary of the steps you perform to structure the implementation model:
1. Create a component diagram in the Component
View 
In this step, you should:
-
Rename the Main component diagram using a more descriptive title.
- Create additional component diagrams.
2. Create a subsystem structure that mirrors the
Design Model structure
Subsystems are modeled as packages. In this step you:
-
Create a package structure in your Component View that mirrors the package structure you created for your design model in the Logical View.
- Create the actual components and assign their stereotypes and Language.
- Assign classes (or interfaces) to components.
- Optionally create a component from an existing software module.
You can drag executables (.exe), ActiveX (.ocx), Data Link Libraries (.dll), and Type Libraries (.tlb) from a source such as Explorer and drop them in a component package (either in the browser or a diagram). You should limit the elements you include to those that are external to your model or elements that are used by the modeled system only. These elements are not intended to be reverse engineered into the model since they rarely contain the complete source code. They are only necessary when building your system.
