root-at-skic
0745de822a
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.
33 lines
992 B
Plaintext
33 lines
992 B
Plaintext
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 }
|