Fuzzy Methods in Software Reliability Modeling

  • Kai-Yuan Cai
Part of the The Kluwer International Series in Engineering and Computer Science book series (SECS, volume 363)


Software is developed by human. If human commits errors, defects may be introduced into software. Under some circumstances, defects may be activated by software inputs and lead to faulty software states and eventually result in software failures. This arouses software reliability problems. Software reliability modeling is aimed at using mathematical tools to deal with software reliability problems. By continuous-time software reliability modeling we mean that the time base used to measure software reliability is continuous, such as calendar time, clock time and CPU execution time. There have been many methodologies adopted for software reliability modeling [2, 13], including random-time methodology, by which inter-failure times are treated as random variables; stochastic methodology, by which the number of software failures occurring in a time interval is treated as a stochastic process; Bayesian methodology; fuzzy methodology; neural network methodology; non-parametric methodology; and others. In this section we introduce a fuzzy software reliability growth model which is applicable to software testing phase in which software reliability normally demonstrates growth trends [4].


Fuzzy Variable Software Reliability Fuzzy Method Software Failure Possibility Space 
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.
    J.E. Angus, L.E. James, “Combined Hardware/Software Reliability Models”, Proc. Annual Reliability and Maintainability Symposium, 1982, pp 176–181.Google Scholar
  2. 2.
    K.Y. Cai, “Towards a Conceptual Framework of Software Run Reliability Modeling”, PDCS2 Deliverables, 1994, pp525–554.Google Scholar
  3. 3.
    K.Y. Cai, Elements of Software Reliability Engineering, Tsinghua University Press, Beijing, (in Chinese), 1995.Google Scholar
  4. 4.
    K.Y. Cai, C.Y. Wen, M.L. Zhang, “A Novel Approach to Software Reliability Modeling”, Microelectronics and Reliability, Vol.33, No.15, 1993, pp2265–2267.CrossRefGoogle Scholar
  5. 5.
    K.Y. Cai, C.Y. Wen, M.L. Zhang, “Reliability Behavior of Combined Hardware-Software Systems”, in: T. Onisawa, J. Kacprzyk (eds), Reliability and Safety Analyses under Fuzziness, Physica-Verlag, 1995, pp183–195.Google Scholar
  6. 6.
    A.L. Goel, J. Soenjoto, “Models for Hardware-Software Systems Operational-Performance Evaluation”, IEEE Transactions on Reliability, Vol.R-31, No.3, 1981, pp232–239.CrossRefGoogle Scholar
  7. 7.
    Z.S. Liu, J.W. Huang, “A New Method for the Calculation of the Best-Fit Line”, Acta Metrologica Sinica, (in Chinese), Vol.9, 1988, pp147–l50.Google Scholar
  8. 8.
    J.D. Musa, A.F. Ackerman, “Quantifying Software Validation: When to Stop Testing”, IEEE Software, Vol.6, No.3, 1989, pp19–27.CrossRefGoogle Scholar
  9. 9.
    J.D. Musa, A. Iannino, K. Okumoto, Software Reliability: Measurement, Prediction, Application, McGraw-Hill, 1987.Google Scholar
  10. 10.
    M.L. Shooman, “Yes, Software Reliability can be Measured and Predicted”, Proceedings Fall Joint Computer Conference, 1987, pp121–122.Google Scholar
  11. 11.
    N.D. Singpurwalla, R. Soyer, “Assessing (Software) Reliability Growth Using a Random Coefficient Autoregressive Process and Its Ramifications”, IEEE Transactions on Software Engineering, Vol.SE-11, No.12, 1985, pp1456–1464.CrossRefGoogle Scholar
  12. 12.
    U. Sumita, Y. Masuda, “Analysis of Software Availability/Reliability under the Influence of Hardware Failures”, IEEE Transactions on Software Engineering, Vol.SE-12, No.1, 1986, pp32–41.MathSciNetGoogle Scholar
  13. 13.
    M. Xie, Software Reliability Modeling, World Scientific, 1991.CrossRefGoogle Scholar

Copyright information

© Kluwer Academic Publishers 1996

Authors and Affiliations

  • Kai-Yuan Cai
    • 1
  1. 1.Department of Automatic ControlBeijing University of Aeronautics and AstronauticsBeijingChina

Personalised recommendations