7517 · AQA A Level
7517/21
Paper 2
Computer Science · June 2023 · Variant 1
Relative difficulty
Analysis source: AQA
Analysis aligned to the official syllabus and assessment design.
4.2 / 5
200
300 min
Procedural and Object-Oriented Programming
Cohort performance
Session statistics from official examination reports
Total marks
200
Duration
300 min
Session difficulty
4.2 / 5
Key examiner messages
Top priorities from the principal examiner before you revise
This series represents a highly demanding assessment, retaining the rigorous standard characteristic of the AQA 7517 specification.
With an overall difficulty rating of 4.2 out of 5, candidates were forced to demonstrate both rapid programmatic problem-solving under tight time constraints in Paper 1 and robust technical detail in Paper 2.
Question difficulty map
How candidates performed on each question in this series
No data available in official reports
Assessment objectives
Skill and AO weighting from official examiner commentary
Skill weighting
Shows the skill mix this paper tested most heavily.
Practical Programming
Weight: 6100%System Architecture
Weight: 467%Mathematical & Calculation
Weight: 233%Modeling & N
Weight: 117%
Method marks watchlist
Where working, steps, or method marks were commonly lost
No data available in official reports
Recurring mistakes across years
Themes examiners flag in multiple recent sessions for this subject
No data available in official reports
Question choice intelligence
Mean scores and popularity for optional questions (HKDSE electives)
No data available in official reports
Level exemplars
What candidate scripts at each grade level looked like
No data available in official reports
Grade & admission context
How marks relate to grade thresholds and entry standards
Report type
Examiner report — national grade boundaries and question-level commentary
Level A*
Approx. 79% of maximum mark
Level A
Approx. 63% of maximum mark
Level B
Approx. 51% of maximum mark
Level C
Approx. 39% of maximum mark
Level D
Approx. 27% of maximum mark
Level E
Approx. 15% of maximum mark
Deep insights
What top candidates did
Techniques and approaches examiners rewarded in this series
No data available in official reports
Command word playbook
How to match each command word to the expected response style
Give reasons and link mechanism to outcome; each point needs a because/so chain.
State features in sequence or list observable properties — do not explain causes unless asked.
Show formula, substitution, and unit; method marks need visible working.
Match the expected response style for “State” questions.
Match the expected response style for “Write” questions.
Match the expected response style for “Complete” questions.
Match the expected response style for “Rewrite” questions.
Time traps
Sections where candidates spent disproportionate time relative to marks
Min per mark: 50
Min per mark: 1.9
Min per mark: 1.5
Min per mark: 1.5
Syllabus traceability
Topics linked to questions and mark weighting in this session
Programming (Fundamentals of programming)
48 marks this session
Structure and role of the processor and its components (Fundamentals of computer organisation and architecture)
26 marks this session
Programming paradigms (Fundamentals of programming)
13 marks this session
MCQ trap analytics
Commonly chosen wrong options from examiner commentary
No data available in official reports
Topic heatmap across years
Mark concentration by topic and exam year for this subject
Mark intensity
Programming (Fundamentals of programming)
Programming paradigms (Fundamentals of programming)
Structure and role of the processor and its components (Fundamentals of computer organisation and architecture)
The Internet (Fundamentals of communication and networking)
Graph-traversal (Fundamentals of algorithms)
Individual (moral), social (ethical), legal and cultural issues and opportunities
Difficulty trend
How session difficulty has shifted across recent years
Paper comparison
Marks and duration breakdown across papers in this session
Paper 1:
Paper 2:
Marks you can still earn
Where valid approaches outside the mark scheme may still gain credit
No data available in official reports
Practise what examiners flagged
Target weak topics from this report inside the Revui app
Programming (Fundamentals of programming)
48 marks this session
Practise in RevuiStructure and role of the processor and its components (Fundamentals of computer organisation and architecture)
26 marks this session
Practise in RevuiProgramming paradigms (Fundamentals of programming)
13 marks this session
Practise in RevuiSelf-diagnostic checklist
Key actions before you sit this paper — copy and tick off as you revise
- 1Message
This series represents a highly demanding assessment, retaining the rigorous standard characteristic of the AQA 7517 specification.
- 2Message
With an overall difficulty rating of 4.2 out of 5, candidates were forced to demonstrate both rapid programmatic problem-solving under tight time constraints in Paper 1 and robust technical detail in Paper 2.
Teacher briefing pack
One-page session summary for tutors and classroom review
June 2023 2023
Computer Science
This series represents a highly demanding assessment, retaining the rigorous standard characteristic of the AQA 7517 specification. With an overall difficulty rating of 4.2 out of 5, candidates were forced to demonstrate both rapid programmatic problem-solving under tight time co
This series represents a highly demanding assessment, retaining the rigorous standard characteristic of the AQA 7517 specification.
With an overall difficulty rating of 4.2 out of 5, candidates were forced to demonstrate both rapid programmatic problem-solving under tight time constraints in Paper 1 and robust technical detail in Paper 2.
- Total marks
- 200
- Duration
- 300 min
- Session difficulty
- 4.2 / 5
Session analysis
This series represents a highly demanding assessment, retaining the rigorous standard characteristic of the AQA 7517 specification. With an overall difficulty rating of 4.2 out of 5, candidates were forced to demonstrate both rapid programmatic problem-solving under tight time constraints in Paper 1 and robust technical detail in Paper 2.
Updated Jun 14, 2026
Paper breakdown
Paper 1:
Paper 2:
Top chapters
Exam structure insights
Marks by chapter
See where the marks were concentrated so revision time goes to the highest-value topics.
Mark accessibility
Estimate which marks were basic, mid-level, or high-difficulty.
75% within easy or medium reach
Command word frequency
Spot common command words so answers match the expected response style.
Question type mix
Compare the mark share of each paper section and question type.
Short Answer / Explain
74·42·37%
Programming
(Practical)
54·5·27%
Algorithms / Mathematical
48·18·24%
Long Essay / Scenario
24·2·12%
Study ROI
Bigger bubbles recur more often; higher bubbles carry more marks, helping you rank revision priorities.
Time vs marks
Compare marks with suggested time allocation to plan exam pacing.
Paper 1 Section A (…
0.65 m/minPaper 1 Section B (…
0.65 m/minPaper 1 Section C (…
0.53 m/minPaper 1 Section D (…1
0.02 m/minTotal marks
64
Total time
160 min
Avg pace
0.40
Next-year prediction
Topics worth watching next year, with the reason shown directly below each bar.
Individual, moral, ethical, legal and cultural issues
95%95%
Graph-traversal
90%90%
Hash tables
85%85%
Stacks/Queues
80%80%
Difficulty Verdict
This series represents a highly demanding assessment, retaining the rigorous standard characteristic of the AQA 7517 specification. With an overall difficulty rating of 4.2 out of 5, candidates were forced to demonstrate both rapid programmatic problem-solving under tight time constraints in Paper 1 and robust technical detail in Paper 2.
Where the Marks Are
In Paper 1, the massive practical programming questions in Section D comprised 37% of the total marks, heavily penalizing candidates who could not debug their code in live conditions. Section B also demanded a robust 12-mark string validation routine. In Paper 2, high-mark essay-style questions dominated, including a 12-mark descriptive essay on CPU improvements and a complex 10-mark Assembly programming question focused on hexadecimal ASCII conversion.
Examiner notes & key calculations
- Off-By-One Indexing: In Paper 1, candidates frequently fell victim to generating out-of-bounds indices (e.g., generating 0 to 36 instead of 0 to 35 for a 6x6 board).
- Circular Queue Pointer Manipulation: Candidates repeatedly failed to handle bounds checking (i.e., checking if the queue was full) before updating front/rear pointers.
- Low-level Syntax and Shifting: Many lost marks in Paper 2's Assembly question by neglecting the immediate operand '#' prefix or misinterpreting the direction of bit shifts.
Analysis is paraphrased for study purposes. Always verify against the official examiner report and mark scheme.