V Model - kubapeter/portfolio GitHub Wiki

The V-model is a [linear process model]]. It adds a more complete focus on testing the product than the [[Waterfall model]]. The [phases of the process form two branches.

  • The left branch in more or less identical with the phases of the Waterfall model.
  • The right branch represents integration and testing activities. As testing work proceeds up the right branch, some level of the product (on the right side) is actively verified against the corresponding design or requirements (on the left side).

Pros and cons

Pros:

  • easy to understand
  • clearly defines deliverables and milestones
  • emphasizes the importance of analysis before design, and design before implementation
  • can be adopted within teams using more sophisticated processes, for well-specified parts of the product that can be outsourced

Cons:

  • not very adaptable to change
  • the client does not see the finished product until everything is virtually complete