SD 6.3-SW: Self-Assessment of the SW Module/Database



		SD 6.3-SW: Self-Assessment of the SW Module/Database

SE6.3-SW - Selbstprüfung des SW-Moduls/der Datenbank durchf.

Contents
Product Flow
Handling
Recommendation
Roles

Methods
Tools Requirements
External Norms
Links to the V-Model Mailinglist

Contents		Product Flow Handling Recommendation Roles		Methods 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
SD5-SW	accepted	All	SW Design (Module) SW Design (Database)	-	-			/ISO IEC 12207/ Devlp. Proc.: SW Coding and Testing
SD6.1-SW	being proc.	All	Implementation Document: SW Modules	SD7-SW	submitted		SSD17 SSD30 SSD31
SD6.1-SW	being proc.	-	SW Modules			ACC ⁽¹⁾ PVER ⁽²⁾	SSD17 SSD30 SSD31 SQA12
SD6.2-SW	being proc.	All	Implementation Document: Database				SSD17 SSD30 SSD31
SD6.2-SW	being proc.	-	Database			ACC ⁽¹⁾ PVER ⁽²⁾	SSD17 SSD30 SSD31

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

The developer must carry out self-assessment of that SW Module or Database which is realized by himself. For that, the assessment prerequisites like installation of object to be assessed within the assessment environment and generation of the required test cases must be created first. After the self-assessment, the results will be evaluated, which determines the future course of the development. Provided that the assessment has been finished successfully in the opinion of SD, the object to be assessed is passed on to QA to be formally assessed; otherwise iterations of SD activities will be required which have to be completed with a renewed self-assessment of the product.

Recommendation

When self-assessing a SW Module or a Database in the case of high criticality, the same rules should be applied as in the subsequent formal QA assessment; i. e. the rules in the Assessment Plan, in the Assessment Specification, and in the Assessment Procedure ought to be adhered to.

Roles

Role	Participation
SW Developer	responsible

Methods

Product	Methods Allocation	Use
Database	ACC - Analysis of Covert Channels ⁽¹⁾	Generate
Database	PVER - Program Verification ⁽²⁾	Generate
SW Modules	ACC - Analysis of Covert Channels ⁽¹⁾	Generate
SW Modules	PVER - Program Verification ⁽²⁾	Generate

Tools Requirements

Product	Functional Tools Requirements
Implementation Document: SW Modules	SSD17 - Debugging SSD30 - Formal Verification SSD31 - Analysis of Covert Channels
SW Modules	SSD17 - Debugging SSD30 - Formal Verification SSD31 - Analysis of Covert Channels SQA12 - Static Assessment of Code
Implementation Document: Database	SSD17 - Debugging SSD30 - Formal Verification SSD31 - Analysis of Covert Channels
Database	SSD17 - Debugging SSD30 - Formal Verification SSD31 - Analysis of Covert Channels

External Norms

Norm	Process	Chapter	Obs.
/ISO IEC 12207/	Development Process	Software Coding and Testing	(s. Part 3 - ISO 3.2.1)

Notes:

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

(2) Method PVER is to be applied in cases of special requirements to the correctness. A formal specification and a program that shall meet the specification are required for the application of PVER. Because of the great effort, the most critical program portions have to be selected for an application of PVER.

Links to the V-Model Mailinglist

Mail 0278 - Re: Organisationseinheiten im QS-Plan / Pruefplan (278)

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