Username   Password       Forgot your password?  Forgot your username? 


Effort-based Release and Patching Time of Software with Warranty using Change Point

Volume 15, Number 6, June 2019, pp. 1724-1733
DOI: 10.23940/ijpe.19.06.p24.17241733

Chetna Choudharya, P. K. Kapurb, Sunil K. Khatric, and A. K. Shrivastavad

aAmity School of Engineering and Technology, Amity University, Uttar Pradesh, 201313, India
bAmity Center for Interdisciplinary Research, Amity University, Uttar Pradesh, 201313, India
cAmity Institute of Information Technology, Amity University, Uttar Pradesh, 201313, India
dInternational Management Institute, Kolkata, West Bengal, 700027, India

(Submitted on October 3, 2017; Revised on February 27, 2018; Accepted on April 3, 2018)


Due to the high dependency on software, the measurement of its performance has become vital. It is a common practice in the software industry to test products exhaustively before release so that the maximum number of faults is detected and removed. Fault detection and the removal rate are governed by many factors such as changes in testing environment, testing strategies, skills, efficiency, etc. The point at which a change in the fault detection rate occurs is known as the change point. Due to the increasing demand of good quality software in a short span and to remain in the market competition, firms are providing warranties on their products to assure reliability. The defects reported during the operational phase are fixed by providing patches. However, delivering patches after release demands extra effort and resources, which is costly and hence not economical for the firms. Considering the above factors, an effort-based cost model with change point and warranty is proposed in this work to determine the optimum release and patch time of a software by minimizing the overall cost. A numerical illustration is provided to validate the proposed cost model.


References: 19

  1. P. K. Kapur, H. Pham, A. Gupta, and P. C. Jha, “Software Reliability Assessment with OR Application,” Springer, Berlin, 2011
  2. N. Ahmad, M. G. M. Khan, and L. S. Rafi, “A Study of Testing-Effort Dependent Inflection S-Shaped Software Reliability Growth Models with Imperfect Debugging,” International Journal of Quality & Reliability Management, Vol. 27, No. 1, pp. 89-110, 2010
  3. S. Yamada, H. Ohtera, and H. Narihisa, “Software Reliability Growth Models with Testing-Effort,” IEEE Transactions on Reliability, Vol. 35, No. 1, pp. 19-23, 1986
  4. C. Y. Huang and S. Y. Kuo, “Analysis of Incorporating Logistic Testing-Effort Function into Software Reliability Modeling,” IEEE Transactions on Reliability, Vol. 51, No. 3, pp. 261-270, 2002
  5. P. K. Kapur, D. N. Goswami, and A. Bardhan, “A General Software Reliability Growth Model with Testing Effort Dependent Learning Process,” International Journal of Modelling and Simulation, Vol. 27, No. 4, pp. 340-346, 2007
  6. P. K. Kapur, S. Ompal, A. G. Aggarwal, and R. Kumar, “Unified Framework for Developing Testing Effort Dependent Software Reliability Growth Models,” WSEAS Transactions on Systems, Vol. 4, No. 8, pp. 521-531, 2009
  7. S. Inoue and S. Yamada, “Lognormal Process Software Reliability Modeling with Testing-Effort,” Journal of Software Engineering and Applications, pp. 8-14, 2013
  8. Q. Zhao, J. Zheng, and J. Li, “Software Reliability Modeling with Testing-Effort Function and Imperfect Debugging,” TELKOMNIKA, Vol. 10, No. 8, pp. 1992-1998, 2012
  9. R. Peng, Y. F. Li, W. J. Zhang, and Q. P. Hu, “Testing Effort Dependent Software Reliability Model for Imperfect Debugging Process Considering Both Detection and Correction,” Reliability Engineering and System Safety, Vol. 126, pp. 37-43, 2014
  10. N. Zhang, G. Cui, and H. Liu, “Considering Detection Effort and Correction Effort for Software Reliability Analysis,” Journal of Computational Information Systems, Vol. 8, No. 19, pp. 7991-8000, 2012
  11. Q. Li, H. Li, and M. Lu, “Incorporating S-Shaped Testing-Effort Functions into NHPP Software Reliability Model with Imperfect Debugging,” Journal of Systems Engineering and Electronics, Vol. 26, No. 1, pp. 190-207, 2015
  12. P. K. Kapur, O. Singh, A. K. Shrivastava, and J. N. P. Singh, “A Software Up-Gradation Model with Testing Effort and Two Types of Imperfect Debugging,” in Proceedings of International Conference on Futuristic Trends in Computational Analysis and Knowledge Management, 2015
  13. M. Zhao, “Change-Point Problems in Software and Reliability,” Communications in Statistics Theory and Methods, Vol. 22, No. 3, pp. 757-768, 1993
  14. C. -Y. Huang and M. R. Lyu, “Optimal Release Time for Software Systems Considering Cost, Testing-Effort, and Test Efficiency,” IEEE Transactions on Reliability, Vol. 54, pp. 583-591, 2005
  15. P. K. Kapur, S. K. Khatri, O. Singh, and A. K. Shrivastava, “When to Stop Testing under Warranty using SRGM with Change Point,” in Proceedings of International Conference on IT in Business, Industry & Govt., pp. 200-205, 2014
  16. C. Luo, H. Okamura, and T. Dohi, “Optimal Planning for Open Source Software Updates,” in Proceedings of the Institution of Mechanical Engineers Part O Journal of Risk and Reliability, 2015
  17. D. Dey, A. Lahiri, and G. Zhang, “Optimal Policies for Security Patch Management,” INFORMS Journal on Computing, Vol. 27, No. 3, pp. 462-477, 2015
  18. A. Tickoo, P. K. Kapur, and A. K. Shrivastava, “Testing Effort based Modeling to Determine Optimal Release and Patching Time of Software,” International Journal of System Assurance Engineering and Management, Vol. 7, No. 4, pp. 427-434, 2016
  19. M. Obha, “Software Reliability Analysis Models,” IBM Journal of Research Development, Vol. 28, No. 4, pp. 428-443, 1984


Please note : You will need Adobe Acrobat viewer to view the full articles.Get Free Adobe Reader

This site uses encryption for transmitting your passwords.