Advertisement

Error Detection

  • Peter Alan Lee
  • Thomas Anderson
Part of the Dependable Computing and Fault-Tolerant Systems book series (DEPENDABLECOMP, volume 3)

Abstract

The starting point for all fault tolerance strategies is the detection of an erroneous state, that is a state which, in the absence of any corrective actions, could have led to a failure of the system. Thus the success of any fault tolerant system will be critically dependent upon the effectiveness of the techniques for error detection.

Keywords

Error Detection Design Fault Diagnostic Check Triple Modular Redundant Component 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.

References

  1. 1.
    J.R. Sklaroff, “Redundancy Management Technique for Space Shuttle Computers,” IBM Journal of Research and Development 20 (1), pp. 20–28 (January 1976).CrossRefGoogle Scholar
  2. 2.
    R.H. Campbell, K.H. Horton, and G.G. Belford, “Simulations of a Fault-Tolerant Deadline Mechanism,” Digest of Papers FTCS-9: Ninth Annual International Symposium on Fault-Tolerant Computing, Madison (WI), pp. 95–101 (June 1979).Google Scholar
  3. 3.
    A. Avizienis et al., “The STAR (Self-Testing and Repairing) Computer: An Investigation of the Theory and Practice of Fault-Tolerant Computer Design,” IEEE Transactions on Computers 20 (11), pp. 1312–1321 (November 1971).CrossRefMATHGoogle Scholar
  4. 4.
    J.J. Stuffier, N.G. Parke, and P.C. Barr, “The SERF Fault-Tolerant Computer,” Digest of Papers FTCI3: 73 International Symposium on Fault-Tolerant Computing, Palo Alto (CA), pp.23–31 ( (June 1973).Google Scholar
  5. 5.
    W.W. Peterson and E.J. Weldon Jr. Error-Correcting Codes, MIT Press, Cambridge MA ) (1972).MATHGoogle Scholar
  6. 6.
    A. Mahmood and E.J. McCluskey. -Watchdog Processors: Error Coverage and Overhead,“ Digest of Papers FTCS-15: Fifteenth Annual International Symposium on Fault-Tolerant Computing, Ann Arbor (MI), pp. 214–219 (June 1985).Google Scholar
  7. 7.
    M.A. Schuette, D.P. Siewiorek, and Y.X. Zhu, “Experimental Evaluation of Two Concurrent Error Detection Schemes,” Digest of Papers FTCS-16: Sixteenth Annual International Symposium on Fault-Tolerant Computing, Vienna, pp. 138–143 (July 1986).Google Scholar
  8. 8.
    A. Avizienis, “Arithmetic Error Codes: Cost and Effectiveness Studies for Applications in Digital Systems Design,” IEEE Transactions on Computers 20 (11), pp. 1322–1331 (November 1971).CrossRefMATHGoogle Scholar
  9. 9.
    R.S. Swarz, “Reliability and Maintainability Enhancements for the VAX-11/780,” Digest of Papers FTCS-8: Eighth Annual International Conference on Fault-Tolerant Computing, Toulouse, pp. 24–28 (June 1978).Google Scholar
  10. 10.
    R.M. Needham, “Protection,” pp. 264–287 in Computing Systems Reliability, (ed. T. Anderson and B. Randell ), Cambridge University Press, Cambridge (1979).Google Scholar
  11. 11.
    G.J. Myers, Advances in Computer Architecture, Wiley, New York (1978).MATHGoogle Scholar
  12. 12.
    R.N. Taylor, “Assertions in Programming Languages,” ACM SIGPLAN Notices 15 (1), pp. 105–109 (January 1980).CrossRefGoogle Scholar
  13. 13.
    S.D. Cha et al., “An Empirical Study of Software Error Detection Using Self-Checks,” Digest of Papers FTCS-17: Seventeenth Annual International Symposium on Fault-Tolerant Computing, Pittsburgh, pp. 156–161 (July 1987).Google Scholar
  14. 14.
    J.P. Black, D.J. Taylor, and D.E. Morgan, “A Compendium of Robust Data Structures,” Digest of Papers FTCS-11: Eleventh Annual International Symposium on Fault-Tolerant Computing, pp. 129–131 (June 1981).Google Scholar
  15. 15.
    D.J. Taylor, D.E. Morgan, and J.P. Black, “Redundancy in Data Structures: Some Theoretical Results,” IEEE Transactions on Software Engineering 6 (6), pp. 595–602 (November 1980).CrossRefMathSciNetGoogle Scholar
  16. 16.
    J.P. Black, D.J. Taylor, and D.E. Morgan, “A Case Study in Fault Tolerant Software,” Software–Practice and Experience 11 (2), pp. 145–157 (February 1981).CrossRefGoogle Scholar
  17. D. Katsuki et al., “ Pluribus - An Operational Fault-Tolerant Multiprocessor,” Proceedings of the IEEE 66 (10), pp.1146–1159 (October 1978).CrossRefGoogle Scholar
  18. 18.
    E.A. Feustel, “On The Advantages of Tagged Architecture,” IEEE Transactions on Computers 22 (7), pp. 644–656 (July 1973).CrossRefGoogle Scholar
  19. 19.
    E.I. Organick, Computer System Organization: The B570016700 Series, Academic Press, New York (1973).Google Scholar
  20. 20.
    J.K. Iliffe, Basic Machine Principles, Macdonald, London (1968).Google Scholar
  21. 21.
    D.M. Harland, Rekursiv: Object-oriented Computer Architecture, Ellis Horwood (1988).Google Scholar
  22. 22.
    R. Kerr, “An Experimental Processor Architecture for Improved Reliability,” pp. 199–212 in State of the Art Report on System Reliability and Integrity, Infotech, Maidenhead (1978).Google Scholar
  23. 23.
    M. Nicolaidis, “Evaluation of a Self-Checking Version of the MC68000 Microprocessor,” Digest of Papers FTCS-15: Fifteenth Annual International Symposium on Fault-Tolerant Computing, Ann Arbor, MI, pp. 350–356 (June 1985).Google Scholar
  24. 24.
    D.A. Rennels, “Architectures for Fault-Tolerant Spacecraft Computers,” Proceedings of the IEEE 66 (10), pp. 1255–1268 (October 1978).CrossRefGoogle Scholar
  25. 25.
    R.M. Sedmak and H.L. Liebergot, “Fault-Tolerance of a General Purpose Computer Implemented by Very Large Scale Integration,” IEEE Transactions on Computers 29 (6), pp. 492–500 (June 1980).CrossRefGoogle Scholar

Copyright information

© Springer-Verlag/Wien 1990

Authors and Affiliations

  • Peter Alan Lee
    • 1
  • Thomas Anderson
    • 1
  1. 1.Computing LaboratoryUniversity of Newcastle upon TyneUK

Personalised recommendations