Requirement traceability

Requirement traceability is a relationship between two requirements that implies the source, derivation, or dependencies between the artifacts.

You can use traceability relationships to determine the extent to which your project requirements are satisfied. As elements or their associated requirements change, you can use traceability relationships to monitor the impact of these changes.

Within Rational® RequisitePro®, you can establish traceability between a requirement and one or more other requirements. While defining these traceability relationships in the requirement properties, you can imply source, derivation, or dependency with directional from and to indicators. For example, you can establish traceability from feature requirements to use-case requirements. If the feature requirement changes during the project to meet new technical or business needs, the traceability relationship is flagged as "suspect" , which indicates a need to evaluate the use case for impact.

Requirement traceability with associated domain elements

When you create an indirect association, a proxy requirement is created to represent the domain element in the Eclipse Element Proxies package in Rational RequisitePro. Traceability is created from the proxy to the targeted requirement. You add traceability between one or more requirements and the proxy requirements.

Use the Requirement Editor and Requirement Trace views to examine and modify traceability relationships between requirements. Use the Requirement Query Results view to examine the results of queries that are created in Rational RequisitePro views; these include Traceability Matrix and Traceability Tree views.

Related tasks
Viewing requirements in query results
Viewing and modifying requirement traceability

Feedback