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
+20
@@ -0,0 +1,20 @@
|
||||
schema_version: 1
|
||||
decision:
|
||||
id: hr-system-drives-identity
|
||||
title: The HR system drives identity
|
||||
status: accepted
|
||||
date: 2026-09-08
|
||||
elements: [hr-system, iam, account, employee-record]
|
||||
diagrams: [0200-application/application-cooperation.archify, 0100-business/onboard-employee.archify]
|
||||
context: >
|
||||
Accounts were created by hand from emails sent by HR.
|
||||
New hires waited days for access, and leavers kept
|
||||
accounts for weeks after their last day.
|
||||
decision: >
|
||||
The HR system is the source of truth for joiners and
|
||||
leavers. Identity management reads its events and
|
||||
creates, changes and disables accounts automatically.
|
||||
consequences: >
|
||||
No account without an employee record. HR data quality
|
||||
now decides access, so start dates must be right. The
|
||||
service desk only handles exceptions.
|
||||
+20
@@ -0,0 +1,20 @@
|
||||
schema_version: 1
|
||||
decision:
|
||||
id: zero-touch-laptops
|
||||
title: Zero-touch enrollment for laptops
|
||||
status: accepted
|
||||
date: 2026-10-05
|
||||
elements: [mdm-app, mdm-saas, laptop, device-svc, asset]
|
||||
diagrams: [0300-technology/infrastructure.archify, 0100-business/onboard-employee.archify]
|
||||
context: >
|
||||
Every laptop was imaged by hand at the service desk,
|
||||
which took half a day per device and left settings that
|
||||
differed from one laptop to the next.
|
||||
decision: >
|
||||
Laptops are registered in device management at purchase.
|
||||
They configure themselves at first sign-in over any
|
||||
internet connection; the office network needs no VPN.
|
||||
consequences: >
|
||||
Laptops can be shipped straight to the new hire. A lost
|
||||
laptop is wiped remotely. Setup depends on the MDM
|
||||
tenant being reachable on the first day.
|
||||
Reference in new issue
Block a user