Requirements-to-UML transformations

This content applies to version 7.5.1 or later. The Requirements-to-UML transformation transforms IBM® Rational® Requirements Composer artifacts into UML model elements.

Valid transformation sources and targets

A valid transformation source is a selection of Rational Requirements Composer elements such as use cases, actors, process elements, or use case diagrams to identify the elements to be transformed from a previously downloaded Rational Requirements Composer project that is archived or expanded.

A valid transformation target is a project or folder in the workspace. If you specify a project or folder in the workspace as the transformation target, the transformation creates a new UML model in the container that you specify.

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.

Comparing and merging transformation output with target UML models

The Requirements-to-UML transformation uses the comparing and merging functions to determine the differences between the target model and the temporary model that the transformation generates. The Fuse (structural Compare) session is opened when reconciliation is needed, for example when the transformation detects that a pre-existing UML model with the same name is in the target project or folder. When you run the Requirements-to-UML transformation, the merge editor displays the differences between the two models. In the Merge editor window, you can select the changes that should be applied to the target model.

Filters in the merge editor

You can use the filters in the merge editor to show or hide the different types of deltas (changes) that occur when you run the Requirements-to-UML transformation. To simplify the view in the merge editor, click Filters on the toolbar, and select the filters to apply.


Feedback