language en

Linked.Archi EA on a Page Ontology

Release: 2020-07-27

Modified on: 2026-05-02
This version:
https://meta.linked.archi/eaonapage/onto/0.1.0#
Revision:
0.1.0
Issued on:
2020-07-27
Authors:
Kalin Maldzhanski
Publisher:
Linked.Archi
See also:
http://kotusev.com/
https://eaonapage.com/
https://www.bcs.org/articles-opinion-and-research/enterprise-architecture-on-a-single-page
https://www.bcs.org/articles-opinion-and-research/enterprise-architecture-practice-on-a-single-page
License:
http://creativecommons.org/licenses/by/4.0/
Visualization:
Visualize with WebVowl
Cite as:
Kotusev, S. (2019). Enterprise architecture and enterprise architecture artifacts: Questioning the old concept in light of new findings. Journal of Information Technology, 34(2), 102-128.
Provenance of this page
draft

Abstract

OWL ontology for the EA on a Page framework — artifact types, processes, participants, and maturity stages for evidence-based EA practice.

Linked.Archi EA on a Page Ontology: Overview back to ToC

This ontology has the following classes and properties.

Classes

Object Properties

Data Properties

Linked.Archi EA on a Page Ontology: Description back to ToC

Ontology for the Enterprise Architecture on a Page framework by Svyatoslav Kotusev. Models the CSVLOD artifact taxonomy (Considerations, Standards, Visions, Landscapes, Outlines, Designs), the three core EA processes (Strategic Planning, Initiative Delivery, Technology Optimization), EA practice participants, maturity stages, and the 24 empirically validated EA artifacts. Based on peer-reviewed research across 27+ organizations, this framework describes how EA practices actually work rather than prescribing how they should work.

Cross-reference for Linked.Archi EA on a Page Ontology classes, object properties and data properties back to ToC

This section provides details for each class and property defined by Linked.Archi EA on a Page Ontology.

Classes

Business Leaderc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#BusinessLeader

Participates in Strategic Planning. Provides business strategy input, approves Visions and investment priorities.
has super-classes
EA Practice Participant c

Considerationc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#Consideration

Global conceptual rules defining how an organization should operate from the IT perspective. Considerations provide overarching guidance for all IT-related decisions and plans. They are permanent, organization-wide, and rarely change. Typical examples: Principles, Policies, Guidelines.
Example
Principles, Policies, Technology Guidelines, Governance Standards.
has super-classes
EA Artifact c

Designc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#Design

Detailed descriptions of specific IT solutions providing enough information for implementation. Designs are project-scoped, detailed, and consumed by delivery teams. Typical examples: Solution Designs, Detailed Specifications, Interface Contracts, Data Models.
Example
Solution Designs, Detailed Technical Specifications, Interface Contracts,
Deployment Architectures.
has super-classes
EA Artifact c

EA Artifactc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#EAArtifact

An enterprise architecture artifact — a document, model, diagram, or other work product used in an EA practice for planning and decision-making. EA artifacts are classified into six general types by the CSVLOD taxonomy based on their usage and purpose.
has super-classes
element c
has sub-classes
Consideration c, Design c, Landscape c, Outline c, Standard c, Vision c
is in domain of
artifact lifecycle dp, artifact scope dp, artifact type op, usage frequency dp, used in process op
is in range of
process uses artifact type op

EA Maturity Stagec back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#MaturityStage

A stage in the maturity of an EA practice, characterized by the processes established, artifacts mastered, governance arrangements in place, and benefits realized.

EA Practice Participantc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#EAParticipant

A stakeholder who participates in EA practice processes.
has super-classes
stakeholder c
has sub-classes
Business Leader c, Enterprise Architect c, IT Leader c, Solution Architect c
is in range of
process participant op

EA Processc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#EAProcess

A core process in an EA practice as defined by the EA on a Page framework. EA practices consist of three distinct but interrelated processes that revolve around the six types of EA artifacts.
has super-classes
architecture process c
has sub-classes
Initiative Delivery c, Strategic Planning c, Technology Optimization c
is in domain of
process participant op, process uses artifact type op
is in range of
used in process op

Enterprise Architectc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#EnterpriseArchitect

Participates in all three EA processes. Develops and maintains Considerations, Visions, Standards, and Landscapes. Reviews Outlines and Designs.
has super-classes
EA Practice Participant c

Initiative Deliveryc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#InitiativeDelivery

The process of turning each IT investment into a working solution. Uses Outlines (initiative-level architecture) and Designs (detailed specifications) to guide project delivery. Involves solution architects and delivery teams.
has super-classes
EA Process c

IT Leaderc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#ITLeader

Participates in Strategic Planning and Technology Optimization. Approves Standards, prioritizes technology investments, and governs the IT landscape.
has super-classes
EA Practice Participant c

Landscapec back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#Landscape

High-level descriptions of the current IT landscape showing what exists today. Landscapes provide a shared factual baseline for planning and decision-making. They are continuously maintained and updated as the landscape changes. Typical examples: Landscape Diagrams, Inventories, Enterprise System Portfolios, Integration Maps.
Example
Application Landscape Diagrams, Technology Inventories, System Portfolios,
Integration Maps, Data Flow Diagrams.
has super-classes
EA Artifact c

Outlinec back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#Outline

High-level descriptions of specific IT initiatives explaining their overall structure and approach. Outlines provide enough architectural context for investment decisions without going into implementation detail. They are initiative-scoped and short-lived. Typical examples: Solution Overviews, Options Assessments, Initiative Architectures.
Example
Solution Overviews, Options Assessments, High-Level Designs,
Architecture Briefs.
has super-classes
EA Artifact c

Solution Architectc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#SolutionArchitect

Primarily participates in Initiative Delivery. Develops Outlines and Designs for specific initiatives, guided by Considerations and Standards.
has super-classes
EA Practice Participant c

Standardc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#Standard

Proven reusable solutions for common IT problems. Standards provide approved technologies, patterns, and reference models that should be used across the organization. They are permanent, organization-wide, and updated periodically as technologies evolve. Typical examples: Technology Reference Models, IT Principles, Guidelines, Patterns.
Example
Technology Reference Models, Integration Patterns, Platform Standards,
Security Standards.
has super-classes
EA Artifact c

Strategic Planningc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#StrategicPlanning

The process of converting business strategy into a desired IT investment portfolio. Uses Considerations (governance rules) and Visions (future-state descriptions) to align IT investments with business direction. Involves senior business and IT leaders.
has super-classes
EA Process c

Technology Optimizationc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#TechnologyOptimization

The process of rationalizing the existing IT landscape. Uses Standards (approved technologies and patterns) and Landscapes (current-state descriptions) to identify optimization opportunities. Involves enterprise architects and technology specialists.
has super-classes
EA Process c

Visionc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#Vision

High-level conceptual descriptions of the desired future state of the organization from the IT perspective. Visions provide long-term direction and are used to align IT investments with business strategy. They are long-lived but evolve as strategy changes. Typical examples: Business Capability Models, Target State Architectures, Roadmaps, Value Chains.
Example
Business Capability Models, Target State Architectures, IT Roadmaps,
Value Chain Maps.
has super-classes
EA Artifact c

Object Properties

artifact typeop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#artifactType

Classifies an EA artifact by its CSVLOD type.
has domain
EA Artifact c

process participantop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#processParticipant

Links an EA process to a participant role.
has domain
EA Process c
has range
EA Practice Participant c

process uses artifact typeop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#processUsesArtifactType

Links an EA process to the artifact types it uses.
has domain
EA Process c
has range
EA Artifact c

used in processop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#usedInProcess

Links an EA artifact type to the process that uses it.
has domain
EA Artifact c
has range
EA Process c

Data Properties

artifact lifecycledp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#artifactLifecycle

The temporal lifecycle of an artifact: permanent (Considerations, Standards), long-lived (Visions, Landscapes), or short-lived (Outlines, Designs).
has domain
EA Artifact c
has range
string

artifact scopedp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#artifactScope

The organizational scope of an artifact: organization-wide (Considerations, Standards, Visions, Landscapes) or initiative-scoped (Outlines, Designs).
has domain
EA Artifact c
has range
string

usage frequencydp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#usageFrequency

How commonly the artifact is used across organizations: essential (majority), common (25-50%), or uncommon (10-25%). Based on empirical research across 27+ organizations.
has domain
EA Artifact c
has range
string

Legend back to ToC

c: Classes
op: Object Properties
dp: Data Properties

Acknowledgments back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.