Requirements Traceability

 

GADC requirements management practice that extends from requirements definition through to implementation. We ensure that each step of the product development process is correct, conforms to the needs of prior and next steps, and conforms to the defined requirements. Our requirements tracing technique helps to ensure that the project delivers what stakeholders expect. Applied correctly requirements tracing is a practice that can greatly increase the quality and reliability of a projects final product while minimizing costly rework resulting from requirements errors.

We define the ability to describe and follow the life of a requirement, in both a forward and backward direction, ideally through each step of the entire products life cycle. This is done by documenting and tracking traceability relationships between requirements. A traceability relationship is a dependency relationship between project and/or product elements. Similar to the way a dynamic project schedule may react to a change in one task, a change to a requirement element may also have a rippling effect on other elements. A well-documented traceability relationship clearly defines requirement dependencies and allows for analysis of how changes in requirements affect other requirements and the project as a whole.