V Model
V Model
V Model
with developing systems.[2][3][4] In systems engineering it is used to define a uniform procedure for product or project development
Overview
The V-model is a graphical representation of the systems development lifecycle. It summarizes the main steps to be taken in conjunction with the corresponding deliverables within computerized system validation framework. The VEE is a process that represents the sequence of steps in a project life cycle development. It describes the activities and results that have to be produced during product development. The left side of the VEE represents the decomposition of requirements, and creation of system specifications. The right side of the V represents integration of parts and their verification.[3][4][5][6][7] V stands for "Verification and Validation" 77. It is very similar to the Classic Waterfall model as it is quite rigid and it contains a lot of iteration.
Objectives
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 acquirers 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.