Image de couverture de Achieving Quality Software Including Its Application to Safety-Related Systems
Achieving Quality Software Including Its Application to Safety-Related Systems
Titre:
Achieving Quality Software Including Its Application to Safety-Related Systems
ISBN (Numéro international normalisé des livres):
9789401105491
Auteur personnel:
Edition:
3rd ed. 1995.
PRODUCTION_INFO:
Dordrecht : Springer Netherlands : Imprint: Springer, 1995.
Description physique:
XIII, 287 p. online resource.
Table des matières:
One The Background to Software Engineering and Quality -- 1 The meaning of quality in software -- 2 Software failures and the life cycle -- 3 Integrity and the safety life cycle -- Two Guidance, Legislation and Liability -- 4 Legislation and liability -- 5 Current standards and guidelines -- 6 Certification and competence -- Three Achieving Software Quality -- 7 The traditional approach -- 8 Formal methods in requirements -- 9 Formal methods in design -- 10 Review and test -- 11 Static analysis -- 12 Languages and processors -- 13 Achieving fault tolerance in design -- Four Management Issues -- 14 Software management issues -- 15 Metrics and modelling -- Five Case Study -- 16 Software system design exercise - addressable detection system -- Appendix 1 Checklists -- Appendix 2 Glossary of terms and abbreviations -- Appendix 3 Bibliography and references.
Extrait:
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.
Auteur collectif ajouté:
Langue:
Anglais