1 Part 1: Fundamentals of the V-Modell

1.3 Basic Concepts of the V-Modell

1.3.1 Overall Structure of the V-Modell

The V-Modell regulates "who" has to do "what" and "when" during a project. Figure 2 provides a survey of the overall structure of the V-Modell. The V-Modell can be applied to a great variety of project constellations; however, not all »V-Modell Project follow the same pattern. Depending on some characteristics, the projects can be classified and subdivided into »Project Type.

In order to ensure that the V-Modell can be employed simply and without significant effort, various »Project Type Variants are predefined, which determine the so-called »Project Execution Strategy. The process modules which must be used and the process modules which can be selected in addition are specified for every project type.

A »Process Module covers an actual task which may have to be accomplished during a V-Modell project. The »Work Product which have to be developed within the scope of the task, the »Activity required for developing the individual products and the »Roles included in the creation of the products are specified within a process module. The individual process modules are self-contained.

The project type does not only define the process modules to be used but also the possible project type variants, which in turn determine additional process modules to be used and the general conditions for the project execution strategy of a project. A »Project Execution Strategy corresponds to a sequence of decision gates. A »Decision Gate indicates a »Project Progress Stage in the »Project Setting where the current state of the project is evaluated. Depending on the evaluation, the Executives decide on the further project processing and can take corrective action as required.

Some process modules and decision gates must be applied to every project compliant with the V-Modell in order to ensure a minimum project execution quality. These mandatory process modules form the »V-Modell Core.

The document »Fundamentals of the V-Modell describes how the standards of the V-Modell should be implemented within the scope of a project. It covers the supporting organizational aspects and the fulfillment of the actual project task.


Figure 2: Overall Structure of the V-Modell and Presentation Based on the Point of View

The elements described up to now are the actual contents of the V-Modell, which are complemented by so-called »Mapping to Standards. A mapping to standards establishes a relation between the terms of a (quasi) standard or a regulation and the contents of the V-Modell. Mapping to Standards include, among others, the »Mapping to CMMI® and the »Mapping to ISO 15288. For users, who have processed their projects up to now in accordance with other regulations, procedures or standards, the mappings to standards facilitate the change to the V-Modell.

During a project, different persons and groups of persons deal with the particular contents of the V-Modell. At the beginning of a project, e.g., the project-specific adaptation of the V-Modell is of prime importance for the »Project Leader. At a later stage of the project, the project leader and the project team focus on the actual process and the respective individual tasks. For quality assurance, on the other hand, the requirements posed by the V-Modell on the products to be tested are essential.

Thus, every V-Modell user group sees the contents of the V-Modell from a different point of view. In order to fulfill the specific requirements of the individual user groups, the documentation of the V-Modell is subdivided into »V-Modell Reference, which correspond exactly to these points of view. Thus, the »V-Modell Reference Tailoring especially describes the creation of a project-specific V-Modell. The contents of the individual V-Modell References have already been described briefly in »Objectives and Structure of the V-Modell.