In large enterprises, there are many different teams working on various products and schedules. Each team may be working with a common development technology, but scheduling and/or dependencies may prevent migration to the newer tooling environment. Organizations that uses Rational Rose RealTime may wish to migrate to Rational Software Architect RealTime Edition, and may realize it is not possible to move all products at the same time. As a result, certain teams are required to continue development with Rational Rose RealTime tooling environment until their issues are resolved.
** Updated 14 September 2009 to include version 7.5.4 changes.
Refer to the attached PDF file to learn how you can continue work in the Rational Rose RealTime tooling while minimizing future migration efforts to the Rational Software Architect RealTime Edition tooling environment.
Note: If you can migrate your entire environment to the Rational Software Architect RealTime Edition tooling environment, review the migration whitepaper HERE to learn the best practices on how to successfully migrate from Rational Rose RealTime to Rational Software Architect RealTime Edition.