Statechart diagram model element notation mappings

You can use the mapping table for Statechart diagram model elements to understand the differences between UML 1.4 and UML 2.0.

UML 1.4 UML 2.0
Action UML Activity (for actions that appear on transitions and states)
Note: The condition (if any) of a Rose action imports as a UML 2.0 guard constraint on a self-transition. Its specification is an OpaqueExpression with a body specified as the Rose condition expression when the Action or Send Event is implemented as the effect of the activity self-transition.
OnEntry (Action) Entry Activity
Do (Action) Do Activity
OnExit (Action) Exit Activity
Note: Multiple occurrences of Entry, Exit, and Do activities are concatenated into the body of a single activity because UML 2.0 allows only one of each kind of activity in a state.
Activity State
Decision Pseudostate with Kind set to Choice.
Event

A State owned Event maps to a self-transition owned by a state.

An Event specified on a self-transition relationship maps to a guard on the self-transition relationship.

Any Event owned by a self-transition relationship maps to a UML Any Trigger.

Note: An event (possibly with arguments) that triggers an action imports as a UML 2.0 Trigger on a self-transition. The trigger name matches the event name and arguments list of the Rose event.
(Send Event) with arguments on a transition and a send target The body property of a nameless activity owned by a transition
Event Argument Name of AnyTrigger
State State
(Initial State) Pseudostate with Kind property set to Initial.
(Shallow History State) Pseudostate with Kind property set to shallowHistory
(Deep History State) Pseudostate with Kind property set to deepHistory
State Diagram Statechart diagram

If there are nested diagrams, they will be moved up the containment tree and are owned by the state machine.

State Machine (owned by an operation) State machine (owned by the class of an operation)

The operation references the state machine as its method.

Synchronization Bar Pseudostate with Kind property set to join or fork.
Transition Event Any Trigger
Transition Guard A constraint with the Specification body equal to the guard text.
Transition Send Event The send event name, target, and arguments are combined in the body of the effect activity created for the Rose action.
Related reference
Activity diagram model element UML notation differences
Class diagram model element UML notation differences
Collaboration diagram model element notation differences
Component diagram model element notation differences
Deployment diagram model element notation differences
Sequence diagram model element notation differences
Use Case diagram model element notation differences
Notational differences in expressing multiplicity
Specific UML 2.0 semantic mapping
Feedback
(C) Copyright IBM Corporation 2004, 2005. All Rights Reserved.