*it is the process of evaluating the software in order to
determine that the software in the given phase satisfy the
condition which was imposed at the beging of the phase.
* Non execution base.
*coulld be conducted either during any phase or end of the
* may be carried out through review(Walk through ,
* it is the process of evaluating the software to determine
the degree through which software meets the user
*Generally being conducted after varification.
Verification is QA activity which ensures that the software
product is designed to deliver all the functionality
whatever mentioned in the requirement specification
document. Reviews, walkthroughs and inspections are its
techniques. It is a preventive phase.
Validation ensures that whatever mentioned in the
requirement specification document should be the intended
behavior of the software. Validation is actual testing. It
is a corrective phase and is QC activity.
Verification: Are you building it right? Ensure that the
software system meets all the functionality.Verification
takes place first and includes the checking for
documentation, code etc.Have static activities as it
includes the reviews, walkthroughs, and inspections to
verify that software is correct or not.Done by developers.
Validation: Are you building the right thing?Ensure that
functionalities meet the intended behavior.Validation occurs
after verification and mainly involves the checking of the
overall product.Have dynamic activities as it includes
executing the software against the requirements.Done by Testers.
Verification: typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. This can be done with checklists, issues lists, walkthroughs, and inspection meetings.
Validation: typically involves actual testing and takes place after verifications are completed. The term 'IV & V' refers to Independent Verification and Validation