Coping with Existing Systems in Information Systems Development

Determining how to cope with existing systems is an important issue for information systems development (ISD). In this paper, we investigate how well different ISD patterns are suited for coping with existing systems. Empirical results, gathered from three software development projects undertaken by a financial institution, suggest propositions regarding how ISD patterns and existing systems affect the characteristics of objective ISD complexity, which in turn determine overall experienced complexity. Existing systems increase complexity due to conflicting interdependencies, but ISD patterns that reduce this complexity, such as those that employ bottom-up or concurrent consideration patterns, are best suited for coping with existing systems. In contrast, top-down and iterative focusing patterns, as classically used in new development, increase the complexity associated with conflicting interdependency, which makes them particularly unsuited for coping with existing systems in ISD.

[1]  Johannes Sametinger,et al.  Software Engineering with Reusable Components , 1997, Springer Berlin Heidelberg.

[2]  Sarma R. Nidumolu.  The Effect of Coordination and Uncertainty on Software Project Performance: Residual Performance Risk as an Intervening Variable , 1995, Inf. Syst. Res..

[3]  Barry W. Boehm,et al.  Improving Software Productivity , 1987, Computer.

[4]  Eugene S. Santos,et al.  Max-product grammars and languages , 1975, Inf. Sci..

[5]  Christopher Poile,et al.  The effects of ambiguity on project task structure in new product development , 2006 .

[6]  Allen S. Lee.  A Scientific Methodology for MIS Case Studies , 1989, MIS Q..

[7]  Allen Newell,et al.  Computer science as empirical inquiry: symbols and search , 1976, CACM.

[8]  Victor R. Basili,et al.  Viewing maintenance as reuse-oriented software development , 1990, IEEE Software.

[9]  Manish Agrawal,et al.  Software Effort, Quality, and Cycle Time: A Study of CMM Level 5 Projects , 2007, IEEE Transactions on Software Engineering.

[10]  Tridas Mukhopadhyay,et al.  Software Processes and Project Performance , 1995, J. Manag. Inf. Syst..

[11]  Thomas M. Pigoski.  Practical Software Maintenance: Best Practices for Managing Your Software Investment , 1996 .

[12]  M. Patton,et al.  Enhancing the quality and credibility of qualitative analysis. , 1999, Health services research.

[13]  Gordon B. Davis,et al.  Software Development Practices, Software Complexity, and Software Maintenance Performance: a Field Study , 1998 .

[14]  Herbert A. Simon,et al.  The Sciences of the Artificial , 1970 .

[15]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[16]  Franz Schober,et al.  Information System Flexibility and the Cost Efficiency of Business Processes , 2006, J. Assoc. Inf. Syst..

[17]  G. G. Stokes.  "J." , 1890, The New Yale Book of Quotations.

[18]  James D. McKeen,et al.  New Developments in Practice II: Enterprise Application Integration , 2002, Commun. Assoc. Inf. Syst..

[19]  James D. Herbsleb,et al.  Familiarity, Complexity, and Team Performance in Geographically Distributed Software Development , 2007, Organ. Sci..

[20]  Prashant Palvia,et al.  Software maintenance management: Changes in the last decade , 1990, J. Softw. Maintenance Res. Pract..

[21]  M. Sawhney.  Don't homogenize, synchronize. , 2001, Harvard business review.

[22]  K. Beck,et al.  Extreme Programming Explained , 2002 .

[23]  Ali Mili,et al.  Reusing Software: Issues and Research Directions , 1995, IEEE Trans. Software Eng..

[24]  K. Eisenhardt.  Building theories from case study research , 1989, STUDI ORGANIZZATIVI.

[25]  H. D. Rombach,et al.  Towards a comprehensive framework for reuse: A reuse-enabling software evolution environment , 1988 .

[26]  Keith H. Bennett,et al.  A Staged Model for the Software Life Cycle , 2000, Computer.

[27]  A. Michael Huberman,et al.  An expanded sourcebook qualitative data analysis , 1994 .

[28]  Izak Benbasat,et al.  The effects of decision support and task contingencies on model formulation: A cognitive perspective , 1996, Decis. Support Syst..

[29]  Tom Mens,et al.  Towards a taxonomy of software change , 2005, J. Softw. Maintenance Res. Pract..

[30]  William B. Frakes,et al.  Software reuse: metrics and models , 1996, CSUR.

[31]  Andrew Pettigrew,et al.  Issues of Time and Site Selection in Longitudinal Research on Change , 1990 .

[32]  D. P. Leyden,et al.  Familiarity and Group Productivity , 1991 .

[33]  D. Campbell.  Task Complexity: A Review and Analysis , 1988 .

[34]  Charles W. Krueger,et al.  Software reuse , 1992, CSUR.

[35]  Klaus Pohl,et al.  Process-Centered Requirements Engineering , 1996 .

[36]  Axel van Lamsweerde,et al.  Managing Conflicts in Goal-Driven Requirements Engineering , 1998, IEEE Trans. Software Eng..

[37]  W A Watson,et al.  Hawthorne effect: implications for prehospital research. , 1995, Annals of emergency medicine.

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

[39]  Ned Chapin,et al.  Types of software evolution and software maintenance , 2001, J. Softw. Maintenance Res. Pract..

[40]  Rajiv D. Banker,et al.  The Moderating Effects of Structure on Volatility and Complexity in Software Enhancement , 2000, Inf. Syst. Res..

[41]  Kalle Lyytinen,et al.  Large-Scale Requirements Analysis Revisited: The need for Understanding the Political Ecology of Requirements Engineering , 2002, Requirements Engineering.

[42]  Audris Mockus,et al.  Variability and Reproducibility in Software Engineering: A Study of Four Companies that Developed the Same System , 2009, IEEE Transactions on Software Engineering.

[43]  Stuart E. Madnick,et al.  Software Project Dynamics: An Integrated Approach , 1991 .

[44]  Kalle Lyytinen,et al.  Large Scale Requirements Analysis as Heterogeneous Engineering , 2002, Scand. J. Inf. Syst..

[45]  Geoff Walsham,et al.  Doing interpretive research , 2006, Eur. J. Inf. Syst..

[46]  Stuart A. Kauffman,et al.  At Home in the Universe , 1995 .

[47]  Frank Zickert.  Analysis of Two Theoretical Perspectives on Information Systems Development: Towards an Integrated Perspective , 2011, Wirtschaftsinformatik.

[48]  Giovanni Dosi,et al.  Division of labor, organizational coordination and market mechanisms in collective problem-solving , 2005 .

[49]  Fred A. Cummins.  Enterprise Integration: An Architecture for Enterprise Application and Systems Integration , 2002 .

[50]  Joyce J. Elam,et al.  Inside a software design team: knowledge acquisition, sharing, and integration , 1993, CACM.

[51]  Hind Benbya,et al.  Toward a complexity theory of information systems development , 2006, Inf. Technol. People.

[52]  Mohamed E. Fayad.  Software Maintenance , 2005, IEEE Softw..

[53]  Aaron J. Shenhar,et al.  One Size Does Not Fit All Projects: Exploring Classical Contingency Domains , 2001, Manag. Sci..

[54]  James H. Cross,et al.  Reverse engineering and design recovery: a taxonomy , 1990, IEEE Software.

[55]  O. Hanseth,et al.  Developing Information Infrastructure: The Tension Between Standardization and Flexibility , 1996 .

[56]  Wilhelm Hasselbring,et al.  Information system integration , 2000, CACM.

[57]  Richard Baskerville,et al.  Generalizing Generalizability in Information Systems Research , 2003, Inf. Syst. Res..

[58]  Rudy Hirschheim,et al.  Four paradigms of information systems development , 1989, CACM.

[59]  Mary Shaw,et al.  Prospects for an engineering discipline of software , 1990, IEEE Software.

[60]  Izak Benbasat,et al.  The Case Research Strategy in Studies of Information Systems , 1987, MIS Q..

[61]  Steve Sawyer,et al.  Analysis by long walk: some approaches to the synthesis of multiple sources of evidence , 2001 .

[62]  Line Dubé,et al.  Rigor in Information Systems Positivist Case Research: Current Practices , 2003, MIS Q..

[63]  Rob Procter,et al.  Software Development Practices , 1995 .

[64]  Keith H. Bennett,et al.  Software maintenance and evolution: a roadmap , 2000, ICSE '00.

[65]  L. Sproull,et al.  Coordinating Expertise in Software Development Teams , 2000 .

[66]  E. B. Swanson,et al.  Software maintenance management , 1980 .

[67]  Richard C. Hicks,et al.  Task Complexity and Informing Science: A Synthesis , 2006, Informing Sci. Int. J. an Emerg. Transdiscipl..

[68]  Shirley Gregor,et al.  The Nature of Theory in Information Systems , 2006, MIS Q..

[69]  T. Jick.  Mixing Qualitative and Quantitative Methods: Triangulation in Action. , 1979 .

[70]  R. Yin.  Enhancing the quality of case studies in health services research. , 1999, Health services research.

[71]  Victor R. Basili,et al.  How reuse influences productivity in object-oriented systems , 1996, CACM.

[72]  Václav Rajlich,et al.  Changing the paradigm of software engineering , 2006, CACM.