Activity diagram to activity diagram mappings (Connector for IBM Rational Rose)
Each Activity Diagram is created as an Activity Diagram or General Flow Diagram in Modeler. You choose whether to import Activity Diagrams as Activity Diagrams or General Flow Diagrams on the Set Import Options page of Connector for IBM Rational Rose.
This topic documents Activity Diagram to Activity Diagram mappings. For information about Activity Diagram to General Flow Diagram mappings, click here
Each Activity Diagram is created as an Activity Diagram in Modeler.
The name of the Activity Diagram in Modeler is set to that of the Activity Diagram in Rose.
When State Machine owned Activity Diagrams are imported, the State Machine is imported as an Activity, or a State Machine and an Activity (the Activity is required to own the Activity Diagram in Modeler):
• If the State Machine that owns the Activity Diagram does not own any Statechart Diagrams or Statechart Diagram items, the State Machine is imported as an Activity. The name of the Activity is set to that of the State Machine.
• If the State Machine that owns the Activity Diagram also owns one or more Statechart Diagram or Statechart Diagram item, the State Machine is imported as a State Machine and an Activity. The name of the imported State Machine is set to that of the State Machine in Rose. The name of the imported Activity is set to that of the State Machine in Rose suffixed by _Activity.
The items on an Activity Diagram are imported as follows.
Activity
Each Activity is created as a Call Behavior Action and linked Activity in Modeler.
If the Activity is stereotyped by the Business Activity or Business Transaction stereotype in the Rose model, the imported Activity is stereotyped by the «Business Activity» or «Business Transaction» stereotype in Modeler. Likewise for other Stereotypes that are applied to Activities in Rose.
 |
Nested Activities are not imported.
|
The following properties are imported.
|
Rose Property
|
Modeler Property
|
|---|---|
|
Documentation
|
Description of the Call Behavior Action.
|
|
Name
|
Name of the Call Behavior Action and Activity.
|
|
State / Activity History
(results in Shallow History)
|
See History State that follows.
|
|
Sub State / Activity History
(results in Deep History)
|
See History State that follows.
|
Control Flow
Each Control Flow is created as a Control Flow in Modeler. The following properties are imported.
|
Rose Property
|
Modeler Property
|
|---|---|
|
Documentation
|
Description
|
|
Name
|
Name
|
Decision
Each Decision is created as a Decision Node in Modeler. The following properties are imported.
|
Rose Property
|
Modeler Property
|
|---|---|
|
Documentation
|
Description
|
|
Name
|
Name
|
End State
Each End State is created as an Activity Final Node in Modeler. The following properties are imported.
|
Rose Property
|
Modeler Property
|
|---|---|
|
Documentation
|
Description
|
|
Name
|
Name
|
History State
Each History State is created as a Call Behavior Action and linked Activity in Modeler. The Call Behavior Action is linked to the Activity through the Linked Item association.
The following properties are imported.
|
Rose Property
|
Modeler Property
|
|---|---|
|
Documentation
|
Description of the Call Behavior Action
|
|
Name
|
Name of the Call Behavior Action and Activity
|
Note (on diagram)
Each Note is created as a Note in Modeler. Note Links are imported.
Object
Each Object is created as an Input Pin or Output Pin in Modeler:
• When an Object has an incoming Object Flow from an Activity, an Output Pin is created on the Call Behavior Action that is created for the source Activity.
• When an Object has an outgoing Object Flow to an Activity, an Output Pin is created on the Call Behavior Action that is created for the target Activity.
• When an Object has an incoming Object Flow from an Activity and an outgoing Object Flow to an Activity, an Input Pin, Output Pin and Object Flow are created in the model.
The following properties are imported to Input Pins and Output Pins.
|
Rose Property
|
Modeler Property
|
|---|---|
|
Documentation
|
Description
|
|
Name
|
Name
|
|
Class
|
Data Type
|
The following properties are imported to Object Flows.
|
Rose Property
|
Modeler Property
|
|---|---|
|
Documentation
|
Description
|
|
Name
|
Name (derived from the names of the source Activity, Object and target Activity)
|
Object Flow
Each Control Flow determines the Call Behavior Action on which an Input Pin or Output Pin is created for an Object (see the preceding Object section). In addition, an Object Flow in Modeler can be created for an Object Flow, Object and Object Flow combination in Rose.
Start State
Each Start State is created as an Initial Node in Modeler. The following properties are imported.
|
Rose Property
|
Modeler Property
|
|---|---|
|
Documentation
|
Description
|
|
Name
|
Name
|
State
Each State is created as an Opaque Action and an associated Atomic State in Modeler. The Opaque Action references its associated Atomic State through a model object reference in its Body property.
When an Activity Diagram contains one or more States, Connector for IBM Rational Rose imports the State Machine that owns the Activity Diagram to Modeler. The Atomic States are created as child items of that State Machine.
Note that nested States are not imported. If a Stereotype is applied to a State in Rose, that Stereotype in Modeler will be applied to the Opaque Action, not the Atomic State.
The following properties are imported.
|
Rose Property
|
Modeler Property
|
|---|---|
|
Documentation
|
Description of the Opaque Action.
|
|
Name
|
Name of the Opaque Action and Atomic State.
|
|
State / Activity History
(results in Shallow History)
|
See History State above.
|
|
Sub State / Activity History
(results in Deep History)
|
See History State above.
|
State Transition
Each State Transition is created as a Control Flow. The following properties are imported.
|
Rose Property
|
Modeler Property
|
|---|---|
|
Documentation
|
Description
|
|
Guard Condition
|
Guard
|
|
|
Other properties are not imported.
|
Synchronization Bar
Each Horizontal Synchronization and Vertical Synchronization is created as a Fork Node in Modeler. In Modeler, a Fork Node has no properties.
In Modeler, the name of the Fork Node is not shown by default. You can show the name of a Fork Node through its view options.
If Connector for IBM Rational Rose creates a Fork Node that should be a Join Node: on the Modeler diagram create a Join Node, reconnect the Fork Node's incoming and outgoing Control Flows to the new Join Node, and then delete the Fork Node.
Swimlane
Each Swimlane is created as an Activity Partition in Modeler. The following properties are imported.
|
Rose Property
|
Modeler Property
|
|---|---|
|
Name
|
Name
|
|
Documentation
|
Description
|
Text Box
Each Text Box is created as a Note in Modeler.