How should architecture documentation be maintained?
Architecture documentation should have clear ownership.
Important architecture information should be reviewed when significant business, technology or organisational changes occur.
A central repository or architecture knowledge base can help, but the tool itself is not the most important factor.
The key questions are:
- Who owns this information?
- Who uses it?
- When was it last reviewed?
- What decisions does it support?
- What happens when it becomes obsolete?
Architecture should be treated as a living management capability rather than a one-time documentation exercise.