As mentioned in part I in this series of articles on legacy code analysis, poorly understood or undocumented legacy application source code is a risky thing.
The Obvious Pitfall – The Broken System No One Knows How to Repair
The popular fear is that a legacy system will break, and there’s no one on staff who understands the code well enough to fix it in a timely and cost-effective fashion. Business operations are disrupted and the costs to debug and fix the problem (with internal or external resources) are high.
Not-So Obvious Undocumented Legacy Code Pitfalls – System Replacement
A large healthcare company was in the process of replacing a legacy custom-built ERP with a commercial off the shelf (COTS) ERP system from Oracle. (more…)
Tags: legacy application replacement, Legacy Code Analysis, legacy system retirement
Posted in Development, Legacy Code Analysis, Modernization | No Comments »