Integrating Rational modeling products with Rational Requirements Composer artifacts fosters collaborations with the customers or analysts to complement the analysis and offer traceability and documentation of original requirements and artifacts for future software development. You can use the integration of Rational Requirements Composer to locate requirements that were approved as part of an iteration assessment review, bringing the requirements and valid related artifacts into the software analysis and design modeling workspace as UML models. For example, you can import process sketches and process elements and their attributes, such as activities, tasks, events, data, control, and data flows. Furthermore, you can handle content changes that are made in Rational Requirements Composer for content that was brought previously into Rational modeling products.
You can directly use the requirements and artifacts from Rational Requirements Composer to create and extend the analysis and design of your solutions, reviewing process sketches as UML activity diagrams and elements, use case sketches as use cases and elements, relationships and links in Rational Requirements Composer between use cases and process elements, and additional properties on Rational Requirements Composer elements such as attribute groups. Moreover, the integration provides a mechanism to navigate back from elements in Rational modeling products to elements in Rational Requirements Composer.
The content brought in from Rational Requirements Composer can be used to create cross-model relationships between a Rational Requirements Composer model within Rational modeling products and other Rational modeling products analysis and design models. The related or derivative model artifacts or elements help you leverage Rational Requirements Composer process sketches and data elements for rigorous service and systems analysis and design, such as normalization and message optimization.