SD 2.4: Allocation of User Requirements



		SD 2.4: Allocation of User Requirements

SE2.4 - Anwenderforderungen zuordnen

Contents
Product Flow
Handling
Roles

Methods
Tools Requirements
External Norms

Contents		Product Flow Handling Roles		Methods Tools Requirements External Norms

Product Flow

From		Product		to		Methods	Tool Req.	Ext. Norms
Activity	State	Chapter	Title	Activity	State	Methods	Tool Req.	Ext. Norms
SD1	accepted	Existing	User Requirements	-	-			/ISO IEC 12207/ Devlp. Proc.: Sys. Arch. Design
SD2.1	being proc.	Existing	System Architecture	-	-
-	-	2.1.3	System Architecture. Requirements Allocation	SD1 ⁽¹⁾ SD2.5 SD2.6 SD3 SD4-SW PM4 PM5	submitted	ER ⁽²⁾	SSD01 SSD09

+ "Chapter" are extra columns from the original printed version of GD 250

* Allocation of User Requirements

In this activity, the total User Requirements and Marginal Conditions for the System have to be allocated to the elements of the technical architecture.

This allocation of requirements is the basis for the requirements analyses and design steps taking place on the lower levels.

It is necessary to observe that the allocation of requirements and Marginal Conditions to the elements of the technical architecture must fulfill the following criteria:

Every requirement must be allocated to at least one element of the technical architecture, ideally exactly to one architecture element.

Each requirement is allocated to the lowest element in the refinement levels which makes it possible to meet the requirement completely. Normally, the total of the requirements have to be allocated to various refinement levels.

Provided that a requirement is of general importance to elements, it must be considered within the scope of the allocation which individual architecture elements this requirement really has to fulfill.

The allocation must be realized in such a manner that it will be possible to prove the fulfillment of the requirement by checking the corresponding architecture element.

* Allocation of IT Security Requirements to the IT Security Measures

With the allocation of the IT security requirements to the IT security measures it must be proven that each IT security requirement is covered by at least one IT security measure, and if the specified IT security objective can be reached with the selected security measures.

Roles

Role	Participation
System Designer	responsible

Methods

Product Methods Allocation Use
Chapter 2.1.3
System Architecture.
Requirements Allocation ER - E/R Modeling ⁽²⁾ Generate

Product	Methods Allocation	Use
Chapter 2.1.3 System Architecture. Requirements Allocation	ER - E/R Modeling ⁽²⁾	Generate

Tools Requirements

Product	Functional Tools Requirements
Chapter 2.1.3 System Architecture. Requirements Allocation	SSD01 - Recording Requirements SSD09 - Supporting Information Structuring

External Norms

Norm	Process	Chapter	Obs.
/ISO IEC 12207/	Development Process	System Architectural Design	(s. Part 3 - ISO 3.2.1)

Notes:

(1) In case a requirements controlling is to be realized on the basis of an actual architecture proposal.

(2) Method ER is to be applied for Information Systems and only if modifications of the E/R models become necessary.

GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster