Clear modules and boundaries
Focused components make responsibilities clear and limit the impact of changes.
Wartbare Software
Software, die Menschen verstehen, reparieren und an veränderte Anforderungen anpassen können.
Einfach erklärt
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.
Die Grundlage
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.
Angewendet von The Forge
Wie wir es praktisch umsetzen
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.
Eine nützliche Grenze
Wichtige Grenzen
- 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.
Ein konkretes Beispiel
One capability, many products
A shared address component has clear inputs and focused tests. Fixing its validation benefits every product that uses it.
Weiterführende Informationen
Primärquellen
Prüfen Sie die Quellen hinter diesen Erklärungen.
Verwandtes Konzept
Accessibility: Barrierefreiheit im Web
Websites so gestalten, dass Menschen mit Behinderungen sie wahrnehmen, bedienen und mit Hilfstechnologien nutzen können.