system integration
The current issue and full text archive of this journal is available at www.emeraldinsight.com/0263-5577.htm What is integration?
What is integration? Thomas Gulledge
George Mason University, Fairfax, Virginia, USA
Abstract
5
Purpose – This paper aims to provide a clarification of the meaning of the term integration.
Design/methodology/approach – A taxonomy of integration definitions derived from the academic and trade literature is developed, analyzed, and documented.
Findings – Integration is a word that is commonly used when discussing enterprise applications.
The term integration is inserted in technical papers, e-mail messages, correspondence, proposals, and even causal conversations. After many years of project work, and many misunderstandings and failed meetings and workshops, it can only be stated that the word has multiple and misunderstood meanings. For technical papers (research and trade), the term must be provided with context, or it is impossible to have a meaningful conversation. Next, multiple alternative definitions (that are valid in the literature for the appropriate context) are presented and explained in some detail.
Research limitations/implications – The paper is not exhaustive, since new definitions of integration may exist or may emerge.
Originality/value – The main contribution of the paper is that it yields clarity on a key term that is frequently used in information systems research. The paper is useful to any researchers or practitioners who are focused on enterprise system implementation.
Keywords Integration, Interface management, Applications, Information systems, Research
Paper type General review
Introduction and importance
Integration is a common term in the enterprise systems literature. Seldom does a meeting occur when the word is not used multiple times and often within quite technical contexts. Unfortunately, our experience is that individuals often have a different understanding of the
What is integration? Thomas Gulledge
George Mason University, Fairfax, Virginia, USA
Abstract
5
Purpose – This paper aims to provide a clarification of the meaning of the term integration.
Design/methodology/approach – A taxonomy of integration definitions derived from the academic and trade literature is developed, analyzed, and documented.
Findings – Integration is a word that is commonly used when discussing enterprise applications.
The term integration is inserted in technical papers, e-mail messages, correspondence, proposals, and even causal conversations. After many years of project work, and many misunderstandings and failed meetings and workshops, it can only be stated that the word has multiple and misunderstood meanings. For technical papers (research and trade), the term must be provided with context, or it is impossible to have a meaningful conversation. Next, multiple alternative definitions (that are valid in the literature for the appropriate context) are presented and explained in some detail.
Research limitations/implications – The paper is not exhaustive, since new definitions of integration may exist or may emerge.
Originality/value – The main contribution of the paper is that it yields clarity on a key term that is frequently used in information systems research. The paper is useful to any researchers or practitioners who are focused on enterprise system implementation.
Keywords Integration, Interface management, Applications, Information systems, Research
Paper type General review
Introduction and importance
Integration is a common term in the enterprise systems literature. Seldom does a meeting occur when the word is not used multiple times and often within quite technical contexts. Unfortunately, our experience is that individuals often have a different understanding of the
References: Anonymous (1999), “Integrate with R/3”, Enterprise Development, Vol. 1 No. 8, pp. 25-6. Farrell, J. (2001), ERP Financial Interfaces, (Power Point Presentation), Defense Financial and Accounting Services, August. Ferguson, R.B. and Callaghan, D. (2002), “Tools to ease integration”, eWeek, Vol. 19 No. 15, p. 12. Gulledge, T.R. and Sommer, R. (2003), “Public sector enterprise resource planning”, Industrial Management & Data Systems, Vol Gulledge, T.R. and Sommer, R. (2004), “Splitting the SAP instance: lessons on scope and business processes”, Journal of Computer Information Systems, Vol Gulledge, T.R., Simon, G. and Sommer, R. (2004), “Analyzing convergence alternatives across existing SAP solutions”, Industrial Management & Data Systems, Vol Gulledge, T.R., Hafez, W., Ledwon, M. and Svensson, C. (2005), “Solution architecture alignment for logistics portfolio management”, International Journal of Services and Standardsin Kangas, M. (2005), Introduction to the SAP Web Application Server, SAP AG, Walldorf. Linthicum, D.S. (2001), “Where EAI meets B2B”, Software Magazine, Vol. 21 No. 2, pp. 22-5. SAP AG (2004), Enterprise Services Architecture: An Introduction, SAP AG, Walldorf. Sivan, S.S. and Venkatavaradan, R. (2005), “Design guidelines: building web service wrappers for an XML-based system”, DevX, available at: www.devx.com/enterprise/Article/27882 Woods, D. (2003), Packaged Composite Applications: An O’Reilly Field Guide to Enterprise Software, O’Reilly Publications, Sebastopol, CA. Zeng, A.Z. and Phatak, B.K. (2003), “Achieving information integration in supply chain management through B2B e-hubs: concepts and analyses”, Industrial Management & Data Joch, A. (2005), “Modern design”, Oracle Magazine, May-June.