WJEC GCSE Computer Science: A Working Revision Plan

WJEC GCSE Computer Science splits into two written papers (Unit 1: Understanding Computer Science, Unit 2: Programming and System Development) plus a non-exam programming assessment that doesn't count toward your final grade but absolutely shapes whether you understand the material well enough to pass the exams. Most students lose marks not from ignorance but from vague answers on questions that reward precision. This guide is about fixing that.

Know exactly what's being tested where

Unit 1 covers binary, hardware, networks, security, and the impact of technology on society. Unit 2 covers algorithms, programming constructs, data types, and databases, but it's still a written exam, not a coding test. That trips people up. You won't be typing Python during Unit 2 — you'll be reading pseudocode, tracing through it by hand, and writing out logic on paper. If you've only ever practised in a code editor with instant feedback, sit down and trace five programs on paper with a pencil, no compiler, no autocomplete. Write the variable values in a table as you go. This is the single most useful exercise for Unit 2 because it forces you to actually execute the logic in your head instead of pattern-matching to code you've seen before.

Binary and number systems: drill until it's boring

Denary to binary conversion, binary to hexadecimal, one's and two's complement, binary addition with overflow — these come up almost every year and they're either right or wrong, no partial credit for vibes. Practice converting numbers using the divide-by-2 method for denary-to-binary and grouping bits in fours for hex conversion. Do ten conversions a day for a week rather than fifty in one sitting the night before. If two's complement negative numbers confuse you, remember the shortcut: flip all the bits, add 1. Test it on a number you already know the answer to, like -5 in 8-bit (11111011), until the process feels automatic rather than something you're reconstructing from a rule you half-remember.

Networking and security: match keywords to definitions precisely

WJEC mark schemes for Unit 1 are strict about terminology. If a question asks about a DoS attack, don't write "someone hacks the website" — write that it floods a server with requests to make it unavailable to legitimate users. Build a glossary as you revise: LAN vs WAN, packet switching, MAC address vs IP address, firewall vs proxy server, symmetric vs asymmetric encryption. For each term, write a one-sentence definition and one-sentence example, in your own words, not copied from a textbook. Copying doesn't build recall. Rewriting from memory does.

Programming constructs: build a personal reference sheet

For Unit 2, know sequence, selection, and iteration cold, along with the difference between a while loop and a for loop in pseudocode terms — condition-controlled versus count-controlled. Practice writing pseudocode for common problems: finding the maximum in a list, validating user input, searching an array linearly. WJEC pseudocode has its own conventions (using INPUT, OUTPUT, IF...THEN...ELSE...ENDIF), so if you've learned Python first, spend deliberate time translating your Python instincts into WJEC's pseudocode style. A for i = 1 to 10 loop in WJEC pseudocode is inclusive of 10 — check this against your revision guide, because getting the boundary wrong on a trace table costs marks even when your logic is otherwise correct.

Past papers are the actual revision, not a bonus activity

Read through the WJEC specification once, then spend most of your remaining time on past papers rather than re-reading notes. Past papers reveal the exact phrasing WJEC uses and the exact level of detail expected in a 4-mark versus a 6-mark answer. Mark your own answers against the published mark scheme and note where you were vague. A common gap: naming a concept correctly but not explaining it in the depth the mark allocation demands. If a question is worth 4 marks, it usually wants four distinct points, not one point said four ways.

The week before the exam

Stop learning new content three or four days out. Instead, redo the past paper questions you got wrong earlier in your revision and check whether you'd get them right now. Keep a single-page summary sheet per topic — binary, networks, security, programming constructs, databases — and read through those instead of full notes. Sleep matters more than one extra hour of cramming; a tired brain doesn't retrieve information well no matter how many times you've read it.

If you want to build the programming fluency behind Unit 2 further, Korra Studio has hands-on Python and Computer Science segments worth working through alongside your revision.