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,34 @@
schema_version: 1
diagram_type: architecture
meta:
title: Business actors and services
output: business-services.html
components:
- ref: shipper
pos: [40, 60]
size: [130, 60]
- ref: recipient
pos: [40, 260]
size: [130, 60]
- ref: delivery-service
pos: [250, 60]
size: [130, 60]
- ref: tracking-service
pos: [250, 260]
size: [130, 60]
- ref: deliver-shipment
pos: [460, 160]
size: [130, 60]
- ref: driver
pos: [670, 60]
size: [130, 60]
- ref: customer-service
pos: [670, 260]
size: [130, 60]
connections:
- { from: delivery-service, to: shipper, label: serves, variant: emphasis }
- { from: tracking-service, to: recipient, label: serves }
- { from: deliver-shipment, to: delivery-service, label: realizes }
- { from: deliver-shipment, to: tracking-service, label: realizes }
- { from: driver, to: deliver-shipment, label: assigned to }
- { from: customer-service, to: tracking-service, label: assigned to }
@@ -0,0 +1,25 @@
schema_version: 2
diagram_type: workflow
meta:
title: Deliver Shipment
output: deliver-shipment.html
viewBox: [840, 534]
lanes:
- { id: customer-lane, label: Shipper and recipient }
- { id: driver-lane, label: Driver }
- { id: hub-lane, label: Hub }
mainPath: [book, pick-up, sort, line-haul, last-mile, pod-step]
nodes:
- { id: book, lane: customer-lane, col: 0, type: external, label: Book shipment, tag: Business Event }
- { id: pick-up, lane: driver-lane, col: 1, type: backend, label: Pick up, tag: Business Process }
- { id: sort, lane: hub-lane, col: 2, type: backend, label: Sort at hub, tag: Business Process }
- { id: line-haul, lane: hub-lane, col: 3, type: backend, label: Line haul, tag: Business Process }
- { id: last-mile, lane: driver-lane, col: 4, type: backend, label: Last mile, tag: Business Process }
- { id: pod-step, lane: customer-lane, col: 5, type: security, label: Delivered, sublabel: proof of delivery, tag: Business Process }
edges:
- { from: book, to: pick-up, label: triggers }
- { from: pick-up, to: sort, label: parcel }
- { from: sort, to: line-haul, label: trailer }
- { from: line-haul, to: last-mile, label: route }
- { from: last-mile, to: pod-step, label: hand over }
- { from: last-mile, to: sort, label: not home, role: return, variant: dashed }
@@ -0,0 +1,32 @@
schema_version: 1
diagram_type: architecture
meta:
title: Application cooperation
output: application-cooperation.html
decisions: [edi-gateway-in-front-of-tms]
components:
- ref: shipper
pos: [40, 260]
size: [130, 60]
- ref: edi-gateway
pos: [250, 260]
size: [130, 60]
decisions: [edi-gateway-in-front-of-tms]
- ref: tms
pos: [460, 260]
size: [130, 60]
- ref: driver-app
pos: [460, 60]
size: [130, 60]
- ref: telematics
pos: [460, 460]
size: [130, 60]
- ref: tracking-portal
pos: [670, 260]
size: [130, 60]
connections:
- { from: shipper, to: edi-gateway, label: bookings, variant: emphasis }
- { from: edi-gateway, to: tms, label: shipments, variant: emphasis }
- { from: driver-app, to: tms, label: scans, labelAt: [525, 134], decisions: [broker-for-tracking-events] }
- { from: telematics, to: tms, label: positions, decisions: [broker-for-tracking-events] }
- { from: tms, to: tracking-portal, label: status }
@@ -0,0 +1,34 @@
schema_version: 1
diagram_type: architecture
meta:
title: Application services and data
output: application-services.html
components:
- ref: tracking-portal
pos: [40, 160]
size: [130, 60]
- ref: tracking-svc
pos: [250, 160]
size: [130, 60]
- ref: tms
pos: [460, 160]
size: [130, 60]
- ref: driver-app
pos: [670, 160]
size: [130, 60]
- ref: shipment
pos: [250, 360]
size: [130, 60]
- ref: tracking-event
pos: [460, 360]
size: [130, 60]
- ref: pod
pos: [670, 360]
size: [130, 60]
connections:
- { from: tracking-svc, to: tracking-portal, label: serves, variant: emphasis }
- { from: tms, to: tracking-svc, label: realizes }
- { from: driver-app, to: tms, label: uses }
- { from: tms, to: shipment, label: accesses }
- { from: tms, to: tracking-event, label: accesses, labelAt: [525, 234] }
- { from: driver-app, to: pod, label: accesses, labelAt: [735, 234] }
@@ -0,0 +1,44 @@
schema_version: 1
diagram_type: architecture
meta:
title: Technology infrastructure
output: infrastructure.html
decisions: [broker-for-tracking-events]
components:
- ref: handhelds
pos: [40, 160]
size: [130, 60]
- ref: telematics-units
pos: [40, 360]
size: [130, 60]
- ref: mobile-network
pos: [250, 260]
size: [130, 60]
- ref: cloud-cluster
pos: [460, 160]
size: [130, 60]
- ref: message-broker
pos: [460, 360]
size: [130, 60]
decisions: [broker-for-tracking-events]
- ref: db-server
pos: [670, 160]
size: [130, 60]
- ref: event-streaming
pos: [670, 360]
size: [130, 60]
boundaries:
- kind: region
label: Field devices
wraps: [handhelds, telematics-units]
- kind: security-group
label: Cloud platform
wraps: [cloud-cluster, message-broker, db-server, event-streaming]
connections:
- { from: handhelds, to: mobile-network, label: LTE }
- { from: telematics-units, to: mobile-network, label: LTE }
- { from: mobile-network, to: cloud-cluster, label: HTTPS, variant: security }
- { from: mobile-network, to: message-broker, label: MQTT, variant: security }
- { from: cloud-cluster, to: message-broker, label: hosts, labelAt: [525, 234] }
- { from: cloud-cluster, to: db-server, label: SQL }
- { from: message-broker, to: event-streaming, label: realizes }
@@ -0,0 +1,20 @@
schema_version: 1
decision:
id: broker-for-tracking-events
title: A message broker for tracking events
status: accepted
date: 2026-09-08
elements: [message-broker, telematics, driver-app, tms, tracking-event]
diagrams: [0300-technology/infrastructure.archify, 0200-application/application-cooperation.archify]
context: >
Handhelds and telematics units posted every scan and position
straight to the TMS. At evening peaks the TMS fell behind and
dropped events when a device retried over a weak signal.
decision: >
Devices publish tracking events to a Kafka message broker on
the cloud cluster. The TMS and telematics read the topics at
their own pace; events are kept for seven days for replay.
consequences: >
Spikes no longer reach the TMS. Status on the tracking portal
can lag by seconds. Consumers must handle duplicate events,
and the broker is one more platform service to run.
@@ -0,0 +1,20 @@
schema_version: 1
decision:
id: edi-gateway-in-front-of-tms
title: An EDI gateway in front of the TMS
status: accepted
date: 2026-09-22
elements: [edi-gateway, tms, shipper, shipment]
diagrams: [0200-application/application-cooperation.archify]
context: >
Large shippers send bookings as EDI files in three dialects.
Each dialect was parsed inside the TMS, so a new shipper meant
a TMS release.
decision: >
A separate EDI gateway receives, validates and translates
every booking into one shipment message for the TMS. It also
sends status messages back in the shipper's dialect.
consequences: >
New shippers are onboarded in the gateway alone. The TMS has
one booking interface. A rejected booking now fails at the
gateway, which customer service must be able to see.
@@ -0,0 +1,17 @@
schema_version: 1
decision:
id: photo-proof-of-delivery
title: Photo as proof of delivery
status: proposed
date: 2026-10-27
elements: [pod, driver-app, handhelds]
diagrams: [0200-application/application-services.archify, 0100-business/deliver-shipment.archify]
context: >
Most parcels are left at the door when nobody signs. Disputes
about such parcels take customer service days to settle.
decision: >
The driver app takes a photo of every parcel left without a
signature and stores it with the proof of delivery.
consequences: >
Disputes are settled from the photo. Photos are personal data
and are deleted after 90 days. Uploads add mobile data cost.
@@ -0,0 +1,59 @@
schema_version: 1
model:
id: logistics-tracking
name: Logistics Tracking
description: >
An ArchiMate example: a parcel carrier lets shippers and recipients
track shipments. Business, application and technology layers are
mapped to folders; each element's ArchiMate type is shown as its tag.
diagram_type: architecture
meta:
title: Logistics Tracking - layered view
output: main.html
components:
- ref: recipient
pos: [40, 70]
size: [170, 60]
- ref: tracking-service
pos: [270, 70]
size: [170, 60]
- ref: deliver-shipment
pos: [500, 70]
size: [170, 60]
- ref: tracking-portal
pos: [40, 270]
size: [170, 60]
- ref: tms
pos: [270, 270]
size: [170, 60]
- ref: tracking-svc
pos: [500, 270]
size: [170, 60]
- ref: mobile-network
pos: [40, 470]
size: [170, 60]
- ref: cloud-cluster
pos: [270, 470]
size: [170, 60]
- ref: event-streaming
pos: [500, 470]
size: [170, 60]
boundaries:
- kind: region
label: Business layer
wraps: [recipient, tracking-service, deliver-shipment]
- kind: region
label: Application layer
wraps: [tracking-portal, tms, tracking-svc]
- kind: region
label: Technology layer
wraps: [mobile-network, cloud-cluster, event-streaming]
connections:
- { from: tracking-service, to: recipient, label: serves, variant: emphasis }
- { from: deliver-shipment, to: tracking-service, label: realizes }
- { from: tracking-portal, to: recipient, label: serves }
- { from: tracking-svc, to: deliver-shipment, label: serves }
- { from: tms, to: tracking-svc, label: realizes }
- { from: mobile-network, to: tracking-portal, label: serves }
- { from: cloud-cluster, to: tms, label: serves }
- { from: event-streaming, to: tracking-svc, label: serves }
@@ -0,0 +1,67 @@
schema_version: 1
elements:
tms:
type: backend
label: TMS
sublabel: App Component
tag: App Component
description: >
Owns shipments, routes and hub plans; the source of truth for status.
diagram: 0200-application/application-cooperation.archify
tracking-portal:
type: frontend
label: Tracking portal
sublabel: App Component
tag: App Component
description: >
Public site where shippers and recipients follow a shipment.
edi-gateway:
type: security
label: EDI gateway
sublabel: App Component
tag: App Component
description: >
Receives booking messages from large shippers and returns status.
driver-app:
type: frontend
label: Driver app
sublabel: App Component
tag: App Component
description: >
Scans parcels at every hand-over and captures proof of delivery.
telematics:
type: backend
label: Telematics
sublabel: App Component
tag: App Component
description: >
Collects vehicle positions and turns them into arrival estimates.
tracking-svc:
type: backend
label: Tracking service
sublabel: App Service
tag: App Service
description: >
Status and arrival estimate of one shipment, offered by the TMS.
diagram: 0200-application/application-services.archify
shipment:
type: database
label: Shipment
sublabel: Data Object
tag: Data Object
description: >
One booked parcel with sender, recipient, route and status.
tracking-event:
type: database
label: Tracking event
sublabel: Data Object
tag: Data Object
description: >
A scan or position report; the history of a shipment.
pod:
type: database
label: Proof of delivery
sublabel: Data Object
tag: Data Object
description: >
Signature or photo taken at the door; closes the shipment.
@@ -0,0 +1,54 @@
schema_version: 1
elements:
shipper:
type: external
label: Shipper
sublabel: Business Actor
tag: Business Actor
description: >
Books shipments, hands parcels over at pick-up and follows
them until delivery.
recipient:
type: external
label: Recipient
sublabel: Business Actor
tag: Business Actor
description: >
Receives the parcel; tracks it and may reschedule delivery.
driver:
type: external
label: Driver
sublabel: Business Role
tag: Business Role
description: >
Collects parcels, drives the routes and captures proof of delivery.
customer-service:
type: external
label: Customer service
sublabel: Business Role
tag: Business Role
description: >
Answers shipper and recipient questions about late or lost parcels.
deliver-shipment:
type: backend
label: Deliver Shipment
sublabel: Business Process
tag: Business Process
description: >
Pick up, sort at hub, line haul, last mile and proof of delivery.
diagram: 0100-business/deliver-shipment.archify
delivery-service:
type: backend
label: Parcel delivery
sublabel: Business Service
tag: Business Service
description: >
What the carrier sells; a parcel collected and delivered on time.
diagram: 0100-business/business-services.archify
tracking-service:
type: backend
label: Shipment tracking
sublabel: Business Service
tag: Business Service
description: >
Where a parcel is and when it arrives, for shippers and recipients.
@@ -0,0 +1,55 @@
schema_version: 1
elements:
cloud-cluster:
type: cloud
label: Cloud cluster
sublabel: Node
brand: kubernetes
tag: Node
description: >
Container cluster that runs the TMS, portal, EDI gateway and telematics.
diagram: 0300-technology/infrastructure.archify
message-broker:
type: messagebus
label: Message broker
sublabel: System Software
brand: apache-kafka
tag: System Software
description: >
Carries tracking events from devices and vehicles to the applications.
db-server:
type: database
label: Database server
sublabel: System Software
brand: postgresql
tag: System Software
description: >
Stores shipments, tracking events and proofs of delivery.
event-streaming:
type: backend
label: Event streaming
sublabel: Tech Service
tag: Tech Service
description: >
Durable, ordered topics that applications publish to and read from.
handhelds:
type: external
label: Handhelds
sublabel: Device
tag: Device
description: >
Scanners carried by drivers and hub staff; run the driver app.
telematics-units:
type: external
label: Telematics units
sublabel: Device
tag: Device
description: >
GPS boxes in vans and trucks; report position every minute.
mobile-network:
type: security
label: Mobile network
sublabel: Network
tag: Network
description: >
Carrier-grade mobile network that links devices to the cluster.