The V-model is another form of traditional SDLC. The V stands for Verification and Calidation model. It is similar to the waterfall model in that it follows a sequential path as shown if Fig 1.9. As well as that, no phase is intitiated until the previous phase has been completed. Testing of each stage occurs in parrallel as can be seen also in Fig 1.9.
In the model shown above there are 5 main stages. They are as follows:
High level design stage: at this stage the system architecture is designed and an integrating plan is also created to how well or otherwise the various components of the system work in unison.
Low level design stage: here the reason for each part of the system is made clear along with creating viable component tests.
Implementation stage: similar to the waterfall model, this is where the coding occurs.
At the final stage the developers convert the module design into code.
Testing occurs in parallel to all stages of the process bar the last.
Advantages of V-model:
- Simplistic in use.
- Testing occurs in parallel to each stage.
- Problems can be detected early and stopped.
Disadvantages of V-model:
- It is a rigid model and unaccommodating to change.
- There are no prototypes produced early on in the system.
- Documents are produced at the start which means if changes are made then the documentation should be adjusted accordingly.
The v-model is best suited to small or medium sized projects with clearly defined requirements.
It is however regarded as a risky enough model.