Exam Intelligence · 3 Official Documents Analysed

How to Score Higher in AQA A Level Computer Science (7517)

Evidence-based Computer Science 7517 exam guide built from official AQA examiner reports and mark schemes. Specialised and comprehensive study tips — specific, cited insights so you can achieve top grades.

View Past Papers

Evidence-BasedBuilt from 3 official examiner reports & mark schemes (2022–2023)

What Are Assessment Objectives (AOs)?

Before we dive in, you need to understand how AQA actually marks your answers.

AO stands for Assessment Objective. Think of AOs as the different “skills” AQA tests you on in every single question. When an examiner marks your paper, they don't just give you a mark out of 12 based on how “good” your answer feels — they allocate specific marks to each AO separately.

For example, a 12-mark question might be split as: AO1 (2 marks) + AO2 (2 marks) + AO3 (2 marks) + AO4 (6 marks). If you write a perfect textbook answer but don't evaluate, you can only score 6 out of 12 — because the other 6 marks are specifically reserved for evaluation.

This is why understanding AOs matters: they tell you exactly what the examiner is looking for and how many marks each skill is worth. Here are the 3 AOs for this subject:

AO1

Demonstrate knowledge and understanding of the principles and concepts of computer science, including abstraction, logic, algorithms and data representation

30% (A-Level overall; AQA per-paper P1 8%, P2 22%, NEA 0%)

Demonstrate knowledge and understanding of the principles of Computer Science, including computational thinking, algorithms, data structures, hardware, software, and programming concepts. Tested throughout Paper 1 (on-screen) and Paper 2 (theory).

AO2

Apply knowledge and understanding of the principles and concepts of computer science, including to analyse problems in computational terms

30% (A-Level overall; AQA per-paper P1 12%, P2 16%, NEA 2%)

Apply knowledge and understanding of Computer Science to familiar and unfamiliar problems, including reading and tracing code, completing algorithms, and applying theoretical concepts in context. Includes trace table questions, Boolean algebra, and SQL writing tasks.

AO3

Design, program and evaluate computer systems that solve problems, making reasoned judgements about these and presenting conclusions

40% (A-Level overall; AQA per-paper P1 20%, P2 2%, NEA 18%)

Design, write and refine programs; evaluate and justify design decisions. Primarily assessed in Paper 1 (on-screen skeleton program tasks), the NEA Project (Paper 3), and extended programming questions in Paper 2.

The key takeaway: Most students lose marks not because they lack knowledge (AO1), but because they skip the higher-order skills — building chains of reasoning (AO2) and making supported judgements (AO3). Everything below shows you exactly how to hit each AO based on what AQA examiners have written in their reports.

🚫

Top Mistakes in A Level Computer Science 7517

The most common reasons students lose marks in A Level Computer Science 7517, cited directly from official AQA examiner reports across multiple sessions.

Imprecise descriptions of circular queue operations — omitting the empty-queue check

Paper 1, June 2022 · Affects: Paper 1

What examiners say

“many answers showing some understanding of the process of removing an item from a circular queue but lacking the precision required to get many marks”
— 7517/1 Paper 1, June 2022

“Students who did know the correct process sometimes omitted the need to check for an empty queue before attempting deletion.”
— 7517/1 Paper 1, June 2022

How to fix this

For circular queue deletion: state the pointer arithmetic explicitly (rear-pointer wraps using modulo), check for an empty queue (front == rear or a count variable == 0) BEFORE attempting deletion, increment the front pointer after removal, and make clear that items do not physically shift. Describe a linear queue only when specifically asked — switching models loses marks.

Failing to write accurate regular expressions — wrong or missing alternation symbol

Paper 1, June 2022 · Affects: Paper 1

What examiners say

“Not many students were able to write an accurate regular expression, with most not using the correct symbol for alternation (|).”
— 7517/1 Paper 1, June 2022

How to fix this

Memorise the AQA regular expression symbols: | for alternation, * for zero-or-more, + for one-or-more, ? for zero-or-one, () for grouping, [] for character class, ^ for start, $ for end. Practise translating a specification (e.g. 'a digit followed by a letter or underscore') into a regex step by step. Test mentally against boundary cases before writing your final answer.

Vague or superficial description of operating system functions — naming without explaining

Paper 2, June 2022 · Affects: Paper 2

What examiners say

“It was not sufficient to simply name functions, such as 'memory management'. Some students put the names of functions into sentences, such as 'the operating system will carry out memory management', but still did not describe what this was and so did not achieve a mark.”
— 7517/2 Paper 2, June 2022

How to fix this

For each OS function, write a mini-definition: memory management = the OS allocates regions of RAM to each process; processor scheduling = the OS decides the order in which processes use the CPU and for how long; device management = the OS communicates with hardware through device drivers, abstracting the hardware from applications. Never use the function name as the answer — you must describe what it does.

Incorrect understanding of start/stop bits — treating them as data delimiters only

Paper 2, June 2022 · Affects: Paper 2

What examiners say

“The most commonly seen response to question part 2.4 was that the start bit identified the start of a data transmission. This was not enough to be markworthy. Good responses identified that the start bit would be used to bring the receiver's clock into synchronisation with the sender's clock.”
— 7517/2 Paper 2, June 2022

“The most commonly seen response to question part 2.5 was that the stop bit identified the end of a data transmission. This response was not markworthy. Good responses explained that the stop bit was sent so that the next start bit could be recognised or to give time for the receiver to process or transfer the received data.”
— 7517/2 Paper 2, June 2022

How to fix this

Link the start bit to clock synchronisation: the receiver uses the start bit to align its clock with the transmitter's clock so that subsequent bits are sampled at the correct time. The stop bit returns the line to the idle (high) state so the next start bit (low) can be detected. Never describe either as simply 'marking the start/end of a message' without the synchronisation mechanism.

Thin-client hardware requirements answered with vague, non-technical terminology

Paper 2, June 2022 · Affects: Paper 2

What examiners say

“Many students used very vague terminology when writing about the hardware requirements of thin-client and thick-client systems. Phrases such as 'high-end server', 'powerful server', 'server with lots of hardware', 'lots of power', 'cheaper computer', 'weak hardware' and 'good communications' were often seen and were not markworthy.”
— 7517/2 Paper 2, June 2022

“at A-Level, students are expected to be more precise, for example to discuss the amount of RAM required, or that processors with multiple cores might be necessary”
— 7517/2 Paper 2, June 2022

How to fix this

Use precise hardware terminology at all times. For thin-client: the server requires more RAM (to run many sessions simultaneously) and multi-core processors (to handle concurrent requests), while clients require minimal processing power and RAM because processing occurs server-side. Always state whether a hardware requirement refers to the server or the client — generic statements are not credited.

Boolean simplification errors — applying De Morgan's law to mixed-operator expressions incorrectly

Paper 2, June 2022 and June 2023 · Affects: Paper 2

What examiners say

“De Morgan's law can only be applied to multiple operators at the same time if the operators are all of the same type.”
— 7517/2 Paper 2, June 2022

“Simplifying B̄ + B to 1 near to the start of the simplification, which was not possible in the expression since AND has a higher precedence than OR.”
— 7517/2 Paper 2, June 2023

How to fix this

Always apply operator precedence before simplifying: NOT has highest precedence, then AND, then OR. De Morgan's law requires all operators under the bar to be of the same type before the law is applied directly. Write each simplification step explicitly. If you see B̄ + B inside a larger expression, check whether the two terms are connected by AND to something else before cancelling to 1.

Assembly language trace errors — wrong shift direction and failing to write final result to memory

Paper 2, June 2022 · Affects: Paper 2

What examiners say

“Shifting the value in R1 left instead of right.”
— 7517/2 Paper 2, June 2022

“Storing a value with a decimal part in R1 when it was shifted right.”
— 7517/2 Paper 2, June 2022

How to fix this

For each assembly language trace: read the mnemonic carefully (LSL = logical shift left, LSR = logical shift right); integer registers cannot hold decimal values after a right shift (truncate). Always track STORE instructions — if the last instruction writes a register to a memory address, fill in the memory column in the trace table. Mark the final memory state explicitly before closing the trace.

Asymmetric encryption and digital signatures — confusing which key is used at each stage

Paper 2, June 2023 · Affects: Paper 2

What examiners say

“The most common mistakes were: Referring to public and private keys, but not recognising that both the sender and receiver had different public and private keys. Mixing up which key was used for each part of the process. Writing vaguely about how the message digest would be used after reception to confirm that the message was sent by A.”
— 7517/2 Paper 2, June 2023

How to fix this

Learn the four-key model: sender encrypts data with the receiver's public key (confidentiality); sender signs by hashing the message then encrypting the hash with the sender's own private key (authentication). The receiver decrypts the signature with the sender's public key to recover the original hash, then recomputes the hash of the received message and compares the two. Each party has a different key pair — never describe a single shared key pair.

Apply what you've learned

Practice identifying these mistakes in real papers. Try a recent paper and mark yourself — you'll spot these patterns immediately.

Try June 2024 All 7517 Papers

✅

What A Level Computer Science 7517 Examiners Reward

Patterns that consistently earn high marks in A Level Computer Science 7517, based on AQA examiner report commentary on top-scoring answers.

Using a list + reverse strategy or two-pointer approach to solve the vowel-swap programming problem

7517 examiners described two approaches that led to working Paper 1 solutions: collecting vowels into a list, reversing it, then substituting back; and a two-pointer approach walking inward from both ends swapping vowels. Creative solutions that used a stack or a recursive subroutine with the substring between the first and last vowels were also credited as showing good problem-solving.

Source: 7517/1 Paper 1, June 2022

Correctly describing normalised floating-point and its benefits for precision and equality testing

7517 examiners noted that good responses recognised that normalising floating point numbers maximises precision within a given number of bits and ensures that there is one unique representation for each number, which makes it simpler to test two numbers for equality — weak answers only said 'increased accuracy' without explaining the mechanism.

Source: 7517/2 Paper 2, June 2022

Structured, detailed responses to the 12-mark fetch-execute and hardware performance question

7517 examiners observed many good responses to this question, praising answers that covered all three stages of the fetch-execute cycle and explained how each hardware improvement (e.g. multiple cores) would allow multiple instructions to be executed simultaneously — vague claims such as 'more instructions per second' without the mechanism were not credited.

Source: 7517/2 Paper 2, June 2023

Applying ethical and legal knowledge with reference to GDPR in the extended-writing question

7517 examiners awarded high marks to responses that recognised consent of the customers would be necessary for the system to be used and that this would be regulated by GDPR, which would place a range of requirements on the supermarket — as opposed to simply stating that 'data was collected without consent'.

Source: 7517/2 Paper 2, June 2022

Correctly completing the assembly language program for hexadecimal ASCII conversion

7517 examiners noted it was pleasing to see many good responses to the hexadecimal ASCII conversion task, with the majority of students correctly performing the masking and/or shifting required to isolate the binary patterns of the two hexadecimal digits and making some attempt to convert these to ASCII codes.

Source: 7517/2 Paper 2, June 2023

Identifying immutability and no-side-effects as key functional programming features for distributed code

7517 examiners awarded marks for good responses that recognised specific features relating to functional programs, such as data structures being immutable and functions having no side-effects — single-word answers such as 'immutable' without explanation were not credited.

Source: 7517/2 Paper 2, June 2023

📝

A Level Computer Science 7517 Answer Frameworks

Structured approaches for each A Level Computer Science 7517 question type, derived from AQA mark scheme requirements.

Extended-writing / discuss question (e.g. ethical/legal implications, network comparison)

~15–20 minutes for a 9–12 mark question

Structure

Define the relevant concepts → apply to the specific scenario → weigh up both sides (ethical and legal separately, or two network types) → reach a conclusion that is tied to the context.

•Always anchor your answer to the scenario given — generic advantages not applied to the context are not credited
•For ethical/legal questions, keep ethics (who should have access, purpose of data) and legal requirements (GDPR, consent) as separate strands
•Name specific legal frameworks (GDPR) and technical terms (referential integrity, foreign key) rather than paraphrasing them vaguely
•Conclude by evaluating which design or approach is more appropriate for the given situation, not just listing pros and cons

Boolean algebra simplification (Paper 2)

~8–12 minutes for a 4–6 mark question

Structure

Write out the original expression → state the precedence order (NOT, AND, OR) → apply one law per line, citing the law used → reach the simplest form.

•Show every step — partial credit is available for valid intermediate steps even if the final answer is wrong
•Apply De Morgan's law only when all operators under the bar are of the same type
•Check operator precedence before cancelling any sub-expression — AND binds more tightly than OR
•Verify your final expression by substituting values from the truth table for a quick sanity check

Assembly language trace table (Paper 2)

~10–15 minutes for a 5–7 mark trace

Structure

Read each instruction in order → update the named register(s) → note any flags set → fill in the memory column for every STORE instruction → check branch conditions before skipping lines.

•Track the direction of shifts carefully (LSL = left, LSR = right); registers hold integers — no decimal parts after a right shift
•Use the # prefix for immediate values and confirm addressing mode matches the question
•Always complete STORE/STR steps — the most common mark lost is not writing the final register value into the memory address
•For branching, evaluate the comparison condition explicitly before deciding whether the branch is taken

On-screen skeleton program modification (Paper 1, Sections B–D)

~15–25 minutes per programming question (varies by marks)

Structure

Read the relevant section of the skeleton carefully → identify the class/method to modify → write syntactically correct code in the language chosen → run a mental test with a boundary case → take a screen capture of working output (never a screen capture of code).

•Submit code as pasted text, not as a screen capture — screen captures of code are hard to read and can obscure long lines
•For recursion solutions, always use the value returned by the recursive call — discarding it means the game state is not updated
•When inheriting, check the class hierarchy — inherit from the correct parent class (e.g. DifficultyCard not Card) to access the needed attributes
•Attempt all longer programming questions: marks are available for simple steps such as declaring a variable with an initial value in the right scope

Practice by topic

Use topical past papers to practice specific question types. Each topic collects questions from multiple years — perfect for drilling the frameworks above.

Topical Past Papers

💬

A Level Computer Science 7517 Command Words Decoded

Each command word in A Level Computer Science 7517 is a scoring instruction. Understanding what AQA examiners expect is critical to earning full marks.

describe2–4 marks typically

Give a detailed account of what something is and how it works. At A-Level, naming a concept without explaining the mechanism behind it is never sufficient.

Common mistake

Naming a function or concept without explanation — e.g. writing 'memory management' instead of explaining that the OS allocates regions of RAM to different processes.

“It was not sufficient to simply name functions, such as 'memory management'.”

explain2–4 marks typically

Give reasons or show how/why something works, making the causal link explicit. A statement without justification is rarely markworthy.

Common mistake

Providing a fact without the causal link — e.g. stating that a peer-to-peer network would be cheaper without explaining that this is because no dedicated server needs to be purchased.

“students who just stated that a peer-to-peer system would be cheaper did not receive a mark as this was a statement rather than an explanation”

identify1 mark typically

Name or select the correct item from the specification. Often used in multiple-choice or 'state the addressing mode' style questions. No justification is required unless the question also says 'explain'.

Common mistake

Giving a vague or general answer — e.g. 'addresses' instead of 'IP addresses' when asked to describe DNS output.

state1 mark typically

Give a concise, precise fact. No working or explanation is needed, but the statement must be technically exact.

Common mistake

Being too vague or using informal language — e.g. 'the thing that controls the computer' instead of 'the operating system manages hardware resources and provides services to applications'.

compare3–4 marks typically

State both similarities and/or differences between two or more items, with each point addressing both items explicitly. Discussing only one side is a common trap.

Common mistake

Only addressing one of the two items being compared — e.g. describing only the advantages of peer-to-peer without contrasting with client-server.

“it is important that students address the context when giving their response, rather than just listing general advantages of a peer-to-peer system”

write (SQL / code)3–6 marks typically

Produce syntactically correct code that exactly matches the stated requirements. Programming marks require code to be syntactically correct — partial credit for correct structure with syntax errors is limited.

Common mistake

Writing the data type before the field name in CREATE TABLE; omitting commas between field definitions; writing the correct logic but introducing syntax errors that prevent the code from running.

📐

A Level Computer Science 7517 Diagram Checklist

Incorrect diagrams in A Level Computer Science 7517 are flagged in every AQA examiner report. Use this checklist before every practice and in the exam.

Diagram checklist

⚠️

Topics Students Struggle With Most In A Level Computer Science 7517

These A Level Computer Science 7517 topics consistently produce the lowest scores. Prioritise these in your revision.

Circular queues — precise pointer-based operations and empty/full checks

7517 examiners reported that question part 2.1 was not well answered, with many students describing a linear queue instead of a circular queue or failing to include the check for an empty queue before attempting deletion. Common errors included removing from the rear and describing all items moving 'up one'.

Affects: Paper 1

Regular expressions — syntax and alternation operator

7517 examiners noted that not many students were able to write an accurate regular expression, with most not using the correct symbol for alternation (|). This question is asked in the context of the skeleton program and requires confident use of regex metacharacters.

Affects: Paper 1

Floating-point representation — normalisation purpose and conversion errors

7517 examiners reported that question part 5.2 (2022) was not answered well, with many students giving vague responses such as 'increased accuracy'. In both 2022 and 2023, a common error was representing -23.25 by concatenating the representation of -23 and +0.25, which gives -22.75.

Affects: Paper 2

Start and stop bits — role in clock synchronisation

7517 examiners found that the standard response that the start bit 'identified the start of a data transmission' was not markworthy and that question parts 2.4 and 2.5 on start and stop bits 'are not well understood'. The synchronisation role of the start bit and the line-idle role of the stop bit were the expected answers.

Affects: Paper 2

Boolean algebra — operator precedence and correct application of De Morgan's law

7517 examiners reported in both 2022 and 2023 that only approximately a quarter of students achieved full marks for Boolean simplification. Recurring errors include simplifying B̄ + B to 1 prematurely when AND has higher precedence, and applying De Morgan's law across mixed AND/OR operators.

Affects: Paper 2

Transport layer and networking protocols — precise role of each OSI/TCP-IP layer

7517 examiners noted in 2023 that most students achieved only one of three marks for the transport layer, with the most common mistake being to describe the role of the network layer instead of the transport layer. Port numbers and end-to-end connection establishment were the discriminating mark points.

Affects: Paper 2

OOP concepts — protected specifier and method overriding linked to inheritance

7517 examiners reported that a significant number of students described the private specifier instead of the protected specifier. Answers for the overriding question often lacked precision — to gain the mark, answers needed to make clear the link to inheritance.

Affects: Paper 1

Functional programming — higher-order functions, recursion traces, and distributed computing properties

7517 examiners found in 2022 that fewer students could correctly apply recursive functions fw and fx in the trace table, with approximately only a quarter achieving all four marks. In 2023, features of functional programming suited to distributed code were not well known — single-word answers such as 'immutable' without explanation were not credited.

Affects: Paper 2

Target your weak areas

The topics above are where most marks are lost. Use past papers and mark schemes to practice these specific areas until they become second nature.

Past Papers & Mark Schemes Topical Papers

Frequently Asked Questions

What papers make up AQA A-Level Computer Science 7517?

There are three components: Paper 1 (7517/1) is a 2-hour 30-minute on-screen exam using a Skeleton Program (100 marks, 40%); Paper 2 (7517/2) is a 2-hour 30-minute written theory exam (100 marks, 40%); and Paper 3 (7517/3) is the NEA (Non-Exam Assessment) programming project (75 marks, 20%), completed over the course of study under teacher supervision. All three components are required for the full A-Level.

What programming languages are allowed in Paper 1?

AQA officially supports four languages for the on-screen Paper 1: C#, Java, Python 3 (Python 2 is no longer supported) and VB.NET. The Skeleton Program is provided in each approved language by AQA. Schools indicate their preferred programming language at the start of the course; students must use that registered language and submit code as text pasted into the Electronic Answer Document — not as screen captures. Centres should test the Skeleton Program on exam-day machines in advance.

What is the NEA project and how is it assessed?

The NEA (Non-Exam Assessment), also called Paper 3 (7517/3), is a student-designed programming project worth 75 marks. It is assessed on five strands: analysis of the problem, design of the solution, implementation (the code itself), testing, and evaluation. The project is completed under teacher supervision during the course and is internally marked then externally moderated by AQA. There is no fixed exam-day time limit, but the work must be the student's own.

Are calculators or programming references allowed in the written exam?

No. Calculators are not permitted in Paper 2 (7517/2). Students must perform all numerical calculations — including binary arithmetic, floating-point conversions, file-size calculations and relative error — by hand and should show clear working, as partial credit is available for correct method even when the final answer is wrong. No programming references, textbooks or language documentation are permitted in either Paper 1 or Paper 2.

Put It All Into Practice

You now know exactly what AQA examiners reward and penalise. The next step is deliberate practice with real papers. We have 10 exam sessions available for A Level Computer Science 7517 — question papers, mark schemes, and examiner reports.

View All Past Papers Latest Session: June 2024 Topical Past Papers