Your browser does not support JavaScript!
http://iet.metastore.ingenta.com
1887

Trade-offs in developing fault tolerant software

Trade-offs in developing fault tolerant software

For access to this article, please select a purchase option:

Buy article PDF
£12.50
(plus tax if applicable)
Buy Knowledge Pack
10 articles for £75.00
(plus taxes if applicable)

IET members benefit from discounts to all IET publications and free access to E&T Magazine. If you are an IET member, log in to your account and the discounts will automatically be applied.

Learn more about IET membership 

Recommend Title Publication to library

You must fill out fields marked with: *

Librarian details
Name:*
Email:*
Your details
Name:*
Email:*
Department:*
Why are you recommending this title?
Select reason:
 
 
 
 
 
IEE Proceedings E (Computers and Digital Techniques) — Recommend this title to your library

Thank you

Your recommendation has been sent to your librarian.

Design diversity has emerged as a powerful mechanism for incorporating software fault tolerance in ultra-reliable systems. In this paper we study the trade-offs available during the development process of fault-tolerant software employing the recovery block approach [2]. When the total available testing time is bounded, our analysis determines how appropriately to allocate testing time to the various redundant modules that make up the fault tolerant system so as to maximise its reliability. This requires a study of the interactions between the various modules in the software system. For example error coverage and the false alarm probability of acceptance test in the recovery block scheme may be interrelated and it may not be possible to simultaneously improve both. Hence there exists a trade-off between acceptance test coverage and false alarm probability. The impact of such trade-offs on system reliability is also studied.

References

    1. 1)
      • B. Littlewood , J.L. Verrall . A Bayesian reliability growth model for computer software. Appl. Stat. , 3 , 332 - 346
    2. 2)
      • J.D. Musa , A. Iannino , K. Okumoto . (1987) , Software reliablity: measurement, prediction, application.
    3. 3)
      • Arlat, J., Kanoun, K., Laprie, J.-C.: `Dependability evaluation of software fault-tolerance', Digest of papers: The 18th international symposium on fault-tolerant computing, 1988, p. 142–147.
    4. 4)
      • N. Leveson , S.S. Cha , J.C. Knight , T.J. Shimeall . The use of self-checks and voting in software error detection: an empirical study. IEEE Trans. Softw. Eng. Apr. , 432 - 443
    5. 5)
      • J.-C. Laprie , J. Arlat , C. Beounes , K. Kanoun . Definition and analysis of hardware and software fault-tolerant architectures. IEEE Computer , 39 - 51
    6. 6)
      • H. Hecht , M. Hecht , D.K. Pradhan . (1986) Fault tolerant software, Fault tolerant computing.
    7. 7)
      • F. Saglietti , W. Ehrenberger . (1986) Software diversity—some considerations about its benefits and its limitations, SAFE-COMP.
    8. 8)
      • Brilliant, S.S., Knight, J.C., Ammann, P.E.: `On the performance of software testing using multiple versions', Digest of papers: The 20th international symposium on fault-tolerant computing, 1990, p. 408–415.
    9. 9)
      • B. Littlewood , T. Anderson . (1985) Software reliability prediction, Resilient computing systems.
    10. 10)
      • K. Okumoto . A statistical method for software quality control. IEEE Trans. Softw. Eng. , 1424 - 1430
    11. 11)
      • A. Goel . Software reliability models: assumptions, limitations, and applicability. IEEE Trans. Softw. Eng. , 1141 - 1423
    12. 12)
      • Lyu, M.R., Avizienis, A.: `Assuring design diversity in N-version software: a design paradigm for N-version programming', 2nd IFIP conference on dependable computing for critical application, 1991, p. 89–98.
    13. 13)
      • B. Randell . System structure for software fault tolerance. IEEE Trans. Softw. Eng. , 220 - 232
    14. 14)
      • Vaidya, N.H., Krishna, C.M., Singh, A.D.: `Testing fault tolerant software', TR93-CSE-17, Technical report, July 1993, p. 1–26.
    15. 15)
      • Pucci, G.: `On the modelling and testing of recovery block structures', Digest of papers: The 20th international symposium on fault-tolerant computing, 1990, p. 356–362.
    16. 16)
      • S.S. Brilliant , J.C. Knight , N.G. Leveson . Analysis of faults in N-version software experiment. IEEE Trans. Softw. Eng. , 238 - 247
    17. 17)
      • J.G. Shanthikumar . Software reliability models: a review. Microelectron. & Reliab. , 5 , 903 - 943
    18. 18)
      • N.D. Singapurwalla . Determining an optimal time interval for testing and debugging software. IEEE Trans. Softw. Eng. , 313 - 319
    19. 19)
      • R.K. Scott , J.W. Gault , D.F. MacAllister . Fault-tolerant software reliability modelling. IEEE Trans. Softw. Eng. , 582 - 592
    20. 20)
      • Cha, S.D., Knight, J.C., Leveson, N.G., Shimeall, T.J.: `An empirical study of software error detection using self-checks', Digest of papers: The 17th international symposium on fault-tolerant computing, 1987, p. 156–161.
http://iet.metastore.ingenta.com/content/journals/10.1049/ip-e.1993.0045
Loading

Related content

content/journals/10.1049/ip-e.1993.0045
pub_keyword,iet_inspecKeyword,pub_concept
6
6
Loading
This is a required field
Please enter a valid email address