A Rational Rose model used for Integrated Use Case Management contains four default packages: "Use Case View", "Logical View", "Deployment View", and "Component View". Spaces in these package names are not tolerated by Java models in Rational XDE. When you upgrade such models to XDE, you must split them into two models, one for Java code design and the other for analysis.
To migrate Rational RequisitePro associations from a Rose Java model to an XDE model, you must first create a separate design model for your Java code, save your Rose model as an XDE model, and migrate the RequisitePro associations when prompted. You cannot have the associated RequisitePro project open with the Exclusive option selected during this procedure.
The model opens in the Model Explorer.
The new converted Java model appears in the Model Explorer beneath the original model. This model contains most of the information in the original model, including obsolete links to use-case documents from the original model, but it does not include RequisitePro associations. We recommend that you delete these links and the view packages referenced above; they do not contain information pertinent to your design model.
Migrating existing Rational RequisitePro project associations from Rational Rose to Rational XDE