This topic explains how to import files created with Rational RoseŽ, and export your Together projects to Rose's .mdl file format. You must obtain and install a license for a Together product with Rational Rose support in order to use this feature. (See Where to Get Help.)
Rose import/export requires that you have a working installation of Rose 98 or Rose 98 i. The import and export modules both spawn a Rose session and interact with Rose itself to perform the import or export operations. Because Together and Rose run concurrently, both require memory and other system resources. If the model is fairly large, be aware that even the recommended memory levels for Together may prove insufficient. A good rule of thumb is to always use the most powerful computer you have available for Rose import/export.
To import a Rose model:
Invoke the Rose Import module from the Tools menu or the Modules tab of the Explorer. The Open File dialog displays.
Enter the path/filename of Rose model file you wish to import and click OK.
A Rose session is started and the Rose model is added to your Together project
Notes:
Rose 98 is started by the converter during the import process. If the model file is updated by Rose 98 or the converter, it is automatically saved.
If the converter finds more than one diagram with the same name in one logical package, the diagram file names are modified by adding an incremented index to the end of the file name. For example, if there is already a diagram file named Main.vfUseCase and the converter needs to save another Main.vfUseCase file, then the latter one is saved as Main1.vfUseCase and the diagram names reflect the changed filename).
Note links ("Note anchors" in Rose terminology) are not imported.
If you have any older Rose models in a format previous to Rose98 (version 4.2), you can convert them using the Rose 98 Evaluation version. You can get that from Rational Software Corporation's Web site at www.rational.com/cgi-bin/www/rose98demo.cgi*
Make sure that the installation file you download is roseent8054c_timelocked2.exe.
When the converter starts Rose 98 to try to load any model of old format, it will ask you whether assign some language to the components or not. Answering 'yes' means that Rose 98 will create default components for all classes you have in your model.
To convert a Together model to Rose .mdl format:
Open a project in Together.
Invoke the Rose Export module from the Tools menu or the Modules tab in the Explorer.
A Rose session is started and the Together model is exported. Use Rose's Logical View to locate the exported classes.
The Export module uses some of the same Coroutine classes as SCC version control support. If you get an error message about missing Coroutine, see Administrator's Guide: Installation: SCC Version Control Support
Together's model structure is more flexible than Rose's. Rose models are always divided into Use Case View, Logical View and Component View, with addition of Deployment View... you cannot add class to Component View, etc. Thus, it's quite possible that the Together project tree won't be replicated exactly in Rose.
The workaround is to repeat the package structure of the Together project in each "View" of the Rose project (except Deployment, which is simply a diagram). Elements and diagrams of the Together project are added to proper package in the corresponding View: Use Cases to Use Case View, classes to Logical View etc. There are some less obvious cases... where are Sequence diagrams created, for example? In Logical View, as it turns out, but you should be able to discover these fairly easily.
Note links are not exported.
The order of messages on Sequence diagram is not
kept after export
Dependencies between components are not shown on diagrams
Shortcuts to interfaces are not created on
component diagrams
Associations/aggregations are not shown on
Deployment diagrams
If a state diagram is not linked to any class or use case, an empty class is created and the diagram is attached to it.
*(URL is not controlled by TogetherSoft and may have changed since the date of this publication)