FUTURE STUDIO · MISSION 06

SYSTEMS ENGINEERING

YEAR 8 · TERM 4 · WEEK 6

Prototype: Systems

Can you make it reliable, usable and testable?

RELIABILITY BAY: Your prototype works normally. That is not enough. A fictional monitoring system must keep logging for eight hours, stay within its error criterion and survive one sensor failure. Test the system, not just the feature.

ENTER MISSION →

MISSION DECKFUTURE STUDIO / WEEK 06SELECT A MODULE

01BRIEFMission

02LEARNIntel

03INVESTIGATEEvidence

04ENGLISHEvidence case

05DECIDEMake the call

06DATANumbers

07PROJECTBuild

08CHECK-INReflect

★GAMEReward

ACTIVE OBJECTIVERELIABILITY BAY: Your prototype works normally. That is not enough. A fictional monitoring system must keep logging for eight hours, stay within its error criterion and survive one sensor failure. Test the system, not just the feature.

WORLDFUTURE STUDIO

SEQUENCE01 / 08

REWARDGAME BREAK

Jump to a lesson part

READY?

Watch. Check the clues. Have a go.

Everything you need is on this page.

Start mission →

Need help getting started?

YOU NEED

Required: a device with this page open.
Optional: headphones for video or read-aloud.
Optional: pen + paper for rough working if that helps you think.
Only if you choose a physical build: simple low-cost craft/reuse materials. A digital sketch or model is always okay instead.

HOW TO DO IT

Read or listen to the Briefing + Learn.
Do the interactive mission.
Use facts from the reading and maths parts.
Make your choice and save your project step.
Play the weekly game. Finish Check-in.

WORK YOUR WAY

Short bursts are fine. Use Learning Tools for easier reading, read-aloud, less on screen, stronger contrast, no-rush and quieter-screen options.

If you get stuck, look at the example and try again.

PROJECT NOTE: Your project can stay digital. Physical making is optional unless you choose that format.

MISSION BRIEFING

RELIABILITY BAY: Your prototype works normally. That is not enough. A fictional monitoring system must keep logging for eight hours, stay within its error criterion and survive one sensor failure. Test the system, not just the feature.

✓Model a prototype as interacting subsystems with dependencies.

✓Use repeated test data and a mean rather than selecting only the best trial.

✓Distinguish redundancy from duplicating the same failure pathway.

✓Document one revision, its mechanism and its trade-off.

INTERACTIVE LEARN MODE

No passive video this week.

This mission is deliberately built around its simulator, investigation, decision room or prototype instead of an external video.

LEARN

SPEC → NORMAL TEST → FAULT TEST → DATA → REDESIGN

Use SPECIFICATION → NORMAL TEST → FAULT TEST → DATA → WEAK DEPENDENCY → REVISION → RETEST. Reliability asks how consistently the system meets criteria, including when something goes wrong. A backup is stronger when it is sufficiently independent from the component it protects. Keep failed trials in the evidence.

LEARNING BUILD

Learn it. See it. Try it.

Look at the example. Check another point of view. Then try the task.

Step 1: Choose a starting clue

WHAT YOU ALREADY KNOW

Reasoning lens:ASSUMPTION → EVIDENCE → CONSTRAINT → TRADE-OFF → TEST → DEFEND / REVISE

What do you already know?

English / communication:Technical specification, annotation and revision log.

Maths / data:Measurement, geometry, area/volume and test statistics.

Topic knowledge:Rigorous design process, integrated systems, criteria, constraints, reliability, redundancy and user testing.

This week’s first target:Model a prototype as interacting subsystems with dependencies.

Which clue is a good place to start?

Choose a source that can directly support part of the investigation. More than one source may be useful, but start with evidence that does not outrun its support.

Need more help? See the teaching

TEACH 1 · CORE MODEL

TEACH 2 · WHAT TO NOTICE

Model a prototype as interacting subsystems with dependencies.Use repeated test data and a mean rather than selecting only the best trial.

TEACH 3 · CONNECT + TRANSFER

Distinguish redundancy from duplicating the same failure pathway. Document one revision, its mechanism and its trade-off.

WORKED EXAMPLE · EVIDENCE

CRITERIA

The fictional unit must log for eight hours, keep sensor error within ±2% on average and tolerate one primary-sensor failure.

Reasoning: Start with exactly what the source establishes. Connect it to the relevant concept, then stop before the claim becomes broader than the evidence. Now compare it with CHERRY-PICK: Removing the 4% trial because it makes the average look worse hides relevant reliability evidence.

Why caution still matters:This item is weak evidence for a broad conclusion: its claim or implication reaches beyond what the available support can establish.

WORKED EXAMPLE · MATHS / DATA ROUTE

Four sensor-error trials are 1%, 2%, 1% and 4%. What is the mean error?

This week’s maths/data focus:Measurement, geometry, area/volume and test statistics.

Define the baseline, cost, time, proportion or criterion first. Calculate on the same basis, then test the result against the user need, constraint or success criterion.

WE DO · GUIDED PRACTICE

Which source needs the most caution before it is used to support a broad conclusion?

Choose any source whose claim outruns its support.

YOU TRY · INDEPENDENT PRACTICE

For Prototype: Systems, explain one core idea, connect it to one named source or observation and one quantitative/data point from this page, then state an alternative explanation, trade-off or limitation that a strong judgement must consider.

Write at least 30 words. Name the evidence or data you are using and keep the claim inside what it can support.

MISCONCEPTION CHECK

CHERRY-PICK:Removing the 4% trial because it makes the average look worse hides relevant reliability evidence.

This item is weak evidence for a broad conclusion: its claim or implication reaches beyond what the available support can establish.

HELP

Try: “The assumption is ___. Evidence ___ supports/challenges it. The main constraint/trade-off is ___. I would defend/revise ___ because ___.”

STRETCH · OPTIONAL

Build the strongest reasonable counter-argument or alternative explanation. Name one additional piece of evidence that could distinguish between the two positions.

FUTURE STUDIO · WEEK 6

PROTOTYPE: SYSTEMS · RELIABILITY BAY

⬡

A prototype is a system under test.

Hold your criteria steady, stress the design and improve the weakest dependency instead of changing the goal after the test.

FICTIONAL WATER-MONITORING UNITMust log data for 8 hours · stay within ±2% sensor error · survive one sensor failure

PRIMARY SENSOR FAILS. CHOOSE THE REDESIGN.

TEST STATISTICS

RELIABILITY PRINCIPLE

Design for the fault, calculate the evidence correctly, then keep failed trials visible.

INVESTIGATE + ENGLISH · EVIDENCE CASE

Reliable systems are tested when the easy path breaks

A prototype that succeeds once under perfect conditions may still be fragile. Reliability testing repeats the task, introduces realistic faults and records failures as evidence. In a monitoring system, a second sensor can improve resilience if it is independent enough to detect disagreement. Adding redundancy can also increase cost, complexity or power use, so the redesign still requires a trade-off.

BUILD THE EVIDENCE CASE · CLAIM → EVIDENCE → REASONING

MAKE THE CALL

Approve the prototype, revise it again or stop this design direction. Defend your decision using reliability evidence and one cost/complexity trade-off.

BUILD YOUR CASE CONCLUSION1. Make the call. 2. Use at least two relevant pieces of evidence. 3. Explain one limitation or uncertainty. 4. Finish with what can responsibly be concluded.Strong structure: My judgement is… The strongest evidence is… However, we still do not know… Therefore…

CASE CONCLUSION: Write 210–290 words as a systems test report. State the criteria, summarise normal and fault evidence, calculate or cite the mean, identify a weak dependency, describe one redesign and explain one new trade-off.

YOUR REASONING

0/210 words minimum for this writing mission.

CLAIMEVIDENCELIMITATIONCONCLUSION

MATHS + DATA LAB

Check the numbers.

HOW TO SUCCEEDRead the situation first. Estimate what a sensible answer should look like, choose an efficient calculation, then use the feedback to check your reasoning.For data questions, explain what the number shows — and what it does not prove.

Four sensor-error trials are 1%, 2%, 1% and 4%. What is the mean error?

Estimate first, then choose the answer.

MISSION 05 · MATHS + DATA LAB

DATA TRAINING

RATIO + RATE · YEAR 8 EXTENSION

6 PROBLEMS

QUICK METHODRATIO + RATE

Find one part or one unit first, then scale up.

GUIDED · Q01–Q03Use the quick method, then check the explanation.

Q01

A 2:3 ratio has 10 in the first part. What is the second part?

Q02

180 km in 3 hours is what average speed?

Q03

4 notebooks cost $12. Cost per notebook?

INDEPENDENT · Q04

Scale 1:100 means 2 cm represents…

INDEPENDENT · Q05

A recipe for 4 uses 300 g. For 8 people?

INDEPENDENT · Q06

Which is the better unit rate?

OPTIONAL CHALLENGE · OPEN RESPONSE

Two options have different starting fees and unit rates. Describe how you would find the break-even point.

0 words · optional

PROJECT HQ · PROJECT FILE 06

BUILD + TEST.

Start something real. Build an idea, test it, improve it, and share it. Make your move.

Start Something: choose an idea, name who it helps, make a small version, then test and improve it.

IDEA→RESEARCH→PLAN→BUILD→TEST→IMPROVE→PRESENT

WEEK 6 · BUILD + TEST · Test the capstone as a system under normal and fault conditions.

SYSTEM SPECIFICATION NORMAL + FAULT EVIDENCE RELIABILITY REVISION

This saves into your Term 4 Start Something project record as you type.

Project sharing will be optional. A future upload system must keep private submission separate from public-showcase/marketing permission.

CHECK-IN

What changed in your thinking?

One thing I learned or questioned

YEAR 8 · REMIX · TERM 4 / WEEK 6

REACTOR PINBALL: OVERDRIVE

Work both flippers, chase target sets and keep the reactor alive.

UPGRADED DIFFICULTYBEST SCORE SAVED

PLAY REACTOR PINBALL: OVERDRIVE

A remastered ICONIC GAMES favourite · phone + keyboard controls.