Before you begin the XDE model import process, it is important
that you understand the main XDE model migration limitations.
The XDE model import process has the following limitations:
After you import your XDE model, it is probable that your imported model
will contain numerous error, warning, and informational messages in the XDE
Import Report view. These messages are expected because XDE is based on UML
1.4, whereas the new modeling products are based on UML 2.0. Most messages
in the XDE Import Report view point out specific differences in UML notation
and how certain XDE model elements map into the Rational® modeling products.
The diagram layout rules, as well as the default colors, fonts, and styles,
have changed significantly from XDE, so most diagrams look different after
migration even if they are semantically identical.
XDE has many add-ins that do useful things with UML models, such as the
add-ins for patterns, code templates, synchronization between models and code,
database modeling, and Rational RequisitePro® integration. While
the Rational XDE
Model Import feature is able to migrate the models used by those add-ins,
it cannot migrate the add-ins themselves. So the Rational modeling products will view
the imported model as a plain UML model and will not be able to usefully manipulate
the model in the same way that XDE could. Even when similar tools exist in
both XDE and the new Rational modeling products, the metadata stored
in the model has changed so significantly that the imported model will not
work with the Rational modeling
products version of the tool. For example, if an XDE model containing patterns
is imported, then the Rational modeling products will not be able to recognize
the patterns in the imported model or be able to do anything useful with those
patterns.
Note: You cannot migrate Rational XDE Extensibility (RXE) API
scripts.
The import process is one-way; once you import a model into the Rational modeling
products, you cannot bring the imported model back into XDE.
The Rational XDE
Model Import wizard uses a lot of memory during the model import process.
Typically, you should expect to use 1.25 times the amount of memory required
to load the imported model. If you notice memory issues while working with
the model in XDE, there is a good chance you may encounter memory issues during
the import process.
Models and user-defined profiles must be migrated to separate projects
because models will not merge correctly unless the user-defined profiles are
kept in a different project. Although compare and merge is not important
during the model import process, it may be important for models used in team
development.