With inheritence !
This is a continuation of my earlier blog - asking what would be the desirable characteristics of a COBOL program - rewritten in OO Java or C#.
In the first step we discussed the necessity for Semantic Translation.
In the next section I would like to discuss the importance of OO in design of data-sections. (I will discuss OO in business logic section a bit later).
Quarterly earning reports looking good.
Meanwhile, Intel's net earning is down - but better than expected.
Does all this point to the green shoots of recovery ?
Step-by-Step Guide to Successful COBOL Modernization
In my yesterday's blog, I asked what would be the desirable characteristics for a COBOL program re-written in Java or C#? It doesn't really matter whether the process is achieved in a manual rewrite, or through automatic translation. But the amount of time and budget allocated to the system matters a lot. If there was a BIG budget and a lot of time, you could end-up with an "ideal" solution (or run over-time and budget, and have the project cancelled).
So, without further ado, here is the major characteristic:
Well, your COBOL legacy Applications will be translated
Various reports suggest that the COBOL code base is still growing between 3 to 5% per year. The past Legacy modernization projects have only touched the tip of the iceburg.
The modernization projects to-date has mostly started due to an immediate "necessity" such as business process changes. In this situation, where budgets allowed, it made sense to re-document, extract the rules, re-design and rewrite. My company - SoftwareMining we also produce business rule extraction tools for this market. But in this discussion, I want to focus on Translations.
As I said, I think we have just seen tip of the iceberg ...