Grades 5–8 · STEM & Computer Science
How do you teach students in Grades 5–8 to design detector alert rules with a false-alarm check?
Short answer: Give students a sequence of simulated sensor readings and two candidate rules, such as alert on one wet reading or alert on two consecutive wet readings. They trace each rule, record the first alert time and count false alarms. Then a leak pattern that breaks the stricter rule shows that every threshold involves a trade-off.
- Grades5–8
- ModelLow-voltage detector model with simulated readings
- ComparesAlert speed vs. false alarms
- Includes42-page PDF, 16 slides, 5 worksheets and answer keys
Smoke detectors that go off when someone makes toast, car alarms that sound in the wind: students know false alarms well. They are less used to thinking about the opposite failure, a detector that stays silent when something is really wrong. Designing an alert rule means balancing both.
Design a Water-Leak Detector turns that balance into a concrete design task. Students work with a low-voltage leak-detector model and simulated readings, not live water or household electrics. They trace rules minute by minute, compare how fast each one alerts and how often it alerts by mistake, and learn that a rule is only as good as the cases it was tested on.
Units for this topic
Design a Water-Leak Detector
The lead unit: students design alert rules for a leak-detector model and compare speed with false alarms.
Sensor Calibration with a Paper Microcontroller
Students calibrate a simulated sensor with known references and check for systematic error.
Design an Accessible Emergency Alert
Students compare emergency alert prototypes against a user profile and a measurable test.
Test an Evacuation Route with a Paper Simulation
A paper simulation where students compare routes and state what a model cannot establish.
Spreadsheet Skills for Classroom Data
Students clean a small dataset and chart only valid rows, reinforcing careful data handling.
Unplugged Robot Debugging Cards
Unplugged tracing of command sequences, a simpler version of tracing rules step by step.
Tracing two rules
The starting case in Design a Water-Leak Detector gives readings every minute: 0, 0, 1, 0, 1, 1, 1, 0, where 1 means the test sensor is wet. Rule A alerts on any single wet reading. Rule B requires two consecutive wet readings. The wet reading at minute 3 is an isolated splash.
Rule A alerts at minute 3, which is a false alarm caused by the splash. Rule B ignores the splash and alerts at minute 6, after two wet readings in a row. Students record both first-alert times and decide what each rule gains and loses.
A simple table works well here: one row per minute, one column per rule, and a mark where each rule would sound. Students can see at a glance that rule A fires early and wrongly, while rule B waits three more minutes for stronger evidence. The question of which is better has no answer until they decide what a missed leak or a needless alert would cost.
- Trace readings minute by minute
- Record the first alert for each rule
- Mark which alerts are false
When the stricter rule fails
Rule B looks better until students see a different leak. In one task, a true leak causes readings of 1, 0, 1, 0. Rule B never fires, because no two wet readings are consecutive. The rule that avoided the false alarm now misses a real problem.
The next case tries a compromise: a two-in-three rule. With leak readings of 1, 0, 1, 0, 1, students trace how it behaves. The transfer challenge asks them to explain the trade-off in raising the threshold further. Each version of the rule fixes one problem and creates another, which is the central lesson of the unit.
Practicing the trace
Short tracing tasks build fluency. In the second context, readings are 0, 1, 0, 1, 1, numbered from minute 1. Students find the first trigger for the one-wet rule (minute 2) and the two-consecutive rule (minute 5). The learning-check item uses 0, 1, 1, 0 and asks when the two-consecutive rule first triggers. The answer is minute 3.
For a related lesson in reading sensor data carefully, Sensor Calibration with a Paper Microcontroller has students correct a systematic offset using known references. Both units share the same caution: a rule that works on tested cases may still fail outside them.
Inside the unit
The unit includes a 42-page teaching PDF with four 90-minute double lessons, an entry diagnosis, differentiation, teacher background, five learner inputs with mini-checks, five ready-to-copy worksheets, five answer keys, support and extension cards, and a 20-point learning check with model responses and a 100-point scoring sheet. Sixteen slides with teacher notes show the traces and rule comparisons. All readings are simulated; the model uses low voltage only.
A five-step sequence
-
Introduce the readings
Show the eight-minute sequence 0, 0, 1, 0, 1, 1, 1, 0 and explain that minute 3 is a splash, not a leak.
-
Trace rule A
Students trace the one-wet rule, find the first alert at minute 3 and label it a false alarm.
-
Trace rule B
Students trace the two-consecutive rule, find the first alert at minute 6 and note the delay compared with rule A.
-
Break the stricter rule
Give the leak pattern 1, 0, 1, 0. Students show that rule B never fires and explain the risk.
-
Propose and test a compromise
Students design a rule such as two wet readings in three minutes, trace it on several sequences, and describe its trade-off.
Common mix-ups and what to try
The best detector alerts as fast as possible.
A rule that fires on every wet reading also fires on splashes. Speed and false alarms have to be weighed together.
A stricter rule is always safer.
Requiring two consecutive wet readings can miss a leak that drips on and off. Students see this with the 1, 0, 1, 0 pattern.
If a rule works on the test data, it is reliable.
A rule is only tested on the cases tried. New patterns can expose failures, so students test several sequences.
More STEM & Computer Science units
Related teaching guides
Frequently asked questions
Do students build a real electronic detector?
No. The unit uses a low-voltage model and simulated readings. Students design and trace rules on paper, with no live water or household electrics.
Do students need coding experience?
No. Rules are written in plain language or simple pseudocode and traced by hand.
Which subjects does this fit?
STEM, engineering design or computer science classes in Grades 5–8 that cover inputs, rules and testing.
How long are the traces?
Short, typically four to eight readings, so students can focus on the logic rather than bookkeeping.
How is learning assessed?
The 20-point learning check asks students to trace rules and explain trade-offs. Model responses and a 100-point scoring sheet support marking.
What if it does not match my engineering standards?
Every resource is built around the curriculum you teach – and if something doesn't fit your standards, the TeachLessons Guarantee applies: we adapt it for you.
Ready for your next lesson?
Get Design a Water-Leak Detector and teach students that every alert rule is a trade-off.
View Design a Water-Leak DetectorInstant digital download. Every resource is built around the curriculum you teach – and if something doesn't fit your standards, the TeachLessons Guarantee applies: we adapt it for you.

