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

EA Specifications and Artifacts

The National Enterprise Architecture Methodology defines a set of specifications and reference artifacts: the EA Content Metamodel, the six reference models, viewpoints, and the requirement record with its fields and states. This page lists them as they appear in the methodology.

Overview

  • Where this page sits: EA specifications and artifacts the practice produces, tied to the EA Content Metamodel and to the Stage 7 requirement records.
  • The EA Content Metamodel defines every component used to document EA information and build the different viewpoints.
  • Six national reference models stem from the metamodel, one for each of the six domains.
  • Entities use viewpoints to present components to stakeholders at different levels of detail, and every requirement is held in the requirements register across eight fields and eight states.

EA Content Metamodel

DomainRole of the Domain in the Metamodel
Business ArchitectureHolds the business capabilities, organisational units, process groups, services, business processes, positions, policies, roles, activities, and products.
Beneficiary Experience ArchitectureDescribes beneficiary segments, journeys, touchpoints, service channels, and the indicators that measure the experience.
Data ArchitectureDefines data entities, attributes, relationships, data owners, and classification and governance levels.
Applications ArchitectureDefines applications, their functions, interfaces, integrations, and their link to capabilities and services.
Technology ArchitectureDefines the infrastructure components: servers, networks, databases, cloud platforms, and operating environments.
Security ArchitectureDefines the protection controls, access mechanisms, identity management, and cybersecurity compliance requirements.

The Six National Reference Models

Models Derived from the Metamodel
1

Business Architecture Reference Model: administrative, core, and supporting capabilities, drawing on APQC and Saudi government practices.

2

Beneficiary Experience Reference Model: components built on the centralised beneficiary policy and international customer experience references.

3

Data Architecture Reference Model: aligned with the national data governance policies and personal data protection controls.

4

Applications Architecture Reference Model: reference components aligned with DGA regulations and national solutions.

5

Technology Architecture Reference Model: components built on the cloud computing guideline and business continuity controls.

6

Security Architecture Reference Model: components based on ISO 27001, Zero Trust Architecture, and National Cybersecurity Authority controls.

Viewpoints and Levels of Detail

Viewpoints are structured presentations of EA components that serve stakeholders at levels of detail ranging from a high-level view down to operational specifics. The viewpoints are set in the development cycle charter at Stage 1, then built up inside the current- and future-state documentation.
1

Capability viewpoint: links administrative, core, and supporting capabilities to services and procedures.

2

Service viewpoint: shows services, their channels, and their link to capabilities and applications.

3

Data viewpoint: presents data entities, their relationships, and their governance.

4

Applications viewpoint: shows applications, their functions, and their integrations.

5

Technology viewpoint: presents the infrastructure and the operating environments.

6

Security viewpoint: presents controls and protection and compliance requirements.

Requirement Record: Eight Fields and Eight States

FieldDescription
Requirement CodeThe approved identifier for the requirement, used for tracking and reference.
Requirement TextA description of the challenge to be addressed through the EA components.
Requirement SourceThe entity or stakeholder that raised the requirement.
Requirement DomainThe primary EA domain to which the requirement belongs.
Affected DomainsThe other domains whose components must be developed to address the requirement.
Related RequirementsThe codes of related requirements that may affect the processing of this one.
Requirement StateThe current position of the requirement in its lifecycle, per the eight approved states.
Implementation PriorityThe priority level of the requirement: High, Medium, or Low.
The Eight Approved Requirement States
1

Approved

2

Suspended

3

Canceled

4

Current State

5

Future State

6

Planned for Implementation

7

In Progress

8

Completed

Reference Note

These specifications follow the National Enterprise Architecture Methodology, issued by the Digital Government Authority under NORA, with its names for the metamodel, the six reference models, the viewpoints, and the requirements register. Entities can add their own components or fields inside the register, as long as the eight approved fields and eight states remain in place.

Related

EA practice outputs

Requirements management

General component model

EA Specifications and Artifacts under NORA | NORA Guide | SAHM