OWL ontology for the EA on a Page framework — six CSVLOD artifact type classes with inter-type relationships, classification properties, processes, process phases, governance model, participants, and maturity stages.
Ontology for the Enterprise Architecture on a Page framework by Svyatoslav Kotusev. Defines the six CSVLOD artifact types as OWL classes (Consideration, Standard, Vision, Landscape, Outline, Design) with inter-type relationship properties describing how artifact types influence each other within an EA practice. Also defines EA processes (Strategic Planning, Initiative Delivery, Technology Optimization), process phases, governance activities, participants, governance bodies and tiers, and maturity stages. Finer-grained classification of the 24 specific artifact types is handled via eaop:classifiedByType pointing to SKOS concepts in the companion taxonomy (eaonapage-tax.ttl). 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.
Linked.Archi
Linked.Archi EA on a Page Ontology
Whether an artifact is primarily business-focused or IT-focused. Values are SKOS concepts from the EA on a Page taxonomy.
ex:MyArtifact eaop:artifactFocus eaoptax:ITFocused .
artifact focus
The temporal lifecycle of an artifact: permanent, long-lived, or short-lived. Values are SKOS concepts from the EA on a Page taxonomy.
ex:MyArtifact eaop:artifactLifecycle eaoptax:Permanent .
artifact lifecycle
The nature of what an artifact describes: rules, structures, or changes. Based on Kotusev's three-way classification. Values are SKOS concepts from the EA on a Page taxonomy.
ex:MyArtifact eaop:artifactNature eaoptax:Rules .
artifact nature
The organizational scope of an artifact: organization-wide, initiative-scoped, or project-scoped. Values are SKOS concepts from the EA on a Page taxonomy.
ex:MyArtifact eaop:artifactScope eaoptax:OrganizationWide .
artifact scope
Links an architecture work product to its specific artifact type in the CSVLOD taxonomy. The target is a skos:Concept from the EA on a Page taxonomy (eaonapage-tax.ttl) — one of the 24 specific artifact types. Same design pattern as zach:classifiedByCell.
classified by type
Usage pattern: ex:TechRefModel a eaop:Standard ; skos:prefLabel "Enterprise Technology Reference Model"@en ; eaop:classifiedByType eaoptax:Technology_Reference_Models . ex:ITRoadmap a eaop:Vision ; skos:prefLabel "IT Roadmap 2026–2028"@en ; eaop:classifiedByType eaoptax:Roadmaps .
Links a governance body to the higher-tier body it escalates decisions to.
escalates to
Standards eventually shape Landscapes — by guiding individual project decisions, Standards determine the structure of the IT landscape that results from those projects.
eventually shape
Links an architecture work product to the governance body responsible for its review and approval.
governed by
Links a governance body to the architecture tier it operates at.
governs tier
Visions guide the evolution of Landscapes.
guide evolution
Visions guide the selection of Standards.
guide selection
Visions guide the structure of Designs.
guide structure
Links a maturity stage to the governance arrangement typically observed at that stage.
has governance arrangement
Links an EA process to one of its constituent phases or sub-activities.
has phase
Considerations influence the creation of Visions.
influence creation
Considerations influence the structure of Designs.
influence design structure
Considerations influence the evolution of Landscapes.
influence evolution
Considerations influence the structure of Outlines.
influence outline structure
Considerations influence the selection of Standards.
influence selection
Considerations influence the structure of Outlines and Designs.
influence structure
Visions initiate the creation of new Outlines for specific IT projects required to achieve the desired future.
initiate new
Links a maturity stage to the EA processes typically established at that stage.
maturity stage process
Links an EA process to a participant role.
process participant
Outlines provide the initial basis for developing more detailed Designs.
provide basis
Landscapes provide the environment for all new IT systems described in Outlines and Designs.
provide environment
Landscapes provide the environment for Designs.
provide environment for design
Landscapes provide the environment for Outlines.
provide environment for outline
Standards provide implementation-specific guidelines for developing Outlines and Designs.
provide guidelines
Standards provide guidelines for developing Designs.
provide guidelines for design
Standards provide guidelines for developing Outlines.
provide guidelines for outline
How commonly the artifact type is used across organizations: essential, common, or uncommon. A type-level classification property. Values are SKOS concepts from the EA on a Page taxonomy.
eaoptax:Principles eaop:usageFrequency eaoptax:Essential .
usage frequency
Links an architecture work product to the EA process it is used in.
used in process
A benefit typically realized at a given maturity stage, based on empirical observation across organizations.
maturity benefit
A challenge typically faced at a given maturity stage, based on empirical observation across organizations.
maturity challenge
The numeric level of an architecture tier in the governance hierarchy: 1 (enterprise), 2 (domain/segment), 3 (solution/project).
tier level
A governance activity where an approved architecture artifact is modified to reflect changed requirements or new constraints.
Amendment
A governance decision to approve an architecture artifact or initiative to proceed.
Approval
A governance activity where architecture artifacts are reviewed against standards, principles, and strategic direction.
Architecture Review
A level in the architecture governance hierarchy. EA on a Page describes one-tier, two-tier, and three-tier governance models depending on organizational size and complexity. Each tier has its own governance bodies, governed artifact types, and decision authority.
Architecture Tier
One-tier: single EA team handles all artifacts. Two-tier: enterprise architects handle strategic artifacts, solution architects handle project artifacts. Three-tier: adds a domain/segment architecture layer between enterprise and solution.
A specific artifact type from the CSVLOD taxonomy — classification slot for architecture work products within an EA practice. Instances are the 24 specific artifact types defined in the taxonomy (e.g., Principles, Technology Reference Models, Business Capability Models, Landscape Diagrams, Solution Overviews, Solution Designs). Same role as zach:ZachmanCell.
Artifact Type
Abstract high-level guidelines or imperatives defining an entire organization. Considerations are overarching conceptual rules important for business executives while also having significant technology-related ramifications. They represent planning decisions established collaboratively by business executives and architects. Due to their implicit duality, Considerations convey one value-related meaning to business executives but another infrastructure-related meaning to architects. Considerations are permanent, very long-lived, established once and then periodically updated. After being agreed upon, they provide a common basis for all further discussions and influence all other artifact types.
Architecture principles defining process standardization and data centralization policies, business continuity requirements.
Consideration
Detailed technical descriptions of separate IT systems actionable for their implementers. Designs provide IT specialists with precise technology- specific information required to deliver the project but are largely irrelevant to business executives. They represent technical planning decisions developed collectively by architects and IT project teams based on corresponding Outlines. Due to their duality, Designs convey one meaning to architects (standards compliance, strategic alignment) and another to project teams (implementation plan). Designs are temporary and limited in their active lifespan to the duration of respective projects.
Solution designs describing in detail application, data, technology and security layers of the IT system.
Design
A stakeholder who participates in EA practice processes.
EA Practice Participant
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.
EA Process
A phase or sub-activity within one of the three core EA processes. Phases represent the lifecycle stages that initiatives pass through within each process.
EA Process Phase
A governance activity where a decision or conflict is escalated to a higher-tier governance body for resolution.
Escalation
A governance decision to grant a temporary deviation from established standards or principles for a specific initiative.
Exemption
An activity within EA governance processes, including architecture reviews, approvals, amendments, exemptions, and escalations.
Governance Activity
A configuration of governance bodies, tiers, decision rights, escalation paths, and governed artifact categories that defines how architecture governance operates in an organization. Different maturity stages and organizational sizes lead to different governance arrangements.
Governance Arrangement
An organizational body that governs architecture decisions and artifacts. Governance bodies review, approve, or reject architecture artifacts and decisions at various levels of the organization. Examples include architecture review boards, steering committees, and technology councils.
Governance Body
EA Function on a Page describes governance bodies at different tiers, each responsible for different artifact types and decision scopes.
Formal models or diagrams describing the IT landscape from the technology perspective at various scopes and levels of granularity. Landscapes are important for architects but virtually useless to business executives. They represent documented facts and may be developed and maintained by individual architects alone. Unlike Visions which focus on the future, Landscapes aim to capture the current as-is state. They provide a baseline or inventory of the existing IT infrastructure. Landscapes are permanent, long-lived, and evolve reactively together with the organization — updated after changes in the landscape occur.
Landscape diagrams depicting main applications, systems, databases and connections between them.
Landscape
A stage in the maturity of an EA practice, characterized by the processes established, artifacts mastered, governance arrangements in place, and benefits realized. EA on a Page defines four stages from Stage Zero (no architecture) to Stage Three (true enterprise architecture).
EA Maturity Stage
The maturity model is descriptive, not prescriptive or predictive. It describes what is typically observed at each stage, not what should be achieved in a linear progression.
High-level descriptions of separate IT projects understandable to business executives. Outlines provide decision-makers with relevant summary information about a proposed new IT system but do not contain sufficient technical details to actually implement it. They represent planning decisions created collaboratively by architects and business executives based on basic requirements. Outlines are often initiated from Visions and are consistent with Considerations. Due to their explicit duality, Outlines convey one meaning to business executives (value, timelines, costs) and another to architects (what needs to be delivered). Outlines are temporary and short-lived — created at early stages of projects to support decision-making, then discarded after projects are initiated or rejected.
Solution overviews describing the essence of the proposed IT solution, its overall impact, estimated cost, time and risks.
Outline
Highly specialized low-level technical guidelines prescribing how the IT landscape should be organized and built. Standards are critically important for architects but largely irrelevant to business executives. They represent technical planning decisions established collectively by architects based on their understanding of the best interests of business executives. Unlike dual Considerations, Standards are virtually invisible to business executives since they reflect technology-specific rules. Standards are permanent and relatively stable, updated periodically with new technologies or better approaches. After being established, Standards influence the designs of all individual IT systems and the overall structure of the IT landscape.
Technology standards prescribing application platforms, database management systems, proven integration patterns.
Standard
Abstract, often one-page diagrams providing high-level views of an entire organization, typically describing the strategic development plan 3-5 years ahead. The long-term strategy reflected in Visions is critical for business executives while also having direct implications for the IT landscape. Visions represent planning decisions developed collaboratively by business executives and architects. Due to their implicit duality, Visions convey one meaning to business executives (strategic priorities) and another to architects (IT investment direction). Visions are permanent but evolving, continuously updated according to the latest strategic changes. After being developed, they provide a basis for directing future investments and prioritizing proposed projects.
Business capability maps showing which capabilities should be uplifted, target state architectures, strategic roadmaps.
Vision
The Practice of Enterprise Architecture: A Modern Approach to Business and IT Alignment
Enterprise Architects: The Agents of Digital Transformation
Participates in Strategic Planning. Provides business strategy input, approves Visions and investment priorities.
Business Leader
Participates in all three EA processes. Develops and maintains Considerations, Visions, Standards, and Landscapes. Reviews Outlines and Designs.
Enterprise Architect
Participates in Strategic Planning and Technology Optimization. Approves Standards, prioritizes technology investments, and governs the IT landscape.
IT Leader
The phase of Initiative Delivery where a new initiative is assessed, an Outline is developed, options are evaluated, and an architectural approach is selected. Produces Solution Overviews and Options Assessments.
Initiation
Involves solution architects working with business stakeholders to understand requirements and propose architectural approaches.
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.
Initiative Delivery
Key questions: What is the best approach for this initiative? What are the options and trade-offs? How should the solution be designed?
The phase of Initiative Delivery where the selected approach is elaborated into detailed Designs and handed over to delivery teams for implementation. Produces Solution Designs and Detailed Specifications.
Realization
Involves solution architects working with delivery teams to translate outlines into implementable specifications.
Primarily participates in Initiative Delivery. Develops Outlines and Designs for specific initiatives, guided by Considerations and Standards.
Solution Architect
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.
Strategic Planning
Key questions: What are our strategic priorities? Where should we invest? What does the target state look like? What principles guide our decisions?
The ongoing cycle of strategic planning where business strategy is translated into IT investment direction. Produces and maintains Considerations and Visions.
Strategic Planning Cycle
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.
Technology Optimization
Key questions: What technologies do we have? Which are redundant or end-of-life? What should be our standard technology stack?