The maintenance implications of the customization of ERP software
Open accessThe DOI matches its Crossref record; 3 of the 3 references it cites were found in a registry or an index.
Abstract
Enterprise resource planning (ERP) software is a dominant approach for dealing with legacy information system problems. In order to avoid invalidating maintenance and development support from the ERP vendor, most organizations reengineer their business processes in line with those implicit within the software. Regardless, some customization is typically required. This paper presents two case studies of ERP projects where customizations have been performed. The case analysis suggests that while customizations can give true organizational benefits, careful consideration is required to determine whether a customization is viable given its potential impact upon future maintenance. Copyright © 2001 John Wiley & Sons, Ltd.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Programs, life cycles, and laws of software evolution
Lehman, M. M. (1980) · Proceedings of the IEEE · doi:10.1109/proc.1980.11805 · Cited by 1,181
Enterprise resource planning: cultural fits and misfits: is ERP a universal solution?
Soh, C., Kien, S. S., & Tay-Yap, J. (2000) · Communications of the ACM · doi:10.1145/332051.332070 · Cited by 686
Risk factors in enterprise-wide/ERP projects
Sumner, M. (2000) · Journal of Information Technology · doi:10.1177/026839620001500407 · Cited by 559
Cited by
Critical Success Factors for Enterprise Resource Planning Implementation and Upgrade
Nah, F. F.-H., & Delgado, S. (2006) · Journal of Computer Information Systems · doi:10.1080/08874417.2006.11645928 · Cited by 399
Enterprise Resource Planning (ERP): a review of the literature
Moon, Y. B. (2007) · International Journal of Management and Enterprise Development · doi:10.1504/ijmed.2007.012679 · Cited by 328
“Eight articles address the ‘Maintenance’ issues in ERP systems.”
BackgroundERP system implementation in large enterprises—A systematic literature review
Ali, M., & Miller, L. (2017) · Journal of Enterprise Information Management · doi:10.1108/jeim-07-2014-0071 · Cited by 221
Pollock, N., Williams, R., & Procter, R. (2003) · Technology Analysis & Strategic Management · doi:10.1080/09537320310001601504 · Cited by 96
Deep Learning for Enterprise Systems Implementation Lifecycle Challenges: Research Directions
Hassanien, H. E.-D., & Elragal, A. (2021) · Informatics · doi:10.3390/informatics8010011 · Cited by 5
Metadata
- Authors
- Light, B.
- Venue
- Journal of Software Maintenance and Evolution: Research and Practice
- Publisher
- Wiley
- Published
- 2001-11
- Volume
- 13
- Issue
- 6
- Pages
- 415-429
- ISSN
- 1532-060X (ISSN-L)
- 1532-0618
- OpenAlex
- W2083414383
- Cited by
- 139
- References
- 3
- FWCI
- 13.24
- Type
- journal article
- Language
- en
- Open access
- green
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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: The maintenance implications of the customization of ERP software. https://app.cochat.ai/papers/10.1002/smr.240
- The paper
- Light, B. (2001). The maintenance implications of the customization of ERP software. Journal of Software Maintenance and Evolution: Research and Practice. https://doi.org/10.1002/smr.240
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.