Requirement association workflows

These workflows describe typical scenarios for using this integration of the Rational RequisitePro and the Rational modeling products.

Associating requirements and domain elements in new products

  1. The analyst or product manager uses RequisitePro to define requirements for a new software product.
  2. The system architect starts a Rational® modeling product and opens the RequisitePro project in the Requirement Explorer view. The system architect studies the requirements and develops a new UML model that reflects those requirements.
  3. The architect associates RequisitePro requirements with UML model elements to indicate which requirements are satisfied by which model elements.
    Note: This architecture can relate an element to a single requirement, such as in the one-to-one association of a use-case element and a use-case requirement, or by traceability to multiple requirements, such as when a single class satisfies multiple requirements. Conversely, multiple elements can trace to a single requirement, such as when multiple classes satisfy one requirement. Model elements and requirements without associations or traceability may represent an incomplete design.
  4. After the architecture is complete, programmers use the UML model to direct their implementation of the application code.

Associating requirements and domain elements in existing products

  1. The analyst or product manager uses RequisitePro to create or modify requirements for an existing software product.
  2. The system architect starts a Rational modeling product and opens the RequisitePro project in the Requirement Explorer view. The system architect creates new model elements and traceability to satisfy new requirements.
  3. The architect also modifies the UML model to reflect changes to the existing design.
    Note: These modifications create changes in associated requirements and may cause traceability to related requirements to be marked as "suspect." These traceability relationships can be viewed in the Requirement Trace and Requirement Query Results views or in RequisitePro and assist the project team in analyzing the impact of proposed changes to the project.
  4. After the architectural changes are complete, programmers use UML model to direct their modification of the application code.
Related concepts
Associations between requirements and domain elements
Related tasks
Associating existing requirements and domain elements
Creating associated domain elements and requirements

Related information

Tutorial on associating requirements and model elements

Feedback
(C) Copyright IBM Corporation 2004, 2005. All Rights Reserved.