Milestone map
Milestone map
2 milestones
Design, build and test a working system
8–10 weeks (about 12 hrs/week)
Design, build and test a system that senses, computes and acts or communicates: for example a sensor node that reports over a radio or serial link, a motor speed controller, a digital filter running on a microcontroller, or a small processor running a program on an FPGA design. Simulation-only is allowed (Wokwi, SimulIDE, ngspice, Verilator). Write the requirements and a test plan first, then show measured results against them. This is what the Honors blind review reads. Hardware is optional, costs money. Safety: 12 V DC or less, from AA, AAA or 9 V batteries or USB only. Never mains power, never a lithium-polymer pack or loose lithium cell, and never a home-made battery charger. Wear eye protection when soldering or cutting leads. Under 18? Use the simulator, or build and solder with an adult present.
Proof required
Link the public repo with the schematic or HDL, the code, the test plan, the results against each requirement, and a README that says how to rerun it (or open it in the simulator).
What gets checked
- The system senses, computes and acts or communicates, and each requirement has a test.
- Every test result is measured or simulated, and failed tests are reported honestly.
- Someone else can rerun it from the repo or the simulator link.
Common mistakes
- A demo with no requirements or test plan.
- Results that the repo cannot reproduce.
Powstik Guide
A working system with its schematic or HDL, code, test plan and results, in a public repo.
Steps
- Write the requirements (what it senses, computes and does).
- Write the test plan with a number for each requirement.
- Build it in simulation first (hardware optional).
- Run every test and record the results.
- Write the README so someone else can rerun it.
Template
README System: Requirements: Test plan (test → expected number): Results (measured → pass or fail): How to rerun it: What I would change:
What gets sent back
- No test plan.
- It does not run from the repo or the simulator link.
- Mains power, a lithium pack or loose cell, a home-made charger, or more than 12 V DC.
Resources
Foundationstart here
What a verifier looks for
- Does it run from the repo or the simulator link?
- Do the measured results match the test plan's numbers?
- The build uses 12 V DC or less from AA, AAA or 9 V batteries or USB; nothing touches mains, and there is no lithium pack, loose cell or home-made charger.
You'll sign in first, then come straight back here.
Give a 10-minute demo and talk
1–2 weeks
Record a 10-minute demo and talk on your capstone for people who know engineering: what it does, how you tested it, and what you would change. Then take their questions.
Proof required
Link the recording and the slides, and say who the audience was (for example a study group, a maker club or a class).
What gets checked
- The talk fits in 10 minutes and shows the system working.
- Results are stated against the requirements.
- Questions are answered honestly, including what did not work.
Common mistakes
- Reading the README aloud.
- Hiding the tests that failed.
Powstik Guide
A recorded 10-minute demo and talk, with questions.
Steps
- Plan one slide per idea.
- Rehearse to 10 minutes.
- Invite people who know engineering.
- Record the demo, the talk and the questions.
Template
Talk plan One-line result: Demo: Three slides that get there: Questions I expect:
What gets sent back
- No recording.
- No questions taken.
Resources
What a verifier looks for
- Does the demo show the system working?
- Do the results match the repo?
- Were questions answered honestly?
You'll sign in first, then come straight back here.
Part of