California Division | Federal Highway Administration

Design Specifications Checklist

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

Deliverable Checklist
Are all the bases covered?	Yes	No	Not Applicable	Comments
Does the High Level Design Document include definition of requirements unique to the chosen architecture [interfaces between sub-systems, for instance]?
Is the definition of each requirement from the Requirements Document complete enough for implementation? Or, does it need to be expanded in the High Level Design Document?
Are system requirements traced to the sub-systems in the High Level Design Document?
Are commercial off-the-shelf products identified in the High Level or Detailed Design Document?
Is the design approach for common software methods defined, as appropriate, in both the High Level and Detailed Design Documents?
Is the architecture, both hardware and software, of the sub-systems [components and interconnections] defined in the high level design specification?
Are any necessary database schema and structures defined in the High Level and Detailed Design Documents?
Are the hardware components defined in enough detail in the design documents to support procurement or fabrication?
Has the trace from requirements to hardware and software components been checked and verified?
Is the Detailed Design Document linked to the source code components, that is, do they use the same object names, file names, attribute names, and method names?