
test my team’s prototype against our criteria and constraints, and record data to see how well it works.
Phase 4: Build
Look back. Find your team’s criteria and constraints table from the Investigate phase. Read it aloud. Is anything missing now that you have built a code?
Which one is a CRITERION, not a constraint?
A test run checks the goals. A good silent signal must send the right message every time. It must be fast. It must work for everyone, including a classmate who cannot hear well. These are the criteria.
Limits shape the design. The signal must reach across the field. It must be safe, with no light in anyone’s eyes. It must use cheap materials. These are the constraints.
Benefits, risks, and costs. A great design adds benefits and cuts risks and costs. A bright flashlight is a benefit. Shining it at faces is a risk. Buying a big speaker is a cost the school may not want.
Worked example 1: a checklist. Diego’s team turns its table into a checklist. They give each item a check or an X after the test run.
| Criterion or constraint | How we test it | Result (check / X) |
|---|---|---|
| Message read correctly | Send 4 messages; count correct | |
| Fast | Time all 4 messages | |
| Works without hearing | Receiver wears ear muffs | |
| Reaches far | Send from the end of the hallway | |
| Safe and cheap | Check: no light in eyes; classroom items only |
Worked example 2: reading results. Diego’s code got 4 of 4 correct up close. From the end of the hallway, it got only 2 of 4. The flashes looked too alike from far away. The test showed a problem they could fix. That is what a test run is for.
Change the situation. Test in more than one way: close and far, quiet and noisy, lights on and lights off. A design that passes every situation is a strong design.
Run your test run, then use your checklist to answer these.
| Situation | Messages correct (out of 4) | Time (seconds) | Notes |
|---|---|---|---|
| Close, quiet | |||
| Far, quiet | |||
| Far, noisy |
Plan your fix.
Write one change your team will try next. Which criterion or constraint will it help with? How will you test it?
How confident are you that you can I can describe my design's criteria and constraints and test against them.
Your test run found strengths and problems. Next lesson is our mid-build checkpoint. Then we will give and get feedback.
Exit ticket: name one criterion and one constraint for the silent signal. Explain why each matters to the client.
Materials: team prototypes and code keys, stopwatches, ear muffs or soft headphones (not playing anything), masking tape to mark distances.
Setup: tape a close spot and a far spot in the hallway. Pair teams so one tests while the other makes crowd noise.
Listen for: mixing up criteria and constraints; “we failed” (a failed trial is useful data).
Support / stretch: provide the checklist pre-filled. Stretch: add a sixth row of the team’s own criterion.