SD 8.2: Self-Assessment of the System
SE8.2 - Selbstprüfung des Systems durchführen
+ "Chapter" are extra columns from the original printed version of GD 250
Self-assessments of the System and possibly of the Segments have to be carried out. In this activity, the SW Units on the defined target hardware have to be assessed.
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.
The self-assessment of Segments (or the System, after a segment level is omitted) should include:
The self-assessment of the System should include:
- assessment against the Technical Requirements with regard to the quality characteristics defined there
- assessment of the technical and functional cooperation, in particular of the SW/HW interfaces
- assessment of the Segment on the target hardware under conditions which closely resemble real ones, by simulation of the system environment and with the support of SW/HW diagnostic tools
- assessment with regard to
- interrupt and I/O signal processing
- synchronization and communication of processors
- error detection and tolerance
- assessment of the man-machine interface if it meets ergonomical and software-ergonomical principles
- assessment against the User Requirements and the System Architecture
- at first, assessment in special assessment environment (e. g. prototype, test rig); then the following system assessment must take place in the operative application environment or on a compatible reference system.
- assessment of the technical and functional cooperation, with special attention to
- system loading with regard to efficiency and robustness
- behavior under worst-case conditions
- demonstration of system security
- typical situations and conditions
- critical situations and functions
- assessment of the cooperation of System/Segment and user with regard to
- user loading
- typical situations and how they are handled
- critical situations and the effects of false operation
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.
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster