QA3CFICSE99

1
QA3 CFICSE 99

• Terry Shepard
• October 1999

2
Sample Software Quality Standard
3
Standard for Software Engineering of Safety
Critical Software

• Issued by Ontario Hydro at the end of 1990 for a
  trial period of 1 year.
• Issued as CE-1001-STD Rev. 1 in January 1995
• Paper by Mike Viola SAFECOMP 9X?

4
Scope of Standard

• Specifies requirements for the engineering
  characteristics of safety critical software for
  nuclear generating stations.
• Not for all types of applications.
• Purpose is to provide confidence that the safety
  critical software product is developed with an
  acceptable level of quality

5
Structure of Standard (Slide 1)

• covers
• requirements definition and verification
• software design and verification,
• code implementation,
• verification and testing,
• planning,
• configuration management and training.

6
Structure of Standard (Slide 2)

• Minimum set of software engineering tasks
• Minimum set of outputs for each task
• Quality of outputs for each task must meet
  defined quality objectives, quality attributes
  and fundamental principles.
• To be acceptable, a software product must meet
  all these requirements.

7
3 categories of tasks

• development,
• verification
• support.

8
Software Engineering Development Tasks, Outputs
and Sample Requirements.

• Next slide

9

10
Software Engineering Verification Tasks, Outputs
and Sample Requirements.

• Next 3 slides

11
(No Transcript)
12
(No Transcript)
13
(No Transcript)
14
Software Engineering Support Tasks, Outputs and
Sample Requirements.

• Next 2 slides

15

16
(No Transcript)
17
Quality Objectives

• Functionality
• Maintainability
• Reliability
• Reviewability and
• Safety.
• These quality objectives are supported by a set
  of quality attributes.

18
Quality Attributes

• Completeness
• Consistency
• Correctness
• Modifiability
• Modularity
• Predictability
• Robustness
• Structuredness
• Traceability
• Understandability and
• Verifiability.

19
Fundamental Principles

• Set of high level guidelines on which the
  software engineering principles in this standard
  are based.
• Measures of the presence or the degree of
  adherence to a quality attribute are derived from
  the fundamental principles
• When measures are satisfied, the quality
  objectives are met and the product is fit for
  use.

20
(No Transcript)
21
Need measures Many measures are subjective out
of necessity.