1 Part 1: Fundamentals of the V-Modell

1.3 Basic Concepts of the V-Modell

1.3.5 V-Modell Core and Process Module Map

The »Process Module used are specified for every »Project Type and every Project Type Variant. Thus, the »Process Module is the central unit of »Tailoring, i.e., of the project-specific adaptation of the V-Modell to a concrete »V-Modell Project. Thereby, the »Process Modules required for a »V-Modell Project are selected and specified in accordance with the specifications of the »Project Type. The Process Modules are divided into four areas depending on the project type. The color identification of these project types are used in Figure 6 for allocating process modules.

V-Modell Core. The first area contains those Process Modules, that may be used in every V-Modell Project. It contains the »V-Modell Core , which ensures a minimum level of project execution quality: in every project »Project Compliant to the V-Modell, the basic management mechanisms as defined in the »Process Module of the »V-Modell Core shall be used. As shown in Figure 6, the »Process Module of the »V-Modell Core include »Project Management, »Quality Assurance, »Configuration Management and »Problem and Change Management.

In addition, but independent of the V-Modell Core, the »Process Modules »Life Cycle Cost Management and »Measurement and Analysis may be used in every »Project Type . »Life Cycle Cost Management defines procedures and tools for integrating the project management into the superior financial management. »Measurement and Analysis provides procedures for the organization-wide acquisition and evaluation of several independent parameters.

Introduction and Maintenance of an Organization-Specific Process Model. Another area contains the process modules for the development of an organization-specific process model. The only process module in this area is »Introduction and Maintenance of an Organization-Specific Process Model. It respects the procedures and directives for the introduction of an organization-specific process module and the following establishment of a continuous improvement process.

System Development. The third area covers all process modules that are necessary or optional for system development. These are »Specification of Requirements, »System Development, »Hardware Development, »Software Development, »Integrated Logistic Support , »Enhancement and Migration of Legacy Systems, »Evaluation of Off-the-Shelf Products, »Usability and Ergonomics, »Safety and Security (Supplier), and »Safety and Security. In addition, the process module »Management of Multiple Projects belongs to this area. It supports the functional segmentation of an overall project into several sub-projects before the final specification of the requirements.

Acquirer/Supplier Interface. The fourth area contains those process modules that serve the communication between Acquirer and Supplier. It covers »Delivery and Acceptance (Acquirer), » Delivery and Acceptance (Supplier), »Drafting and Conclusion of Contract (Acquirer), and » Drafting and Conclusion of Contract (Supplier). These process modules define the relationship between Acquirer and Supplier and how it is fixed contractually. Moreover, it describes how the developed item has to be delivered by the Supplier to the Acquirer and how the acceptance procedure has to be organized.

The individual process modules of the V-Modell will be described in detail in the »V-Modell Reference Tailoring.


Figure 6: »Process Module Map