![]() |
![]() |
![]() |
|
![]() |
|||
| SD 8.2: Self-Assessment of the System |
SE8.2 - Selbstprüfung des Systems durchführen
Contents
|
|
|
|---|
Product Flow
| From | Product | to | Methods | Tool Req. | Ext. Norms | |||
|---|---|---|---|---|---|---|---|---|
| Activity | State | Chapter | Title | Activity | State | |||
| SD8.1 | being proc. | Existing |
System |
SD8.3 | submitted | |||
+ "Chapter" are extra columns from the original printed version of GD 250
Handling
For that, the assessment prerequisites like installation of the System 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 further procedure.
Provided that the assessment has been finished successfully in the opinion of SD, the System 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 System.
Recommendation
The real application environment can be simulated.
When self-assessing a System 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, the Assessment Specification, and the Assessment Procedure ought to be adhered to.
Roles
| Role | Participation | ||||
|---|---|---|---|---|---|
| System Designer | responsible
| SW Developer |
cooperating
| HW Developer |
cooperating
| |
Tools Requirements
External Norms
![]() |
![]() |
GDPA Online
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster
![]() |