IT Innovation Squeeze: Propositions and a Methodology for Deciding to Continue or Decommission Legacy Systems

Organizations have been confronted with fast moving developments in the Information Technology (IT) sector over the past decades. Many new technological paradigms have emerged and left a landscape of legacy in which more and more money is spent on maintaining this landscape at the expense of innovating. Especially where business requirements put time pressure on the evolution of the IT landscape the decision whether to continue and maintain legacy systems or to decommission legacy systems in time has become a huge challenge. We formulate a set of propositions influencing the decision to decommission or continue legacy systems. This set of propositions is derived from literature and interviews with high level managers of organizations. Software characteristics, development methods, dependency of systems, lock-in, system complexity, new technologies and system ownership influence the decision whether to decommission or to maintain a system. We conclude this paper by proposing a methodology that helps organizations in finding the right balance between discontinuing and maintaining legacy systems.

[1]  N. Denzin Sociological Methods: A Sourcebook , 1978 .

[2]  R. Gordon,et al.  Five Puzzles in the Behavior of Productivity, Investment, and Innovation , 2004 .

[3]  Rajiv D. Banker,et al.  Software complexity and maintenance costs , 1993, CACM.

[4]  Jeanne W. Ross,et al.  Enterprise Architecture As Strategy: Creating a Foundation for Business Execution , 2006 .

[5]  S. Rosenbaum,et al.  Structured heuristic evaluation of online documentation , 2002, Proceedings. IEEE International Professional Communication Conference.

[6]  Bing Wu,et al.  Legacy Information Systems: Issues and Directions , 1999, IEEE Softw..

[7]  James Martin,et al.  Software Maintenance: The Problem and Its Solutions , 1983 .

[8]  Barry W. Boehm,et al.  Eight Lessons Learned during COTS-Based Systems Maintenance , 2003, IEEE Softw..

[9]  Wilma M. Osborne,et al.  Guidance on software maintenance , 1983 .

[10]  Leslie P. Willcocks,et al.  Managing Outsourcing: The Life Cycle Imperative , 2005, MIS Q. Executive.

[11]  David S. Linthicum,et al.  Enterprise Application Integration , 1999 .

[12]  Albert H. C. Tsang Strategic dimensions of maintenance management , 2002 .

[13]  Wolfgang Pree Component-based software development-a new paradigm in software engineering? , 1997, Proceedings of Joint 4th International Computer Science Conference and 4th Asia Pacific Software Engineering Conference.

[14]  S. K. Jha,et al.  Component Based Software Development : A New Paradigm , 2014 .

[15]  Pearl Brereton,et al.  Turning Software into a Service , 2003, Computer.

[16]  M. Jeffery,et al.  Best Practices in IT Portfolio Management , 2004 .

[17]  K. T. Yeo,et al.  Critical failure factors in information system projects , 2002 .

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

[19]  David Lorge Parnas Software Engineering - Missing in Action: A Personal Perspective , 2011, Computer.

[20]  Aniello Cimitile,et al.  Migrating legacy systems to the Web: an experience report , 2001, Proceedings Fifth European Conference on Software Maintenance and Reengineering.

[21]  David Cohen,et al.  Agile Software Development , 2003 .

[22]  David Schuff,et al.  Managing your total IT cost of ownership , 2002, CACM.

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

[24]  Robert L. Glass,et al.  Software Conflict 2.0: The Art and Science of Software Engineering , 2006 .

[25]  T. Capers Jones,et al.  Estimating software costs , 1998 .

[26]  Jiang Guo,et al.  Using category theory to model software component dependencies , 2002, Proceedings Ninth Annual IEEE International Conference and Workshop on the Engineering of Computer-Based Systems.

[27]  Kevin Keating,et al.  Software Maintenance As Part of the Software Life Cycle , 2003 .

[28]  A. von Mayrhauser,et al.  Code decay analysis of legacy software through successive releases , 1999, 1999 IEEE Aerospace Conference. Proceedings (Cat. No.99TH8403).

[29]  Magnus Klofsten,et al.  Innovation support for new technology‐based firms: the Swedish Teknopol approach , 2000 .

[30]  Robert J. Kauffman,et al.  When Is It Beneficial for a Firm to Pursue a Unified Procurement Strategy for Enterprise Software Solutions? , 2009, 2009 42nd Hawaii International Conference on System Sciences.

[31]  Hans van Vliet,et al.  Software engineering - principles and practice , 1993 .

[32]  M. Blume Portfolio Theory: A Step Toward Its Practical Application , 1970 .

[33]  Doug Hamilton Linking strategic information systems concepts to practice: systems integration at the portfolio level , 1999, J. Inf. Technol..

[34]  Leslie P. Willcocks,et al.  Intelligent It Outsourcing , 2003 .

[35]  Alistair Cockburn,et al.  Agile Software Development , 2001 .

[36]  L. Erlikh,et al.  Leveraging legacy system dollars for e-business , 2000 .