DevOps Model RealTime takes an evolutionary leap from the existing Rational Rose RealTime (RoseRT) technology base for two main reasons:
Model RealTime is built on the Eclipse Integrated Development Environment (IDE) platform (www.eclipse.org) and
Model RealTime is based on UML2 https://www.omg.org/spec/UML/.
This big change in underlying technology means that the migration from the RoseRT tooling is complex and necessitates some paradigm shifts to accommodate the integrations into Eclipse and the news in UML2.
| Technology | Implementation RoseRT | Implementation Model RealTime |
|---|---|---|
| Base platform | Windows MFC application (porting technology allows it to run on Linux / Solaris) | Eclipse IDE and plugins in Java. Runs on many platforms. |
| Semantic specification | UML 1.x + Custom RealTime Extensions | UML 2.2 (+ some features from UML 2.3). RealTime extensions using the UML-RT profile. |
| Meta-model engine | Custom implementation | EMF (www.eclipse.org/modeling/emf/) |
| Workspace | Single model per workspace | Multiple projects + multiple models per workspace |
The RoseRT import wizard in Model RealTime attempts to make migration as seamless as possible, but it still requires direction at the enterprise and architecture level to ensure that all software components are migrated in a scalable way. The goal of this document is to give some guidance to the "Enterprise Architect" whose role is to oversee the migration process and coordinate teams to ensure that they migrate in a compatible way to each other within an enterprise organization.
This document assumes that the reader is an expert in RoseRT model structure and general functionality. In addition, knowledge of Source Control management systems such as Git or ClearCase is beneficial to understand how the resulting fragmented model is stored in the repository.