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
+20
@@ -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.
|
||||
+20
@@ -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.
|
||||
+17
@@ -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.
|
||||
Reference in new issue
Block a user