Computer Science
Specification: WJEC-GCSE-Computer-Science
The WJEC GCSE Computer Science specification covers 4 topics with 10 learning objectives (WJEC-GCSE-Computer-Science). Use the topic browser below to explore subtopics, exam tips, common mistakes, and key terminology for each area of the course.
Computer Science develops your understanding of how computers work and how to program them effectively. You'll learn algorithms, data structures, systems architecture and develop practical programming skills.
4
Topics
10
Objectives
105
Exam Tips
106
Pitfalls
Key Features
- Write and debug programs
- Design efficient algorithms
- Understand computer systems
- Develop computational thinking
About WJEC GCSE Computer Science
WJEC GCSE Computer Science is a comprehensive qualification designed to introduce students to the fundamental principles of computer science, including computational thinking, programming, and the impact of digital technology on society. It is suitable for students who wish to develop a deep understanding of how computers work and how to create software solutions.
This qualification develops key industry skills such as problem-solving, logical reasoning, and programming in Python or other high-level languages. Employers highly value these skills as they are essential for careers in technology, engineering, and data science.
The course maps directly to real-world career paths such as software development, cybersecurity, and IT consultancy, and provides a strong foundation for further study at A-level or in vocational qualifications like BTEC Computing.
Assessment Structure
The WJEC GCSE Computer Science qualification is assessed through two external examinations: Unit 1 (Understanding Computer Science) is a written exam worth 50% of the total grade, covering hardware, software, data representation, and ethical issues. Unit 2 (Computational Thinking and Programming) is an on-screen exam worth 50%, focusing on algorithms, programming constructs, and problem-solving. There is no coursework component, but students must complete a non-exam assessment (NEA) that involves a programming project, which is internally assessed and externally moderated, contributing to the practical skills element.
Why Choose WJEC?
- WJEC offers a clear and structured specification that balances theoretical knowledge with practical programming skills, making it accessible for a wide range of learners.
- The on-screen assessment for Unit 2 allows students to demonstrate their programming ability in a realistic environment, directly testing their coding and problem-solving skills.
- WJEC provides extensive support materials, including past papers, mark schemes, and online resources, helping students and teachers prepare effectively.
Frequently Asked Questions
Assessment Objectives
Demonstrate knowledge and understanding of the key concepts and principles of computer science
Apply knowledge and understanding of key concepts and principles of computer science
Analyse problems in computational terms: • to make reasoned judgements • to design, program, evaluate and refine solutions
What Gets Top Grades
Knowledge & Understanding
Demonstrates comprehensive and accurate knowledge
- Uses correct subject-specific terminology
- Shows detailed understanding of concepts
- Makes accurate connections between topics
- Demonstrates depth beyond surface-level knowledge
Application
Applies knowledge effectively to new contexts
- Selects relevant knowledge for the question
- Adapts understanding to unfamiliar scenarios
- Uses examples appropriately
- Shows awareness of context
Analysis & Evaluation
Develops sophisticated analytical arguments
- Constructs logical chains of reasoning
- Considers multiple perspectives
- Weighs evidence to reach justified conclusions
- Acknowledges limitations and nuances
Key Command Words
Give a single fact or term
Name, select, or recognise
Set out main features briefly
Give an account of what something is like or what happens
Give reasons with developed cause→effect chains
State similarities AND differences (both required)
Examine in detail showing cause→effect→consequence chains
Weigh up BOTH sides, reach JUSTIFIED conclusion
Make judgments about importance with justification
Show formula→substitution→calculation→answer with units
Common Exam Mistakes
Pitfalls to avoid in your exams
- •Confusing a stub with the actual, fully functional component it represents.
- •Failing to understand that a stub is a temporary placeholder for testing or development.
- •Not being able to provide a practical example of when a stub would be used.
- •Overlooking the need for stubs to accurately mimic the expected behaviour of the real component.
- •Confusing stubs with mock objects or the actual components they are designed to simulate, failing to grasp their temporary and controlled nature.
- •Overlooking the holistic nature of E2E testing, focusing only on individual components rather than the complete system flow.
- •Struggling to provide concrete, practical examples of when and why a stub would be implemented in a real-world development scenario.
- •Not differentiating between unit testing (testing individual modules) and E2E testing (testing the entire system), and where stubs fit into the broader testing strategy.
Top Examiner Tips
Expert advice for exam success
- •Focus on understanding the role of a stub in simplifying complex testing scenarios, rather than its technical implementation.
- •Be prepared to explain why stubs are useful, particularly in situations where parts of a system are still under development or are external.
- •Use clear, concise language to define and describe the concept, avoiding jargon where possible or explaining it if used.
- •Think about a simple system (e.g., an online shop) and how you might test it if the payment gateway or inventory system wasn't ready – this helps illustrate the stub concept.
- •Emphasise practical application: When discussing E2E testing and stubs, think about a simple program or system and how these concepts would apply to its development and testing phases.
- •Clearly distinguish between *what* E2E testing aims to achieve (validating full system flow) and *what* a stub is (a placeholder for a part), focusing on their distinct roles.
- •Use clear, concise language and provide simple analogies (e.g., a stand-in actor for a missing actor in a play rehearsal) to explain complex concepts like stubs.
- •Structure your answers by defining the term, explaining its purpose, and then providing a clear, relevant example to illustrate your understanding.
Specification Topics
Ready to master Computer Science?
Start practising with AI-powered quizzes tailored to your WJEC GCSE specification.
Get Started Free