A Review on Software Maintenance Issues and How to Reduce Maintenance Efforts
Open accessAbstract
Software Maintenance and evolution are identifying by their huge cost and slow speed of implementation.Survey showed that around 60% of the maintenance effort was on the total cost of software.But after delivering the software to the client, the maintenance work begins.This paper suggests some issues and problems faced by software maintenance process.There are some issues of software maintenance i.e.: database size, system age, maintenance budget, system size, staff size or restructuring for change.This paper presents several ways to reduce cost and efforts involved in software maintenance.Software maintenance costs can be reduced significantly if the software architecture is well defined, clearly documented, and creates an environment that promotes design consistency through the use of guidelines and testing quality.
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
In practice, up to 80% of effort is spent maintaining and evolving legacy code, requiring coordinated changes across modules, versions, and specifications.
“In practice, up to 80% of effort is spent maintaining and evolving legacy code, requiring coordinated changes across modules, versions, and specifications (Kaur and Singh, 2015; Singh et al., 2019).”
From SWE-EVO: Benchmarking Coding Agents in Long-Horizon Software Evolution Scenarios (2025) · cites this paper as Kaur and Singh, 2015
Section 2.3, “Change Implementation” (page unavailable), describes changes propagating between components, and section 2.22 discusses maintaining legacy systems. The paper does not establish that up to 80% of effort is spent maintaining and evolving legacy code: its Abstract instead gives an approximate 60% figure for maintenance's share of software cost. The cited passages also do not establish coordinated changes across versions and specifications. (LLM, conf=0.86)
Experimental — accuracy not yet measuredSWE-Bench focuses on discrete issue resolution and does not capture the core SE challenge: continuous evolution of existing systems.
“SWE-Bench focuses on discrete issue resolution and does not capture the core SE challenge: continuous evolution of existing systems (Kaur and Singh, 2015; Singh et al., 2019).”
From SWE-EVO: Benchmarking Coding Agents in Long-Horizon Software Evolution Scenarios (2025) · cites this paper as Kaur and Singh, 2015
The Introduction describes maintenance as modifying a software product after delivery to meet new requirements, supporting the importance of evolving existing systems. The paper does not discuss SWE-Bench or establish that discrete issue resolution fails to capture that challenge. (LLM, conf=0.85)
Experimental — accuracy not yet measured
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Cites
No references could be resolved yet.
Research works printed but not linked: 4
- Bennett, K. H., "Legacy Systems: Coping with Success", IEEE Software, 12(1):19-23, 1995.
- Bennett, K. H., Ramage, M., Munro, M., "Decision Model for Legacy Systems", IEE Proceedings on Software, 146(3):153-159, 1999.
- International Journal of Technical Research and Applications e-ISSN: 2320-8163, www.ijtra.com Volume 2, Issue 6 (Nov-Dec 2014),"DEVELOPMENT OF A SOFTWARE MAINTENANCE COST ESTIMATION MODEL" 4TH GL PERSPECTIVE Mohammad Islam1, Dr. Vinodani Katiyar2 1Research Scholar, Shri Venkateshwara University,Gajraula, UP, India 2Professor, SRM, University, Lucknow, UP, India 1mohdislam3@gmail.com, 2drvinodani@gmail.com.
- W. Li and S. Henry. Maintenance Metrics for the Object Oriented Paradigm. In IEEE Proc. of the 1 st Int. Sw. Metrics Symposium, pages 52{60, May 1993.
Cited by
Sorted by citations
SWE-EVO: Benchmarking Coding Agents in Long-Horizon Software Evolution Scenarios
Le, T., Thai, M. V. T., Manh, D. N., Nhat, H. P., & Bui, N. D. Q. (2025) · arXiv · doi:10.48550/arxiv.2512.18470
“In contrast to isolated issue resolution, real-world software evolution involves interpreting high-level requirements, planning multi-step modifications, and navigating large-scale repositories across versions (Kaur and Singh, 2015; Singh et al., 2019).”
- Authors
- Kaur, U., & Singh, G.
- Venue
- International Journal of Computer Applications
- Publisher
- Foundation of Computer Science
- Published
- 2015-05-20
- Volume
- 118
- Issue
- 1
- Pages
- 6-11
- ISSN
- 0975-8887 (ISSN-L)
- OpenAlex
- W631877113
- Cited by
- 15
- References
- 0
- Citations by year
- 2026: 1 · 2025: 2 · 2024: 2 · 2023: 1 · 2022: 3 · 2021: 2 · 2020: 2 · 2019: 1 · 2016: 1
- FWCI
- 0.90
- Type
- journal article
- Language
- en
- Open access
- bronze
- doi.org
- Locations
- International Journal of Computer Applications (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Physical Sciences › Computer Science › Artificial Intelligence › Advanced Software Engineering Methodologies
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Keywords
- software maintenance, maintenance cost reduction, software evolution, software architecture, software documentation, design consistency, maintenance budget, database size, system age, software restructuring
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
