Legacy Information Systems: Issues and Directions

  title={Legacy Information Systems: Issues and Directions},
  author={Jes{\'u}s Bisbal and Deirdre Lawless and Bing Wu and J. B. Grimson},
  journal={IEEE Softw.},
A legacy information system represents a massive, long-term business investment. Unfortunately, such systems are often brittle, slow and non-extensible. Capturing legacy system data in a way that can support organizations into the future is an important but relatively new research area. The authors offer an overview of existing research and present two promising methodologies for legacy information system migration. 

Figures from this paper

A Method for Rewriting Legacy Systems using Business Process Management Technology

The use of BPM for migrating legacy systems based on Business Process Management facilitates the monitoring and continuous improvement of the information systems existing in the organization.

Value-Based Migration of Legacy Data Structures

This work reports on the experiences from a migration project at a large bank that pursued a value-based approach, in which migration efforts were first focused on a small set of business processes that were identified as most crucial for the enterprise.

Designating Legacy Status to IT Systems : A framework in relation to a future-oriented perspective on legacy systems

Maintaining the system might prove ineffective in accommodating necessary changes, but a system migration will help organizations to adapt and thrive in the face of change.

Risk-aware Migration of Legacy Data Structures

This work reports on the experiences from a migration project at a large bank that pursued a value-based approach, in which migration efforts were first focused on a small set of business processes that were identified as most crucial for the enterprise.

Reverse Engineering Interaction Plans for Legacy Interface Migration

Mathaino is discussed, an intelligent, multi platform, semi-automated, and low risk solution for migrating legacy user interfaces to the web by wrapping them with web-accessible front-ends.

Migration of Legacy Information Systems

This chapter addresses the problem of platform migration of large business applications, that is, complex software systems built around a database and comprising thousands of programs, and describes the State of the Art in information system migration.

A Practical Approach for Modernization of Legacy Systems

This paper examines the issues concerning the migration of legacy data objects to RDMS to guarantee performance, efficiency, share ability and ease of future enhancements.

Research on Reuse of Legacy System Based on SOA

This paper discusses the construction of all kinds of information integration platform of the urgent problems to be solved and how to integrate the existing legacy system into a reusable Web service component.

Reengineering legacy systems using Web

This research has analyzed the different ways in which a Web based solution can be provided for the technological requirement of legacy systems and focus on Web-based development solutions.

Process evaluation of general data migration guidelines : A comparative study

Information systems form the backbone of many organizations today and are vital for their daily activities. For each day these systems grows bigger and more customized to the point where it is heav



The Transition of Legacy Systems to a Distributed Architecture

The Transition Process Transition Design Considerations Transition Overview Road Map of Transition Process of Legacy Systems Index.

Building Consistent Sample Databases to Support Information System Evolution and Migration

This paper focuses on prototype databases, which are needed in any information system development process to support data-intensive applications development and using synthetic data to populate these databases.

Migrating Legacy Systems: Gateways, Interfaces, and the Incremental Approach

Focusing on data migration, the authors outline key techniques for transforming a legacy IS into a flexible system that meets current needs and is adaptable to unpredictable future changes and advocate a step-by-step strategy that migrates the system to a decomposable target environment while the current IS remains completely operational.

Legacy Systems: Coping with Success

Legacy systems may be defined informally as "large software systems that we don't know how to cope with but that are vital to our organization". Legacy software was written years ago using outdated

The Butterfly Methodology: a gateway-free approach for migrating legacy information systems

  • Bing WuD. Lawless D. O'Sullivan
  • Computer Science
    Proceedings. Third IEEE International Conference on Engineering of Complex Computer Systems (Cat. No.97TB100168)
  • 1997
The Butterfly Methodology is presented, which questions the need for the parallel operation of the legacy and target systems during migration, and introduces an innovative gateway-free approach to migrating legacy information systems in a mission-critical environment.

Encapsulating legacy software for use in client/server systems

  • H. Sneed
  • Computer Science
    Proceedings of WCRE '96: 4rd Working Conference on Reverse Engineering
  • 1996
Achieving this promises a new form of coexistence between monolithic legacy systems on the mainframe and object-oriented, distributed systems in the network and introduces a new mode of software reuse.

Systems reengineering patterns

This paper argues that the main problem is not that the necessary expertise does not exist, but rather, that it is hard for software engineers to become expert, and that an approach via systems reengineering patterns can help.

Implications of Distributed Object Technology for Reengineering

The question posed by this paper is the extent to which reengineering strategies ought to continue to use program understanding technology, as the cost/benefit ratio of certain forms of program understanding appears to be staying roughly the same over time, while the cost of wrapping legacy systems or their subsystems is dropping rapidly.

Software Reengineering Patterns

The idea of software reengineering patterns, which adapt the ideas of design patterns to identify lessons in successful reengineering projects and to make these lessons available to new projects are introduced.

Reverse engineering and design recovery: a taxonomy

The authors define and relate six terms: forward engineering, reverse engineering, redocumentation, design recovery, restructuring, and reengineering to apply to the underlying engineering processes, regardless of the degree of automation applied.