Untitled

Banker, Rajiv D.; Datar, Srikant M.; Kemerer, Chris F.; Zweig, Dani

doi:10.1023/a:1013156608583

Cited by 24 publications

(7 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Several studies have shown that annual maintenance costs increase with the age of the software (Ali, 2012; Banker et al. , 1993, Banker et al. , 2002; Chan et al.…”

Section: Drawbacks Of Current Cost-benefit Analysismentioning

confidence: 99%

“…, 2016) and the process of maintaining software degrades its structure gradually and further decreases its maintainability (Jones, 2006 ) . Maintenance is given a secondary role in many firms and it may not be as good as development and contribute to more corrective maintenance (Banker et al. , 2002; Kemerer, 1995; Zhang et al.…”

Section: C/b Analysis For Software Maintenancementioning

confidence: 99%

“…Several studies have shown that annual maintenance costs increase with the age of the software (Ali, 2012;Banker et al, 1993, Banker et al, 2002Chan et al, 1996). This increase can be attributed to a hidden component called deterioration.…”

Section: Drawbacks Of Current Cost-benefit Analysismentioning

confidence: 99%

“…Many software development methods do not explicitly consider maintainability (ease of maintenance) (Falessi et al, 2016) and the process of maintaining software degrades its structure gradually and further decreases its maintainability (Jones, 2006). Maintenance is given a secondary role in many firms and it may not be as good as development and contribute to more corrective maintenance (Banker et al, 2002;Kemerer, 1995;Zhang et al, 2001, Zhang et al, 2003. The age and failure to maintain the currency of system documentation may cause inappropriate architecture changes and violate original design artifacts (Eick et al, 2001).…”

Section: Hidden Cost Of Deteriorationmentioning

confidence: 99%

See 3 more Smart Citations

A critical review of cost-benefit analysis for business software investments

Sakthivel

2023

AJB

View full text Add to dashboard Cite

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.

show abstract

“…Several studies have shown that annual maintenance costs increase with the age of the software (Ali, 2012; Banker et al. , 1993, Banker et al. , 2002; Chan et al.…”

Section: Drawbacks Of Current Cost-benefit Analysismentioning

confidence: 99%

Section: C/b Analysis For Software Maintenancementioning

confidence: 99%

Section: Drawbacks Of Current Cost-benefit Analysismentioning

confidence: 99%

Section: Hidden Cost Of Deteriorationmentioning

confidence: 99%

See 2 more Smart Citations

A critical review of cost-benefit analysis for business software investments

Sakthivel

2023

AJB

View full text Add to dashboard Cite

show abstract

“…The basic idea with the use of SHR in software maintenance is to increase maintainers efficiency by providing them the relevant data, which should reduce their reliance on their intuition and experience. In addition, historical data on maintenance everyday practice can be used to support management activities within an organization [19,20,21], or as a source of valuable data for maintenance practice assessment and improvement [22,23].…”

Section: Software Maintenancementioning

confidence: 99%

Software maintenance improvement in small software companies: Reflections on experiences

Stojanov¹

2021

3rd International Workshop on Information, Computation, and Control Systems for Distributed Environments 2021

View full text Add to dashboard Cite

Software maintenance has been recognized as the most demanding and costly phase in the software life cycle. Software maintenance tasks, although require a more complex set of skills and knowledge, are far less interesting to software engineers than software development tasks. In addition, insight into the scholarly literature revealed that the knowledge basis on software maintenance is significantly less than the knowledge base on software development. Due to the obvious constraints of small software companies, they do not have time, people, and other resources for assessing and improving their software maintenance practice. This paper presents the author’s reflections on experience in assessing and improving software maintenance practice in an indigenous micro software company.

show abstract