This information is for planning purposes only. The information herein is subject to change or removal without notice before the products described may become available.
The CE/CLM products were renamed in version 7.0. As the help is updated to reflect the changes, the topics might contain inconsistencies. For details on the name change, see Renaming the IBM Continuous Engineering Portfolio.


Traceability is used to trace a project element to related project elements, especially those related to requirements. Traceability helps determine that a requirement is satisfied from inception through implementation and testing. Create traceability relationships by linking requirements to other requirements and to development and test artifacts.

Traceability supports these activities:
  • Derivation, elaboration, and coverage analysis. Trace between requirements to specify the source, derivation, or dependencies between the requirements; for example, detailed requirements can trace to high-level, more general feature requirements or stakeholder needs. Detailed requirements elaborate high-level requirements. Use traceability to verify that all requirements have the required elaboration to fully describe the objectives.
  • Impact analysis. Assess the impact of change (or proposed change) by using traceability. When requirements change mid-project based on input from stakeholders, traceability helps assess the impact (and cost) of change. When suspect artifact profiles are implemented, changes that occur in linked artifacts can produce suspect indicators on the artifacts. Suspect indicators alert team members of potential impact of change. Traceability can be the basis for negotiating the change. This helps expose dependencies and "hidden" costs of change.
  • Lifecycle coverage analysis. Verify that all the necessary development and test items are in place for implementing and validating requirements.
  • Progress analysis. Track progress and completion status of linked requirements, development items, and test cases.
  • Reporting. Track the above mentioned activities plus other activities, such as sign-off, audit records, etc.

Use link types to specify types of traceability relationships. See Linking artifacts.

Use the Links Explorer to view linked artifact information, to create, delete, and explore linked artifacts, and to remove and modify links.

To link to development and test artifacts, see Linking to artifacts in Jazz-based products. To view traceability to development and test artifacts on your dashboard, add a Requirements Tracing widget to your user dashboard. See adding a widget .

video icon Video channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community forums library

support icon Support

IBM Support Community
Deployment wiki