These workflows describe typical scenarios for using this integration
of the Rational® RequisitePro® and Rational Software Architect tools.
Associating requirements and model elements in new products
- The analyst or product manager uses RequisitePro to
define requirements for a new software product.
- The system architect starts Software Architect 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.
- 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 traceabilty may represent an incomplete design.
- After the architecture is complete, programmers use the UML model to direct
their implementation of the application code.
Associating requirements and model elements in existing products
- The analyst or product manager uses RequisitePro to
create or modify requirements for an existing software product.
- The system architect starts Software Architect and opens the RequisitePro project
in the Requirement Explorer. The system architect creates
new model elements and traceability to satisfy new requirements.
- 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.
- After the architectural changes are complete, programmers use UML model
to direct their modification of the application code.