Skip to main content
SAHM

This site uses cookies to improve your experience and analyze visits.

Accept all
Reject all (essential only)
Customize
Learn more about cookies
SAHM logo
  • Home
  • About
  • Pricing
  • Knowledge Hub
  • Support
  • Book a Meeting
  • Customer Portal
  • Employee Portal
  • Contact
Menu

Language

Services

Digital TransformationEnterprise ArchitectureNORA ComplianceEA Tool ImplementationPricing

Expertise

TOGAF FrameworkDGA NORAAvolution ABACUSIT Strategy

Company

About UsContact Us

Resources

Schedule ConsultationRequest DemoCustomer SupportSubmit Ticket

Legal

Privacy PolicyTerms of ServiceCookie PolicyAccessibilitySecurity Policy

Get in touch

info@sahm.sa+966 53 113 0434

2023 - 2026 © SAHM Information Technology. All Rights Reserved. | Riyadh, Saudi Arabia

Back to Guides

Managing EA Requirements & Change Governance

Stage 7 of the national EA methodology: approving requirements, tracking their status, and assessing how changes affect the development cycle and ongoing digital projects, alongside the EA governance procedures.

In Brief

  • Placement in NORA: Section II — Stage 7 procedure: Managing Temporary Exemptions for Non-Compliance with Defined Standards.
  • A continuous stage that runs in parallel with every stage of the EA development cycle.
  • Three steps: approving the EA requirements, tracking their status, and assessing the impact of changes on them.
  • EA governance procedures are applied to digital initiatives and projects to check that delivery matches the requirements.
  • When the gap is minor, the procedure for managing temporary exemptions for non-compliance with defined standards is used.

Steps of Stage 7

Approving EA requirementsThe Chief Enterprise Architect logs each requirement reaching the team after validating it, capturing the requirement code, text, source, domain, the EA domains it affects, related requirements, current state, and implementation priority.
Tracking requirement statusThe EA team follows each requirement from start to closure and updates its state after every stage of the development cycle, on cancellation, when the stakeholder asks for a change, or while the initiative addressing it is being delivered.
Assessing the impact of changesThe team assesses the impact of any change, whether it falls inside the development cycle (no scope change, scope adjustment, or cycle suspension) or surfaces during digital project delivery through the EA governance procedures.
Applying governance to projectsWhen project outputs match the requirement, only the status is updated. When the gap is minor, the temporary exemptions procedure is run. When outputs do not match, the team studies the reason and either rejects the change or updates the requirement on the basis of a valid justification.

Outcomes of Applying the Procedures to Digital Projects

Verification ResultAction Taken
Project outputs match the requirementsNo corrective action is needed; the requirement status is simply updated.
Minor gap between project outputs and the requirementsThe procedure for managing temporary exemptions for non-compliance with defined standards is run, provided the non-compliance does not have a significant effect on any EA domain. The requirement and its status are then updated with a note that an exception or exemption is in place.
Project outputs do not match the requirementsThe EA team studies the reasons for the gap and either rejects the change (no valid justification), or updates the requirement and its status on the basis of a valid justification — for example, when a specific technology cannot be used because of national laws or standards.
Change impact during the development cycleThree options depending on the size of the impact: no scope change, a scope adjustment with cycle rescheduling, or suspending the cycle and rerunning the "Defining the Scope of the Development Cycle" stage.
In studying and approving requirements, the Chief Enterprise Architect weighs the assumptions and constraints of each one, the principles attached to the affected domains, and the related policies, standards, and guidelines. Requirements management is tied directly to the entity’s EA governance procedures, and depends on regular contact with project managers to keep an accurate picture of how each requirement is being delivered.

Related

EA Requirements Management

Governance & Committees

National Methodology

Managing EA Requirements & Change Governance | NORA Guide | SAHM