Integrations (PTC products, 3rd party products and code) > 3rd party product integrations (CM, DOORS, Rose, Simulink and XML) > Connector for IBM Rational Rose > Items and diagram mappings > Statechart diagram mappings (Connector for IBM Rational Rose)
  
Statechart diagram mappings (Connector for IBM Rational Rose)
Each Statechart Diagram is created as a State Diagram in Modeler.
Warning Connector for IBM Rational Rose does not validate any State Diagrams it creates in Modeler. You may have to modify imported State Diagrams to make them valid in Modeler.
The items on a Statechart Diagram are imported as follows.
Atomic State
Each Atomic State is created as either an Atomic State or Sequential State in Modeler:
• If the Atomic State does not own any history states, it is created as an Atomic State in Modeler.
• If the Atomic State owns history states, it is created as a Sequential State in Modeler.
The following properties are imported.
Rose Property
Modeler Property
Action
Activity or Event Action Block. For more information, see State Actions that follows.
Documentation
Description
Name
Name
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.
If an Atomic State is stereotyped in Rose, a Stereotype of the same name is applied to the State in Modeler (Connector for IBM Rational Rose creates the Stereotype if required).
Composite State
Each Composite State is created as a Sequential State in Modeler. The following properties are imported.
Rose Property
Modeler Property
Action
Activity or Event Action Block. For more information, see State Actions that follows.
Documentation
Description
Name
Name
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.
Warning If a composite state owns a State Diagram, the child State Diagram is not created in Modeler. This is because in Modeler, Sequential and Concurrent States cannot own State Diagrams.
If a Composite State is stereotyped in Rose, a Stereotype of the same name is applied to the State in Modeler (Connector for IBM Rational Rose creates the Stereotype if required).
End State
Each End State is created is created as a Final State in Modeler. The following properties are imported.
Rose Property
Modeler Property
Documentation
Description
Name
Name
Note that Actions are not imported, because in Modeler, Final States cannot have Activities or Event Action Blocks.
History State
Each History State is created as a History State in Modeler. The following properties are imported.
Rose Property
Modeler Property
Documentation
Description
Name
Name
Shallow History (Sub State / Activity History check box of parent State cleared)
Deep History check box cleared
Deep History (Sub State / Activity History check box of parent State selected)
Deep History check box selected
* 
Actions are not imported, because History States cannot have Activities or Event Action Blocks in Modeler.
Note (on diagram)
Each Note is created as a Note in Modeler. Note Links are not imported.
Start State
Each Start State is created as an Initial State in Modeler. The following properties are imported.
Rose Property
Modeler Property
Documentation
Description
Name
Name
Note that Actions are not imported, because in Modeler, Initial States cannot have Activities or Event Action Blocks.
State Machine
Each State Machine is created as a State Machine in Modeler.
A Statechart Diagram is always a child of a State Machine in Rose. Typically, when a Statechart Diagram is imported to Modeler, the State Diagram in Modeler is created as a child of a State Machine that is created for the owning State Machine in Rose. However, when a Statechart Diagram's State Machine is a child of an Atomic State in Rose, the State Machine is not imported because in Modeler Atomic States directly own State Diagrams.
The following properties are imported.
Rose Property
Modeler Property
Documentation
Description
Name
Name
State Actions
Each State Action is created as an Event Action Block or Activity on the State.
The When part of an Action is handled as follows:
Rose When Property Set To
Result in Modeler
On Entry
Event Action Block on State, Trigger Type set to Entry. If the Rose State has many On Entry actions, they are combined in a single Event Action Block in Modeler.
On Exit
Event Action Block on State, Trigger Type set to Exit. If the Rose State has many On Exit actions, they are combined in a single Event Action Block in Modeler.
On Event
Event Action Block on State. The Trigger Type of the Event Action Block is determined by the Event name in Rose. If the Event name in Rose...
Matches an Operation name of the State Diagram's owning Class, then Trigger Type is set to Call.
Starts with 'when', then Trigger Type is set to Change.
Starts with 'after', then Trigger Type is set to Time.
Does not match an Operation name, and does not start with either 'when' or 'after', then Trigger Type is set to Signal. If the Event name (in Rose) does not match an Event item in Modeler, Connector for IBM Rational Rose creates that Event in the model, and links it to the Event Action Block.
In each case, the Condition property of the Action is added to the Guard Condition property in Modeler. The Arguments property is not imported.
Do
If the Action calls an Operation, creates Operation in Modeler (if it does not exist), and then adds an Activity to the State to call that Operation.
If the Action does not call an Operation, creates Event Action Block on State, and sets its Trigger Type property to Entry. If an Event Action Block of Trigger Type Entry exists, Connector for IBM Rational Rose appends the Actions of that Event Action Block.
The Type part of an Action is handled as follows:
Rose Type Property Set To
Result in Modeler
Action
Name property is added to the Action property of the Event Action Block.
Sent Event
Name, Send Arguments and Send Target properties are added to the Action property of the Event Action Block.
State Transition
Each State Transition is created as a Transition and Event Action Block in Modeler. The following properties are imported.
Rose Property
Modeler Property
Event
Connector for IBM Rational Rose sets the Trigger Type to Signal, creates the Event in Modeler, and then links the Event to the Event Action Block
Guard Conditions
Guard Condition of Event Action Block
Action
Action of Event Action Block
Send Event
Action of Event Action Block
Send Arguments
Action of Event Action Block
Send Target
Action of Event Action Block
Note that the Arguments, Stereotype and Documentation properties are not imported.
If a State Transition is stereotyped in Rose, a Stereotype of the same name is applied to the Transition in Modeler (Connector for IBM Rational Rose creates the Stereotype if required).
Text Box
Each Text Box is created as a Note in Modeler.