1. Has a complete product been specified (TW)?

2. Are all of the specified requirements within the scope of the current statement of work (JSE)?

3. Are all requirements traceable to system concept statements (JSE)?

4. Are goals/objectives for the software consistent with goals for the system (SE)?

5. Does the document contain enough information to stand alone (TW)?

6. Has each major function been adequately described (SSE)?

7. Have all major system interfaces been described (SSE)?

8. Are all of the requirements specified clear and unambiguous (SE)?

9. Are all diagrams clear and able to stand alone without supplementary text (TW)?

10. Does the specification address (SE, SSE)?

   a. Hardware and software constraints?

   b. System performance?

   c. Storage and memory constraints?

(Yes)(No)

   d. I/O channel usage constraints?

   e. System states or modes of operation supported?

   f. System failure/recovery?

   f. System failure/recovery?

   f. System failure/recovery?

   g. System expansion?

   h. Business area data model?

   i. Appropriate Enterprise Model, if needed?

   i. Appropriate Enterprise Model, if needed?

   j. Appropriate Process Model (is use of IDEF required?)

   k. Initial Data Dictionary, using approved standard data elements, if required?

11. Does the specification clearly describe the problem the system is to solve (SE)?

12. Do requirements answer the question "what" and not "how" (SE)?

13. Has the risk associated with development been identified (SSE)?

14. Have alternative software requirements been considered (SE)?

15. Do specified requirements affect project plans/estimates (SSE)?

16. Have system acceptance criteria been defined (TE)?

16. Have system acceptance criteria been defined (TE)?

17. Have all assumptions and dependencies been considered(SE)?

1. Does the design trace to the requirements specification (JSE)?

2. Have any unnecessary requirements been added (SE)?

3. Does the design satisfy all software requirements (SSE)?

4. Is the design fully implementable (SE)?

5. Is the design modular (SSE)?

6. Has reuse of appropriate existing materials been considered (SSE)?

7. Has system maintainability been considered (SE)?

8. Has performance been estimated and found acceptable (SE)?

9. Has memory utilization been estimated and found acceptable (SE)?

10. Have all external interfaces been defined (SE)?

11. Are the system components functionally independent (SSE)?

12. Is the overall design factored (i.e., top level modules decide program flow and bottom-level modules perform I/O and computational work) (SE)?

13. Is the data structure consistent with the information domain (SSE)?

14. Have all new techniques been successfully prototyped (SSE)?

15. Has system usability been considered (SE)?

16. If incremental development is planned, is the "build" plan reasonable, workable (SE)?

17. Do data structures support the logical data architecture access and distribution requirements?

18. Do system components support the logical process architecture user access needs?

19. Does the implementation architecture support the organizational, geographic, processing, data access, communication and support requirements of the proposed design?

1. Have all categories of potentially reusable materials been identified?

2. Have criteria been established for the selection of candidate reusable materials?

3. Have all reasonable sources of reusable components been explored?

4. Do candidate software materials adhere to required standards?

5. Has the degree of support available for candidate materials been determined?

6. Have licensing or other legal requirements been identified?

7. Has the maturity of all candidate reusable non-COTS software components been verified?

8. Is each candidate software component well documented?

9. Are candidate reusable software components structured to be maintainable?

10. Is the implementation of the candidate software components efficient?

11. Do the candidate reusable software components perform their advertised functions correctly and completely?

12. Has the amount of adaptation required of each candidate material been determined?

1. Does the detailed design trace to the interface and high-level designs (JSE)?

2. Are the interfaces consistent with the interface design (SE)?

3. Does the design satisfy all allocated software requirements (SE)?

4. Is the design fully implementable (SSE)?

5. Is the design amenable to the implementation language (SSE)?

6. Has information-hiding been fully utilized (SSE)?

7. Are structured programming constructs used throughout (SE)?

8. Is the logical complexity reasonable (JSE)?

9. Have language/operating-system dependencies been minimized (SE)?

10. Is compound logic minimized JSE)?

11. Has inverse logic been eliminated, or at least minimized (JSE)?

12. Are algorithms logically correct and produce the desired effect (SE)?

13. Have all error and boundary conditions been specified (SE)?

14. Is local data structure properly defined (SE)?

15. Has maintainability been considered (SE)?

16. Has performance been estimated and found acceptable (SSE)?

17. Is the user interface usable, consistent across the system (SE)?

18. In general, will the system be usable by the target user audience (SE)?

19. Is the "build" plan doable (SSE)?

1. Does the code adhere to established coding standards and guidelines (JSE, SE, SSE)?

2. Is the code adequately and accurately commented (JSE)?

3. Is the translation of the design into executable code complete and correct (SE)?

4. Are all elements of the code traceable to the allocated requirements (JSE)?

5. Are all error and boundary conditions properly handled (SE)?

6. Is the associated unit test plan complete, correct and adequate (JSE, SE)?

1. Does the Test Plan identify the test organization and appropriate staffing (skills and skill-levels) (TW)?

2. Does the Test Plan define a workable overall formal test approach (STE)?

3. Does the test plan identify a standard naming convention for test conditions/variations and test procedures (JTE)?

4. Does the test approach/schedule promote evaluation of software soon after its availability (STE)?

5. Does the test plan address all relevant types of tests; e.g functional, regression, stress, performance, acceptance, etc. (TE, STE)?

6. Does the Test Plan identify all relevant environmental factors and variants; e.g., hardware constraints, etc. (TE, STE)?

7. Does the plan correctly interpret requirements (TE, STE)?

8. Do all test conditions/variations trace back to the software requirements (JTE, STE)?

9. Does the Test Plan identify a reasonable set of test conditions/variations for each requirement (STE, TE)?

10. Do the test conditions/variations include tests of messages generated by the software (JTE)?

11. Do the test conditions/variations identified provide adequate test coverage; error, as well as legitimate conditions (TE, STE)?

12. Does the Test Plan identify all needed support software (i.e.,stubs, drivers, simulators, emulators, etc.), test equipment and responsibility for acquisition/development (TE)?

13. Does the Test Plan describe hardware constraints, requirements (TE)?

14. Does the Test Plan identify test data requirements and needed time frames (TE, STE)?

15. Does the Test Plan identify all hard test problems and approaches to mitigation (TE,STE)?

16. Does the Test Plan identify how tests will be verified (QA, TE)?

17. Does the allocation of conditions/variations to test procedures minimize redundancy (JTE)?

18. Is the allocation of test conditions/variations to test procedures reasonable, logical (TE)?

19. Are all test conditions/variations allocated to at least one test procedure (ITE)?

20. Does the Test Plan address configuration control of all test materials (JTE, QA)?

1. Does each test procedure design trace to the test conditions/variations allocated in the Test Plan (JTE)?

2. Does the test procedure design satisfy all allocated test conditions/variations (TE, STE)?

3. Is each test procedure design fully implementable (TE, STE)?

4. Is each test procedure design logically executable (TE, STE)?

5. Does the test procedure design minimize duplication of steps/tests (JTE)?

6. Is the test procedure design efficient (TE, STE)?

7. Does the test procedure design minimize dependence on data/conditions generated in previous test steps (TE, STE)?

8. Does each test procedure design minimize execution time (TE, STE)?

9. Does the test procedure design minimize the effort required to restore the test environment if restart is necessary (TE)?

10. Do the tests and method of execution truly test the associated software requirements and test conditions/variations (TE, STE)?

11. Is there enough detail to fully implement the test procedure design (TE)?

12. Has long term procedure maintenance been considered (TE)?

13. Does each series of steps culminate in a pass/fail result (JTE, TE)?

14. Are verification steps well documented (JTE, TE)?

1. Does each test procedure trace to the test conditions/variations allocated in the Test Plan(JTE)?

2. Does the test procedure correctly implement all allocated test conditions/variations (TE, STE)?

3. Is the test procedure fully executable (TE, STE)?

4. Are test steps fully documented (QTE)?

5. Are instructions for execution clear and concise (JTE)?

6. Does the test procedure minimize duplication of steps/tests (JTE, TE)?

7. Does the test procedure minimize dependence on data/conditions generated in previous test steps (TE, STE)?

8. Does the test procedure minimize execution time (TE, STE)?

9. Does the implementation of test procedure minimize the effort required to restore the test environment if restart is necessary (TE)?

10. Does each logical series of steps in the test procedure culminate in an obvious pass/fail result (JTE)?

11. Are expected results clearly documented and correct (TE, STE)?

1. Does the Information Plan define a workable approach to document development (TW)?

2. Have all resources required to produce the document(s) been identified (SSE)?

3. Has the target audience been identified ((SE)?

4. Has the correct target audience been identified (SSE)?

5. Has the educational level of the target audience been identified (SE)?

6. Does the Information Plan accurately and completely identify all functions the end users will need to perform (SE)?

7. Does the Information Plan identify all of the scenarios in which end users will typically find themselves (SE, SSE)?

8. Is the planned organization of the document(s) highly usable (SSE)?

9. Has a provision been made for independent (end-user, etc.) draft document reviews for usability (SSE)?

10. Are all typically requested topics included in the planned index (SE, SSE)?

11. Have all of the needed graphics been identified (TW, SE)?

12. Will the document(s) include a sufficient number of examples (TW)?

13. Has a source of each example been identified (TW, SE)?

14. Does the Information Plan describe how examples will be verified/validated (TE)?

15. Does the Information Plan correctly interpret system requirements (SE, SSE)?

16. Does the Information Plan address the configuration control of publications materials (SE)?

17. Does the Information Plan call for the associated document(s) to be completed in the right time frame (SSE)?

18. Has technical ownership been identified (e.g., appropriate author/developer) (SSE)?

1. Does each outline trace to the requirements allocated in the associated Information Plan (TW)?

2. Have all of the requirements identified in the associated Information Plan been addressed in the outline (TW, SE)?

3. Is the outline sufficiently detailed to be implementable (SE, SSE)?

4. Are topics covered in a logical/reasonable sequence (SE, TW)?

5. Are specific procedures required identified (SE)?

6. Are the major steps involved in each procedure documented (SE)?

7. Is each documented procedure correct (SE, SSE)?

8. Are the expected results of each procedure clearly defined and correct (SE, SSE)?

9. Have any additionally required graphics been identified (SE)?

10. Has responsibility for producing/obtaining the required graphics and/or examples been assigned (SSE)?

11. Has responsibility for producing/obtaining the required examples been assigned (SSE)?

12. Has responsibility for verifying required examples been assigned (TE)?

1. Does the draft document follow the approved outline (TW)?

2. Are all software requirements (functionality) reflected in the document (SE)?

3. Has a writing assessment (i.e., FOG index, created by Robert Gunning, serves as a practical yardstick for determining the degree of difficulty in any type of writing) been performed to ensure that the writing level is suitable for the target audience (TW)?

4. Have all of the embedded examples and graphics been verified as correct (TE, SE)?

5. Have all of the graphics and examples been appropriately collocated with the associated text (TW)?

6. Are all of the procedures and examples easy to understand and follow (TW, SE)?

7. Are expected results of procedures clearly documented (TW)?

8. Does the organization of the document make it easy to locate specific information (TW, SE)?

9. Does the table of contents match the document contents (TW)?

10. Has a usability review been conducted (SE)?