← Back to the chapter · Previous detail · Next detail →
Technical detail · Capstone Projects: Planning and Evidence
Measure states and inject faults
Evidence also needs grain. If a project records average latency, reviewers need to know whether it was measured per packet, per batch, per geofence event, per watering cycle, or per dashboard refresh. Power evidence should separate sensor warm-up, MCU active state, radio transmit, radio receive, sleep, and fault recovery. Security evidence should separate authentication, authorization, encryption in transit, credential rotation, and operational recovery.
Fault injection makes those contracts visible. Unplug a sensor, restart the broker, send a duplicate message, deny a dashboard permission, force a GPS timeout, or run the actuator with an empty tank flag. The point is not to make the prototype production-grade; it is to prove the team knows where the interface can fail and what evidence shows the failure was handled honestly.