Clear modules and boundaries
Focused components make responsibilities clear and limit the impact of changes.
Logiciel maintenable
Un logiciel que les personnes peuvent comprendre, réparer et adapter à mesure que leurs besoins évoluent.
En termes simples
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.
Les fondements
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.
Appliqué par The Forge
Comment nous le mettons en pratique
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.
Une limite utile
Les limites à garder en tête
- 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 exemple concret
One capability, many products
A shared address component has clear inputs and focused tests. Fixing its validation benefits every product that uses it.
Pour aller plus loin
Sources principales
Consultez les sources de ces explications.
Concept associé
Accessibility: Accessibilité web
Concevoir des sites que les personnes en situation de handicap peuvent percevoir, utiliser et comprendre avec leurs technologies d'assistance.