Using Software Product Line to improve ERP Engineering: Literature Review and Analysis
Abstract
On the one hand, getting advantages of Enterprise Resource Planning (ERP) systems largely depends on their capacity to be configured and adapted to fit the customer and domain requirements. On the other hand, product line engineering (PLE) is a promising approach for configuring and adapting products by means of configuration and derivation processes. While the literature and industrial experiences show the benefits of PLE methods, techniques and tools, there is still a lack of interest in addressing ERP engineering issues with the product line strategy. Objective: The aim of this paper is to identify and analyze the different ways presented in the literature to improve ERP engineering issues with the methods, techniques and tools provided by PLE. Method: To achieve that objective, we reviewed the literature and analyzed available publications. Results: This literature review analyzes six research papers at the intersection between ERP and PLE. It shows that the product line strategy can indeed be applied for ERP configuration and customization. It further shows the evolving interest on this topic and discusses existing contributions.
Downloads
References
M. Newman andY. Zhao, “The process of enterprise resource planning implementation and business process re-engineering: tales from two Chinese small and medium-sized enterprises”, Information Systems Journal, vol. 18, no4, p. 405–426, 2008.
H. H. Chang, “Technical and management perceptions of enterprise information system importance, implementation and benefits”, Information Systems Journal, vol. 16, no3, p. 263‑292, 2006.
S. Pekkola, E.Niemi, M. Rossi, M. Ruskamo, andT. Salmimaa, “ERP Research At ECIS And ICIS: A Fashion Wave Calming Down?”, in Proceedings of the European Conference on IS (ECIS), Utrecht, NL, 2013.
A. Al-Mudimigh, M. Zairi, andM. Al-Mashari, “ERP software implementation: an integrative framework”, Eur J Inf Syst, vol. 10, no4, p. 216‑226, 2001.
A. Parr andG. Shanks, “A model of ERP project implementation”, Journal of Information Technology, vol. 15, no4, p. 289‑303, 2000.
M. L. Markus, C. Tanis, and P. C. Van Fenema, “Multisite ERP implementations”, Communications of the ACM, vol. 43, no4, p. 42–46, 2000.
A. Davis, “ERP Customization Impacts on Strategic Alignment and Systems Alignment”, SAIS Proceedings of the Southern Association of IS (SAIS), vol. Paper 45, 2005.
M. Rosemann, “Requirements Engineering for Enterprise Systems”, in Proceedings of the American Conf. on IS (AMCIS), 2001.
M. Daneva, “Lessons learnt from five years of experience in ERP requirements engineering”, in Proceedings 11th IEEE Int. Req. Eng. Conference (RE’2003), 2003, p. 45‑54.
J. Bosch, “Design and use of software architectures: adopting and evolving a product-line approach”. Pearson Education, 2000.
P. Clements andL. Northrop, Software product lines: practices and patterns, vol. 59. Addison-Wesley Reading, 2002.
P. Sawyer, R. Mazo, D. Diaz, C. Salinesi, andD. Hughes, “Using Constraint Programming to Manage Configurations in Self-Adaptive Systems”, Computer, vol. 45, no10, p. 56‑63, 2012.
S. Ouali, N. Kraiem, andH. Ben Ghezala, “Framework for Evolving Software Product Line”, International Journal of Software Engineering & Applications, vol. 2, no2, 2011.
K. C. Kang, S. G. Cohen, J. A. Hess, W. E. Novak, and A. S. Peterson, “Feature-oriented domain analysis (FODA) feasibility study”, DTIC Document, 1990.
D. Dhungana, R. Rabiser, and P. Grunbacher, “Decision-Oriented Modelingof Product Line Architectures”, in The Working IEEE/IFIP Conference on Software Architecture (WICSA’07), 2007, p. 22‑22.
C. Salinesi,R. Mazo, O. Djebbi, D. Diaz, and A. Lora-Michiels, “Constraints: The core of product line engineering”, in Proceedings of the 5th Int’l Conf. on Research Challenges in Information Science (RCIS’11), 2011, p. 1‑10.
R. Mazo, C. Salinesi, D. Diaz, and others, “Abstract Constraints: A General Framework for Solver-Independent Reasoning on Product LineModels”, INSIGHT-Journal of International Council on Systems Engineering (INCOSE), vol. 14, no4, 2011.
K. Pohl, G. Böckle, andF. vann der Linden, Software Product Line Engineering: Foundations, Principles and Techniques. Springer, 2005.
M. Daneva and R. J. Wieringa, “Requirements Engineering for Enterprise Systems: What We Know and What We Don’t Know?”in Intentional Perspectives on Information Systems Engineering, Springer, 2010, p. 115–136.
T. H. Davenport, “Putting the enterprise into the enterprise system”, Harvard Business Review, vol. 76, no4, 1998.
M. Bradford, Modern ERP: Select, Implement and Use Today’s Advanced Business Systems. Lulu.com, 2010.
B. A. Kitchenham and S. Charters, “Guidelines for performing Systematic Literature Reviews in Software Engineering -Version 2.3”, Keele University, EBSE Technical Report, 2007.
B. A. Kitchenham, O. P. Brereton, M. Turner, M. Niazi, S. Linkman, R. Pretorius, and D. Budgen, “Refining the systematic literature review process—two participant-observer case studies”, Empirical Software Engineering, vol. 15, no6, p. 618‑653, 2010.
G. A. Thomas and S. Jajodia, “Commercial-off-the-shelf enterprise resource planning software implementations in the public sector: practical approachesfor improving project success”, Journal of Government Financial Management, vol. 53, no2, p. 12–19, 2004.
P. Grünbacher, R. Rabiser, D. Dhungana, and M. Lehofer, “Model-Based Customization and Deployment of Eclipse-BasedTools: Industrial Experiences”, in 24th IEEE/ACM Int’l Conf. on Automated Software Engineering (ASE’09), 2009, p. 247‑256.
This article is published by LAJC under a Creative Commons Attribution-Non-Commercial-Share-Alike 4.0 International License. This means that non-exclusive copyright is transferred to the National Polytechnic School. The Author (s) give their consent to the Editorial Committee to publish the article in the issue that best suits the interests of this Journal. Find out more in our Copyright Notice.
Disclaimer
LAJC in no event shall be liable for any direct, indirect, incidental, punitive, or consequential copyright infringement claims related to articles that have been submitted for evaluation, or published in any issue of this journal. Find out more in our Disclaimer Notice.