Requirements Traceability Guideline
Summary: Tracing your requirements to tests, to code, or to other requirements, can be a complex and time-consuming effort. If you're contracted to a government project you may not have a choice. But is it worth it in the private sector? This guideline discusses traceability processes, requirements, and how to weigh the costs and benefits.
This template will help you:
What you get:
- Assign responsibility for creating and maintaining labeling guidelines and for definition, initial creation, and upkeep of any traceability matrix (or matrices) to be used.
- Ensure that the project is delivering on the original customer needs and requirements each step of the way.
- Ensure that each requirement is explicitly covered in subsequent project documents such as specifications, implementation pieces, and/or test cases.
- Minimize maintenance costs by ensuring all requirements are tested.
- Instructions for using the guideline.
- An introduction and overview of requirements traceability and the Requirements Management System.
- Requirements attributes for traceability matrices.
- Example traceability matrices in both spreadsheet and word processor format.