Challenge the Convincing Alert

Challenge the Convincing Alert

Challenge the Convincing Alert

Picture a flood alert created from a five-minute average. The screen turns red, but the high reading arrived late and was counted in the wrong window. The alert looks reasonable while answering a different question from the one the operator asked.

Write the claim behind the alert in plain words. Name the source, event time, arrival time, grouping rule, stored state, output time, and action. Decide how the system treats late, repeated, missing, and corrected records. Keep a link from the output back to every input that changed it.

Test one trap at a time. Delay a reading, send it twice, change the clock, fill a stage, restart with saved state, and correct an earlier value. Check whether the alert changes, whether the operator can see why, and whether recovery repeats or loses an action. Record the owner and retest trigger.

Back to the chapter