Break a problem into smaller jobs and explain how they connect.
DO NOW AND PRIOR LEARNING · 5 MINUTES
Ask: “What needs to happen to get ready for school?”
Students list possible jobs. Compare responses and identify broad parts, such as getting dressed, preparing food and packing a bag.
Explain that a familiar task can contain several smaller problems.
EXPLAIN AND MODEL · I DO · 10 MINUTES
Model breaking “get ready for school” into smaller jobs. Select “pack my bag” and break it down further:
Check the timetable.
Identify what is needed.
Collect the items.
Pack them.
Think aloud about each part’s result. Draw a dependency arrow to show that checking the timetable informs which books to collect.
Contrast “books”, an item, with “choose the books needed today”, a subproblem.
Key idea: Decomposition identifies the parts. Sequencing puts actions into an order.
GUIDED PRACTICE AND CHECK · WE DO · 10 MINUTES
Task 1: Breaking a problem into parts
Decompose brushing teeth together into three parts: preparation, cleaning and finishing.
Ask students to suggest smaller steps within each part. Identify what must happen first and what each part produces.
Check everyone’s understanding:
“Is toothpaste a subproblem?”
Expected response: No. “Prepare the toothbrush” is a job with a result.
Together, improve a vague instruction such as “clean your teeth”.
COLLABORATIVE PRACTICE · 15 MINUTES
Task 2: Sort and explain
In pairs, choose a familiar task, such as tying shoelaces, packing sports equipment or organising a desk.
Make a task map with at least three meaningful subproblems.
Label each part’s result.
Draw an arrow showing one dependency.
Write precise instructions for one selected part.
Swap with another pair. Follow or trace their instructions and identify an assumption or missing step.
Revise your instructions using the feedback.
Discuss: Why can an apparently simple task require many detailed steps?
COUNTING ALGORITHM AND FLOWCHART · 15 MINUTES
Task 3: Make a task map
Introduce the problem: “Say the numbers 1 to 5 in order.”
First, write a sequential algorithm:
Start → Say 1 → Say 2 → Say 3 → Say 4 → Say 5 → Stop
Then introduce a loop that reuses instructions:
Start.
Set number to 0.
Ask: “Is number greater than 4?”
If Yes, stop.
If No, add 1 to number, say number, then return to the question.
Translate the algorithm into a flowchart using:
Ovals for Start and Stop.
Rectangles for setting or changing the number.
Parallelograms for saying the number.
A diamond for the decision, with arrows labelled Yes and No.
Students trace both charts and record the numbers said. Check that both say 1, 2, 3, 4, 5, without saying 0 or 6.
Key idea: Decomposition helps identify the jobs: initialise, check, update and output. A flowchart shows how the algorithm connects those jobs.
INDEPENDENT EVIDENCE AND PLENARY · 5 MINUTES
Students independently:
Name two subproblems from their chosen task.
Give the result of one.
Explain one dependency.
Complete: “Decomposition helps because…”
Collect the task map and counting trace.
Next lesson: Apply these ideas to instructions for making a sandwich.
Lesson 2 · Applying decomposition — Make a sandwich
Break a task into smaller jobs, write precise instructions, and improve them through testing.
DO NOW AND PRIOR LEARNING · 5 MINUTES
Ask students to answer without looking at their notes:
What does decomposition mean?
What are three smaller jobs involved in making a sandwich?
Which jobs must happen in a particular order? Why?
Compare responses. Check that students identify jobs, such as preparing the bread, rather than simply listing ingredients.
EXPLAIN AND MODEL · I DO · 10 MINUTES
Show the ingredients and equipment, or paper sandwich props.
In pairs, students write a short, numbered set of instructions for making a sandwich. Ask them to include one clear action per step.
Choose one example and follow it exactly as written, within the agreed food-handling and equipment routines. Students watch for missing details or unexpected results.
Think aloud about the smaller jobs:
Prepare the bread.
Add the filling.
Assemble the sandwich.
Identify each job’s output and explain how another job uses it.
Key idea: Decomposition identifies smaller jobs. An algorithm gives precise instructions for carrying them out.
GUIDED PRACTICE AND CHECK · WE DO · 10 MINUTES
Ask: “Which instruction caused a problem, and why?”
Together, identify a missing, unclear or incorrectly ordered step.
Rewrite the instruction.
Ask students to predict what will happen.
Test the revised instruction.
Check whether the change worked.
Students review and improve their own instructions before another demonstration.
Key idea: Debugging means finding and fixing errors. Retesting checks whether the fix worked.
COLLABORATIVE PRACTICE · 18 MINUTES
Pairs join another pair. Use paper props or approved ingredients, following the teacher’s food-handling and equipment instructions.
Group your sandwich instructions into smaller jobs.
Name the output of each job.
Swap instructions with the other pair.
Take turns reading the instructions, making the sandwich and observing.
Follow the instructions as written. Pause if a step is unclear and record the problem.
Improve the instruction and test it again.
Record your findings:
Original instruction → Problem observed → Improved instruction → Retest result
Discuss: Which jobs depend on an output from an earlier job?
INDEPENDENT EVIDENCE · 12 MINUTES
Students work independently.
Draw a task map showing three or four smaller jobs involved in making the sandwich.
Label each job’s output.
Draw arrows showing dependencies between jobs.
Choose one job and write precise instructions for it.
Explain what would happen if one required output was missing.
Use the sentence starter:
“_____ depends on _____ because _____.”
Key idea: A useful task map shows both the smaller jobs and how they connect.
PLENARY · 5 MINUTES
Students complete these statements independently:
Decomposition helped us by…
One unclear instruction was…
We improved it by…
Our retest showed…
Invite two students to share their explanations. Ask the class to check whether each explanation includes evidence from a test.
Collect: Original and improved instructions, test record, individual task map and exit responses.
60 minutes
Use clear, ordered instructions to sort cards, trace each pass, and record evidence about how the algorithm works.
Year 9 curriculum knowledge K1
Computational thinking uses decomposition, abstraction, pattern recognition, algorithms, and evaluation to analyse problems for digital solutions.
Year 9 curriculum practice P1
Explain simple problems by identifying purpose, users, inputs, outputs, constraints, context, and key steps.
Knowledge focus
An algorithm uses clear, ordered steps to solve a problem. Different algorithms can produce the same sorted output. Selection sort repeatedly selects the smallest remaining item and places it at the sorted boundary.
Practice and evidence
Represent and trace a precise sorting algorithm using physical cards. Evidence: an individual selection-sort trace and a paired comparison log retained for Lesson 6.
Learning intentions
Explain what an algorithm is.
Follow and trace selection sort accurately.
Identify the sorted and unsorted regions.
Record comparisons and actual swaps consistently.
Resources
Number cards 1–6 for each pair; a boundary marker such as a ruler or strip of paper; a small “smallest so far” marker; timers; recording sheets.
Students answer independently before reviewing answers:
How did recognising a pattern help you adapt a counting method?
Write three smaller jobs involved in making toast. Which must happen in a particular order?
Describe one error in a previous set of instructions and explain how you corrected it.
Briefly connect their answers:
Decomposition helps us identify the smaller jobs. Pattern recognition helps us notice repeated actions. Today, we will organise repeated actions into a precise algorithm and check that it works.
An algorithm is a set of clear, ordered steps for solving a problem. Someone else should be able to follow the steps without guessing.
Recall that more than one valid order of toast-making instructions can achieve the same result, provided necessary dependencies are respected. Similarly, different sorting algorithms can produce the same ordered list.
Give pairs six shuffled cards and one minute to arrange them from smallest to largest. Ask:
What did you do first?
Could another pair follow your explanation exactly?
Did everyone use the same method?
Explain that they will now follow one specific algorithm: selection sort.
Display and model these instructions:
Lay out the cards in a row. Place the boundary marker before the first card. All cards are initially unsorted.
Mark the first card in the unsorted region as the smallest so far.
Compare each remaining unsorted card with the smallest so far, moving from left to right.
If a card is smaller, move the smallest-so-far marker to it.
After checking the whole unsorted region, swap the selected smallest card with the first unsorted card. If it is already there, leave it in place.
Move the boundary one position to the right. The card just placed is now in the sorted region.
Repeat until only one unsorted card remains. It is already in its final position.
Counting rules
Count one comparison whenever you compare a new card’s value with the smallest value found so far.
Count one swap when two cards exchange positions.
Do not count selecting the first candidate as a comparison.
Do not count a card staying in its own position as a swap.
Use:
4, 2, 6, 1, 5, 3
Think aloud:
“The first unsorted card is 4, so that is my smallest so far. Is 2 smaller than 4? Yes: my smallest becomes 2. Is 6 smaller than 2? No. Is 1 smaller than 2? Yes: my smallest becomes 1. Is 5 smaller than 1? No. Is 3 smaller than 1? No.”
The smallest card is 1. Swap it with 4, then move the boundary:
1 | 2, 6, 4, 5, 3
Record 5 comparisons and 1 swap.
Emphasise:
We check the entire unsorted region before swapping. Selection sort does not repeatedly swap neighbouring cards.
Every student writes an answer:
Why is the smallest selected card in its final position after this pass?
Expected reasoning:
We compared it with every other card in the unsorted region. None is smaller, so it belongs in the first available position when sorting from smallest to largest.
Also ask students to identify:
The sorted region.
The unsorted region.
Whether the cards in the unsorted region must already be in order.
Inspect all responses. Re-model any uncertainty about checking every remaining card before selecting the final minimum.
Continue from:
1 | 2, 6, 4, 5, 3
Students predict and direct the second pass.
Ask:
Which card starts as the smallest so far?
Which cards must we compare with it?
How many comparisons will this pass require?
Does a swap need to happen?
The result is:
1, 2 | 6, 4, 5, 3
Record 4 comparisons and 0 swaps. Explain that the boundary still moves when the smallest card is already correctly placed.
Complete this checklist together:
Feature
Our sorting problem
Purpose
Arrange numbers from smallest to largest.
User
A student following the sorting instructions.
Input
Six number cards in a given order.
Output
The same six cards in ascending order.
Constraint
Follow selection sort, checking the whole unsorted region before placing its smallest card.
Context
A physical model of how a computer can sort data.
Key steps
Select a candidate, compare remaining values, swap if needed, move the boundary, repeat.
Pairs reset their cards to:
4, 2, 6, 1, 5, 3
Assign roles:
Operator: follows the procedure and moves the cards and markers.
Observer: checks the procedure and records comparisons, swaps, and the row after each pass.
Swap roles after each pass.
Start timing when the first pass begins. Stop when the cards are sorted. Prioritise following the algorithm accurately.
Complete the trace:
Pass
Selected smallest value
Row after the pass, showing the boundary
Comparisons
Actual swaps
1
2
3
4
5
Total
Repeat the same procedure with:
1, 2, 3, 4, 5, 6
Before starting, predict:
Will this version of selection sort still make comparisons?
Will it make any swaps?
Record both runs:
Starting order
Total comparisons
Total swaps
Time
4, 2, 6, 1, 5, 3
1, 2, 3, 4, 5, 6
Discuss:
What stayed the same? What changed? Use your recorded evidence.
Explain that physical timing is affected by handling cards, recording, and familiarity. One faster run alone does not establish that a method is more efficient.
Each student independently traces one complete pass on:
3, 5, 2, 4, 1, 6
Record:
Each comparison and any change to the smallest so far.
The selected smallest value.
The row after the pass, with the boundary.
The number of comparisons and actual swaps.
Keep individual traces and paired logs for Lesson 6.
Students answer independently:
Why is the smallest selected card in its final position after this pass?
Then complete:
“One instruction that makes selection sort precise is __________.”
Collect responses and use them to identify what needs revisiting before Lesson 6.
Responsive and adaptive teaching
Provide a numbered procedure, a physical boundary marker, and a “smallest so far” marker. If students swap too early or only compare neighbouring cards, re-model one pass and ask them to explain when a swap is allowed. Follow feedback with a fresh individual attempt.
For students needing a smaller starting task, use four cards before returning to six. Extend secure students by asking them to explain why this version still makes comparisons on already sorted input, or to test repeated values such as 3, 1, 3, 2, 1, 2.
Science of learning
Retrieve prior knowledge before reviewing it. Model explicitly with a think-aloud, check every student’s understanding, and gradually remove prompts. Give specific feedback followed by a fresh attempt. Revisit decomposition, pattern recognition, and error correction during the sorting tasks.
Potential DMI connection
Retain trace records and comparison logs as evidence for evaluating the method and explaining later improvements or choices.
Teacher reference
For 4, 2, 6, 1, 5, 3, the completed passes are:
Pass
Row after the pass
Comparisons
Swaps
1
1 | 2, 6, 4, 5, 3
5
1
2
1, 2 | 6, 4, 5, 3
4
0
3
1, 2, 3 | 4, 5, 6
3
1
4
1, 2, 3, 4 | 5, 6
2
0
5
1, 2, 3, 4, 5 | 6
1
0
Total
15
2
Already sorted input requires 15 comparisons and 0 swaps using this procedure.
The independent first pass produces 1 | 5, 2, 4, 3, 6, with 5 comparisons and 1 swap.
Unit plan Year 9 • Digital Technologies and Computer Science • 12 weeks
Rationale and local context
How can a new student find a school destination from a tiny digital sign? The class begins by breaking down problems and testing instructions. Students then learn how bits can represent a number, a character or a pixel, before sending a sign that another student can reconstruct and interpret.
Given design brief
Design a 4 × 4 wayfinding icon and a short text label for a visitor. Send a partner the label bytes, the pixel data and all decoding instructions. The reader must reconstruct all 16 pixels and identify the intended meaning without hints. Keep the reader’s first attempt and use it to improve the sign.
Links to prior and future learning
Entry points to check
Year 8 experience with instructions, simple maps, whole-number place value and grid coordinates. Check rather than assume prior access to coding.
Year 10: trace longer algorithms, evaluate their behaviour on varied inputs and introduce hexadecimal notation as a further way to write RGB channel values.
Delivery and resources
Each week has one 60-minute core lesson and one 60-minute application lesson for a two-period timetable. In a one-period course teach the core lesson each week. Weeks 1–11 introduce the specified concepts; week 12 brings them together. No programming account is required.
Prepare number cards, paper sandwich pieces, square grids, mini-whiteboards, place-value cards, coloured pencils and a projector. Use an RGB slider or colour picker showing decimal values. Paper grids and labelled channel cards work offline.
The unit has a useful progression:
Lesson 1-5: Decomposition → Abstraction → Pattern Recognition → Algorithms → Evaluation
Lessons 6-11: Binary → Numbers → Text → Images
That means the first five lessons establish how computer scientists approach problems, while the final six establish how computers represent information.
For the data-representation section, make this one idea recur constantly:
So the same binary pattern might represent a number, a character, a pixel value, or something else depending on the agreed representation. That gives the binary lessons a purpose rather than binary conversion being just an isolated mathematical exercise.
For the explicit curriculum knowledge, I would put the boxed terms on the board and deliberately use them in student explanations: Decomposition, Abstraction, Pattern Recognition, Algorithms, Evaluation, Binary Representation, Character Encoding, and Image Representation.
TECHQUITY / YEAR 9 COMPUTER SCIENCE
Knowledge and practices
The statements below unpack the supplied Year 9 content for this unit. These are teacher planning statements rather than verbatim curriculum wording.
TECHQUITY / YEAR 9 COMPUTER SCIENCE
Knowledge and practices
The statements below unpack the supplied Year 9 content for this unit. These are teacher planning statements rather than verbatim curriculum wording.
Subject knowledge
A bit string has no single inherent meaning. For example, 01000001 can mean 65, the ASCII character A, or eight monochrome pixels under an agreed key. Decimal RGB describes amounts of emitted light. A colour key maps a short pixel code to an RGB triple; storing palette indexes is different from storing three full channels for every pixel.
TECHQUITY / YEAR 9 COMPUTER SCIENCE
Science of learning in the sequence
Start from memory before revealing the answer. Return to an older idea as well as the previous lesson: week 8 reuses binary conversion; week 10 revisits decoding conventions; week 12 asks for all three interpretations of one byte. Use a worked example, complete a second together, then ask for an independent response. Use errors to choose the next example
TECHQUITY / YEAR 9 COMPUTER SCIENCE
Connections and access
Mathematics contributes place value and grid coordinates; English contributes precise procedural writing. Local place names give encoding a real consequence. Ask a knowledgeable speaker or use the school’s established spelling before publishing a label. Offer tactile tokens, large grids, oral explanations and written colour-channel labels. Rotate encoder and decoder roles so each learner practises both.
Use DMI where a design decision depends on the intended user. A correctly encoded sign can still be hard to recognise. That difference gives students a reason to test and revise it.
TECHQUITY / YEAR 9 COMPUTER SCIENCE
Using the evidence
Record separately whether each student can explain the knowledge and demonstrate the practice independently, with a prompt, or not yet. A correct group product alone is insufficient. Reteach the first failed step, then check a fresh example.
Teacher reflection
Which errors persisted after a week? Which support could be removed? Did students explain both technical correctness and user understanding? Record one example and one change for the next class.
Teacher references: Tāhūrangi, Technology Years 0–10 (2026); Australian Education Research Organisation, Spacing and retrieval practice and Explicit instruction practice guides. Visual styling follows the Techquity Hub’s purple, Righteous headings and Arial body type.
Individual transfer check