0.11.0: arc42 and ArchiMate examples; ref in every diagram kind
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.
This commit is contained in:
1 parent
f4df6a0834
commit
0745de822a
85 files changed
+2945
-67
No files matched your search
@@ -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 }
|
||||
Reference in new issue
Block a user