U.S. Department of Transportation
Federal Highway Administration
1200 New Jersey Avenue, SE
Washington, DC 20590
202-366-4000
California Division
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
|
 |
|
 |
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 |
| Is there a definition of all the major system functions? | ||||
| With each function of the system, is there a set of requirements that describes: what the function does, who is assigned to do it, and under what conditions [e.g. environmental, reliability, and availability.] | ||||
| Are all terms, definitions, and acronyms defined? | ||||
| Are all supporting documents such as standards, concept of operations, and others referenced? | ||||
| Does each requirement have a link [traceability] to a higher level requirement of a user-specified need? | ||||
| Is each requirement concise, verifiable, clear, feasible, necessary, unambiguous, and technology independent? | ||||
| Are all technology dependent requirements identified as constraints? | ||||
| Does each requirement have a method of verification defined? | ||||
| 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? | ||||
 |
 |
 |
