6 Part 6: V-Modell Reference Activities

6.3 Activities

6.3.7 Requirements and Analyses

6.3.7.1 Determining Requirements Overall Project

Purpose

The aim of the activity will be to specify the requirements and an outline of the acquirer's overall system design in such a way that the overall project can be subdivided into sub-projects. This activity will also create the preconditions for the traceability of user requirements over the whole life cycle of a system.

In an iterative process, user requirements shall be continuously refined and improved until their quality and detail will be sufficient for a subdivision of the overall project into sub-projects. This will be done by making analyses, setting priorities, making evaluations and establishing a quality assurance process for all user requirements. After checking the user requirements with regard to their feasibility, cost-effectiveness and affordability, the overall project can be subdivided into sub-projects, which can be realized independently.

When defining the the Requirements Specification Overall Project, the initial situation and the objective shall be described at first. This is followed by the preparation of the functional and non-functional requirements. At the same time, an »Outline of the Life Cycle and the Overall System Architecture shall be prepared. The Outline of the Overall System Architecture is the most important foundation fo the subdivision of the overall project into sub-projects.

The process of defining the requirements will end with the analysis of the quality of the requirements and the preparation of the scope of delivery and the acceptance criteria.

6.3.7.1.1 Describing Initial Situation and Objectives

See Describing Initial Situation and Objectives in activity Determining Requirements.

6.3.7.1.2 Specifying Functional Requirements

See Specifying Functional Requirements in activity Determining Requirements.

6.3.7.1.3 Specifying Non-Functional Requirements

See Specifying Non-Functional Requirements in activity Determining Requirements.

6.3.7.1.4 Preparing Outline of System Life Cycle and Overall System Architecture

See Preparing Outline of System Life Cycle and Overall System Architecture in activity Determining Requirements.

6.3.7.1.5 Determining Risk Acceptance and Safety and Security Levels

See Determining Risk Acceptance in activity Determining Requirements.

6.3.7.1.6 Determining Sub-Projects

The individual elements of the overall system architecture shall be analyzed in order to determine if the overall project can be subdivided into sub-projects which will be executed independently. If the project cannot be subdivided into completely "autonomous" sub-projects, the interdependences between the sub-projects shall be described. These interdependences can be described based on technical interfaces, delivery items, schedules and resources.

Afterwards, the functional and non-functional requirements posed on the overall project shall be assigned to the respective sub-projects.

A specific sub-project Integration must be defined in order to integrate the sub-projects to be realized.

6.3.7.1.7 Analyzing Quality of Requirements

See Analyzing Quality of Requirements in activity Determining Requirements.

6.3.7.1.8 Specifying Scope of Delivery and Acceptance Criteria

See Specifying Scope of Delivery and Acceptance Criteria in activity Determining Requirements.