Quote:
Originally Posted by padmajasrinath
can anyone tell me about v-model?
|
The V-model was originally developed from the waterfall software process model.
The four main process phases – requirements, specification, design and implementation – have a corresponding verification and validation testing phase. Implementation of modules is tested by unit testing, system design is tested by integration testing, system specifications are tested by system testing and finally acceptance testing verifies the requirements. The V-model gets its name from the timing of the phases. Starting from the requirements, the system is developed one phase at a time until the lowest phase, the implementation phase, is finished. At this stage testing begins, starting from unit testing and moving up one test level at a time until the acceptance testing phase is completed.
[1] The V-model is easy to understand, but the timing of the phases where testing occurs after all implementation is done, is not an adequate approach in today’s iterative software processes. However, the test levels from the V-model which associate a certain process phase with a testing phase is still relevant and will be used in this project. When the test levels from the V-model are used in parallel with development, and more importantly, when the different levels are tested simultaneously in multiple
iterations, the V-model testing method can become an effective and manageable testing process.