Six enterprise architecture domains that fit together to give a complete picture of the entity from more than one angle. Each domain has its own national reference model and a set of principles set out in the National Enterprise Architecture Methodology guideline.
Overview
Where this page sits in NORA: Section I — Domains and Principles of the National Enterprise Architecture.
In brief
Six enterprise architecture domains that fit together to give a complete view of the entity from more than one angle.
Each domain has its own national reference model issued by the Digital Government Authority, plus a set of principles set out in the methodology guideline.
Strategic alignment starts at business architecture and then carries through to the rest, so the outputs stay in line with the entity direction.
Business Architecture
The first entry point into enterprise architecture. Links the entity strategy to its technical enablers, and covers business capabilities, entity services, business processes, organisational structure, and policies.
Beneficiary Experience Architecture
One of the new domains in the framework. Designs and improves the beneficiary experience across the entity services by mapping every point of interaction and identifying needs and expectations. Covers external and internal beneficiaries.
Application Architecture
The link between business and beneficiary experience on one side and the technical domains on the other. Defines the digital applications used or needed to digitise the entity operations, services, and the data tied to them.
Data Architecture
Defines and develops the entity data assets, including sources, ownership, classification, structuring, and storage, to support decision-making and meet the requirements of the National Data Management Office.
Technology Architecture
Defines and develops the technical infrastructure components, including equipment, systems, and networks, to give the entity a digital infrastructure with a secure and reliable technical base.
Security Architecture
Identifies and updates the tools and services that protect technical assets from breaches and threats, addresses vulnerabilities, and supports compliance with the requirements of the National Cybersecurity Authority.
Domain relationships
The development cycle starts at Business Architecture as the first entry point, runs through the rest of the domains, and ends at Security Architecture, which cuts across the others to protect their components.
Business
Beneficiary Experience
Applications
Data
Technology
Security
Strategic alignment
Strategic alignment starts at business architecture. Its components map straight to the entity goals, indicators, initiatives, and projects, then extend to the other domains, so the technical outputs keep serving the strategic direction and update with it whenever it shifts.
The EA development cycle treats the six domains as one integrated picture, yet each domain components are documented and developed on their own, then aligned with the rest through the methodology stages. Every domain has its own national reference model.
