You can use the mapping table for collaboration diagram model elements to understand the differences in metamodel implementation and the differences in UML notation between Rational Rose® and the Rational® modeling products in the Software Development Platform—Rational Software Modeler and Rational Software Architect. Collaboration diagrams are called communication diagrams in UML 2.0.
Rational Rose (UML 1.4) | Software Architect and Software Modeler (UML 2.0) |
---|---|
Class Instance | Lifeline that represents a property in the Collaboration. |
Data Token | Not imported Data tokens do not have a corresponding model element in UML 2.0. |
Link | Message Pathway |
Mechanism | Maps to a Collaboration and an Interaction where the latter is contained by the former. There are some structural differences to consider: |
Message Arrow | Not imported. In Rose, the arrow figure and message label (with the number and the message name) are distinct views on the diagram and can be combined in various ways. In the UML communication diagram, every message label has its own arrow view. |
Message Label | UML2 message label with both the arrow and the label text. |
Object | Lifeline representing a property in the Collaboration. |
Return Messages | Return Messages. Return Messages import, but they do not appear in the diagram editor. |
Self-link | Message Pathway The appearance of this connector is very different
in UML 2.0. After import, the connector does not appear as an arc, but as
a square connector with three bend points on the bottom-right corner of the
lifeline.
Note: The original placement of messages cannot be
maintained as in the Rose model because message views are stacked vertically
on the connector.
|