Rational Rose RealTime import artifacts

When you import a Rational Rose® RealTime model into Rational® Software Architect RealTime Edition, you need several model-related artifacts during the import process, such as controlled units and property sets, in addition to the basic Rational Rose RealTime model (RTMDL). Some artifacts, such as stereotype configuration files and model property sets import into UML profiles.

The following table defines and describes model-related artifacts and what happens to them during the import process. You can use this list to prepare the files that are required to import a Rational Rose RealTime model successfully.

Rational Rose RealTime artifact Description What happens on import
Controlled units You can use Rational Rose RealTime controlled units to divide a model into individual pieces of information. Controlled units can help you to share parts of a Rational Rose RealTime model with multiple users or to reduce the size of a single file. When you import a Rational Rose RealTime model that references controlled units, you can specify that all content in the controlled unit be imported in any of the following formats:
  • As a fragment, which is semantically equivalent to a controlled unit in Rational Rose RealTime
  • As absorbed or uncontrolled in the owning model resource
  • As a new model
  • As a shortcut, or shadow package, that references the originally imported package that still resides in Rational Rose RealTime
External files You can use external files to connect additional information that resides outside a model to a specific part of a model. When you import a model with a reference to an external file, if there is an external document referenced through a pathmap, the model import wizard converts the Rational Rose RealTime pathmap to a GMF pathmap, and uses it to create the document link.
Model property sets (PTY) Model property sets contain custom information that is applied to specific Rational Rose RealTime model elements. Properties have types such as string, enumeration, text, Boolean, float, and integer. UML profiles are created from Rational Rose RealTime properties that are declared in the model, but not necessarily defined in the PTY file. The concept of property sets is maintained; however, they are implemented through UML profiles.
Reference models Reference models are somewhat similar to controlled units. Reference models contain content that your Rational Rose RealTime model accesses for additional information. When you import a Rational Rose RealTime 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 Rational Rose RealTime registry files reference artifacts such as DefaultStereotype.ini files that are necessary for importing all stereotypes. Rational Rose RealTime registry files are critical for importingRational Rose RealTime models that were created in Linux™ and UNIX® environments, because the stereotype information only imports if you specify a registry file.
Rational Rose RealTime model workspace (RTWKS) A model workspace contains basic configuration information for working with a Rational Rose RealTime model. Rational Rose RealTime model workspaces are not imported. However, during the import process, the Rational Rose RealTime model import wizard uses active component information from the *.rtusr file.
Rational Rose RealTime model (RTMDL) A Rational Rose RealTime model is a file that contains most of the content in a model. Other model content might reside in controlled units. Rational Rose RealTime models are based on text files. During the import process, the Rational Rose RealTime model converts to a model file that has .emx as a file name extension.
Stereotype configuration files (for example, stereotype.ini and DefaultStereotypes.ini) A stereotype configuration file defines a set of Rational Rose RealTime stereotypes, including the location of icon files and settings that affect the usage and display of the defined stereotypes. Typically, stereotype configuration files have .ini as a file name extension, but any extension is allowed. The stereotypes that are defined in the stereotype.ini file convert into UML profiles.
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 images for Rational Rose RealTime model and diagram elements. Stereotype image files are used in the import process and are defined in the resulting UML profile.


Feedback