Mission / Subsystem Trade-off

Student flow

Do this in order

Open Student Mode →

Step 1

Choose learner level

Step 2

Pick a mission type

Step 3

Review subsystem priority cards

Step 4

Allocate the priority budget

Step 5

Read the trade-off warnings

Step 6

Choose a final design strategy

Step 7

Local self-check (assessment)

Step 8

Capture evidence and continue

Local-only learning activity. Nothing is submitted; use copy/export or a screenshot to share evidence manually.

Learning outcomes

Student can explain how a mission objective changes subsystem priorities and justify at least one engineering trade-off using evidence.

Explain how a mission objective shifts subsystem priorities.
Allocate a limited priority budget across subsystems.
Defend a chosen trade-off with at least one piece of evidence (warning or constraint).

Key vocabulary

Mission objective: What the mission must accomplish for users or science (one clear sentence).
Subsystem priority: How important a subsystem is for this specific mission objective (low / medium / high).
Trade-off: A choice where increasing one quality forces a decrease somewhere else.
Constraint: A limit you cannot cross (e.g., total mass, total power, available contact time).
Requirement: A specific thing the system must do or provide to meet the objective.
Power budget: Accounting of generated, stored, and consumed power over the mission timeline.
Data budget: Accounting of data generated onboard versus data downlinkable through contact windows.
Pointing requirement: How accurately the spacecraft must aim cameras, antennas, or sensors.
Contact window: Time when a ground station can hear the spacecraft and exchange data.
Risk: A possible event that would reduce mission success — handled by margin and verification.
Verification: Evidence that a requirement is actually met (test, analysis, or demonstration).

Concept primer

Mission / Subsystem Trade-off: Choose What Matters Most — explore how a CubeSat mission objective changes subsystem priorities, resources, and engineering trade-offs.

Open Mission / Subsystem Trade-off at `/twin/learn/activities/orientation_mission_subsystem_tradeoff` — interactive mission selector, subsystem priority allocation, budget feedback, and trade-off warning panel (teaching-grade; not a flight simulator).

Print priority cards: write low/medium/high for each subsystem under two different mission objectives; compare which subsystems shifted.

Interactive lab

Teaching-grade software activity slot — not a flight simulator or certified propagator.

Learner level

Choose your level

Mission type

Pick a mission objective

A CubeSat mission objective forces choices. The mission you pick changes which subsystems matter most and which trade-offs become real.

Subsystem priorities

Allocate your priority budget

Priority budget

0 / 10 used

10 points remaining.

Set each subsystem to Low, Medium, or High. Low costs 1 point, Medium costs 2, High costs 3. Total budget: 10.

Payload performance

Pressures: power, data rate, thermal, pointing accuracy

How capable the science / mission instrument must be — image resolution, sensor frequency, data rate, duty cycle.

Power reliability

Pressures: mass, volume, battery cycles, duty cycle limits

How tight the power margin must stay — solar generation vs loads, eclipse survival, safe-mode triggers.

Communication / downlink

Pressures: contact time, data rate, ground complexity

How much we must move data between spacecraft and ground — link budget assumptions, contact time use.

Pointing (ADCS)

ADCS / pointing

Pressures: pointing accuracy, development complexity, actuator power

How tightly the spacecraft must point at targets, antennas, or sun — affects payload, comms, and power.

Onboard computer / data

OBC / data handling

Pressures: development complexity, data rate, memory

How sophisticated onboard scheduling, storage, and autonomy must be to keep the mission usable.

Thermal safety

Pressures: mass, volume, duty cycle limits

Keeping components within temperature limits in vacuum + radiation environment.

Structure / mechanical

Pressures: mass, volume, classroom safety

Mechanical survival through launch loads, deployments, and thermal cycling.

Ground operations

Pressures: contact time, ops staffing, classroom safety / visibility

Operator effort, scheduling, and station availability needed to fly the mission day to day.

Trade-off warnings

What your priorities trigger

Local rules surface likely engineering pressures from your priority choices and mission. Use them to defend or revise your design.

No trade-off warnings yet. Pick a mission and adjust subsystem priorities to see how engineering pressures change.

Final design strategy

Choose one strategy

You cannot maximize everything. Commit to one direction and explain it.

Reflection

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: What is an engineering trade-off?

Quick check: For an Earth imaging mission, which subsystem usually becomes more important than for a beacon-only mission?

Quick check: What usually happens when a payload generates more data per orbit?

Quick check: Why can’t a small CubeSat maximize every subsystem at once?

Discussion prompt

Short answer (local only)

Write notes for yourself or your group. Nothing is submitted.

Short answer: Pick one trade-off your selected design forces (one subsystem went up, another went down) and explain why your strategy accepts it.

Checklist

Local checklist self-check

Use this to verify you covered key ideas. Nothing is submitted.

Checklist: Mission / Subsystem Trade-off readiness (self-check)

0 / 5 checked

I selected a mission type.I allocated subsystem priorities within the budget.I read at least one trade-off warning and could explain it.I selected one final design strategy.I captured an evidence summary (copy/export).

Rubric preview

Rubric (self-check / discussion guide)

Optional local self-check selections. This is not a gradebook and is not saved to an account.

Rubric preview (self-check): trade-off reasoning

Subsystem priorities reflect the chosen mission objective.

No selection

Beginning

Priorities feel random or all maxed out.

Developing

Most priorities reasonable; one or two not justified.

Proficient

Priorities clearly track mission objective; budget respected.

Extension

Discusses how a different mission would shift priorities.

At least one engineering trade-off is named with evidence.

No selection

Beginning

No trade-off named.

Developing

Trade-off named without evidence (e.g., warning ignored).

Proficient

Trade-off named, warning or constraint cited as evidence.

Extension

Explains how the trade-off would be verified or mitigated.

Local summary

Assessment summary (practice only)

Completion

0 / 7 sections complete

Quick checks

0 / 4 correct

Shown only to support self-check.

Checklist

0 / 5 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.

Mission brief

Observation (what you noticed)

Reflection (your explanation)

Selected inputs

Learner level: Middle school
Mission type: (not selected)
Mission objective example: (no mission selected)
Final design strategy: (not selected)

Generated outputs

Subsystem priorities: - Payload performance: — - Power reliability: — - Communication / downlink: — - ADCS / pointing: — - OBC / data handling: — - Thermal safety: — - Structure / mechanical: — - Ground operations: —
Priority budget: 0 / 10 used (10 remaining). Default budget for Middle school: 10.
Trade-off warnings: (no warnings triggered yet)
Strategy rationale: (no strategy selected)

Checklist

Evidence checklist

1/4 checked

Mission type selected
Subsystem priorities allocated (0 / 8)
Final design strategy chosen
Priority budget respected

Evidence artifact (local-only)

Captured: 2026-05-16T07:38:32.382Z · Level: Middle school · Track: orientation

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: Mission / Subsystem Trade-off
Track: orientation
Learner level: Middle school
Captured: 2026-05-16T07:38:32.382Z

Mission brief:
(not provided)

Selected inputs:
- Learner level: Middle school
- Mission type: (not selected)
- Mission objective example: (no mission selected)
- Final design strategy: (not selected)

Generated outputs:
- Subsystem priorities: - Payload performance: —
- Power reliability: —
- Communication / downlink: —
- ADCS / pointing: —
- OBC / data handling: —
- Thermal safety: —
- Structure / mechanical: —
- Ground operations: —
- Priority budget: 0 / 10 used (10 remaining). Default budget for Middle school: 10.
- Trade-off warnings: (no warnings triggered yet)
- Strategy rationale: (no strategy selected)

Checklist:
- [ ] Mission type selected
- [ ] Subsystem priorities allocated (0 / 8)
- [ ] Final design strategy chosen
- [x] Priority budget respected

Observations:
(not provided)

Reflection:
(not provided)

Model boundary note:
Teaching-grade browser activity. Not flight-certified analysis; no submission, no grade, no teacher visibility without manual sharing.

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).

Mission type and example objective recorded
Subsystem priorities and budget used / remaining
Trade-off warning explanation and selected design strategy
Reflection on the accepted trade-off
Self-check summary and copied evidence artifact text

Reflection

Choose level and mission type; allocate a limited subsystem priority budget; read trade-off warnings; pick a final design strategy; complete local self-check; capture evidence.

Responses are not persisted in this preview unless a specific activity component adds storage later.

Assessment / quick check

Justify one trade-off created by your mission objective: which subsystem went up, which went down, and why is that defensible?

Teacher notes

Run after Subsystem Detective to teach subsystem prioritization and how mission objectives drive engineering trade-offs.

Teacher guide

Run after Subsystem Detective

Open Teacher Mode →

Next steps

Next activity: Digital Twin Before Hardware →Prior: Subsystem Detective →Curriculum map →

20 min intro

Whole-class: pick one mission and walk through priority budget together.

45 min lesson

Pairs allocate priorities, read warnings, choose a strategy, complete self-check.

90 min lab

Compare two missions back-to-back, defend strategies, add evidence + rubric.

Facilitation prompts

Ask each pair: which subsystem dropped most when you chose your mission, and why is that OK?
Compare two teams that picked different strategies for the same mission — what does each accept?
Prompt a verification sentence: how would you know a high-priority subsystem actually delivered?

Expected evidence

Selected mission and budget summary (used / remaining)
Subsystem priorities and one trade-off explained with a warning
Final design strategy with a one-sentence reflection
Local self-check summary and copied evidence text

Misconceptions

More priorities set to high = a better mission.

High costs more from the budget and stresses other subsystems; better designs justify each high.

Mission type doesn’t change subsystem priorities.

Mission objective is the whole point — imaging vs beacon vs classroom kit changes priorities significantly.

Trade-off warnings mean the design is broken.

Warnings flag pressures; a defensible design names the warning and explains the chosen strategy.

Local-only: this activity does not submit work, assign grades, or provide teacher visibility into student evidence.

Next activity

Suggested progression from the mission learning path. Links avoid missing activity routes.

Previous: Subsystem Detective →

Next: Digital Twin Before Hardware →

Curriculum map →Learn hub →