EA Practice Outputs

What each of the seven stages of the National Enterprise Architecture Methodology actually produces: scope documents, current-state reports, future-state designs, the roadmap, and approval minutes.

At a glance

Where this page sits: a catalogue of the documents and artifacts produced across the seven NORA methodology stages and the four supporting elements.
The National EA Methodology has seven main stages that run in an integrated way, not as a strict linear sequence.
Every stage has its own inputs, steps, and outputs, and produces documents, blueprints, reports, and approval minutes.
Outputs are approved at the level that fits them: the Head of Entity, the Digital Transformation Committee, the EA Governance Committee, or the Chief Enterprise Architect.

Approval authorities

Head of Entity, or their delegate: approves the major strategic outputs such as the development-cycle scope and the roadmap.

Digital Transformation Committee, with the EA Governance Committee: approves outputs that sit where EA work meets digital-transformation priorities.

EA Governance Committee: approves the practice operational outputs from current-state diagnosis, future-state design, and gap analysis.

Chief Enterprise Architect, with the relevant unit where it applies: approves operational updates and day-to-day technical requirements.

Outputs of the seven stages

Stage	Main outputs
1. Defining the EA Development Cycle Scope	A scope document covering the targeted components and viewpoints, the responsibilities matrix, and formal approval of the scope.
2. Diagnosing the Current Situation	An inventory of the existing EA components in each domain, their analysis, and a current-state report with recommendations.
3. Exploring Future Trends	A review of the current-state findings, the results of studying similar practices, and a future design-trends document.
4. Designing the Future State	Future EA designs for each domain, with the approved blueprints and viewpoints.
5. EA Gap Analysis	A register of the gaps between the current and target states, with impact and prioritisation analysis.
6. Developing the Roadmap	A roadmap to deliver the target EA, covering initiatives, projects, priorities, and how each one ties to strategic performance indicators.
7. Managing EA Requirements	An approved requirements register, status tracking, and an assessment of how changes hit it.

Supporting elements

Key takeaway

Alongside the seven stages, the methodology rests on four supporting elements that run throughout the work: EA governance, knowledge management, communications and change enablement, and maturity measurement. Their effect shows up across most of the outputs rather than in one single deliverable.

Source: Guideline for Implementing the National Enterprise Architecture Methodology, issued by the Digital Government Authority.

EA reports

Periodic reports on practice state and development cycles.

EA procedures

Operating procedures governing the EA practice.

National methodology

The seven stages and supporting elements.

Ready to start?

Book a free consultation. We walk through your priorities and recommend the right starting point.

At a glance

Where this page sits: a catalogue of the documents and artifacts produced across the seven NORA methodology stages and the four supporting elements.
The National EA Methodology has seven main stages that run in an integrated way, not as a strict linear sequence.
Every stage has its own inputs, steps, and outputs, and produces documents, blueprints, reports, and approval minutes.
Outputs are approved at the level that fits them: the Head of Entity, the Digital Transformation Committee, the EA Governance Committee, or the Chief Enterprise Architect.

Approval authorities

Head of Entity, or their delegate: approves the major strategic outputs such as the development-cycle scope and the roadmap.

Digital Transformation Committee, with the EA Governance Committee: approves outputs that sit where EA work meets digital-transformation priorities.

EA Governance Committee: approves the practice operational outputs from current-state diagnosis, future-state design, and gap analysis.

Chief Enterprise Architect, with the relevant unit where it applies: approves operational updates and day-to-day technical requirements.

Outputs of the seven stages

Stage	Main outputs
1. Defining the EA Development Cycle Scope	A scope document covering the targeted components and viewpoints, the responsibilities matrix, and formal approval of the scope.
2. Diagnosing the Current Situation	An inventory of the existing EA components in each domain, their analysis, and a current-state report with recommendations.
3. Exploring Future Trends	A review of the current-state findings, the results of studying similar practices, and a future design-trends document.
4. Designing the Future State	Future EA designs for each domain, with the approved blueprints and viewpoints.
5. EA Gap Analysis	A register of the gaps between the current and target states, with impact and prioritisation analysis.
6. Developing the Roadmap	A roadmap to deliver the target EA, covering initiatives, projects, priorities, and how each one ties to strategic performance indicators.
7. Managing EA Requirements	An approved requirements register, status tracking, and an assessment of how changes hit it.

Supporting elements

Key takeaway

Source: Guideline for Implementing the National Enterprise Architecture Methodology, issued by the Digital Government Authority.

EA Practice Outputs

At a glance

Approval authorities

Outputs of the seven stages

Supporting elements

Related

EA reports

EA procedures

National methodology

Ready to start?

EA Practice Outputs

At a glance

Approval authorities

Outputs of the seven stages

Supporting elements

Related

EA reports

EA procedures

National methodology

Ready to start?