Architecture repository behind compliance, landscape and portfolio reporting

Context

The client arrived with three separate requests, each scoped as its own piece of work: raise compliance visibility, review the architecture landscape from an enterprise-architecture standpoint, and reorganise reporting so that the value of IT projects is visible and easy to demonstrate to the business.

Approach

Read the three requests as three symptoms of one cause. The enterprise had no single queryable description of itself, so every question — about compliance, about the landscape, about what a project was worth — had to be assembled by hand, and went stale on the day it was answered. Rather than deliver three reports, proposed one instrument: an architecture repository built as code, with every report derived from the model instead of maintained alongside it.

Mid-engagement the client added a fourth requirement — the ability to follow a requirement’s fate from the originating business requirement through to the test that proves it. The same repository absorbed it without a change of approach, which is the argument for the instrument made in practice rather than on a slide.

Outcome

Delivered the repository and the reporting layer above it.

• Compliance visibility became a query. A set of compliance reports generated from the model, so the state is read rather than assembled.
• The landscape stopped dating from the day it was drawn. Source diagrams plus dynamic reports that render the current landscape from the model on every read.
• End-to-end requirements traceability — from the originating business requirement through to the test that proves it, in one chain.
• A new document format for engineers and business analysts: dynamic documents bound to the model, which refresh themselves from it, generate prose from the requirements embedded in them, and show which parts of the document are missing or out of date.

Key result

Replaced three hand-assembled reporting demands with one architecture-as-code repository — compliance reports, an always-current landscape view, and originating-requirement-to-test traceability all derived from a single model, plus a self-updating document format that shows its own gaps.