a Review of Current Practices, Standards and Guidelines including New Methods and Development Tools
First Statement of Responsibility
by David J. Smith, Kenneth B. Wood.
EDITION STATEMENT
Edition Statement
Second edition
.PUBLICATION, DISTRIBUTION, ETC
Place of Publication, Distribution, etc.
Dordrecht
Name of Publisher, Distributor, etc.
Springer Netherlands
Date of Publication, Distribution, etc.
1989
PHYSICAL DESCRIPTION
Specific Material Designation and Extent of Item
1 ressource en ligne (XVIII, 284 pages)
CONTENTS NOTE
Text of Note
1. The Background to Software Engineering and Quality --; 1 The Meaning of Quality in Software --; 2 Software Failures--Causes and Hazards --; 3 The Effect of the Software Life-cycle on Quality --; 2. Current Quality Systems and Software Standards --; 4 The Traditional Approach to Software Quality --; 5 Current Standards and Guidelines --; 3. Software Quality Engineering--an Ideal Approach --; 6 An Engineering Approach to Defining Requirements --; 7 Putting Design into an Engineering Context --; 8 A Structured Approach to Static and Dynamic Testing --; 9 Languages and Their Importance --; 10 Aspects of Fault Tolerance in Software Design --; 4. New Management For Software Design --; 11 Software Project Management --; 12 Quality--can it be Measured? --; 13 The Role of the Software Engineer --; 5. Exercise --; 14 Software System Design Exercise--Addressable Detection System --; Checklist Application Chart --; Glossary of Terms --; A Terms Connected with Failure --; B Terms Connected with Software --; C Terms Connected with Software Systems and their Hardware --; D Terms Connected with Procedures, Management and Documents --; E Terms Connected with Test --; F Common Abbreviations --; 1 British Standards --; 2 UK Defence Standards --; 3 US Standards --; 4 Other Standards and Guidelines --; 5 Books.
SUMMARY OR ABSTRACT
Text of Note
During the 18 months since the publication of the 1st edition the practice of software quality and the availability of tools and guidance for its implementation has increased dramatically. The emphasis on the need for formal methods has increased and calls for certification of safety critical software are now common. In particular this 2nd edition: -Expands the treatment of static analysis and includes a comƯ prehensive but simple example in order to illustrate clearly the functions of each analyser in Chapter 8.-Describes formal requirements languages more fully in Chapter 6.-Updates the compendium of available guidelines and standards in Chapter 5.-Expands the description of the many high level languages in Chapter 9.-Improves and expands the exercise into a 49 page case study consisting of a documentation hierarchy for a safety system in Chapter 14. It is seeded with deliberate errors and ambiguities and now includes guidance in finding them.