Imperfect Debugging/Testing Efficiency Software Reliability Growth Models

  • P. K. Kapur
  • H. Pham
  • A. Gupta
  • P. C. Jha
Part of the Springer Series in Reliability Engineering book series (RELIABILITY)


Software systems are the means developed and designed by humans for automated operation of several types of real operating systems meant for human kind. Even though the creator of software systems is the universe most dominant and intelligent creature in the universe we cannot deny the possibility of software failures during their operation period. These failures are mainly due to faults manifested in them by their designers. Primarily testing of software is performed with a goal to detect and remove most of the underlying faults. Even though the software testing and debugging team put its best efforts, uses distinct methods and techniques or the developers makes heavy expenditure on testing and debugging latest, well planed and controlled strategies, we cannot be sure that the software can be made free of all type of faults at the time of its launch.


Usage Function Reliability Growth Fault Content Failure Intensity Bass Model 
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.



  1. 1.
    Kapur PK, Kumar D, Gupta A, Jha PC (2006) On how to model software reliability growth in the presence of imperfect debugging and fault generation. In: Proceedings 2nd international conference on reliability and safety engineering, INCRESE, pp 261–268Google Scholar
  2. 2.
    Goel AL (1985) Software reliability models: assumptions, limitations and applicability. IEEE Trans Software Eng SE-11:1411–1423CrossRefGoogle Scholar
  3. 3.
    Jelinski Z, Moranda P (1972) Software reliability research. In: Freiberger W (ed) Statistical computer performance evaluation. Academic Press, New York, pp 465–484Google Scholar
  4. 4.
    Kapur PK, Garg RB (1990) Optimal software release policies for software reliability growth models under imperfect debugging. Recherché Operationanelle/Operations Research 24:295–305MATHGoogle Scholar
  5. 5.
    Goel AL, Okumoto K (1979) Time dependent error detection rate model for software reliability and other performance measures. IEEE Trans Reliability R-28(3):206–211CrossRefGoogle Scholar
  6. 6.
    Ohba M, Chou X M (1989) Does imperfect debugging effect software reliability growth. In: Proceedings 11th international conference of software engineering, pp 237–244Google Scholar
  7. 7.
    Xie M (2003) A study of the effect of imperfect debugging on software development cost. IEEE Trans Software Eng 29(5):471–473CrossRefGoogle Scholar
  8. 8.
    Zhang X, Teng X, Pham H (2003) Considering fault removal efficiency in software reliability assessment. IEEE Trans Syst Man Cybern Part A Syst Humans 33(1):114–120CrossRefGoogle Scholar
  9. 9.
    Yamada S, Tokunou K, Osaki S (1992) Imperfect debugging models with fault introduction rate for software reliability assessment. Int J Syst Sci 23(12):2253–2264CrossRefGoogle Scholar
  10. 10.
    Kapur PK, Grover PS, Younes S (1994) Modeling an imperfect debugging phenomenon with testing effort. In: Proceedings 5th international symposium on software reliability engineering (ISSRE’1994). IEEE Computer Society, Monterey, pp 178–183Google Scholar
  11. 11.
    Lynch T, Pham H, Kuo W (1994) Modeling software-reliability with multiple failure-types and imperfect debugging. In: 1994 proceedings annual reliability and maintainability symposium, pp 235–240Google Scholar
  12. 12.
    Lo HJ, Huang CY (2004) Incorporating imperfect debugging into software fault processes. TENCON 2004. In: 2004 IEEE region 10 conference, vol 2, 21–24 November 2004, pp 326–329Google Scholar
  13. 13.
    Kapur PK, Younes S (1996) Modeling an imperfect debugging phenomenon in software reliability. Microelectron Reliability 36(5):645–650CrossRefGoogle Scholar
  14. 14.
    Pham H, Nordmann L, Zhang XA (1999) General imperfect-software-debugging model with s-shaped fault-detection rate. IEEE Trans Reliability 48(2):169–175CrossRefGoogle Scholar
  15. 15.
    Pham H (2000) Software reliability. Springer-Verlag, New YorkMATHGoogle Scholar
  16. 16.
    Kapur P K, Singh O, Gupta A (2005e) Some modeling peculiarities in software reliability. Quality, reliability and infocom technology, trends and future directions. Narosa Publications Pt. Ltd., New Delhi, pp 20–34Google Scholar
  17. 17.
    Yamada S, Ohba M, Osaki S (1983) S-shaped software reliability growth modeling for software error detection. IEEE Trans Reliability R-32(5):475–484CrossRefGoogle Scholar
  18. 18.
    Pham H, Zhang X (2003) NHPP software reliability and cost models with testing coverage. Eur J Oper Res 145(2):443–454MATHCrossRefGoogle Scholar
  19. 19.
    Kapur PK, Gupta A, Jha PC (2007) Reliability growth modeling and optimal release policy of a n-version programming system incorporating the effect of fault removal efficiency. Int J Autom Comput 4(4):369–379CrossRefGoogle Scholar
  20. 20.
    Kumar D, Kapur R, Sehgal VK, Jha PC (2007) On the development of software reliability growth models with two types of imperfect debugging. Commun Dependability Qual Manag Int J 10(3):105–122Google Scholar
  21. 21.
    Huang CY, Kuo SY, Lyu MR, Lo HJ (2000) Effort-index-based software reliability growth models and performance assessment. In: Proceedings 24th annual international computer software and applications conference (COMPSAC 2000), Taipei, Taiwan, 25–27 October 2000, pp 454–459Google Scholar
  22. 22.
    Kapur PK, Gupta A, Jha PC (2007) Reliability analysis of project and product type software in operational phase incorporating the effect of fault removal efficiency. Int J Reliability Qual Safety Eng 14(3):219–240CrossRefGoogle Scholar
  23. 23.
    ESA Board for Software Standardization and Control (1995) Guide to the software operations and maintenance phase. European Space Agency, 8-10, rue Mario-Nikis, 75738 PARIS CEDEX, France, ESA PSS-05-07 Issue 1 Revision 1Google Scholar
  24. 24.
    Pham H (2006) System software reliability. Reliability engineering series. Springer, LondonGoogle Scholar
  25. 25.
    Jeske DR, Zhang X, Pham L (2001) Accounting for realities when estimating the field failure rate of software. In: Proceedings 12th international symposium on software reliability engineering, pp 332–339Google Scholar
  26. 26.
    Kenny GQ (1993) Estimating defects in a commercial software during operational use. IEEE Trans Reliability 42(1):107–115CrossRefGoogle Scholar
  27. 27.
    Kapur PK, Bardhan AK, Jha PC (2003) Optimal reliability allocation problem for a modular software system. OPSEARCH J Oper Res Soc India 40(2):133–148MathSciNetGoogle Scholar
  28. 28.
    Bass FM (1969) A new product growth model for consumer durables. Manag Sci 15:215–227MATHCrossRefGoogle Scholar
  29. 29.
    Givon M, Mahajan V, Muller E (1980) Software piracy: estimation of lost sales and the impact on software diffusion. J Marketing 59:29–37CrossRefGoogle Scholar
  30. 30.
    Brooks WD, Motley RW (1980) Analysis of discrete software reliability models—technical report (RADC-TR-80-84). Rome Air Development Center, New YorkGoogle Scholar
  31. 31.
    Musa JD (1980) Software reliability data. Data and Analysis Center for software, USA,

Copyright information

©  Springer-Verlag London Limited 2011

Authors and Affiliations

  1. 1.Department of Operational ResearchUniversity of DelhiDelhiIndia
  2. 2.Department of Industrial and Systems EngineeringRutgers UniversityPiscatawayUSA

Personalised recommendations