← Back to the chapter · Previous detail · Next detail →
Technical detail · A Repeatable Design Method
Choose model detail that can change the decision
Every network model leaves something out. A simulator may approximate radio propagation, traffic timing, duty-cycle behavior, device sleep, queueing, mobility, interference, gateway backhaul, or broker behavior. A packet capture may show the protocol exchange but miss the site geometry. A short pilot may reveal installation problems but not seasonal traffic, firmware rollout load, long-term battery behavior, certificate expiry, or support escalation. Model fidelity is therefore a design choice: spend detail on the mechanism that can change the decision, and state what remains outside the evidence boundary.
The methodology should make those limits explicit. In MQTT, quality of service (QoS) sets how carefully a message is delivered and acknowledged; session expiry sets how long the broker keeps a disconnected client’s session state. These settings affect delivery and reconnection behavior, so record their assumed values. Physical-layer assumptions include path loss, antenna orientation, wall materials, metal shelving, water absorption, weather, noise floor, RSSI/SNR, receiver sensitivity, spreading factor, channel plan, and transmit-power limits. Protocol assumptions also include CoAP confirmable retransmission, TCP congestion behavior, TLS handshake cost, RPL DODAG repair (rebuilding routes in a low-power IPv6 mesh when links or parents fail), 802.15.4 MAC retries, Wi-Fi roaming, LoRaWAN ADR, BLE connection intervals, Thread router promotion, Zigbee binding, and cellular attach behavior. Operations assumptions include gateway backhaul, certificate expiry, SIM lifecycle, monitoring coverage, maintenance windows, spare devices, firmware update cadence, and incident escalation.