Many students leave the IGCSE Computer Science Paper 2 exam convinced they answered the 15-mark scenario question correctly — only to be disappointed by their result.

This usually isn't because the code was "wrong".

It's because Paper 2 does not reward complete-looking solutions. It rewards meeting specific requirements in a clear, examinable way.

Mark schemes are not model answers

One of the biggest misunderstandings about Paper 2 is how mark schemes work.

Mark schemes are checklists, not ideal solutions. Examiners are not comparing your answer to a perfect version — they are checking whether each requirement in the question has been met somewhere in your response.

This is why two very different-looking answers can earn the same mark.

It is also why answers that "work" can still lose marks.

⚠️ Where marks are commonly lost

From analysing multiple exam series and reviewing student scripts, the same issues appear again and again:

  • Writing a full solution without clearly separating requirements
  • Missing a small condition embedded in the scenario text
  • Combining multiple requirements into one block of logic
  • Running out of time and leaving later logic unfinished
  • Being unsure whether partial credit will be awarded

These are process problems, not gaps in knowledge.

Correct logic can still be invisible to the examiner

In longer scenario questions, examiners read quickly.

If your logic is correct but buried inside a long loop or mixed with unrelated steps, it becomes difficult to award marks confidently.

This is why structure matters more than elegance.

A solution that clearly shows what requirement is being met will often score higher than a more compact or sophisticated one.

The role of comments in earning marks

Comments are not decoration in Paper 2 — they are signals.

When comments directly reflect the requirements in the question, they make it obvious to the examiner where marks should be awarded.

Even if the code beneath a comment is incomplete, the comment itself can demonstrate intent and earn method marks.

This is especially important under time pressure.

💡 The key takeaway

Paper 2 does not punish imperfect code.

It punishes unclear structure.

Students who understand this early stop worrying about whether their answer "looks right" and start focusing on whether each requirement has been clearly addressed. That shift alone often leads to a significant improvement in marks.

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:

  • r/IGCSE — exam strategy and revision discussions

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