eduKateSG · The Gold Standard · Junior College 2
Find your next learning step
Choose a JC2 Computing tutor by watching how they help a student reason about a solution. Look for clear specifications, understandable algorithms and deliberate testing. This guide focuses on H2 Computing support that develops the learner’s ability to explain and repair their own work.
The featured classroom photograph is illustrative. The original examples and learning guidance below should be used alongside the syllabus for your examination year and your college’s current instructions.
Complete chapter index
Understand and practise · Chapters 1–3
Apply and review · Chapters 4–6
Ask which examination year and syllabus the tutor uses. H2 Computing is syllabus 9569 for 2027. Resources and reference guidance should match the student’s actual course.
Bring a recent practical attempt and a written response. Ask the tutor to identify a priority and explain the proposed teaching step.
Check important qualification and experience claims directly. A demonstration using the student’s work complements recommendations and shows how the tutor communicates.
A useful tutor first clarifies the intended input and output. Then they distinguish a specification problem from an algorithm, implementation or testing problem.
Notice whether the learner is asked to predict behaviour. A small trace can reveal more about understanding than immediately running a large program.
Ask what independent task will test the lesson’s effect. The answer should include something the student will design or explain without a supplied solution.
Consider an original task: find the first position of a target in a list, using zero-based positions, or return −1 if it is absent. A linear search examines items from left to right and stops at the first match.
For [7, 4, 7] with target 7, the result is 0. A solution that keeps replacing the result on every match may return 2, which violates the requirement to find the first position.
For target 9, the result is −1. For an empty list, it is also −1 under this specification. These tests clarify the behaviour before code is written.
Ask the tutor to explain why stopping on the first match is correct and how the result would change if the task asked for every matching position. This reveals whether teaching develops reasoning beyond a memorised implementation.
Feedback should identify the first incorrect decision and explain a repair the learner can justify. A working final program is useful evidence alongside that explanation.
Ask how tests are chosen. Normal cases, boundary cases and cases designed to expose plausible faults each serve a purpose.
Look for a methodical debugging process: form a hypothesis, inspect relevant state and test the explanation. The student should increasingly choose the next step.
Confirm fees, duration, group size, materials, cancellation terms and communication directly. Discuss how practical work and written reasoning receive feedback.
Agree on independent practice between lessons. A manageable task with careful review can produce better evidence than a large unfinished project.
The tutor should work within the college’s current requirements and help the learner understand the permitted tools and reference guidance for the relevant examination year.
Use a fresh task on an agreed skill. Compare specification, design, correctness, explanation and test quality with the starting attempt.
If progress stalls, ask how the teaching plan will change in response to the observed difficulty. Revisiting a simpler representation may be useful.
The gold standard is a student who increasingly designs, tests and explains solutions without relying on the tutor to supply the algorithm or locate every fault.
Official sources
SEAB: 2027 H2 Computing 9569 syllabus
Checked on 18 October 2026. Teaching examples are original illustrations. Refer to SEAB for notices and the syllabus applying to your examination year.