SAFECOMP ’93 pp 157-168 | Cite as

Dependability: from Concepts to Limits

  • Jean-Claude Laprie
Conference paper


Our society is faced with an ever increasing dependence on computing systems, which lead to question ourselves about the limits of their dependability. In order to respond this question, a global conceptual and terminological framework is needed, which is first given. The analysis of the limits in dependability which is then conducted identifies design faults as the major limiting factor, a consequence of which is the concluding recommendation of applying a fault tolerance approach to the improvement of the production process.


Fault Tolerance Software Fault Fault Injection Covert Channel Fault Removal 
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. Arl 90.
    J. Arlat, M. Aguera, L. Amat, Y. Crouzet, J.C. Fabre, J.C. Laprie, E. Martins, D. Powell, “Fault injection for dependability validation: a methodology and some applications”, IEEE Transactions on Software Engineering, Special Issue on Experimental Computer Science, vol. 16, no. 2, Feb. 1990, pp. 166–182CrossRefGoogle Scholar
  2. Arn 73.
    T.F. Arnold, “The concept of coverage and its effect on the reliability model of repairable systems”, IEEE Trans. on Computers, vol. C-22, June 1973, pp. 251–254.CrossRefGoogle Scholar
  3. Bou 69.
    W.G. Bouricius, W.C. Carter, P.R. Schneider, “Reliability Modeling Techniques for Self-Repairing Computer Systems”, Proc. 24th ACM National Conf., 1969, pp. 295–309.Google Scholar
  4. COM 92.
    “Computing the Future”, Report of the Committee to Asses the Scope and Direction of Computer Science and Technology of the National Research Council, Communications of ACM, vol. 35, no. 11, Nov. 1992, pp. 30–40.Google Scholar
  5. Che 78.
    L. Chen, A. Avizienis, “N-version programming: a fault-tolerance approach to reliability of software operation”, Proc. 8th IEEE Int. Symp. on Fault Tolerant Computing (FTCS-8), Toulouse, France, June 1978, pp. 3–9.Google Scholar
  6. Cho 92.
    G.S. Choi, R.K. Iyer, “FOCUS: an experimental environment for fault sensitivity analysis”, IEEE Trans. on Computers, vol. 41, no. 12, Dec. 1992, pp. 1515–1526CrossRefGoogle Scholar
  7. Cra 92.
    R. Cramp, M.A. Vouk, W. Jones, “On operational availability of a large software-based telecommunications system”, Proc. 3rd Int. Symp. on Software Reliability Engineering, Research Triangle Park, North Carolina, Oct. 1992, pp. 358–366.Google Scholar
  8. Dav 81.
    E.A. Davis, P.K. Giloth, “No 4 ESS: performance objectives and service experience”, The Bell System Technical Journal, vol. 60, no. 6, July–Aug. 1981, pp. 1203–1224.CrossRefGoogle Scholar
  9. Des 91.
    Y. Deswarte, L. Blain, J.C. Fabre, “Intrusion tolerance in distributed computing systems”, Proc. 1991 IEEE Symposium on Research in Security and Privacy, Oakland (USA), 20–22 Mai 1991, pp.110–121Google Scholar
  10. Dug 89.
    J.B. Dugan, K.S. Trivedi, “Coverage modeling for dependability analysis of fault-tolerant systems”, IEEE Trans. on Computers, vol. 38, no. 6, June 1989, pp. 775–787.CrossRefGoogle Scholar
  11. Eck 91.
    D.E. Eckhardt, A.K. Caglayan, J.C. Knight, L.D. Lee, D.F. McAllister, M.A. Vouk, J.P.J. Kelly, “An experimental evaluation of software redundancy as a strategy for improving reliability”, IEEE Trans. on Software Engineering, vol. 17, no. 7, July 1991, 692–702.CrossRefGoogle Scholar
  12. EEC 91.
    Information Technology Security Evaluation Criteria, Provisional Harmonised criteria, Office for Official Publications of the European Communities, June 1991.Google Scholar
  13. Elm 72.
    W.R. Elmendorf, “Fault-tolerant programming”, Proc. 2nd IEEE Int. Symp. on Fault Tolerant Computing (FTCS-2), Newton, Massachusetts, June 1972, pp. 79–83.Google Scholar
  14. Gas 88.
    M. Gasser, Building a Secure Computer System, Van Nostrand Reinhold, 1988.Google Scholar
  15. Geb 88.
    J. Gebman, D. McIver, H. Shulman, “Faults with nonstationary observability are limiting avionics R&M”, Proc. 8th AIAA/IEEE Digital Systems Avionics Conf., San Jose, California, Oct. 1988, pp. 16–23.Google Scholar
  16. Ghe 91.
    C. Ghezzi, M. Jazayeri, D. Mandrioli, Fundamentals of Software Engineering, Prentice-Hall, 1991Google Scholar
  17. Gla 81.
    R.L. Glass, “Persistent software errors”, IEEE Transactions on Software Engineering, vol. SE-7, no. 2, March 1981, pp. 162–168.CrossRefGoogle Scholar
  18. Gra 86.
    J.N. Gray, “Why do computers stop and what can be done about it?”, Proc. 5th Symp. on Reliability in Distributed Software and Database Systems, Los Angeles, Jan. 1986, pp. 3–12.Google Scholar
  19. Gra 90.
    J. Gray, “A census of Tandem system availability between 1985 and 1990”, IEEE Trans. on Reliability, vol. 39, no. 4, Oct. 1990, pp. 409–418.CrossRefGoogle Scholar
  20. Gun 89.
    U. Gunneflo, J. Karlsson, J. Torin, “Evaluation of error detection schemes using fault injection by heavy-ion radiation”, Proc. 19th IEEE Int. Symp. on Fault Tolerant Computing (FTCS-19), Chicago, June 1989, pp. 340–347.Google Scholar
  21. Hec 87.
    H. Hecht, H. Dussault, “Correlated failures in fault-tolerant computers”, IEEE Trans. on Reliability, vol. R-36, no. 2, June 1987, pp. 171–175.CrossRefGoogle Scholar
  22. Hua 93.
    Y. Huang, C. Kintala, “Software implemented fault tolerance: technologies and experience”, Proc. 23rd IEEE Int. Symp. on Fault-Tolerant Computing (FTCS-23), Toulouse, June 1993, pp. 2–9.Google Scholar
  23. Iye 82.
    R.K. Iyer, S.E. Butner, E.J. McCluskey, “A statistical failure/load relationship: results of a multi-computer study”, IEEE Trans. on Computers, vol. C-31, July 1982, pp. 697–706.CrossRefGoogle Scholar
  24. Jac 91.
    J. Jacob, “The basic integrity theorem”, Prcc. IEEE International Symposium on Security and Privacy, Oakland, May 1991, pp. 89–97.Google Scholar
  25. Jon 92.
    E. Jonsson, T. Olovsson, “On the Integration of Security and Dependability in Computer Systems”, Proc. IASTED Int. Conf. for Reliability, Quality Control and Risk Assessment, 1992.Google Scholar
  26. Jos 88.
    M.K. Joseph, A. Avizienis, “A fault tolerance approach to computer viruses”, Proc. 1988 Symp. on Security and Privacy, Oakland, April 1988, pp. 52–58.Google Scholar
  27. Kan 87.
    K. Kanoun, T. Sabourin, “Software dependability of a telephone switching system”, Proc. 17th IEEE Int. Symp. on Fault-Tolerant Computing (FTCS-17), Pittsburgh, Pennsylvania, USA, June 1987, pp. 236–241.Google Scholar
  28. Kui 85.
    B. Kuipers, “Commonsense reasoning about causality: deriving behavior from structure”, in Qualitative Reasoning about Physical Systems, D.G. Bobrow editor, MIT Press, 1985, pp. 169–203.Google Scholar
  29. Lap 90.
    J.C. Laprie, J. Arlat, C. Beounes, K. Kanoun, “Definition and analysis of hardware- and software-fault-tolerant architectures”, IEEE Computer, vol. 23, no. 7, July 1990, pp. 39–51.CrossRefGoogle Scholar
  30. Lap 92a.
    J.C. Laprie, ed., Dependability: Basic Concepts and Terminology, Springer-Verlag, Vienna, 1992.zbMATHGoogle Scholar
  31. Lap 92b.
    J.C. Laprie, “Dependability: a unifying concept for reliable, safe, secure computing”, Proc. 12th IFIP World Computer Congress, Madrid, Spain, Sept. 1992, vol. I, pp. 585–593Google Scholar
  32. Lap 92c.
    J.C. Laprie, “For a product-in-a-process approach to software reliability evaluation”, Proc. 3rd Int. Symp. on Software Reliability Engineering, Research Triangle Park, NC, Oct. 1992, pp. 134–139.Google Scholar
  33. Max 86.
    R.A. Maxion, “Towards fault-tolerant user interfaces”, Proc. 5th IFAC Workshop on Safety of Computer Control Systems (SAFECOMP’86), Sarlat, France, Oct. 1986, pp. 117–122.Google Scholar
  34. Nor 83.
    D.A. Norman, “Design rules based on analyses of human error”, Communications of the ACM, vol. 26, no. 4, April 1983, pp. 254–258.CrossRefGoogle Scholar
  35. Par 90.
    D.L. Parnas, A.J. van Schouwen, S.P. Kwan, “Evaluation of safety-critical software”, Communications of the ACM, vol. 33, no. 4, June 1990, pp. 636–648.CrossRefGoogle Scholar
  36. Pow 92.
    D. Powell, “Failure Mode Assumptions and Assumption Coverage”, Proc. 22nd IEEE Int. Symp. on Fault-Tolerant Computing (FTCS-22), Boston, July 1992, pp.386–395.Google Scholar
  37. Rab 89.
    M.O. Rabin, “Efficient dispersal of information for security, load balancing and fault tolerance”, Jounal of the ACM, vol. 36, no. 2, April 1989, pp. 335–348.MathSciNetCrossRefGoogle Scholar
  38. Ran 75.
    B. Randell, “System Structure for Software Fault Tolerance”, IEEE Trans. on Software Engineering, vol. SE-1, no. 2, 1975, pp.220–232,.MathSciNetCrossRefGoogle Scholar
  39. Rou 87.
    W.B. Rouse, N.M. Morris, “Conceptual design of a human error tolerant interface for complex engineering systems”, Automatica, vol. 23, no. 2, 1987, pp. 231–235.CrossRefGoogle Scholar
  40. Sie 92.
    D.P. Siewiorek, R.S. Swarz, The Theory and Practice of Reliable System Design, Digital Press, 1992.Google Scholar
  41. The 91.
    P. Thévenod-Fosse, H. Waeselynck, “An investigation of statistical software testing”, Journal of Software Testing, Verification and Reliability, vol. 1, no. 2, 1991, pp. 5–25.CrossRefGoogle Scholar
  42. Toy 78.
    W.N. Toy, “Fault-tolerant design of local ESS processors”, Proceedings of the IEEE, vol. 66, no. 19, Oct. 1978, pp. 1126–1145.CrossRefGoogle Scholar
  43. Vog 88.
    U. Voges, ed., Application of design diversity in computerized control systems, Springer Verlag, Vienna, 1988.Google Scholar
  44. Wil 92.
    C. Wild, S. Zeil, G. Feng, “Employing accumulated knowledge to refine test descriptions”, Software Testing, Verification and Reliability, vol. 2, no. 2, July 1992, pp. 53–68.CrossRefGoogle Scholar

Copyright information

© Springer-Verlag London Limited 1993

Authors and Affiliations

  • Jean-Claude Laprie
    • 1
  1. 1.LAAS-CNRSToulouseFrance

Personalised recommendations