← Back to the chapter · Previous detail
Technical detail · Empathize and Define
Make constraints testable
Make the constraint set precise enough that a prototype can fail honestly. A vague finding such as “users need trust” is not testable. A stronger constraint says that after a sensor misses three reporting intervals, the interface must show stale status, last successful heartbeat, battery estimate, network path, and next recovery action within one screen. A vague finding such as “installation is confusing” becomes a commissioning state machine with entry criteria, timeout handling, retry copy, and logs for QR scan, BLE pairing, Wi-Fi credential exchange, cloud claim, and first telemetry publish.
This translation also exposes privacy and safety obligations early. Purpose limitation means using collected information only for the reason people were told it would be used. Field-level retention means setting how long each kind of data is kept, rather than keeping every field for the same period. If research shows that a device observes a shared corridor, the data model needs these limits and access roles. A nearby device or gateway can remove or blur identifying details before sending data to the cloud; this is called edge redaction. If an alert can trigger a physical response, the system needs confidence thresholds, duplicate suppression, audit records, manual override, and clear ownership for who acts. The Define stage is complete only when the team can point from every major product claim to an observed need, a system behavior, a measurable outcome, and a prototype or field test that can prove or disprove the assumption.
- Finding to state: Turn observed confusion into explicit product states, labels, and recovery paths.
- Finding to metric: Measure task completion, correct alert classification, setup recovery, acknowledgement time, and privacy comprehension.
- Finding to prototype: Choose paper flow, Figma screen, bench device, MQTT mock, or field pilot based on the current uncertainty.
Use NIST SP 800-213 for IoT device cybersecurity requirements planning from the device perspective.