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:
1 parent
21770c241d
commit
d9777fb90e
74 files changed
+2768
-7
No files matched your search
@@ -0,0 +1,31 @@
|
||||
schema_version: 1
|
||||
diagram_type: architecture
|
||||
meta:
|
||||
title: Business layer
|
||||
output: business-layer.html
|
||||
components:
|
||||
- ref: customer
|
||||
pos: [40, 160]
|
||||
size: [130, 60]
|
||||
- ref: insurant
|
||||
pos: [250, 160]
|
||||
size: [130, 60]
|
||||
- ref: claim-registration
|
||||
pos: [460, 60]
|
||||
size: [150, 60]
|
||||
- ref: claim-payment
|
||||
pos: [460, 260]
|
||||
size: [150, 60]
|
||||
- ref: handle-claim
|
||||
pos: [690, 160]
|
||||
size: [150, 60]
|
||||
- ref: claims-handler
|
||||
pos: [920, 160]
|
||||
size: [130, 60]
|
||||
connections:
|
||||
- { from: customer, to: insurant, label: assigned to }
|
||||
- { from: claim-registration, to: insurant, label: serves, variant: emphasis }
|
||||
- { from: claim-payment, to: insurant, label: serves }
|
||||
- { from: handle-claim, to: claim-registration, label: realizes }
|
||||
- { from: handle-claim, to: claim-payment, label: realizes }
|
||||
- { from: claims-handler, to: handle-claim, label: assigned to }
|
||||
@@ -0,0 +1,29 @@
|
||||
schema_version: 2
|
||||
diagram_type: workflow
|
||||
meta:
|
||||
title: Handle Claim
|
||||
output: handle-claim.html
|
||||
viewBox: [840, 534]
|
||||
lanes:
|
||||
- { id: insurant-lane, label: Insurant }
|
||||
- { id: handler-lane, label: Claims handler }
|
||||
- { id: systems-lane, label: Applications }
|
||||
mainPath: [damage, register, accept, valuate, pay]
|
||||
nodes:
|
||||
- { id: damage, lane: insurant-lane, col: 0, type: external, label: Damage occurs, tag: Business Event }
|
||||
- { ref: insurant, lane: insurant-lane, col: 5 }
|
||||
- { id: register, lane: handler-lane, col: 1, type: backend, label: Register, tag: Business Process }
|
||||
- { id: accept, lane: handler-lane, col: 2, type: security, label: Accept, sublabel: check coverage, tag: Business Process }
|
||||
- { id: valuate, lane: handler-lane, col: 3, type: backend, label: Valuate, tag: Business Process }
|
||||
- { id: pay, lane: handler-lane, col: 4, type: backend, label: Pay, tag: Business Process }
|
||||
- { ref: claims-app, lane: systems-lane, col: 2 }
|
||||
- { ref: payment, lane: systems-lane, col: 4 }
|
||||
edges:
|
||||
- { from: damage, to: register, label: report }
|
||||
- { from: register, to: accept }
|
||||
- { from: accept, to: valuate, label: covered }
|
||||
- { from: valuate, to: pay, label: approved }
|
||||
- { from: pay, to: insurant, label: paid }
|
||||
- { from: accept, to: insurant, label: rejected, role: branch, variant: dashed }
|
||||
- { from: claims-app, to: accept, label: serves, role: async }
|
||||
- { from: payment, to: pay, label: serves, role: async }
|
||||
@@ -0,0 +1,32 @@
|
||||
schema_version: 1
|
||||
diagram_type: architecture
|
||||
meta:
|
||||
title: Application cooperation
|
||||
output: application-cooperation.html
|
||||
components:
|
||||
- ref: portal
|
||||
pos: [40, 260]
|
||||
size: [130, 60]
|
||||
- ref: claims-app
|
||||
pos: [250, 260]
|
||||
size: [130, 60]
|
||||
- ref: crm
|
||||
pos: [250, 60]
|
||||
size: [130, 60]
|
||||
- ref: policy-admin
|
||||
pos: [460, 160]
|
||||
size: [130, 60]
|
||||
decisions: [policies-stay-on-mainframe]
|
||||
- ref: doc-mgmt
|
||||
pos: [460, 360]
|
||||
size: [130, 60]
|
||||
decisions: [documents-in-object-storage]
|
||||
- ref: payment
|
||||
pos: [250, 460]
|
||||
size: [130, 60]
|
||||
connections:
|
||||
- { from: portal, to: claims-app, label: claims, variant: emphasis }
|
||||
- { from: crm, to: claims-app, label: customer, labelAt: [315, 134] }
|
||||
- { from: policy-admin, to: claims-app, label: coverage, decisions: [policies-stay-on-mainframe] }
|
||||
- { from: claims-app, to: doc-mgmt, label: documents }
|
||||
- { from: claims-app, to: payment, label: payments, labelAt: [315, 334] }
|
||||
@@ -0,0 +1,36 @@
|
||||
schema_version: 1
|
||||
diagram_type: architecture
|
||||
meta:
|
||||
title: Application structure
|
||||
output: application-structure.html
|
||||
components:
|
||||
- ref: portal
|
||||
pos: [40, 160]
|
||||
size: [130, 60]
|
||||
- ref: claims-admin
|
||||
pos: [250, 160]
|
||||
size: [130, 60]
|
||||
- ref: claims-app
|
||||
pos: [460, 160]
|
||||
size: [130, 60]
|
||||
- ref: claim
|
||||
pos: [460, 360]
|
||||
size: [130, 60]
|
||||
- ref: crm
|
||||
pos: [670, 60]
|
||||
size: [130, 60]
|
||||
- ref: customer-file
|
||||
pos: [880, 60]
|
||||
size: [130, 60]
|
||||
- ref: policy-admin
|
||||
pos: [670, 260]
|
||||
size: [130, 60]
|
||||
- ref: policy
|
||||
pos: [880, 260]
|
||||
size: [130, 60]
|
||||
connections:
|
||||
- { from: claims-admin, to: portal, label: serves, variant: emphasis }
|
||||
- { from: claims-app, to: claims-admin, label: realizes }
|
||||
- { from: claims-app, to: claim, label: accesses, labelAt: [525, 234] }
|
||||
- { from: crm, to: customer-file, label: accesses }
|
||||
- { from: policy-admin, to: policy, label: accesses }
|
||||
@@ -0,0 +1,45 @@
|
||||
schema_version: 1
|
||||
diagram_type: architecture
|
||||
meta:
|
||||
title: Technology layer
|
||||
output: infrastructure.html
|
||||
components:
|
||||
- ref: dmz
|
||||
pos: [40, 160]
|
||||
size: [130, 60]
|
||||
- ref: doc-store
|
||||
pos: [250, 60]
|
||||
size: [130, 60]
|
||||
decisions: [documents-in-object-storage]
|
||||
- ref: app-servers
|
||||
pos: [250, 160]
|
||||
size: [130, 60]
|
||||
- ref: db-service
|
||||
pos: [250, 260]
|
||||
size: [130, 60]
|
||||
- ref: db-cluster
|
||||
pos: [250, 360]
|
||||
size: [130, 60]
|
||||
- ref: mq
|
||||
pos: [460, 160]
|
||||
size: [130, 60]
|
||||
- ref: mainframe
|
||||
pos: [670, 160]
|
||||
size: [130, 60]
|
||||
decisions: [policies-stay-on-mainframe]
|
||||
- ref: dc-lan
|
||||
pos: [670, 360]
|
||||
size: [130, 60]
|
||||
boundaries:
|
||||
- kind: region
|
||||
label: Data centre
|
||||
wraps: [doc-store, app-servers, db-service, db-cluster, mq, mainframe, dc-lan]
|
||||
connections:
|
||||
- { from: dmz, to: app-servers, label: HTTPS, variant: security }
|
||||
- { from: app-servers, to: doc-store, label: S3 API }
|
||||
- { from: db-service, to: app-servers, label: serves }
|
||||
- { from: db-cluster, to: db-service, label: realizes }
|
||||
- { from: app-servers, to: mq, label: MQ }
|
||||
- { from: mq, to: mainframe, label: bridge }
|
||||
- { from: db-cluster, to: dc-lan, label: LAN }
|
||||
- { from: mainframe, to: dc-lan, label: LAN, labelAt: [735, 234] }
|
||||
+20
@@ -0,0 +1,20 @@
|
||||
schema_version: 1
|
||||
decision:
|
||||
id: policies-stay-on-mainframe
|
||||
title: Policies stay on the mainframe
|
||||
status: accepted
|
||||
date: 2026-09-08
|
||||
elements: [policy-admin, mainframe, mq, claims-app]
|
||||
diagrams: [0200-application/application-cooperation.archify, 0300-technology/infrastructure.archify]
|
||||
context: >
|
||||
The new claims application needs coverage data for every
|
||||
claim. Policy administration has run on the mainframe for
|
||||
twenty years and a migration was estimated at three years.
|
||||
decision: >
|
||||
Policy administration stays on the mainframe. The claims
|
||||
application reads coverage through the message queue bridge
|
||||
and never copies policies into its own database.
|
||||
consequences: >
|
||||
Accepting a claim depends on the mainframe being up during
|
||||
office hours. The queue bridge must be kept and tested.
|
||||
A later migration needs its own decision.
|
||||
+20
@@ -0,0 +1,20 @@
|
||||
schema_version: 1
|
||||
decision:
|
||||
id: documents-in-object-storage
|
||||
title: Claim documents in object storage
|
||||
status: accepted
|
||||
date: 2026-10-14
|
||||
elements: [doc-mgmt, doc-store, claims-app]
|
||||
diagrams: [0200-application/application-cooperation.archify, 0300-technology/infrastructure.archify]
|
||||
context: >
|
||||
Photos and expert reports were stored as blobs in the claims
|
||||
database. The database grew by forty gigabytes a month and
|
||||
backups no longer fitted the nightly window.
|
||||
decision: >
|
||||
Document management stores every file in the document store
|
||||
and keeps only a reference in the claim. The claims
|
||||
application never writes files itself.
|
||||
consequences: >
|
||||
Database backups shrink and stay fast. Documents get their own
|
||||
retention rules. A claim and its files are restored from two
|
||||
places after an incident.
|
||||
@@ -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 }
|
||||
@@ -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.
|
||||
Reference in new issue
Block a user