Application of multi attribute utility theory in multiple releases of software

  • P. K. KapurEmail author
  • Jyotish N. P. Singh
  • Ompal Singh
Original Article


One of the important applications of software reliability models is the determination of software release time. Most of the existing studies on this topic use models based on non homogeneous Poisson process with a bounded mean value function. Multi up gradation based software reliability growth model is developed for successive release modelling and analysis. Based on this model, maximum fault removal for upgraded software and optimal release time of upgraded software are investigated as well. This paper proposes a new practical method for determining when to stop software testing considering failure intensity and cost as two factors simultaneously. This issue has been widely known as the optimal release problem of software product. The proposed new decision model based on multi-attribute utility analysis is tested on the real world data sets. In addition, the proposed decision model can help companies to make a rational decision on the optimal timing of the software.


Software reliability growth model Multi attribute utility theory Multi release 



The research work presented in this paper is supported by grants to the first author from Department of Science and Technology (DST) Grant No SR/S4/MS: 600/09, India.


  1. Brito J, de Almeida AT (2009) Multi-attribute risk assessment for risk ranking of natural gas pipelines. Reliab Eng Syst Saf 94:187–198CrossRefGoogle Scholar
  2. Dalal SR, Mallows CL (1988) When should one stop testing software? J Am Stat Assoc 83:872–879CrossRefzbMATHMathSciNetGoogle Scholar
  3. Ehrlich W et al (1993) Determining the cost of a stop-test decision. IEEE SoftwGoogle Scholar
  4. Ferreira RJP et al (2009) A multi-criteria decision model to determine inspection intervals of condition monitoring based on delay time analysis. Reliab Eng Syst Saf 94:905–912CrossRefGoogle Scholar
  5. Fishburn CP (1970) Utility theory for decision making. Wiley, New YorkzbMATHGoogle Scholar
  6. Goel L, Okumoto K (1979) Time-dependent error-detection rate model for software reliability and other performance measures. IEEE Trans Reliab 28:206–211CrossRefzbMATHGoogle Scholar
  7. Kapur PK, Garg RB (1990) Cost reliability optimum release policies for a software system with testing effort. Oper Res 27:109–116zbMATHGoogle Scholar
  8. Kapur PK et al (1999) Contributions to hardware and software reliability. World Scientific, SingaporeCrossRefzbMATHGoogle Scholar
  9. Kapur PK et al (2008) A unified approach for developing software reliability growth models in the presence of imperfect debugging and error generation. IEEE Trans Reliab 60:331–340CrossRefGoogle Scholar
  10. Kapur PK et al (2010a) Multi up-gradation software reliability growth model with imperfect debugging. Int J Syst Assur Eng Manag 1:299–306CrossRefGoogle Scholar
  11. Kapur PK et al (2010b) Multi up-gradation software reliability model, presented at the 2nd international conference on reliability, safety & hazard (ICRESH-2010), MumbaiGoogle Scholar
  12. Kapur PK et al (2011) Software reliability assessment with OR applications. Springer, UKCrossRefzbMATHGoogle Scholar
  13. Kapur PK et al (2011) Development of a multi-release SRGM incorporating the effect of bugs reported from operational phase, IEEE Trans on Reliability Google Scholar
  14. Keeney RL, Raiffa H (1976) decisions with multiple objectives: preferences and value tradeoffs. Wiley, New YorkGoogle Scholar
  15. Li X et al (2011) Reliability analysis and optimal version-updating for open source software. Inf Softw Technol 53:929–936CrossRefGoogle Scholar
  16. Lin CT, Huang CY (2006) Software release time management: how to use reliability growth models to make better decisions. In: IEEE international conference on management of innovation and technology. p 658–662Google Scholar
  17. McDaid K, Wilson SP (2001) Deciding how long to test software. The Statistician 50:117–134MathSciNetGoogle Scholar
  18. Musa JD et al (1987) Measurement, prediction and application. McGraw Hill, New YorkGoogle Scholar
  19. Obha M (1984) Software reliability analysis models. IBM J Res Dev 28:428–443CrossRefGoogle Scholar
  20. Okumoto K, Goel AL (1983) Optimal release time for computer software. IEEE Trans Softw Eng 9:323–327Google Scholar
  21. Pham H (2000) Software reliability. Springer, SingaporezbMATHGoogle Scholar
  22. Pham H (2006) System software reliability. Springer, BerlinGoogle Scholar
  23. Pham H, Zhang X (1999) Software release policies with gain in reliability justifying costs. Ann Softw Eng 8:147–166CrossRefGoogle Scholar
  24. Ping CAO et al (2010) An optimal release policy for software testing process. In: 29th Chinese control conference, ChinaGoogle Scholar
  25. Samoladas L et al (2010) Survival analysis on the duration of open source projects. Inf Softw Technol 52:902–922CrossRefGoogle Scholar
  26. Winterfeldt DV, Edwards W (1986) Decision analysis and behavioral research. Cambridge University Press, CambridgeGoogle Scholar
  27. Wood (1996) Predicting software reliability. IEEE Comput 9:69–77CrossRefGoogle Scholar
  28. Xie M (1991) Software reliability modeling. World Scientific Publishing, SingaporeGoogle Scholar
  29. Yamada S et al (1984) S-shaped software reliability growth models and their applications. IEEE Trans Reliab 33:289–292CrossRefGoogle Scholar

Copyright information

© The Society for Reliability Engineering, Quality and Operations Management (SREQOM), India and The Division of Operation and Maintenance, Lulea University of Technology, Sweden 2014

Authors and Affiliations

  • P. K. Kapur
    • 1
    Email author
  • Jyotish N. P. Singh
    • 2
  • Ompal Singh
    • 2
  1. 1.Amity International Business SchoolAmity UniversityNoidaIndia
  2. 2.Department of Operational ResearchUniversity of DelhiDelhiIndia

Personalised recommendations