California Division | Federal Highway Administration

Traceability Checklist

The Microsoft Word version of this checklist is an editable form that can be used to support process reviews.

Process Checklist
Are all the bases covered?	Yes	No	Not Applicable	Comments
Is a requirements management tool needed for the project?
If a requirements tool is needed, has it been procured and configured for the project?
Is the staff trained on the use of the tool?
Is access to the requirements management tool available to all stakeholders and the development team?
Has the extent of traceability been defined?
Are all user needs/requirements traced to system requirements?
Have the concept of operation scenarios been traced to the system requirements and the validation plan?
Have the system requirements been traced to the system verification plan?
Have the system requirements been traced to the high level design?
Has the high level design been traced to the sub-system verification plans?
Has the high level design been traced to the detailed design?
Has the detailed design been traced to the unit verification plan/procedures?
Has the detailed design been traced to implementation artifacts [SW source code, HW documentation etc]?
Have the verification procedures been traced to the verification plans at all levels?
Has all needed supporting project documentation been traced?
Has traceability been maintained during the operations & maintenance, changes & upgrades, and retirement & replacement?