Did you know? A good IF–ELSE condition does more than work for the example shown in class. Its branches must be mutually clear at the boundaries and collectively cover every valid input the program is expected to handle.

G2 Computing tuition can help by teaching a child to design the decision table before assembling blocks. If the cases are unclear in plain language, adding colourful programming blocks usually hides the gap rather than fixing it.

Try this now: ask your child to classify four scores—49, 50, 74 and 75—under a rule where 75 and above is “Distinction”, 50 to 74 is “Pass”, and below 50 is “Support”. If any boundary is placed twice or not placed at all, repair the conditions before coding.

Plan the cases before arranging blocks

A decision table turns an invisible logic problem into something inspectable. Each row describes one case, its condition and its output.

Case	Condition	Output
High range	score ≥ 75	Distinction
Middle range	score ≥ 50 after the first test is false	Pass
Remaining valid scores	ELSE	Support

Order matters. Testing “score ≥ 50” first would capture 75 as well, preventing the distinction branch from running in an IF–ELSE chain. Start with the most restrictive upper category, then let ELSE collect the genuine remainder.

Back to contents

Find the exact logic gap

• Boundary gap: the child cannot decide whether 50 belongs above or below the cut-off.
• Order gap: a broad condition appears before a narrower one and captures too many inputs.
• Coverage gap: a possible input reaches no branch because the conditions leave a hole.
• Overlap gap: two independent IF blocks both run when only one outcome was intended.
• State gap: the condition is correct, but the variable was not initialised or updated as expected.

A useful diagnostic asks the learner to predict outputs for values just below, exactly at and just above every threshold. That separates a logic problem from a block-placement or variable problem.

Back to contents

Build and test a three-way decision

In plain-language pseudocode, the score classifier is:

IF score >= 75
  output "Distinction"
ELSE
  IF score >= 50
    output "Pass"
  ELSE
    output "Support"

The second IF is reached only when the first condition is false, so it does not need to repeat “score < 75”. This is one level of nesting. The final ELSE covers every remaining valid score.

Test value	Expected route	Why it matters
49	Support	Just below the pass boundary
50	Pass	Exactly on the pass boundary
74	Pass	Just below distinction
75	Distinction	Exactly on the distinction boundary

These are boundary tests, not random guesses. A learner should also add one ordinary value from each range, such as 30, 62 and 88, then compare actual outputs with the table.

Back to contents

Use AND, OR and NOT deliberately

Suppose a game unlocks a level only when points are at least 100 and the key has been collected. AND is appropriate because both conditions must be true. If the level can be opened by a key or a passcode, OR is appropriate because either route is sufficient. NOT reverses a Boolean state, such as “not gameOver”.

Tuition should make the truth conditions visible with short tables and predictions before blocks are assembled. In a small group of three, if that is the actual class arrangement, one learner can state the cases, one can build the blocks, and one can test the boundaries. They should rotate and then complete an unseen condition independently. Parents should confirm that the provider actually teaches G2 Computing.

For school practical work and examinations, the child must create and submit their own files under school or examination supervision. Tuition may teach transferable planning, debugging and checking habits, but should not produce assessed artefacts on the student’s behalf.

Back to contents

Align practice with K237 for 2027

The official 2027 SEAB G2 Computing syllabus K237 includes IF and IF–ELSE conditional instructions, up to one level of nested IFs, together with logical operators AND, OR and NOT and relational operators >, < and =. It also requires learners to identify and correct program errors.

K237 is new for first examination in 2027. Paper 1 is a 1 hour 30 minute e-examination worth 50%; Paper 2 is a 2 hour 15 minute lab-based examination worth 50%, with practical tasks in media software, spreadsheets and programming. All questions are compulsory.

G2 is the subject level, not a Posting Group. Computing is not offered by every school or taken by every G2 learner, so check the school’s subject offering, the child’s actual combination and the approved software used for the course.

Back to contents

Check independent transfer

• Your child writes the cases in plain language before coding.
• They identify every threshold and test values on both sides.
• They explain why branch order changes the result.
• They choose AND, OR or NOT from meaning, not appearance.
• They compare expected and actual output and locate the first divergence.

Use one unfamiliar decision each week: ticket category, game access, temperature alert or delivery fee. Ask for the decision table, pseudocode, boundary values and actual outputs. A working program with an explained test set is stronger evidence than blocks that happen to work for one input.

Useful next reading: tracing a program without guessing, stopping invalid spreadsheet data, and the MOE and SEAB syllabus guide directory.

Back to contents