Improving software robustness with dependability cases

Programs fail mainly for two reasons: logic errors in the code, and exception failures. Exception failures can account for up to 2/3 of system crashes, hence are worthy of serious attention. Traditional approaches to reducing exception failures, such as code reviews, wallthroughs and formal testing, while very useful, are limited in their ability to address a core problem: the programmer's inadequate coverage of exceptional conditions. The problem of coverage might be rooted in cognitive factors that impede the mental generation (or recollection) of exception cases that would pertain in a particular situation, resulting in insufficient software robustness. This paper describes a study to test the hypothesis that robustness for exception failures can be improved through the use of dependability cases. Dependability cases, derived from safety cases, comprise a methodology based on structured taxonomies and memory aids for helping software designer think about and improve exception-handling coverage. A controlled experiment conducted with 59 subjects revealed a statistically significant 43% increase in exception-handling robustness. An ancillary experiment conducted with 38 subjects provides convergent evidence that the effect is authentic, and not due to programming expertise alone.

[1]  W.N. Toy,et al.  Fault-tolerant design of local ESS processors , 1978, Proceedings of the IEEE.

[2]  Marilyn W. Bush,et al.  Improving software quality: the use of formal inspections at the Jet Propulsion Laboratory , 1990, [1990] Proceedings. 12th International Conference on Software Engineering.

[3]  Edward Kit,et al.  Software testing in the real world - improving the process , 1995 .

[4]  Wayne A. Wickelgren,et al.  Learning and memory , 1978 .

[5]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[6]  Robert S. Swarz,et al.  The theory and practice of reliable system design , 1982 .

[7]  Flaviu Cristian,et al.  Exception Handling and Tolerance of Software Faults , 1995 .

[8]  Nancy Pennington,et al.  Chapter 6 The Structure of Memory Performance in Experts: Implications for Memory in Everyday Life , 1993 .

[9]  T. Griffin Semiology of graphics: diagrams, networks, maps. Bertin, Jacques (trans. W. j. Berg). The University of Wisconsin Press, Madison, 1983. 416 pages. ISBN 0 299 09060 4. US$75.00, cloth. , 1987 .

[10]  D. Spalding The Principles of Psychology , 1873, Nature.

[11]  Nancy G. Leveson,et al.  Safeware: System Safety and Computers , 1995 .

[12]  J. Shaoul Human Error , 1973, Nature.

[13]  V. Rich Personal communication , 1989, Nature.

[14]  W E Vesely,et al.  Fault Tree Handbook , 1987 .

[15]  Roger Shaw Safety and Reliability of Software Based Systems , 1997, Springer London.

[16]  Roger Shaw,et al.  Safety Cases — How Did We Get Here? , 1997 .

[17]  Joseph G. Voelkel,et al.  Guide to Quality Control , 1982 .

[18]  Marilyn W. Bush Improving software quality: the use of formal inspections at the JPL , 1990, ICSE '90.

[19]  Peter G. Bishop,et al.  The SHIP Safety Case Approach , 1995, SAFECOMP.