This page gives you a revision route for SPM Computer Science: a checklist of things you should be able to do in each topic cluster, and an order to practise them. Tick a line only when you can do it on a blank page without looking at notes.
It sits under the SPM Computer Science learning guide. Confirm the current paper format and assessed components with the Lembaga Peperiksaan website and your school teacher, since these can change between years.
What order should I revise in?
Start with reading and tracing, then move to writing, then to debugging. Reading code comes first because you cannot write or fix what you cannot follow.
| Week block | Skill focus | Why this order |
|---|---|---|
| 1 | Trace code with a trace table | Every later skill depends on it |
| 2 | Write selection and loops | Uses tracing to check your own code |
| 3 | Debug and test | Needs both tracing and writing |
| 4 | Data, logic and mixed questions | Mixed questions under time |
Adjust the blocks to the weeks you actually have. The realistic revision planner turns your real free hours into a schedule.
Topic checklist: can you do this?
Programming and algorithms
- Name the data type of a value and say why a variable was chosen over a constant.
- Trace a selection structure with values on each side of a boundary.
- Write a loop whose first and last passes you can predict.
- Follow a function call and say what each parameter holds.
- Find a fault in a short program and say whether it is a syntax, logic or runtime error.
Practise these in programming foundations and advanced programming practice.
Computing systems and logic
- Convert a value between number systems within your syllabus.
- Complete a truth table for a two or three input expression.
- Explain what a hardware component does in a small system.
The computing systems and logic cluster covers these.
Data and databases
- Identify entities, attributes and a suitable primary key in a short description.
- Explain what a foreign key links.
- Predict which rows a simple query returns from a small table.
See data and databases and database development.
Interfaces and project work
- Judge a screen against clarity, feedback and navigation.
- Separate structure, presentation and behaviour in a small page.
- Plan and test your own assessed project, and record your own work.
Use human-computer interaction and web and project development.
How do I use the checklist each week?
Pick three unticked lines on Monday. Do one original question for each, then mark the line green only if you solved it without help.
Keep the lines that stay red. Those are the topics for your next session, and the skill evidence tracker records them so you can see how your skills change over the weeks instead of guessing.
Keep a mistake list
For every wrong answer, write the line where your thinking went off course, not only the correct answer. A list such as “used < instead of <=” or “forgot to update the counter” shows patterns quickly.
Review the list before each session with the spaced recall planner and the mistake log and paper-error review. Three repeated entries tell you which skill deserves a teacher’s attention.
When a teacher helps most
A checklist shows where the gaps are. Closing them is faster with someone who reads your working and asks why you chose each line. If you want that, see online one-to-one Computer Science tuition, which starts with the one-hour trial class (from RM50).