← Back to the chapter · Next detail →
Technical detail · Capstone Projects: Planning and Evidence
Specify each interface contract
Treat every interface as a contract with evidence. Device-to-firmware contracts need pinout, bus speed, calibration, units, timing, error code, and warm-up behavior. Firmware-to-network contracts need topic naming, payload schema, QoS, retry behavior, local buffer limit, and duplicate handling. Network-to-cloud contracts need identity, authorization, TLS or DTLS posture where applicable, idempotency, schema version, and retention. Cloud-to-dashboard contracts need freshness labels, missing-data states, alert owner, and permission behavior.
Use the data path as the organizing model. At the device, verify sampling rate, calibration constants, units, monotonic timestamps, watchdog behavior, and error codes. At the radio or gateway, record RSSI or SNR, retry count, channel plan, duty-cycle limits, local buffer behavior, and whether duplicate packets are possible. At the broker and cloud service, record MQTT QoS, retained-message policy, device identity, topic authorization, schema version, idempotency key, retention window, and alert-rule owner. At the dashboard, distinguish missing data, stale data, out-of-range data, and values suppressed by permissions.