2.65 · Proof of concept · Set up
Environments and Operations Real
Where the service would run, how it would be watched and kept safe, and how staff learn it. A target, not deployed.
Picture: Headless capture of poc/index.html?v=envs&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale.
Screen · Proof of concept · Set up
Where the service would run, how it would be watched and kept safe, and how staff learn it. A target, not deployed.
- Sources
- Interchange
- Twin
- Screens
- Plan
- Kind
- Screen
- Status
- target
- Airport layer
- Screens: the POC story and the spines
- Airport area
- not linked
- System
- not linked
- Sensor type
- not linked
Open the screen · Open the detail
Level 2 of 3 This component, complete on its own. Its files, sources and tests are the detail below. Open the detail
Open this screen in the proof of concept
Capture of the screen: Environments and Operations. Dark and light modes.
Narration line
It shows the development, test and production environments, labelled target.
Source: poc/bearings/envs.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 (4)
- Show the development, test and production environments, labelled target (REQ-SFB-069)
- Show the cloud alarms, the log stream and the health checks the pattern configures (REQ-SFB-069, REQ-SFB-053)
- Show security and redundancy as the pattern configures them (REQ-SFB-069, REQ-SFB-046)
- Show the learning built into the product (REQ-SFB-069, REQ-SFB-047)
Requirements matrix rows that name this screen (1)
| Row | RFP section | Requirement | Status |
|---|
| M-073 | B ii; B v | Environments, monitoring, security and redundancy | target |
Requirement identifiers (4)
REQ-SFB-046, REQ-SFB-047, REQ-SFB-053, REQ-SFB-069