Legacy Application Re-Engineering
As the CIO or decision maker in your organization regarding the use of technology, you have probably inherited existing software systems. As you introduce new technology into your company, you will find that integration with certain legacy applications requires considerable skill and planning.
Some considerations include:
Is it better to replace the legacy application or extend its life?
Will keeping the legacy system operational be more or less cost-effective in the long term?
How much effort is needed to migrate legacy platforms?
How much effort is needed to re-engineer legacy applications?
The true cost of legacy applications may be difficult to ascertain quickly but often keeping these systems alive can cost more than migrating them. When you leave a legacy system as it is without making any change, you will incur both direct and indirect costs. Direct costs include tangible expenses incurred by running and maintaining these systems. Indirect costs may not be realized or fully understood right away. These may include things such as loss in users or visitors that lead to a loss in opportunity, revenue and related problems.
Modernizing the legacy system is essential to creating flexibility and thus having options again. Flexibility translates into easier maintenance since adaptability leads to more choices in management. The longer a legacy systems persists the smaller the knowledge pool becomes to maintain it, as the experienced developers move on to newer, glitzier technologies.