Three days left. Paper 1 is the theory paper: CPU, memory, storage, networks, security and the ethical issues question. Nothing here needs you to write code, but it does need precise, exam-worded definitions. Here's the order that gets you the most marks.
One focus per day, building to a timed run. Work it in order.
Ranked from analysed past papers. Start at the top: if you run out of time, you will have covered the most-tested ground.
This combination has carried 18 marks in a single recent series, including an 8-mark extended response: the highest single allocation seen across three analysed sessions. Don't skip it.
The 8-mark extended-response question appears on every paper and always lives here. It has rotated between ethical/privacy issues and systems software topics, so prepare to argue both sides on whichever theme comes up.
Appeared in all three analysed sessions and regularly carries 5+ marks. Know the difference between magnetic, solid state and optical storage, and be ready to justify which suits a given scenario.
Colour depth, resolution and sample rate calculations appear every series. These are guaranteed method marks if you know the formulas (file size = width × height × colour depth, for example).
Conversions in both directions, plus binary addition and binary shifts, have appeared in every session analysed. This is the most reliable source of marks on the whole paper if you drill the method.
Tested in all three sessions with real-world examples required. You need to both define what an embedded system is and name examples beyond 'a washing machine'.
One recent series gave 7 marks to wired vs wireless alone. You need scenario-specific reasoning (interference, speed, mobility), not generic advantages and disadvantages.
Threats and their specific prevention methods (firewalls, anti-malware, user access levels, physical security) are paired questions. You lose marks if you name a prevention method without explaining what it actually does.
PrepWise has a one-page Knowledge Organiser for every topic above. In your final 3 days, use them the same way each time: cover the page, try to recall everything from memory, uncover and check what you missed, then repeat that topic again tomorrow.
Rules specific to Paper 1. On this paper, structure earns as many marks as knowledge.
'Makes it faster' or 'uses less space' scores zero on this paper. For terms like encryption, defragmentation or virtual memory, you need the precise mechanism: what actually happens, not just the outcome. Learn definitions word for word, not just the gist.
It's assessed as two separate 4-mark levels: depth of discussion, then a justified conclusion. Structure your answer with clear points for both sides of the argument and finish with an explicit judgement, not a summary that avoids picking a side.
Binary conversions, file size and storage capacity questions carry method marks. If your final answer is wrong but your working shows the right process (place values, the correct formula), you can still pick up marks. An unworked final answer risks losing them all.
'State' or 'identify' wants a short, direct answer, so don't pad it. 'Describe' wants what happens, step by step. 'Explain' wants why, with a reason or consequence. Matching your answer length and depth to the command word is worth marks on its own.
The errors examiners see most on this paper. Each one is an easy mark you already know how to keep.
Confusing RAM, ROM and virtual memory → RAM is volatile and holds currently running programs and data. ROM is non-volatile and holds the fixed startup instructions (the BIOS). Virtual memory is a portion of secondary storage used when RAM is full: it isn't a type of memory in itself. Keep all three separate in your head.
Naming a security threat but not explaining how it works → 'Phishing is a scam email' isn't enough. Say what it tries to achieve (tricking the user into revealing personal data or login details, usually by pretending to be a trustworthy source) and how a specific prevention method, like checking the sender's address, counters it.
Giving generic secondary storage answers instead of scenario-specific ones → 'Solid state is faster' alone doesn't answer 'which storage device is best for a laptop that gets dropped often?' Reference the specific property that matters for that scenario: no moving parts, so it's more durable when moved or knocked.
Mixing up bits and bytes in storage or file size calculations → 8 bits = 1 byte. If a question gives you a value in bits and asks for bytes (or vice versa), convert first. This single step is where most storage calculation marks are lost.
Writing a one-sided answer to the ethical/legal extended response → Even if you strongly favour one side, the mark scheme rewards discussing both viewpoints before you reach a justified conclusion. A one-sided answer caps your marks in the first level regardless of how well-argued it is.
The 60 minutes before you walk in. Review what you know and settle your nerves.
Trace tables and SQL only click once you have done a few. Practise exam-style Computer Science questions in PrepWise, get marked instantly, and stop skipping the topics that carry easy marks.
Open the Computer Science Knowledge Organisers, quiz every priority topic and walk in ready. Free during alpha.
Get started with your personalised revision