Experimenting with the Rational Rose RealTime import process

Several differences exist between Rational Rose® RealTime and Rational® Software Architect RealTime Edition. You should take time to understand these differences so that you can make educated decisions about how to import Rational Rose RealTime models. When you understand the details of the import process, the transition from Rational Rose RealTime to Rational Software Architect RealTime Edition is easier.

About this task

When you experiment with the import process, you can identify missing references to controlled units, experiment with various import options, and examine how a model differs before and after the import process.

Use the following guidelines when you experiment with the Rational Rose RealTime model import process:

Procedure

  1. Analyze the controlled units in the model and determine how to import them. To save the settings for how to import controlled units, in the Rational Rose RealTime model import wizard, click Save Custom Conversion. You can use the Save Custom Conversion functionality to avoid modifying the conversion settings for each controlled unit multiple times. This functionality is particularly helpful when you experiment with migrating controlled units in very large models. If the import wizard detects a custom conversion configuration file in the workspace, you can click Load Custom Conversion to restore the saved settings for importing controlled units.
  2. Determine which stereotype configuration files should import as UML profiles. You can skip specific Rational Rose RealTime stereotypes during the import process if you determine that you no longer need them. If you import multiple models that use the same stereotype configuration file, you can create a new UML profile the first time that you import a model, and each subsequent model can reference existing UML profiles that were migrated. Multiple models can reference a common UML profile.
  3. Determine which property sets to import as UML profiles. To speed up the import process, you should import only the property sets that you plan to use after the migration. For example, you might want to import only used property sets and ignore any property sets that are only defined in the original model.
  4. In the Problems view, review any errors, warnings, or informational messages that occurred during the import process.
  5. To locate broken semantic rules in your model, in the Project Explorer view, right-click a model; then click Validate. Typically, any errors relate to adherence to UML requirements, logic, structure, and use.
  6. Compare the original Rational Rose RealTime models with the new models to learn how the UML notation differs from Rational Rose RealTime. Compare specific models and diagrams to discover the notational differences in UML and to verify the integrity of the diagrams.
  7. Repeat the process as needed. Adjust or improve each experiment by modifying the Rational Rose RealTime model and by changing various settings on the Preferences page of the Rational Rose RealTime wizard. For example, you might notice that strings that are too large for diagram elements overlap in sequence diagrams after the import process. You can modify the preferences for the diagram appearance to change the diagram layout or font settings.

Feedback