IGCSE Computer Science: What the Exam Papers Really Reward in 2023+

A comprehensive breakdown of every Paper 1 question from 2017 to 2023, organised by topic. Use this to identify patterns, focus your revision, and find specific past paper questions to practise.

Quick Navigation

Other Sections

Most Frequent Topics

Based on analysis of all papers from 2017–2023, these are the most frequently tested concepts:

Data Representation

Data Compression

Hardware and Software

Computer Architecture

Networks

Communication and Internet Technologies

Programming

Logic Gates

Security

Operating Systems

Database Systems

Note: Query tables (QBE) are no longer assessed since 2021. Only SQL is now tested.

How to Use This Resource

1. Identify weak topics – Use the frequency data above to prioritise high-frequency topics
2. Find specific questions – Use the tables to locate past paper questions on topics you want to practise
3. Track patterns – Note which question types appear regularly (e.g., binary conversions, firewall functions)
4. Practise systematically – Work through questions topic-by-topic rather than paper-by-paper

External Resources

• r/IGCSE community discussions ↗
• Isaac Computer Science – problem-solving practice ↗
• Official CAIE 0478 syllabus page ↗

Understanding Paper 2: Why Correct Code Still Loses Marks

For many students, Paper 2 feels unpredictable.

You can understand programming concepts, write working code in class, and still lose a surprising number of marks in the exam. That isn't because your logic is wrong — it's because Paper 2 does not reward programming skill in the way most students expect.

After analysing CAIE IGCSE Computer Science Paper 2 mark schemes from 2017 to 2023, a clear pattern emerges.

Paper 2 rewards approach, structure, and visibility of intent far more than syntactic accuracy or "clever" solutions.

How Paper 2 Marks Are Actually Awarded

Across multiple years and variants, the same marking behaviour appears again and again:

• Marks are awarded per requirement, not per overall solution
• Each bullet point or instruction in the question maps directly to marks
• Method marks are common, even when later logic is incomplete
• Variable names, language choice, and formatting are flexible
• Syntax errors are often ignored if intent is clear

In short: examiners are checking boxes, not running your code.

If a requirement is not clearly met somewhere on the page, it usually earns zero — even if your overall solution would "work".

Why Students Lose Marks on Paper 2

The most common error is trying to solve the entire problem in one pass.

Students read the scenario, start writing pseudocode immediately, and aim for a complete solution as quickly as possible. This feels logical — but it hides evidence from the examiner.

When everything is written as one block:

• It's hard to see which requirement is being met
• Missing one step can collapse multiple marks
• Partial understanding is not visible
• Running out of time costs everything at once

This is why two students with similar understanding can receive very different marks.

An Examiner-Friendly Approach to Paper 2 Scenarios

High-scoring scripts almost always follow the same pattern:

1. Extract the requirements first
   The question already lists what the program must do. These are usually written in the order the mark scheme expects.
2. Turn each requirement into a short comment
   Each comment acts as a signpost for the examiner.
3. Write the solution directly under each comment
   One requirement at a time. One mark opportunity at a time.

This approach does three things:

• Makes your intent obvious
• Prevents drifting away from the question
• Protects marks if you run out of time

Even unfinished answers can score well if the structure is clear.

Why "correct code" still loses marks

Paper 2 is not testing whether you can program a working system.

It is testing whether you can:

• Interpret a scenario
• Translate requirements into algorithmic steps
• Show those steps clearly and explicitly

A fully working solution that skips a stated requirement will lose marks. A partially completed solution that clearly addresses each requirement can still score strongly.

This is why self-marking is unreliable — students judge correctness, while examiners judge evidence.

A better way to practise Paper 2

The most effective preparation in the final weeks is not doing more questions, but practising deliberately:

• Redo past Paper 2 scenario questions
• Compare your answer directly to the mark scheme
• Check whether each requirement is clearly visible
• Ask yourself: "Would an examiner be able to award marks quickly here?"

If you want structured practice with examiner-style feedback, tools that assess answers requirement-by-requirement can help highlight where marks are actually being lost. Used properly, they can reinforce the mindset Paper 2 demands rather than encouraging guesswork.

Final takeaway

Paper 2 is predictable once you stop treating it like a programming test.

It rewards:

• Requirement-driven thinking
• Clear structure
• Visible intent

If you change how you approach the question, the marks usually follow.

This mindset shift alone is often worth more than learning new syntax in the final weeks before the exam.