Step 10 -- Review Test Case Output


  • Compare to truth
  • How close?
  • Pass?
  • Fail?
  • Marginal?
  • If fail or marginal, what is source of differences?

  • Identify causes of freezes/crashes/discrepancies
  • Trace back through code
  • From instrumentation or debug, how did it happen?
  • Identification most useful when VV&A done in parallel with development

  • Identify root cause of problem
  • User input
  • Code problem
  • Algorithm problem
  • Interface
  • Hardware
  • Identification most useful when VV&A done in parallel with development

  • Document and fix cause of problem (generally can only fix when done in parallel with development)

    • 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