Model Concepts (OWL Ontology)
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), process phases and
governance activities, EA practice participants, governance bodies and tiers,
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.
This is not an official IASA document.
https://meta.linked.archi/eaonapage/onto#
Formal Rules (SHACL Shapes)
SHACL validation shapes for the EA on a Page framework. Validates
artifact instances, process-artifact mappings, governance arrangements, and
maturity stage consistency. These shapes encode the structural rules implicit
in the EA on a Page framework.
https://meta.linked.archi/eaonapage/shapes#
Concept Classification (SKOS)
Classification of 24 EA artifacts by CSVLOD type and usage frequency.
https://meta.linked.archi/eaonapage/tax#EAOnAPageScheme
Architecture Viewpoints
Viewpoints for the EA on a Page framework. Each viewpoint specifies
the artifact types it includes, the stakeholders it targets, and the purpose it
serves. Derived from the CSVLOD artifact taxonomy and the three core EA processes
described by Kotusev.
EA on a Page does not formally define viewpoints, but its artifact types and
processes imply a natural set of viewpoints that practitioners use in practice.
These viewpoints formalize those implicit conventions.
https://meta.linked.archi/eaonapage/viewpoints#
Viewpoint Library (SKOS)
Classification of EA on a Page viewpoints by the EA process they
primarily support: Strategic Planning, Technology Optimization, or Initiative
Delivery.
https://meta.linked.archi/eaonapage/viewpoints#ViewpointCatalog
Deliverable Templates
A strategic document that captures the organization's architecture
principles, policies, and high-level direction. Combines Considerations (governance
rules) with Visions (future-state descriptions) to articulate how IT investments
should be guided. Typically produced annually or when business strategy changes
significantly.
https://meta.linked.archi/eaonapage/deliverable-templates#ArchitectureStrategy
Deliverable Templates
A document that defines the organization's technology standards,
approved technology stack, and rationalization roadmap. Combines Standards
(approved technologies) with Landscapes (current state) to identify optimization
opportunities and plan technology evolution.
https://meta.linked.archi/eaonapage/deliverable-templates#TechnologyStrategy
Deliverable Templates
A structured catalog of approved technologies organized by functional
area. Each technology entry includes lifecycle status (invest, maintain, contain,
retire), ownership, and usage guidelines. The primary Standards artifact.
https://meta.linked.archi/eaonapage/deliverable-templates#TechnologyReferenceModelDocument
Deliverable Templates
A concise document produced during the Initiation phase that
describes a proposed initiative at a high level — business context, proposed
approach, key assumptions, and estimated effort. Used to secure initial
approval and funding for further architecture work.
https://meta.linked.archi/eaonapage/deliverable-templates#SolutionBrief
Deliverable Templates
A document produced during the Initiation phase that describes
the proposed solution at a level sufficient for investment decisions. Includes
the solution concept, options assessment, standards compliance check, and
recommended approach. The primary Outline artifact.
https://meta.linked.archi/eaonapage/deliverable-templates#SolutionOverviewDocument
Deliverable Templates
A detailed document produced during the Realization phase that
specifies the solution architecture at a level sufficient for implementation.
Includes component design, interface contracts, data models, deployment
topology, and non-functional requirements. The primary Design artifact.
https://meta.linked.archi/eaonapage/deliverable-templates#SolutionDesignDocument
Deliverable Templates
A document that captures the organization's architecture principles
and policies — the Considerations artifacts. Principles are high-level governance
rules that guide all IT-related decisions. Policies are specific mandatory rules.
Typically maintained by enterprise architects and approved by the steering
committee.
https://meta.linked.archi/eaonapage/deliverable-templates#ArchitecturePrinciplesDocument
Deliverable Templates
A time-sequenced plan showing the transition from current state to
target state. Combines strategic direction (Visions) with current reality
(Landscapes) to produce a phased investment plan. Typically maintained
quarterly and presented to business and IT leadership.
https://meta.linked.archi/eaonapage/deliverable-templates#RoadmapDocument
Reference Data
Classification of EA practice maturity into four stages based on
empirical observation across 27+ organizations. Describes what is typically
observed at each stage, not what should be achieved in a linear progression.
https://meta.linked.archi/eaonapage/tax#MaturityScheme
Reference Data
Classification of EA governance arrangements including architecture
tiers, governance body types, and governance activities. Based on EA Function
on a Page by Kotusev.
https://meta.linked.archi/eaonapage/tax#GovernanceScheme
| Type | Resource | Description | URI |
| Model Concepts (OWL Ontology) |
onto |
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), process phases and
governance activities, EA practice participants, governance bodies and tiers,
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.
This is not an official IASA document. |
https://meta.linked.archi/eaonapage/onto# |
| Formal Rules (SHACL Shapes) |
shapes |
SHACL validation shapes for the EA on a Page framework. Validates
artifact instances, process-artifact mappings, governance arrangements, and
maturity stage consistency. These shapes encode the structural rules implicit
in the EA on a Page framework. |
https://meta.linked.archi/eaonapage/shapes# |
| Concept Classification (SKOS) |
EA on a Page Artifact Classification |
Classification of 24 EA artifacts by CSVLOD type and usage frequency. |
https://meta.linked.archi/eaonapage/tax#EAOnAPageScheme |
| Architecture Viewpoints |
viewpoints |
Viewpoints for the EA on a Page framework. Each viewpoint specifies
the artifact types it includes, the stakeholders it targets, and the purpose it
serves. Derived from the CSVLOD artifact taxonomy and the three core EA processes
described by Kotusev.
EA on a Page does not formally define viewpoints, but its artifact types and
processes imply a natural set of viewpoints that practitioners use in practice.
These viewpoints formalize those implicit conventions. |
https://meta.linked.archi/eaonapage/viewpoints# |
| Viewpoint Library (SKOS) |
EA on a Page Viewpoint Catalog |
Classification of EA on a Page viewpoints by the EA process they
primarily support: Strategic Planning, Technology Optimization, or Initiative
Delivery. |
https://meta.linked.archi/eaonapage/viewpoints#ViewpointCatalog |
| Deliverable Templates |
Architecture Strategy |
A strategic document that captures the organization's architecture
principles, policies, and high-level direction. Combines Considerations (governance
rules) with Visions (future-state descriptions) to articulate how IT investments
should be guided. Typically produced annually or when business strategy changes
significantly. |
https://meta.linked.archi/eaonapage/deliverable-templates#ArchitectureStrategy |
| Deliverable Templates |
Technology Strategy |
A document that defines the organization's technology standards,
approved technology stack, and rationalization roadmap. Combines Standards
(approved technologies) with Landscapes (current state) to identify optimization
opportunities and plan technology evolution. |
https://meta.linked.archi/eaonapage/deliverable-templates#TechnologyStrategy |
| Deliverable Templates |
Technology Reference Model |
A structured catalog of approved technologies organized by functional
area. Each technology entry includes lifecycle status (invest, maintain, contain,
retire), ownership, and usage guidelines. The primary Standards artifact. |
https://meta.linked.archi/eaonapage/deliverable-templates#TechnologyReferenceModelDocument |
| Deliverable Templates |
Solution Brief |
A concise document produced during the Initiation phase that
describes a proposed initiative at a high level — business context, proposed
approach, key assumptions, and estimated effort. Used to secure initial
approval and funding for further architecture work. |
https://meta.linked.archi/eaonapage/deliverable-templates#SolutionBrief |
| Deliverable Templates |
Solution Overview |
A document produced during the Initiation phase that describes
the proposed solution at a level sufficient for investment decisions. Includes
the solution concept, options assessment, standards compliance check, and
recommended approach. The primary Outline artifact. |
https://meta.linked.archi/eaonapage/deliverable-templates#SolutionOverviewDocument |
| Deliverable Templates |
Solution Design |
A detailed document produced during the Realization phase that
specifies the solution architecture at a level sufficient for implementation.
Includes component design, interface contracts, data models, deployment
topology, and non-functional requirements. The primary Design artifact. |
https://meta.linked.archi/eaonapage/deliverable-templates#SolutionDesignDocument |
| Deliverable Templates |
Architecture Principles Document |
A document that captures the organization's architecture principles
and policies — the Considerations artifacts. Principles are high-level governance
rules that guide all IT-related decisions. Policies are specific mandatory rules.
Typically maintained by enterprise architects and approved by the steering
committee. |
https://meta.linked.archi/eaonapage/deliverable-templates#ArchitecturePrinciplesDocument |
| Deliverable Templates |
Roadmap |
A time-sequenced plan showing the transition from current state to
target state. Combines strategic direction (Visions) with current reality
(Landscapes) to produce a phased investment plan. Typically maintained
quarterly and presented to business and IT leadership. |
https://meta.linked.archi/eaonapage/deliverable-templates#RoadmapDocument |
| Reference Data |
EA on a Page Maturity Model |
Classification of EA practice maturity into four stages based on
empirical observation across 27+ organizations. Describes what is typically
observed at each stage, not what should be achieved in a linear progression. |
https://meta.linked.archi/eaonapage/tax#MaturityScheme |
| Reference Data |
EA on a Page Governance Classification |
Classification of EA governance arrangements including architecture
tiers, governance body types, and governance activities. Based on EA Function
on a Page by Kotusev. |
https://meta.linked.archi/eaonapage/tax#GovernanceScheme |