5 Part 5: V-Modell Reference Work Products

5.3 Products

5.3.7 Requirements and Analyses

5.3.7.3 Requirements Specification Overall Project

Process module: Management of Multiple Projects

Responsible: Requirements Engineer (Acquirer) (when using process module Management of Multiple Projects)

Activity: Determining Requirements Overall Project

Participating: User, Executive, Project Leader, Data Protection Manager, Security Manager, Safety Manager

Work Product Attributes: initial

Purpose

The Product Requirements Specification Overall Project includes all mandatory requirements posed on the system to be developed, which describe the overall project in a complete and consistent manner. It is basis for the subdivision into sub-projects.

All relevant system requirements will be determined and documented by the supplier. The core of the Requirements Specification Overall Project comprises the functional and non-functional system requirements and an outline of the overall system design. The design considers the future environment and infrastructure for the system and provides guidelines for technological decisions. The outline of the overall system architecture is the decisive basis for subdividing the overall project into sub-projects.

In addition, the system life cycle phases to be supported will be identified and incorporated as logistic requirements. The delivery terms and acceptance criteria are also part of the requirements.

The functional and non-functional requirements are not only intended as development specifications, but also as basis for the tracing of requirements and the change management. The requirements should be prepared in such a way that traceability and a suitable change management are possible for the entire system life cycle.

The acquirer alone is responsible for the preparation and quality of the Requirements Specification. If required, he may task a third party with the preparation. Generally, the Requirements Specification should not specify technical solutions in order to ensure that architects and developers are not restricted in their search for optimum technical solutions.

Depends on

Requirements Specification, Project Proposal (see product dependency 5.4)

Requirements Specification (see product dependency 5.5)

Evaluation of the Overall Project Requirements Specification (see product dependency 5.25)

Requirements Specification, Project Proposal (see product dependency 5.27)