legacy software
noun
Legacy software still serves an important purpose but is difficult to maintain, change or replace because of technical limitations, missing knowledge or strong dependencies.
The insurer is modernizing its legacy software in stages so daily processing can continue.
Legacy software has often been used for years and supports processes that cannot simply stop. Age alone does not make an application legacy software. The term mainly applies when maintenance or expansion becomes increasingly difficult, for example because of outdated technology, limited documentation or knowledge held by only a few people.
When does software become legacy?
Software can become legacy while still working well every day. Problems arise when its programming languages, Glossary · In briefframeworkA framework is a coherent foundation for software development, providing reusable code, a defined structure and conventions for building an application.Read more or Glossary · In briefdependencyA dependency is a software component or system that other software needs in order to build or run, such as a library, framework or external service.Read more are no longer supported. A difficult Glossary · In briefcodebaseA codebase is the collection of source code used to build and maintain a software product or component.Read more, missing tests and integrations with other systems can also make changes risky.
The most significant factor varies by organization. An old system with good documentation and active maintenance may cause few problems. A newer application can quickly become legacy if nobody understands how important components interact or necessary updates are difficult to make.
Replace or modernize legacy software?
Complete replacement is not always the best first step. An organization can modernize gradually by identifying risks, adding tests, renewing vulnerable components or reducing coupling between systems. Useful functionality is preserved while maintenance becomes more manageable.
The approach depends on business value, technical risks and available knowledge. Replacement sometimes makes sense because the existing foundation blocks further development. In other cases, gradual modernization reduces the risks of migrating a critical system and its accumulated domain knowledge.