What is the V model ?
The V model is another traditional method of software development. The V model stands for verification and validation. Just like the waterfall model each phase must be completed before another one can begin. Testing of the product is planned in parallel with a corresponding phase of development.
The various phases are as follows
Business and system requirement specifications begin the life cycle just like the waterfall model. The difference in this model is that before development a system test plan is created. The test plan focusses on meeting the functionality specified in the requirements gathering.
The High Level Design
This phase aims to design the system. It provides an overview of the solution and product and service/process. An Integration test takes place here to see can the pieces of software systems have the ability to work together.
The low Level Design
This is where the actual software components are designed. Component tests are created in this phase as well .
This phase is, again, where all coding takes place. Once coding is complete, the path of execution continues up the right side of the V where the test plans developed earlier are now put to use. Coding is at the bottom of the V-Shape model. Module design is converted into code by developers.
In the next blog I will discuss the advantages and disadvantage of the v model.