England A-level Computer Science study guide
DfE and Ofqual requirements, current AQA 7517, OCR H446 and Eduqas A500QS specifications, and amended UK data-protection guidance reviewed 29 July 2026
601 practice questions
120 flashcards
Completely free

A-level Computer Science Study Guide

Connect algorithms, programs, data and computer systems while building the analytical and project skills shared across England exam boards.

DfE common core
AQA · OCR · Eduqas checked
80% exam · 20% project

Most popular

Start with free practice questions

Jump into a mixed set drawn from 601 free practice questions.

Free Practice Questions

Exam structure

Know the split before you start drilling

England A-level Computer Science Common Core

100%

0 scored + 0 pretest

Qualification

Linear A level

The A level is assessed at the end of the course; standalone AS arrangements and content are separate.

Assessment balance

80% exam · 20% NEA

Ofqual requires 80% of A-level marks from examination and 20% from non-examination assessment.

Assessment objectives

AO1 · AO2 · AO3

Knowledge, application or computational analysis, and designing, programming and evaluating systems each account for 30–40%.

Mathematics

At least 10%

At least 10% of assessment tests mathematical skills, including Boolean algebra, number bases and algorithm complexity.

Programming project

Substantial solution

The 20% NEA requires an authenticated programmed solution or investigation; marks, evidence and administration differ by board.

Study coverage

601 original questions

The 24-topic allocation is an independent study design, not an official mark weighting for AQA, OCR or Eduqas.

Start here

How to study A-level Computer Science

Build algorithmic and programming foundations before integrating systems, data and project evidence.

1

1. Define and trace

Practise abstraction, decomposition, algorithms, state tracing and Boolean reasoning.

2

2. Implement and compare

Use precise types, modular interfaces and suitable data structures, then compare correctness and efficiency.

3

3. Integrate and evaluate

Connect architecture, networks and databases to a systematic project process with evidence-led testing and evaluation.

About the exam

A-level Computer Science Exam structure

An independent A-level Computer Science study guide built from the DfE common content and Ofqual assessment requirements, cross-checked against current AQA, Cambridge OCR and Eduqas specifications.

Issuer and path

A-level Computer Science Study Guide is administered through England A-level awarding bodies. Check official resources before booking, retesting, or relying on a stale requirement.

England A-level Computer Science Common Core

100%

0 scored + 0 pretest

The DfE knowledge, programming, mathematical and problem-solving requirements common to regulated AS and A-level Computer Science specifications in England, organised for study rather than as one board's paper split.

Use your own board's current materials

Check the exact entry code, paper split, programming language or environment, pseudocode conventions, preliminary materials, NEA authentication and submission rules for your cohort. Do not substitute a Pearson International A Level or a Wales-only WJEC route.

How to use this guide

How to study A-level Computer Science

Define the problem and representation, trace the state change, justify the algorithm or architecture, then test the result against requirements, evidence and constraints.

1. Define the problem and representation

State the inputs, outputs, constraints, assumptions and the data or system model being used.

2. Trace the mechanism

Follow every relevant state change, instruction, packet, query or data-structure operation in order.

3. Justify the choice

Relate the algorithm, structure, architecture or control to correctness, efficiency, risk and the stated requirements.

4. Test the conclusion

Check boundary cases, units, complexity, security assumptions, user evidence and alternative explanations before evaluating.

Computational Thinking and Algorithms
Common core

Abstraction, Decomposition and Modelling

Representing the essential features of a problem, dividing it into manageable parts and selecting a model whose assumptions are suitable for the purpose.

Key rules

Rule 1

Abstraction suppresses irrelevant detail while retaining the state, behaviour and relationships needed to solve the problem.

Exam cue: State what information is retained, what is omitted and why the omission is safe.

Rule 2

Decomposition produces smaller components with clear responsibilities, inputs, outputs and dependencies.

Exam cue: Give each subproblem one coherent responsibility and define how it interacts with the rest.

Rule 3

A computational model is useful only within its assumptions, representation choices and validation evidence.

Exam cue: Test the model against representative, boundary and exceptional real-world cases.

Common traps

Treating abstraction as simply removing as much detail as possible.

Prevention: Do not substitute a memorised definition or generic advantage until you have identified the input, state, stakeholder and constraint in the task.

Splitting a problem without defining the interfaces between parts.

Prevention: Do not substitute a memorised definition or generic advantage until you have identified the input, state, stakeholder and constraint in the task.

Assuming a model is correct because the program runs.

Prevention: Do not substitute a memorised definition or generic advantage until you have identified the input, state, stakeholder and constraint in the task.

Memory anchors

Abstraction

Retain the essential properties of a problem while hiding irrelevant detail.

Decomposition

Break a complex problem into smaller, connected subproblems.

Model

A model is a purposeful representation with explicit assumptions and limits.

Interface

An interface defines how components exchange data or services.

Validation

Validation asks whether the model represents the intended real-world problem sufficiently well.

Next best moves

Quick check-up

Use a short quiz to confirm the rule pattern is actually sticking.

Check-up Questions

1-2 question checkpoint

A route-planning model stores junctions and road lengths but omits building colours. Which computational-thinking technique justifies the omission?

A school timetabling problem is divided into room allocation, teacher availability and clash checking. What is this division called?

Answer all questions to submit.

Next step personalized recommendations

Open another topic next

Official resources

Verify the details with the official sources

Use these links for eligibility, scheduling, handbook rules, and issuer updates. Our guide helps you study; official sources tell you what the testing partner currently requires.

FAQ

Common A-level Computer Science questions

Is this an official exam-board study guide?

No. It is an independent resource based on DfE content common to regulated England specifications and Ofqual's assessment rules, then cross-checked against current AQA, Cambridge OCR and Eduqas materials.

Why does the guide not reproduce one board's paper structure?

Boards split theory, programming and systems content differently. This guide organises the statutory common core for learning; use the current specification and assessment materials for your board's exact paper coverage, timing, preliminary material and rubric.

Do all A-level Computer Science routes include a project?

Regulated England A levels must allocate 20% to non-examination assessment. The shared purpose is a substantial programmed solution or investigation, but AQA, OCR and Eduqas use different mark totals, criteria, evidence structures and administrative instructions.

Can I use any programming language or pseudocode style?

Not automatically. Language choices, exam programming arrangements and pseudocode conventions vary by board and sometimes by assessment series. Use the current materials for the exact qualification and cohort.

How do the current AQA, OCR and Eduqas A levels split assessment?

AQA 7517 uses an on-screen programming Paper 1 worth 40%, a written Paper 2 worth 40% and a computing practical project worth 20%. OCR H446 uses Computer systems at 40%, Algorithms and programming at 40% and a Programming project at 20%. Eduqas A500QS uses Programming and System Development at 40%, Computer Architecture, Data, Communication and Applications at 40% and a Programmed Solution to a Problem at 20%. Always check the current series instructions as language, preliminary-material and submission arrangements are not interchangeable.

Why is Pearson Edexcel not listed as an England board route?

Pearson's current public 2026 Computer Science qualification is an International Advanced Level, not the regulated England A level covered here. Do not substitute its four-unit structure for AQA 7517, OCR H446 or Eduqas A500QS.

Which content is stable and which needs a current check?

Core ideas such as algorithms, data representation, architecture, protocols and database modelling are stable. Named laws, security threats, development tools, contemporary technologies and board administration can change, so verify current official materials for the exam year.

Are the topic allocations official weights?

No. DfE specifies common content and Ofqual specifies assessment objectives and the 80/20 balance, but there is no shared official percentage for these 24 study topics. The allocations only plan balanced future practice coverage.

What is Pass Harbor?

Completely free exam prep for 247 UK exams.

  • Practice questions
  • Flashcards
  • Study guides
  • Mock exams
  • No registration
  • No paywall
  • Start instantly
No more expensive exam prep. Quality study tools should be accessible to everyone.