root-at-skic
f4663c089d
Numbered cards for the text sections (1.1-1.3, 2, 4, 11, 12) on the overview, domain interfaces on the technical context, black-box descriptions for every building block, blocks mapped to nodes in the deployment view, crosscutting concepts on level 1, and a 1000-quality folder with the quality tree. The example test checks each section's card.
78 lines
1.9 KiB
Plaintext
78 lines
1.9 KiB
Plaintext
schema_version: 1
|
|
diagram_type: architecture
|
|
meta:
|
|
title: Quality tree
|
|
output: quality-tree.html
|
|
legend:
|
|
mode: hidden
|
|
components:
|
|
- id: quality
|
|
type: cloud
|
|
label: Quality
|
|
pos: [40, 200]
|
|
size: [130, 120]
|
|
- id: usability
|
|
type: frontend
|
|
label: Usability
|
|
pos: [250, 60]
|
|
size: [130, 60]
|
|
- id: security
|
|
type: security
|
|
label: Security
|
|
pos: [250, 160]
|
|
size: [130, 60]
|
|
- id: reliability
|
|
type: backend
|
|
label: Reliability
|
|
pos: [250, 310]
|
|
size: [130, 60]
|
|
- id: maintainability
|
|
type: backend
|
|
label: Maintainability
|
|
pos: [250, 460]
|
|
size: [130, 60]
|
|
- id: q-search
|
|
type: external
|
|
label: Search under 1 s
|
|
pos: [460, 60]
|
|
size: [170, 60]
|
|
- id: q-leaver
|
|
type: external
|
|
label: Leaver out in 5 min
|
|
pos: [460, 160]
|
|
size: [170, 60]
|
|
- id: q-restore
|
|
type: external
|
|
label: Restore in 30 min
|
|
pos: [460, 260]
|
|
size: [170, 60]
|
|
- id: q-pod
|
|
type: external
|
|
label: Pod back in 1 min
|
|
pos: [460, 360]
|
|
size: [170, 60]
|
|
- id: q-upgrade
|
|
type: external
|
|
label: Upgrade in 1 hour
|
|
pos: [460, 460]
|
|
size: [170, 60]
|
|
connections:
|
|
- { from: quality, to: usability }
|
|
- { from: quality, to: security }
|
|
- { from: quality, to: reliability }
|
|
- { from: quality, to: maintainability }
|
|
- { from: usability, to: q-search }
|
|
- { from: security, to: q-leaver }
|
|
- { from: reliability, to: q-restore }
|
|
- { from: reliability, to: q-pod }
|
|
- { from: maintainability, to: q-upgrade }
|
|
cards:
|
|
- dot: emerald
|
|
title: 10 Quality scenarios
|
|
items:
|
|
- "Search: an engineer searches 5000 pages; results in under 1 s"
|
|
- "Leaver: HR disables an account; wiki access ends within 5 minutes"
|
|
- "Restore: the database is lost; the admin restores last night in 30 minutes"
|
|
- "Crash: an API pod dies; the cluster restarts it, no data lost, back in 1 minute"
|
|
- "Upgrade: a new wiki version ships; one admin rolls it out in 1 hour"
|