Back to Guides

General component model for EA

The general component model (metamodel) for EA is a cornerstone of the EA practice in entities: it defines all components that belong to the EA domains. It is a reference used to build EA views and helps entities identify EA components, their attributes, and the relationships between them.

Component model guide

At a glance

6
domains
1
general model
Building blocksComponents, attributes, relationships. Each block belongs to one domain.
ViewsCatalogs, matrices, visual views from the general model
Browse as a siteDiagramCards

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 (business, user experience, applications, data, technology, security). Relationships connect components within a domain and with components in other domains.

Objectives of the general component model

The general component model aims to provide the guidance components needed so that entities can define their own general component model and develop their EA components. The main objectives are:

Provide a clear, detailed reference for building the entity’s general component model in line with international best practice and national regulatory requirements, and for configuring the EA tool and speeding up digitisation of EA practice.

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

Emphasise the importance of defining the right relationships between EA components in the same domain and with components in other EA domains.

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

Key considerations for preparing the general component model

This guide provides a reference model only. The EA team should choose, add, or modify building blocks to fit the entity’s needs. The general model should be reviewed and updated periodically.

Define whether documenting components and their attributes is mandatory or optional when designing the entity’s general component model.

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

Consider the language(s) used to document component content and attributes; more than one language may be used.

Define and document fixed values for some component attributes as predefined lists (e.g. currency, date/time format, priority list).

When designing EA views, ensure all required components and relationships are available; if not, update the general component model to meet the new views’ requirements.

EA management must coordinate with relevant units (e.g. organisational excellence, cybersecurity, IT) to develop EA domain components that relate to their work.

Overall landscape of the general component model

The general component model represents all building blocks used to describe the entity from an EA perspective, distributed across the EA domains to which each block belongs. The guideline defines and details the attributes of each component and the main relationships between components. Additional relationships may be defined as needed by the entity.

Strategic alignment components are not part of the EA domains assigned to the EA management unit; but to ensure a holistic view and alignment of EA components with the entity’s strategic components, a number of reference components have been defined in the general component model.

Building blocks by domain (detail)

The guide defines the building blocks per domain, their attributes (and type of each attribute), and their relationships with building blocks in other domains. From these building blocks, catalogs, matrices, and views are built to serve different stakeholder perspectives.

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

Strategic alignment

Vision

The long-term goal the entity seeks to achieve; describes a future state or benefit that reflects the entity’s ambition.

Mission

The purpose and reason for the entity’s existence, plus the values and main activities that support the vision.

Goal

Levels of performance, outputs, and results the entity aims to achieve within a set period, aligned with its vision and mission.

Pillar

Specific focus areas to support achieving the entity’s goals by setting work priorities and directing resources and capabilities.

Initiative

A logical grouping of projects and programmes within a defined scope under the entity’s strategic direction to achieve strategic goals.

Project

A set of activities and tasks carried out within a set period using defined resources (time, budget, people) to achieve a specific goal.

KPI

The measure used to assess success or progress towards approved goals or to calculate the efficiency of a given task using a defined formula and inputs.

Business architecture

Business capability

The strategic and operational capability that distinguishes the entity and enables it to achieve its goals; includes skills, knowledge, technology, financial resources, and relationships.

Organizational unit

Part of the entity’s organisational structure with defined responsibilities; the set of units forms the entity’s full organisational structure and may include sub-units.

Service provider

Any external entity or individual that participates in delivering the entity’s work or services under a joint agreement defining tasks and responsibilities.

Service

The value the entity (or organisational unit) delivers to the beneficiary through a set of activities or procedures.

Process group

A logical set of interrelated work procedures that serve one or more business capabilities.

Work procedure

A sequence of steps or activities performed by a person or group to achieve a specific goal or outcome, according to the level of detail documented.

Product

The final output from performing an activity or successfully delivering a service; may be a tangible or digital product.

Job title

The organisational makeup of tasks and responsibilities of the entity’s staff within the work context.

Role

The behaviour embodied by a given position when contributing to a procedure or service; a position may have several roles.

Policy

The organisational framework that sets the principles and controls to be followed when carrying out tasks and work, and provides guidance on the scope of an organisational unit.

Template

The template used to deliver services or execute work procedures; a logical container for collecting required data.

Activity

The detail of how a specific procedure is carried out.

User (beneficiary) experience architecture

Beneficiary

Any individual or entity that benefits from the services provided by the entity (or an internal organisational unit).

Beneficiary journey

How the beneficiary interacts with the entity across all stages of service delivery.

Persona

A representative sample of a segment of beneficiaries who share goals, needs, experiences, and behaviours.

Phase

A set of defined steps within a clear timeframe that the beneficiary goes through when dealing with the entity to obtain a service or achieve value.

Step

A step the beneficiary takes or interacts with within each phase of their journey with the entity.

Data architecture

Data entity

A set of data that shares the same properties and has similar behaviour; elements used to represent the entity’s activity in a service, work, or procedure.

Data store

Information on where data is stored and kept, electronic or paper, including structured, semi-structured, and unstructured data.

Data attributes

A set of shared components that together form the data entity.

Applications architecture

Application

A programme or technical tool designed to perform specific functions for the user directly through the software life cycle.

Application component

A set of core, multi-function software units; each unit is distinct and can perform a unique function or set of related functions within the application.

Application function

A more precise, defined task or process performed by the application; usually implemented as a programme function, i.e. a set of software operations that perform a specific task.

Technical integration interface

A technical connection point used by the application to exchange data, automate technical linkage between functions and procedures, or manage event flow.

Technology architecture

Data centre

The place the entity uses to host computing components (servers, storage, network, applications and services), whether owned by the entity or hosted with a cloud provider.

Physical host

The physical hardware the entity owns (stand-alone, racked, or part of HCI or blade servers); may host virtual servers; includes manufacturer, resources, and network location.

Server

The server used to host systems, applications, services, and databases; physical or virtual; includes OS, resources, and environment type (production, development, test, staging).

Container engine

Container engines used by the entity; includes data centre, manufacturer, position in network layers, environment type, and end-of-support date.

Network device

Network devices of various types owned by the entity at its sites and data centres; includes location, manufacturer, position in network structure, and device type and function.

Network link

Network connectivity to link devices to each other or other components, or to connect to the internet or to branches and data centres; includes link types, technologies, speeds, providers, bandwidth, and cost.

Storage

Devices and tools used to store systems, software, and data; includes storage capacity and device type and version.

Infrastructure service

Core services provided by the technology infrastructure (e.g. DNS, directory service, network address distribution, text, voice, or video communication).

Infrastructure tool

Tools or software used to manage, monitor, run, or support infrastructure components (e.g. network and server performance and availability monitoring); includes provider and end-of-support date.

Peripheral device

Peripheral devices used by the entity (desktop, laptop, printers, scanners); includes manufacturer, operating systems, and location.

Licence

A usage agreement for hardware or software used by the entity (perpetual or subscription); includes quantity, acquisition date, and expiry date.

Security architecture

Security device

Security solution devices used to achieve information security; includes manufacturer, technical specifications, end-of-support date, and licences.

Security software

Software or tools used to achieve information security; includes provider, licences used, and end-of-support date.

Security service

An agreement between the entity and a security services provider (e.g. managed SOC, penetration testing); provides information on service type, scope, SLA, start/end dates, and cost.

Expected outputs

The entity must document all components of the general component model in a single document that includes:

Overall landscape of the general component model

Definition of strategic alignment building blocks + attributes + relationships with other domains

Definition of business architecture building blocks + attributes + relationships

Definition of user experience architecture building blocks + attributes + relationships

Definition of data architecture building blocks + attributes + relationships

Definition of applications architecture building blocks + attributes + relationships

Definition of technology architecture building blocks + attributes + relationships

Definition of security architecture building blocks + attributes + relationships

Related topics

Six domains

Reference models

EA views