2. It means verification and validation .
Just like WATER FALL model, The life cycle of the V model
is a sequential path of the execution of the process.
Each phase must be completed before the next phase
begins.
The testing of the product is planned in parallel with
corresponding phase of development.
Introduction
3. Objectives
It should be used for small to medium size
projects where requirements are clearly
defined.
It should be chosen when simple technical
resources are available with needed
technical expertise.
5. Principles of V-Model
• Large to Small
• Data/Process Integrity
• Scalability
• Cross Referencing
• Tangible Documentation
6. Why preferred?
When to use?
• It is easy to manage due to the rigidity of the model. Each phase of V-
Model has specific deliverables and a review process.
• Proactive defect tracking – that is defects are found at early stage.
• Where requirements are clearly defined and fixed.
• The V-Model is used when ample technical resources are available with
technical expertise.
7. Advantages
• Simple and easy to use.
• Testing activities like planning, test design happens well
before coding.
• This saves a lot of time.
• Avoids the down word flow of the defects.
• Works well for small projects where requirements are easily
understood.
8. Disadvantages
• Very rigid and cost flexible.
• Software is developed during the implantation phase,
so no early prototypes of the software are produced.
•If any changes happens, then the test requirement
documents has been updated.
9. Conclusion
High confidence of the costumer is required for
choosing the V-shaped model approach since no
prototypes are produced. There is a very high risk
involved in meeting expectation.