How the assessment works, in general terms
GCSE Computer Science is offered by several exam boards, and the papers differ between them. Before you plan anything, find out which board your school entered you for and download its specification. Three of the most common are AQA 8525, Pearson Edexcel and OCR J277.
Edexcel's course page describes onscreen practical programming assessments, so on that board you should expect to write and test code at a computer. For AQA and OCR, the pages Sessioned opened did not set out the paper formats, so check each specification PDF for the number of papers, their lengths and how programming is examined. Your school will also tell you about any assessed practical work.
Whatever the board, the same skills carry over: reading code, writing code, converting between number bases, and explaining how computers and networks work in clear sentences.
Common mistakes
- Only reading. Programming is learned by typing code, running it and fixing it. Reading a solution is not the same as being able to write one.
- Skipping the trace table. When a loop or a condition confuses you, writing out each variable line by line usually settles it.
- Rushing binary and hex. Most slips are arithmetic ones, such as a missed column or a misread place value. Check by converting back.
- Vague definitions. Answers like "it makes things faster" earn little. Say what the component does and why that matters.
- Learning a favourite algorithm but not tracing it. You may be asked to follow a search or sort step by step on a given list.
- Practising only on topics you enjoy. Make a list of the areas that feel shaky and give those the first slot each day while you are fresh.
- Leaving ethics until last. These questions reward balanced points with a reason attached, so practise them.
A four-week plan
Stretch or squeeze the weeks to match your exam date. Short, frequent practice usually beats one long evening. Use the revision timetable to lay these out around your other commitments.
Week 1: algorithms and programming basics
Revisit sequence, selection and iteration, then trace linear search, binary search and a simple sort by hand. Write five short programs from scratch, such as a times-table printer or a password length checker. Finish each one by testing it with at least three different inputs and noting what you expected before you ran it.
Week 2: data representation
Practise binary, denary and hexadecimal conversions daily, then binary addition and shifts. Work out file sizes for images and sound from first principles, and compare lossy and lossless compression.
Week 3: hardware, networks and software
Cover the CPU and the fetch-decode-execute cycle, memory and storage, then networks, protocols and the operating system. Draw each diagram from memory and label it.
Week 4: security, ethics and mixed practice
Go through threats and defences, then the ethical, legal and environmental impacts of technology. Spend the rest of the week on mixed questions and on past papers, which you can find via the past papers tool.
Technique by area
Algorithms and pseudocode
Decompose a problem into steps before writing anything. Use a trace table to follow values. Exams may present code in their own pseudocode or reference-language style, so ask your teacher which style your paper uses and practise reading it as well as writing it. When you are asked to complete or correct an algorithm, check the boundaries first: the first and last item, an empty list and a single item.
Programming practice
Choose one language and stay with it. Build up from small pieces: take input, validate it, loop, store results in a list, then split the code into subroutines. When something fails, read the error message, check the line it points to and test with one simple input. Learn to tell syntax errors from logic errors, because the fixes are different. Practise writing test data that includes normal, boundary and invalid values.
Data representation and binary
Write the place values above every binary number: 128, 64, 32, 16, 8, 4, 2, 1. For hexadecimal, convert each digit to four bits and back. Show your working, since method marks are common in conversion questions. For images and sound, write the formula before you substitute numbers, and keep your units straight (bits, bytes, kilobytes).
Hardware and networks
Learn each component as a job description: what it does, what it holds, what it passes on. For the fetch-decode-execute cycle, name the registers in order. For networks, link every term to its purpose, for example a router forwards packets between networks and a protocol is an agreed set of rules. Compare wired and wireless connections using specific points rather than general ones.
Security
Pair every threat with a defence and a reason it works. Phishing is countered by training and filters, brute force by strong passwords and lockouts, and injection by validating input. Be able to say why a defence reduces risk rather than removes it.
Ethics and impacts
Structure longer answers as a point, an explanation and a consequence, and give both sides when asked to discuss. Cover privacy, access to technology, environmental effects, and the legal side of technology. Check your board's specification, or ask your teacher, which laws you are expected to name.
Free tools to use alongside this guide
- Flashcards for definitions and hex values.
- Progress tracker to tick off topics as you go.
- Review planner to space out your return visits to each topic.
- GCSE Computer Science glossary and practice quiz.
Part of the GCSE Computer Science revision set: the glossary of key terms and self-marking quiz.