Practice¶
Architecture practice guidance — how to use the Linked.Archi metamodels alongside other modelling approaches in real-world architecture practices.
If you are deciding which notation or framework to use, working out how to combine them without duplicating models, or aligning your practice with current analyst guidance, these articles work through the trade-offs with concrete, notation-independent examples.
Combining Notations¶
How modelling notations relate, when to use each, and how to use them together without duplication.
| Guide | Topic |
|---|---|
| C4 and ArchiMate — Reading Guide | Entry point for the trilogy below (recommended order: 1 → 2 → 3) |
| 1. Diagramming Approach Meets Modelling Language | Steel-man debate: ArchiMate makes C4 unnecessary vs C4 is essential |
| 2. C4/Structurizr and ArchiMate | Decision frameworks, integration strategy, team scenarios |
| 3. ArchiMate Application Layer vs C4 Containers | Modelling patterns and decision matrix for the overlap zone |
| C4/Structurizr vs UML | Diagram-by-diagram mapping across all 14 UML and 7 C4 types |
| Backstage as C4 Complement or Replacement | Three-way comparison (C4, Backstage, ArchiMate) with the three-model architecture |
| Deployment Modelling | ArchiMate Technology layer vs C4 deployment vs Backstage |
| ArchiMate in Structurizr DSL and Beyond | Can Structurizr DSL express ArchiMate? Evaluation of DSL options (Turtle, YAML-LD, LinkML) |
Methods & Tooling¶
How to apply architecture methods and build tooling with Linked.Archi.
| Guide | Topic |
|---|---|
| EA Frameworks Compared | How Zachman, TOGAF, EA on a Page, ADMIT, BTABoK, and BizBOK relate and complement each other |
| Zachman vs EA on a Page | Deep comparison of two artifact classification frameworks — theoretical completeness meets empirical validation |
| Classifying Business and Application Architecture with CSVLOD | Where capability maps, decomposition, realization, and solution artifacts fit in the six CSVLOD types — notation-independent, with ArchiMate as the worked example |
| ATAM Evaluation in Practice | Complete ATAM walkthrough using all Linked.Archi modules — governance, decisions, patterns, quality attributes, and risk analysis |
| ADD Design in Practice | Three ADD iterations designing a payment platform — from reference architecture selection through data resilience to security |
| Build Your Own Metamodel | Extend ArchiMate 4.0 to build a custom content framework — from elements through SHACL to document generation |
| Build Your Own Modelling Tool | From finished metamodel to working tool — palette, canvas, SHACL validation, viewpoint filtering, document generation, and AI agent access |
| Cloud Platform Walkthrough | Complete worked example — design rationale for every file in the Cloud Platform custom metamodel |
| Knowledge on Another Level — OKF and Linked.Archi | How Google's Open Knowledge Format compares to the Linked.Archi graph — worked example, DIKW placement, and how the two compose |
| How Linked.Archi Bridges the Gap | How the knowledge graph solves the last-mile adoption problem — model once, view everywhere |
Domain Extensions¶
Practice guides for specific architecture domains built as Linked.Archi extensions.
| Guide | Topic |
|---|---|
| AI Ethics & Governance | EU AI Act compliance — risk classification, conformity assessment, bias assessment, human oversight |
| Financial Architecture | TCO, investment cases, cost-benefit analysis, FinOps — cost as a queryable dimension |
| EA-as-a-Service | Service catalogue, engagements, satisfaction tracking, capability portfolios, maturity assessment |
| ML-Enabled Systems | ML model architecture — stakeholders, viewpoints, integration boundaries, quality attributes |
| Gartner 2025 Extensions | Cross-extension composition and queries across AI governance, financial architecture, and EA-as-a-Service |
Industry Alignment¶
How Linked.Archi addresses current industry trends and analyst guidance.
| Guide | Topic |
|---|---|
| Architectural Data vs Architectural Knowledge | The fundamental distinction between recording what exists and understanding why — and what it takes to cross the gap |
| Architecture Knowledge Lifecycle | How architectural knowledge is created, captured, validated, shared, applied, evolved, and retired |
| Gartner 2025 — EA Diagnosis | How Linked.Archi addresses Gartner's five EA mistakes and three strategic trends |
| Enterprise Ontologies Are Mandatory | Why Gartner, Forrester, and industry leaders now consider enterprise ontologies mandatory for AI transformation |