Evolution for Software Engineerings
Software evolution is the stage after release where the product is fixed, adapted and extended over years. It includes managing technical debt, refactoring legacy code, handling dependency upgrades, retiring features and documenting decisions. It also covers professional ethics, such as privacy, honesty about limits and the social impact of software.
Stage: Delivery and Maintenance · Part of the Software Engineering roadmap · Last reviewed 19 November 2026
What to learn in Evolution
- Track technical debt and justify paying part of it down to a manager
- Plan a safe upgrade of a major dependency with tests as a safety net
- Document a design decision as a short architecture decision record
- Apply the ACM or IEEE code of ethics to a realistic dilemma
- Decide when to rewrite a system and when to refactor it incrementally
Evolution interview questions
What is technical debt?
Technical debt is the future cost created by choosing a quick or messy solution now. Like financial debt it accrues interest: later changes get slower and riskier. Some debt is deliberate and reasonable, but it should be recorded and repaid through refactoring before it blocks delivery.
Why is rewriting a system from scratch often risky?
A rewrite throws away years of embedded fixes and edge-case knowledge, takes longer than estimated and delivers no value until the end. Incremental approaches, such as strangling old modules behind an interface, let the team ship improvements continuously while reducing risk.
Where Evolution fits in the Software Engineering roadmap
Evolution belongs to the Delivery and Maintenance stage (advanced level). Keep it alive.
Other units in this stage
Back to the full Software Engineering roadmap