中文（繁體）
中文（简体）
English
IGCSE Computer Science 0478 Paper 2 Drill Guide: Working Algorithms
TUTORZONE EXAM DRILL GUIDE · IGCSE COMPUTER SCIENCE 0478 PAPER 2: ALGORITHMS AND CODE
Paper 2 marks hang on whether you can turn a solution into runnable code in the required language. Plenty of candidates solve the problem on paper but lose the whole block to an uninitialised variable or a loop boundary. This page covers the drilling method only: reading order, a three-line plan before coding, a checklist and the error log.
How is IGCSE Computer Science 0478 Paper 2 assessed, and what does each part carry?
Paper 1 (Computer Systems): Short-answer and structured, 75 marks, Topics 1-6 (75 marks (50%)); Paper 2 (Algorithms, Programming and Logic): Short-answer + structured + scenario, 75 marks (75 marks (50%))
Assessment at a glance (2027)
| Component | Content | Weighting | Duration |
|---|---|---|---|
| Paper 1 (Computer Systems) | Short-answer and structured, 75 marks, Topics 1-6 | 75 marks (50%) | 1 h 45 min |
| Paper 2 (Algorithms, Programming and Logic) | Short-answer + structured + scenario, 75 marks | 75 marks (50%) | 1 h 45 min |
IGCSE Computer Science drilling technique: 10 questions in 1 h 45 min is about 10 minutes each. Show place values for binary (8+0+2+1); give definitions and examples for concepts (RAM/ROM, LAN/WAN).
What each paper is actually testing
| Paper | Drill focus | How marks are lost |
|---|---|---|
| Paper 1 (Computer Systems) | show steps for binary, definitions for concepts | A variable is used before initialisation, invalidating the block. |
| Paper 2 (Algorithms, Programming and Logic) | algorithms, flowcharts, logic gates | An off-by-one loop bound so the output is always one item short. |
What is each IGCSE Computer Science 0478 Paper 2 paper really testing, and what should you drill?
Paper 1 (Computer Systems): show steps for binary, definitions for concepts; Paper 2 (Algorithms, Programming and Logic): algorithms, flowcharts, logic gates
Drill order: by topic, then by year, then the mark scheme
| Step | What you do | Why |
|---|---|---|
| 1. By topic | Work through each topic, starting with the paper that allows least help (no calculator / closed book) | Exposes what is genuinely not understood |
| 2. By year | Whole papers to time, one or two a week | Trains pace, stamina and question selection |
| 3. Mark scheme | Go through the marking scheme question by question and log the scoring steps you missed | Most lost marks are written wrong, not thought wrong |
Should drilling go by topic first or by year?
By topic first, then whole papers by year, then the mark scheme. The first third of the time goes topic by topic (8-10 years of the same topic back to back), the middle switches to timed whole papers, and the last fortnight only redoes the recurring errors from your log.
A 12-week drilling timetable
| Week | Phase | What to do |
|---|---|---|
| Weeks 1-3 | By topic: foundation | Topic by topic, starting with the easiest marks, building habits and recall |
| Weeks 4-6 | By topic: core | 8-10 years of the same topic back to back, errors classified by topic |
| Weeks 7-8 | By topic: advanced and electives | Elective and higher-order topics, now under time pressure |
| Weeks 9-10 | By year: timed papers | One full paper a week, timed, no reference materials |
| Week 11 | Mark scheme work | Question by question against the marking scheme; list the scoring steps you omitted |
| Week 12 | Plug holes and simulate | Only the recurring errors from your log, then one full exam simulation |
Subject-specific weighting for this timetable: Weeks one to four take one question type per session: trace tables, loops, conditions, file handling, dry-running the values by hand each time. Weeks five to eight run whole timed papers with the three-line plan written before any code. The final four weeks are long questions only, checked against the same checklist before the paper is handed in.
Use it properly: this is not a checklist to finish. Every week must keep time for redoing errors, or from week 9 you will be repeating the same batch.
Pacing
| Paper | Time | Suggested split |
|---|---|---|
| Paper 1 (Computer Systems) | 1 h 45 min | about 10 min per question |
| Paper 2 (Algorithms, Programming and Logic) | 1 h 45 min | write pseudocode for programming |
How should the time be split inside each IGCSE Computer Science 0478 Paper 2 paper?
Paper 1 (Computer Systems): about 10 min per question; Paper 2 (Algorithms, Programming and Logic): write pseudocode for programming
The drilling mistakes that cost the most marks
| Mistake | What it looks like | What actually happens | Instead |
|---|---|---|---|
| Wrong place values | 1011 as 13 | Place values are 8/4/2/1 | 8+0+2+1 = 11 |
| RAM/ROM mixed | RAM as non-volatile | RAM volatile, ROM non-volatile | RAM volatile, ROM non-volatile |
| Hex error | FF as 165 | F=15, FF=15×16+15 | FF = 255 |
The error log and the mark scheme
Three columns: question type; the line that failed (uninitialised, boundary, format, language); and the fixed version. Once a mistake appears three times, condense it onto a single card and revise only that card before the exam.
How many years should you drill?
The IGCSE Computer Science structure has been stable recently, so older papers stay useful: time the last five as whole papers and split earlier ones by question type. The official scheme shows where each block earns marks, so mark against it block by block.
How many years of past papers is enough?
The IGCSE Computer Science structure has been stable recently, so older papers stay useful: time the last five as whole papers and split earlier ones by question type. The official scheme shows where each block earns marks, so mark against it block by block.
Frequently asked questions
Is this page a mock paper or a drilling guide?
This is the IGCSE Computer Science 0478 Paper 2 drilling guide: assessment structure, drill order, a 12-week timetable, pacing, common mark losses and the error-log method. For questions with answers, use the IGCSE Computer Science 0478 Paper 2 mock papers linked under Related.
By topic or by year first?
By topic. Eight to ten years of the same topic back to back is what exposes repeating errors; going straight to whole papers just repeats the same batch under time pressure.
How should the error log be written?
Do not copy out questions. Per error record four things: question reference, which step failed (concept, wording, calculation), what the mark scheme requires, and the correct action next time.
May I write pseudocode?
If a language is specified, use it. Pseudocode is acceptable only where the question asks for an algorithm, and it must still show input, process and output.
Does one small bug zero the whole question?
Usually not: most schemes award marks per block for the plan, correct syntax and correct output, so partial code beats a blank.
Official references
| Resource | What to use it for |
|---|---|
| Cambridge IGCSE Computer Science 0478 syllabus (2026-2028) | Confirm the Paper 1/2 marks and times |
| https://www.tutorzone.com.hk/en-igcse-physics-0625-paper-4-mock-2027/ | IGCSE Physics (0625) drilling mock |
Original mock: IGCSE Computer Science 0478 Paper 2 mock paper with answers; more practice in the practice area.
Next step: find a tutor / register as a tutor
After drilling, the hard part is telling a conceptual error from a writing error. Tell us the year group, the school and your available times, and TutorZone will match you with a tutor who knows the HKEAA assessment requirements.
Demand for tutors in this subject is steady, and those who can explain the marking scheme and where marks are won are especially sought after. Register free; you pay only when a match succeeds.
