中文（繁體）
中文（简体）
English
A-Level Computer Science 9618 Paper 4: Declaration, Logic, Testing
Programming: write the test data before the code
Paper 4 is the practical paper, usually written on paper, and the marks sit in three layers: declaration, logic and testing – not in whether the code would run. The usual failures are an undeclared variable, an unhandled boundary or a file step in the wrong order. Drill the order: inputs and outputs, then test data, then the body.
How is A-Level Computer Science 9618 Paper 4 assessed, and what does each part carry?
Paper 4 (Practical): Submit code + testing, 75 marks (25% A-Level); Paper 2 (Problem-solving and Programming): Answered in pseudocode, 75 marks (25% A-Level)
Assessment at a glance (2027)
| Component | Content | Weighting | Duration |
|---|---|---|---|
| Paper 4 (Practical) | Submit code + testing, 75 marks | 25% A-Level | 2 h 30 min |
| Paper 2 (Problem-solving and Programming) | Answered in pseudocode, 75 marks | 25% A-Level | 2 hours |
A-Level Computer Science Paper 4 drilling technique: write the design (input-process-output) before coding; arrays are 0-based (0 TO 3); write boundary-value tests for functions; print your test evidence before submitting. Boundary testing is a common lost mark.
What each paper is actually testing
| Paper | Drill focus | How marks are lost |
|---|---|---|
| Paper 4 (Practical) | design + code + test | The body is written straight onto the answer paper with variables and arrays undeclared, so the structure marks go even when the logic is right. |
| Paper 2 (Problem-solving and Programming) | algorithms + data structures | File work skips the open, read-write, close order and never handles a missing file, so the later parts of the question fall with it. |
What is each A-Level Computer Science 9618 Paper 4 paper really testing, and what should you drill?
Paper 4 (Practical): design + code + test; Paper 2 (Problem-solving and Programming): algorithms + data structures
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 1-3: declarations and data structures. Write a variable table (name, type, purpose) before the body.\nWeeks 4-6: loops and conditions. Drill the three boundaries – first item, last item, empty collection – once each.\nWeeks 7-9: files and exceptions. Always open, process, close, and add one error-handling line.\nWeeks 10-12: whole papers to time, spending the first minute on test data; redo only the undeclared and the boundary failures.
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 4 (Practical) | 2 h 30 min | 20 min plan, 100 min code, 30 min test |
| Paper 2 (Problem-solving and Programming) | 2 hours | about 20 min per question |
How should the time be split inside each A-Level Computer Science 9618 Paper 4 paper?
Paper 4 (Practical): 20 min plan, 100 min code, 30 min test; Paper 2 (Problem-solving and Programming): about 20 min per question
The drilling mistakes that cost the most marks
| Mistake | What it looks like | What actually happens | Instead |
|---|---|---|---|
| No test plan | Code only | List input, expected and actual output | test evidence |
| Array bound wrong | 1 TO 4 | 0-based: 0 TO 3 | 0 TO 3 |
| Condition order wrong | >=70 before >=80 | Test the higher threshold first | >=80 first |
The error log and the mark scheme
Three columns: the question and what was missing, the scheme key words (declaration, type, boundary, open and close, test data), and whether the loss was structure, logic or testing. Structure deserves its own tally – it is the easiest to dismiss when reviewing.
How many years should you drill?
9618 is the current syllabus; older papers use different numbering and language conventions, so the format may not match. Fix the shape with the 9618 specimen and the last three to five years, then use older papers for algorithm practice rewritten in the current style.
How many years of past papers is enough?
9618 is the current syllabus; older papers use different numbering and language conventions, so the format may not match. Fix the shape with the 9618 specimen and the last three to five years, then use older papers for algorithm practice rewritten in the current style.
Frequently asked questions
Is this page a mock paper or a drilling guide?
This is the A-Level Computer Science 9618 Paper 4 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 A-Level Computer Science 9618 Paper 4 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.
Should comments be written in a paper-based programming exam?
Yes, at the key points only: inputs and outputs, the purpose of a loop, error handling. Comments show intent, which helps the marker find the marks and helps you review.
Do you need to memorise syntax?
Memorise the structures rather than every character: declarations, loops, conditions and file statements should come out in one go. The rest can follow the language reference in the paper.
Official references
| Resource | What to use it for |
|---|---|
| Cambridge A-Level Computer Science 9618 syllabus (2027-2029) | Confirm the Paper 1-4 marks and times |
| https://www.tutorzone.com.hk/en-alevel-computer-science-9618-paper-2-mock-2027/ | A-Level Computer Science Paper 2 drilling mock |
Related: practice area · A-Level Computer Science Paper 2 drilling mock
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.
