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
@@ -0,0 +1,67 @@
|
||||
schema_version: 1
|
||||
elements:
|
||||
tms:
|
||||
type: backend
|
||||
label: TMS
|
||||
sublabel: App Component
|
||||
tag: App Component
|
||||
description: >
|
||||
Owns shipments, routes and hub plans; the source of truth for status.
|
||||
diagram: 0200-application/application-cooperation.archify
|
||||
tracking-portal:
|
||||
type: frontend
|
||||
label: Tracking portal
|
||||
sublabel: App Component
|
||||
tag: App Component
|
||||
description: >
|
||||
Public site where shippers and recipients follow a shipment.
|
||||
edi-gateway:
|
||||
type: security
|
||||
label: EDI gateway
|
||||
sublabel: App Component
|
||||
tag: App Component
|
||||
description: >
|
||||
Receives booking messages from large shippers and returns status.
|
||||
driver-app:
|
||||
type: frontend
|
||||
label: Driver app
|
||||
sublabel: App Component
|
||||
tag: App Component
|
||||
description: >
|
||||
Scans parcels at every hand-over and captures proof of delivery.
|
||||
telematics:
|
||||
type: backend
|
||||
label: Telematics
|
||||
sublabel: App Component
|
||||
tag: App Component
|
||||
description: >
|
||||
Collects vehicle positions and turns them into arrival estimates.
|
||||
tracking-svc:
|
||||
type: backend
|
||||
label: Tracking service
|
||||
sublabel: App Service
|
||||
tag: App Service
|
||||
description: >
|
||||
Status and arrival estimate of one shipment, offered by the TMS.
|
||||
diagram: 0200-application/application-services.archify
|
||||
shipment:
|
||||
type: database
|
||||
label: Shipment
|
||||
sublabel: Data Object
|
||||
tag: Data Object
|
||||
description: >
|
||||
One booked parcel with sender, recipient, route and status.
|
||||
tracking-event:
|
||||
type: database
|
||||
label: Tracking event
|
||||
sublabel: Data Object
|
||||
tag: Data Object
|
||||
description: >
|
||||
A scan or position report; the history of a shipment.
|
||||
pod:
|
||||
type: database
|
||||
label: Proof of delivery
|
||||
sublabel: Data Object
|
||||
tag: Data Object
|
||||
description: >
|
||||
Signature or photo taken at the door; closes the shipment.
|
||||
@@ -0,0 +1,54 @@
|
||||
schema_version: 1
|
||||
elements:
|
||||
shipper:
|
||||
type: external
|
||||
label: Shipper
|
||||
sublabel: Business Actor
|
||||
tag: Business Actor
|
||||
description: >
|
||||
Books shipments, hands parcels over at pick-up and follows
|
||||
them until delivery.
|
||||
recipient:
|
||||
type: external
|
||||
label: Recipient
|
||||
sublabel: Business Actor
|
||||
tag: Business Actor
|
||||
description: >
|
||||
Receives the parcel; tracks it and may reschedule delivery.
|
||||
driver:
|
||||
type: external
|
||||
label: Driver
|
||||
sublabel: Business Role
|
||||
tag: Business Role
|
||||
description: >
|
||||
Collects parcels, drives the routes and captures proof of delivery.
|
||||
customer-service:
|
||||
type: external
|
||||
label: Customer service
|
||||
sublabel: Business Role
|
||||
tag: Business Role
|
||||
description: >
|
||||
Answers shipper and recipient questions about late or lost parcels.
|
||||
deliver-shipment:
|
||||
type: backend
|
||||
label: Deliver Shipment
|
||||
sublabel: Business Process
|
||||
tag: Business Process
|
||||
description: >
|
||||
Pick up, sort at hub, line haul, last mile and proof of delivery.
|
||||
diagram: 0100-business/deliver-shipment.archify
|
||||
delivery-service:
|
||||
type: backend
|
||||
label: Parcel delivery
|
||||
sublabel: Business Service
|
||||
tag: Business Service
|
||||
description: >
|
||||
What the carrier sells; a parcel collected and delivered on time.
|
||||
diagram: 0100-business/business-services.archify
|
||||
tracking-service:
|
||||
type: backend
|
||||
label: Shipment tracking
|
||||
sublabel: Business Service
|
||||
tag: Business Service
|
||||
description: >
|
||||
Where a parcel is and when it arrives, for shippers and recipients.
|
||||
@@ -0,0 +1,55 @@
|
||||
schema_version: 1
|
||||
elements:
|
||||
cloud-cluster:
|
||||
type: cloud
|
||||
label: Cloud cluster
|
||||
sublabel: Node
|
||||
brand: kubernetes
|
||||
tag: Node
|
||||
description: >
|
||||
Container cluster that runs the TMS, portal, EDI gateway and telematics.
|
||||
diagram: 0300-technology/infrastructure.archify
|
||||
message-broker:
|
||||
type: messagebus
|
||||
label: Message broker
|
||||
sublabel: System Software
|
||||
brand: apache-kafka
|
||||
tag: System Software
|
||||
description: >
|
||||
Carries tracking events from devices and vehicles to the applications.
|
||||
db-server:
|
||||
type: database
|
||||
label: Database server
|
||||
sublabel: System Software
|
||||
brand: postgresql
|
||||
tag: System Software
|
||||
description: >
|
||||
Stores shipments, tracking events and proofs of delivery.
|
||||
event-streaming:
|
||||
type: backend
|
||||
label: Event streaming
|
||||
sublabel: Tech Service
|
||||
tag: Tech Service
|
||||
description: >
|
||||
Durable, ordered topics that applications publish to and read from.
|
||||
handhelds:
|
||||
type: external
|
||||
label: Handhelds
|
||||
sublabel: Device
|
||||
tag: Device
|
||||
description: >
|
||||
Scanners carried by drivers and hub staff; run the driver app.
|
||||
telematics-units:
|
||||
type: external
|
||||
label: Telematics units
|
||||
sublabel: Device
|
||||
tag: Device
|
||||
description: >
|
||||
GPS boxes in vans and trucks; report position every minute.
|
||||
mobile-network:
|
||||
type: security
|
||||
label: Mobile network
|
||||
sublabel: Network
|
||||
tag: Network
|
||||
description: >
|
||||
Carrier-grade mobile network that links devices to the cluster.
|
||||
Reference in new issue
Block a user