Abstract
With successful multi up gradations of software as an indispensable part of any Information Technology company, the challenge before them is to decide when to stop testing these multiple versions. Too much of testing delays the software system’s entry into the market and also costs more. Releasing the software system too soon without adequate testing may cause customers’ dissatisfaction and may lead to failure of the software system in the market. In this paper we introduce cost model for each release of software based on debugging costs at different phases of software development viz-a-viz, testing and operational phase. Our model incorporates three new features that are not included in the literature. First, to the total cost incurred during the testing phase of new release, we add the debugging cost associated with remaining number of reported faults from previous release. Second, we consider that some of the remaining faults of previous release are partly removed during the testing phase and partly during the operational phase of new release. Third, we calculate the optimal testing time for each release of software in the presence of debugging costs associated from the previous releases. An Algorithm for finding optimal testing time for each version is developed. We estimate the parameters of the model using Statistical Package for Social Sciences on real data set and obtain optimum stopping time for each version of software using Maple software.
This is a preview of subscription content, log in via an institution to check access.
Similar content being viewed by others
References
Ali AI (2011) Software upgrade cost justification: making a case, In: Proceedings of Informing Science & IT Education Conference (InSITE)
Dalal SR, Mallows CL (1988) When should one stop testing software? J Am Stat Assoc 83:872–879
Ehrlich W, Prasanna B, Stampfel J, Wu J (1993) Determining the cost of a stop-test decision. IEEE Softw 10(2):33–42
Hu Q, Peng R, Levitin G (2012) Optimal distribution of software testing time considering multiple releases. Int J Perform Eng 8(6):705–707
Jain M, Handa BR (2001) Cost analysis for repairable units under hybrid warranty. In: Agarwal ML (ed) Recent developments in operational research. Narosa Publishing House, New Delhi, pp 149–165
Kapur PK, Garg RB (1990) Cost reliability optimum release policies for a software system with testing effort. Oper Res 27:109–116
Kapur PK, Garg RB, Kumar S (1999) Contributions to hardware and software reliability. World Scientific, Singapore
Kapur PK, Singh O, Garmabaki AS, Singh J (2010a) Multi up-gradation software reliability growth model with imperfect debugging. Int J Syst Assur Eng Manag 1:299–306
Kapur PK, Tondon A, Kaur G (2010) Multi up-gradation software reliability model, 2nd international conference on reliability, safety & hazard (ICRESH-2010), Mumbai, pp 468–474
Kapur PK, Garg RB, Aggarwal AG, Tandon A (2010) Two dimensional flexible software reliability growth model and related release policy. In: 4th National Conference; INDIACom-2010
Kapur PK, Pham H, Gupta A, Jha PC (2011) Software reliability assessment with OR applications. Springer, London
Kapur PK, Pham H, Aggarwal AG, Kaur G (2012) Two-dimensional multi-release software reliability modelling and optimal release planning. IEEE Trans Reliab 61(3):758–768
Lai R, Garg M, Kapur PK, Liu S (2010) A study of when to release a software product from the perspective of software reliability models. J Softw 6(4):651–661
McDaid K, Wilson SP (2001) Deciding how long to test software. Statistician 50:117–134
Musa JD, Iannino A, Okumoto K (1987) Software reliability, measurement, prediction and application. McGraw Hill, New York
Okumoto K, Goel AL (1980) Optimum release time for software system based on reliability and cost criteria. J Syst Softw 14:315–318
Okumoto K, Goel AL (1983) Optimal release time for computer software. IEEE Trans Softw Eng 9:323–327
Pham H (2000) Software reliability. Springer, Singapore
Pham H (2003) A software cost model with imperfect debugging, random life cycle and penalty cost. Int J Syst Sci 27:455–463
Pham H (2006) System software reliability. Springer-Verlag, London
Popstojanova KG, Trivedi KS (2001) Architecture-based approach to reliability assessment of software systems. Perform Eval 45:179–204
Tal U, McCollin C, Dell AB (2002) An optimal statistical testing policy for software reliability. Demonstr Saf Crit Syst 137(3):544–557
Williams DRP, Vivekanandan P (2005) Life-time warranty cost model for software reliability with discount rate. J Comput Sci 1:53–59
Wood (1996) Predicting software reliability. IEEE Comput 9:69–77
Xie M (1991) Software reliability modeling. World Scientific Publishing, Singapore
Xie M, Yang B (2003) A study of the effect of imperfect debugging on software development cost model. IEEE Trans Softw Eng 29(5):471–473
Yamada S (1994) Optimal release problems with warranty period based on a software maintenance cost model. Trans IPS Jpn 35(9):2197–2202
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
About this article
Cite this article
Kapur, P.K., Sachdeva, N. & Singh, J.N.P. Optimal cost: a criterion to release multiple versions of software. Int J Syst Assur Eng Manag 5, 174–180 (2014). https://doi.org/10.1007/s13198-014-0228-3
Received:
Published:
Issue Date:
DOI: https://doi.org/10.1007/s13198-014-0228-3