GCSE Computer Science Paper 1: What Actually Matters

Paper 1 for GCSE Computer Science (most commonly AQA 8525/1 or OCR J277/01) covers the theory side of the subject: how computers actually work under the hood. Paper 2 handles algorithms and programming, but Paper 1 is where students either build a solid foundation or get caught out by vague definitions they half-remember from Year 10.

Systems architecture and the fetch-execute cycle

This is the section that trips up more students than it should, mostly because they memorise the fetch-decode-execute cycle as a chant without understanding what each register does. You need to know the roles of the Program Counter, Accumulator, Memory Address Register (MAR) and Memory Data Register (MDR), and be able to explain, in order, how an instruction moves from RAM into the CPU and gets executed.

Von Neumann architecture questions often ask students to explain why clock speed, number of cores, and cache size affect performance. Don't just say "more cache is faster" — explain that cache is faster to access than RAM because of its physical proximity to the CPU, so keeping frequently used data closer reduces waiting time. Examiners want the mechanism, not the conclusion.

Memory and storage: know your units and your trade-offs

This section blends factual recall (RAM vs ROM, volatile vs non-volatile) with comparison questions on storage types: magnetic (HDD), optical (DVD/Blu-ray), and solid-state (SSD/flash). A common exam trap is asking students to justify a storage choice for a specific scenario — a laptop for a photographer, a server, a games console. You need to weigh capacity, speed, durability, portability, and cost, and actually apply them to the scenario rather than listing generic pros and cons.

Data representation questions cover binary, hexadecimal, and denary conversions, plus binary arithmetic (addition and overflow) and how images and sound are represented digitally. Practice converting 8-bit binary numbers to hex without a calculator — it comes up almost every paper, and it's free marks if you're fluent.

Networks: topologies, protocols, and the practical stuff

Students often know the terms — LAN, WAN, client-server, peer-to-peer — but struggle to explain why you'd pick one network topology over another. Star topology questions usually ask about single points of failure (the switch) versus the cost of extra cabling. Know the difference between TCP/IP layers conceptually: application, transport, network, link — you won't need deep protocol detail at GCSE level, but you should be able to say what each layer roughly does.

Protocols like HTTP, HTTPS, FTP, and TCP/IP itself show up as short-answer questions. Be specific: HTTPS encrypts data in transit using TLS, HTTP doesn't. That single distinction is worth memorising precisely because it's asked so often.

Boolean logic and truth tables

This is one of the more mechanical sections and one where practice pays off directly. AND, OR, NOT gates, and their combinations, get tested through truth tables and sometimes logic circuit diagrams. Work through past paper circuits by hand rather than trying to memorise patterns — a 3-input truth table has 8 rows, and if you're not systematic (000, 001, 010, 011...) you'll make careless errors under time pressure.

Systems software and security

Operating system functions (memory management, user interface, file management, peripheral management) are usually low-mark, high-frequency questions — the kind you should never lose marks on. Utility software (defragmentation, compression, encryption software) gets asked alongside them.

Security threats — malware, phishing, SQL injection, brute-force attacks, DDoS — appear almost every year, often paired with a matching prevention method question. Know the specific defence for each threat rather than a generic