Before you begin to import your Rational Rose models
to the new Rational® UML
modeling products, be sure that you store a copy of your model in a recoverable
location, verify that your system meets the minimum system requirements, and
so on. Properly preparing to import your Rose models will help
you migrate models and related artifacts.
Note: When you import your Rose models, it is important
to know that you are only importing your UML models and related files such
as property sets. If you used Rose to round-trip engineer (RTE) your source
code, you do not need the code available at the time you import your model.
You can import your source code using standard Eclipse capabilities.
Before
you begin to import your Rose models, complete these steps and have the required
information available.
To prepare to import a Rose model:
- Ensure that your system meets all of the memory, hardware, and
software requirements. It is possible that your imported model will be much
larger than the size of your original Rose model; therefore, disk space may
be an issue for large Rose models. For example, if your Rose model accesses
a reference model, the contents of the referenced model are included in the
model you are importing. If your original model is 10 MB and references a
30 MB model, the imported model size is at least 40 MB in size.
- Install Rose on the machine on which you plan to import your Rose
model. Ideally, you should use the same machine that you used to create the
Rose model so the Rose Model Import wizard has access to all of the registry
settings, stereotype initialization (INI) files, stereotype graphics, and
other related Rose Add-In information.
- Determine if you want Rose package (.CAT) and component packages
(.SUB) subunit files to import as separate models, or as packages inside the
imported UML 2.0. When you import a Rose model using the Rose Model Import
wizard, you can specify several settings that allow you to control how subunits
import.
- Verify that the model you are going to import is based on petal
version 47 or higher. If you import a Rose model that is based on petal version
46 or below, you may lose data. Consider upgrading your model to a supported
petal version in Rose before you import your model. In addition to model (MDL)
files, check the petal version of all controlled units such as CAT, SUB, PRC,
and PRP files.
- Make sure that your model and all related files such as subunits
are backed up in a recoverable location.
- Try to reduce the size of your Rose model before you import. Go
through your model and delete model artifacts that you know you will not use
after import. When you reduce the size of your model, the import process is
faster and your imported model is less complex and it will be easier to identify
potential problems.
- Open your model in Rose and verify that you have access to all
subunits and external files associated with your model. You can use the Check
Model command in Rose to look for unresolved references in your
model. You cannot resolve broken references after you import a Rose model.
- If possible, import your Rose model on the same system that you
used to create the model. Using the same system is extremely important because
the Rational Rose Model Import wizard has access to all
information such as stereotype configuration files and associated image files
that Rose uses.
Now you are ready to begin to import your Rose model files.