V-Model
From Wikipedia, the free encyclopedia
The V-Model defines a uniform procedure for IT product development. It is the standard for German federal administration and defense projects. As it is publicly available many companies also use it. It is a project management method comparable to PRINCE2 and describes methods for project management as well as methods for system development.
The current version of the V-Model is the V-Model XT (http://www.v-modell-xt.de) which was finalized February 2005. It is not really comparable to CMMI. While CMMI only describes "What" has to be done, the V-Model also describes "How" and "When" it has to be done and "Who" is responsible for doing it.
The V-model was developed to regulate the software development process within the German federal administration. It describes the activities and results that have to be produced during software development.
The V-model is a graphical representation of the system development lifecycle. It summarizes the main steps to be taken in conjunction with the corresponding deliverables within computerized system validation framework.
The left tail of the V represents the specification stream where the system specifications are defined. The right tail of the V represents the testing stream where the systems are being tested (against the specifications defined on the left-tail). The bottom of the V where the tails meet, represents the development stream.
The specification stream mainly consists of:
- User Requirement Specifications
- Functional Specifications
- Design Specifications
The testing stream generally consists of:
- Installation Qualification
- Operational Qualification
- Performance Qualification
The development stream can consist (depending on the system type and the development scope) in customization, configuration or coding.
[edit] See also
- (French) Cycle en V (if you understand French, this page is far more detailed)
- RUP (as a different process)
[edit] External links
- What is the V-model? (in German)
- Types of Testing
- Image
- Software Processes (also the V-Modell)
- "New Models for Test Development" by Brian Marick, Quality Week '99 - a rebuttal of the V-model
