Let’s consider an example of a typical Informix 4GL application suite consisting of
- 200 separately compiled 4GL programs
- 1500 4GL source-code modules
- 600 screens (4GL forms)
- 500K LOC of 4GL source code
This application provides data maintenance and data entry functionality for an enterprise. Converting the original application to another technology, say Java or C# would be a complete new development as they cannot leverage the existing 4GL code. The entire application would have to be rewritten! Assuming approximately 160 lines of code per day (based on the Gartner Group 1 estimates for code modernization), we can easily assign at least 2 years of development job with 10 experienced Java developers. This time excludes the bug fixing time which will be spent on fixing the bugs that appear during development.
If the team is really capable and finishes it off within a year, still since the new application would be entirely a new Java logic, complete testing and certification process would have to be performed, as is with any other new application.
Modernizing with Genero on the other hand will reuse the existing 4GL code, a direct saving on rewriting as well as testing. With various options available to deploy, the modernized code can be rendered as GUI on any platform like Mac, Windows, and Linux etc or with Genero Web Client can be used as a web service.
Hence, considering a suitable modernization scenario is always a logical approach, before one decides to invest years and thousand sometimes millions of dollars into a lengthy and unpredictable migration process.
When to Opt for Modernizations?
In 2006, the Gartner Group estimated that 10,000 mainframe application systems contain about 200 billion lines of legacy code. Another study showed that on an average a Fortune 100 company has 35 million lines of code. Every year the code increases by about 10% due to maintenance and enhancement jobs.*
After 8 years these mission critical systems have become even more cumbersome. Companies facing such issues are often advised by IT consultants to opt for modernization or application rationalization. So how to do CIOs decide when is the right time for modernization? To your help we present a checklist and if your legacy application qualifies any 2 points, then now is the time to opt for modernization.
- If your application has served you for more than 10 years, then keeping in view the rate of modern technological innovations, it is safe to assume that your application lacks the technological edge.
- If the front end of your application is still text/character based or a very primitive GUI, you have to update the front end to make it more user-friendly.
- If the application architecture is old and composed of many separate applications linked to each other which is causing a lot of maintenance issues.
- If your application is not SOA enabled.
- If your OS (operating system) and database is no longer supported.
- If integration with new apps like email, cloud, mobile, social media etc is not possible. • If crucial knowledge of application has been lost due to employee turnover.
