Verification and Validation is the process of investigating whether a software system satisfies specifications and standards and fulfills the required purpose. Barry Boehm described verification and validation as the following:
Verification: Are we building the product right?
Validation: Are we building the right product?
Verification
Verification is the process of checking that software achieves its goal without any bugs. It is the process to ensure whether the product that is developed is right or not. It verifies whether the developed product fulfills the requirements that we have. Verification is simply known as Static Testing.
Static Testing
Verification Testing is known as Static Testing and it can be simply termed as checking whether we are developing the right product or not and also whether our software is fulfilling the customer’s requirement or not. Here are some of the activities that are involved in verification.
- Inspections
- Reviews
- Walkthroughs
- Desk-checking
Verification and Validation
Validation
Validation is the process of checking whether the software product is up to the mark or in other words product has high-level requirements. It is the process of checking the validation of the product i.e. it checks what we are developing is the right product. it is a validation of actual and expected products. Validation is simply known as Dynamic Testing.
Dynamic Testing
Validation Testing is known as Dynamic Testing in which we examine whether we have developed the product right or not and also about the business needs of the client. Here are some of the activities that are involved in Validation.
- Black Box Testing
- White Box Testing
- Unit Testing
- Integration Testing
Note: Verification is followed by Validation.
Validation” width=”inherit” height=”inherit”>
For more, refer to Differences Between Verification and Validation.
Questions For Practice
1. Software validation mainly checks for inconsistencies between [UGC NET 2019]
(A) Use cases and user requirements
(B) Implementation and system design blueprints
(C) Detailed specifications and user requirements
(D) Function specifications and use cases
Answer: Correct Answer is (C).
For more, refer to UGC-NET | NTA UGC NET 2019 June – II | Question 26
2. Complete each of the following sentences in List-1 on the left-hand side by filling in the word or phrase from List-2 on the right-hand side that best completes the sentence. [UGC-NET 2017]
|
List-1 |
List-2 |
|---|---|
|
i. Determining whether you have built the right system is called _______. |
A. Software Testing |
|
ii. Determining whether you have built the system right is called _______. |
B. Software Verification |
|
iii. ______ is the process of demonstrating. |
C. Software debugging the existence of defects |
|
iv. ______ is the process of discovering the cause of a defect and fixing it. |
D. Software Validation |
(A) i – B, ii – D, iii – A, iv – C
(B) i – B, ii – D, iii – C, iv – A
(C) i – D, ii – B, iii – C, iv – A
(D) i – D, ii – B, iii – A, iv – C
Solution: Correct Answer is (D).
3. Which type of testing is typically associated with software verification?
(A) Regression testing
(B) Usability testing
(C) Alpha testing
(D) User acceptance testing
Solution: Correct Answer is (A).
Frequently Asked Questions
1. How does automated testing fit into the verification and validation process?
Answer:
Tools and Scropts present in Automated Testing helps in improving the efficiency of verification and validation. It helps in automating repetitive test cases, reducing human error, and providing rapid feedback on code changes.
2. List some challenges in Verification and Validation Process?
Answer:
Some of the challenges in verification and validation: Some of the challenges in verification and Validation is listed below. the creation of test cases, handling difficult complex interaction, clear and unambiguous requirements, creating comprehensive test cases, handling complex software interactions, managing testing environments, and dealing with time and resources.
