Clear modules and boundaries
Focused components make responsibilities clear and limit the impact of changes.
Software manutenibile
Software che le persone possono comprendere, riparare e adattare al cambiare delle esigenze.
In parole semplici
Maintainable software is easy to understand and change, with clear code, useful documentation, and reliable checks.
Use enough structure for likely changes while keeping complexity and upkeep manageable.
Le fondamenta
What matters in Maintainability
Checks people can rely on
Types, tests, and automated checks help catch regressions.
Understandable ownership
Keep documentation and decisions accessible beyond the original developer.
Applicato da The Forge
Come lo mettiamo in pratica
We match the software’s structure to the team’s capacity to maintain it.
Design around responsibilities
Organise code around clear responsibilities.
Reuse with intent
Share repeated functionality while keeping product-specific behaviour close to its use.
Keep changes small and checked
Small changes and focused checks make defects easier to find.
Maintain the operating knowledge
Keep dependency, deployment, and recovery documentation current.
Un limite utile
Limiti da tenere presenti
- It does not mean the software will never need maintenance or redesign.
- It is not achieved by adding abstractions, patterns, or documentation everywhere.
- Clean-looking code alone is insufficient if the product cannot be tested, deployed, or understood safely.
Un esempio concreto
One capability, many products
A shared address component has clear inputs and focused tests. Fixing its validation benefits every product that uses it.
Approfondimenti
Fonti primarie
Consulta le fonti alla base di queste spiegazioni.
Concetto correlato
Accessibility: Accessibilità web
Progettare siti che le persone con disabilità possano percepire, utilizzare e comprendere con le tecnologie assistive.