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.
35 lines
944 B
Plaintext
35 lines
944 B
Plaintext
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] }
|