The ever-growing cost to maintain systems continues to crush IT organizations, robbing their ability to fund innovation while increasing risks across the organization. The cost of maintaining a software system is directly proportional to the size and complexity of the system. Therefore any effort to reduce the size and complexity translates into direct improvement of software maintenance costs. The following provides guidance on how a static code analysis of applications generates actionable insight you can take to immediately improve the maintainability of systems.
Eliminate dead code
Between 5-10 percent of legacy application source code is dead code -- code that can never be executed in a running program. It wastes computation time, complicates the deployment process, complicates maintenance, and distorts program measurements by artificially inflating the LOC.
To improve readability and ensure that logic errors are resolved, dead code should be identified, understood, and eliminated.
Make sure your source code is documented
Application maintenance accounts for more than 80 percent of the lifetime cost of an application, so wasting effort on just trying to understand excessively complex code is an enormous waste of time and money that development could be putting toward innovation. Believe it or not, 47 percent of software maintenance is spent understanding the existing codebase. Programmers who work on an application with no documentation spent 21.5 percent longer trying to understand the codebase.
IT managers need to ensure that there are proper processes in place for code documentation and they’re being adhered to by development.
Identify and eliminate duplicate code
Between 5 and 20 percent of typical business systems source code is duplicated -- what developers call copy and paste development.
It might seem like an easy fix at first, but it increases the time it takes for developers to get up to speed. Not only that, but it also impacts feature enhancements since the same changes need to be made on multiple clones. As a result, it increases the amount of test cases you need to do before deployment and carries the potential to impact your company’s reputation due to update anomalies.
Reduce code complexity
Now that you’ve identified and fixed problem areas in your application portfolio, it’s time to work on its resiliency and stability by reducing its overall complexity. High levels of software complexity account for approximately 25 percent of maintenance costs or more than 17 percent of total lifecycle costs. This increased complexity makes it a burden to transfer the application to a new outsourcer without creating a huge learning curve that dilutes the expected cost benefits. Similarly to eliminating duplicate code, reducing code complexity allows new features to be delivered more quickly.
Pulling yourself out of the application maintenance death spiral
Each one of these exercises is aimed at helping your organization pull itself out of its application maintenance death spiral that consumes critical IT resources. The path to regaining control is first through visibility generated by automated code review then through governance that is focused on the end result -- the product.
IT leaders need measures that track trends in the health of critical applications -- robustness, security, changeability, performance efficiency, and transferability -- in order to know where they need to invest their resources to sustain the level of service they provide to the business.
Read more about source code analysis and application maintenance here: “Unsustainable: Regaining Control of Uncontrollable Apps.”
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.