The diagram problem

Architecture knowledge often starts with a diagram, a presentation or a design document. Those artefacts are useful, but their relationships are difficult to maintain when the estate changes. One diagram may describe a service, another an API, and a third the same application under a slightly different name.

Make identity independent of the view

A useful repository gives the application, API, capability or integration an identity of its own. Multiple diagrams can refer to the same element, rather than copying a slightly different description into each view. This creates a foundation for navigation, reporting and impact analysis.

Relationships are first-class information

Connections between elements should not exist solely as lines on a diagram. If an application provides a service or an integration connects two systems, that relationship belongs in a governed model. Views then become different ways of exploring the same information.

Govern only what adds value

A shared architecture repository should ask for the minimum information needed to make a record meaningful, progressively enriching it as decisions depend on it. Excessive mandatory fields often produce the appearance of governance without making the architecture more useful.

The practical test

Ask whether a new architect can find an application, understand its role, identify its upstream and downstream dependencies, and see why a change is being proposed. If that journey takes hours of chasing documents, a repository has not yet fulfilled its promise.

The MétiArch perspective

Explore more MétiArch Insights for practical architecture perspectives.

← Explore all insights