Abstract
PurposeCost-benefit (C/B) analysis helps to determine the economic feasibility of business software investments. Research literature and published practices do not recognize substantial software maintenance costs in C/B analysis. Current analyses emphasize the benefits of an initial investment but do not consider the recurring benefits of each enhancement during the software lifecycle. Such analyses could lead to incorrect investment decisions and lost business opportunities. This article aims to review current research on software lifecycle costs and develop a theoretically sound C/B analysis.Design/methodology/approachThis article reviews current C/B analyses and discusses their shortcomings in treating the significant recurring maintenance costs. It analyzes the findings of various studies on software maintenance and synthesizes these findings to identify the nature of various maintenance costs and their benefits. Based on the synthesis, it theorizes various cost and benefit elements for inclusion in a revised C/B analysis.FindingsThis article identifies each recurring maintenance cost relevant to C/B analysis. It also identifies recurring benefits from each enhancement that hitherto have been omitted. Finally, this article discusses how these costs and benefits should be treated in the revised C/Bs analysis.Research limitations/implicationsThis is a conceptual paper proposing a new C/B analysis and requires an empirical validation.Practical implicationsThis article provides a revision of the C/B analysis that is long overdue. It will help to justify a software investment correctly, rank software projects that compete for limited funds and help create a sound software project portfolio. Since 20% of software products may incur 80% of software investment, this analysis will help to make correct software investments and avoid lost business opportunities. This article also describes a practical method to use the revised C/B analysis.Originality/valueThis article provides a revision of the C/B analysis that is long overdue. It will help to justify a software investment correctly, rank software projects that compete for limited funds and help create a sound software project portfolio. Since 20% of software products may incur 80% of software investment, this analysis will help to make correct software investments and avoid lost business opportunities. This article also describes a practical method to use the revised C/B analysis.
Reference56 articles.
1. Framework for using cost-benefit analysis in making the case for software upgrade;Issues in Informing Science and Information Technology,2012
2. The financial aspect of managing technical debt: a systematic literature review;Information and Software Technology,2015
3. Financial appraisal and the IS/IT investment decision-making process;Journal of Information Technology,1998
4. Software complexity and maintenance costs;Communications of the ACM,1993