schema_version: 1 model: id: insurance-claims name: Insurance Claims description: > ArchiMate example: how Halbrook Mutual handles claims. The business, application and technology layers are mapped to folders, and each element's ArchiMate type is shown as its tag. diagram_type: architecture meta: title: Insurance Claims - layered view output: main.html components: - ref: insurant pos: [40, 70] size: [170, 60] - ref: claim-registration pos: [270, 70] size: [170, 60] - ref: handle-claim pos: [500, 70] size: [170, 60] - ref: portal pos: [40, 270] size: [170, 60] - ref: claims-app pos: [270, 270] size: [170, 60] - ref: claims-admin pos: [500, 270] size: [170, 60] - ref: dmz pos: [40, 470] size: [170, 60] - ref: app-servers pos: [270, 470] size: [170, 60] - ref: db-cluster pos: [500, 470] size: [170, 60] boundaries: - kind: region label: Business layer wraps: [insurant, claim-registration, handle-claim] - kind: region label: Application layer wraps: [portal, claims-app, claims-admin] - kind: region label: Technology layer wraps: [dmz, app-servers, db-cluster] connections: - { from: claim-registration, to: insurant, label: serves, variant: emphasis } - { from: handle-claim, to: claim-registration, label: realizes } - { from: portal, to: insurant, label: serves } - { from: claims-admin, to: handle-claim, label: serves } - { from: claims-app, to: claims-admin, label: realizes } - { from: dmz, to: portal, label: serves } - { from: app-servers, to: claims-app, label: serves } - { from: db-cluster, to: app-servers, label: serves }