A traceability matrix is a report from the requirements database
or repository. What information the report contains depends on your need.
Information requirements determine the associated information that you store
with the requirements. Requirements management tools capture associated
information or provide the capability to add it.
The examples show forward and backward tracing between user and
system requirements. User requirement identifiers begin with "U" and system
requirements with "S." Tracing S12 to its source makes it clear this requirement
is erroneous: it must be eliminated, rewritten, or the traceability corrected.
For requirements tracing and resulting reports to work, the
requirements must be of good quality. Requirements of poor quality transfer work
to subsequent phases of the SDLC, increasing cost and schedule and creating
disputes with the customer.
A variety of reports are necessary to manage requirements.
Reporting needs should be determined at the start of the effort and documented
in the requirements management plan.