- Read how Carlos improved his bike whistle code. Original device: 1 short meant slow, 2 short meant stop. Test showed the whistle was hard to hear when wind blew away. Problem: sound did not reach his friend. Carlos added a bright orange flag to wave when stopping. New test on a windy day: his friend saw the flag and stopped. What change made the device work better?
Answer: Problem: wind blocked sound → Improvement: added bright flag → Result: friend saw stop signal
This question tests understanding of 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving (or iterating) means making something better after testing shows problems. We use test results to decide what to change. Good improvements solve specific problems found during testing. Carlos's original device was a bike whistle code using different patterns. Testing showed a problem: the whistle was hard to hear when wind blew the sound away. The cause was that wind dispersed sound waves before they reached his friend. Carlos improved the device by adding a bright orange flag to wave when stopping. The improvement addresses the problem because visual signals (flag) are not affected by wind like sound signals are. The correct answer says "Problem: wind blocked sound → Improvement: added bright flag → Result: friend saw stop signal" which accurately identifies how Carlos switched from sound to sight when wind interfered. This shows understanding of iteration: test results (showed wind problem) → analyze (sound affected by wind) → improve (add visual backup) → test again (friend saw flag). Distractors like "Problem: too dark → Improvement: glow sticks" are wrong because this describes a different scenario - Carlos's problem was wind affecting sound, not darkness affecting sight. Students might choose this if they memorize solutions without understanding which problem each solves. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: "Before: whistle sound blown away by wind. After: added visible flag. Now: friend sees signal even in wind! The flag solved the wind problem." Emphasize matching solutions to problems: wind affects sound but not sight, so add visual signal. Let students practice: test different signals in various conditions (wind, rain, distance), identify which conditions affect which signals. Watch for: students who apply solutions randomly without considering the specific problem.
- Read how Carlos improved his whistle signals after a test. Original device: 1 short=slow, 2 short=stop. Test showed wind made the whistle hard to hear. Carlos added a bright orange flag and used whistle + flag wave for "stop." New test: friend stopped in the wind. What problem did Carlos solve by improving the device?
Answer: Problem: wind made whistle hard to hear → Improvement: added a flag signal → Result: friend could see stop.
This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance, focusing on improving the device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process: design, build, test, improve, and test again. Testing reveals what works and what doesn't, and we use those results to decide on changes that solve specific problems, then test again to verify the improvement. Carlos's original device was whistle signals with 1 short for 'slow' and 2 short for 'stop.' Testing showed a problem: wind made the whistle hard to hear. The cause was wind dispersing sound waves. Carlos improved the device by adding a bright orange flag and using whistle + flag wave for 'stop.' The improvement addresses the problem because the flag adds a visual signal unaffected by wind. The correct answer says 'Problem: wind made whistle hard to hear → Improvement: added a flag signal → Result: friend could see stop' which accurately identifies the problem and targeted improvement. This shows understanding of iteration: test results (showed hearing issue) → analyze (understand why) → improve (add visual) → test again (verify it worked). A distractor like 'Problem: no problem at all → Improvement: no changes → Result: it always worked in wind' is wrong because it denies the test-revealed problem. Students might choose this if they ignore test results or think conditions don't affect devices. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: hard to hear in wind. After: added flag. Now: can see signal!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes). Let students practice: build simple device, test it, find one problem, discuss what might fix it, try improvement, test again.
- Read how Sofia improved her flag signals after a test. Original device: wave flag=can play, hold up=yes, down=no. Test showed it did not work at nighttime because it was too dark to see. Sofia taped glow sticks to both flags and kept the same motions. New test at night: the friend saw the glowing flag and answered. Why did Sofia add glow sticks?
Answer: Problem: Too dark to see → Improvement: added glow sticks → Result: flags were visible at night.
This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance, focusing on improving the device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process: design, build, test, improve, and test again. Testing reveals what works and what doesn't, and we use those results to decide on changes that solve specific problems, then test again to verify the improvement. Sofia's original device was flag signals with wave for 'can play,' up for 'yes,' and down for 'no.' Testing showed a problem: it did not work at nighttime because it was too dark to see. The cause was lack of light making the flags invisible. Sofia improved the device by taping glow sticks to both flags and keeping the same motions. The improvement addresses the problem because glow sticks provide light, making the flags visible in the dark. The correct answer says 'Problem: Too dark to see → Improvement: added glow sticks → Result: flags were visible at night' which accurately identifies the problem from testing and how the improvement solved it. This shows understanding of iteration: test results (showed darkness issue) → analyze (understand why) → improve (add light source) → test again (verify it worked). A distractor like 'Problem: No one liked the colors → Improvement: painted stripes → Result: flags looked nicer in daytime' is wrong because it identifies a wrong problem not from testing and describes a change not made, unrelated to visibility. Students might choose this if they do not connect test results to improvements or confuse aesthetic changes with functional ones. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: could not see flag at night. After: added glow stick. Now: can see at night!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes). Let students practice: build simple device, test it, find one problem, discuss what might fix it, try improvement, test again.
- Read how Jamal improved his dinner bell. Test showed the bell did not work when his door was closed because the sound was blocked. Jamal moved the bell to the stairway and tested again with the door closed. He heard the rings. How did Jamal improve the device?
Answer: Problem: sound blocked → Improvement: moved bell to stairway → Result: sound carried even with door closed.
This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process where you design, build, test, improve, and test again to ensure it works well. Testing reveals what works and what doesn't, allowing us to use those results to decide on targeted changes that solve specific issues, and then test again to verify the improvement. Jamal's original device was a dinner bell for signaling meal times. Testing showed a problem: the bell did not work when his door was closed because the sound was blocked. Jamal improved the device by moving the bell to the stairway. The correct answer says 'Problem: sound blocked → Improvement: moved bell to stairway → Result: sound carried even with door closed' which accurately identifies the improvement made and why it solves the problem, showing understanding of iteration: test results (showed blockage) → analyze (understand why) → improve (make changes that address cause) → test again (verify it worked). A distractor like 'Problem: no problem → Improvement: changed ring code daily → Result: Jamal got confused each time' is wrong because it claims no problem when testing showed one and describes a change not made, and students might choose this if they confuse code changes with physical improvements. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: sound blocked by door. After: moved to stairway. Now: can hear with door closed!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes).
- Read how Marcus improved his window light board after a test. Original device: a flashing light in the window meant "come in." Test showed it did not work on a sunny day because the lights were not bright enough and kids were not always looking. Marcus added more bulbs and added a small bell that rang when lights flashed. New test: sunny day, kids heard the bell, looked, and saw the flashing lights. Did the improvement solve the problem?
Answer: Yes, brighter lights and a bell helped kids notice in sunshine.
This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance, focusing on improving the device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process: design, build, test, improve, and test again. Testing reveals what works and what doesn't, and we use those results to decide on changes that solve specific problems, then test again to verify the improvement. Marcus's original device was a flashing light in the window meaning 'come in.' Testing showed a problem: it did not work on a sunny day because the lights were not bright enough and kids were not always looking. The cause was sunlight overpowering the lights and lack of attention cue. Marcus improved the device by adding more bulbs for brightness and a small bell that rang with flashes. The improvement addresses the problem because brighter lights are visible in sun and the bell alerts kids to look. The correct answer says 'Yes, brighter lights and a bell helped kids notice in sunshine' which accurately identifies why the improvement solved the visibility and attention issues. This shows understanding of iteration: test results (showed brightness and notice issues) → analyze (understand why) → improve (increase brightness and add sound cue) → test again (verify it worked). A distractor like 'No, it still failed in sun because he used fewer bulbs and no bell' is wrong because it confuses the changes made, claiming fewer bulbs when more were added. Students might choose this if they confuse before and after or do not follow the cause-effect chain. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: lights too dim in sun, no alert. After: brighter lights and bell. Now: kids notice!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes). Let students practice: build simple device, test it, find one problem, discuss what might fix it, try improvement, test again.
- Read how Sofia improved her flag signals. Test showed the flags did not work at night because it was too dark. She added glow sticks to the flags and tested again at night. Her friend saw the glowing flag and answered "yes." Did the improvement solve the problem?
Answer: Problem: too dark to see → Improvement: glow sticks → Result: friend saw the flag at night clearly.
This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process where you design, build, test, improve, and test again to ensure it works well. Testing reveals what works and what doesn't, allowing us to use those results to decide on targeted changes that solve specific issues, and then test again to verify the improvement. Sofia's original device was flag signals for communication like 'can play?' or yes/no. Testing showed a problem: flags did not work at night because it was too dark. Sofia improved the device by adding glow sticks to the flags. The correct answer says 'Problem: too dark to see → Improvement: glow sticks → Result: friend saw the flag at night clearly' which accurately identifies the problem that testing revealed and the improvement made, showing understanding of iteration: test results (showed darkness issue) → analyze (understand why) → improve (make changes that address cause) → test again (verify it worked). A distractor like 'Problem: too dark to see → Improvement: changed nothing → Result: friend still could not see the flag' is wrong because it claims no improvement when one was made and worked, and students might choose this if they do not understand how changes solve problems. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: could not see flag at night. After: added glow sticks. Now: can see glowing flag!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes).
- Read how Emma improved her flashlight code. Original device: 1 flash meant come here, 2 meant yes, 3 meant no. Test showed white flashes did not work in bright daytime because they were hard to see. Emma taped red cellophane on her flashlight. New test in a bright room: her brother saw the red flashes. What problem did Emma solve by improving the device?
Answer: Problem: bright room hid flashes → Improvement: red filter → Result: brother saw flashes in daylight
This question tests understanding of 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving (or iterating) means making something better after testing shows problems. We use test results to decide what to change. Testing shows what works and what does not work. Emma's original device was a flashlight code using white light flashes. Testing showed a problem: white flashes did not work in bright daytime because they were hard to see. The cause was that white light does not contrast well against bright backgrounds. Emma improved the device by taping red cellophane on her flashlight. The improvement addresses the problem because red light provides better contrast against bright daylight than white light. The correct answer says "Problem: bright room hid flashes → Improvement: red filter → Result: brother saw flashes in daylight" which accurately identifies how brightness masked white flashes and how the red filter solved this. This shows understanding of iteration: test results (showed brightness interference) → analyze (white blends with bright light) → improve (add color contrast) → test again (brother saw red flashes). Distractors like "Problem: nighttime darkness → Improvement: glow sticks" are wrong because this describes a completely different scenario - Emma's problem was too much light (brightness), not darkness. Students might choose this if they memorize solution patterns without understanding the actual problem being solved. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: "Before: white flash invisible in bright room. After: red cellophane added. Now: red flash visible in bright room! The color solved the brightness problem." Emphasize that different lighting conditions need different solutions: darkness needs light added, brightness needs contrast added. Watch for: students who think all visibility problems are about adding more light.
- Read how Jamal improved his dinner bell. Original device: 2 rings meant 5 minutes, 3 rings meant now. Test showed Jamal did not hear it with his door closed because sound was blocked. Jamal moved the bell to the stairway. New test: Jamal heard 3 rings with the door closed. What change made the device work better?
Answer: Problem: sound blocked → Improvement: moved bell to stairway → Result: sound carried to Jamal
This question tests understanding of 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving (or iterating) means making something better after testing shows problems. Engineering design process: design → build → test → improve → test again. Good improvements solve specific problems found during testing. Jamal's original device was a dinner bell with coded rings in one location. Testing showed a problem: Jamal did not hear it with his door closed because sound was blocked. The cause was that the closed door prevented sound waves from reaching Jamal. Jamal improved the device by moving the bell to the stairway. The improvement addresses the problem because sound from an open stairway can travel throughout the house better than sound trapped behind a door. The correct answer says "Problem: sound blocked → Improvement: moved bell to stairway → Result: sound carried to Jamal" which accurately identifies how relocating the bell to an open area solved the sound blockage problem. This shows understanding of iteration: test results (showed blockage) → analyze (door blocks sound) → improve (move to open location) → test again (sound reached Jamal). Distractors like "Problem: too dark → Improvement: glow sticks" are wrong because Jamal's device was a sound device (bell) with a sound problem (blockage), not a light device with a visibility problem. Students might choose this if they confuse different types of communication devices and their specific problems. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: "Before: bell behind door, sound blocked. After: bell in stairway. Now: sound travels freely! Moving solved the blockage problem." Let students practice: place sound makers in different locations, test with barriers, discover how location affects sound travel. Watch for: students who think all improvements involve adding materials rather than changing location.
- Read how Marcus improved his light board. Original device: a window light flashed to mean "come in." Test showed it was hard to see in sunny weather, and kids were not always looking. Problem: lights were not bright enough and no one noticed. Marcus added more bulbs and a small bell that rang. New test on a sunny day: kids heard the bell and saw the lights. Why does the improved device work better?
Answer: Problem: too sunny → Improvement: more bulbs and bell → Result: kids noticed and saw the signal
This question tests understanding of 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving (or iterating) means making something better after testing shows problems. Testing shows what works and what does not work. After improving, we test again to see if the improvement worked. Marcus's original device was a window light flash signal. Testing showed two problems: lights were hard to see in sunny weather and kids were not always looking at the window. The cause was insufficient brightness in sunlight and lack of attention-getting feature. Marcus improved the device by adding more bulbs (for brightness) and a small bell (to get attention). The improvement addresses both problems because brighter lights show up better in sun and the bell alerts kids to look. The correct answer says "Problem: too sunny → Improvement: more bulbs and bell → Result: kids noticed and saw the signal" which accurately identifies how the improvements solved both visibility and attention problems. This shows understanding of iteration: test results (showed two problems) → analyze (not bright enough, not noticed) → improve (add brightness and sound alert) → test again (kids heard bell and saw lights). Distractors like "Problem: too quiet → Improvement: fewer bulbs" are wrong because this suggests reducing bulbs would help with sound, which makes no sense - Marcus added bulbs for brightness and a bell for sound. Students might choose this if they confuse which improvement addresses which problem. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: "Before: dim light in sun, kids did not look. After: brighter lights and bell. Now: bell makes kids look, bright lights visible! Two improvements for two problems." Emphasize that devices can have multiple problems requiring multiple improvements. Watch for: students who think one change fixes everything or who do not connect specific improvements to specific problems.
- Read how Marcus improved his window light board. Test showed kids did not always look at the window, and the lights were hard to see in sun. Marcus added a bell that rang with the flashing lights and added more bulbs. New test: kids heard the bell and looked. Why did Marcus add a bell?
Answer: Problem: kids were not looking → Improvement: added bell sound → Result: bell got attention so kids looked at lights.
This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process where you design, build, test, improve, and test again to ensure it works well. Testing reveals what works and what doesn't, allowing us to use those results to decide on targeted changes that solve specific issues, and then test again to verify the improvement. Marcus's original device was a window light board with flashing lights for signaling. Testing showed problems: kids did not always look at the window, and lights were hard to see in sun. Marcus improved the device by adding a bell that rang with the flashing lights and more bulbs. The correct answer says 'Problem: kids were not looking → Improvement: added bell sound → Result: bell got attention so kids looked at lights' which accurately identifies a key problem and why the improvement solves it, showing understanding of iteration: test results (showed attention issue) → analyze (understand why) → improve (make changes that address cause) → test again (verify it worked). A distractor like 'Problem: no problem → Improvement: added bell sound → Result: the device worked the same as before' is wrong because it ignores the problems found in testing and claims no change in function, and students might choose this if they do not connect additions to solving specific issues. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: kids missed lights. After: added bell. Now: bell alerts them to look!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes).
- Read how Sofia improved her flag system after a test. Original device: wave=can play, up=yes, down=no. Test showed it did not work at night because it was too dark. Sofia taped glow sticks to the flags and kept the same motions. New test at night worked. How did Sofia improve the device?
Answer: Problem: too dark → Improvement: taped glow sticks → Result: flags could be seen at night.
This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance, focusing on improving the device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process: design, build, test, improve, and test again. Testing reveals what works and what doesn't, and we use those results to decide on changes that solve specific problems, then test again to verify the improvement. Sofia's original device was a flag system with wave for 'can play,' up for 'yes,' and down for 'no.' Testing showed a problem: it did not work at night because it was too dark. The cause was lack of light making flags invisible. Sofia improved the device by taping glow sticks to the flags and keeping the same motions. The improvement addresses the problem because glow sticks emit light, making flags visible in darkness. The correct answer says 'Problem: too dark → Improvement: taped glow sticks → Result: flags could be seen at night' which accurately identifies the problem, improvement, and result. This shows understanding of iteration: test results (showed darkness issue) → analyze (understand why) → improve (add light) → test again (verify it worked). A distractor like 'Problem: no problem → Improvement: changed nothing → Result: flags worked in the dark before' is wrong because it claims no problem when testing showed failure in dark. Students might choose this if they do not connect test results to improvements or think devices work without changes. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: too dark to see. After: glow sticks. Now: visible at night!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes). Let students practice: build simple device, test it, find one problem, discuss what might fix it, try improvement, test again.
- Read how Emma improved her flashlight code. Before: white flashes were hard to see in bright daytime. Test showed her brother missed the signal because the room was too bright. Problem: the light did not show up. Emma added red cellophane on her flashlight and kept the same code. New test in a bright room: her brother saw the red flashes and understood. Why did Emma add red cellophane?
Answer: Problem: too bright → Improvement: red cellophane → Result: flashes showed up in daylight
This question tests understanding of 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving (or iterating) means making something better after testing shows problems. Engineering design process: design → build → test → improve → test again. Testing shows what works and what does not work. We use test results to decide what to change. Emma's original device was white flashlight flashes for communication. Testing showed a problem: white flashes were hard to see in bright daytime because the room was too bright. The cause was that white light did not show up well against bright backgrounds. Emma improved the device by adding red cellophane to her flashlight. The improvement addresses the problem because red light contrasts better with bright daylight than white light does. The correct answer says "Problem: too bright → Improvement: red cellophane → Result: flashes showed up in daylight" which accurately identifies the problem that testing revealed (too bright), the improvement made (red cellophane), and why the improvement solves the problem (flashes now show up). This shows understanding of iteration: test results (showed brightness problem) → analyze (white light hard to see) → improve (add red filter) → test again (brother saw red flashes). Distractors like "Problem: dark night" are wrong because the test showed the opposite problem - it was too bright during daytime, not too dark at night. Students might choose this if they confuse when different colored lights work best or assume all visibility problems are about darkness. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: "Before: could not see white flash in bright room. After: added red cellophane. Now: can see red flash in bright room! The red color solved the brightness problem." Emphasize targeted improvements: identify specific problem from test (too bright), understand cause (white blends with bright light), change the specific thing causing problem (add color that contrasts). Watch for: students who think darkness is the only visibility problem, or who do not understand how color contrast helps visibility in different lighting conditions.
- Read how Emma improved her flashlight code after a test. Before: 1 flash=come here, 2=yes, 3=no. Test showed it did not work in bright daylight because her brother could not see the white flashes. Emma added red cellophane to her flashlight and blue cellophane to her brother's. She kept the same code. New test in a bright room: her brother saw the red flashes and understood. What problem did Emma solve by improving the device?
Answer: Problem: Flashes were hard to see → Improvement: added red cellophane → Result: flashes showed up in bright daylight.
This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance, focusing on improving the device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process: design, build, test, improve, and test again. Testing reveals what works and what doesn't, and we use those results to decide on changes that solve specific problems, then test again to verify the improvement. Emma's original device was a flashlight code with 1 flash for 'come here,' 2 for 'yes,' and 3 for 'no.' Testing showed a problem: it did not work in bright daylight because her brother could not see the white flashes. The cause was the white light blending into the bright surroundings. Emma improved the device by adding red cellophane to her flashlight and blue to her brother's. The improvement addresses the problem because colored flashes are more visible against bright daylight. The correct answer says 'Problem: Flashes were hard to see → Improvement: added red cellophane → Result: flashes showed up in bright daylight' which accurately identifies the problem from testing, the targeted improvement, and the successful result. This shows understanding of iteration: test results (showed visibility issue) → analyze (understand why) → improve (add color for contrast) → test again (verify it worked). A distractor like 'Problem: There was no problem → Improvement: no changes → Result: it worked perfectly in bright rooms before' is wrong because it denies the test-revealed problem and claims no improvement was needed, when testing clearly showed failure in daylight. Students might choose this if they do not connect test results to improvements or think devices always work without changes. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: could not see white flashes in daylight. After: added red cellophane. Now: can see red flashes!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes). Let students practice: build simple device, test it, find one problem, discuss what might fix it, try improvement, test again.
- Read how Sofia improved her flag signals. Original device: wave meant "can play?", hold up meant "yes," down meant "no." Test showed the flags did not work at night because it was too dark to see. Sofia taped glow sticks on both flags. New test at night: her friend saw the glowing flag and answered. Did the improvement solve the problem?
Answer: Problem: too dark → Improvement: glow sticks → Result: friend saw the flags at night
This question tests understanding of 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving (or iterating) means making something better after testing shows problems. Testing shows what works and what does not work. This cycle continues until device works well. Sofia's original device was flag signals using different positions. Testing showed a problem: the flags did not work at night because it was too dark to see them. The cause was lack of light - flags need light to be visible. Sofia improved the device by taping glow sticks on both flags. The improvement addresses the problem because glow sticks produce their own light, making flags visible in darkness. The correct answer says "Problem: too dark → Improvement: glow sticks → Result: friend saw the flags at night" which accurately identifies the problem (darkness), the improvement (adding light source), and confirms the improvement worked. This shows understanding of iteration: test results (showed darkness problem) → analyze (need light to see) → improve (add glow sticks) → test again (friend saw glowing flags). Distractors like "Problem: too bright" are wrong because the test showed darkness was the problem, not brightness - this is the opposite condition. Students might choose this if they confuse different visibility problems or do not understand that darkness and brightness require different solutions. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: "Before: could not see flag at night. After: added glow stick. Now: can see at night! The glow stick solved the dark problem." Emphasize that improvements must match the specific problem: darkness needs light added, brightness needs contrast or shading. Let students practice: test visual signals in different lighting, identify when each fails, discuss appropriate improvements. Watch for: students who suggest random improvements not connected to the darkness problem.
- Read how Chen improved his drum code. Original device: 3 fast taps meant "stop." Test showed one worker near a loud saw could not hear the drum. Problem: the drum sound was covered by noise. Chen added a red flag on a tall pole and waved it with 3 taps. New test: all workers saw the flag and stopped. What did Chen learn from testing that led to improvement?
Answer: Problem: drum was too soft → Improvement: added red flag → Result: workers could see stop signal
This question tests understanding of 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving (or iterating) means making something better after testing shows problems. Good improvements solve specific problems found during testing. This cycle continues until device works well. Chen's original device was a drum code with 3 fast taps meaning "stop." Testing showed a problem: one worker near a loud saw could not hear the drum because the drum sound was covered by noise. The cause was that the saw's loud noise masked the drum sound. Chen improved the device by adding a red flag on a tall pole to wave with the drum taps. The improvement addresses the problem because visual signals (flag) are not affected by noise like sound signals are. The correct answer says "Problem: drum was too soft → Improvement: added red flag → Result: workers could see stop signal" which accurately identifies that the drum sound was insufficient (too soft relative to saw noise) and adding a visual signal solved it. This shows understanding of iteration: test results (showed noise interference) → analyze (sound masked by louder sound) → improve (add visual backup) → test again (all workers saw flag). Distractors like "Problem: workers could not see → Improvement: turned off lights" are wrong because the original problem was about hearing the drum, not seeing, and turning off lights would make visibility worse. Students might choose this if they confuse the original problem with the solution. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: "Before: drum sound covered by saw noise. After: added visible flag. Now: workers see flag even with noise! The flag solved the noise problem." Emphasize using different senses when one is blocked: if sound fails, try sight; if sight fails, try sound. Watch for: students who think making drums louder is the only solution to noise problems.
- Read how Carlos improved his bike whistle code. Original: 1 short meant slow, 2 short meant stop. Test showed on a windy day his friend could not hear well because the wind blew the sound away. Carlos added a bright orange flag and used whistle plus waving the flag for "stop." New test: friend saw the flag and stopped. What problem did Carlos solve by improving the device?
Answer: Problem: friend could not hear in wind → Improvement: added bright flag → Result: friend could see the stop signal.
This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process where you design, build, test, improve, and test again to ensure it works well. Testing reveals what works and what doesn't, allowing us to use those results to decide on targeted changes that solve specific issues, and then test again to verify the improvement. Carlos's original device was a bike whistle code with 1 short meaning slow and 2 short meaning stop. Testing showed a problem: on a windy day, his friend could not hear well because the wind blew the sound away. Carlos improved the device by adding a bright orange flag and using whistle plus waving the flag for 'stop.' The correct answer says 'Problem: friend could not hear in wind → Improvement: added bright flag → Result: friend could see the stop signal' which accurately identifies the problem that testing revealed and the improvement made, showing understanding of iteration: test results (showed audibility issue) → analyze (understand why) → improve (make changes that address cause) → test again (verify it worked). A distractor like 'Problem: no problem at all → Improvement: changed nothing → Result: it worked the same as before' is wrong because it claims no problem existed when testing showed wind interference, and students might choose this if they do not connect test results to improvements. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: could not hear whistle in wind. After: added flag. Now: can see signal in wind!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes).
- Read how Emma improved her flashlight code. Test showed white flashes did not work in a bright room. She taped red cellophane on her flashlight, kept 1=come here, 2=yes, 3=no, and tested again in daylight. Now her brother saw the red flashes clearly. What change made the device work better?
Answer: Problem: bright room hid flashes → Improvement: added red cellophane → Result: brother saw flashes in daylight.
This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process where you design, build, test, improve, and test again to ensure it works well. Testing reveals what works and what doesn't, allowing us to use those results to decide on targeted changes that solve specific issues, and then test again to verify the improvement. Emma's original device was a flashlight with white flashes for codes like 1=come here, 2=yes, 3=no. Testing showed a problem: white flashes did not work in a bright room because the brightness hid them. Emma improved the device by taping red cellophane on the flashlight. The correct answer says 'Problem: bright room hid flashes → Improvement: added red cellophane → Result: brother saw flashes in daylight' which accurately identifies the improvement made and why it solves the problem, showing understanding of iteration: test results (showed visibility issue) → analyze (understand why) → improve (make changes that address cause) → test again (verify it worked). A distractor like 'Problem: no problem → Improvement: changed nothing → Result: it worked the same as before' is wrong because it claims no problem existed when testing clearly showed one, and students might choose this if they do not connect test results to improvements or think devices are perfect without testing. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: could not see white flashes in bright room. After: added red cellophane. Now: can see red flashes in daylight!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes).
- Read how Carlos improved his bike whistle code after a test. Original device: 1 short=slow, 2 short=stop. Test showed it did not work on a windy day because the friend could not hear the whistle well. Carlos kept the whistle code and added a bright orange flag on his bike. New code: whistle + wave flag=stop, just whistle=slow. New test: windy day, friend saw the flag and stopped. Why does the improved device work better?
Answer: Problem: Wind blocked sound → Improvement: added orange flag → Result: friend could see the stop signal.
This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance, focusing on improving the device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process: design, build, test, improve, and test again. Testing reveals what works and what doesn't, and we use those results to decide on changes that solve specific problems, then test again to verify the improvement. Carlos's original device was a bike whistle code with 1 short for 'slow' and 2 short for 'stop.' Testing showed a problem: it did not work on a windy day because the friend could not hear the whistle well. The cause was wind interfering with sound transmission. Carlos improved the device by adding a bright orange flag on his bike, with new code: whistle + wave flag for 'stop,' just whistle for 'slow.' The improvement addresses the problem because the visual flag provides a sight-based signal that wind doesn't affect. The correct answer says 'Problem: Wind blocked sound → Improvement: added orange flag → Result: friend could see the stop signal' which accurately identifies the problem and how the visual addition solved it. This shows understanding of iteration: test results (showed sound issue in wind) → analyze (understand why) → improve (add visual element) → test again (verify it worked). A distractor like 'Problem: No problem happened → Improvement: changed nothing → Result: whistle was always easy to hear' is wrong because it claims no problem existed when testing showed wind interference. Students might choose this if they do not understand how specific conditions like wind cause problems or ignore test results. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: could not hear whistle in wind. After: added flag. Now: can see signal!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes). Let students practice: build simple device, test it, find one problem, discuss what might fix it, try improvement, test again.
- Read how Marcus improved his window light board. Original: flashing lights meant "come in." Test showed it did not work on a sunny day because the lights were not bright enough, and kids were not always looking. Marcus added more bulbs and a small bell that rang when the lights flashed. New test: kids heard the bell, looked, and saw the lights. Why does the improved device work better?
Answer: Problem: lights too dim and missed → Improvement: brighter lights plus bell → Result: kids heard bell and saw flashes.
This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process where you design, build, test, improve, and test again to ensure it works well. Testing reveals what works and what doesn't, allowing us to use those results to decide on targeted changes that solve specific issues, and then test again to verify the improvement. Marcus's original device was a window light board with flashing lights meaning 'come in.' Testing showed a problem: it did not work on a sunny day because lights were not bright enough, and kids were not always looking. Marcus improved the device by adding more bulbs and a small bell that rang when lights flashed. The correct answer says 'Problem: lights too dim and missed → Improvement: brighter lights plus bell → Result: kids heard bell and saw flashes' which accurately identifies the problems that testing revealed and why the improvements solve them, showing understanding of iteration: test results (showed visibility and attention issues) → analyze (understand why) → improve (make changes that address causes) → test again (verify it worked). A distractor like 'Problem: too dark at night → Improvement: turned off the lights → Result: kids saw better without light' is wrong because it identifies the wrong problem and a change not made, and students might choose this if they confuse day and night conditions. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: missed dim lights. After: added bell and brighter lights. Now: hear and see!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes).
- Read how Marcus improved his light board. Before: the light flash was hard to see in sun, and kids did not look at the window. Test showed the signal was missed. Marcus added more bulbs and a bell. New test: kids heard the bell, looked, and saw the flash. Did the improvement solve the problem?
Answer: Problem: too sunny and missed → Improvement: brighter bulbs and bell → Result: kids noticed and came in
This question tests understanding of 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving (or iterating) means making something better after testing shows problems. After improving, we test again to see if the improvement worked. This cycle continues until device works well. Marcus's original device was a window light flash signal. Testing showed two problems: the light flash was hard to see in sun and kids did not look at the window to notice the signal. The cause was insufficient brightness for sunny conditions and lack of attention-getting feature. Marcus improved the device by adding more bulbs (for visibility in sun) and a bell (to alert kids to look). The improvement addresses both problems because brighter lights overcome sunny conditions and the bell draws attention to look for the visual signal. The correct answer says "Problem: too sunny and missed → Improvement: brighter bulbs and bell → Result: kids noticed and came in" which accurately identifies both problems and how each improvement addressed them. This shows understanding of iteration: test results (showed two problems) → analyze (not bright enough, not noticed) → improve (increase brightness, add alert) → test again (kids heard bell and saw bright signal). Distractors like "Problem: no problem → Improvement: none" are wrong because the passage clearly states testing revealed problems that needed solving. Students might choose this if they do not carefully read about the test results. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: "Before: dim light lost in sun, kids did not notice. After: bright lights and bell. Now: bell alerts, bright lights visible! Two improvements for two problems." Emphasize reading test results carefully to identify all problems. Watch for: students who miss that multiple problems can require multiple coordinated improvements.
