~11–13 mins read
15 Best Revision Tips to Achieve A* in A-Level Computer Science
A-Level Computer Science is a unique mix of logic, theory, and practical programming. Securing an A* is not just about working hard — it’s about working smart with a strategic and consistent revision approach.
This subject requires mastery of algorithms, data structures, programming, networks, databases, computational thinking, and coursework. Across exam boards such as AQA, OCR, and Edexcel, the principles remain the same: understand the specification, practise relentlessly, and refine exam technique.
Below are the 15 best revision tips, combining expert strategies, student-tested methods, and practical actions to help you achieve that top grade.
Table of Contents
- Master the Specification Inside Out
- Understand, Don’t Just Memorise
- Practice Past Papers Relentlessly
- Code, Code, Code!
- Create Revision Resources
- Utilise Online Resources
- Teach Others (or Yourself)
- Focus on Weak Areas
- Understand the Command Words
- Learn Key Definitions Precisely
- Break Down Large Topics
- Active Recall & Spaced Repetition
- Simulate Exam Conditions
- Coursework and Project Strategy
- Take Care of Yourself & Reflect
Tip #1: Master the Specification Inside Out
Your exam board specification is your revision roadmap. It lists every single concept and skill that could be tested.
Action: Download it from AQA, OCR, or Edexcel. Go line by line — tick off topics you’ve mastered, highlight weaker ones, and treat it like a checklist.
Tip #2: Understand, Don’t Just Memorise
Computer Science is about logic and reasoning, not rote memory. Memorisation won’t save you in curveball questions.
Action: For each topic (e.g., encryption, OOP, network protocols), ask:
- What is it?
- How does it work?
- Why is it important?
- Strengths and weaknesses?
If you can teach it, you understand it.
Tip #3: Practice Past Papers Relentlessly
Past papers reveal examiner habits, recurring styles, and traps.
Action:
- Attempt untimed with notes → timed mocks later.
- Always use mark schemes + examiner reports.
- Track mistakes: careless vs knowledge gap vs technique issue.
Tip #4: Code, Code, Code!
Programming is central. You cannot wing syntax or debugging.
Action:
- Code daily in Python, Java, or VB.NET.
- Recreate sorting, searching, Dijkstra’s from scratch.
- Build mini-projects (e.g., calculators, games).
- Use LeetCode, HackerRank, Codewars for algorithm fluency.
Tip #5: Create Revision Resources
Passive reading doesn’t stick — active creation embeds knowledge.
Action:
- Mind Maps for topics like Networks/Databases.
- Flashcards for SQL, pseudocode, Boolean algebra.
- Diagrams for flowcharts, architectures, OS.
- Summary Sheets per chapter (1 page each).
Tip #6: Utilise Online Resources
Textbooks alone aren’t enough.
Action:
- YouTube: Craig’n’Dave (AQA), Computerphile.
- Forums: Stack Overflow, PMT, Reddit CS.
- Revision platforms: Save My Exams, Seneca.
- GitHub: explore open-source projects.
Tip #7: Teach Others (or Yourself)
Explaining forces clarity. If you can’t teach it, you don’t know it.
Action:
- Study groups + peer teaching.
- Rubber Duck Debugging (explain aloud to an object).
Tip #8: Focus on Weak Areas
Students often over-revise strong areas. That won’t move grades.
Action:
- Identify weak topics from mocks.
- Dedicate double-time to them.
- Rotate revision so all topics stay fresh.
Tip #9: Understand the Command Words
Misreading command words = lost marks.
| Word | Meaning |
|---|---|
| Describe | Facts only |
| Explain | Give reasons, mechanisms |
| Evaluate | Pros, cons, conclusion |
| Justify | Provide reasoning |
Tip #10: Learn Key Definitions Precisely
Examiners love definitions — tiny slips = lost marks.
Action:
- Flashcards for keywords: abstraction, recursion, deadlock, polymorphism.
- Write them word-for-word as per textbook/mark scheme.
Tip #11: Break Down Large Topics
Big topics overwhelm. Break them.
Example (Networking):
- OSI Model
- TCP/IP Stack
- Network Hardware
- Security Protocols
Tip #12: Active Recall & Spaced Repetition
Memory = recall, not reread.
Action:
- Anki/Quizlet flashcards.
- Space reviews (1d, 3d, 1w, 2w).
- Focus on SQL, Big-O, normalisation.
Tip #13: Simulate Exam Conditions
Practise pressure, not just knowledge.
Action:
- Sit full papers in silence.
- Use mark-per-minute rules.
- Review with schemes, loop errors into next revision.
Tip #14: Coursework and Project Strategy
For NEA/coursework boards, this is a grade booster.
Action:
- Pick an engaging project.
- Document design → implementation → testing → evaluation.
- Link theory (e.g., chosen data structure).
- Seek feedback early.
Tip #15: Take Care of Yourself & Reflect
Your brain is hardware. Protect it.
Action:
- 7–8 hrs sleep, good diet, hydration.
- Exercise to reduce stress.
- After each paper, reflect: mistakes → underlying topic → fix.
Final Verdict
Achieving an A* in A-Level Computer Science is about consistency, precision, and balance. By coding daily, mastering the spec, leveraging past papers, and managing health, you’ll ace the exam while building real-world tech skills that carry into university and industry.
FAQs (SEO-Optimised)
1: How do I get an A* in A-Level Computer Science? By mastering the spec, practising past papers, coding daily, and refining exam technique. Strategy beats cramming.
2: Which exam board is hardest for Computer Science? OCR is often toughest (algorithms-heavy), while AQA/Edexcel are more structured. Approach remains similar.
3: How many hours per week should I revise? 10–12 hrs in Year 13, rising to 15–18 hrs near exams. Prioritise quality — active recall + past papers.
4: Best way to revise algorithms? Use flowcharts, pseudocode, trace tables → then code them → analyse Big-O efficiency.
5: Should I code daily? Yes. Even 30–60 mins builds fluency and prevents silly mistakes.
6: Are flashcards useful? Yes — for SQL, Boolean algebra, definitions. Pair with spaced repetition.
7: How do I balance coursework vs exams? Start coursework early, keep steady progress, link theory. Don’t let it crowd exam prep.
8: Common exam mistakes? Misreading command words, vague definitions, missing working in algorithms.
9: Can I get A* if weak at maths? Yes — but practise Boolean logic, binary, algorithms (maths-heavy areas).
10: Is group revision effective? Yes. Use solo sessions for focus, group sessions for teaching/clarifying.
11: Best online resources? Craig’n’Dave, Computerphile, Save My Exams, HackerRank, LeetCode.
12: When to start revising? Year 13 start ideally. If late, prioritise high-yield topics, definitions, past papers.
Quick Links (GLECTA)
- 📘 Our Courses
- 📞 Request a Callback
- 💻 A-Level Computer Science Tuition
- 📝 Book A-Level Mocks
- 📚 Free Resources (KS1–A Level)