11 Steps in VV&A:


Introduction

What and Why of VV&A


1. Examine Proc Doc

2. Examine Sys Doc

3. Interview Developers

4. Interview Users

5. Examine Code I

6. Examine Code II

7. Determine Truth

8. Generate Test Cases

9. Run Test Cases

10. Review Test Output

11. Assessment


SDP Template

SQPP Template

SCMP Template

WBS Template




Basic Work Breakdown Structure (WBS) Template


  1. Requirements
  2. System
  3. Software

  4. Design
  5. System
  6. Software
  7. Algorithm Development

  8. Code

  9. Unit Test
  10. Creation of unit tests
  11. Creation of acceptability (pass/fail) criteria
  12. Documentation of expected results
  13. Documentation of actual results

  14. Integration Test
  15. Creation of integration tests
  16. Creation of acceptability criteria
  17. Documentation of expected results
  18. Documentation of actual results

  19. Quality Assurance

  20. Reviews
  21. Requirements Reviews
  22. Design Reviews
  23. Code Walkthroughs
  24. Peer Reviews
  25. Software Quality Assurance (SQA) Reviews

  26. Training
  27. Non-software training (Infrared Engineering, Calculus, etc.)
  28. Software training (C++, FORTRAN, ADA, etc.)

  29. Customer Support
  30. Reports/Documentation
  31. Presentations/Briefings
  32. Demonstrations/Customer Training

  33. Configuration Management
  34. Requirements
  35. Design Documents
  36. Versions of Code Released To User
  37. User Documentation

  38. Travel

Documentation falls under one of the major categories above -- documenting unit or integration tests falls under testing; briefings for peer reviews fall under reviews; user manuals fall under customer support. If desired, you could instead have a separate sub-category for documentation within each of these categories (testing, reviews, customer support).

For a small or medium-size project, the eleven major categories will probably suffice. For a very large project, you may wish to break down the WBS into some of the sub-categories shown. The reviews category could fall under requirements, design, or code. But for a small project it may be better to make it a separate category, rather than breaking the others into sub-categories.