You can use the
Rational
Rose Model Subunit Conversion page of the
Rational
Rose Model Import wizard for several reasons; you can import
Rose subunits (such as .cat and .sub files) into independent models or you can import subunits as fragments. You can also
take a mixed approach by importing some subunits as models and other
subunits as fragments.
Before you begin
Before you specify which subunits
you want to import as separate models or as fragments, you must select
the
Convert subunits to models or fragments 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. Not all Rose models contain subunits;
if your model does not contain subunits, you can advance to the next
page in the wizard.
About this task
To import Rose subunits as independent models or as fragments:
Procedure
- Select the Convert subunits to models or fragments check
box. Notice how all of the subunits in the Rose model
are displayed in the Subunits list; using this list, you can specify
whether you want subunits to import as fragments (analogous to subunits)
or as independent models.
Note: Steps 2, 4, and 5 are only available
when you import one or more subunits as models.
- 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 push
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.
- In the Subunit list table, select a subunit name, then
click the corresponding Fragment or Model option
depending upon how you want to import a specific subunit. The Fragment and Model options
are displayed under the Convert to column; Fragment is
listed by default.
Note: You can also select the Convert
all subunits to models check box to toggle the default
setting of Fragment.
- 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.efx.
- 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.efx, 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, select 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.
- If you want to import one of more subunits as fragments,
specify the fragment model-naming conventions by completing one of
the following steps:
- Click Use subunit file names to have
your fragment files use the name of the actual subunit file name.
For example, if a Rose subunit file has a name of Analysis_Classes.cat,
the fragment name after import is Analysis_Classes.emx.
- Click Use subunit package names to
have fragments 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 fragment name after import is Analysis_Artifacts.efx,
regardless of the original subunit file name.
- 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.
Results
After you import the Rose model and have specified that Rose
subunits import as independent models or are converted to fragments,
the models and fragments are displayed in the
Project Explorer view.
Shortcuts to the imported subunit models are also displayed for quick
navigation in the
Project Explorer view. All
Rose models that include Rose subunit models convert to a model file
with an .emx file extension; fragments have an .efx file extension.