Cross-contextual use of integrated information systems

Many organizations now purchase and customize software rather than build information systems. In this light, some argue that high-level data modeling no longer has a role. In this paper, we examine the contemporary relevance of high-level data modeling. We addressed this issue by asking 21 experienced data-modeling practitioners to reflect on their work and to give their opinions on trends and future directions in high-level data modeling. We analyzed transcripts of our interviews with them using Klein and Myers’s (1999) framework for qualitative research. We found considerable variation in the practice of high-level data modeling. We also found that high-level data modeling is still considered important, even though organizations ultimately may purchase off-the-shelf software. The reason is that high-level data modeling assists organizations to obtain clarity about IT project scope and requirements, thereby reducing the risk that costly implementation mistakes will be made.

[1]  T. Davenport.  Putting the enterprise into the enterprise system. , 1998, Harvard business review.

[2]  David C. Hay,et al.  Data model patterns : a metadata map , 2006 .

[3]  Karlheinz Kautz,et al.  The Utilization of Information Systems Development Methodologies in Practice , 2004 .

[4]  M. Markus,et al.  The Enterprise System Experience— From Adoption to Success , 2000 .

[5]  H. V. Jagadish,et al.  Database Modeling and Design: Logical Design , 2011 .

[6]  Graeme G. Shanks,et al.  Understanding corporate data models , 1999, Inf. Manag..

[7]  Ralph Kimball,et al.  The Data Warehouse Lifecycle Toolkit: Expert Methods for Designing, Developing and Deploying Data Warehouses with CD Rom , 1998 .

[8]  J. Morse.  Qualitative data analysis (2nd ed): Mathew B. Miles and A. Michael Huberman. Thousand Oaks, CA: Sage Publications, 1994. Price: $65.00 hardback, $32.00 paperback. 238 pp , 1996 .

[9]  Peter B. Seddon,et al.  Assessing and managing the benefits of enterprise systems: the business manager's perspective , 2002, Inf. Syst. J..

[10]  E. F. Codd,et al.  A relational model of data for large shared data banks , 1970, CACM.

[11]  Marta Indulska,et al.  How do practitioners use conceptual modeling in practice? , 2006, Data Knowl. Eng..

[12]  Peter B. Seddon,et al.  A content-analytic study of the advantages and disadvantages of process modelling , 2003 .

[13]  Julie E. Kendall,et al.  Systems analysis and design , 1981 .

[14]  Carl L. Gordon,et al.  Systems Analysis and Design: Current Practices , 1987, MIS Q..

[15]  Dinesh Batra,et al.  Conceptual Data Modeling Patterns: Representation and Validation , 2005, J. Database Manag..

[16]  Dinesh Batra,et al.  Cognitive complexity in data modeling: causes and recommendations , 2007, Requirements Engineering.

[17]  Christiane Floyd,et al.  A Comparative Evaluation of System Development Methods , 1986, Information Systems Design Methodologies: Improving the Practice.

[18]  W. Neuman,et al.  Basics of Social Research: Qualitative and Quantitative Approaches , 2006 .

[19]  Michael D. Myers,et al.  A Set of Principles for Conducting and Evaluating Interpretive Field Studies in Information Systems , 1999, MIS Q..

[20]  Ron Weber,et al.  Research Commentary: Information Systems and Conceptual Modeling - A Research Agenda , 2002, Inf. Syst. Res..

[21]  Barbara Wixom,et al.  An Empirical Investigation of the Factors Affecting Data Warehousing Success , 2001, MIS Q..

[22]  Sue Holwell,et al.  Information, Systems and Information Systems: Making Sense of the Field , 1998 .

[23]  Graeme G. Shanks,et al.  The challenges of strategic data planning in practice: an interpretive case study , 1997, J. Strateg. Inf. Syst..