Step 4 -- Interview Users


  • Who are the users?

  • How do you usually solve these types of problems?

  • What are typical inputs and outputs?

  • What kinds of problems does this system, or type of system, usually have?

  • Do you have to be careful in the way any of the inputs are defined?

  • Do you have to be careful how you use the outputs?

  • Are there cases which often lead to unreasonable outputs?

  • Are there cases which often lead to failure? Near failure? Is failure graceful?

  • How much user knowledge/training is required to solve this problem?

  • How much user knowledge/training is required to use this system (or current systems)?

  • What do you need that current systems don't provide?

  • During testing, what do you compare to (what is truth)?

  • Do you use error bounds to increase confidence in the outputs?

  • What is the fidelity of this system perceived to be? What do you want (need) it to be?


    • 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