OCR Project: Analysis, Scope and Authenticity

The project contributes 70 marks and 20% of the A-level. Analysis has 10 marks, design 15, development and testing 25, and evaluation 20. Components 03 and 04 are moderation submission routes for the same programming-project content. They are not alternative topics that remove the need for a project.

Choose a meaningful problem with enough computational demand for appropriate decomposition, algorithms and iteration. A title or genre does not guarantee a mark band. Consider available time, data, user access, language experience and technical risk. An oversized idea can be refined to a coherent core; adding unrelated features solely to appear complex can make completion and evaluation harder.

Identify stakeholders and explain how the proposed outcome serves their actual needs. Research comparable approaches to discover useful ideas, limits and trade-offs, then justify the features relevant to this problem. A list of copied screenshots is weaker than an explanation connecting observations to requirements. Represent important data and constraints early.

Define measurable success criteria using observable outcomes and stated conditions. “Easy to use” needs a concrete task and evidence plan; “fast” needs a workload and meaningful target. Explain boundaries and omissions so evaluation can distinguish an unmet commitment from a feature deliberately outside scope. Include justified hardware and software needs where relevant, rather than a generic catalogue of devices.

OCR lists acceptable project languages in appendix 5e and provides a centre route for considering other choices. The specification requires a suitable graphical interface; exceptional command-line cases need prior OCR authorisation through the centre under the project-setting guidance. A console example in a lesson is therefore not automatically a sufficient final project interface. Confirm suitability with your teacher early.

Keep evidence of your own analysis, decisions, code and revisions. Follow current OCR, JCQ and centre rules for outside help, sources and AI; acknowledge permitted material as required. Naming a source does not make copied assessed thinking your independent achievement. These lessons explain preparation through small generic examples, rather than supplying a complete project to submit. Do not invent research conversations or user needs to fill a report.

Attempt the task before opening its worked response. Record each change of state, explain the rule used, and check the result against the original requirements. Code examples labelled Python 3 use that language’s conventions; pseudocode states its own assumptions.