System-Level Reliability and Sensitivity Analyses for Three Fault-Tolerant System Architectures

  • Joanne Bechta Dugan
  • Michael R. Lyu
Part of the Dependable Computing and Fault-Tolerant Systems book series (DEPENDABLECOMP, volume 9)


This paper discusses the modeling and analysis of three major fault-tolerant software system architectures: DRB (Distributed Recovery Blocks), NVP (N-Version Programming) and NSCP (N Self-Checking Programming). In the system-level reliability modeling domain, fault tree analysis techniques and Markov modeling techniques are combined to incorporate transient and permanent hardware faults as well as unrelated and related software faults. These models are parameterized by a real-world fault-tolerant flight control computer application for evaluations and comparisons. In particular, a series of sensitivity analysis is performed to explore the critical components in each fault-tolerant architecture and display their quantitative impacts to the overall system reliability.


IEEE Transaction Acceptance Test Fault Tree Software Fault Software Failure 
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]
    Algirdas AviŽienis. The N-version approach to fault-tolerant software. IEEE Transactions on Software Engineering, SE-11(12):1491–1501, December 1985.CrossRefGoogle Scholar
  2. [2]
    P.G. Bishop, D.G. Esp, M. Barnes, P. Humphreys, G. Dahl, and J. Lahti. PODS — a project of diverse software. IEEE Transactions on Software Engineering, SE-12(9):929–940, September 1986.Google Scholar
  3. [3]
    D. Briere and P. Traverse. Airbus A320/A330/A340 electrical flight controls: A family of fault-tolerant systems. In Proceedings of the 23rd Symposium on Fault Tolerant Computing, pages 616-623, 1993.Google Scholar
  4. [4]
    Joanne Bechta Dugan and K. S. Trivedi. Coverage modeling for dependability analysis of fault-tolerant systems. IEEE Transactions on Computers, 38(6):775–787, 1989.CrossRefGoogle Scholar
  5. [5]
    Robert Geist and Kishor Trivedi. Reliability estimation of fault-tolerant systems: Tools and techniques. IEEE Computer, pages 52-61, July 1990.Google Scholar
  6. [6]
    Gunnar Hagelin. ERICSSON safety system for railway control. In U. Voges, editor, Software Diversity in Computerized Control Systems, pages 11-21. Springer-Verlag, 1988.Google Scholar
  7. [7]
    A. D. Hills. Digital fly-by-wire experience. In Proceedings AGARD Lecture Series, number 143, October 1985.Google Scholar
  8. [8]
    Allen M. Johnson and Miroslaw Malek. Survey of software tools for evaluating reliability availability, and serviceability. ACM Computing Surveys, 20(4):227–269, December 1988.CrossRefGoogle Scholar
  9. [9]
    K.H. Kim and Howard O. Welch. Distributed execution of recovery blocks: An approach for uniform treatment of hardware and software faults in real-time applications. IEEE Transactions on Computers, 38(5):626–636, May 1989.CrossRefGoogle Scholar
  10. [10]
    Jaynarayan H. Lala and Linda S. Alger. Hardware and software fault tolerance: A unified architectural approach. In Proc. IEEE Int. Symp. on Fault-Tolerant Computing, FTCS-18, pages 240-245, June 1988.Google Scholar
  11. [11]
    Jean-Claude Laprie. Dependability evaluation of software systems in operation. IEEE Transactions on Software Engineering, SE-10(6):701–714, November 1984.CrossRefGoogle Scholar
  12. [12]
    Jean-Claude Laprie, Jean Arlat, Christian Beounes, and Karama Kanoun. Definition and Analysis of Hardware-and Software-Fault-Tolerant Architectures. IEEE Computer, pages 39-51, July 1990.Google Scholar
  13. [13]
    Jean-Claude Laprie and Karama Kanoun. X-ware reliability and availability modeling. IEEE Transactions on Software Engineering, pages 130-147, February, 1992.Google Scholar
  14. [14]
    Michael R. Lyu and Yu-Tao He. Improving the N-version programming process through the evolution of a design paradigm. IEEE Transactions on Reliability, June 1993.Google Scholar
  15. [15]
    C. V. Ramamoorthy, Y. Mok, F. Bastani, G. Chin, and K. Suzuki. Application of a methodology for the development and validation of reliable process control software. IEEE Transactions on Software Engineering, SE-7(6):537–555, November 1981.CrossRefGoogle Scholar
  16. [16]
    Brian Randell. System structure for software fault tolerance. IEEE Transactions on Software Engineering, SE-l(2):220–232, June 1975.MathSciNetGoogle Scholar
  17. [17]
    R. Sahner and K. S. Trivedi. Reliability modeling using SHARPE. IEEE Transactions on Reliability, R-36(2): 186–193, June 1987.CrossRefGoogle Scholar
  18. [18]
    R. Keith Scott, James W. Gault, and David F. McAllister. Fault-tolerantsoftware reliability modeling. IEEE Transactions on Software Engineering, SE-13(5):582–592, May 1987.CrossRefGoogle Scholar
  19. [19]
    Kang G. Shin and Yann-Hang Lee. Evaluation of error recovery blocks used for cooperating processes. IEEE Transactions on Software Engineering, SE-10(6):692–700, November 1984.CrossRefGoogle Scholar
  20. [20]
    George. E. Stark. Dependability evaluation of integrated hardware/software systems. IEEE Transactions on Reliability, pages 440-444, October 1987.Google Scholar
  21. [21]
    Pascal Traverse. Airbus and ATR system architecture and specification. In U. Voges, editor, Software Diversity in Computerized Control Systems, pages 95-104. Springer-Verlag, June 1986.Google Scholar
  22. [22]
    Udo Voges. Use of diversity in experimental reactor safety systems. In U. Voges, editor, Software Diversity in Computerized Control Systems, pages 29-49. Springer-Verlag, 1988.Google Scholar
  23. [23]
    L. J. Yount. Architectural solutions to safety problems of digital flight-critical systems for commercial transports. In Proceedings AIAA/IEEE Digital Avionics Systems Conference, pages 1-8, December 1984.Google Scholar

Copyright information

© Springer-Verlag/Wien 1995

Authors and Affiliations

  • Joanne Bechta Dugan
    • 1
  • Michael R. Lyu
    • 2
  1. 1.Department of Electrical EngineeringUniversity of VirginiaCharlottesvilleUSA
  2. 2.BellcoreMorristownUSA

Personalised recommendations