Skip to content · ⁨본문 바로가기⁩

Browse · ⁨탐색⁩

A-Level Computer Science · ⁨A-Level 컴퓨터 과학⁩

Browse past papers, syllabus content, handouts, and vocabulary for every subject. · ⁨모든 주제에 대해 과거 논문, syllabus 내용, 핸드아웃 및 어휘를 Browse하십시오.⁩

Past papers · ⁨과거 논문⁩Handouts · ⁨교재 자료⁩Exercise sheets · ⁨연습지⁩Vocabulary · ⁨어휘⁩

No PDFs in this folder. · ⁨이 폴더에 PDF가 없습니다.⁩

Study A-Level Computer Science · ⁨A-Level 컴퓨터 과학⁩ · ⁨A-Level Computer Science · ⁨A-Level 컴퓨터 과학⁩ 공부하기⁩
Revise a topic · ⁨주제 복습하기⁩

Got a question wrong? Open the notes for that topic. · ⁨틀린 문제가 있나요? 그 주지의 노트를 열십시오.⁩

Teaching this subject? Everything for the classroom in one place · ⁨이 주제를 가르치신가요? 교실所需的 모든 것을 한곳에서⁩ →

Tips · ⁨팁⁩

Split these papers by half. Theory questions suit short, frequent sessions — they test recall of precise definitions, and precision decays fast. Programming questions need long, uninterrupted sittings, because the skill is holding a whole solution in your head.

Write the code by hand, then type it in and run it. Past papers are the one place you can discover that what you "would have written" does not compile — much cheaper to find out now than in the exam hall.

When marking theory, compare your wording to the scheme word by word, not by meaning. This subject's schemes are unusually literal, and the right idea in the wrong words often scores zero. Keep a list of the phrasings you keep missing.

Browse all subjects · ⁨모든 주제浏览⁩

Log in or create account · ⁨로그인 또는 계정 만들기⁩

IGCSE, A-Level & AP