Transforming requirements artifacts into UML models

This content applies to version 7.5.1 or later. Use the Requirements-to-UML transformation to create a Unified Modeling Language (UML) model from IBM® Rational® Requirements Composer artifacts.

About this task

The following steps describe the process at a high level. The links to topics that follow the steps provide details for transforming Rational Requirements Composer into UML models.

Note: To import archives from Rational Requirements Composer version 2.0 or later, you must use a Rational modeling product that is version 7.5.5 Interim Fix 002 or later.

Procedure

  1. Download the artifacts or archived file from Rational Requirements Composer to your local file system.
  2. Open one of the Rational modeling products, and select an existing modeling project or create a new one.
  3. From the Modeling menu, click Transformation > Create new configuration.
  4. In the wizard, select Requirements Composer Integration > Requirements Composer Artifact Transform. Follow the steps in the wizard to create a transformation configuration file.
  5. Use the configuration user interface to designate the transformation source by selecting a folder that contains the downloaded artifacts or archive file in your local file system. The transformable artifacts from the source folder or archive are displayed on the source side of the configuration interface.
  6. Select a workspace project to serve as a target for the transformed artifacts. If appropriate projects are not displayed, you can create a target project in the transformation window.
  7. Use the Additional properties page to set or modify other properties that are related to transformation.
  8. Run the transformation to generate the UML artifacts.
  9. If the target project already contains artifacts, the Structural Compare Merge (Fuse) window opens for the artifacts before the existing files are overwritten with new content. When the Structural Compare Merge session is completed, your defined changes are applied to the existing artifacts, and the target artifact is overwritten. If you cancel the Structural Compare Merge session, the existing artifact is not overwritten.

Feedback