The DOI matches its Crossref record; 11 of the 11 references it cites were found in a registry or an index.
Analysis of Legacy System in Software Application Development: A Comparative Survey
Open accessAbstract
Software evolution is one of the challenging issues in today’s business environment. It is necessary for the organizations, which make use of Information, and Communication Technologies will have to align their business processes to compete with global business. The existing large software systems (“legacy” systems) have never been built to cope with the current business requirement for their poor coding, design structures, logic and documentation. Moreover, Legacy applications have various problems such as lack of up to-date documentation, skilled man power, resources of the Legacy applications, and high maintenance costs. Even though the Legacy system is obsolete, it contains detailed business rules and in continuous use, because it satisfies the users' needs and forms the backbone of the information flow of organization. One of the possible solutions is to refactor or modernize those systems into a new platform. It is necessary to analyse the existing legacy system for better understanding the business logic and its functionalities. This paper analyses various techniques proposed for understanding Legacy systems in existence.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
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 the citing paper
“Unlike the greenfield programming tasks commonly assigned in academic settings, where students start from scratch, brownfield programming tasks require students to integrate new code into existing code bases, which, because they are written by others, can be difficult to understand and modify [38].”
From The Effects of GitHub Copilot on Computing Students' Programming Effectiveness, Efficiency, and Processes in Brownfield Coding Tasks (2025) · cites this paper as [38]
Citations
Cites
Analyzing the reuse potential of migrating legacy components to a service-oriented architecture
Lewis, G. A., Morris, E., & Smith, D. (2006) · Euromicro Conference on Software Maintenance and Reengineering (CSMR) · doi:10.1109/csmr.2006.9 · Cited by 62
Khadka, R., Saeidi, A., Idu, A., Hage, J., & Jansen, S. (2012) · IGI Global eBooks · doi:10.4018/978-1-4666-2488-7.ch003 · Cited by 52
A Case Study on Software Evolution towards Service-Oriented Architecture
Cuadrado, F., García, B., Dueñas, J. C., & G., H. A. P. (2008) · International Conference on Advanced Information Networking and Applications Workshops (WAINA) · doi:10.1109/waina.2008.296 · Cited by 51
Extracting ontologies from legacy systems for understanding and re-engineering
Yang, H., Cui, Z., & O’Brien, P. (2003) · IEEE Annual International Computer Software and Applications Conference (COMPSAC) · doi:10.1109/cmpsac.1999.812512 · Cited by 33
GAMBUSE: A Gap Analysis Methodology for Engineering SOA-Based Applications
Nguyen, D. K., van den Heuvel, W., Papazoglou, M. P., de Castro, V., & Marcos, E. (2009) · Lecture notes in computer science · doi:10.1007/978-3-642-02463-4_16 · Cited by 21
Marchetto, A., & Ricca, F. (2008) · IEEE International Symposium on Web Site Evolution (WSE) · doi:10.1109/wse.2008.4655392 · Cited by 18
Alahmari, S. A., Roure, D. D., & Zaluska, E. (2010) · IEEE International Enterprise Distributed Object Computing Conference Workshops (EDOCW) · doi:10.1109/edocw.2010.28 · Cited by 15
Lewis, G. A., & Smith, D. B. (2007) · Springer eBooks · doi:10.1007/978-3-540-75912-6_17 · Cited by 11
Huang, H. Y., Tan, H. F., Zhu, J., & Zhao, W. M. (2008) · Lecture notes in computer science · doi:10.1007/978-3-540-68073-4_24 · Cited by 9
Salama, R. A., & Aly, S. G. (2008) · Software Engineering Research and Practice · Cited by 9
Cited by
Shihab, M. I. H., Hundhausen, C., Tariq, A., Haque, S., Qiao, Y., & Mulanda, B. W. (2025) · Proceedings of the 2025 ACM Conference on International Computing Education Research V.1 · doi:10.1145/3702652.3744219 · Cited by 28
Legacy Systems Modernisation for Citizen-Centric Digital Government: A Conceptual Model
Bakar, H. K. A., Razali, R., & Jambari, D. I. (2021) · Sustainability · doi:10.3390/su132313112 · Cited by 17
A Guidance to Legacy Systems Modernization
Bakar, H. K. A., Razali, R., & Jambari, D. I. (2020) · International Journal on Advanced Science Engineering and Information Technology · doi:10.18517/ijaseit.10.3.10265 · Cited by 15
Explaining the Business-Technological Age of Legacy Information Systems
Rosenkranz, S., Staegemann, D. G., Volk, M., & Turowski, K. (2024) · IEEE Access · doi:10.1109/access.2024.3414377 · Cited by 20
Software obsolescence risk assessment approach using multicriteria decision‐making
Bowlds, T. F., Fossaceca, J. M., & Iammartino, R. (2018) · Systems Engineering · doi:10.1002/sys.21446 · Cited by 11
Metadata
- Authors
- Srinivas, M., Ramakrishna, G., Rao, K. R., & Babu, E. S.
- Affiliations
- Koneru Lakshmaiah Education Foundation (IN)
- ORCID
- Babu, E. Suresh
- Venue
- International Journal of Electrical and Computer Engineering (IJECE)
- Published
- 2016-02-01
- Volume
- 6
- Issue
- 1
- Pages
- 292
- ISSN
- 2088-8708 (ISSN-L)
- OpenAlex
- W2277756685
- Cited by
- 26
- References
- 11
- Citations by year
- 2026: 2 · 2025: 5 · 2024: 2 · 2023: 2 · 2022: 2 · 2021: 4 · 2020: 2 · 2019: 2 · 2018: 3 · 2017: 2
- FWCI
- 5.21
- Type
- journal article
- Language
- en
- Open access
- diamond
- doi.org
- Licence
- Locations
- International Journal of Electrical and Computer Engineering (IJECE) (publishedVersion, cc-by-nc-nd)
- International Journal of Electrical and Computer Engineering (IJECE) (publishedVersion, cc-by-sa)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
- Physical Sciences › Computer Science › Software › Model-Driven Software Engineering Techniques
- Keywords
- legacy systems, software evolution, refactoring, modernization, software maintenance costs, documentation deficiencies
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
