The V-model is an abstract, comprehensive project management structure for the software development. Its name refers to the V-shaped representation of the project elements such as IT-Systemdefinitionen and tests, arranged according to their rough temporal position and its detail depth (French diagram: ).

The first V-model was developed 1986 in Germany. First it was intended for IT-projects of the public hand, long it in addition, in the private sector is used.

Usually a new variant of the V-model from the variant preceding in each case is developed, as soon as an improvement need is recognized. General characteristics of these variants and the pro and cons, which accompany with their application, are described in separate articles (procedural model (software), processing concept (software)).

Contrary to a classical phase model in the V-model activities and results are only defined and no strict temporal succession is demanded. In particular one looks for the typical acceptance, which define a phase end, here in vain. It is possible nevertheless to illustrate the activities of the V-model e.g. in a water drop case or a spiral model.

History

In the year 1986 the Federal Ministry for defense started two projects

• Software development environment for information systems (SEU-IS) and
• Software development environment for weapon and weapon delivery systems (SEU-WS)

with the following goals:

• To make the costs over the entire software development and care process transparency and also limit in consequence.
• To guarantee and/or this further improve by suitable measures a minimum standard for software quality.
• To attain by comparability of the offers of third a larger independence from individual offerers to.
• To standardize and arrange more transparent the development of software in the own house.

The military origin

For this in principle also processing concepts of the NATO-allied would have been applicable, like e.g. the American standard DoD STD 2167 A or the French standard GAM T 17. A detailed examination of these models showed however that they were not able, all requirements to become fair. Thus one decided to an self-development, which brought a first version out of the V-model in the year 1988 - as result of the project SEU-WS -. Into this until April 1990 the realizations from the project SEU-IS were then integrated and the improved version of the V-model by decree was fixed from February 1991 by the Federal Minister for defense as level of development pool of broadcasting corporations for the software production with the German Federal Armed Forces.

The civilian V-model

Since also different federal authorities saw themselves confronted with completely similarly stored problems, the V-model at the end of of 1991 was transferred to the Federal Government for information technology at the coordination and advisory board in the federal administration (KBSt) to provide with the task a civilian version of the V-model. These work was final and by the Federal Minister of the defense and the Federal Minister of the Interior published and fixed the uniform version of the V-model resulting from it in August 1993.

V-model 97

New software development beginnings (e.g. Object orientation, etc.) made necessary a revision of the V-model, particularly since this was very strongly to the "“classical software development beginning"” cut up to this time. As result in June 1997 the V-model '97 was published, which was recommended since for any software development in the federal administration for application.

V-model XT

This work was replaced in the course by new realizations in the software development in February 2005 by the version 1.0 V-model of the XT (XT = extremes Tailoring). Points of main change are here

• the V-model becomes adaptable to the respective needs (tailorbar).
• Integration of the client: So far the defaults were aligned to the contractor. Now there are also procedure components for the client.
• Stronger modularity: The four past Submodelle exist in this form no longer, but only procedure components, from which the concrete procedural model of a project is arranged ("“tailoring"”).
• Stronger orientation toward agiler and incremental beginnings: "“Way of as, to which."” The V-model XT does not give any regulations over the temporal succession of procedure components. The produced products are located in the center and not the documentation as with RUP.

One finds an introductory overview in bases of the V-model.

Since the V-model in half-yearly distances is updated, the version 1.2 (of 1.02.2006) is replaced to 01.08.2006 by the version 1.3. Extensive documentation and tools, the program [http://ftp.uni-kl.de/pub/v-modell-xt/Release-1.2/Werkzeuge/Projektassistent/V-Modell-XT-Projektassistent-Windows.exe project assistant] so e.g. exist already now, which makes a producing and a Tailoring possible of the necessary documents.

Essential structure of the V-model

The structure of the documentation

The documentation V-model of the XT consists of 9 parts, about which only the two first parts are obligating for all V-model-users. The remaining 7 parts understand themselves as reference books. The V-model XT consists of the following parts:

1. Part 1: Bases of the V-model (introduction, concepts,"…)
2. Part 2: A route by the V-model (small example project)
3. Part 3: V-model-reference Tailoring (as I adapt the V-model to my
4. Part 4: V-model-reference roles (whom need I for my
5. Part 5: V-model-reference of products (as project results are to look, which they
6. Part 6: V-model-reference activities (as I provide
7. Part 7: V-model-reference convention illustrations (I already know VM97/CMMI/"… Where in the V-model XT do I find
8. Part 8: Appendix (which tools and methods/am I can Glossary"…)
9. Part 9: Collecting mains (collecting main files (rtf) with description of application)

The V-model-core

The V-model summarizes a set from similarly stored activities to a procedure component in such a way specified. Some these procedure components find with all projects application and therefore as V-model core are designated. In addition belong:

1. PM: Project management
2. QA: Quality assurance
3. Km: Configuration management
4. Pa: Problem and change management

Products and activities

The V-model defines a set of documents, which are called products. These consist of individual topics. Products, which have a strong contentwise connection, are too arranged again the same product group.

Each defined product goes through four conditions:

1. planned
2. in treatment
3. submitted
4. accepted

whereby the following transitions between these conditions are possible:

One calls activities, which change products, activities; these are for their part compound from individual partial activities, which treat then exactly in each case a topic. Contentwise related activities are combined thereby again into groups of activities. To each activity is exactly deposited, which products it necessarily and/or changed and which work procedures are necessary to cause the desired modification. For this purpose each activity a product river and a completion is defined. While the product river describes, from which activities the necessary input products with which condition come, in order in modified form and/or modified condition to a following activity to be then passed on, contain the completion more exact instructions for the execution of the activity.

The temporal succession of the activities results thus from the availability of the necessary (part) products in a certain condition.

Characteristics

Procedural models are used for the application development by IT-systems of most diverse size and complexity. In order to produce with completion of smaller and middle projects no excessively large additional expenditure, the V-model for these project sizes caper conditions, which reduce the quantity of the activities and products to the necessary measure, defines. One calls the procedure of the adaptation of the V-model on the project-specific needs Tailoring.

Tools

• in step (V-model 97 and V-model XT)
• XT editor
• XT project assistant

Articles in category "V-model"

We found here 1 articles.

Related Websites

We found here 3 related websites.

• tell me about v model - Q&A
  v model is model in which testing is done prallelly with development.left ... V - model in the SDLC will allow the process to have testing and coding as a ...


• Types of testing in the development process including the V model
  There are many testing types. This article explains each type of testing, and where it fits into the development process, including the V Model.


• V-Modell - Wikipedia, the free encyclopedia
  The V-model was developed to regulate the software development process ... The V-model is a graphical representation of the system development lifecycle. ...