Collaboration diagram mappings (Connector for IBM Rational Rose)
Each selected Collaboration Diagram is created as a Communication Diagram in Modeler. The name of the Communication Diagram is derived from the Package and Collaboration Diagram names in Rose:
<package name>::<collaboration diagram name>
The items on the Collaboration Diagram are imported as follows.
Actor Instance
Typically, each Actor Instance is created as an Actor in Modeler; however, if two or more Actor instances have no instance names and are based on the same Underlying Class, a single Actor is created in the model and used multiple times on the Modeler Communication Diagram.
The following instance properties are imported:
|
Rose Property
|
Modeler Property
|
|---|---|
|
Documentation
|
Description
|
|
Name
|
Name. Note that if the Actor Instance Name is blank, the Name of its underlying Class is used.
|
Class Instance
Each Class Instance is created as an Instance item on the Communication Diagram in Modeler. The underlying Class is created in Modeler. The following instance properties are imported:
|
Rose Property
|
Modeler Property
|
|---|---|
|
Multiple Instances
|
Multiple
|
|
Name
|
Instance Name
|
 |
• The Persistence property is not imported.
• If the underlying Class is not in the Packages selected for import, then the Class and its Package (only the Package item and not its content) are imported.
• If a Class instance does not have an underlying Class in Rose, Connector for IBM Rational Rose creates an underlying Class in Modeler. The underlying Class is created using a default name, such as Class14.
|
Data Token
Not imported.
Link
Each Link is created as a Link in Modeler.
Link Message
Each Link Message is created as either an Operation Message or an Event Message in Modeler:
• If the Name of the Link Message matches an Operation name in the destination Class or its Superclass, an Operation Message is created in Modeler (unless it exists).
• If the Name of the Link Message does not match an Operation name in the destination Class or its Superclass, an Event Message and its underlying Event are created in Modeler (unless they exists).
|
|
If the target of an Operation Message is an Actor, the link message is not imported because Modeler Actors do not support Operations.
|
The following properties of the Link Message are imported.
|
Rose Property
|
Modeler Property
|
|---|---|
|
Documentation
|
Description
|
|
Name
|
Name
|
|
Simple (Synchronization)
|
Call (Synchronous)
|
|
Synchronous (Synchronization)
|
Waiting (Synchronous)
|
|
Balking (Synchronization)
|
Balking (Synchronous)
|
|
Timeout (Synchronization)
|
Timed (Synchronous)
|
|
Asynchronous (Synchronization)
|
Asynchronous
|
|
Aperiodic (Frequency)
|
Episodic
|
|
Periodic (Frequency)
|
Periodic
|
Note (on diagram)
Each Note is created as a Note in Modeler. Note Links are not imported.
Object
Each Object is created as a Class Instance on the Communication Diagram in Modeler. The underlying Class is created in Modeler. The following instance properties are imported:
|
Rose Property
|
Modeler Property
|
|---|---|
|
Multiple Instances
|
Multiple
|
|
Name
|
Instance Name
|
|
|
If an object does not have an underlying Class in Rose, Connector for IBM Rational Rose creates an underlying Class in Modeler. The underlying Class is created using a default name, such as Class14.
|
Text Box
Each Text Box is created as a Note in Modeler.