โ† Back to the chapter

Technical detail ยท Edge-Fog Use Cases: Decision Framework

Boundary tests and retest triggers

Use this matrix to turn the placement record into repeatable boundary tests. Each row links a failure or change to evidence and a reason to reopen the decision.

Boundary testWhat to varyPass evidenceRetest trigger
Disconnected operationWAN loss, broker restart, gateway reboot, local storage pressure.Named local behavior, queued or summarized records, safe stop rule, and replay result.New gateway software, storage policy, broker path, or response requirement.
Command authorityAllowed commands, stale commands, duplicate commands, denied identities.Command validation logs, rejection evidence, local override behavior, and audit trail.New actuator, role model, identity provider, or firmware version.
Evidence retentionFiltering level, compression, sampling window, privacy rule, retention window.Review can still explain alerts, misses, outages, model decisions, and operator action.New analytics goal, compliance rule, support process, or privacy boundary.
Lifecycle changeUpdate, rollback, replacement device, certificate rotation, model replacement.Known owner, rollback proof, version record, compatibility check, and health signal.New hardware revision, model runtime, gateway image, or cloud API contract.

โ† Back to the chapter