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

General Component Model for EA

The general component model (metamodel) is the technical foundation of EA practice, defining all components, attributes, and relationships across the six EA domains.

What Is the General Component Model?

  • A conceptual framework that describes EA components at conceptual, logical, and physical levels and links domains.
  • Each building block is defined once only and belongs to one of the six EA domains.
  • Relationships connect components within a domain and with components in other domains.

Model Structure

Strategic Alignment

Vision, Mission, Goal, Pillar, Initiative, Project, KPI

Business Architecture

Business capability, Organisational unit, Service, Work procedure, Policy, Role

Beneficiary Experience Architecture

Beneficiary, Beneficiary journey, Persona, Phase, Step

Data Architecture

Data entity, Data store, Data attributes

Applications Architecture

Application, Application component, Application function, Integration interface

Technology Architecture

Data centre, Server, Network device, Storage, Licence

Security Architecture

Security device, Security software, Security service

From building blocks, catalogs, matrices, and views are built to serve different stakeholder perspectives.

Objectives

Provide a clear, detailed reference for building the entity's general component model in line with international best practice and national regulatory requirements.

Speed up the process of identifying the building blocks needed to document and develop EA components.

Emphasise the importance of defining relationships between EA components within and across domains.

Support the configuration of tools used to document and develop EA components (EA tools).

Key Considerations

This guide provides a reference model only. The EA team should choose, add, or modify building blocks to fit the entity's needs.

Each building block is defined once only in the general component model and is assigned to one EA domain only.

When designing EA views, ensure all required components and relationships are available.

EA management must coordinate with relevant units (e.g. organisational excellence, cybersecurity, IT).

The guideline for building the general component model is issued by the Digital Government Authority (DGA) under NORA.

Related Topics

Six Domains

Reference Models

Practice Outputs

General Component Model for EA | NORA Guide | SAHM