Changing an object whether it is a requirement, a test step, or a section of source code, can potentially require changes in other elements of the project. Requirement traceability is supported to allow you to see relationships between requirements and other related development and testing information. Linking related objects together helps to ensure that changes are implemented correctly at all levels.

Traceability is key to assessing requirement coverage and assess the impact of requirement changes. Caliber provides full traceability

When you create a traceability link, implied links are automatically created to other requirements that may be affected. For example, if there are direct links between a software requirement and a GUI requirement, and between the GUI requirement and a coding requirement, there is also an implied link between the software requirement and the coding requirement. Implied links are displayed in the Traceability Matrix as dotted arrows.

When a requirement is changed, links to other objects become suspect. Suspect traces are an indicator that other objects might be affected by the changed requirement and should be reviewed. Suspect traces are indicated in the Traceability Matrix by a red arrow with a red question mark centered on the arrow. Suspect traces can be separated from other traces with the Show Suspect Traces toolbar button in the Traceability Diagram.

You can view the Traceability Matrix to see all traceability links at a glance or you can view the Traceability Diagram to see the traceability links for a specific requirement.

Many traceability views are provided in Caliber: