Same Words, Different Meanings: Are Basic IS/IT Concepts Our Self-Imposed Tower Of Babel?

This article began as a response to an exchange of letters concerning the need for more vs. less user participation in IS projects. It grew into an exploration of whether and how ten 1999 CAIS articles use basic IS/IT terms with different meanings and connotations related to the different perspectives of their authors. The article characterizes differences between an IT perspective and a business perspective and categorizes the ten articles accordingly. It then presents numerous quotes from the articles to illustrate differences across the articles in terms of their use of eight basic concepts: system, user, stakeholder, IS project, implementation, reengineering, requirements, and solution. To help understand the differences and their significance, the article makes extensive use of distinctions between work systems, information systems, and projects. When applied to the articles these distinctions raise questions such as whether the term “system” refers to a work system, information system, or software, and whether the term “user” refers to hands-on users, people who receive information, or managers whose organizations use information systems. An underlying theme throughout is that the lack of conscious attention to the meaning of basic terms and points of reference may be a significant impediment to effective communication and to our ability to make sense out of research findings and even journalistic anecdotes about what seemed to work or not work in particular situations.

[1]  Ephraim R. McLean,et al.  Information Systems Success: The Quest for the Dependent Variable , 1992, Inf. Syst. Res..

[2]  D. Sandy Staples,et al.  Dimensions of Information Systems Success , 1999, Commun. Assoc. Inf. Syst..

[3]  Tony Elliman,et al.  Focus Issue on Legacy Information Systems and Business Process Change: The Role of Stakeholders in Managing Change , 1999, Commun. Assoc. Inf. Syst..

[4]  Rob Pooley,et al.  Legacy Information Systems and Business Process Change: A Patterns Perspective , 1999, Commun. Assoc. Inf. Syst..

[5]  Ben Light,et al.  Focus Issue on Legacy Information Systems and Business Process Change: A Business Perspective of Legacy Information Systems , 1999, Commun. Assoc. Inf. Syst..

[6]  M. Lynne Markus,et al.  If we build it, they will come: Designing information systems that people want to use , 1994 .

[7]  Jane Fedorowicz,et al.  Assessing Risks in Two Projects: A Strategic Opportunity and a Necessary Evil , 1999, Commun. Assoc. Inf. Syst..

[8]  George M. Giaglis,et al.  Focus Issue on Legacy Information Systems and Business Process Change: On the Integrated Design and Evaluation of Business Processes and Information Systems , 1999, Commun. Assoc. Inf. Syst..

[9]  Kostas S. Metaxiotis,et al.  Evaluating the Integrated Measurement and Evaluation System IMES: A Success Story , 1999, Commun. Assoc. Inf. Syst..

[10]  Steven L. Alter A General, Yet Useful Theory of Information Systems , 1999, Commun. Assoc. Inf. Syst..

[11]  Ben Light,et al.  Focus issue on legacy information systems and busines process engineering: a business perspective of legacy information systems , 1999 .

[12]  Pericles Loucopoulos,et al.  Focus Issue on Legacy Information Systems and Business Process Change: Modelling of Organisational Change Using the EKD Framework , 1999, Commun. Assoc. Inf. Syst..

[13]  Steven L. Alter,et al.  Information Systems: A Management Perspective , 1991 .

[14]  Lorne Olfman,et al.  The role of the end user: letters , 1999 .

[15]  Allen S. Lee Rigor and relevance in MIS research: beyond the approach of positivism alone , 1999 .

[16]  Michael Stonebraker,et al.  Migrating Legacy Systems: Gateways, Interfaces, and the Incremental Approach , 1995 .

[17]  Lynda M. Applegate,et al.  Rigor and Relevance in MIS Research-Introduction , 1999 .

[18]  Jaak Jurison,et al.  Software Project Management: The Manager's View , 1999, Commun. Assoc. Inf. Syst..

[19]  Alan O'Callaghan,et al.  Focus Issue on Legacy Information Systems and Business Process Change: Migrating Large-Scale Legacy Systems to Component-Based and Object Technology: The Evolution of a Pattern Language , 1999, Commun. Assoc. Inf. Syst..

[20]  Izak Benbasat,et al.  Empirical Research in Information Systems: The Practice of Relevance , 1999, MIS Q..

[21]  Cynthia Mathis Beath,et al.  The Contradictory Structure of Systems Development Methodologies: Deconstructing the IS-User Relationship in Information Engineering , 1994, Inf. Syst. Res..

[22]  Elayne Coakes,et al.  Focus issue on legacy information systems and business process engineering: the role of stakeholders in managing change , 1999 .

[23]  Tom Rodden,et al.  Focus Issue on Legacy Information Systems and Business Process Change: Banking on the Old technology: Understanding the Organisational Context of 'Legacy' Issues , 1999, Commun. Assoc. Inf. Syst..

[24]  F. W. McFarlan,et al.  Portfolio approach to information systems , 1989 .

[25]  Blake Ives,et al.  User Involvement and MIS Success: A Review of Research , 1984 .