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.

While most of the Rose Import online help topics apply to all of the new UML modeling products, several topics that discuss visual editing and transformations only apply to Rational Software Architect.

Model-driven development
For IBM Rational Rose users, the Rational UML modeling products in theRational Software Delivery Platform present a new paradigm for code and model development. Get started by reviewing the basic differences between round-trip engineering (RTE), visual editing, and transformation capabilities.
UML modeling and visual editing
You can develop your project from the top down through Unified Modeling Language (UML) analysis and design models. In addition, you can visualize your code with dynamically generated topic diagrams as well as manually created class diagrams.
Transformations
A transformation is the mechanism that takes a source set of elements and changes them into a new target set of elements. Like round-trip engineering (RTE) in Rational Rose, the result of a transformation can be code generated from a model. However, transformations are customizable and vastly more powerful than RTE in what they can do.
Subunits and fragments
In the IBM Rational UML modeling products, you use fragments to logically divide models into multiple levels and sections. In Rational Rose, you use a similar concept called subunits to refine and break up a model. When you import Rose models, you can import subunits independent models, fragments, or packages.
Multiple models
A key difference between Rational Rose and the new UML modeling products involve models and model management. You can have multiple projects and models open at the same time in the new UML modeling products, whereas you can only open one model at a time in Rose.
Rose top-level model views
Rational Rose required the use of the following views in every model: use case, logical, component, and deployment. While all Rose models import using this model organization structure, you are not required to keep your models organized in the same way within the new Rational UML modeling products.
Model property sets and UML profiles
The new UML modeling products store domain-specific information as properties of stereotypes in UML profiles.

Related tasks:

Migrating Rose models

Preparing for Rose model migration

Related reference:

User interface reference for Rose users

Rose model import preferences

Rose import artifacts

Feedback