Step 2 -- Examine System Documentation


  • Documents
  • Program Plan
  • Current V&V Plan
  • Technical Requirements Document (TRD)
  • System Requirements Document (SRD)
  • Operational Requirements Documents (ORD)
  • Functional Descriptions
  • User Manuals

  • Inputs and outputs of developer tests (unit and integration)

  • What models and algorithms does the system use?

  • Assumptions/limitations/constraints

  • Examples
  • Typical inputs
  • Typical outputs
  • Are there any inputs that can lead to problems?

  • Is there some kind of bounds checking or input checking?

  • Does the system produce any warning/error messages, or simply run/crash?

  • How much user knowledge/training is required?

  • Are there differences in use for beginners vs. experienced users?

  • During testing, what was output compared to (what is truth)?

  • Does the system use error bounds to increase confidence in the outputs?

  • What is the fidelity of this system perceived to be?

  • What DOD or commercial standards were required? Were they followed?

  • How clear is system documentation?
  • Was it used during development?
  • Was it produced during development, or after?

    • The Eleven Steps In VV&A:

    1.     Examine Process Documentation
    2. Examine System Documentation
    3. Interview Developers
    4. Interview Users

    5. Examine Code 1 (Look For Problems)
    6. Examine Code 2 (Break It)
    7. Determine Truth

    8. Generate Test Cases
    9. Run Test Cases
    10. Review Test Case Output
    11. Assessment


    Software Development Plan (SDP) Template
    Software Configuration Management Plan (SCMP) Template
    Software Quality Program Plan (SQPP) Template
    Work Breakdown Structure (WBS) Template

    Introduction
    What And Why Of VV&A