Verification and Validation (V&V)
These two concepts are really related to software testing.
Did you remember “product right”, “right product” thing in your high school. Yes this is it, so we go through these stuffs, how would it be help to your life.
We use these stuffs for user satisfaction and protect our well establish company name from errors and software bug complains from stakeholders .
How ever validation and verification is totally different cases in testing .
What is verification means?
Verification is the process of checking that a software achieves its goal without any bugs.That mean developers , testers have to test do our product has any bugs or errors.It is the process to ensure whether the product that is developed is right or not.The developer has huge role in this case.
Definition of Verification
The process of evaluating work-products (not the actual final product) of a development phase to determine whether they meet the specified requirements for that phase.
Objective of Verification
To ensure that the product is being built according to the requirements and design specifications. In other words, to ensure that work products meet their specified requirements.
What is validation means?
Validation is the process of checking whether the software product is up to the mark or in other words product has high level requirements.We have huge responsible to get all the requirements from our stakeholder in requirement gathering phrase.That requirement gathering stage is so important , if user or company fail to declare all the requirements at the end client has to pay huge amount of money for software changes.Business Analysis should gather right information to building and designing the software/system correctly.In this stage we are analyzing, did we have full-fill all the requirements those client/customer/stockholder asked,
Definition of Validation
The process of evaluating software during or at the end of the development process to determine whether it satisfies specified business requirements.
Objective of Validation
To ensure that the product actually meets the user’s needs and that the specifications were correct in the first place. In other words, to demonstrate that the product fulfills its intended use when placed in its intended environment.
This 5 phase approach of the Validation process is being followed in many Industries like Manufacturing, Medical, Pharmaceuticals etc. Here validation will be done by the end customer before buying the machinery, equipment or the product.
The constituents of the Validation activities for a software is to prove that ‘the software is ready for consumption by the users’, and to mainly verify the successful installation of the software followed by the functionality and operability.
Verification: Are we building the product right?
Validation: Are we building the right product?
Differences between Verification and Validation
Verification is a static practice of verifying documents, design, code and program.
Validation is a dynamic mechanism of validating and testing the actual product.
Verification does not involve executing the code.
Validation always involves executing the code.
Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc
Validation uses methods like black box (functional) testing, gray box testing, and white box (structural) testing etc.
Verification is to check whether the software conforms to specifications.
Validation is to check whether software meets the customer expectations and requirements.
The goal of verification is application and software architecture and specification.
The goal of validation is an actual product.
further:
https://www.geeksforgeeks.org/differences-between-verification-and-validation/
