(Length: 5 pages)

August 31, 2005

IT Alchemy Turns COBOL Source Code Into Java

The End Result Will Disappoint Most Customers

This is the third document in the "Modernizing The Practice Of Application Maintenance" series.

by Phil Murphy


Executive Summary (This is a document excerpt)

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.

Buy Risk-Free

Download and print PDF immediately. Price: US $499

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

Find Documents In Related Categories

This document falls under the following categories. Click on a link below to find similar documents.

Analyst: Phil Murphy
Technology: Application Development, Application Development Processes & Tools, Application Infrastructure Technologies, Architecture & Technology Strategy
Geography: Asia Pacific, Europe, North America