
show what I know about structures, criteria and constraints, and fair test plans, so my team is ready to critique and improve.
Phase 4: Build
Do Now. Quick review with flashcards. Quiz your partner. Then flip roles.
Criterion
Tap to revealSomething a design must do
Constraint
Tap to revealA limit, like time, cost, size, or materials
Fair test
Tap to revealChange one thing, keep the rest the same
Failure point
Tap to revealA part that does not work yet
Structure
Tap to revealA part of a living thing
Function
Tap to revealThe job a part does
Checkpoint time. A checkpoint is a quick stop to see what you know. It is not a surprise. It helps you and your teacher find what to practice before the big test day.
How to answer a choice question. Read the question twice. Cover the answers and think of your own answer first. Then read every choice. Cross out the ones you know are wrong. Pick the best one left.
Worked example 1. “Which part of a rose helps keep it from being eaten?” Choices: roots, thorns, petals, seeds. Roots take in water, so cross that out. Petals and seeds help with making new plants. Thorns poke animals that try to eat the stem. The answer is thorns.
Worked example 2. “A team tests two clips. Clip A has 4 hooks. Clip B has 8 hooks. What should stay the same?” We look for the choice that keeps the bag, the snack, and the shakes the same. Only the number of hooks should change.
After the checkpoint. Your team will look at the answers together. Any idea that many of us missed becomes a quick reteach tomorrow.
Answer each question on your own first. Then compare with your team. Use the arrows to move through the checkpoint.
On your own, write a short answer.
Pick your team's borrowed structure. Explain how it works with at least one other part of the plant or animal to help it survive. Then name one criterion your invention must meet.
How confident are you that you can I can explain criteria, constraints, and fair tests.
Look at your answers with your team. Circle any question you are still unsure about. Next time, teams will trade feedback in a critique circle.
Exit ticket: which checkpoint question was hardest for you? Write what you now know about it.
Materials: devices or printed checkpoint; a tally sheet to track which items many students miss.
Setup: About 15 minutes for the checkpoint, 10 to review as teams, the rest for the written answer and a quick prototype check. Item map: roots = 4-LS1-1:2a; owl system = 4-LS1-1:4a; criterion and constraint = 3-5-ETS1-1:3a/3b; fair test = 3-5-ETS1-3:3a; why test = 3-5-ETS1-3:1a; felt evidence = 3-5-ETS1-3:2b.
Listen for: mixing up criteria and constraints (the most common miss), and “the talons caught it” without the senses and brain. Reteach the weakest item at the start of 3.17.
Support / stretch: Read items aloud on request; this is a science check, not a reading check. Stretch: students write one new four-choice question with one right answer and three tempting wrong ones.