Requirements traceability
Beginner
Keeping a link from every promise in the spec to the test that proves the chip keeps it.
Novice
Links from each requirement up to the customer need it serves and down to the tests that prove it. The links expose requirements that nothing tests, and tests that check something nobody asked for.
Expert
Kept in both directions and maintained by tools: requirement IDs appear in test plans, coverage reports and the final signoff checklist, so a script can report the status of every requirement. It is mandatory in regulated work such as aircraft (DO-254) and automotive (ISO 26262) electronics, where reviewers check that verification covers each requirement completely.
Explained in Specification (Design Flow).
See also: Requirement (“shall” statement), Verification plan (testplan).