Class diagram model element mappings

You can use the mapping table for Class 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.

Rational Rose (UML 1.4) Software Architect and Software Modeler (UML 2.0)
Argument Name Template Parameter with a Class as its ownedParameteredElement property. The Class name is the Rose argument name.
Argument Type Type property of the Rose stereotype.
Argument Default Value Reference to an existing class in the model, if available, otherwise the Default property of the Rose stereotype.
Association Role Association End property
The ends are owned in one of two ways:
  • They can be owned by the association which indicates that the end is not navigable.
  • They can be owned by the classifier that is the supplier of the association end on the association end to indicate that the end is navigable.
In Rose, Associations can only own roles.
Association with an Association Class Associations and the class are merged into a single element in UML2.0. Only the globally unique identifier (guid) of the association is preserved in the UML 2.0 model.
Formal Argument Template Parameter Substitution
Formal Arguments (collection of Formal Arguments) Template Binding
Template Parameter The Type attribute of the template parameter imports as a stereotype of the Template Parameter.
Three-Tier diagram Class diagram

The tiers are not imported. Consider recreating them with Geometric Shapes.

Interpret UML2.0 conventions in the Rose model check box
Note: When you select the Interpret UML2 conventions in the Rose model check box in the Rational Rose Model Import Preferences page of the Rose Model Import wizard, you enable specific UML 2.0 semantics from Rose.
Attributes and Association Roles (whose names begin with a slash such as:
/owner
Derived property
Note: The slash is removed from the name.
Classes stereotyped as Primitive Primitive Types, unless they own nested classifiers or behaviors such as state machines. UML2 Primitive Types cannot contain these constructs.
Classes stereotyped as Datatype Primitive Types, unless they own nested classifiers or behaviors such as state machines. UML2 Primitive Types cannot contain these constructs. The Datatype stereotype is retained as a keyword to distinguish these from other primitive types.
Association ends that are constrained as Union Derived Union properties
Association ends that are constrained as Unique Unique properties
Association ends that are constrained as Ordered Ordered properties
Association ends that are constrained as subsets <property-name> SubsettedProperty Collections (properties referencing the subsetted properties)
Association ends that are constrained as redefines <property-name> RefinedProperty Collections (properties referencing the subsetted properties)
Dependency relationships stereotyped as Import between two packages PackageImports
Dependency relationships stereotyped as Import between a namespace and another element, and where both elements are not packages ElementImports
Properties in the UML 2.0 model that are not association ends Unique properties
Note: Properties in the UML 2.0 model that are association ends are always unique when you select the Interpret UML2.0 conventions in the Rose model check box.
Related tasks
Specifying Rose model import preferences
Related reference
Activity diagram model element mappings
Collaboration diagram model element mappings
Component diagram model element mappings
Deployment diagram model element mappings
Sequence diagram model element mappings
Statechart diagram model element mappings
Use Case diagram model element mappings
Notational differences in expressing multiplicity
Terms of use | Feedback
(C) Copyright IBM Corporation 2004, 2005. All Rights Reserved.