You can use the Import Rose Subunits as Independent Models page
of the Rational Rose Model Import wizard to create independent
UML 2.0 models from Rose subunits such as .cat and .sub files. You can also
use this page to map Rose subunits to existing UML 2.0 models.
Before you specify which subunits you want to import as separate models,
you must select the Create Independent Models From Rose Subunits check
box. If you do not select this check box and the Rose model you are importing
references subunits, all subunit content is copied into packages inside the
imported model.
To import Rose subunits as independent models:
- Click the Create independent models from rose subunits check
box.
- Select a new project or reference an existing one by completing
one of the following steps:
- Click Existing project and then navigate and
specify an already defined project using the Browse button.
- Click New project, type a project name, and
then specify a location.
Note: If you decide to create a new project outside of the default location,
clear the Use default check box.
- Specify how you want the subunit model directory structure to appear
after import by completing one of the following steps:
- Click With subunit directory structure to keep
the subunit models in the same hierarchical Rose directory structure.
- Click In one directory to import the subunit
models in a flat directory structure, regardless of how they were structured
in Rose.
- Specify the subunit model naming conventions by completing one
of the following steps:
- Click Use subunit file names to have your imported
subunit models use the name of the actual subunit file name. For example,
if a Rose subunit file has a name of Analysis_Classes.cat, the subunit model
after import is named Analysis_Classes.emx.
- Click Use subunit package names to have your
imported subunit models use the name of the package that contains the Rose
subunit. For example, if a Rose subunit resides inside a package named Analysis_Artifacts,
the subunit model name after import is Analysis_Artifacts.emx, regardless
of the original subunit file name.
Important: If a model already exists in the destination
project with the same name, a model name conflict occurs. When a conflict
occurs, the subunit model name is suffixed with a
_1 string
to give the subunit model a unique name. In addition, a warning message is
displayed in the
Problems view.
To avoid model
name conflicts, click the
With subunit directory structure and
Use
subunit file names check boxes when you import a Rose model that
references subunits. If a name conflict occurs, for best results, resolve
all name conflicts that occur and reimport the model so you can correctly
share created subunit models during subsequent imports of models with the
same subunit files.
- Complete one of the following steps:
- Click Map subunits to existing models to import
subunits into models that you have already imported or already created within
the Rational UML modeling products.
- Click Next to advance to the Map
Property Sets page of the Rose Model Import wizard.
After you import the Rose model and have specified that Rose subunits
import as independent models, the models and subunit models appear in the
Model Explorer view. Shortcuts to the imported subunit models also appear
for quick navigation in the Model Explorer view. All
Rose models including Rose subunit models convert to a model
file with an .emx file extension during the import process.