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.
21 lines
798 B
Plaintext
21 lines
798 B
Plaintext
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.
|