A legacy system is defined as:
...a computer system or application program that is usually mainframe-based and utilizes older technologies. In many cases, legacy systems continue to be used because of the prohibitive cost of replacing or redesigning them, and often despite their lack of competitiveness or incompatibility with modern equivalents.
These systems have typically been in operation a long time, and their functions are too essential to be disrupted by upgrading or integrating with another system. In most cases, these systems are large, monolithic and difficult to modify.
The facts on legacy systems:
- The challenge faced by many organizations is this: legacy systems often do not support direct reporting and analysis from important business information contained in these systems.
- The barriers represented by legacy systems artificially limit the creativity and ability of end-users to solve problems and perform the full scope of reporting and analysis on the data that currently exists in their organization.
- The typical solutions put forward - upgraded software, data marts or custom programs - all require a significant commitment of time and financial resources, making it difficult to build a strong business case for many projects that involve legacy systems.
- The fall-back decision of ‘do nothing’ has consistently proven to have its own real costs, both hidden and visible, as organizations are unable to make decisions and see risks based on all the information that could be made available to them.
> See also: Mainframe Data Sources Accessed by Arbutus
