← Back to the chapter · Previous detail
Technical detail · A Repeatable Design Method
Keep a reproducible evidence record
Under the hood, the design record needs enough provenance that another reviewer can challenge or rerun the work. Store simulator version, configuration files, random-seed policy, topology inputs, traffic traces, packet-capture location, clock synchronization, firmware version, gateway firmware, cloud-region assumptions, and post-processing scripts. If a report shows latency percentiles, say how timestamps were captured and whether gateway, broker, or application clocks were aligned. If a report shows packet delivery, say whether duplicate receptions, retransmissions, retained messages, and application-level de-duplication were counted. If a result depends on a default model, name that default rather than hiding it behind a chart.
- Model state: Topology, traffic distribution, mobility, loss model, queue policy, retry timing, firmware behavior, and sample schedule.
- Measurement state: Capture point, clock alignment, sample size, test duration, site condition, firmware version, and calibration status.
- Decision state: Accepted margin, fallback plan, owner, deployment limit, monitoring requirement, known blind spot, and next review trigger.
Check the tool itself with a small case whose answer is known. Check units. Check signs. Check that a larger loss makes the link worse. Check that more traffic cannot create free capacity. These tests show that the tool follows its own rules.