Document Controls

  • View a Print Friendly version of this document

    Print
  • Toggle highlighting of search terms in this document

  • Text Size: 

    • A (normal)
    • A (larger)
    • A (largest)

For Application Development Professionals

Primary Analyst Photo Document Information Rate this Document

November 11, 2005

Java, COBOL, And Perl Share A Common Problem

Lack Of Application Knowledge Creates Maintenance Issues

by Phil Murphy

with Kimberly Q. Dowling

This is an excerpt

Executive Summary

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.

This is an excerpt

Buy Risk-Free

Price: US $199

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.

Add to cart

Save and Share

Document Tools

Spread the word: