Re: COBOL to Java conversion
- From: Robert <no@xxxxxx>
- Date: Tue, 30 Oct 2007 08:06:03 -0600
On Mon, 29 Oct 2007 05:06:19 -0700, HansJ <hjigel@xxxxxx> wrote:
We are in the business of migrating Unisys COBOL mainframe
applications to Unix.
Using the same programming language and keeping the code intact is a
key element, because we think that there are enough issues to deal
with.
Recently we have seen requests to not only move to a different
platform, but also to change the language to be Java.
We don't need to discuss all the issues that come with a language
change, like maintainability, staff competence, etc. as this is a
different topic.
I would be interested in knowing if anyone has seen a successful
project of this type that has a significant size.
A significant size would be more than one million lines of COBOL code.
The system rewrite most discussed in print was the Chrysler payroll, discussed here
http://en.wikipedia.org/wiki/Chrysler_Comprehensive_Compensation
That one was in Smalltalk and Gemstone. If they were doing it today, they would use Java
and J2EE. There is enough similarity to make the experience relevant. The key concept is
an object oriented code-centric style of design and management, then called Extreme
Programming (XP).
Make a list of the factors needed for a successful IT project, then ask how many of them
can be performed by the language or compiler. My list looks like this:
1. Management, leadership
2. Programming talent
3. Clear definition of goals
4. Management support, lack of politics
5. Testing, quality control
6. Adequate resources -- time, people, software tools, hardware
7. Development speed
.
- References:
- COBOL to Java conversion
- From: HansJ
- COBOL to Java conversion
- Prev by Date: Re: A Trend Towards Lower Software Maintenance Budgets?
- Next by Date: Re: COBOL to Java conversion
- Previous by thread: Re: COBOL to Java conversion
- Next by thread: Re: "Free" workbench/IDE
- Index(es):
Relevant Pages
|
