Scenario 2: Author and manage requirements in Rational RequisitePro

You can choose to author and manage requirements in a Rational® RequisitePro® project and then import them into a Rational Requirements Composer project for more definition and elaboration.

When you import requirements that are located in Microsoft® Word documents in Rational RequisitePro, the text of the requirements is displayed in Rational Requirements Composer as plain rather than formatted text, and it is read-only. To view the formatted text, follow the link to the requirement in RequisiteWeb. You can edit the requirement attribute values in either tool.

When you import requirements that are not located in Microsoft Word documents in Rational RequisitePro, you can edit the text of the requirements in Rational Requirements Composer. After editing, the text becomes read-only in Rational RequisitePro. It is displayed as plain text in the client for Windows® and formatted text in RequisiteWeb.

Changes are updated in both tools if the synchronization options were enabled when the integration was configured.

Figure 1 provides an example of authoring in Rational RequisitePro and importing requirements into Rational Requirements Composer.

Figure 1. Integration scenario 2
The graphic shows the scenario that is outlined in the following steps.

In this scenario, you follow this sequence:

  1. Create requirements in Rational RequisitePro views.
  2. Add traceability to and from other requirements in Rational RequisitePro, including document-based requirements.
  3. Import requirements into Rational Requirements Composer from RequisiteWeb.
  4. Elaborate the requirements in Rational Requirements Composer by using requirement definition techniques (business process diagrams, user interface sketches, screen flows, storyboards, use-case diagrams, use cases, actors, and documents).
  5. Modify attributes in either Rational RequisitePro or Rational Requirements Composer.

Feedback