In 2022, Cambridge removed the pre-release material from Paper 2. Students now face an unseen 15-mark scenario question — and they have roughly 30 minutes to solve it.

What changed

Before 2022, students could prepare for Paper 2 by practising with known pre-release scenarios. Now, the entire paper tests how well students can read, interpret, and code a solution to a problem they've never seen.

The May 2025 syllabus update added further constraints: solutions must now adhere more strictly to the chosen language. Examiners are explicitly told to penalise "Java-ish" or "Python-ish" pseudocode — hybrid answers that mix syntax from different languages.

This puts real pressure on students, particularly those writing in Java, where even simple solutions can become long-winded and eat into exam time.

What we found in the classroom

After analysing mark schemes and trialling different approaches under timed conditions with my classes, we arrived at a clear conclusion: writing all answers in pseudocode is the fastest and most reliable strategy for completing the 15-marker in time.

We experimented with modular solutions — using function calls and stubbing out each function to meet the requirements. On paper, it seemed elegant. In practice, it created too much code and took too long. Writing out function signatures, parameters, and return types consumed valuable minutes.

The approach that worked best was simpler: code each requirement in turn, in order, with no function stubbing. Just straightforward iterations and conditionals — one requirement at a time.

💡 The key pattern

Across multiple years and exam sessions, the same pattern appears:

  • Marks are awarded per requirement, not per line of code
  • The scenario is structured so each requirement appears in the order you should code it — one requirement at a time
  • Method marks are available even when solutions are incomplete
Paper 2 rewards approach more than syntax.

⚠️ Where marks are usually lost

Students commonly lose marks by:

  • Writing a complete solution without clearly separating requirements
  • Missing one small condition hidden in the scenario text
  • Running out of time and leaving logic unfinished
  • Being unsure whether their answer would earn partial credit

These are process problems, not knowledge gaps.

A more reliable way to approach scenario questions

A consistent, examiner-friendly approach is:

  1. Read the scenario once to understand the context
  2. Re-read and extract each requirement in order
  3. Write each requirement as a short comment
  4. Write the pseudocode directly under that comment
  5. Move on only when that requirement is satisfied

This mirrors how mark schemes are structured and makes your intent clear to the examiner.

Even if time runs out, clear comments can still earn method marks.

Why self-marking is difficult

Many students ask:

"How do I know what score I would actually get?"

Mark schemes are not model answers — they are checklists. Comparing your work to them requires experience, especially for partial credit.

This is why structured practice — with feedback — matters more than volume alone.

Further reading and resources

Further discussion

This analysis is based on recurring questions and exam-preparation discussions from students studying IGCSE Computer Science (0478), particularly around the Paper 2 scenario question.

Key ideas from this article have been explored and refined through public student discussions, including those on:

These discussions help highlight common misconceptions and patterns in how marks are awarded across exam series.