Software is the heart of every organisation, beating in the background to keep organizations up and running. Similar to human hearts, we expect software to perform perfectly all hours of the day. With software, when things go wrong, they do so spectacularly.
12-year-old apps need TLC to prevent teenage tantrums
The report found service-critical applications used by organizations were an average of 12-years-old, two years older than the average application analyzed. The majority of these were still anchored by legacy COBOL systems, which have been left without active development as they are written in code most developers no longer understand.
Whilst there is a strong focus on application modernization and new application innovation, IT leaders are prioritizing low-impact applications, as they no longer understand their maturing apps, living in fear of the potential repercussions that application modernization could inflict upon older apps. This leaves older high-impact software such as business-critical enterprise systems amassing software complexity and technical debt.
Given these findings, this issue is compounded further with nearly half, 46%, of business revenue-related systems serve both internal and external customers. Without active development or application modernization, these systems pose a greater risk of lapsing into failure which will have widespread effects.
Deteriorating software struggles to be understood
Only 25% of business-critical apps scored higher than 87 (out of 100) in application resiliency, which measures the ability of an application to recover from certain types of failure, whilst still providing an acceptable level of service to the business. Low application resiliency often result in extended down time, frustrating users and driving up running costs.
Development teams are one-third of their ideal size
The report confirms development teams are significantly understaffed by 65% when compared to the Constructive Cost Model (COCOMO II); a trusted method which estimates the effort, cost and schedule for software projects. Currently development teams have 5.5 full time equivalents (FTEs), whereas COCOMO II recommends 16 FTEs to be allocated for maintenance activities. The mounting pressure placed on these short-staffed teams to develop new functionality and maintain increasingly complex systems leads to high employee turnover and outsourcing. With high levels of employee turnover, the continuity of systems’ maintenance is disrupted, often leaving complex code behind which is hard to decipher, snowballing technical debt.
Why Software Intelligence needs to be the new normal
In a constantly advancing digital age, accelerated by the rapid rise of IoT devices, companies will struggle to keep pace managing and maintaining their systems without insights.
Software Intelligence, a deep analysis of the software architecture, provides unprecedented visibility into the inner workings of all systems, legacy or new. Highlighting software quality & security risks, code complexity, technical debt and several other software health metrics to ensure a better understanding of the software problems companies face today and in the future.
With this information, architects are able to make informed decisions, reducing the business pressures on those teams which can force them to take short-cuts, ultimately reducing costs as well as risk.
If businesses want to protect their reputation and build customer satisfaction, they must recognize the importance of their technology and the people who maintain it. Without significant investment and focus on these two key factors, organizations will cave in on themselves, and be left in a dilapidated state, and no-one will be left to pick up the pieces.