Third-generation programming languages (3GL) like COBOL or PL/1 are seen as outdated languages for “has-been” developers, and do not interest new ones anymore (there were even predictions saying that COBOL was going to die in mid-term.) These new developers prefer more modern technologies, like J2EE or .NET, and, worryingly, educational organizations provide few learning opportunities for 3GLs.
As a consequence, people who can create and maintain applications implemented in COBOL or PL/1 are not as common. Some shops have had to organize quick training sessions to maintain their manpower. In other words, there are few experts but the need is there! Fortunately, there are initiatives like those done by platform and compiler vendors:
These applications were created many years ago and are now called “legacy apps,” although they are still alive (yes, COBOL’s not dead!) and continue to manage many businesses around the planet. Analyzing legacy code is like an archeological mission. I have often experienced such situations where I’ve gone back in time discovering different layers of code, implemented by multiple waves of developers (some are already retired!).
We can see the different ways and practices that were used to produce code with the same programming language. Program headers look like books of history—some are so long they give a preview about the size, complexity, and the probability of finding error-prone code, potential bugs, and bad coding practices.
If experienced 3GL developers are not numerous, then knowledge regarding these apps becomes quite low in terms of:
Even if there aren’t many changes, quality measurement is particularly important to avoid having these central applications out of control. This can help developers produce robust and efficient code more easily, and enable application owners to check if updates completed by outsourcers respect coding guidelines.
Also, these applications generally have a sizeable technical debt, due to their many years of service. Even if it is not possible to resolve the whole debt, it is important to keep it under control and avoid increasing its size. Maybe in 100 years they will be replaced by new technologies.
Legacy apps are no longer on the main stage, but they do generate huge amount of work for development teams. So keep an eye on the code!
Erik Oltmans, an Associate Partner from EY, Netherlands, spoke at the Software Intelligence Forum on how the consulting behemoth uses Software Intelligence in its Transaction Advisory services.
Erik describes the changing landscape of M & A. Besides the financial and commercial aspects, PE firms now equally value technical assessments, especially for targets with significant software assets. He goes on to detail how CAST Highlight makes these assessments possible with limited access to the targetâ€™s systems, customized quality metrics, and liability implications of open source components - all three that are critical for an M&A due diligence.