OCR A-Level Computer Science
Explore your course, one topic at a time.
Course 601/4911/5
Course version · 601/4911/5Version from Aug 2015Change version
Choose the version your school teaches. Your teacher can confirm which one, including for resits.
Explore your topics
6 topics
Course topics6 topics
Assessment and exam guidance
What Gets Top Grades
A*/Grade 9
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
OCR
State
1 mark
Give a single fact or term
Identify
1 mark
Name or select
Describe
2-4 marks
Account of process or features
Explain
3-6 marks
Give reasons with BUSINESS-FACING outcomes
Analyse
6-9 marks
Examine methodically showing cause→effect→outcome
Evaluate
9-12 marks
Judge, weigh up evidence, reach SYNOPTIC conclusion
Tips and common mistakes
Common Exam Mistakes
Pitfalls to avoid in your exams
- •Students often conflate agile methodologies with a lack of planning or documentation, ignoring that agile values working software over comprehensive documentation but still requires appropriate documentation and careful sprint planning.
- •A common misconception is that the waterfall model never allows any revisiting of previous stages; in practice, there can be feedback loops, but the overall progression remains linear and changes in later stages are costly.
- •Students frequently confuse system testing with acceptance testing: system testing is performed by the development team against technical specifications, while acceptance testing is performed by the client to ensure business requirements are met.
- •Many learners incorrectly believe that unit testing alone is sufficient for quality assurance, overlooking that integration and system testing catch defects that emerge from module interactions and environmental factors.
- •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).
Top Examiner Tips
Expert advice for exam success
- •When comparing methodologies, structure your answer using a clear framework such as 'planning, execution, delivery, and adaptability' to ensure balanced and comprehensive coverage.
- •Use precise technical terminology; for instance, refer to 'iterations' in agile and 'phases' in waterfall, and distinguish between 'verification' (testing against specifications) and 'validation' (testing against user needs).
- •In testing questions, always relate each level to a specific phase of development and provide a real-world example, e.g., 'during unit testing of a login module, we'd check boundary values for password length'.
- •For high-mark questions, demonstrate critical evaluation by discussing trade-offs, such as the suitability of waterfall for well-defined projects versus agile for evolving requirements, and the cost-benefit of each testing level.
- •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
Ready for a little practice?
Create your account to start practising Computer Science.
Start free
7 days Premium · Then free forever · No card, no charge