Skip to main content

Testing Safety-Related Software

A Practical Handbook

  • Book
  • © 1999

Overview

  • Covers most up-to-date standards including the relevant IEEE and IEC standards Presents clear structured guidelines on leading test practices Shows how proper testing can result in acceptable safety integrity levels Based on the experiences of nine partners from fields as diverse as oil and gas production, transportation, aerospace, nuclear power, and defense Discusses timing analysis and simulation (which lack coverage in general)

  • No other books currently offer a similar survey of testing techniques for practitioners

This is a preview of subscription content, log in via an institution to check access.

Access this book

eBook USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Other ways to access

Licence this eBook for your library

Institutional subscriptions

Table of contents (9 chapters)

Keywords

About this book

As software is very complex, we can only test a limited range of the possible states of the software in a reasonable time frame. In 1972, Dijkstra [1] claimed that 'program testing can be used to show the pres­ ence of bugs, but never their absence' to persuade us that a testing approach alone is not acceptable. This frequently quoted statement represented our knowledge about software testing at that time, and after over 25 years intensive practice, experiment and research, although software testing has been developed into a validation and ver­ ification technique indispensable to software engineering discipline, Dijkstra's state­ ment is still valid. To gain confidence in the safety of software based systems we must therefore assess both the product and the process of its development. Testing is one of the main ways of assessing the product, but it must be seen, together with process assessment, in the context of an overall safety case. This book provides guidance on how to make best use of the limited resources available for testing and to maximise the contribution that testing of the product makes to the safety case. 1.1 Context The safety assurance of software based systems is a complex task as most fail­ ures stem from design errors committed by humans. To provide safety assur­ on the integrity of the system and put ance, evidence needs to be gathered forward as an argued case (the safety case) that the system is adequately safe.

Editors and Affiliations

  • George House, Glasgow, UK

    Stewart N. Gardiner

Bibliographic Information

Publish with us