Software maintenance consumes up to 90 percent of a product's total lifecycle cost.
In short: While the tech industry prizes new development, the reality is that most software life is spent in maintenance. Often dismissed as low-skill work, this phase is actually a complex, event-driven discipline that determines whether a system survives or becomes an unmanageable, expensive legacy burden.
Software maintenance is the modification of a product after its delivery to users. Despite its reputation as a secondary task, it is the longest and most expensive phase of the software lifecycle, accounting for 80 to 90 percent of total costs. The discipline has changed little since R. G. Canning described it as an 'iceberg' in 1972, yet it remains understudied compared to initial development.
The process is driven by external events, such as user requests or bug discoveries, rather than the rigid requirements of initial creation. Maintenance is categorized into four types: corrective, to fix bugs; adaptive, to handle changing environments; perfective, to improve performance or maintainability; and preventive, to ensure future reliability. Because modifying code often introduces new bugs or ripple effects, testing—specifically regression and revalidation—frequently consumes the majority of maintenance resources.
A major hurdle is 'code entropy,' where the system's structure degrades over time due to technical debt. This occurs when developers prioritize speed over maintainability, often because they are not the ones who will eventually maintain the code. When a system becomes too costly to update, it reaches 'legacy' status. Organizations then face difficult choices: freezing the system to extract final revenue, wrapping it in new interfaces, or undertaking a multi-year migration to a new platform.
Offshoring maintenance to lower-cost countries like India or China has been a common strategy since the turn of the twenty-first century, aiming to reduce labor costs and enable around-the-clock support. However, this often creates communication barriers and organizational disjunction. Ultimately, the success of maintenance depends on the ability to understand existing code, a skill that is rarely prioritized in engineering education, leaving many companies struggling to manage the software they rely on.
Opens the Intellect+ feed with this card first. Swipe up for the next one.
Sources
- Summary by Intellect · source: Software maintenance
To cite this card, link to https://intellectplus.co.uk/app/technology-software-maintenance.
How we source, check and correct cards: Editorial standards.
General information, not professional advice. Spotted an error? Flag the card or see corrections and complaints.
Intellect Plus is a visual educational discovery platform for exploring fascinating facts and ideas. Brain Food, Not Brain Rot. What is Intellect Plus?
Related
More in Computing and information technology · More in Technology · Latest · A–Z · All topics