EA Procedures under NORA

The National Enterprise Architecture Methodology uses a defined set of procedures to run its seven stages and govern requirements. This page lists the procedures that NORA names explicitly together with the procedures embedded inside the stages, using the names adopted by the Digital Government Authority.

Overview

Where this page sits: operating procedures for the EA practice. The procedure NORA names by name (temporary exemptions) sits under change governance.
Seven stages form the EA development cycle, starting with scope definition and ending with requirements management.
The procedure for Managing Temporary Exemptions for Non-Compliance with Defined Standards is the only procedure NORA names in full.
The other procedures are drawn from the stage steps themselves: approving scope, diagnosing the current state, studying future trends, designing the future state, analysing gaps, building the roadmap, and governing requirements.

Procedures across the seven stages

Stage	Procedure
Stage 1: Defining the Scope of the EA Development Cycle	Review the entity strategic directions, set the domains, viewpoints, and levels of detail, and approve the development cycle charter.
Stage 2: Diagnosing the Current State	Document the current components for each domain individually, then analyse them in an integrated way to surface strengths and weaknesses.
Stage 3: Identifying and Studying Future Trends	Study local and global experiences and national requirements, and agree on the future-trend features for each domain.
Stage 4: Designing the Future State	Draft the initial future vision for the components, align them across domains, and detail them inside the approved viewpoints.
Stage 5: Analysing EA Gaps	Compare the current and future states, identify gaps and their impact, and propose solutions aligned with the entity priorities.
Stage 6: Developing the Roadmap to Achieve the Objectives	Build the list of initiatives and projects, prioritise them by impact and ease of implementation, and reconcile them with owners of other strategies.
Stage 7: Managing EA Requirements	A continuous procedure that runs in parallel with the other stages: approve requirements, monitor their states, and assess the impact of changes on them.

Requirements management procedures (Stage 7)

Approve EA Requirements: the Chief EA Architect documents the requirement and its eight fields, then analyses its impact on the approved list and re-prioritises.

Monitor the State of EA Requirements: the team tracks the requirement from inception to closure and updates its state after each stage, on cancellation or amendment, or when a new requirement affects it.

Assess the Impact of Changes in EA Requirements: the team evaluates the change against the cycle scope and against digital initiative execution, then decides to keep the scope, adjust it, or halt the cycle and redefine it.

Temporary exemptions procedure

The procedure for Managing Temporary Exemptions for Non-Compliance with Defined Standards applies during digital initiative and project execution when there is a slight variance between project outputs and EA requirements, provided the non-compliance does not significantly affect any EA domain. It grants an exception or temporary exemption, then updates the requirement and its state with a note about the exception or exemption.

When it applies: a slight variance between digital project outputs and an approved requirement, with no major impact on the domain.

Decision: grant a temporary exemption through this procedure instead of rejecting the requirement or stalling the project.

Impact: update the requirements register with an exception or exemption flag and record the justification.

Limits: the procedure does not apply when non-compliance touches an entire EA domain.

EA governance procedures

Procedure	Purpose
Governing Digital Initiative and Project Execution	Verify alignment between digital project outputs and EA principles and future components, and trigger the temporary exemptions procedure when needed.
Governing the List of Ongoing and Scheduled Projects	Review the project list and adjust scopes to serve the entity objectives and EA priorities.
Governing the EA Component Development Cycle	Track the seven stages, approve the outputs between stages, and keep the change record.
Governing the EA Requirements Register	Maintain a central requirements register and control the lifecycle from approval to closure across the eight states.

Reference note

Key takeaway

This page uses the names adopted by the National Enterprise Architecture Methodology, issued by the Digital Government Authority under NORA. The only procedure named in full is Managing Temporary Exemptions for Non-Compliance with Defined Standards. The remaining procedures are drawn from the wording of the seven stages and the requirements management steps. Entities can add their own operational procedures without overriding the official names.

Change governance

Managing temporary exemptions and change impact.

Requirements management

Governing requirements across the development cycle.

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.

EA Procedures under NORA

Overview

Where this page sits: operating procedures for the EA practice. The procedure NORA names by name (temporary exemptions) sits under change governance.
Seven stages form the EA development cycle, starting with scope definition and ending with requirements management.
The procedure for Managing Temporary Exemptions for Non-Compliance with Defined Standards is the only procedure NORA names in full.
The other procedures are drawn from the stage steps themselves: approving scope, diagnosing the current state, studying future trends, designing the future state, analysing gaps, building the roadmap, and governing requirements.

Procedures across the seven stages

Stage	Procedure
Stage 1: Defining the Scope of the EA Development Cycle	Review the entity strategic directions, set the domains, viewpoints, and levels of detail, and approve the development cycle charter.
Stage 2: Diagnosing the Current State	Document the current components for each domain individually, then analyse them in an integrated way to surface strengths and weaknesses.
Stage 3: Identifying and Studying Future Trends	Study local and global experiences and national requirements, and agree on the future-trend features for each domain.
Stage 4: Designing the Future State	Draft the initial future vision for the components, align them across domains, and detail them inside the approved viewpoints.
Stage 5: Analysing EA Gaps	Compare the current and future states, identify gaps and their impact, and propose solutions aligned with the entity priorities.
Stage 6: Developing the Roadmap to Achieve the Objectives	Build the list of initiatives and projects, prioritise them by impact and ease of implementation, and reconcile them with owners of other strategies.
Stage 7: Managing EA Requirements	A continuous procedure that runs in parallel with the other stages: approve requirements, monitor their states, and assess the impact of changes on them.

Requirements management procedures (Stage 7)

Approve EA Requirements: the Chief EA Architect documents the requirement and its eight fields, then analyses its impact on the approved list and re-prioritises.

Temporary exemptions procedure

When it applies: a slight variance between digital project outputs and an approved requirement, with no major impact on the domain.

Decision: grant a temporary exemption through this procedure instead of rejecting the requirement or stalling the project.

Impact: update the requirements register with an exception or exemption flag and record the justification.

Limits: the procedure does not apply when non-compliance touches an entire EA domain.

EA governance procedures

Procedure	Purpose
Governing Digital Initiative and Project Execution	Verify alignment between digital project outputs and EA principles and future components, and trigger the temporary exemptions procedure when needed.
Governing the List of Ongoing and Scheduled Projects	Review the project list and adjust scopes to serve the entity objectives and EA priorities.
Governing the EA Component Development Cycle	Track the seven stages, approve the outputs between stages, and keep the change record.
Governing the EA Requirements Register	Maintain a central requirements register and control the lifecycle from approval to closure across the eight states.

Reference note

Key takeaway

EA Procedures under NORA

Overview

Procedures across the seven stages

Requirements management procedures (Stage 7)

Temporary exemptions procedure

EA governance procedures

Reference note

Related

Change governance

Requirements management

National methodology

Ready to start?

EA Procedures under NORA

Overview

Procedures across the seven stages

Requirements management procedures (Stage 7)

Temporary exemptions procedure

EA governance procedures

Reference note

Related

Change governance

Requirements management

National methodology

Ready to start?