Naming differences between UML 1.4 and later UML versions
The Unified Modeling Language (UML) changed in several
ways after version 1.4. While visual modeling tools such as IBM® Rational Rose® and IBM Rational® XDE support
UML 1.4, the new IBM Rational Software Architect Designer support
UML 2.0 and later. Use this topic as a quick reference to learn the
new names of specific model elements that changed during UML 2.0.
For example, a specific model element that defines who or
what performs a specific role was named a swimlane (or partition)
in UML 1.4, but is now named an activity partition. In
general, the most important changes between these UML versions are
in the area of behavioral diagrams; specifically, activity diagrams
and sequence diagrams. In some cases, a renamed model element indicates
significant change to the model element functionality since version
1.4.
At a very high level, the following information provides a
good place to start learning about the differences between UML 1.4
and UML 2.0 and later versions; the table is not meant to be a comprehensive
resource that documents every UML notation difference. For detailed
information about the UML and the various versions, refer to the following
resources:
Note: Model elements referenced in this table have a different
name between each version of UML; if a model element is not listed,
assume it has the same name as in UML 1.4.
| UML 1.4 model element name | UML 2.0 and later model element name |
|---|---|
| Association end | Member end and Property |
| Object (when used in activity diagrams) | Object node |
| Object (when used in sequence diagrams) | Lifeline |
| Collaboration diagrams | Communication diagrams |
| Swimlane (or partition) | ActivityPartition |
| Activity | Structured activity node |
| Decision | Decision node or merge node |
| Final State or end state | Final Activity Node |
| Initial state or start state | Initial node |
| Object Instance (in activity diagrams) | Central buffer node |
| State | Structured activity node |
| State machine | Structured activity node |
| Synchronization bar (synch bar) | Fork node or Join node |
| Transition (on an activity diagram) | Control flow |
| Transition condition (guard condition) | Control flow guard |
| Formal Argument | Template Parameter Substitution |
| Formal Arguments (collection of Formal Arguments) | Template Binding |
| Three-tiered diagrams | Class diagrams |
| Class Instance | Lifeline |
| Self-link | Message pathway |
| Connection relationship | Communication Path |
| Process (in a deployment diagram) | Artifact |
| Processor | Execution environment |
| Destruction marker | Stop node |
| Focus of Control | Execution Occurrence |
| Action | UML activity |
| State diagram | Statechart diagram |