SD 5-SW: Detailed SW Design



		SD 5-SW: Detailed SW Design

SD5-SW - SW-Feinentwurf

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	-	-
SD3	accepted	All	Technical Requirements	-	-
SD4-SW	accepted	All	Software Architecture	-	-
SD4-SW	accepted	All	Interface Overview	-	-
SD4-SW	accepted	All	Interface Description	-	-
CM4.1	being proc.	Existing	Data-Dictionary	CM4 SD6-SW	being proc./ submitted	ACC ⁽¹⁾ DVER ⁽⁴⁾ FS ⁽⁵⁾
-	-	All	SW Design (Module) SW Design (Database)	SD6-SW	submitted	ACC ⁽¹⁾ COM ⁽²⁾ CRC ⁽²⁾ DNAV ⁽⁴⁾ DVER ⁽⁴⁾ FS ⁽⁵⁾ IAM ⁽²⁾ LOGM MODIAG ⁽²⁾ NORM PCODE SIMU ⁽⁷⁾ STMO ⁽³⁾
SD4-SW	being proc.	Existing	Operational Information: User Manual Diagnosis Manual Operator Manual Other Application Information	SD8	being proc.

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

Handling

Figure 4.6: SD5 - Detailed SW Design

Software Architecture and Interface Description are the basis for this activity. Here all information is kept that will be required to utilize the performance of a SW Module. The specifications and details for the realization of each SW Module, each SW Component and each Database must be defined. This is needed for the subsequent definition of resources and time requirements of the individual architecture elements and the entire SW Unit that must meet the expected requirements.

Furthermore, the Operational Information (User Manual, Diagnosis Manual, Operator Manual, Other Application Information) has to be updated with design-related details.

Roles

Role	Participation
SW Developer	responsible (SD5.1-SW, SD5.2-SW)
Technical Author	cooperating ( SD5.1-SW)

Sub-activities

SD5.1 - Description of SW Component/Module/Database,
SD5.2 - Analysis of Resources and Time Requirements

Tools Requirements

Being defined

External Norms

Being defined

Links to the V-Model Mailinglist

Mail 0524 - Mehrere Fragen zum V-Modell (524)
Mail 0256 - Re: Midestanforderungen (256)
Mail 0134 - V-Modell 97 (134)

Notes:

(1) Method ACC must be applied according to [ITSEC].

(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) A formal specification on two different abstraction levels is required for the application of DVER. Because of the great effort, the most critical portions of a specification have to be selected for which the DVER has to be applied. According to [ITSEC], method DVER is required for the proof of the formal security model with the evaluation level E4, for the proof of consistency between security model and preliminary design DVER is required with the evaluation level E6.

(5) Method FS is to be applied in case of special requirements to correctness, e. g. based on very high criticality. According to [ITSEC], FS is required for the description of the formal security model with the evaluation level E4, for the preliminary design FS is required with the evaluation level E6.

(6) Method DNAV is to be applied for hierarchical or network-like database types.

(7) Method SIMU is to be applied if reliability requirements are high nd the use conditions are so complex that static investigations with regard to feasibility and resource requirements are not sufficient.

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