What is V Model?
V model is also known as the Verification and Validation model. In the V model, the testing phase goes in parallel with the development phase. Thus, the testing phase starts right at the beginning of SDLC.
As we can see in the above diagram, the test activities start in parallel with the development activities e.g. during the requirement analysis phase, acceptance-test cases are prepared by the testing team; during the system design phase, the system test case is prepared. Similarly, for each phase of development, a corresponding QA activity is performed. Later, when the deliverable gets ready, the QA artifacts are used to conduct the testing. Along with that, each phase of the development phase is verified before moving to the next phase.
Advantages of V Model
- Each phase of development is tested before moving to next phase, hence there is a higher rate of success.
- It avoids defect leakage to the later phases as each phase is verified explicitly.
- The model has clear and defined steps. So, it is easier to implement.
- It is suitable for smaller projects where requirements are fixed.
Disadvantages of V Model
- The testing team starts in parallel with development. Hence, the overall budget and resource usage increases.
- Change in requirement are difficult to incorporate.
- The working model of the software is only available in the later phases of the development.
- It is not suitable for complex and large applications because of its rigid process.
Kuldeep is the founder and lead author of ArtOfTesting. He is skilled in test automation, performance testing, big data, and CI-CD. He brings his decade of experience to his current role where he is dedicated to educating the QA professionals. You can connect with him on LinkedIn.
2 thoughts on “V Model”
i believe in the diagram , acceptance testing & Unit testing should be swapped to make it look correct.
Thanks a lot. Corrected.