V-model (software development): Difference between revisions

Revision as of 09:50, 17 April 2024

Revision as of 09:52, 17 April 2024

Line 4:

{{Software development process}}

In [[software development]], the '''V-model'''<ref>[[Kevin Forsberg]] and [[Harold Mooz]], "The Relationship of System Engineering to the Project Cycle", in Proceedings of the First Annual Symposium of National Council on System Engineering, October 1991: 57–65.</ref> represents a [[software development process|development process]] that may be considered an extension of the [[waterfall model]] and is an example of the more [[V-model|general V-model]]. Instead of moving down in a linear waylinearly, the process steps are bent upwards after the [[source code|coding]] phase, to form the typical V shape. The V-Model demonstrates the relationships between each phase of the development life cycle and its associated phase of [[Software testing|testing]]. The horizontal and vertical axes represent time or project completeness (left-to-right) and level of abstraction (coarsest-grain abstraction uppermost), respectively.

== Project definition phases ==