This tutorial walks you through the workflow of migrating a model from Rational Rose RealTime (RoseRT) to DevOps Model RealTime, using a basic sample with minimal structure, including a capsule and a state diagram that includes an initial point, an initial transition, and a single state
Note: If you are planning a full-scale migration, refer to the Introduction topic, which provides detailed planning guidance from a project-level perspective.
Prerequisites
Before starting, ensure you have:
You should already have a working model in RoseRT. Here's an example of what such a model may look like:
Note the full path where the .mdl file is stored. This will be useful in adding the model while importing RoseRT model in Model RealTime.
Launch Eclipse with a workspace set up for Model RealTime development.
Go to the File menu and choose Import.
In the Import wizard, expand the Other section and select Rational Rose RealTime Model.
Click Next to proceed.
Browse to the location of the saved RoseRT model file.
Choose where to import the model:
Click Next.
The next page shows controlled units and path mappings:
For simple models, no changes are needed. Click Finish.
After the import:
You’ll see a Hello World project in the Project Explorer.
The imported state diagram should closely match what you saw in RoseRT (when you opened the model in RoseRT ):
The layout may vary slightly, but the model structure and semantics are preserved.
Once your model is successfully imported, the next step is to build the component in Model RealTime.
In the Project Explorer, right-click to build the .tcjs file.
This compiles the model and generates code using Model RealTime.
Note: Before building the component, ensure that the compiler selected is compatible with the TargetRTS configuration. In many cases, the development environment for RoseRT may be using an outdated compiler. When transitioning to build the same component using Model RealTime, it's often necessary to update the development environment by switching to a more recent compiler version. For more information, see Post Migration Best Practices.