Linked.Archi EA on a Page Deliverable Templates
type: Ontology
imports: core#
license: http://creativecommons.org/licenses/by/4.0/
preferred namespace prefix: eaopdt
creator: Kalin Maldzhanski
description: Deliverable templates for the EA on a Page framework. Each template defines the structure and required viewpoints for a common EA deliverable. Based on the artifact types and typical structures described by Kotusev. EA on a Page explicitly says templates should be adapted rather than copied. These templates capture the typical structure observed across organizations and should be customized to local context.
created: 2026-05-03
modified: 2026-05-03
publisher: Linked.Archi
publisher: linked.archi
status: draft
version IRI: 0.1.0#
version info: 0.1.0
was derived from: EA on a Page (Svyatoslav Kotusev, 2017)

Architecture Strategy
type: DeliverableTemplate
definition: 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.
template requires viewpoint: BusinessCapabilityVP
template requires viewpoint: RoadmapVP
template targets purpose: Deciding
template targets purpose: Informing
template has section: 1. Architecture Principles & Policies
template has section: 2. Business Capability Assessment
template has section: 3. Target State Architecture
template has section: 4. Strategic Roadmap

1. Architecture Principles & Policies
type: TemplateSection
section order: 1
definition: Governing rules and constraints for IT-related decisions.
section viewpoint: BusinessCapabilityVP

2. Business Capability Assessment
type: TemplateSection
section order: 2
definition: Current business capabilities and their IT support maturity.
section viewpoint: BusinessCapabilityVP

3. Target State Architecture
type: TemplateSection
section order: 3
definition: Desired future state of the IT landscape aligned with business strategy.
section viewpoint: RoadmapVP

4. Strategic Roadmap
type: TemplateSection
section order: 4
definition: Sequenced transition plan from current state to target state.
section viewpoint: RoadmapVP

Technology Strategy
type: DeliverableTemplate
definition: 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.
template requires viewpoint: StandardsComplianceVP
template requires viewpoint: LandscapeVP
template targets purpose: Governing
template targets purpose: Deciding
template has section: 1. Technology Reference Model
template has section: 2. Current Technology Landscape
template has section: 3. Compliance Assessment
template has section: 4. Rationalization Roadmap

1. Technology Reference Model
type: TemplateSection
section order: 1
definition: Approved technologies organized by functional area with lifecycle status.
section viewpoint: StandardsComplianceVP

2. Current Technology Landscape
type: TemplateSection
section order: 2
definition: Inventory and assessment of the current technology estate.
section viewpoint: LandscapeVP

3. Compliance Assessment
type: TemplateSection
section order: 3
definition: Gap analysis between current landscape and approved standards.
section viewpoint: StandardsComplianceVP

4. Rationalization Roadmap
type: TemplateSection
section order: 4
definition: Sequenced plan for technology consolidation and modernization.
section viewpoint: LandscapeVP

Technology Reference Model
type: DeliverableTemplate
definition: 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.
template requires viewpoint: StandardsComplianceVP
template targets purpose: Governing
template has section: 1. Technology Categories
template has section: 2. Lifecycle Status
template has section: 3. Migration Guidance

1. Technology Categories
type: TemplateSection
section order: 1
definition: Functional areas and their approved technology options.
section viewpoint: StandardsComplianceVP

2. Lifecycle Status
type: TemplateSection
section order: 2
definition: Current lifecycle status of each technology (invest, maintain, contain, retire).
section viewpoint: StandardsComplianceVP

3. Migration Guidance
type: TemplateSection
section order: 3
definition: Guidance for transitioning from deprecated to approved technologies.
section viewpoint: StandardsComplianceVP

Solution Brief
type: DeliverableTemplate
definition: 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.
template requires viewpoint: OptionsAssessmentVP
template targets purpose: Deciding
template has section: 1. Business Context & Drivers
template has section: 2. Proposed Approach
template has section: 3. Estimates & Assumptions

1. Business Context & Drivers
type: TemplateSection
section order: 1
definition: Business need, strategic alignment, and key stakeholders.

2. Proposed Approach
type: TemplateSection
section order: 2
definition: High-level solution concept and key architectural decisions.
section viewpoint: OptionsAssessmentVP

3. Estimates & Assumptions
type: TemplateSection
section order: 3
definition: Effort estimates, key assumptions, risks, and dependencies.

Solution Overview
type: DeliverableTemplate
definition: 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.
template requires viewpoint: OptionsAssessmentVP
template requires viewpoint: StandardsComplianceVP
template targets purpose: Deciding
template has section: 1. Business Context
template has section: 2. Solution Options
template has section: 3. Standards Compliance
template has section: 4. Recommended Approach
template has section: 5. Implementation Roadmap

1. Business Context
type: TemplateSection
section order: 1
definition: Business need, strategic alignment, scope, and stakeholders.

2. Solution Options
type: TemplateSection
section order: 2
definition: Alternative approaches with pros, cons, costs, and risks.
section viewpoint: OptionsAssessmentVP

3. Standards Compliance
type: TemplateSection
section order: 3
definition: Assessment of each option against approved standards and principles.
section viewpoint: StandardsComplianceVP

4. Recommended Approach
type: TemplateSection
section order: 4
definition: Selected option with rationale, trade-offs, and conditions.
section viewpoint: OptionsAssessmentVP

5. Implementation Roadmap
type: TemplateSection
section order: 5
definition: High-level delivery plan, milestones, and dependencies.

Solution Design
type: DeliverableTemplate
definition: 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.
template requires viewpoint: SolutionDesignVP
template requires viewpoint: StandardsComplianceVP
template targets purpose: Designing
template has section: 1. Solution Context
template has section: 2. Component Architecture
template has section: 3. Interface Contracts
template has section: 4. Data Architecture
template has section: 5. Deployment Architecture
template has section: 6. Standards Compliance & Exemptions

1. Solution Context
type: TemplateSection
section order: 1
definition: Business context, scope, constraints, and reference to the approved Solution Overview.

2. Component Architecture
type: TemplateSection
section order: 2
definition: Solution components, their responsibilities, and interactions.
section viewpoint: SolutionDesignVP

3. Interface Contracts
type: TemplateSection
section order: 3
definition: APIs, message formats, protocols, and integration patterns.
section viewpoint: SolutionDesignVP

4. Data Architecture
type: TemplateSection
section order: 4
definition: Data models, data flows, storage, and data governance.
section viewpoint: SolutionDesignVP

5. Deployment Architecture
type: TemplateSection
section order: 5
definition: Infrastructure topology, environments, scaling, and resilience.
section viewpoint: SolutionDesignVP

6. Standards Compliance & Exemptions
type: TemplateSection
section order: 6
definition: Compliance with approved standards, any exemptions requested, and remediation plans.
section viewpoint: StandardsComplianceVP

Architecture Principles Document
type: DeliverableTemplate
definition: 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.
template requires viewpoint: BusinessCapabilityVP
template targets purpose: Governing
template has section: 1. Architecture Principles
template has section: 2. Architecture Policies
template has section: 3. Governance & Compliance

1. Architecture Principles
type: TemplateSection
section order: 1
definition: High-level principles with rationale, implications, and examples.

2. Architecture Policies
type: TemplateSection
section order: 2
definition: Mandatory rules with scope, enforcement mechanism, and exceptions process.

3. Governance & Compliance
type: TemplateSection
section order: 3
definition: How principles and policies are governed, reviewed, and enforced.
section viewpoint: GovernanceOverviewVP

Roadmap
type: DeliverableTemplate
definition: 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.
template requires viewpoint: RoadmapVP
template requires viewpoint: LandscapeVP
template targets purpose: Deciding
template targets purpose: Informing
template has section: 1. Current State Summary
template has section: 2. Target State
template has section: 3. Transition Phases
template has section: 4. Investment Priorities

1. Current State Summary
type: TemplateSection
section order: 1
definition: Key aspects of the current IT landscape relevant to the roadmap scope.
section viewpoint: LandscapeVP

2. Target State
type: TemplateSection
section order: 2
definition: Desired future state aligned with business strategy.
section viewpoint: RoadmapVP

3. Transition Phases
type: TemplateSection
section order: 3
definition: Sequenced phases with initiatives, dependencies, and milestones.
section viewpoint: RoadmapVP

4. Investment Priorities
type: TemplateSection
section order: 4
definition: Prioritized initiatives with estimated costs, benefits, and risks.