About the exam
WJEC GCSE Computer Science Exam structure
An independent study guide for the current WJEC Made-for-Wales GCSE Computer Science qualification, aligned to Understanding Computer Science and the annual pre-release Computer Programming assessment.
Issuer and path
WJEC GCSE Computer Science Study Guide is administered through WJEC CBAC Ltd. Check official resources before booking, retesting, or relying on a stale requirement.
Unit 1: Understanding Computer Science
50 scored + 0 pretest
Computer architecture, data, communication, algorithms, software, logic, operating systems and systems development.
Unit 2: Computer Programming
50 scored + 0 pretest
Investigation, design, Python implementation, testing, refinement and evaluation in an annual pre-release context.
Before using Unit 2 materials
Confirm qualification code, unit, assessment year, medium and the live brief. Follow the current WJEC Portal, Python IDLE, file, restricted-environment and Surpass instructions; public sample files do not replace the annual assessment pack.
Official Outline Coverage Map
Coverage is mapped to official outline item counts so content depth can be checked without hard-coding a single exam.
| Topic | Official outline items | Your questions | Your flashcards | Confidence |
|---|---|---|---|---|
| 1.1 Computer Architecture | 0 | 45 | 6 | Strong |
| 1.2 How Systems Are Structured and Function | 0 | 55 | 6 | Strong |
| 1.3 How Systems Communicate | 0 | 55 | 6 | Strong |
| 1.4 Algorithms | 0 | 40 | 6 | Strong |
| 1.5 Software | 0 | 45 | 6 | Strong |
| 1.6 Logical Operations | 0 | 20 | 6 | Strong |
| 1.7 Operating Systems | 0 | 20 | 6 | Strong |
| 1.8 Systems Development Life Cycle | 0 | 21 | 6 | Strong |
| 2.1 Investigation | 0 | 60 | 6 | Strong |
| 2.2 Design | 0 | 60 | 6 | Strong |
| 2.3 Implementation | 0 | 120 | 6 | Strong |
| 2.4 Testing, Refinement and Evaluation | 0 | 60 | 6 | Strong |
How to use this guide
How to study WJEC GCSE Computer Science
Learn the computing principle, apply it to the named system or scenario, trace the data and control flow, and test the result against requirements.
1. Identify the unit and requirement
Locate the task in Unit 1 or Unit 2, read the command word and name the user, input, process, output, constraint or system property required.
2. Choose the representation
Select exact terminology, a calculation, truth table, trace table, pseudocode, structure diagram, data model or Python construct.
3. Trace data and control
Follow values through storage, transmission, conditions, loops, subroutines, files and events, including boundaries and failure paths.
4. Implement or explain precisely
Use readable modular steps or code, connect each choice to the scenario and keep types, interfaces, validation and security explicit.
5. Test and judge
State expected evidence, compare it with actual behaviour and evaluate correctness, efficiency, usability, robustness and fitness for purpose.
Made-for-Wales unit map
Move from computing principles to a complete Python solution
Build Unit 1 systems and algorithm knowledge, then apply investigation, design, implementation, testing and evaluation to Unit 2 scenarios.
Computer Architecture
Processors, memory, buses, peripheral devices, secondary storage and performance.
Choose a topic to open below
Data, File Structures and Automated Systems
Representation, storage and compression of data, data and file structures, and automated systems.
Choose a topic to open below
Networks, Cybersecurity and Privacy
Network infrastructure and communication, threats, protection, personal data and privacy.
Choose a topic to open below
Algorithms and Software
Algorithmic thinking, programming principles, software development and program construction.
Choose a topic to open below
Logic, Operating Systems and Systems Development
Logical operations, operating-system services and the wider systems development life cycle.
Choose a topic to open below
Programming Investigation and Design
Decomposition, abstraction, pattern recognition, requirements, algorithms, data models and interface design.
Choose a topic to open below
Python Implementation
Python 3 program construction, data structures, files, subroutines, validation, authentication and Tkinter interfaces.
Choose a topic to open below
Testing, Refinement and Evaluation
Test planning, evidence-led debugging and improvement, efficiency and evaluation against requirements.
Choose a topic to open below
1.1 Computer Architecture
Explain how processor, memory, buses, peripherals and storage cooperate, and compare architectures and devices for a stated use.
Key rules
Rule 1
Motherboard, PSU, CPU, GPU, expansion cards, cooling, ports, fetch-decode-execute, registers, cache, clock speed and cores
Exam cue: Identify the current WJEC unit, the command word and whether the task asks for knowledge, application or computational analysis.
Rule 2
Input and output peripherals, sensors, actuators, energy efficiency and hardware lifecycle impacts
Exam cue: Trace data, addresses and control signals through a complete fetch-decode-execute cycle before judging performance or device suitability.
Rule 3
RAM, ROM, flash, cache, virtual memory and optical, magnetic, solid-state and cloud storage trade-offs
Exam cue: Use precise terminology, trace inputs and state changes, and test the answer against the data, scenario or program behaviour.
Common traps
Treating clock speed, core count or storage capacity as the only performance factor without considering cache, workload and other constraints.
Prevention: Avoid generic descriptions, unchecked traces and cross-board assumptions; make every answer depend on the named data, system, algorithm or scenario.
Importing the legacy WJEC structure, a different board's content or a Foundation/Higher tier assumption.
Prevention: Use qualification code 3460QS or 3460CS and the current two-unit untiered structure; do not import a legacy or cross-board route.
Giving a generic description without applying it to the named system, data set, algorithm or pre-release scenario.
Prevention: Practice cannot replace the annual live brief, specified Python environment, clean-copy rule, restricted examination files or Surpass upload process.
Memory anchors
Fetch-decode-execute cycle
The processor repeatedly fetches an instruction, decodes it and executes the required operation.
Registers
Very small, fast processor locations that hold instructions, addresses, data and intermediate results.
Cache
Fast memory close to the processor that stores frequently needed instructions and data.
RAM and ROM
RAM is volatile working memory; ROM is non-volatile memory that stores fixed instructions such as firmware.
Sensor and actuator
A sensor collects input from the environment; an actuator produces a physical output.
Secondary storage trade-off
Choose a device by balancing capacity, access speed, portability, durability, reliability and cost.
Next best moves
Quick check-up
Use a short quiz to confirm the rule pattern is actually sticking.
Check-up Questions
During fetch, which register holds the address of the next instruction?
After an instruction is fetched, what is the processor's next stage?
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.
WJEC GCSE Computer Science Made-for-Wales qualification page
The current qualification hub for specification, sample materials, teaching guidance and programming resources.
WJEC GCSE Computer Science specification
Approved Version 3 specification for teaching from September 2025 and award from Summer 2027.
Unit 1 sample assessment materials
Official digital-assessment sample material for Understanding Computer Science.
Unit 2 sample assessment materials
Official sample on-screen examination material for Computer Programming.
Unit 2 sample pre-release materials
Public sample showing the information-for-candidates and scenario format; the live annual brief is issued through the WJEC Portal.
WJEC GCSE Computer Science delivery guide
Official teaching and sequencing support for the two-unit Made-for-Wales qualification.
Made-for-Wales first assessment opportunities
WJEC schedule confirming Summer 2026 for Computer Science Unit 1 and Summer 2027 for Unit 2.
FAQ
Common WJEC GCSE Computer Science questions
Is this an official WJEC resource?
No. This is an independent guide aligned to current public WJEC documents. The live specification, annual pre-release brief, examination files, timetable and centre instructions remain authoritative.
Who is this qualification for?
It is the Qualifications Wales-regulated Made-for-Wales GCSE Computer Science and is not available to centres in England. This module serves Wales only and must not be mixed with another board's specification.
When is the current specification taught and assessed?
Teaching began in September 2025. Unit 1 was first available in Summer 2026. Unit 2 and the first full qualification award are available in Summer 2027. It is primarily designed as a two-year Years 10-11 programme.
Is this the legacy WJEC GCSE Computer Science?
No. The current English-medium qualification code is 3460QS, not legacy 3500QS. The current Made-for-Wales qualification has two equally weighted digital units and a Year 10 pre-release brief for the Unit 2 Python assessment.
How is Unit 1 assessed?
Understanding Computer Science is an 80-mark digital examination lasting 1 hour 30 minutes and worth 50%. It uses objective responses, short answers and extended answers and was first available in Summer 2026.
How does Unit 2 work?
Computer Programming is an 80-mark, two-hour on-screen examination worth 50%, set and marked by WJEC. Tasks apply investigation, design, implementation, testing, refinement and evaluation to a scenario in an annual pre-release brief.
When can candidates see the Unit 2 pre-release brief?
It is available to centres through the WJEC Portal in September of Year 10. Centres choose the distribution date, but it must be during Year 10. Candidates sit the assessment in Year 11, receive a clean copy and may not bring prompts or notes.
Which programming environment is required?
Candidates need Python 3 and must use the Python IDLE version specified in the live pre-release brief and examination instructions. Public materials use standard Python IDLE and Tkinter. Centres may use another IDE for teaching, but not as a substitute for the specified examination environment.
Is there a Foundation or Higher tier?
No. The qualification is not tiered and reports grades A* to G, with U for performance below the minimum award standard.
What is the terminal rule?
Pre-16 candidates must complete at least 40% of the qualification in the cash-in series. Post-16 candidates do not have a terminal rule. Resit rules differ, so current WJEC entry guidance should be checked before entries are made.
Can static practice reproduce a full Unit 2 mock?
No. Static practice can develop content, tracing, design, Python and testing skills, but it cannot reproduce the annual secure scenario, specified Python IDLE environment, examination files, Surpass restrictions or upload workflow. Full-mock mode is therefore disabled.
Are the 601 planned questions included?
Yes. The bank contains 601 original single-answer questions split 301 for Unit 1 and 300 for Unit 2. Python output and error items are executed during QA; static practice builds public specification skills without reproducing the controlled annual assessment.