Capture of the screen: Systems of Record. Dark and light modes.
Narration line
It lets you prove the Authority's systems stay the record: every value on every screen names the system that owns it, and the twin holds no value of its own for a function a system of record covers.
Source: poc/bearings/sources.json, beat "What it shows"
Group
Set up
Status as the app labels it
Real
Basis
The screen runs. Data: carefully crafted and curated test data for common use cases.
What the screen must do (7)
Prove the Authority's systems stay the record: every value on every screen names the system that owns it, and the twin holds no value of its own for a function a system of record covers (REQ-FUNC-007, REQ-FUNC-014)
List every system of record and public source with its state (proposed, approved, active, paused, blocked, retired) and the age of its last reading (REQ-FUNC-011)
Show the probe, the licence or data agreement, the freshness target and the approver for each source (REQ-FUNC-012, REQ-FUNC-013)
Refuse to activate a source without a probe, a confirmed licence and an approver who is not the activator (REQ-FUNC-012, REQ-SEC-002)
Show the selected airport systems the RFP names as awaiting RFP until the document is read (REQ-FUNC-017)
Show which values each source owns, so the system of record is never in doubt (REQ-FUNC-014, REQ-FUNC-016)
Name each of the Authority's systems as Attachment C 6.9 lists them, with their connectivity (REQ-SFB-011, REQ-SFB-021, REQ-SFB-022, REQ-SFB-023)
Requirements matrix rows that name this screen (15)