1 Part 1: Fundamentals of the V-Modell

1.3 Basic Concepts of the V-Modell

1.3.3 Project Type Variant

For each »Project Type, the V-Modell offers at least one »Project Type Variant, which characterizes the Project in more detail. A Project Type Variant in a Project determines particularly the general conditions for possible project flows, which are used as selection criteria in the »Tailoring process. A Project Type Variant determines the design of the »Project Execution Strategy and thus the possible workflow in the coarse plan of a Project.

The selection of a Project Variant can also integrate »Process Module and »Project Characteristics , complementing those of the project type specifications, into the Project.

Figure 4 indicates different Project Type Variants provided by the V-Modell and the characteristics used for selecting the suitable Project Type Variant:

• For the Project Type »Introduction and Maintenance of an Organization-Specific Process Model, there is only one suitable Project Type Variant, which has the same name.
• For the Project Type »System Development Project (Acquirer) , the distinction is based on the structure of the order: The Project Type Variant is selected depending on the fact as to whether the Acquirer cooperates with one or several Suppliers simultatneously.
• The Selection of a suitable Project Type Variant within the framework of the Project Types »System Development Project (Supplier) and »System Development Project (Acquirer/Supplier) generally depends on the system life cycle section covered by the Project. Enhancement and migration require another Project Type Variant than system maintenance.

Figure 4: Assignment of Project Type Variants to Project Types