arc42 and ArchiMate examples: nine models, three per framework; 1.2

The six models from extension 0.11.0 (arc42 by section, ArchiMate by
layer) next to the three C4 ones; model:scaffold --example offers them
and the tests validate each with 0 problems.
This commit is contained in:
root-at-skic committed 2026-11-08 22:57:00 +02:00
1 parent 21770c241d
commit d9777fb90e
74 files changed
+2768 -7

No files matched your search

@@ -0,0 +1,59 @@
schema_version: 1
model:
id: insurance-claims
name: Insurance Claims
description: >
ArchiMate example: how Halbrook Mutual handles claims. The business,
application and technology layers are mapped to folders, and each
element's ArchiMate type is shown as its tag.
diagram_type: architecture
meta:
title: Insurance Claims - layered view
output: main.html
components:
- ref: insurant
pos: [40, 70]
size: [170, 60]
- ref: claim-registration
pos: [270, 70]
size: [170, 60]
- ref: handle-claim
pos: [500, 70]
size: [170, 60]
- ref: portal
pos: [40, 270]
size: [170, 60]
- ref: claims-app
pos: [270, 270]
size: [170, 60]
- ref: claims-admin
pos: [500, 270]
size: [170, 60]
- ref: dmz
pos: [40, 470]
size: [170, 60]
- ref: app-servers
pos: [270, 470]
size: [170, 60]
- ref: db-cluster
pos: [500, 470]
size: [170, 60]
boundaries:
- kind: region
label: Business layer
wraps: [insurant, claim-registration, handle-claim]
- kind: region
label: Application layer
wraps: [portal, claims-app, claims-admin]
- kind: region
label: Technology layer
wraps: [dmz, app-servers, db-cluster]
connections:
- { from: claim-registration, to: insurant, label: serves, variant: emphasis }
- { from: handle-claim, to: claim-registration, label: realizes }
- { from: portal, to: insurant, label: serves }
- { from: claims-admin, to: handle-claim, label: serves }
- { from: claims-app, to: claims-admin, label: realizes }
- { from: dmz, to: portal, label: serves }
- { from: app-servers, to: claims-app, label: serves }
- { from: db-cluster, to: app-servers, label: serves }