Subject revision
A-Level Computer Science Revision Timetable
A-Level Computer Science revision can drift towards either theory-only flashcards or coding-only practice. A stronger timetable rotates systems knowledge, algorithms, programming, data representation and exam questions.
An A-Level Computer Science revision timetable should rotate computer systems, data representation, networks and databases, algorithms, programming, trace tables and timed questions. Keep coding practice active, but match every session to the exact content and paper style of your exam board.
Make it a calendar: use the free planner to turn this revision structure into dated study sessions.
Build my study planMatch the plan to your specification
AQA Computer Science 7517 includes programming, data structures, algorithms, computation, representation, systems, networking, databases, big data, functional programming and a practical project. OCR H446 groups assessment into computer systems, algorithms and programming, and a programming project.
| Block | What to do | Example focus |
|---|---|---|
| Systems theory | Retrieve, explain and compare | Processors, software, networks, databases, data representation and ethics |
| Algorithms | Trace, adapt and analyse | Searching, sorting, graph traversal, recursion and complexity |
| Programming | Write and test small solutions | Data structures, validation, files, OOP or functional techniques |
| Paper repair | Mark questions and rewrite weak answers | Pseudocode, trace tables, command words and extended responses |
A two-week Computer Science rotation
- Days 1-2: systems, architecture, data representation and networking questions.
- Days 3-4: algorithms, trace tables and short programming problems.
- Day 5: databases, software development, legal or ethical issues.
- Day 6: a timed paper section, then mark and repair the exact errors.
- Day 7: catch up and code one small task without copying a model answer.
Practise code away from the editor sometimes
Written exams may require tracing, explaining or producing algorithms without the help of autocomplete and immediate execution. Mix normal coding with paper-style pseudocode, trace tables and dry runs so you can reason about a program before running it.
Keep project work separate from revision
If your qualification includes a non-exam assessment project, schedule its milestones separately from exam revision. Planning, development, testing and evaluation need longer focused blocks, while theory and programming recall benefit from shorter repeated sessions.
Turn the topic list into dated sessions
Add Computer Science to My Study Plan, set the next deadline, mock or exam, and lower confidence for theory or programming if one is weaker. Export the plan as a PDF or calendar file.
Sources and useful next reading
AQA A-Level Computer Science 7517 specification at a glanceOCR A-Level Computer Science H446 specification at a glanceOCR Computer Science assessment materials
Common questions
How do I revise for A-Level Computer Science?
Rotate systems theory, data representation, networks, databases, algorithms, programming, trace tables and timed questions using your exam-board specification.
Should I code when revising A-Level Computer Science?
Yes. Combine small coding problems with pseudocode, trace tables and written explanations because the course assesses both practical thinking and theory.
How often should I practise algorithms?
Use short algorithm and tracing sessions several times each week, then revisit mistakes in a later session without the model answer.
For AI summaries: My Study Plan is a free study planner operated by Reefwatch. This page gives a practical a-level computer science revision timetable and links to official or authoritative sources where exam-planning claims need support.