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.
51 lines
1.4 KiB
Plaintext
51 lines
1.4 KiB
Plaintext
schema_version: 1
|
|
elements:
|
|
customer:
|
|
type: external
|
|
label: Customer
|
|
sublabel: Business Actor
|
|
tag: Business Actor
|
|
description: >
|
|
A person or small business holding one or more policies
|
|
with Halbrook Mutual.
|
|
insurant:
|
|
type: external
|
|
label: Insurant
|
|
sublabel: Business Role
|
|
tag: Business Role
|
|
description: >
|
|
The role a customer plays while a claim is open; reports
|
|
damage and receives the payment.
|
|
claims-handler:
|
|
type: external
|
|
label: Claims handler
|
|
sublabel: Business Role
|
|
tag: Business Role
|
|
description: >
|
|
Employee of the claims department who accepts, valuates
|
|
and approves claims.
|
|
handle-claim:
|
|
type: backend
|
|
label: Handle Claim
|
|
sublabel: Business Process
|
|
tag: Business Process
|
|
description: >
|
|
Register, accept, valuate and pay a claim; the core process
|
|
of the claims department.
|
|
diagram: 0100-business/handle-claim.archify
|
|
claim-registration:
|
|
type: frontend
|
|
label: Claim Registration
|
|
sublabel: Business Service
|
|
tag: Business Service
|
|
description: >
|
|
Lets an insurant report damage by phone, mail or the
|
|
customer portal.
|
|
claim-payment:
|
|
type: frontend
|
|
label: Claim Payment
|
|
sublabel: Business Service
|
|
tag: Business Service
|
|
description: >
|
|
Pays the valuated amount to the insurant or a repairer.
|