1 Part 1: Fundamentals of the V-Modell

1.3 Basic Concepts of the V-Modell

1.3.2 Project Types

The V-Modell can profitably be used in a variety of project constellations as guideline for the systematic managing and processing of a project. Not every V-Modell project follows the same stereotype pattern. Depending on characteristic features, projects can be subdivided into »Project Types. This classification will be described briefly in the following paragraphs.

A project is classified by its project type. The V-Modell supports projects for awarding a contract to a supplier and projects for developing a »System as supplier or as acquirer/supplier. These three projects types are distinguished based on the project role which the project assumes with respect to other stakeholders. The project roles are subdivided into »Acquirer, »Supplier or Projects where specification of requirements, project management and development are executed within an. organization (Acquirer/Supplier). Each project role implies a specific view with regard to the project and includes several specific project tasks. The V-Modell uses the so-called Subject of the Project for concretizing the framework of the approach. The V-Modell supports the development of software (SW), hardware (HW), complex or embedded hardware and software systems (HW and SW) and the system integration. The »Tailoring process must provide a suitable »Project Characteristic . In addition to contract awarding and development project types, the V-Model also supports projects for the introduction and maintenance of process models. For the »Introduction and Maintenance of an Organization-Specific Process Model , the V-Modell offers an individual project type.

The different project roles can be subdivided into three classes. In the project role Acquirer/Supplier, exactly one V-Modell project is executed in order to autonomously develop a system or an organization-specific process model. In the project role Acquirer, a system development contract is awarded to one or more suppliers based on specified requirements. In the project role Supplier, a system development project is executed based on the requirements specified by the Acquirer. It is important to note, that a distinction between Acquirer and Supplier is impossible during the development of an organization-specific process model.


Figure 3: Classification of Projects and Subdivision into Project Types

As shown in Figure 3, the following project types are specified based on the Subject of the Project and the Project Role:

The selection of a project type is the first step for determining "what" has to be done in a project. The decision for a »Project Type integrates the process modules into the project and determines the project characteristics to be considered.