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.
54 lines
1.3 KiB
Plaintext
54 lines
1.3 KiB
Plaintext
schema_version: 1
|
|
elements:
|
|
hr-saas:
|
|
type: cloud
|
|
label: HR tenant
|
|
sublabel: Node
|
|
tag: Node
|
|
description: >
|
|
The SaaS tenant that runs the HR system.
|
|
diagram: 0300-technology/infrastructure.archify
|
|
itsm-saas:
|
|
type: cloud
|
|
label: ITSM tenant
|
|
sublabel: Node
|
|
tag: Node
|
|
description: >
|
|
The SaaS tenant that runs IT service management.
|
|
mdm-saas:
|
|
type: cloud
|
|
label: MDM tenant
|
|
sublabel: Node
|
|
tag: Node
|
|
description: >
|
|
The SaaS tenant that runs device management.
|
|
directory:
|
|
type: backend
|
|
label: Directory
|
|
sublabel: System Software
|
|
tag: System Software
|
|
description: >
|
|
Cloud directory service; users, groups and devices.
|
|
diagram: 0300-technology/infrastructure.archify
|
|
sso:
|
|
type: security
|
|
label: Single sign-on
|
|
sublabel: Tech Service
|
|
tag: Tech Service
|
|
description: >
|
|
SAML and OIDC sign-in for every SaaS tenant, backed by the directory.
|
|
laptop:
|
|
type: frontend
|
|
label: Laptop
|
|
sublabel: Device
|
|
tag: Device
|
|
description: >
|
|
Company laptop, enrolled before it is handed over.
|
|
office-net:
|
|
type: messagebus
|
|
label: Office network
|
|
sublabel: Network
|
|
tag: Network
|
|
description: >
|
|
Wired and wireless network of the office; internet only, no VPN.
|