build a first model of our shelter and plan a test for each criterion and constraint.
Phase 4: Build
Do Now. Why might an engineer build a small model before building the real thing? Give one reason.
What is a prototype?
The reading opens over the lesson; close it to come back to exactly where you were.
Weather Team, it is time to build. Choose the design you will make. Then buy your supplies with tokens and write down the cost.
Our design goals. In our design brief we wrote draft rules. Now we turn them into rules we can test on a model. Criteria are what the shelter must do. To show the seats stay dry, the learner paper under the roof stays dry. To show it stands up to wind, the shelter stays standing and moves 2 cm or less in fan wind. To show it keeps papers in place, the paper stays put. Six learner cards fit inside, with one open side so learners can see and reach the garden. Constraints are our limits. It fits on a 30 cm by 30 cm cardboard base. It is no taller than 30 cm. Our materials budget is 20 supply tokens or fewer. We build it in one class period.
Why we test. The purpose of testing is to find failure points. A failure point is a place where the design stops working. Finding one is good news. Now you know what to fix.
Plan a test for each goal. Each criterion and each constraint gets its own test. Decide what you will do, what you will measure and what stays the same.
Worked example 1: Grace’s rain test plan. Grace puts a paper towel square under the roof. Her team sprays 20 squirts from 30 cm above. They count wet spots on the square. The number of squirts and the height stay the same.
Worked example 2: Dev’s wind test plan. Dev marks where the base sits. The teacher runs a fan from 1 meter away for 30 seconds. Dev measures how many centimeters the base moved and writes whether the shelter stayed up. The fan distance and the time stay the same.
| Goal | How we will test it | What we measure | What stays the same |
|---|---|---|---|
| Paper stays dry | |||
| Stays up and in place | |||
| Six cards fit | |||
| Fits base and height | |||
| 20 tokens or fewer |
Build for 18 minutes. Stop when your teacher calls a check-in.
Finish your test plan table.
Explain why your team is testing the shelter. Use the words failure point.
Where do you think your shelter will fail first? Why?
Label your shelter and set it on the shelf. Next time the storm comes to our classroom.
Exit ticket: how many tokens did your shelter cost? Is that within our limit?
Materials: 30 cm cardboard bases, craft sticks, straws, card stock, tape, string, clay, pennies or washers, tested roof materials, tokens, scissors, six learner cards per team.
Sample token prices: sticks and straws 1 for 2 pieces, tape 1 per 30 cm, clay 2 per lump, roof materials as listed in 2.17.
Pacing: warm-up 3, reading 5, mini lecture 5, build 18, test plan and exit 9 minutes.
Misconceptions: “a failed test means we did badly”; “one test can check everything.”
Supports: pre-cut posts and offer a starter base. Stretch: design the shelter to come apart and fit in a folder.
Answer guide: test plans name an action, a measure and at least one thing kept the same. Purpose answers say testing finds failure points to improve.
NASA Jet Propulsion Laboratory Education, Engineering Design Process Flow Chart · NASA/JPL-Caltech education resource; reuse follows the JPL Image Policy
Engineers at NASA’s Jet Propulsion Laboratory help build robots and spacecraft. They share a chart for students. It shows how engineers solve problems. A chart like this is called a flow chart. You follow it from box to box.
First, engineers identify the problem. Next, they brainstorm ideas that might solve it. Then they select one design. After that, they build a model or prototype. A prototype is a first try at the real thing.
Now comes the test. Engineers test the prototype and judge how well it worked. Then the chart asks a question: did this solve the problem?
If the answer is yes, they share the solution. If the answer is no, they do not quit. The arrow goes back. They build again and test again. They keep going until they reach a solution.
So a test that shows a problem is not a failure. It tells engineers what to do next.
Source: NASA Jet Propulsion Laboratory Education, Engineering Design Process Flow Chart (jpl.nasa.gov)