VALIDATION & VERIFICATION PLAN (Template)

Contents

Summery of Updates to this Version of the Document
Purpose
Contract Summary
Verification and Validation process
Importance of the Verification and Validation Process
Mechanisms, Methods and Tools
Industry Verification and Validation Best Practices
References consulted
Appendixes
A Verification Process (Flowchart)

Summery of Updates to this Version of the Document

• V1 This is the first version of the document. It includes a brief outline of each topic.

Contract Summary

Verification and Validation process

  1. Address verification early in the requirement process.
  2. Review every requirement to identify non-verifiable requirements.
  3. ensure that as every verification of a requirement is planned, tag it with method, level and phase.
  4. Carry out formal technical reviews on each iteration of design
  5. Identify duplication and inefficiencies in verification plan.
  6. Set up a strategic approach to testing ensuring validation of produced components (including dynamic testing and static testing techniques, please refer to the testing plan).
    Importance of the Verification and Validation Process

The importance of verification and validation is set of activities that ensure that software correctly implements a specific function that is the right function for the customer. It is important the purposed system will meets its specifications and has the correct outputs. One of the common pitfalls in the development process is to think: ‘how to I design’ rather than ‘how will I verify’.

Mechanisms, Methods and Tools

The following methods can be used for verification:
• Testing (Dynamic Testing: Functional, Structural and Random. Static testing)
• Analysis (Consistency techniques and Measurement techniques)
• Demonstration
• Inspection
• Tractability of requirements supports the verification
• Formal Technical Reviews
• Quality and configuration audits
• Document reviews
• Constructive Testing scheme.
As with other project plans it is best to use familiar proven verification/ validation techniques

Industry Requirements Best Practices

• UML compliance
• BSC requirements for certain projects

References

• Effective Requirements Practices –Ralph R. Young (2001)
• Project Managers Toolkit – David M Shailer (2001)
• M301 Course Material (2001)
• Verification/ Validation/ Certification – Eushiun Tran – Carnegie Mellon University (1999)

Appendices

A REQUIREMENT PROCESS (FLOWCHARTS AND PROCESS DESCRIPTIONS)

B PRC RULES OF CONDUCT


• Respect each person.
• Share responsibility.
• Criticize ideas, not people
• Keep an open mind
• Question and participate.
• Arrive on time
• Keep interruptions to a minimum
• Manage by fact.