Risk-driven software reliability and testing

Norm Schneidewind, Mike Hinchey

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

Classical methods of accepting or rejecting products, which are not generally known by the software reliability community, are used as a baseline for developing test criteria. Testing criteria are designed to estimate the number of tests, and associated fault removal, that would result in reduced risk and increased reliability to the point where the software can be deployed. For the purpose of experimenting with test criteria, which are based on relationships between the producer and the consumer of software, we developed a template for test scenarios, using hypothetical distributions of faults and failures. The template was applied to a release of the Shuttle flight software to determine whether hypothetical and real-world results would be consistent. This was not the case; hence, we recommend that practitioners experiment with more than one test criterion to reduce the risk of deploying their software.

Original languageEnglish
Title of host publicationProceedings - The 2nd IEEE International Conference on Secure System Integration and Reliability Improvement, SSIRI 2008
Pages183-184
Number of pages2
DOIs
Publication statusPublished - 2008
Externally publishedYes
Event2nd IEEE International Conference on Secure System Integration and Reliability Improvement, SSIRI 2008 - Yokohama, Japan
Duration: 14 Jul 200817 Jul 2008

Publication series

NameProceedings - The 2nd IEEE International Conference on Secure System Integration and Reliability Improvement, SSIRI 2008

Conference

Conference2nd IEEE International Conference on Secure System Integration and Reliability Improvement, SSIRI 2008
Country/TerritoryJapan
CityYokohama
Period14/07/0817/07/08

Keywords

  • Software reliability
  • Software risk
  • Test criteria

Fingerprint

Dive into the research topics of 'Risk-driven software reliability and testing'. Together they form a unique fingerprint.

Cite this