Software Fault Tolerance Forestalls Crashes: To Err Is Human; To Forgive Is Fault Tolerant

Advances in Computers

Volumn 58, Issue C, 2003, Pages 239-286

  Bernstein, Lawrence ^a  

^a STEVENS INSTITUTE OF TECHNOLOGY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 77956777781     PISSN: 00652458     EISSN: None     Source Type: Book Series    
DOI: 10.1016/S0065-2458(03)58006-8     Document Type: Review

References (34)

1. AT&T Bell Laboratories. Programming languages. A History of Engineering and Science in the Bell System VII (1984) 379-380
2. Baratloo A., Singh N., and Tsai T. Transparent run-time defense against stack smashing attacks. Proceedings of 2000 USENIX Annual Technical Conference, San Diego, CA (2000) 18-23
3. BEA White Paper. Managing complexity with application infrastructure. BEA Systems, San Jose, CA. http://www.bea.com
4. Bernstein L. Software investment strategy. Bell Labs Technical Journal 2 3 (1997) 233-243
5. Bernstein L., and Yuhas C.M. Testing network management software. Journal of Network and Systems Management 1 1 (1993) 5-15
6. Beugnard A. Making components contract aware. Computer 12 7 (1999) 38-45
7. Boehm B., et al., Software estimation with COCOMO II, PTR
8. Carreira J., et al. Fault tolerance for Windows applications. Byte Magazine (February 1997) 51-52
9. http://www.cigitallabs.com/resources/definitions/software_safety.html
10. Fowler M. Refactoring-Improving the Design of Existing Code (2000), Addison-Wesley p. xvi
11. Friedman T.L. The Hackers' lessons. The New York Times 15 (2000) A27
12. Gaud S. Object stamp of approval. ComputerWorld 31 11 (1997) 1
13. Goma H. Reusable software requirements and architecture for families of systems. Journal of Systems & Software 28 3 (1995) 189-202
14. Hatton L. Safer C: Developing Software for High-Integrity and Safety-Critical Systems. The McGraw-Hill International Series in Software Engineering (1997)
15. Huang Y., and Kintala C.M.R. Software implemented fault tolerance: technologies and experience. In: Lyu M. (Ed). Proceedings of 23rd Internat. Symposium on Fault-Tolerant Computing, Toulouse, France, June 1993, Software Fault Tolerance (1995), John Wiley & Sons 2-9
16. In: Krishnamurthy B. (Ed). Practical Reusable UNIX Software (1995), John Wiley & Sons, New York 5-8
17. Leveson N.G. Safeware-System Safety and Computers (1995), Addison-Wesley p. 436
18. Lim W.C. Effects of reuse on quality, productivity and economics. IEEE Software (1994) 23-29
19. Lyu M., Handbook of Software Fault Tolerance, chapter 2
20. Lyu M.R. Software Fault Tolerance (1995), John Wiley and Sons, Chichester
21. March S. Learning from Pathfinder's bumpy start. Software Testing & Quality Engineering 1 5 (1999) 10-12
22. Marciniak J.J. Encyclopedia of Software Engineering (2002), John Wiley and Sons pp. 526-546
23. Musa J., Iannino A., and Okumoto K. Software Reliability: Measurement, Prediction, Application (1987), McGraw-Hill Appendix E
24. National Research Council. Information Systems Trustworthiness Interim Report (1997), National Academy Press, Washington, DC pp. 18-29
25. Neuman P.G. Computer Related Risks (1995), Addison-Wesley pp. 20-21
26. Software manufacturing. UNIX Review 7 (1989) 38-45
27. Selby R. Empirically analyzing software reuse in a production environment. In: Tracz W. (Ed). Software Reuse: Emerging Technology (1988), IEEE Computer Society Press 176-189
28. Sha L. Using simplicity to control complexity. IEEE Software 18 4 (2001) 27
29. Siweiorek D., and Swarz R. The Theory and Practice of Reliable System Design (1982), Digital Press, Bedford, MA p. 7
30. Stoyen A.D. Fighting complexity in computer systems. Computer 30 8 (1997) 47-48. http://computer.org/pubs/computer/computer.htm
31. Tai A.T., Chau S.N., Alkalaj L., and Hecht H. On-board preventive maintenance: Analysis of effectiveness and optimal duty period. Proceedings of the 3rd International Workshop on Object-Oriented Real-time Dependable Systems (WORDS'97), Newport Beach, CA (1997) 40-47
32. Wallace D.R., Ippolito L.M., "A framework for the development and assurance of high integrity software", National Institute of Standards and Technology (NIST) Special Publication 500-223, U.S. Dept. of Commerce, Dec. 1994, p. ix
33. Wallace M. Who Needs a Diploma? Why the high-tech industry wants dropouts. The New York Times Magazine 5 (2000) 76-78
34. Yemini Y., Goldszmidt G., and Yemini S. Network management by delegation. In: Krishnan I., and Zimmer W. (Eds). Integrated Network Management, II (1991), Elsevier, New York 95-107