2V’s of coding

To understand the meaning of the 2V’s of coding which are verification and validations, there must be a descriptive key difference between them so that one can make a conclusion of what is it of each one. Verification and validation are the process of reviewing a code to check for system specifications and standards that must be satisfied.  The informatic engineer, Barry W. Boehm, does an incredible job at describing each of the 2V’s. He states that verification answers the question of “Are we building the product right?”, and that validation answers the question of “Are we building the right product?”.

There are several tools, techniques and tips when doing both of the V’s. These tools help us to make the work correctly and with the technology that we have, we can make the verification and validation much faster. From the use of these tools we find the first difference between Validation and verification which is the order that they take. Verification is followed by validation because verification checks that the software will run as a static testing, while validation is used when the software can run, and we want to find if it is what we wanted.

Verification

It is a process of reviewing and checking for any bugs in the software. The goal must be achieved by the software in this process and any errors need to be fixed before jumping into the validation process. The verification process has specifications and requirements that it must have so that one can be sure that it is developed right or not. As we said before, verification is a static testing because it is being reviewed with patience and examines very specific blocks of code.

Activities involved in verification:

• Inspections
• Reviews
• Walkthroughs
• Desk-checking

Validation

It is the process that takes places after the verification one. This process checks whether the software is up to the mark of the requirements. In this time, it checks the flow of processes within the software so that it has the efficiency and complexity that it is looked for. As the question in the beginning stated, this process checks if we are developing the right product. That is why it is a dynamic testing, because we are using the whole program as it is intended to be used in the future.

Activities involved in validation:

• Black box testing
• White box testing
• Unit testing
• Integration testing

To conclude with verification and validation, there is a table of comparatives from Guru99 which can help you have a more in-depth realization of differences between both processes.

Verification	Validation
The verifying process includes checking documents, design, code, and program	It is a dynamic mechanism of testing and validating the actual product
It does not involve executing the code	It always involves executing the code
Verification uses methods like reviews, walkthroughs, inspections, and desk- checking etc.	It uses methods like Black Box Testing, White Box Testing, and non-functional testing
Whether the software conforms to specification is checked	It checks whether the software meets the requirements and expectations of a customer
It finds bugs early in the development cycle It finds bugs early in the development cycle	It can find bugs that the verification process can not catch

A river cuts through a rock not because of its power, but its persistence