Yes—good G3 Computing tuition can make this distinction wonderfully concrete: a valid input satisfies the program’s input rules, while a correct output satisfies what the problem says the program must produce. One is about what may enter; the other is about what should come out.
If your child mixes them up, the immediate next step is to choose one short program and write two separate sentences before coding: “The input is valid when …” and “The output is correct when …”. That tiny separation often reveals whether the real gap is requirements, validation, program logic or testing.
Did you know? A program can accept perfectly valid data and still produce a wrong answer. That is why repeating definitions is not enough; tuition should help a student trace the whole journey from requirement to test result.
A quick route through this guide
First diagnose which sentence breaks down
Ask your child to explain an error without touching the keyboard. If the explanation is “the user typed something bad”, ask which stated rule it breaks. If the explanation is “the answer is wrong”, ask what the expected output should have been. A student who cannot answer the first question needs help expressing an input contract; a student who cannot answer the second needs help deriving an expected result. A student who can answer both but cannot locate the fault needs tracing and debugging practice.
This diagnosis matters because more coding is not always the cure. Sometimes the missing skill is reading the requirement precisely.
Tuition can teach two checkpoints, not one vague “check”
- Input checkpoint: state type, range, presence, length, format or existence rules.
- Output checkpoint: calculate or reason out the expected result independently of the program.
- Run and compare: decide whether rejection, acceptance and output are each correct.
- Name the fault: requirement, validation rule, test data, logic or output formatting.
In a three-student lesson, if that format is actually offered for the subject, one learner can propose an input, another can act as the program, and the third can challenge the expected output. The value is the explanation loop—not the group size by itself.
Example: a valid age can still lead to the wrong fee
Suppose a school activity accepts ages 13 to 17 and charges $8 for students aged 15 and below, otherwise $10. The input 15 is valid because it is within the allowed range. The correct output is $8. If the program prints $10 because its condition uses age < 15, validation succeeded but the output is incorrect. If the input is 19, the program should reject or request input again before any fee is calculated.
A tutor can vary only one thing at a time: try 12, 13, 15, 16, 17 and 18; predict acceptance first; then predict the fee. This creates boundary awareness without blurring validation and logic.
How this aligns with G3 Computing K349
The official 2027 G3 Computing syllabus (K349) asks students to specify inputs and requirements for valid inputs, outputs and requirements for correct outputs. It also includes justifying validation, applying length, range, presence, format, existence and check-digit checks, and designing normal, error and boundary test cases. Paper 1 is a two-hour written paper worth 60%; Paper 2 is a two-hour-30-minute lab examination worth 40%.
Posting Group is not the same thing as subject level. Confirm the level your child actually takes and use the year-specific syllabus; the SEAB 2027 G3 school-candidate directory is the reliable starting point.
What independent progress should look like
- Your child states the input rule before seeing sample data.
- They predict the expected output without relying on the program’s result.
- They include a boundary case and an invalid case for a reason.
- They can say, “The input is valid, but the output is wrong because …”.
Tuition has done its job when the student can design this evidence alone, not merely recognise a tutor’s completed table. For the next step, use the companion guide on choosing normal, boundary and invalid test data, or return to the series directory.

