1 Part 1: Fundamentals of the V-Modell

1.4 Management Mechanisms of the V-Modell

1.4.3 Project Planning

After the project-specific adaptation of the V-Modell (»Tailoring) has been completed, the project execution strategy, which specifies the sequence of the project progress stages to be achieved during the project, has been determined. A project progress stage is represented by a decision gate.

The actual number of decision gates and the corresponding project progress stages depend on the needs of the project to be executed. The project execution strategy only provides a general frame, which has to be filled by the project as required.

Within the scope of a system development, for example, a prototype of the system should first be developed in order to validate the prepared »Overall System Specification; afterwards, the contracts for the proper system development should be awarded based on the gained experience. As shown in Figure 10, the »V-Modell Project will then include the »Decision Gate »Requirements Specified, »Request for Proposal Released, »Contract Awarded and »Acceptance Completed twice - once for the prototype and once for the proper system.

images/ALLG-PDS-Beispiel.gif

Figure 10: Project-Specific Development of the Project Execution Strategy

This project-specific development of the »Project Execution Strategy has to be prepared by the »Project Leader during project planning and has to be included in the »Project Manual and the »Project Plan.

Thus, a basic frame for a detailed project planning and organization is defined. The decision gates of the project execution strategy give the order of the products to be created. A product which will be created once and only once during a project is designated as »Initial Product in the V-Modell. The initial products and the products defined by the decision gates - together with the corresponding activities - can be integrated immediately into the project plan.

A so called »Generative Product Dependency defines additional products and activities which have to be planned. A generative product dependency defines what particular contents of a product imperatively imply the creation of additional products. However, it is not regulated, when these products have to be finished. For example, the V-Modell contains a generative product dependency defining that for each »Hardware Unit that has been identified in the »System Architecture, a »Hardware Specification has to be created. In detail, the generative product dependencies are described in the »V-Modell Reference Work Products.

The project plan must be complemented by additional products and activities as required by these generative product dependencies. In addition, further products - and thus also activities - can of course be integrated into the plan, always considering the defined generative product dependencies.