Verification and Validation
Verification and validation are used interchangeably but have different definitions.
Verification:
“Doing in the right way”. Typically involves review and meetings to evaluate documents, plan, code, requirements and specifications.
Occurs with each stage. This is done by walk through and auditing.
To identify defects in the product early in the life cycle
Verifications are classified based on the Time and purpose
Validation:
Doing the right thing”. It typically involves actual testing and takes place after verification. It occurs across stages .It is done by inspection, simulation and prototyping.
Uses the traceability matrix to review requirements.
It confirms that deliverables of the product in later stages meet requirement specified in earlier.
Types of reviews:
In – process review
Decision –point / phase –end
Post implementation reviews.
1. In Process review:
- This review happens during the specific period of development cycle like design period
- It is used to find defects in the work product and work process
- Catches defects early where they are less costly to correct
2. Decision –point / phase –end:
- It is also referred to as milestone review
- Review of the product and process near the completion of each phase of development
- Decision for proceeding with development are based on cost, schedule, risk, progress, reading for next phase
- Contains requirements, critical design, test readiness and phase end review.
3. Post implementation reviews:
- Review / evaluation of the product that includes planned Vs actual development results and compliance with requirement
- Used for process improvement of software development
- Can be held up to 3 to 6 months after implementation.
