(Length: 5 pages)

Executive Summary (This is a document excerpt)

Applications written in Java, Perl, C# or any other language just three years ago have begun to develop "legacy" attributes: The original authors are gone; the applications are poorly documented and poorly understood; and although the business relies on the applications, it fears changing them for the unknown effects that any changes may cause. Have the first legacy Java applications really arrived? Perhaps, but a deeper analysis of the complaints reveals the real truth: The wholesale loss of application knowledge creates most of the maintenance issues. IT organizations should not dismiss these applications as useless legacy artifacts, destined for rip-and-replace; rather, they should redeem the value locked inside of the applications.

Buy Risk-Free

Download and print PDF immediately. Price: US $49

Our Money-Back Guarantee: If you are not completely satisfied, return it for a full refund within three weeks of your online purchase.

Already a Forrester Client?
Log in to read this document.