ABSTRACT
For many IT professionals, the term “legacy system” evokes images of a 20-year-old program that is about to be superseded by a new piece of software, typically an integrated system that was designed to replace a hodgepodge of ancient programs. While this is a valid definition, it can also be argued that all systems become legacy the moment they are placed in production. Whether 20 days or 20 years old, the systems face similar challenges. They must continue to run properly, even when the infrastructure changes; they must adapt to a changing business environment; and they must be flexible enough to accommodate new functionality. In short, they must be maintained.
