SD 3: SW/HW Requirements Analysis



		SD 3: SW/HW Requirements Analysis

SE3 - SW-/HW-Anforderungsanalyse

Contents
Product Flow
Handling
Roles
Sub-activities

Tools Requirements
External Norms
Links to the V-Model Mailinglist

Contents		Product Flow Handling Roles Sub-activities		Tools Requirements External Norms Links to the V-Model Mailinglist

Product Flow

From		Product		to		Methods	Tool Req.	Ext. Norms
Activity	State	Chapter	Title	Activity	State	Methods	Tool Req.	Ext. Norms
SD1	accepted	All	User Requirements	-	-
SD2	accepted	All	System Architecture	-	-
SD2	being proc.	Existing	Interface Description	-	-
SD2	being proc.	Existing	Operational Information: User Manual Diagnosis Manual Operator Manual Other Application Information	SD4-SW SD4-HW	being proc.
SD2	being proc.	Existing	Technical Requirements	SD4-SW SD4-HW SD5-SW	submitted	COM ⁽²⁾ CFM ⁽¹⁾ CRC ⁽²⁾ DFM DIAL ⁽⁴⁾ DTAB ⁽⁸⁾ ELH ⁽⁷⁾ ER ⁽⁶⁾ FCTD FNET ⁽⁵⁾ IAM ⁽²⁾ SBM/ ⁽⁵⁾ STM ⁽⁹⁾ STMO ⁽³⁾

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

Handling

Figure 4.4: SD3 - SW/HW Requirements Analysis

Within the scope of activity SD3 - SW/HW Requirements Analysis, the Technical Requirements and the Operational Information (User Manual, Diagnosis Manual, Operator Manual, Other Application Information) are upgraded with regard to one Software Unit or one HW Unit. The User Requirements, the System Architecture and the previously derived Technical Requirements are the starting point of this activity. On this basis the general requirements, the requirements for interfaces, functionality, quality characteristics, SW development environment and SWMM environment have to be analyzed and defined.

The Operational Information generated on system level must be completed by SW/HW-related information. Based on the Technical Requirements all information must be obtained that are required for the user documentation.

Roles

Role	Participation
SD Supervisor	cooperating (SD3.5)
System Designer	responsible (SD3.1, SD3.2, SD3.3, SD3.4, SD3.5)
Technical Author	cooperating (SD3.5)

Sub-activities

SD3.1 - Definition of General Requirements from SW/HW Unit Point of View
SD3.2 - Specification of Requirements for External Interfaces of SW/HW Unit
SD3.3 - Definition of Requirements for the Functionality
SD3.4 - Definition of Requirements for the Quality of the SW/HS Unit
SD3.5 - Definition of Requirements for the Development and SWMM Environment

Tools Requirements

Being defined

External Norms

Being defined

Links to the V-Model Mailinglist

Mail 0637 - Re: Prüf-Grundsatz (637)
Mail 0524 - Mehrere Fragen zum V-Modell (524)
Mail 0178 - Re: Technische Anforderungen (178)

Notes:

(1) Method CFM is to be applied for event-driven systems in case it is required for the representation of the control flow based on a high complexity.

(2) The methods have to be applied in object-oriented developments.

(3) Method STMO is to be applied for the dynamic system modeling in object-oriented procedures.

(4) Method DIAL is to be applied for dialogue functions with screen masks.

(5) Method SBM is to be applied for realtime applications or respectively distributed systems with a high level of criticality. Method FNET is to be applied for information systems.

(6) Method ER is to be applied for information systems.

(7) Method ELH is to be applied for information systems.

(8) Method DTAB is to be applied for the description of complex facts and circumstances.

(9) Method STM is to be applied if complex situations have to be considered during the run of the function or the process.

This page online • GDPA Online • Last Updated 07.Feb.2003 by C. Freericks