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.
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:
Create a component diagram in the Component View
Create a subsystem structure that mirrors the Design Model structure
1. Create a component diagram in the Component View
In this step, you should:
2. Create a subsystem structure that mirrors the Design Model structure
Subsystems are modeled as packages. In this step you:
You can drag executable programs (.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.