GCSE Computer Science

Pseudocode in GCSE Computer Science exams

What pseudocode is, and why exams use it

Pseudocode is a way of writing an algorithm's logic without committing to any one programming language's exact syntax. Exam boards use it because it's language-neutral — a student who's learned Python and a student who's learned VB can both read the same pseudocode question and understand it equally. Pseudocode tests whether you understand the logic of an algorithm, not whether you remember a specific language's punctuation.

Key pseudocode constructs

The constructs that appear across AQA, OCR, and Edexcel pseudocode are broadly consistent, even where the exact keywords differ slightly between boards:

• Assignment — x ← 5 or x = 5 — sets a variable's value.
• Input/output — INPUT, OUTPUT or PRINT — reading from and writing to the user.
• Selection — IF ... THEN ... ELSE ... ENDIF, sometimes with ELSE IF.
• Loops — FOR ... ENDFOR (count-controlled), WHILE ... ENDWHILE (condition-controlled).
• Subroutine calls — CALL a named procedure or function, often with parameters in brackets.

How to read pseudocode and trace through it

Reading pseudocode is the same skill as reading Python: work through it one line at a time, and keep track of what every variable holds as you go — a trace table works just as well on pseudocode as it does on Python. One habit worth building deliberately: don't silently translate pseudocode into Python in your head as you read it. Read the logic on its own terms first, and only translate if the question actually asks for Python.

total ← 0
FOR i ← 1 TO 5
    INPUT number
    total ← total + number
ENDFOR
OUTPUT total

Work through this the same way you would a trace table: total starts at 0, the loop runs five times, and on each pass a new number is added to the running total. After the loop, the final total is output.

How to write pseudocode answers that get marks

Examiners mark pseudocode on logical correctness, not on hitting one exact syntax. That means: use clear, consistent notation throughout your answer — pick one style for assignment and one for loops, and stick to it; indent loop and selection bodies so the structure is visible at a glance; and name variables so their purpose is obvious. A marker who has to guess what a variable is doing is a marker about to award fewer marks.

What examiners actually test

Pseudocode questions typically ask you to trace through given pseudocode and state the output, convert pseudocode to a specific language (or vice versa), or write pseudocode for a described algorithm from scratch. The construct most worth being fluent in is the count-controlled loop (FOR ... ENDFOR) paired with an accumulator variable — it's the backbone of most short pseudocode questions.