Use OCR AS Level Computer Science H046 past papers, mark schemes, examiner reports, and grade boundaries to practise the exact question types that appear in the real exam.
Computer Science H046 past papers are strongest when each paper is reviewed for technical terminology, logic steps, tracing accuracy, and method clarity, then the next paper is used to test whether loose terminology, skipped logic, or weak trace-table control is still costing marks.
Latest year
Coverage
Years listed
Subject code
Computer Science past papers that reflect the real paper
Mark past papers for the details that matter
Turn each past paper into the next gain
Start with pseudocode questions, theory questions, trace tables, and full past papers so your revision matches the actual paper balance and demands.
Use mark schemes and examiner reports to check technical terminology, logic steps, tracing accuracy, and method clarity after every paper.
Use the result of one paper to repair loose terminology, skipped logic, or weak trace-table control before the next timed attempt.
Use these follow-up resources when the next revision step needs more focused practice, worked support, or faster recall repair.
Find recent Computer Science papers, mark schemes, examiner reports, and direct links to related subject archives. Start with the latest session first, mark it carefully, then work backwards through older years as timing and answer quality improve.
Start with recent material, mark it carefully, and move into focused follow-up only where marks are still being lost.
Begin with newer pseudocode questions, theory questions, trace tables, and full past papers so the first past papers reflect current wording, paper balance, and examiner expectations.
Review technical terminology, logic steps, tracing accuracy, and method clarity rather than looking only at the final score.
Use the pattern in your past papers to identify whether loose terminology, skipped logic, or weak trace-table control is the main mark-loss area.
Use another recent paper to check whether the same weakness still appears once the repair work is done.
Computer Science and IT past papers reward exact terms, not approximate everyday language.
Past papers show whether students can follow algorithms, variables, and program flow step by step.
Use mark schemes to check whether systems, networks, data, or security concepts are being applied properly.
Full papers matter because command words and layered explanations still decide many marks.
Computer Science and IT past papers are especially useful because they combine short factual recall with longer algorithmic or systems explanations. Many marks are lost when a student knows the topic but cannot express the method or trace it cleanly.
The most productive review cycle is to finish a recent paper, mark the logic and terminology carefully, and then return to another past paper to check whether those same coding, tracing, or systems weaknesses still appear.
Start with the newest pseudocode questions, theory questions, trace tables, and full past papers first, then work backwards once the latest past papers feel more controlled under time pressure.
Use the mark scheme and examiner report together to review technical terminology, logic steps, tracing accuracy, and method clarity. That review is where the real improvement usually starts.
List the marks lost across the paper, decide whether loose terminology, skipped logic, or weak trace-table control was the main problem, and repair that issue before the next full past paper.
Yes. After the latest past papers are complete, older past papers are still useful for repetition, wider coverage, and testing whether the same mistakes keep repeating.
Use these links to continue with the same subject, qualification level, or a supporting study tool.
Open 2024 papers
Jump straight to the newest question papers and mark schemes.Use these only when free papers, mark schemes, and reports have already shown the exact gap you want to fix.