A study of the effect of imperfect debugging on software development cost

2003 ◽  
Vol 29 (5) ◽  
pp. 471-473 ◽  
Author(s):  
Min Xie ◽  
Bo Yang
2019 ◽  
Vol 37 (9/10) ◽  
pp. 1233-1257
Author(s):  
Vibha Verma ◽  
Sameer Anand ◽  
Anu Gupta Aggarwal

Purpose The purpose of this paper is to identify and quantify the key components of the overall cost of software development when warranty coverage is given by a developer. Also, the authors have studied the impact of imperfect debugging on the optimal release time, warranty policy and development cost which signifies that it is important for the developers to control the parameters that cause a sharp increase in cost. Design/methodology/approach An optimization problem is formulated to minimize software development cost by considering imperfect fault removal process, faults generation at a constant rate and an environmental factor to differentiate the operational phase from the testing phase. Another optimization problem under perfect debugging conditions, i.e. without error generation is constructed for comparison. These optimization models are solved in MATLAB, and their solutions provide insights to the degree of impact of imperfect debugging on the optimal policies with respect to software release time and warranty time. Findings A real-life fault data set of Radar System is used to study the impact of various cost factors via sensitivity analysis on release and warranty policy. If firms tend to provide warranty for a longer period of time, then they may have to bear losses due to increased debugging cost with more number of failures occurring during the warrantied time but if the warranty is not provided for sufficient time it may not act as sufficient hedge during field failures. Originality/value Every firm is fighting to remain in the competition and expand market share by offering the latest technology-based products, using innovative marketing strategies. Warranty is one such strategic tool to promote the product among masses and develop a sense of quality in the user’s mind. In this paper, the failures encountered during development and after software release are considered to model the failure process.


2012 ◽  
Vol 32 ◽  
pp. 285-291 ◽  
Author(s):  
Ricardo de A. Araújo ◽  
Adriano L.I. Oliveira ◽  
Sergio Soares ◽  
Silvio Meira

2008 ◽  
Vol 81 (11) ◽  
pp. 1853-1867 ◽  
Author(s):  
K. Vinay Kumar ◽  
V. Ravi ◽  
Mahil Carr ◽  
N. Raj Kiran

Author(s):  
Sabrina Ahmad ◽  
Noor Azilah Muda ◽  
Azah Kamilah Muda ◽  
Zahriah Othman

1995 ◽  
Vol 31 (2) ◽  
pp. 125-134 ◽  
Author(s):  
Albert L. Lederer ◽  
Jayesh Prasad

Sign in / Sign up

Export Citation Format

Share Document