Star Wars Day Engineering Challenge: Build a Recon Droid Prototype (Grades 9–12) You will complete the physical build in class using mostly recyclable/reused materials. This Formative is your group’s engineering design log: document your plan, upload sketches/photos, record test results, and reflect on iterations. Submission: One group member submits for the team (include names/roles where prompted). Upload evidence at each checkpoint. Challenge option: Add a moving part (simple mechanism) or a basic robotics component if available.
Your team has been contracted to design a recon droid prototype for a mission where humans can’t safely go. (Yes… recon droids can be shady—we’ll address ethics later.)
Your prototype should:
Survive a “field drop” test from a safe classroom height agreed on by your teacher.
Carry at least one “sensor” or “tool” feature (prototype version is okay—e.g., a periscope, camera placeholder, mirror, light, “sample grabber,” etc.).
Include a clear way to store/relay information (e.g., map sketch pocket, data card slot, QR code tag, pretend antenna, or actual microcontroller if available).
Be labeled with major subsystems (chassis/body, sensor/tool, power, communications, and one other).
Mostly recyclable/reused materials (bring from home or use classroom scrap).
Fits on a desktop and can be carried safely by one student.
Must be safe: no sharp exposed edges; no hazardous liquids/chemicals.
Add one:
A moving mechanism (hinge, lever, claw, wheel/axle, cam, rubber-band drive), OR
A simple robotics component (if available): small motor/servo, LED indicator, microcontroller, etc.
Throughout this Formative you’ll upload: sketches, photos, and test notes. This is how your teacher tracks your engineering process.
In 3 words or fewer: What is your recon droid’s main mission?
Write a clear problem statement for your recon droid.
Include:
Who the “user” is
The environment/constraints
What success looks like (measurable)
Any assumptions you’re making
Upload a photo of your first sketch OR draw directly.
Your sketch must:
Show a front/side view (one is fine)
Label at least 5 parts/subsystems
Indicate at least one moving feature OR where it could be added
Match each recon droid subsystem to its main job.
| Stavka koja se može prevući | arrow_right_alt | Odgovarajuća stavka |
|---|---|---|
Communications | arrow_right_alt | Holds structure and protects parts |
Data storage | arrow_right_alt | Detects/observes the environment |
Chassis | arrow_right_alt | Provides energy for functions |
Sensor suite | arrow_right_alt | Sends/receives information |
Power module | arrow_right_alt | Records observations for later review |
List the materials you plan to use and explain why each one fits your design.
Include:
Material/source (e.g., cereal box cardboard, bottle caps)
What it will be used for
Why it’s a good fit (strength, flexibility, weight, availability, etc.)
Any backup substitutions
You need to attach a cardboard “sensor mast” to a cardboard body so it can survive a drop test and be adjusted during iteration. Which fastening approach is most effective for strength and easy redesign?
Upload 1–3 photos of your prototype mid-build.
In a sentence or two, describe:
What changed from your initial sketch
One challenge you ran into
Before you test, write your plan.
Include:
What you will test (drop, mobility, sensor/tool function, data return, etc.)
Your measurable success criteria
What you will measure/observe and how
Variables you will keep the same vs. change
Safety notes
In 3 words or fewer: What was your biggest failure mode in testing?
Which changes are the best next steps for improving your prototype based on test results? (Select 2)
Upload 1–2 photos showing the change you made after testing.
In 2–3 sentences, explain:
What you changed
Why you changed it (connect to evidence)
What you predict will improve
Recon droids can collect information without people noticing.
Answer as a team:
What is one realistic harm your recon droid could cause if used irresponsibly?
What is one design feature or rule/protocol you could add to reduce that harm?
Who should have control/permission to use the droid, and why?
Resequence the steps into a strong engineering workflow.
Iterate based on evidence
Sketch & plan materials/constraints
Brainstorm and choose a concept
Build a prototype
Define the problem & success criteria
Communicate results
Test and record data
Answer as a team.
Include:
What changed the most from your first sketch to your latest version?
What evidence led you to make that change?
What tradeoff did you accept (e.g., weight vs. strength, speed vs. stability), and why?
If you had one more class period, what would you improve next?
Team roles: list names + what each person contributed
Which design choices would most likely improve survivability in a drop test? (Select 2)
Which requirement best matches a constraint (something that limits your design)?