CCBA® and CBAP® Certifications Study Guide

Why trace requirements?

There are a number of reasons why you should want to trace a requirement:

• It will enable quick identification of gaps within the supplied solution, as well as the supplied requirements.
• It will aid in the understanding of the size of the change.
• By tracing a requirement through development, testing, and implementation, you keep track of the requirement's status throughout the life cycle of the project.
• Traceability also supports requirements allocation and release planning.

Requirements traceability provides a clear view of requirements in a way that allows the team to plan and allocate which requirements to include into which releases. In this way, when looking at requirements within the same subject matter area, ...