Computer Science
Specification: 601/4911/5
The OCR A-Level Computer Science specification covers 6 topics with 75 learning objectives (601/4911/5). Use the topic browser below to explore subtopics, exam tips, common mistakes, and key terminology for each area of the course.
Starting OCR A-Level Computer Science this term? The whole specification is below, unit by unit.
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.
6
Topics
75
Objectives
76
Exam Tips
78
Pitfalls
Key Features
- Write and debug programs
- Design efficient algorithms
- Understand computer systems
- Develop computational thinking
About OCR A-Level Computer Science
OCR A-Level Computer Science (H446) provides a deep dive into the fundamental principles of computation, equipping you with a robust understanding of how computer systems work and are programmed. This specification covers both theoretical concepts, such as algorithms and data structures, and practical application through programming, fostering analytical and problem-solving skills essential for higher education and careers in technology.
The course is structured to build your knowledge progressively, moving from foundational computing principles to advanced topics like object-oriented programming, networks, and cyber security. You'll explore the impact of computing on society and develop an appreciation for the ethical considerations involved, preparing you to be a responsible and innovative contributor to the digital world.
Assessment Structure
The OCR A-Level Computer Science qualification is assessed through three components: two written exams and one practical project. 'Paper 1: Computer Systems' (01) is a 2-hour 30-minute written exam worth 140 marks, contributing 40% of the total A-Level. 'Paper 2: Algorithms and Programming' (02) is also a 2-hour 30-minute written exam, worth 140 marks and contributing 40%. The final component, 'Programming Project' (03/04), is a non-exam assessment (NEA) where students develop a practical solution to a user-defined problem, worth 70 marks and contributing 20% of the total qualification.
Why Choose OCR?
- OCR's specification (H446) is highly respected by universities and employers for its rigorous academic content and strong emphasis on practical programming skills, ensuring you gain relevant and sought-after expertise.
- The 'Programming Project' (NEA) component allows you to apply your knowledge to a real-world problem of your choosing, providing a valuable opportunity to demonstrate independent problem-solving and software development abilities.
- OCR's clear and well-structured content, supported by extensive resources, makes complex computer science concepts accessible, helping you build a solid foundation and achieve your full potential.
Frequently Asked Questions
Assessment Objectives
Demonstrate knowledge and understanding of the principles and concepts of computer science, including abstraction, logic, algorithms and data representation
Apply knowledge and understanding of the principles and concepts of computer science, including to analyse problems in computational terms
Design, program and evaluate computer systems that solve problems, making reasoned judgements about these and presenting conclusions
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 or select
Account of process or features
Give reasons with BUSINESS-FACING outcomes
Examine methodically showing cause→effect→outcome
Judge, weigh up evidence, reach SYNOPTIC conclusion
Common Exam Mistakes
Pitfalls to avoid in your exams
- •Confusing volatile (RAM) with non-volatile storage (SSD, HDD) when discussing primary vs secondary storage, especially in the context of 'memory'.
- •Stating that SSDs have moving parts or are more susceptible to mechanical failure than HDDs, showing a fundamental misunderstanding of solid-state technology.
- •Assuming optical storage (CD, DVD, Blu-ray) uses magnetic principles; failing to recognise the role of laser reflection on pits and lands.
- •Describing output devices solely by their physical appearance without explaining the underlying technology (e.g., stating 'a monitor displays images' without mentioning LCD/OLED, resolution, or refresh rate).
- •Confusing RISC as having more instructions than CISC due to the word 'reduced'
- •Believing GPUs are only used for graphics processing and not for general-purpose parallel computation
- •Assuming that doubling the number of processor cores always results in double the performance
- •Failing to distinguish between multicore systems and parallel computing systems, treating them as identical
Top Examiner Tips
Expert advice for exam success
- •When comparing storage types, construct a mental or written table with rows for type (magnetic/optical/solid state) and columns for capacity, portability, speed, durability, and cost. Then justify the choice for given scenarios like a camera (small, durable, low power → SD card) or a data centre (high capacity, fast → enterprise HDD or SSD).
- •For input/output devices, avoid generic lists. Instead, structure your answer by category (manual vs automatic input, visual vs physical output) and always state a typical use case, e.g., 'A barcode reader uses a laser or camera to scan codes, commonly used in retail for fast, error-free price lookup.'
- •Use precise technical vocabulary: say 'actuator' not 'motor', 'refresh rate' not 'speed' for monitors, and 'seek time' or 'random access time' for storage performance to demonstrate depth.
- •When comparing RISC and CISC, always support your answer with specific technical details such as instruction pipelining, register usage, and clock cycles per instruction
- •Use precise terminology like 'SIMD', 'MIMD', 'hyper-threading', and 'concurrency' to demonstrate in-depth knowledge
- •In longer answers, structure your response to first describe, then compare, and finally evaluate the real-world applications of each processor type
- •When describing the fetch-execute cycle, use a stepwise approach and clearly indicate register transfers (e.g., PC → MAR) to demonstrate understanding of data movement and control flow.
- •For comparison questions on architectures, construct a table with criteria like memory space, bus complexity, common applications, and security implications to ensure all marking points are systematically addressed.
Specification Topics
Ready to master Computer Science?
Start practising with AI-powered quizzes tailored to your OCR A-Level specification.
7 days of full Premium · No card required · Free plan forever after