A Developer Gateway To IT World...

Techie Uncle Software Testing Core Java Java Spring C Programming Operating System HTML 5 Java 8 ES6 Project

V Model

Spiral Model

What is V Model?

  1. It comes under Software Development Life Cycle(SDLC) model.

  2. The execution of this model happens in sequential manner in a V Shape.

  3. Development of each step directly associated with the testing phase.

  4. The next phase will executes only after the completion of the previous phase execution.

  5. In this model, development and testing will work corresponding.

  6. The V-Model is an extension of the waterfall model.

  7. It is also known as Verification and Validation model.


It is a static technique.In this technique, testing is done without executing the code.This technique used for document verification.Documents always works as static.

It includes:


  1. In this we do review of requirements.

  2. In this we do review of documents.

  3. In this we do review of design.

  4. In this we do review of coding.


  1. In this we do verifaction with the help of BA, developer and teamleader.

  2. In this we schedule meeting with teamleader or manger for out queries related to product.


  1. It is a formal way review.

  2. We discuss the issues with team and raise the issues to solve.

  3. This meeting can happens at anytime.

  4. No schedule of meeting as such.


It is a dynamic technique. It contains functional and non-functional testing done by executing codes. It is the process to evaluate the software after the completion of the development phase to determine whether the software meets the customer expectations and requirements.

Phases of V Model:-

  • Planning(Feasibility Study)

  • Design

  • Development

  • Testing

Advantages of V Model:-

  • It is easy to understand and use.

  • It avoids the downward flow of the defects.

  • It works well for small projects.

  • High utilization of resource.

  • Higher chancees of success over the waterfall model .

Disadvantages of V Model:-

  • It is not a good for object-oriented projects.

  • It is not a good for complex projects.

  • It is not good for those projects where requirements are not clear.

  • It is least flexible.

  • It is very expensive model.