How to migrate Rose UML model subunits to Rational Software Architect. Introduction. Part one of this series briefly discussed subunits and fragments. This allows you to break up a large, complex model into smaller units that individual developers can work independently.
Each of the individual subunits or fragments can exist separately under version control and helps enable a project team to develop a model in parallel. The Software Architect environment also supports working with multiple models at the same time, unlike Rational Rose that allows working with only one model at a time. Using the Rational Software Architect environment you can break up a large model into multiple, smaller sub models similar to the fragments. The advantage of using sub models is that they can exist independently of the main model, unlike fragments which can exist only inside the main model. These independent sub models can also be shared by multiple models.
The IBM. The tool also supports sharing the subunits with existing models in the Software Architect solution. This article discusses the various options available for converting subunits during import of a Rose model to your Software Architect environment. Prerequisites. As a prerequisite, you need the following rational software installed, and you need to be familiar with using both products. The tools needed include: Rational Software Architect Standard Edition Version 7.
Rational Rose solution, with models that contain Petal Version 4. Software Architect environment.
To open IBM Rational Software Architect v8.0. WebSphere Software 8.0.1->IBM Rational Software Architect for WebSphere Software. This document provides an overview of new features and enhancments in IBM Rational Software Architect. You can now export BPMN project from the.
If you have models that use Petal Version 4. Petal Version 4. 7 first within your Rational Rose tool. These models must be free of errors before you import them. You may use the Check Model option in Rational Rose tool to verify that they are error- free. Before you start planning your Rose model subunits migration, it is important that you read the IBM developer Works . How to migrate UML models to Rational Software Architect.
As root packages. You may also choose to import some subunits as models, some as root packages, and yet other subunits as fragments. You can remap subunits to existing models and packages. You can also apply a mixed approach by remapping some subunits while converting others to fragment, models or root packages. Back to top. Import of subunits as fragments.
When you import subunits as fragment, each of the subunits (. IBM. For example, Subunit. X. cat in Rational Rose has been converted to Subunit.
- Rational software Rational Software Architect Standard.
- UML Model Reporting with Rational Software Architect and BIRT. UML Model Reporting with Rational Software Architect and BIRT. Export reports as PDF, HTML,MS.
- The Design Manager 3.0 extension for Rational Software Architect includes. Reporting on Rational Software Architect.
- Rational Software Architect for WebSphere Software: A platform optimized for SOA, JEE and Websphere applications. Rational Software Architect Design Manager .
- Rational Modeling 101 Gavin Arthurs. Rational Rhapsody Rational Software Architect.
- Import Visio Rational System Architect.pdf. Outbreak Report Import/Export.
- ProVision is the industry leading enterprise modeling software. Rational Software Architect. ProVision’s translator function enables you to export ProVision.
- Enterprise Architect: Export UML Diagrams in. The third way was to export them into a pdf.
X. efx in the Software Architect tool, as shown in Figure 1 below. Figure 1. Subunits in Rational Rose converted to fragments in Rational Software Architect. Back to top. Import of subunits as models. When you import subunits as models, each of the subunits (. Rational Rose solution will be imported as a separate model (.
Software Architect tool and a shortcut will be created in the model containing the subunit to the newly created model(from subunit) as shown in Figure 2 below. All the references to the elements of the subunits are automatically updated to the elements of the model created from the subunit.
For example, Subunit. X. cat of Model. A in the Rational Rose solution has been converted to Subunit. X. emx in your Rational Software Architect environment after import.
There is new shortcut created for subunit Subunit. X in Model. A, which points to the newly created model Subunit. X (Subunit. X. emx) inside the project named Shared.
Subunits in the Rational Rose tool converted to models in the Rational Software Architect solution. Back to top. Import of subunits as packages.
When you import subunits as packages, each of the subunits (. Rational Rose will be imported as a separate model (. Software Architect solution. The model containing subunit will add element import to the newly created package (from subunit) as shown in Figure 3 below.
All the references to the elements of the subunits are automatically updated to the elements of the package created from the subunit. For example, Subunit. X. cat of Model. A in the Rational Rose tool has been converted to Subunit. X. emx(with type set as package) in your Software Architect solution after import.
There is new element import created for subunit Subunit. X in Model. A, which points to the newly created package Subunit. X (Subunit. X. emx) inside the project named Shared.
Subunits in Rational Rose tool converted to packages in the Rational Software Architect solution. Back to top. Steps to import subunits as fragments, models or root packages.
Follow the steps in . How to migrate UML models to Rational Software Architect. This section will show a step- by- step usage of the Rational Rose Model Subunit Conversion wizard page for subunit conversion.
Note: The . Enable subunit conversion. In the Rational Rose Model Import wizard, on the Rational Rose Model Subunit Conversion page, select the check box labeled Convert subunits to fragments, models or packages as shown in Figure 4 below. Figure 4. Rational Rose Model Subunit Conversion wizard.
By default, all the subunits are converted to fragments. Therefore, when the user enables the subunit conversion, the Subunit list table gets enabled and all the subunits in the Subunits list table have Convert to/Share column set to fragment.
Step 2. Specify the conversion choice for the subunits. After completing Step 1, by default all the subunits in the subunits list table will be converted to fragments.
You have to modify the subunit list in order to import subunits as independent models; or root packages. There are two ways to accomplish this: Option 1: In the Subunit list table, select a subunit name; then, click on the Convert to/Share column, you will see a drop- down list with three choices Fragment, Model or Package as shown in Figure 5 below. Select one of the desired choices for the subunit conversion. Figure 5. Drop- down list in Subunit list table. Option 2: Right click on the Subunit list table, this will open up a Convert subunits popup menu as shown in Figure 6 below. Select All to menu option, you will see a sub menu with three choices Fragment, Model or Package as seen in Figure 6.
Select one of the desired choices; Convert to/Share column for all the subunits in the Subunit list table will be updated with the selected type. The popup menu is very useful when you have large number of subunits and all of them have to be converted to same type during import. Figure 6. Popup menu in Subunit list table. Proceed to Step 3 if you are importing one or more subunits as fragments. Perform Step 4 if you have selected to import one or more subunits as model or root package. Step 3. Select the naming conventions for fragments. This step is applicable only when you import one or more subunits as fragment.
Select the name of the fragment by making appropriate choice in Fragment creation options panel as shown in Figure 7 below. To create fragments with the subunit file name, click Use subunit file names; to use the package name of the subunit, click Use subunit package names. For example consider a subunit Subunit.
A. cat which has package name defined as Package. A in Rational Rose model. If you select Use subunit file names option then the fragment name will be set to Subunit.
A. Fragment, model or package creation options. Step 4. Specify project and naming conventions for models/root packages.
These steps are applicable only when you import importing one or more subunits as models or root package. Specify the project You have to specify the project for creation of the model/root package using Model/Package creation options panel as shown in Figure 7 above. To use the existing projects select Existing project option and use the Browse button to select one of the existing project from the workspace. To create new project select the New project option and type the name to be used for new project in the Project name text box. The new project will be created at the location specified in the Location text box; by default the location will be set to the current workspace. To change the location uncheck the Use Default check box, this will enable the browse button to specify the new location. Select the directory structure Specify the directory structure to be used for the models or root packages using Createmodels/packages panel as shown in Figure 7 above.
To keep the hierarchical structure same as that in Rational Rose select With subunit directory structure option; to impose a flat directory structure select In one directory option. For example the Subunit. A. cat is stored at location C: \XYZ in Rational Rose model i. C: \XYZ\Subunit. A. You have imported the subunits into RSA model project ABC located at C: \workspace i.
If With subunit directory structure option is selected then Subunit. A. emx will be created inside project ABC with the directory structure preserved i. C: \workspace\ABC\XYZ\Subunit. A. emx; if In one directory option is selected then Subunit.
A. emx will be created directly inside project ABC i. C: \workspace\ABC\Subunit. A. emx. 3. Select the naming convention Select the name of the model/root package by making appropriate choice using For model/package file names panel as shown in Figure 7 above. To create model/root package with the subunit file name, click Use subunit file names; to use the package name of the subunit, click Use subunit package names.
For example consider a subunit Subunit. A. cat which has package name defined as Package. A in Rational Rose model. If you select Use subunit file names option then the model/root package name will be set to Subunit. A. emx after import but if you choose Use subunit package names then the model/root package name will be set to Package. A. emx after import. After you specify the appropriate options for subunits import, the models, root packages, and fragments are created in RSA and displayed in the Project Explorer view.
Back to top. Mapping subunits. The Rational Rose tool supports sharing of subunits between two or more models to allow the re- use of the model components.