AQA A-Level Computer Science 7517: A Study Guide

AQA's A-level Computer Science specification (7517) is one of the most widely taught computing qualifications in England, and it rewards students who combine theoretical understanding with genuine programming practice. Whether you're a student plotting your revision timeline or a parent trying to make sense of the spec code, here's a clear-eyed look at what 7517 actually covers and how to approach it.

What the Qualification Covers

7517 is assessed across two written exam papers plus a Non-Exam Assessment (NEA) programming project. Paper 1 focuses heavily on programming: you'll be expected to write, trace, and debug code in a language such as Python, Java, VB.NET, or C#, alongside skip-list, tree, and graph data structures. Paper 2 covers the theory side — computer systems architecture, memory and storage, wired and wireless networking, databases, big data, and the legal, ethical, and cultural implications of computing. Both papers also test computational thinking: algorithm design, Big O notation, and problem decomposition.

A recurring theme across the spec is that AQA wants students to think like computer scientists, not just memorize facts. Expect questions that ask you to design an algorithm from scratch, justify a data structure choice, or explain trade-offs in system design.

The Non-Exam Assessment (NEA)

The NEA is a substantial, self-directed programming project worth a meaningful chunk of the final grade. Students choose a real-world problem, analyze requirements, design a solution, implement it in code, and test it thoroughly — then write it all up in a structured report. The strongest projects aren't necessarily the most technically flashy; they're the ones with a clearly defined problem, sensible design decisions, and evidence of iterative testing against a written test plan.

A few practical tips for the NEA:

• Pick a problem you understand deeply. A well-scoped, modest project with excellent documentation beats an overambitious app that's half-finished.
• Document as you go. Screenshots of test runs, version history, and design rationale are much easier to capture in real time than reconstructed after the fact.
• Use appropriate data structures deliberately, and be ready to explain why you chose them — this maps directly onto marking criteria around design justification.

Programming Fluency Matters

Unlike some computing qualifications that treat programming as a minor skill, 7517 leans heavily on it. Students need to be comfortable with:

• Core control structures, functions, and recursion
• Object-oriented programming concepts (classes, inheritance, encapsulation)
• Standard algorithms: searching (linear, binary), sorting (bubble, merge, quick), and traversal of trees and graphs
• Reading and tracing unfamiliar code under exam pressure, including using trace tables

Regular, hands-on coding practice — not just reading about syntax — is the single highest-leverage activity for Paper 1. Past papers with mark schemes are invaluable here, since AQA's expected answer style (e.g., how much pseudocode detail earns marks) becomes obvious quickly with repetition.

Theory Topics Worth Prioritizing

On the Paper 2 side, students often underestimate networking and system architecture questions. Know the OSI/TCP-IP layers at a working level, understand how the CPU fetch-execute cycle works, and be able to compare storage technologies (SSD vs HDD vs magnetic tape) in terms of practical trade-offs like speed, cost, and durability. Database topics — normalization, SQL queries, entity relationship diagrams — tend to be scored generously when answers are precise and use correct terminology. 

Building a Revision Rhythm

A sensible cadence blends three activities: coding practice, past-paper questions, and active recall of definitions (protocols, data structure operations, legal frameworks like data protection principles). Spacing these out across weeks — rather than cramming theory the week before exams — tends to produce far stronger recall, especially for the denser Paper 2 content.

7517 is demanding, but its structure rewards students who treat computer science as a practical discipline rather than a memorization exercise. Strong code, clear justification, and precise technical vocabulary go a long way.

If you're working through topics like algorithms, networking fundamentals, or database design, Korra Studio's related segments are a solid next stop for structured practice.