A good Computer Science study route starts with three confirmed facts: your syllabus code, your exam year and the notation your paper uses. Everything else, the topic list, the time per topic and the practice, follows from those.
This page shows how to build that route in four steps, with a worked example you can copy and adjust. The wider Computer Science learning guide holds the full topic map.
Which syllabus are you actually studying?
Cambridge lists more than one Computer Science code, and guidance online is often written for a different exam year. Two students in the same class can also be entered for different series.
Ask your school or exam centre for three things: the code (for example 0478 or 0265), the exam year and the series. The syllabus and exam-year navigator turns these into a checking list. Then read the page on 0478 or 0265, and open the syllabus on the Cambridge page.
Step 1: Turn the syllabus into a topic list
Copy the topic headings from the Cambridge syllabus into your own list. Next to each one, write a rating from your own honest check: can explain, can do with notes or not yet.
Then match each heading to a module here, using the learning guide as the map. If a heading has no match, flag it and ask your teacher at school.
Step 2: Count your real blocks
Count blocks you will actually use, not blocks you wish you had. A block is one focused session, say 45 minutes. The realistic revision planner shows a visible conflict when the workload is larger than the blocks available, which is better than a plan that hides it.
Protect at least one rest day a week. A plan that needs every evening will break in the first exam-season week.
Step 3: Split the blocks by purpose
Not every block teaches something new. Split them into four purposes:
- Learn: a new topic, with notes and one worked example.
- Retest: a fresh question on an old topic, two or more days later.
- Mixed practice: questions from several topics in one sitting, see original practice.
- Buffer: unplanned time for a topic that took longer than expected.
Worked example: a 16-week route
Mina has 16 weeks and can manage 3 blocks a week.
| Item | Calculation | Blocks |
|---|---|---|
| Total available | 16 weeks × 3 blocks | 48 |
| Retest and mixed practice | 8 (one every two weeks) | 8 |
| Buffer | 4 (one every four weeks) | 4 |
| Left to learn | 48 − 8 − 4 | 36 |
| Per module (18 modules) | 36 ÷ 18 | 2 |
Two blocks for every module is too even. Algorithm design, repetition and arrays, and pseudocode need more practice than, say, the hardware overview.
So Mina moves 3 extra blocks to those three modules (3 each) and takes 1 block each from three lighter modules (1 each). Check: 3 × 3 + 3 × 1 + 12 × 2 = 9 + 3 + 24 = 36. The total is unchanged.
A common trap: planning all learning first
Some students schedule every topic once and leave retests for “later”. Later often becomes the last week. A topic met in week 2 and not seen again until week 15 has usually faded.
The fix is built into the table above: retest blocks are part of the plan from day one. Keep them, even when learning blocks run behind.
Step 4: Review the route every two weeks
Every two weeks, ask three questions. Which topics moved from “not yet” to “can explain”?
Which errors appear again in the mistake log? Did any block overrun?
Adjust the next two weeks only. A plan that is rewritten every day stops being a plan.
When a study route needs a teacher
Self-study works well when the gaps are clear and you can find your own errors. It helps to add a teacher when you finish a trace and still cannot see why your answer is wrong, or when several topics feel equally unclear and you cannot tell where to start.
If that sounds familiar, online one-to-one Computer Science tuition begins with a paid one-hour trial at the assigned teacher’s confirmed rate, from RM80.