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

August 31, 2005

IT Alchemy Turns COBOL Source Code Into Java

The End Result Will Disappoint Most Customers

by Phil Murphy

This is an excerpt

Executive Summary

Vendors that provide automatic conversion of COBOL to Java to transition out of aging legacy COBOL applications are offering something that is too good to be true. The goals of such an effort are either to create a complete system replacement or to clone some of the business rules in Java. The former replaces a pitifully small piece of the application — less than 15% to 20% — and the latter creates a dubious set of "candidate rules" that require manual review. When it works properly, cloning also creates duplicate code, leaving one version of COBOL in place as it creates another in Java, and duplicate code introduces new maintenance synchronization nightmares. Either way, these tools deliver far less than the marketing claims promise.

This is an excerpt

Buy Risk-Free

Price: US $499

Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.

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

Add to cart

Save and Share

Document Tools

Spread the word: