When you import a IBM Rational Rose model into the new UML modeling products, there are several model-related artifacts such as controlled units and property sets that you need during the import process in addition to the basic Rose model (MDL). Some artifacts, such as stereotype configuration files and model property sets import into UML 2.0 profiles, while other artifacts, such as Rose workspace files (WSP), are not needed or used after import.
The following table defines and describes model-related artifacts and what happens to them during the import process. You can use this list when you are preparing to gather all of the necessary files needed to successfully import your Rose model.
Rose artifact | Description | What happens on import |
---|---|---|
Controlled units: |
You can use Rose controlled units to break up a model into individual chunks of information. Controlled units help you share parts of a Rose model with multiple users, or simply reduce the size of a single file. | When you import a Rose model that references controlled units, all
content that resides inside the controlled unit is copied into the new model.
After import, you can only control models at the model level. Tip: After
import, consider using the refactoring feature to break packages into separate
resources.
|
External files | You can use external files to connect additional information that resides outside a model to a specific part of a model. For example, you might connect a use case to a document that provides more information about the use case. | External files are converted to absolute paths; external files are
not copied into the Eclipse workspace. Note: Unlike Rose, the
new UML modeling products use path maps for references to UML model elements
only. You cannot use these path map variables to create relative paths to
external files like you can in Rose.
|
Model property sets (PTY) | Model property sets are information that is applied to specific Rose model elements. Properties have types such as string, enumeration, text, Boolean, float, and integer. | UML 2.0 profiles are created from Rose properties declared in the model, not necessarily the PTY file. |
Reference models | Reference models are somewhat similar to controlled units. Reference models contain content that your Rose model accesses for additional information. | When you import a Rose model that accesses a reference model, all
content from the referenced model is copied into the new model. Note: Referenced
models may significantly increase the size of your imported model.
|
Registry files (REG) | The Rose registry files reference artifacts such as DefaultStereotype.ini files that are needed when importing all stereotypes. You must create these when needed. Refer to the Rose import release notes for details. | Rose registry files are critical when importing Rose models created in Linux™ and UNIX® environments. |
Rose model (MDL) | A Rose model is a file that contains most of the content within a model. Other model content may reside within controlled units such as a CAT file. Rose models are based on ASCII-based text files. | Converts to a model file with an .emx file extension. |
Rose model workspace (WSP) | A Rose model workspace is a snapshot of all currently loaded Rose controlled units and open diagrams. By defining one or more workspace, you can set up your working environment in Rose and return to that environment each time you are ready to work. | A Rose model workspace file is not imported because the Rational® UML modeling products do not have the concept of controlled units. Model information is only controlled at the model level; you cannot control model information at the same granularity as Rose. |
Stereotype configuration files (for example, stereotype.ini and DefaultStereotypes.ini) | A stereotype configuration file defines a set of Rose stereotypes, including the location of icon files as well as settings that affect the usage and display of the defined stereotypes. Typically, the extension of a stereotype configuration file is .ini, but any extension is allowed. | UML 2.0 profiles are created from stereotypes defined in the stereotype.ini file. |
Stereotype image files (EMF, WMF, and BMP) | Stereotype image files are typically referenced by DefaultStereotype.ini files and other stereotype configuration files. They provide the stereotype image used in Rose model and diagram elements. | Stereotype image files are used in the import process and are defined in the resulting UML 2.0 profile. |