Year 9 computing: tackle trace tables with confidence this October

By October, Year 9 computing lessons may be moving from writing simple programs towards explaining exactly what an algorithm does. If trace tables feature in your child’s autumn work, they offer a useful way to practise careful reasoning before an assessment.

A trace table records how values change as instructions run. Pupils can understand the overall purpose of a program yet still lose track of an individual step. The answer is not to guess the final result more quickly. It is to make each change visible.

1. Start with three instructions and two variables

Begin without loops or complicated conditions. Ask your child to follow these instructions in order: set score to 4, set bonus to 3, then set score to score + bonus.

Make two columns labelled score and bonus. Record the starting values, then the change that makes score equal 7. Explain that a variable stores a value, and an assignment can replace that value.

Ask: “When the score changes, does the bonus change too?” It stays at 3 because no instruction replaces it. This small distinction helps prevent a common mistake: changing several values when only one assignment has happened.

Use the notation taught at school. Some classes use arrows for assignment, while programming languages may use an equals sign.

2. Give each loop repetition its own space

Once straight sequences feel manageable, introduce a short counting loop. Set total to 0. For each value of number from 1 to 3 inclusive, add number to total. After the loop, output total.

A simple practice table looks like this:

The output is 6. Ask your child to point to the instruction being executed before writing each change. This slows down the moment where pupils sometimes skip a repetition or add the wrong number.

For school questions, follow the supplied table layout. Teachers may expect rows at different points in the algorithm, so the example above is a practice structure rather than a universal format.

3. Test the exact boundary of a condition

Conditions need precise checking. Try this rule: if score > 10, output “Target passed”; otherwise, output “Keep practising”.

Ask your child to test scores of 9, 10 and 11. A score of 10 still produces “Keep practising” because greater than does not include equality. Then change the condition to score >= 10 and ask which result changes.

Encourage your child to write “true” or “false” beside each condition before following its branch. With a loop, check the stopping rule just as carefully. Do not assume every loop includes its final stated number: the exact instructions matter.

4. Build a short October checking routine

Before half term, try two ten minute sessions each week, using examples from current lessons. In the first session, complete one trace with support. In the second, attempt a similar question independently.

Check the first point where the answer differs, rather than replacing the whole table. Was a value copied incorrectly, a condition misread or an instruction skipped? Set the next practice task around that specific difficulty.

If repeated confusion is making computing stressful, discuss it with the teacher. For tailored one to one support, take the free 2 minute quiz to explore help suited to your child’s needs.