3 Part 3: V-Modell Reference Tailoring

3.4 Project Types

3.4.3 System Development Project (Acquirer/Supplier)

Description

This project type deals with V-Modell projects which need not be separated into a project on the acquirer side and a project on the supplier side. This may be possible if the system development project is executed by one organization or if several organizations participating in a project cooperate deliberately. In contrast to the separated »System Development Project (Acquirer) and »System Development Project (Supplier), the System Development Project (Acquirer/Supplier) does not require the work product Supply and Contracting and the double project organization with two Project Leaders. Tasks of the acquirer side may - for example - be fulfilled by a functional department, and tasks of the supplier side may be fulfilled by the IT department.

The mandatory and optional process modules for this project are depicted in Figure Figure 9. The »Decision Gate of the possible »Project Execution Strategy for this »Project Type are listed in Figure Figure 10.

images/ALLG-VBLandkarte-AGAN.gif

Figure 9: Relations between the »Process Module for the Project Type »System Development Project (Acquirer/Supplier)

images/ALLG-PDS-PTAGAN.gif

Figure 10: Decision Gates of the Project Execution Strategies Available for Projects of the Type System Development Project (Acquirer/Supplier)

Possible project type variants:

Project (Acquirer/Supplier) Including Development, Enhancement or Migration, Project (Acquirer/Supplier) Including System Maintenance

Process Modules to be used:

Specification of Requirements, Configuration Management, Delivery and Acceptance (Acquirer), Delivery and Acceptance (Supplier), Problem and Change Management, Project Management, Quality Assurance, System Development

Project characteristics to be determined during tailoring:

Security (Supplier), Life Cycle Cost Management, Project Measures, Off-the-Shelf Products, User Interface, Subject of the Project