Ebook: Achieving Quality Software: Including Its Application to Safety-Related Systems
- Tags: Mechanical Engineering, Software Engineering/Programming and Operating Systems
- Year: 1995
- Publisher: Springer Netherlands
- Edition: 3
- Language: English
- pdf
The rapid growth in use of programmable technology, in nearly all sectors of Engineering, is a well-known established trend and one which there is every reason to believe will continue into the foreseeable future. The drivers of this trend include cost, flexibility, rich functionality and certain reliability and safety advantages. However, as explained in this book, these advantages have to be carefully weighed against a number of dis advantages which, amongst other things, have fundamental implications for reliability and safety. Ideally, a programmable system would be viewed as a fusion of hardware, software and user (or 'skinware'), operating under a set of environmental conditions. To date, such a unifying model does not exist and so hardware, software and human factors are still considered largely as three separate disciplines, albeit with certain interdependencies. Established techniques are available which enable the engineer to develop systems comprising purely hardware components to a prescribed reliability and performance. Software, however, is fundamentally different in a number of ways, and does not lend itself to equivalent analysis. A major problem with software is its poor 'visibility', and consequently the great difficulty in understanding and predicting its behaviour in all cir cumstances. This results in the ever-present software design flaws, or 'bugs', which have plagued the software industry from its beginnings.
Content:
Front Matter....Pages i-xiii
Front Matter....Pages 1-1
The meaning of quality in software....Pages 3-8
Software failures and the life cycle....Pages 9-18
Integrity and the safety life cycle....Pages 19-25
Front Matter....Pages 27-27
Legislation and liability....Pages 29-37
Current standards and guidelines....Pages 38-58
Certification and competence....Pages 59-65
Front Matter....Pages 67-67
The traditional approach....Pages 69-89
Formal methods in requirements....Pages 90-102
Formal methods in design....Pages 103-111
Review and test....Pages 112-122
Static analysis....Pages 123-144
Languages and processors....Pages 145-163
Achieving fault tolerance in design....Pages 164-176
Front Matter....Pages 177-177
Software management issues....Pages 179-191
Metrics and modelling....Pages 192-205
Front Matter....Pages 207-207
Software system design exercise — addressable detection system....Pages 209-255
Back Matter....Pages 257-287
Content:
Front Matter....Pages i-xiii
Front Matter....Pages 1-1
The meaning of quality in software....Pages 3-8
Software failures and the life cycle....Pages 9-18
Integrity and the safety life cycle....Pages 19-25
Front Matter....Pages 27-27
Legislation and liability....Pages 29-37
Current standards and guidelines....Pages 38-58
Certification and competence....Pages 59-65
Front Matter....Pages 67-67
The traditional approach....Pages 69-89
Formal methods in requirements....Pages 90-102
Formal methods in design....Pages 103-111
Review and test....Pages 112-122
Static analysis....Pages 123-144
Languages and processors....Pages 145-163
Achieving fault tolerance in design....Pages 164-176
Front Matter....Pages 177-177
Software management issues....Pages 179-191
Metrics and modelling....Pages 192-205
Front Matter....Pages 207-207
Software system design exercise — addressable detection system....Pages 209-255
Back Matter....Pages 257-287
....