Considerations for managing Rational DOORS projects
The project must exist in IBM® Rational® DOORS® before
you can connect to it from IBM Rational Rhapsody®.
In Rational DOORS,
create the project in which you can export Rational Rhapsody data
if the Rational DOORS project
does not exist.
Identifying formal modules to create
Use the Create module per package option to export
design elements from the IBM Rational Rhapsody project
to formal modules with the same names as their packages in the IBM Rational DOORS project.
If this option is disabled, all elements are exported to a single
formal module named RHAPSODY_MODULE.
Selecting metatypes for export
Use the IBM Rational DOORS export
options to select the types of elements that can be exported, instead
of selecting individual elements to export.
Rational DOORS use case and sequence diagrams
Certain element types in IBM Rational Rhapsody are
connected in logical relationships with each other. For example, a
use case diagram in Rational Rhapsody can
hold references to the sequence diagram that describes it. Rational Rhapsody creates
a link between the relational shadows (for example, the use case shadow
and its corresponding sequence diagram shadow) during the export operation.
These connections are expressed in the IBM Rational DOORS formal
module, like any other Rational Rhapsody model
information.