Detailansicht

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.

Inhaltsangabe1. The Background to Software Engineering and Quality.- 1 The Meaning of Quality in Software.- 1.1 Quality-What is it?.- 1.2 Quality-The Elusive Element.- 1.3 The Software Process-Craft or Science?.- 1.4 Blending Engineering Discipline and Software Design.- 1.5 The Conflict between Quality and Time.- 1.6 The Decline of Hardware and the Rise of Software.- 2 Software Failures-Causes and Hazards.- 2.1 Advantages and Disadvantages of Programmable Systems.- 2.2 Software-related Failures-Fault, Error, Failure.- 2.3 Causes of Faults.- 2.4 Safety Critical Software.- 2.5 Quantifying Software Reliability.- 3 The Effect of the Software Life-cycle on Quality.- 3.1 The Meaning of 'Life-Cycle'.- 3.2 Achieving Quality Software.- 3.3 Current Practice.- 3.4 Quality Control and Quality Assurance.- 2. Current Quality Systems and Software Standards.- 4 The Traditional Approach to Software Quality.- 4.1 Quality Systems.- 4.2 Quality Organisation, Management and Review.- 4.3 Design Documentation.- 4.4 Configuration Management and Change Control.- 4.5 Programming Standards.- 4.5.1 General Rules.- 4.5.2 Structured Programming.- 4.5.3 Describing the Modules.- 4.6 Design Reviews.- 4.7 Test and Integration.- 4.8 Subcontracted and Bought-in Software.- 4.8.1 Shelf versus Custom Software.- 4.8.2 Vendor Appraisal.- 4.8.3 Field Experience and History.- 4.9 Audit.- Checklists.- 5 Current Standards and Guidelines.- 5.1 The Need for Standards.- 5.2 How Standards Evolve.- 5.3 A Summary of Current Quality Systems.- 5.3.1 UK Defence Standard 05-21.- 5.3.2 British Standard 5750 (1987).- 5.3.3 NATO Standards-AQAP Series.- 5.3.4 UK Defence Standard 00-16.- 5.3.5 UK Defence Standard 00-55.- 5.3.6 ISO 9001 (1987).- 5.4 Current Software Standards and Guidelines.- 5.4.1 HSE Document: Programmable Electronic Systems in Safety Related Applications (UK).- 5.4.2 IEE: Guidelines for the Documentation of Software in Industrial Computer Systems (UK).- 5.4.3 EEA: Guide to the Quality Assurance of Software (UK).- 5.4.4 EEA: Establishing a Quality Assurance Function for Software (UK).- 5.4.5 EEA: Software Configuration Management (UK).- 5.4.6 EEA: A Guide to the Successful Start-Up of a Software Project (UK).- 5.4.7 Ministry of Defence MASCOT (UK).- 5.4.8 Ministry of Defence JSP188: Requirements for the Documentation of Software in Military Operational Real-Time Computer Systems (UK).- 5.4.9 IEEE: Software Engineering Standards (USA).- 5.4.10 ElektronikCentralen: Standards and Regulations for Software Approval and Certification (Denmark).- 5.4.11 Guidelines for the Nordic Factory Inspectorates.- 5.4.12 TUV handbook: Microcomputer in der Sicherheitstechnik (Germany).- 5.4.13 EWICS TC7 Documents.- 5.4.14 CEC Collaborative Project.- 5.4.15 US Department of Defense Standard 2167: Defense System for Software Development.- 5.4.16 IECCA: Guide to the Management of Software-Based Systems for Defence, 3rd Edition.- 5.4.17 I Gas E: SR15, The Use of Programmable Electronic Systems in Safety Related Applications in the Gas Industry.- 5.4.18 EEMUA: Safety Related Programmable Electronic Systems.- 5.4.19 STARTS: The STARTS Guide.- 5.4.20 Some Other Documents.- 5.5 Systems for the Future.- 5.5.1 Paperless Design.- 3. Software Quality Engineering-an Ideal Approach.- 6 An Engineering Approach to Defining Requirements.- 6.1 Engineer versus Programmer.- 6.2 A New Look at the Life-Cycle.- 6.3 Current State of the Art.- 6.4 Formal versus Free Expression.- 6.5 Expressing Requirements-Specification Techniques.- 6.6 Available Specification Languages and Design Methodologies.- 6.6.1 IORL (Input/Output Requirements Language).- 6.6.2 CORE (COntrolled Requirements Expression).- 6.6.3 VDM (Vienna Development Methodology).- 6.6.4 Z.- 6.6.5 OBJ.- 6.6.6 SREM (Software Requirements Engineering Methodology).- 6.6.7 MASCOT (Modular Approach to Software Construction, Operation and Test).- 6.6.8 SSADM (Structured Systems Analysis and Design Methodology).- 6.6.9 JSD (Jackson System Development).- 6.6.10 SADT (Structu