Linked.Archi Core Deliverable Templates
Framework-agnostic deliverable templates that define the content structure of common architecture documents. Each template specifies which viewpoints are required — the actual views are created when someone instantiates the template into a concrete deliverable (arch:Model). These templates reference core viewpoints. Framework-specific templates (e.g., TOGAF Architecture Definition Document) should be defined in the respective framework's file, referencing framework-specific viewpoints.
Linked.Archi
Markdown Document
Renders the deliverable as a Markdown document with headings per section, embedded diagrams as images, and tables for catalogs and matrices. Suitable for Git-based documentation workflows (MkDocs, Docusaurus, Jekyll).
handlebars render --template deliverable.md.hbs
HTML Report
Renders the deliverable as a standalone HTML page with interactive navigation, collapsible sections, and embedded SVG diagrams. Suitable for intranet publishing and stakeholder portals.
python generate.py --format html --template deliverable.html.j2
PDF Document
Renders the deliverable as a paginated PDF with formal layout, headers/footers, table of contents, and print-ready diagrams. Suitable for governance submissions, audits, and formal sign-off.
python generate.py --format pdf --template deliverable.tex
Slide Deck
Renders the deliverable as a presentation slide deck with one section per slide or slide group. Diagrams are simplified for projection. Suitable for architecture review boards and stakeholder briefings.
python generate.py --format pptx --template deliverable.pptx
Interactive Dashboard
Renders the deliverable as an interactive web dashboard with filterable views, drill-down navigation, and live data from the knowledge graph. Suitable for continuous architecture monitoring and portfolio management.
python generate.py --format dashboard --template dashboard.d3.js
1. Architecture Landscape
High-level overview of the architecture showing major components and domains.
2. Stakeholder Analysis
Map stakeholders to their concerns and the viewpoints that address them.
3. Component Inventory
Catalog of all architecture components with key attributes.
4. Dependency Analysis
Matrix showing dependencies between components for impact analysis.
5. Standards Compliance
Assessment of component compliance with applicable standards.
1. Solution Context
Overview of the solution within the broader architecture landscape.
2. Process Design
Process flows showing activities, decision points, and handoffs.
3. Interface Design
Interface map showing component connections, protocols, and data flows.
4. Deployment Design
Deployment map showing where components run and hosting relationships.
5. Architecture Decisions
Log of architecture decisions with context, rationale, and status.
1. Impact Analysis
Propagation of change through dependencies — what breaks if this changes.
2. Dependency Assessment
Full dependency matrix for the affected components.
3. Gap Analysis
Differences between current and target state after the change.
4. Migration Roadmap
Planned evolution steps to implement the change.
Architecture Overview Document
A high-level architecture document providing stakeholders with an overview of the architecture landscape, component inventory, dependencies, and standards compliance. Suitable for governance reviews and onboarding.
Solution Design Document
A solution-level architecture document covering process design, interface design, deployment topology, and architecture decisions. Used by solution architects and development teams during design and implementation.
Change Impact Assessment
An assessment document for evaluating the impact of a proposed architecture change. Covers impact propagation, dependency analysis, gap analysis, and migration planning. Used for change governance and decision-making.