Rose model migration

To use Rose models in the new Rational® modeling products, you must migrate the models.

The Rose Import online help refers to IBM® DevOps Software Architect and IBM Rational Software Modeler as Rational modeling products. While most of the online help topics apply to all of the tools, several topics that discuss visual editing and transformations do not apply toRational Software Modeler.

Limitations of Rose model migration
Before you begin the Rose model import process, it is important that you understand some of the main Rose model migration limitations.
Supported Rose Petal versions
There are many versions of Rational Rose and Petal (PTL), the platform-independent syntaxRational Rose uses to store models and model components in a file. Rational Rose models that contain petal version 47, 48, or 50 are the only versions that you can import into the new UML modeling products.
Rose import artifacts
When you import aIBM Rational Rose model into the new UML modeling products, there are several model-related artifacts such as subunits 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 profiles, while other artifacts, such as Rose workspace files (WSP), are not needed or used after import.
Key differences for Rose users
The UML modeling products in the IBM Rational Software Delivery Platform present a new paradigm for code and model development. Learn about the major differences between Rose and the new UML modeling products in the Rational Software Delivery Platform. Rational Software Architect combines the visual modeling aspect of Rational Rose with the advantages of visual editing and transformation services, while Rational Software Modeler represents stand-alone UML modeling.

Related tasks:

Importing Rational Rose models

Preparing for Rose model migration

Migrating Rose models

Feedback