Vee Model
The V-model of the systems engineering process.[1]
The V-model is a graphical representation of a systems development lifecycle. It is used to produce
rigorous development lifecycle models and project management models. The V-model falls into
three broad categories, the German V-Modell, a general testing model and the US government
standard.[2]
The V-model summarizes the main steps to be taken in conjunction with the corresponding
deliverables within computerized system validation framework, or project life cycle development. It
describes the activities to be performed and the results that have to be produced during product
development.
The left side of the "V" represents the decomposition of requirements, and creation of system
specifications. The right side of the "V" represents integration of parts and their validation. However,
requirements need to be validated first against the higher level requirements or user needs.
Furthermore, there is also something as validation of system models (e.g. FEM). This can partially
be done at the left side also. To claim that validation only occurs at the right side may not be correct.
The easiest way is to say that verification is always against the requirements (technical terms) and
validation always against the real world or the user needs.
Validation can be expressed by the query "Are you building the right thing?" and verification by "Are
you building it right?"
Validation vs. verification[edit]
It is sometimes said that validation can be expressed by the query "Are you building the right thing?"
and verification by "Are you building it right?" In practice, the usage of these terms varies.
The PMBOK guide, an IEEE standard (jointly maintained by INCOSE, the Systems engineering
Research Council SERC, and IEEE Computer Society) defines them as follows in its 4th edition:[17]
"Validation. The assurance that a product, service, or system meets the needs of the customer
and other identified stakeholders. It often involves acceptance and suitability with external
customers. Contrast with verification."
"Verification. The evaluation of whether or not a product, service, or system complies with a
regulation, requirement, specification, or imposed condition. It is often an internal process.
Contrast with validation."
Objectives[edit]
The V-model provides guidance for the planning and realization of projects. The following objectives
are intended to be achieved by a project execution:
Minimization of project risks: The V-model improves project transparency and project control
by specifying standardized approaches and describing the corresponding results and
responsible roles. It permits an early recognition of planning deviations and risks and improves
process management, thus reducing the project risk.
Improvement and guarantee of quality: As a standardized process model, the V-Model
ensures that the results to be provided are complete and have the desired quality. Defined
interim results can be checked at an early stage. Uniform product contents will improve
readability, understandability and verifiability.
Reduction of total cost over the entire project and system life cycle: The effort for the
development, production, operation and maintenance of a system can be calculated, estimated
and controlled in a transparent manner by applying a standardized process model. The results
obtained are uniform and easily retraced. This reduces the acquirer's dependency on the
supplier and the effort for subsequent activities and projects.
Improvement of communication between all stakeholders: The standardized and uniform
description of all relevant elements and terms is the basis for the mutual understanding between
all stakeholders. Thus, the frictional loss between user, acquirer, supplier and developer is
reduced.
Advantages[edit]
These are the advantages V-model offers in front of other systems development models:
The users of the V-model participate in the development and maintenance of the V-model. A
change control board publicly maintains the V-Model. The change control board meets
anywhere from every day to weekly and processes all change requests received during system
development and test.[23]
The V-model provides concrete assistance on how to implement an activity and its work steps,
defining explicitly the events needed to complete a work step: each activity schema contains
instructions, recommendations and detailed explanations of the activity.
[Link]
