These
workflows describe typical scenarios for using the integration of
Rational® RequisitePro® and
the
Rational Software Delivery Platform products.
Associating requirements with UML
model elements
- The analyst or product manager uses Rational RequisitePro to create or modify requirements for a software product.
- The system architect starts a Rational Software Delivery Platform product
that supports UML modeling and opens the Rational RequisitePro project in the Requirement Explorer view. The system
architect studies the requirements and develops a new UML model that reflects
those requirements.
- The architect associates Rational RequisitePro requirements
with UML model elements to indicate which requirements are satisfied by which
model elements.
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 feature
requirement.
- The system architect opens a Traceability Matrix or Traceability Tree
view (or creates one in Rational RequisitePro)
to ensure coverage for all requirements. Individual traceability relationships
can be viewed in the Requirement Trace and Requirement
Query Results views. Model elements and requirements without associations
or traceability might represent an incomplete design.
- After the design is complete, programmers use the UML model to direct
their implementation of the application code.
- As the project progresses, the product manager or development manager
continues to monitor traceability to watch for changes to associated requirements.
These changes might cause traceability between requirements to be marked as
"suspect," which indicates that the requirements should be reviewed.
Associating requirements and development
domain elements
- The analyst or product manager uses Rational RequisitePro to create or modify requirements for a software product.
- The system architect starts a Rational Software Delivery Platform product
and opens the Rational RequisitePro project
in the Requirement Explorer view.
- The system architect creates development domain elements, such as classes
or J2EE Beans, and associates them with related requirements.
- The system architect opens a Traceability Matrix or Traceability Tree
view (or creates one in Rational RequisitePro)
to ensure coverage for all requirements. Individual traceability relationships
can be viewed in the Requirement Trace and Requirement
Query Results views. Domain elements and requirements without associations
or traceability might represent an incomplete design.
- After the design is complete, programmers use the associated requirements
to provide details for their implementation of the application code.
- As the project progresses, the product manager or development manager
continues to monitor traceability to watch for changes to associated requirements.
These changes might cause traceability between requirements to be marked as
"suspect," which indicates that the requirements should be reviewed.