Mission Design & Payload Thinking
Choose a Mission Objective
Select a mission objective and understand how it shapes all other decisions.
- Time estimate
- 20–25 min
- Complexity
- introductory
- Maturity
- pilot ready
- Simulator readiness
- partial
- Software available now
- Available now as teaching model — Mission Design Lab templates with objectives and constraint cards; not a requirements database or CAD.
Student flow
1) Pick a scenario
2) Rewrite vague → testable
3) Generate brief
Evidence and self-check are local-only. Copy/export or screenshot if you want to share.
Learning outcomes
Student can state a clear mission objective and explain how it drives system requirements.
- State the difference between a mission objective and a system requirement.
- Explain why a vague objective ('take pictures') leads to poor design.
- Connect mission objective to payload type.
Concept primer
Select a mission objective and understand how it shapes all other decisions.
Select a mission template in Mission Design Lab; read objective and constraint cards.
Write a one-sentence mission objective and list three things the satellite must do.
Interactive lab
Teaching-grade software activity slot — not a flight simulator or certified propagator.
Pick a scenario
Rewrite vague → testable
Vague objective: “Take pictures of coastal cities.”
Hints:
- Name the user (who acts on the images?).
- Pick a measurable resolution or area.
- State a cadence (per day / per week).
Three derived needs
What must the satellite do to support your objective? Hints based on your scenario:
- Daylight imaging passes over coastal regions.
- Pointing accuracy good enough for the chosen resolution.
- Downlink capacity for image data per day.
Mission brief (auto-generated)
(Write your rewritten objective above to generate a brief.)
Local self-check
Assessment (practice only)
Use this as a self-check and discussion starter. It is local-only and not a grade.
Optional: attaches a local summary (completed / quick checks / checklist count).
Quick check
Multiple choice self-check
This is a local self-check to support discussion. It is not a grade.
Quick check: Which statement best describes the difference between a mission objective and a system requirement?
Quick check: Which is the most testable rewrite of the vague objective ‘take pictures of cities’?
Discussion prompt
Short answer (local only)
Write notes for yourself or your group. Nothing is submitted.
Short answer (1–2 sentences): Pick a vague objective like ‘help farmers’ and rewrite it so it includes who benefits, what is measured, and one threshold.
Checklist
Local checklist self-check
Use this to verify you covered key ideas. Nothing is submitted.
Checklist: Before claiming my objective is testable, can I say…
0 / 4 checked
Local summary
Assessment summary (practice only)
Completion
0 / 4 sections complete
Quick checks
0 / 2 correct
Shown only to support self-check.
Checklist
0 / 4 items checked
Reminder
Local-only practice summary. Not a grade and not submitted anywhere.
What this preview is / is not
Assessment engine v0 boundary note
- Student view (local practice): use this as a self-check and discussion starter.
- Local-only preview/practice: your answers are not submitted.
- No backend, no accounts, no roster, and no LMS integration.
- Not a grade. No credential or official scoring is implied.
- Teacher visibility into student answers is not implemented in MVPF8.
- Evidence runtime engine arrives in Phase 9 (not in this preview).
Capture
Evidence capture (local-only)
Capture what you did, what changed, what you observed, and how you explain it. This stays in your browser unless you copy/share it manually.
Selected inputs
- Scenario: Coastal flood imaging
- Vague objective: Take pictures of coastal cities.
Generated outputs
- Rewritten objective: (empty)
- Derived need 1: (empty)
- Derived need 2: (empty)
- Derived need 3: (empty)
- Mission brief: (Write your rewritten objective above to generate a brief.)
- Quality self-score (out of 4): 0
Checklist
Evidence checklist
0/4 checked
Evidence artifact (local-only)
Choose a Mission Objective
Captured: 2026-05-16T07:38:32.718Z · Level: middle_school · Track: mission_design_payload
Summary
Copyable class summary
Copy a readable summary for class notes, or copy JSON for a structured record. Local-only: nothing is submitted.
Evidence artifact (v1) Activity: Choose a Mission Objective Track: mission_design_payload Learner level: middle_school Captured: 2026-05-16T07:38:32.718Z Mission brief: Turn a vague mission idea into a clear, testable mission objective with a user, a measurable outcome, and a threshold. Selected inputs: - Scenario: Coastal flood imaging - Vague objective: Take pictures of coastal cities. Generated outputs: - Rewritten objective: (empty) - Derived need 1: (empty) - Derived need 2: (empty) - Derived need 3: (empty) - Mission brief: (Write your rewritten objective above to generate a brief.) - Quality self-score (out of 4): 0 Checklist: - [ ] I named the user or beneficiary on Earth. - [ ] I named the measurable outcome (what the mission produces). - [ ] I included at least one numeric threshold. - [ ] I treated this as a teaching brief, not a flight-grade requirements doc. Observations: (not provided) Reflection: (not provided) Model boundary note: Local-only teaching model. Not a requirements database, not CAD, not automated mission verification. Mission Design Lab is a teaching estimate. Evidence is not submitted anywhere and is not a grade. Policy reminder: - Local-only capture. Not submitted anywhere. Not a grade.
Evidence capture
Expected outputs learners should be able to show after the lab (Phase 9 evidence engine preview available).
- Written objective + three derived needs
- Student explains why vague objectives fail in design reviews
Reflection
Choose between three mission scenarios (imaging, communication, climate monitoring) and justify the choice.
Responses are not persisted in this preview unless a specific activity component adds storage later.
Assessment / quick check
Rewrite a vague objective (“take pictures”) into a testable objective with who, what, and why it matters.
Teacher notes
Use three contrasting scenario cards; force students to pick one and defend trade-offs aloud.
Teacher guide
Choose a Mission Objective
Use this block as facilitation guidance for the Mission Design / Payload mini-course. There is no roster, submission, or teacher visibility workflow in this phase — evidence is shared manually.
Facilitation moves
- Insist on naming a user or beneficiary out loud before any rewrite.
- Reject ‘good’, ‘fast’, ‘a lot’ — push for numbers and units.
- Use the testable example only after students attempt their own rewrite.
- Connect the brief to Activity 2.2: which subsystems does this objective imply?
Misconceptions to watch for
‘Take pictures’ is a mission objective.
An objective names a user, a measurable outcome, and at least one threshold. ‘Take pictures’ is a verb without scope.
An objective is the same thing as a payload.
The objective is the goal; the payload is the instrument that helps achieve it. They drive different decisions.
Boundary reminder: Mission Design / Payload is a teaching model (not a requirements database, not CAD, not automated verification) and the experience is local-only (no accounts, no submissions, not a grade).
Next activity
Suggested progression from the mission learning path. Links avoid missing activity routes.