Ransford's NotesCourses
Workspace

What EA Is and Is Not

Distinguish enterprise architecture from solution architecture, IT strategy, and programme management so the learner can place EA in the right organisational context.

PreliminaryDerived from TOGAF

What enterprise architecture is, set beside its neighbours

Enterprise architecture is easiest to define by contrast. Read the same three rows, scope, horizon and output, across enterprise architecture, solution architecture and IT strategy to see where each one stops.

Enterprise architecture spans the whole enterprise over a multi-year horizon; solution architecture designs one system for a release; IT strategy sets technology direction alone. Naming the neighbours stops EA being mistaken for either of them.

What enterprise architecture is, set beside its neighbours A comparison matrix that defines enterprise architecture by contrast. Three discipline columns, enterprise architecture, solution architecture and IT strategy, are read against three rows down the left edge: scope, horizon and output. The enterprise architecture column is emphasised with an accent wash and a red spine on each cell. Its scope is business and IT end to end, its horizon multi-year, its output a governed roadmap. Solution architecture covers one system for a release. IT strategy covers the technology estate alone. A red note states that naming the neighbours is the definition: only the enterprise architecture column spans business and IT over many years. Enterprise architecture The discipline this tool defines Solution architecture IT strategy Row 1 Scope Row 2 Horizon Row 3 Output Business and IT Whole enterprise, end to end Multi-year Continuous, not a project Governed roadmap Owned across the enterprise A single system One product or platform One release A delivery, then handover Build design For the delivery team Technology estate The IT function alone Planning cycle IT-led, periodic refresh Direction plan Where technology should go Naming the neighbours is the definition.EA is mistaken for solution architecture or IT strategy until you fix its scope, horizon and output against theirs. Onlythe EA column spans business and IT, end to end, over many years.