Skip to content
Marlbridge

Exam Preparation

OxfordAQA International GCSE Computer Science: The Pre-Released Skeleton Program and Paper 2

How to prepare for OxfordAQA International GCSE Computer Science 9210's on-screen Paper 1 built on a pre-released skeleton program, the May/June-only series change, and a worked incremental-coding routine.

Level
IGCSE
Topic
Exam preparation – Papers 1 and 2
Updated

Aligned to OxfordAQA IGCSE Computer Science (9210), First teaching 2017, first examined 2019. Official specification .

Syllabus page (what it covers and how it is assessed): OxfordAQA IGCSE Computer Science.

Found an error? Report a correction.

Need help with this topic? Request a free trial class for IGCSE Computer Science (9210).

OxfordAQA International GCSE Computer Science (9210) is linear and untiered, with no coursework. Both papers run 2 hours, carry 80 marks and are worth 50%. Paper 1 (Programming) is an on-screen examination set against a pre-released skeleton program, available in a choice of C#, Python 3 or Visual Basic. Paper 2 (Concepts and Principles of Computer Science) is a written paper. Note also that examinations for this specification now take place in May/June only, with no November series from 2026. These notes complement the site’s guides to Algorithms and Programming Fundamentals.

The pre-released skeleton program is the single biggest preparation opportunity

Paper 1 is built on code you are given before the exam. A candidate who opens that code for the first time in the examination room has given away the whole advantage the design intends. Exam-preparation priority: work with the skeleton program extensively beforehand – read every function, run it, trace what each part does, deliberately break it and fix it, and add small features to it. Familiarity with its structure is what makes the exam’s modifications quick rather than exploratory.

Choose your language early and stay with it

The paper is available in C# and Python 3 as well as Visual Basic. Exam-preparation priority: settle the choice early and do all practice in that language. Switching late costs fluency in exactly the mechanical areas – syntax for loops, string handling, file input – where hesitation is most expensive under a two-hour clock.

On-screen means the environment itself is part of the exam

Paper 1 is sat at a computer, so speed with the editor, running the program and reading error messages all affect the mark. Exam-preparation priority: practise in the exact environment your centre uses, without internet search available. Debugging fluency – reading a stack trace and locating the line – is a trainable skill and one that written revision never touches.

The May/June-only change removes a resit route

With no November series from 2026, a disappointing result waits a full year rather than a few months. Exam-preparation priority: plan for the first sitting to be the sitting, and confirm the series with your centre rather than assuming a second opportunity within the academic year.

Paper 2’s theory rewards precise terminology

Concepts and principles questions turn on stating things exactly: the specific steps of an algorithm, the exact difference between two similar ideas, correct terminology for hardware, networking and data representation. Exam-preparation priority: write definitions from memory and compare them against the specification’s own wording. “Roughly right” answers are a well-known source of dropped marks in this part of the subject.

Trace tables should be written, not done mentally

Both papers reward the ability to determine what a piece of code does. Exam-preparation priority: practise trace tables on paper – a column per variable, a row per iteration. Mental tracing is where confident candidates make avoidable errors, and a written trace table is creditable working in its own right.

Worked routine: making a change to the skeleton program

The routine below is an original model written for this resource, not a reproduction of any official past paper, skeleton program or mark scheme.

Step 1 - read the whole task and note the required OUTPUT exactly:
Format, spacing, wording. Marks frequently depend on matching a
specified output precisely.

Step 2 - locate the part of the skeleton you need to change:
This is fast only if you explored the program beforehand.

Step 3 - make the smallest change that runs:
Then build on it. A partially working program scores; a broken
one usually does not.

Step 4 - test after each small addition:
An error found after three lines is trivial to locate; the same
error after sixty is not.

Step 5 - if one sub-task blocks you, move on:
Later sub-tasks are normally credited independently. Leave a
comment marking what is unfinished and return if time allows.

Step 6 - save as the paper instructs, when it instructs:
Unsaved work is unmarkable work.

Step 3 is the habit that most reliably protects marks: incremental development is simultaneously good practice and good exam strategy.

Before/during exam checklist

  • Before the exams: work extensively with the pre-released skeleton program; settle your language early and practise only in it; practise in your centre’s actual environment without internet help; write Paper 2 definitions from memory and check them against the specification’s wording; practise written trace tables; confirm your series given the May/June-only change.
  • During Paper 1: note the exact required output, build incrementally, test as you go, move on from blockers, and save as instructed.
  • During Paper 2: use precise terminology and write trace tables out rather than tracing mentally.

Self-test

  1. What is distinctive about Paper 1, and what preparation does it demand?
  2. Which languages is Paper 1 available in, and why choose early?
  3. What has changed about the examination series, and what follows?
  4. Why is incremental development an exam strategy rather than only good practice?

Answers: 1. It is an on-screen programming examination set against a pre-released skeleton program, so the program should be read, run, traced, broken and extended thoroughly before the exam. 2. C#, Python 3 or Visual Basic – choosing early preserves fluency in the mechanical areas (loop syntax, string handling, file input) where hesitation is most costly under a two-hour clock. 3. Exams now take place in May/June only, with no November series from 2026, so a disappointing result waits a full year rather than a few months. 4. Because a program that runs and completes part of the task earns marks while a more ambitious one that does not compile earns very few, and errors found early are far cheaper to locate.

Written against the assessment section of OxfordAQA’s own International GCSE Computer Science (9210) qualification page (official OxfordAQA page, verified 2026-08-28). The coding routine above is an original model written for this resource, not a reproduction of any official past paper, skeleton program or mark scheme. Always check the current specification for your examination series at oxfordaqa.com.

Get free revision emails (optional)

Occasional emails with practice questions, worked explanations and links to free resources for the qualification and subjects you choose. No spam, and you can unsubscribe from any email. The free tools on this site never need an email.

Subjects (optional, up to 6)

Choose a qualification to see its subjects.

Related resources

Related articles

Studying this with a teacher

Working through Computer Science IGCSE?

This page is free and stays free. If you would rather be taught it, Marlbridge runs Computer Science classes one-to-one and in small groups of up to 15, online in your own time zone. The first trial class is free. WhatsApp replies within an hour (8am–11pm Pakistan time, every day); email the same day.

OxfordAQA Computer Science teachers at Marlbridge