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.
Related Rational Unified Process information: Activity:
Structure the Implementation Model.
Overview
Component diagrams provide a physical view of the current model. A
component diagram shows the organizations and dependencies among
software components, including source code components, binary code
components, and executable components. These diagrams also show the
externally-visible behavior of the components by displaying the
interfaces of the components. Calling dependencies among components
are shown as dependency relationships between components and
interfaces on other components. Note that the interfaces belong to
the logical view, but they can occur both in class diagrams and in
component diagrams.
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:
-
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 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 components you include to those that
are external to your model or components that are used by the modeled
system only. These components 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.
Copyright
© 1987 - 2001 Rational Software Corporation
|