![Close [x]](http://dw1.s81c.com/i/c.gif){kind=small}
Summary
This tutorial stepped you through the process of migrating a UML model from Rational Rose to Rational Systems Developer. While the Rose Import Wizard is fairly straight-forward to use and provides you with quite a few options to consider while importing your model, what you do prior to importing the model can be even more important. Following these tips should make your migration efforts smooth and successful.- Open the model in Rose and load all associated subunits to verify that they are all available on the machine from which the import will be performed. It's also a good idea to run a Rose Check Model and fix some of the more blatant errors in the source model. If not, all those problems that you ignored in Rose are going to be migrated as well.
- When planning the migration of a Rose model that contains controlled units, it is important to think about how you want to partition the resulting Rational Systems Developer model since Rational Systems Developer does not support controlled units. You may want to consider breaking up the imported model into several models. Don't feel constrained by the previous organization of subunits, as the former subunits may be a too fine grain division (or it may be just right). You should be sure to plan for time to document the new model structure and describe its intended usage after the migration.
- If you have properties that are common to several models, or if you want to reduce the memory usage during import, and if you do not override any of the common property values, then you may want to consider importing the model properties separately. Then you'll just need to reference the shared profile project on the profile page of the Rose Model Import wizard.
- To retain stereotype icons in diagrams, either use the same computer for Rose as well as Rational Sofware Modeler, Software Architect, or Systems Developer, or follow the recommended steps to stereotype artifacts available during import.
- When migrating a Rose model to Rational Systems Developer, delete the parts of the Rose model that are at a "code-level" of abstraction. These parts include classes, operations, and attributes that directly correspond to code. Migrate only the parts of the Rose model that are at a higher level of abstraction (e.g., architectural and high-level design content).
Table of contents
Next steps from IBM
Rational Modeler is a free, UML 2.1 based environment that helps users to improve communication by specifying, visualizing and documenting their system, architecture and software designs using a standard graphical language.
Tags
Use the search field to find all types of content in My developerWorks with that tag.
Use the slider bar to see more or fewer tags.
Popular tags shows the top tags for this particular content zone (for example, Java technology, Linux, WebSphere).
My tags shows your tags for this particular content zone (for example, Java technology, Linux, WebSphere).
Use the search field to find all types of content in My developerWorks with that tag. Popular tags shows the top tags for this particular content zone (for example, Java technology, Linux, WebSphere). My tags shows your tags for this particular content zone (for example, Java technology, Linux, WebSphere).
Popular tutorial tags |
My tutorial tagsSkip to tags list
Popular tutorial tags |
My tutorial tags
