UML element mappings between Rational Rose and later Rational modeling products

In the Rose Model Import wizard, on the Rational Rose® Model Import Preferences page, you can select the Interpret UML2 conventions in the Rose model check box to enable later UML semantics for the elements from the Rational Rose model.
Rational Rose (UML 1.4) Rational® modeling products (UML 2.0 and later)
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.

Feedback