|Software development process|
|Paradigms and models|
|Methodologies and frameworks|
|Standards and BOKs|
The V-model is a term applied to a range of models, from a conceptual model designed to produce a simplified understanding of the complexity associated with systems development to detailed, rigorous development lifecycle models and project management models.
There are several radically different forms of the V-model, and this creates considerable confusion. The V-model falls into three broad categories.
Firstly there is the German V-Model "Das V-Modell", the official project management methodology of the German government. It is roughly equivalent to PRINCE2, but more directly relevant to software development. The key attribute of using a "V" representation was to require proof that the products from the left-side of the V were acceptable by the appropriate test and integration organization implementing the right-side of the V. 
In the UK and throughout the testing community worldwide, the V-model is widely seen as a vaguer illustrative depiction of the software development process as described in the ISTQB Foundation Syllabus for software testers. There is no single accepted definition of this model, which is more directly covered in the alternative article on the V-Model (software development). There are therefore multiple variations of this version. This problem must be borne in mind when discussing the V-model.
The US also has a government standard V-model which dates back about 20 years like its German counterpart. Its scope is a narrower systems development lifecycle model, but far more detailed and more rigorous than most UK practitioners and testers would understand by the V-model.
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 V represents the sequence of steps in a 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.
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. Sometimes they are even used interchangeably.
- "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."
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.
Systems engineering and verification
The systems engineering process (SEP) provides a path for improving the cost effectiveness of complex systems as experienced by the system owner over the entire life of the system, from conception to retirement.
It involved early and comprehensive identification of goals, a concept of operations that describes user needs and the operating environment, thorough and testable system requirements, detailed design, implementation, rigorous acceptance testing of the implemented system to ensure it meets the stated requirements (system verification), measuring its effectiveness in addressing goals (system validation), on-going operation and maintenance, system upgrades over time, and eventual retirement.
The process emphasizes requirements-driven design and testing. All design elements and acceptance tests must be traceable to one or more system requirements and every requirement must be addressed by at least one design element and acceptance test. Such rigor ensures nothing is done unnecessarily and everything that is necessary is accomplished.
The two streams
The specification stream mainly consists of:
- User requirement specifications
- Functional requirement specifications
- Design specifications
The testing stream generally consists of:
- Installation qualification (IQ)
- Operational qualification (OQ)
- Performance qualification (PQ)
The development stream can consist (depending on the system type and the development scope) of customization, configuration or coding.
The V-model is used to regulate the software development process within the German federal administration. Nowadays it is still the standard for German federal administration and defense projects, as well as software developers within the region.
The concept of the V-model was developed simultaneously, but independently, in Germany and in the United States in the late 1980s:
- The German V-model was originally developed by IABG in Ottobrunn, near Munich, in cooperation with the Federal Office for Defense Technology and Procurement in Koblenz, for the Federal Ministry of Defense. It was taken over by the Federal Ministry of the Interior for the civilian public authorities domain in summer 1992.
- The US V-model, as documented in the 1991 proceedings for the National Council on Systems Engineering (NCOSE; now INCOSE as of 1995), was developed for satellite systems involving hardware, software, and human interaction.
- The V-model first appeared at Hughes Aircraft circa 1982 as part of the pre-proposal effort for the FAA Advanced Automation System (AAS) program. It eventually formed the test strategy for the Hughes AAS Design Competition Phase (DCP) proposal. It was created to show the test and integration approach which was driven by new challenges to surface latent defects in the software. The need for this new level of latent defect detection was driven by the goal to start automating the thinking and planning processes of the air traffic controller as envisioned by the automated enroute air traffic control (AERA) program. The reason the V is so powerful comes from the Hughes culture of coupling all text and analysis to multi dimensional images. It was the foundation of Sequential Thematic Organization of Publications (STOP)  created by Hughes in 1963 and used until Hughes was divested by the Howard Hughes Medical Institute in 1985.
- The US Department of Defense puts the systems engineering process interactions into a V-model relationship.
One fundamental characteristic of the US V-model is that time and maturity move from left to right and one cannot move back in time. All iteration is along a vertical line to higher or lower levels in the system hierarchy, as shown in the figure. This has proven to be an important aspect of the model. The expansion of the model to a dual-Vee concept is treated in reference.
As the V-model is publicly available many companies also use it. In project management it is a method comparable to PRINCE2 and describes methods for project management as well as methods for system development. The V-Model while rigid in process, can be very flexible in application, especially as it pertains to the scope outside of the realm of the System Development Lifecycle normal parameters.
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.
- 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.
- The placing of contracts for services is not regulated.
- The organization and execution of operation, maintenance, repair and disposal of the system are not covered by the V-model. However, planning and preparation of a concept for these tasks are regulated in the V-model.
- The V-model addresses software development within a project rather than a whole organization.
- IBM Rational Unified Process (as a supporting software process)
- Systems architecture
- Systems analysis
- Systems design
- Dual Vee Model
- Clarus Concept of Operations. Publication No. FHWA-JPO-05-072, Federal Highway Administration (FHWA), 2005
- "The Dangerous & Seductive V Model", accessed January 9, 2013.
- "Das V-Modell site (in German)", accessed January 9, 2013.
- German Directive 250, Software Development Standard for the German Federal Armed Forces, V-Model, Software Lifecycle Process Model, August 1992
- "Fundamentals of the V-Modell". Retrieved 14 Apr 2016.
- "V-Modell XT, Part 1: Fundamentals of the V-Modell" (PDF). Retrieved 14 Apr 2016.
- "International Software Testing Qualifications Board – Foundation Level Syllabus", accessed January 9, 2013.
- "Systems Engineering for Intelligent Transportation Systems" (PDF). US Dept. of Transportation. p. 10. Retrieved June 9, 2007.
- "US Dept of Transportation, Federal Highway Administration. Systems Engineering Guidebook for ITS", accessed January 9, 2013.
- Forsberg, K., Mooz, H., Cotterman, H. Visualizing Project Management, 3rd edition, John Wiley and Sons, New York, NY, 2005. Pages 108-116, 242-248, 341-360.
- International Council On Systems Engineering (INCOSE), Systems Engineering Handbook Version 3.1, August 2007, pages 3.3 to 3.8
- "BUILDING ON A LEGACY: RENEWED FOCUS ON SYSTEMS ENGINEERING IN DEFENSE ACQUISITION" (PDF). Retrieved 14 Apr 2016.
- "Using V Models for Testing". Retrieved 14 Apr 2016.
- Forsberg, K., Mooz, H. (1998). "System Engineering for Faster, Cheaper, Better" (PDF). Center of Systems Management. Archived from the original (PDF) on April 20, 2003.
- "The SE VEE". SEOR, George Mason University. Retrieved May 26, 2007.
- Forsberg, K. and Mooz, H., "The Relationship of Systems Engineering to the Project Cycle," First Annual Symposium of the National Council On Systems Engineering (NCOSE), October 1991
- IEEE. "IEEE Guide--Adoption of the Project Management Institute (PMI) Standard A Guide to the Project Management Body of Knowledge (PMBOK Guide)--Fourth Edition". p. 452. doi:10.1109/IEEESTD.2011.6086685. Retrieved December 7, 2012.
- Systems Engineering Fundamentals. Defense Acquisition University Press, 2001.
- "V-Model Lifecycle Process Model". v-modell.iabg.de. Retrieved December 24, 2015.
- "Sequential Thematic Organization of Publications (STOP)". web.archive.org. Retrieved December 24, 2015.
- "Sustainable Development Possible with Creative System Engineering". ISBN 0615216307.
- "A New Systems Engineering Model and an Old, Familiar Friend; Figure 2 V-9 Process Interactions" (PDF). Defense AT&L. Apr 2006. p. 51. Retrieved 7 Apr 2016.
- "Further Development of the V-Modell". v-modell.iabg.de. Retrieved December 24, 2015.
- "Overview of the Activity Model of the V-Modell". v-modell.iabg.de. Retrieved December 24, 2015.
- "Limits of the VModel". v-modell.iabg.de. Retrieved December 24, 2015.
- Christian Bucanac, The V-Model
|Wikimedia Commons has media related to V-models.|
- Vee Model of Systems Engineering Design and Integration
- What is the V-model? (in German)
- V-Model XT Documentation (1.3)
- Death of the V-Model (small software projects but not large systems of systems?)