The V-Model is Dead. Long Live the V-Model!
A V-model documents relationships between information, and does not restrict the
sequence of creation of information.
People who thought that a V-model is not useful or necessary are often dissatisfied
with restrictions that they themselves have added to a V-model, rather than the
original intention and essence of a V-model.
Some people think of a waterfall model when a V-model is mentioned. And it
seems that most people have not read the original article, from which the waterfall
model was extracted, from Dr. Winston W. Royce which warns against the
simplistic one way step-by-step development with no iterations. Dr. Royce in his
article MANAGING THE DEVELOPMENT OF LARGE SOFTWARE
SYSTEMS highly recommends an iterative and incremental approach.
A V-model represents graphically; ownership of and relationships between
A V-model is a static model and does not restrict sequence of creation of artefacts.
The V-model is state-of-the-art.