Unit 12 — Advanced Design and Robotics - Frog Trap, Stomp Rockets, and Final Challenges

• Observation of design thinking and decision-making
• Testing and data collection from multiple design iterations
• Class discussions about what works and why
• Sketches and documentation of design process
• Peer feedback on prototypes and presentations

Completed frog trap, stomp rocket, or other final challenge design with full documentation of problem, design process, testing data, and results; presentation explaining how the design was engineered and tested

Assessment of student ability to independently apply engineering design process to a new problem; reflection on STEM skills and learning across the year

Students may demonstrate understanding through a simplified design challenge with fewer components or a reduced scope (e.g., designing one part of a trap or rocket instead of the full system). Visual supports such as step-by-step photo guides, labeled diagrams, or video models of the engineering process may be provided. Students may explain their design choices orally with teacher support, or respond to guided questions about their testing and iterations instead of writing detailed documentation.

During complex multi-step design challenges, students benefit from chunked directions with visual step-by-step sequences and a model of the expected end product to reference throughout building and testing. For documentation and final presentations, allow students to demonstrate their design reasoning through oral explanation, dictation, or labeled drawings rather than requiring extended written responses. Providing structured graphic organizers that scaffold the engineering design process — such as sections for 'problem,' 'plan,' 'test,' and 'fix' — supports students in organizing their thinking without being overwhelmed by open-ended documentation. Frequent check-ins during testing cycles help students stay on track and receive feedback before frustration builds.

Students should have access to a distraction-reduced workspace during building and testing phases, as hands-on design challenges can involve a high level of stimulation that makes focus difficult. Extended time should be provided for documentation and any presentation components, and verbal or pictorial alternatives to written recording may be offered as needed. Preferential placement near the teacher during design demonstrations ensures students can see and hear modeling clearly before beginning independent work.

Introduce key engineering vocabulary — such as 'design,' 'prototype,' 'test,' 'iterate,' and 'data' — with visual supports like picture cards or a word wall before challenges begin, reinforcing these terms consistently throughout each project. Directions for each design phase should be given in short, clear steps and accompanied by visual diagrams or teacher demonstration so that language demands do not become a barrier to participation in the hands-on work. Encouraging students to sketch, label in their home language, or talk through their design process with a partner supports meaning-making across language levels. Connecting challenge contexts to familiar real-world experiences, such as movement or trapping in nature, can help build accessible entry points into the content.

Begin each challenge by activating prior knowledge of the engineering design process through brief review of steps students have used successfully in earlier units, helping students see that they already have relevant skills to draw on. Offering a partially completed design template or a simplified version of the challenge with fewer variables allows students to experience success and build confidence before adding complexity. Breaking the multi-week projects into smaller, clearly defined milestones with regular check-ins helps students maintain momentum and receive positive feedback on incremental progress. Pairing students strategically during collaborative work ensures peer support without removing individual accountability.

Students who demonstrate quick mastery of the core design challenge should be encouraged to add self-imposed constraints — such as limiting materials, optimizing for a specific measurable outcome, or combining elements of multiple projects — to push their engineering thinking to a deeper level. Extending the data collection and analysis component by asking students to compare results across iterations, form and test hypotheses, or present findings in a structured format similar to a scientific report adds meaningful rigor. Students may also be invited to research real-world engineering problems related to the challenge themes — such as wildlife conservation engineering or aerospace design — and connect that knowledge to their own design decisions, fostering interdisciplinary depth.