0.11.0: arc42 and ArchiMate examples; ref in every diagram kind

Six example models next to the three C4 ones: arc42 (Cinema Tickets, IoT
Telemetry, Team Wiki) by section, ArchiMate (Insurance Claims, HR
Onboarding, Logistics Tracking) by layer, each validated with 0 errors and
0 warnings. resolveRefs and the editor schemas now take ref: in workflow
and dataflow nodes, sequence participants and lifecycle states, as the
skill already did. Example tests check each framework's folders.
This commit is contained in:
root-at-skic committed 2026-11-08 22:54:23 +02:00
1 parent f4df6a0834
commit 0745de822a
85 files changed
+2945 -67

No files matched your search

@@ -0,0 +1,76 @@
schema_version: 1
elements:
portal:
type: frontend
label: Customer Portal
sublabel: App Interface
tag: App Interface
description: >
Web and mobile front end where customers report claims and
follow their status.
claims-admin:
type: cloud
label: Claims Admin
sublabel: App Service
tag: App Service
description: >
Register, look up and update claims; used by the portal and
by claims handlers.
claims-app:
type: backend
label: Claims App
sublabel: App Component
tag: App Component
description: >
Owns claims from registration to payment; the system of
record for claims.
diagram: 0200-application/application-structure.archify
crm:
type: backend
label: CRM
sublabel: App Component
tag: App Component
description: >
Customer contacts, addresses and the customer file.
policy-admin:
type: backend
label: Policy Admin
sublabel: App Component
tag: App Component
description: >
Policies, coverage and premiums; runs on the mainframe.
doc-mgmt:
type: backend
label: Document Mgmt
sublabel: App Component
tag: App Component
description: >
Scanned letters, photos and expert reports attached to claims.
payment:
type: backend
label: Payment
sublabel: App Component
tag: App Component
description: >
Sends approved claim payments to the bank in daily batches.
claim:
type: database
label: Claim
sublabel: Data Object
tag: Data Object
description: >
One reported damage, its valuation and its payment status.
policy:
type: database
label: Policy
sublabel: Data Object
tag: Data Object
description: >
Coverage, deductible and term of an insurance contract.
customer-file:
type: database
label: Customer File
sublabel: Data Object
tag: Data Object
description: >
Everything known about a customer; contacts, policies, claims.
@@ -0,0 +1,50 @@
schema_version: 1
elements:
customer:
type: external
label: Customer
sublabel: Business Actor
tag: Business Actor
description: >
A person or small business holding one or more policies
with Halbrook Mutual.
insurant:
type: external
label: Insurant
sublabel: Business Role
tag: Business Role
description: >
The role a customer plays while a claim is open; reports
damage and receives the payment.
claims-handler:
type: external
label: Claims handler
sublabel: Business Role
tag: Business Role
description: >
Employee of the claims department who accepts, valuates
and approves claims.
handle-claim:
type: backend
label: Handle Claim
sublabel: Business Process
tag: Business Process
description: >
Register, accept, valuate and pay a claim; the core process
of the claims department.
diagram: 0100-business/handle-claim.archify
claim-registration:
type: frontend
label: Claim Registration
sublabel: Business Service
tag: Business Service
description: >
Lets an insurant report damage by phone, mail or the
customer portal.
claim-payment:
type: frontend
label: Claim Payment
sublabel: Business Service
tag: Business Service
description: >
Pays the valuated amount to the insurant or a repairer.
@@ -0,0 +1,62 @@
schema_version: 1
elements:
app-servers:
type: backend
label: App Servers
sublabel: Node
tag: Node
description: >
Two virtual machine hosts running the claims app, CRM and the
portal back end.
diagram: 0300-technology/infrastructure.archify
db-cluster:
type: database
label: DB Cluster
sublabel: Node
brand: postgresql
tag: Node
description: >
Primary and standby database servers for claims and CRM data.
doc-store:
type: database
label: Document Store
sublabel: System Software
tag: System Software
description: >
Object storage for scans and photos; written by document
management only.
mainframe:
type: backend
label: Mainframe
sublabel: Node
tag: Node
description: >
Hosts policy administration and the nightly payment batch.
mq:
type: messagebus
label: Message Queue
sublabel: System Software
tag: System Software
description: >
Queue manager between the app servers and the mainframe.
db-service:
type: cloud
label: DB Service
sublabel: Tech Service
tag: Tech Service
description: >
Managed SQL access with backups, offered to all applications.
dc-lan:
type: messagebus
label: Data Centre LAN
sublabel: Network
tag: Network
description: >
Internal network linking app servers, databases and mainframe.
dmz:
type: security
label: DMZ Gateway
sublabel: Network
tag: Network
description: >
Reverse proxy and firewall between the internet and the LAN.