Fault-Tolerant Automatic Control

  • Marc Bodson
  • John Lehoczky
  • Ragunathan Rajkumar
  • Lui Sha
  • Jennifer Stephan
Part of the The Springer International Series in Engineering and Computer Science book series (SECS, volume 297)


There has been great progress in the area of hardware fault-tolerance. Unfortunately, the same cannot be said about software fault-tolerance. Computing system failures are increasingly caused by software faults. A commercial study by Tandem Computing Inc.


Software Architecture Fuzzy Logic Controller Ball Position Complex Software Software Fault 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    A. Avizienis and J. Kelly, “Fault Tolerance by Design Diversity: Concepts and Experiments,”Computervol. 17, no. 8, pp. 67–80, 1984.CrossRefGoogle Scholar
  2. 2.
    M. Bodson, J. Lehoczky, R. Rajkumar, L. Sha, M. Smith and J. Stephan, “Software Fault-Tolerance for Control of Responsive Systems,”Proc. of the Third International Workshop of Responsive Computer SystemsOctober 1993.Google Scholar
  3. 3.
    M. Bodson, J. Lehoczky, R. Rajkumar, L. Sha, J. Stephan and M. Smith, “Control Reconfiguration in the Presence of Software Failures,” The Proceedings of the IEEE Conference on Decision and Control, San Antonio, TX, 1993.Google Scholar
  4. 4.
    R. L. Glass, “Persistent Software Errors,”IEEE Trans. on Software Engineeringvol. 7, no. 2, pp. 162–168, 1981.CrossRefGoogle Scholar
  5. 5.
    J. Gray “A Census of Tandem System Availability Between 1985 and 1990,”IEEE Transactions on Reliabilityvol. 39, no.4, pp. 409–418, 1990.CrossRefGoogle Scholar
  6. 6.
    J. Kelly and S. Murphy, “Achieving Dependability Throughout the Development Process: A Distributed Software Experiment,”IEEE Trans. on Software Engineeringvol. 16, no 2, pp. 153–165, February 1990.CrossRefGoogle Scholar
  7. 7.
    F. Levendel, “Defects and Reliability Analysis of Large Software Systems,”19th Symposium on Fault Tolerant Computing, pp. 238–244, 1989.Google Scholar
  8. 8.
    J. D. Musa, “A Theory of Software Reliability and its Application,”IEEE Trans. on Software Engineeringvol. SE-1, no. 3, pp. 312–327, Sept., 1975.CrossRefGoogle Scholar
  9. 9.
    S. L. Pfleeger, “Measuring Software Reliability,”IEEE Spectrumpp. 5660, August 1992.Google Scholar
  10. 10.
    B. Randell, “System Structure for Software Fault Tolerance,”IEEE Trans. on Software Engineeringvol. 1, pp. 220–232, 1975.CrossRefGoogle Scholar
  11. 11.
    L. Sha, J. Lehoczky, and M. Bodson, “ The Simplex Architecture: Analytic Redundancy for Software Fault Tolerance,”Proc. of the First International Workshop of Responsive Computer SystemsNice, France, 1991.Google Scholar
  12. 12.
    L. Sha, J. Lehoczky, M. Bodson, P. Krupp and C. Nowacki, “Position Paper: Responsive Airborne Radar Systems,”Proc. of the Second International Workshop of Responsive Computer SystemsOctober 1992.Google Scholar
  13. 13.
    G. Watson, “Three Little Bits Breed a Big, Bad Bug,”IEEE Spectrump. 52, May 1992.Google Scholar

Copyright information

© Springer Science+Business Media New York 1995

Authors and Affiliations

  • Marc Bodson
    • 1
  • John Lehoczky
    • 2
  • Ragunathan Rajkumar
    • 3
  • Lui Sha
    • 3
  • Jennifer Stephan
    • 4
  1. 1.Department of Electrical EngineeringUniversity of UtahSalt Lake CityUSA
  2. 2.Department of StatisticsCarnegie Mellon UniversityPittsburghUSA
  3. 3.Software Engineering InstituteCarnegie Mellon UniversityPittsburghUSA
  4. 4.Department of Electrical and Computer EngineeringCarnegie Mellon UniversityPittsburghUSA

Personalised recommendations