Importing Rational Rose subunits as models, root packages, or fragments

You can import subunits from Rational Rose® models into the Rational® UML modeling products in several ways by specifying import options in the Rational Rose Model Import wizard, on the Rational Rose Model Subunit Conversion page.

Before you begin

Before you specify which subunits to import as separate models, root packages, or fragments, you must select the Convert subunits to fragments, models or packages check box. If the Rational Rose model that you are importing references subunits, and you do not select this check box, all subunit content is copied into packages inside the imported model. Not all Rational Rose models contain subunits; if your model does not contain subunits, you can advance to the next page of the Rational Rose Model Import wizard.

About this task

you can import files that have .cat and .sub as file name extensions into independent models and root packages, or you can import them as fragments. You can also map subunits to models or packages from one or more existing modeling projects. You can apply a mixed approach by remapping subunits to models and root packages in existing modeling projects, or you can import several subunits as models, some as root packages, and other subunits as fragments. To avoid manually configuring conversion options for the same set of subunits for multiple import operations, you can create a conversion pattern and apply the pattern for the subsequent import operations.

To import Rational Rose subunits:
  1. Decide how to import the subunits:
    • To map Rose subunits to existing models or root packages from one or more existing modeling projects, proceed to step 2.
    • To import Rose subunits as independent models, root packages, or fragments, proceed to step 3.
    • To save the conversion options for the subunits and apply them to a subsequent import operation, proceed to step 4
  2. To map Rose subunits to existing models or root packages from one or more existing modeling projects complete the following steps:
    1. In the Rational Rose Model Import wizard, on the Rational Rose Model Subunit Conversion page, select the Map subunits to existing models/packages check box.
    2. In the Source Directory field, navigate to and select one or more projects, and click OK. The subunits are updated in the Subunits list table, with Convert to/Share set to Share and Sharable set to Yes. The Convert To/Share area appears empty for all nested subunits of a sharable subunit because you cannot modify it. The other subunits that cannot be shared have the previous values preserved in the Convert To/Share column.
    3. If you do not want to share a subunit, modify the Convert To/Share options (Fragment, Model or Package) for individual subunits. After the import process, each subunit imports as a new fragment, model, or root package based on the option that you specify. All the nested subunits become unshared automatically.
    4. If the subunit has Sharable set to Yes but Convert To/Share section is not set to Share, you can modify the Convert To/Share to Share to share the subunit. The Convert To/Share appears empty for all nested subunits of a sharable subunit; you cannot modify this option.
  3. To import Rose subunits as independent models, root packages, or fragments, complete the following steps:
    1. In the Rational Rose Model Import wizard, on the Rational Rose Model Subunit Conversion page, select the Convert subunits to fragments, models or packages check box. The subunits in the Rational Rose model are displayed in the Subunits list; you can use this list to specify whether subunits import as fragments, which are analogous to subunits in Rational Rose; as independent models; or as root packages.
      Note: Steps 3.b, 3.d, and 3.e are available only when you import one or more subunits as models or root packages.
    2. Specify a new project or browse to an existing one.
      Note: If you create a new project outside the default location, clear the Use default check box.
    3. In the Subunit list table, select a subunit name; then, in the Convert to/Share column, specify whether to import the subunit as a fragment, model, or package.
      Note: To make quick global changes for how to import subunits, right-click any subunit name in the subunit list; then convert all subunits to fragments, models, or packages. If you selected the Map subunits to existing models/packages option, you can also convert all non-shared subunits to fragments, models, or packages.
    4. Specify the directory structure for the imported subunit models or root packages: to keep the hierarchical structure from Rational Rose, click With subunit directory structure; to impose a flat directory structure, click In one directory.
    5. Specify the naming conventions for the imported subunit models or root packages: to use the subunit file name from Rational Rose, click Use subunit file names (for example, Analysis_Classes.cat becomes Analysis_Classes.emx); to use the package name from Rational Rose that contains the subunit, click Use subunit package names (for example, a subunit in a package named Analysis_Artifacts, becomes Analysis_Artifacts.emx, regardless of the original subunit file name).
      Important: If a model in the destination project has the same name, a conflict occurs. When a conflict occurs, the subunit model name is suffixed with _1 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 options when you import a Rational Rose model that references subunits. If a conflict occurs, resolve all name conflicts and import the model again.
    6. If you import one or more subunits as fragments, specify the naming conventions for the fragments: to use the subunit file name from Rational Rose, click Use subunit file names; to use the package name from Rational Rose that contains the subunit, click Use subunit package names.
    7. To advance to the Map Property Sets page of the wizard, click Next.
  4. To save the conversion options for the subunits that you specified in step 2 or 3, and apply the options to a subsequent import operation, complete the following steps:
    1. To save the conversion options for subunits, click Save Selection, and in the Save Subunit Conversion Selections As dialog box, enter the name of the new file, and click Save.
    2. To load the previously saved selection for the same set of subunits, click Load Selection, and in the Load Subunit Conversion Selections Configuration dialog box select the file that contains the conversion options, and apply the file to the current subunit conversion wizard page.
    3. To restore the subunit conversion wizard page to the default selections, click Restore Defaults.

After you import the Rational Rose model and specify the import options, the models, root packages, and fragments are displayed in the Project Explorer view. Shortcuts to the imported subunit models are also displayed in the Project Explorer view. Subunits that are imported as new root packages or shared with existing root packages are referenced as an element import in the model. All Rational Rose models that include Rational Rose subunit models or root packages convert to model files with .emx file name extensions; fragments have .efx file name extensions.

What to do next


Feedback