V Model

V - model

* This is the most common and classic of life cycle models, also referred to as a linear-sequential life cycle model. It is very simple to understand and use. In a
waterfall model, each phase must be completed in its entirety before the next phase can begin. At the end of each phase, a review takes place to determine if the project is on the right path and whether or not to continue or discard the project. Unlike what we mentioned in the general model, phases do not overlap in a waterfall model.

The least flexible and most obsolete of the life cycle models. Well suited to projects that has low risk in the areas of user interface and performance requirements, but

high risk in budget and schedule predictability and control.

Advantages
§ Simple and easy to use.
§ Each phase has specific deliverables.
§ Higher chance of success over the waterfall model due to the development of test plans early on during the life cycle.
§ Works well for small projects where requirements are easily understood.

Disadvantages
§ Very rigid, like the waterfall model.
§ Little flexibility and adjusting scope is difficult and expensive.
§ Software is developed during the implementation phase, so no early prototypes of the software are produced.
§ Model doesn’t provide a clear path for problems found during testing phases.