Rational Rose model import Release Notes

© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Release notes

1.0 Limitations
   1.1 pointer type parameters and arguments
   1.2 Importing Actors in Rose
   1.3 constraints on association
2.0 Known problems and workarounds
   2.1 Usage of pathmap symbols in external doc references

1.0 Limitations

1.1 pointer type parameters and arguments

In Rational Rose®, if a argument or parameter is defined as pointer type, it will import with the same type as in Rose; however, the pointer type is indicated as multiplicity (*).

1.2 Importing Actors in Rose

In Rational Rose, an Actor is represented as a class element that is stereotyped as Actor; in the new Rational Modeling products, an actual UML 2 Actor model element exists (the Actor model element is not a stereotyped class).

During import, the Rose Model Import wizard maps stereotyped classes from Rose to UML 2 actor model elements when you select the Interpret UML 2 conventions check box in the Rose Model Import wizard preferences.

If you clear the Interpret UML 2 conventions check box, all actors in the Rose model import as UML 2 classes stereotyped as actor.

1.3 constraints on association

If a Rose model role has a constraint on a non-navigable association, it does not get imported as a constraint on Association.

This is also evident in the cases where Rose model has constraints on roles on a directed Actor-Usecase association as the Actor does not own the roles in UML 2.

Constraint movement is done from Association to the Classifier on the other end only if there is navigability in the association, and that navigability is going to be maintained in the imported model (thereby handling the case for Actor and Usecase associations).

2.0 Known problems and workarounds

2.1 Usage of pathmap symbols in external doc references

If an external file reference contains a pathmap symbol:

  1. The pathmap symbol will be resolved if it is a not prefixed
    pathmap (i.e. it does not occur at the start of the file path).
  2. For prefixed pathmap symbols, you are prompted to update the pathmap
    symbol table in the Rose Model Import wizard. The value for the pathmap symbol should be derived from the
    ROSE pathmap values and all recursive calls should be resolved.

Workaround: You must update the pathmap by creating a new symbol (Windows > Preferences > Modeling > Pathmaps > Linked Resources > New) and then select the new symbol and add it to the pathmap (Windows > Preferences > Modeling > Pathmaps).