The V-Model is one of the most important models for showing the development process and the links between software development and testing. This section explains how the V-Model was created and what its advantages and disadvantages are.
How the V-Model was Created
The V-Model is an example of a Software Development Lifecycle specifying what activities are performed in which order. It is derived from an older model called the Waterfall, and it more accurately represents what the key aspects of traditional development should be. These articles show the history and features behind the V-Model.
- Software Development Life Cycle - explains the basic principles of what a software development life cycle is.
- Waterfall Model the seven stages of a waterfall model and how they match the four phases of a SDLC.
- From Waterfall model to V-Model - explains how the V-Model is derived from the waterfall model and the advantages of doing so.
- Types of Testing - gives an overview of all types of testing that should be employed during a project.
- The old V-Model diagram that was on this site.
The Advantages and Disadvantages of the V-Model
The V-Model has a number of advantages, in fact so many that the disadvantages can go unnoticed. The V-Model in particular lends itself to the ideas of verification and validation. These articles explore these ideas.
- Verification and Validation - Definitions and diagrams showing what each term means for testing and the key differences between them.
Where V-Models Help
- Why Projects Fail - six key issues about why projects fail.
- How Projects Succeed describes factors to avoid project failure.