Week 17 · overview
Week 17: Capstone Phase 2: Mission Plan and Evidence Package
This week, you will build capstone mission plan package for a bounded Drone Engineering scenario. The work stays in classroom-safe analysis, supplied evidence, simulation, planning, and documentation. It does not authorize real flight or unsupervised hardware work.
The engineering problem
A concept brief is approved for planning, but the team has not yet organized route logic, roles, evidence, and review gates.
The core idea is that a plan is not ready until someone outside the team can inspect it. Students will connect that idea to route logic, platform assumptions, data requirements, crew roles, source verification, checklists, and artifact naming make the plan reviewable.
Evidence you keep
| Sequence | Evidence artifact |
|---|---|
| Lesson 1 | Mechanism explanation and first evidence table |
| Lesson 2 | Boundary note and no-go or revision condition |
| Lesson 3 | Review-ready decision table |
| Capstone Log | Capstone mission plan package with limitation statement |
Vocabulary and decision lens
Important language this week includes: system boundary, evidence, limitation, no-go condition, revision rule, and capstone phase 2: mission plan and evidence package.
Decision lens: revise any plan element that cannot be inspected, assigned, tested, or defended.
Approximate time: 3 to 4 class periods, about 160 to 200 minutes of reading, analysis, evidence writing, and review.