SAHM

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

Accept
Decline
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

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 Principles

Fundamental guidelines that govern decision-making and the development of EA components across all domains.

Overview

  • Define a set of principles for each of the six EA domains.
  • Principles are not exhaustive and can be extended with domain specialists.
  • Ensure standardisation, consistency, and alignment across components.

Principles Catalog by Domain

Business Architecture
CodePrincipleRationale
BA 01Strategic AlignmentLink business strategy to EA to deliver added value.
BA 02Innovation and CreativityAdopt innovation in investment decisions for emerging technology.
BA 03Co-creation & InteroperabilityCollaborative work between internal units and external stakeholders.
BA 04Unified Documentation & ExecutionFollow unified reference standards for documenting capabilities and services.
BA 05Business ContinuityEnsure continuity of critical capabilities and services in all circumstances.
BA 06Regulatory ComplianceComply with all laws and policies when developing business architecture.
Beneficiary Experience Architecture
CodePrincipleRationale
XA 01Beneficiary CentricityAlign with DGA beneficiary-centric policy.
XA 02Beneficiary SegmentationStudy all beneficiary segments and their needs.
XA 03Life ExperienceAchieve full coverage and integration in service delivery.
Application Architecture
CodePrincipleRationale
AP 01Fit for PurposeDefine application functions that fit business digitisation.
AP 02Based on StandardsBuild on global standards while complying with national policies.
AP 03Ease of UseDesign easy-to-learn applications with multi-channel access.
AP 04Secured by DesignIntegrate security into the design of all components.
AP 05Adaptable & ScalableAccommodate changes in requirements and workload systematically.
AP 06ReusableDesign modules to operate independently and be reusable.
Data Architecture
CodePrincipleRationale
DA 01Single Request for DataRequest data from beneficiaries once; integrate with sources.
DA 02Single Data SourceRely on a single trusted source per data entity.
DA 03Data Governance ComplianceComply with approved data management and governance standards.
DA 04Support Analysis & Decision MakingUse data to support leadership in decision-making.
DA 05360-Degree ViewFull documentation of data entities and their relationships.
Technology Architecture
CodePrincipleRationale
TA 01Cloud FirstCloud computing as a core part of technology strategy.
TA 02Compliance with StandardsComply with national and global standards (NCA, ISO, NIST).
TA 03Business Led ChangesRespond to business needs and plan changes accordingly.
TA 04Control Technical DiversityReduce maintenance costs and unify technologies.
TA 05Resilience & High AvailabilityResilient infrastructure with redundancy and failover.
TA 06Cost OptimizationDesign for best cost use and efficiency.
TA 07Scalability & PerformanceDesign scalable solutions with optimal performance.
TA 08Environmental SustainabilityConsider sustainability and reduce carbon impact.
Security Architecture
CodePrincipleRationale
SA 01Least PrivilegeRestrict permissions to the minimum required for the role.
SA 02Defense in DepthApply multiple layers of security controls.
SA 03Zero Trust ArchitectureSecurity model based on "never trust, always verify".
SA 04Strong Identity FoundationEstablish a unified IAM framework.

Compliance & Expected Outputs

Compliance status (compliant, non-compliant, partially compliant, not applicable, unknown) can be measured for technical specifications, workbooks, designs, and proposals.

Governance Note

Expected outputs include EA principle cards for all domains, linking principles to EA requirements per domain, and compliance status. These principles improve EA governance and achieve cost efficiency in investment decisions.

Related Topics

Standards & Specs

Six EA Domains

Establishing Practice

EA Principles | NORA | SAHM