Complete OCR A-Level Computer Science specification revision resources. Tailored syllabus coverage with topic breakdowns, quizzes, and practice questions.
Overview
OCR A-Level Computer Science dives deep into the heart of how computers and software work, and how to solve problems through computational thinking. You'll explore the science behind the screen: from the inner workings of processors and data representation, to how networks and databases function in modern systems. The course balances theory with practical programming, encouraging you to think like a computer scientist—analysing issues, designing algorithms, and writing efficient code.
Structured around two main themes, 'Computer Systems' and 'Algorithms and Programming', the specification gives you a thorough understanding of both hardware and software. You'll study the characteristics of contemporary systems, software development methodologies, and the exchange and storage of data. Alongside, you'll develop your programming skills using a high-level language, learning to apply standard algorithms and data structures to tackle complex problems.
A standout feature is the Programming Project, where you'll independently research, design, develop, and evaluate a software solution for a real-world problem of your choice. This coursework component allows you to showcase your creativity and technical ability, producing a substantial portfolio that universities and employers highly value. Throughout the course, you'll also consider the ethical, legal, and cultural impacts of digital technology, preparing you to be a responsible digital citizen.
Why Choose OCR for Computer Science?
OCR's A-Level Computer Science offers a well-balanced mix of theory and hands-on programming, making it ideal for students who want to understand both the 'why' and the 'how' of computing. The substantial programming project (20% of the grade) gives you the freedom to create a meaningful software solution, which can be a fantastic portfolio piece for university applications or apprenticeships in tech.
The specification is highly regarded for its clarity and depth, with a logical structure that builds your knowledge progressively. Detailed teaching resources and past papers are readily available, making revision straightforward. The emphasis on computational thinking and mathematical skills also provides excellent preparation for STEM degrees, particularly Computer Science, Engineering, and Mathematics.
Compared to other boards, OCR places a stronger emphasis on the theoretical underpinnings of computer science, such as Boolean algebra, data structures, and the complexities of system architecture. This academic rigour is valued by top universities and gives you a deeper, more robust understanding that goes beyond just learning to code.
Assessment & Exam Structure
The qualification is assessed through three components: two written exam papers and a non-exam assessment. Paper 1 (Computer Systems) and Paper 2 (Algorithms and Programming) are both 2 hours 30 minutes long, each worth 140 marks and 40% of the final A-Level. Paper 1 covers the theoretical aspects of computing, while Paper 2 focuses on problem-solving, algorithms, and coding skills with a mix of short and extended response questions, including a scenario-based task. The Programming Project (non-exam assessment) is worth 70 marks, contributing the final 20%. It is internally assessed by your teacher and externally moderated by OCR. Total marks available across the course are 350.
Specification Topics
- The characteristics of contemporary processors, input, output and storage devices
- Structure and function of the processor
- Types of processor
- Input, output and storage
- Software and software development
- Systems Software
- Applications Generation
- Software Development
- Types of Programming Language
- Exchanging data
- Compression, Encryption and Hashing
- Databases
- Networks
- Web Technologies
- Data types, data structures and algorithms
- Data Types
- Data Structures
- Boolean Algebra
- Legal, moral, cultural and ethical issues
- Computing related legislation
- Moral and ethical Issues
- Elements of computational thinking
- Thinking abstractly
- Thinking ahead
- Thinking procedurally
- Thinking logically
- Thinking concurrently
- Problem solving and programming
- Programming techniques
- Computational methods
- Algorithms
- Analysis of the problem
- Problem identification
- Stakeholders
- Research the problem
- Specify the proposed solution
- Design of the solution
- Decompose the problem
- Describe the solution
- Describe the approach to testing
- Developing the solution
- Iterative development process
- Testing to inform development
- Evaluation
- Testing to inform evaluation
- Success of the solution
- Describe the final product
- Maintenance and development
Top Exam Board Tips
- Be prepared to trace the contents of registers during the Fetch-Decode-Execute cycle.
- When discussing CPU performance, always link factors like cache or clock speed to the efficiency of the FDE cycle.
- Use specific examples of storage devices (e.g., SSD vs HDD) when asked to justify their application to a problem.
- Ensure you can clearly distinguish between the roles of the control bus, address bus, and data bus.
- Use clear, technical terminology when describing register operations during the Fetch-Decode-Execute cycle.
- When discussing performance, always link the factor (e.g., cache size) to the reduction in time spent waiting for data from slower main memory.
- Be prepared to draw or label diagrams of the CPU architecture.
- Ensure you can explain how assembly language instructions map directly to the movement of data between registers and memory.
- Be prepared to compare CISC and RISC in terms of instruction sets and clock cycles
- Focus on the 'why' behind using a GPU for non-graphical tasks, such as parallel data processing
Common Mistakes to Avoid
- Confusing the roles of the MAR and MDR during the Fetch-Decode-Execute cycle.
- Failing to explain how bus width or type affects data transfer.
- Misunderstanding the difference between Von Neumann and Harvard architectures.
- Assuming GPUs are only used for graphics rendering.
- Confusing the characteristics of volatile (RAM) and non-volatile (ROM/Storage) memory.
- Confusing the roles of the Memory Address Register (MAR) and Memory Data Register (MDR).
- Failing to explain how the Control Unit manages the flow of data through the buses.
- Inaccurately describing the impact of increasing clock speed without considering thermal or physical constraints.