POE course icon
POE Unit 3 • Lesson 3.18

Final Mission Demonstration and Design Review

Focus question: How can a team defend that its integrated autonomous system meets the mission requirements?

Mission Briefing

Today’s Plan

A focused sequence that advances the rover and VEX ground-support mission.

Opening promptConcept modelGuided practiceInteractive applicationEvidence checkExit ticket
Lesson Targets

What You Will Be Able to Do

Learning Target

I can organize a design review that connects requirements, architecture, test data, revisions, and final performance.

Evidence

Final mission demonstration and design review

Success Looks Like

Every major claim is supported by visible system evidence or quantitative mission data.

Activity Flow

How the Lesson Moves

Each step builds the control-systems reasoning needed for today’s deliverable.

1. Demonstrate the mission

Show the integrated rover and ground-support sequence.

2. Present the evidence

Connect requirements to architecture, tests, and revisions.

3. Defend the design

Answer questions using data, limitations, and next-step recommendations.

Lesson Interactive

Final mission demonstration and design review Practice

Apply the lesson concept to an aerospace rover or VEX ground-support scenario. Use the feedback to correct reasoning before documenting the main deliverable.

Final Evidence

4/5Mission passes
80%Success rate
83.5 sMedian pass time
9.5 mmMedian stop error

Order the Design-Review Story

  1. Revisions made after testing
  2. Mission need and measurable requirements
  3. System architecture and control logic
  4. Integrated prototype and demonstration plan
  5. Test method and quantitative data
  6. Final performance compared with requirements
  7. Remaining limitation and next recommendation
A defensible review connects the mission need to architecture, prototype, data, revisions, final performance, and limitations.
Today’s Work

Main Deliverable

Final Mission Design Review

Create one focused engineering artifact that demonstrates today’s learning.

  • Present the mission need, architecture, control logic, prototype, test data, revisions, and final result.
  • Use quantitative evidence to defend each major performance claim and identify one remaining limitation.
Exit Ticket

Mission Debrief

1

State one control-systems or automation idea from today in your own words.

2

Name one measurement, calculation, trace, or test result that supports your design decision.

3

Identify one interface, logic, safety, or reliability risk to carry into the next lesson.

Resources

Lesson Resources

Presentation

Lesson 3.18 PowerPoint

Use the presentation to review the lesson concepts, examples, and activity directions.

Course Hub

Principles of Engineering

Return to the POE course hub for units, resources, certifications, and course information.

Unit Challenge

Rover Mission + VEX Ground Support System

Use the integrated mission context when connecting logic, sensing, actuation, testing, and design-review evidence.