Skip to topic
    ← Back to course topics

    Research the problem — OCR A-Level Computer Science

    Research the problem explained

    Research the problem covers 3 specification points, including (a) Research the problem and solutions to… and (b) Describe the essential features of a….

    Read the full explanation

    Open a point below for its explanation and revision guidance.

    (a) Research the problem and solutions to similar problems to identify and justify suitable approaches to a solution.

    This criterion asks you to investigate before you design. First, research the problem itself: identify the user, the inputs, the outputs and the constraints, and record them in your own words. Second, research solutions to similar problems, such as existing apps or published algorithms, noting what each does well and where it falls short. Third, identify suitable approaches for your own solution, for example choosing a database-backed design over a flat file for a stock system. Finally, justify each approach by linking it to the requirements and to the strengths you observed. A justification shows why an approach is suitable, not merely that it exists.

    (b) Describe the essential features of a computational solution explaining these choices.

    Describe the essential features of a computational solution, then explain the choices behind them. Essential features are the elements the solution must have to meet the problem: inputs, processing, outputs, data structures, algorithms and the user interface. Describe each one clearly enough that a reader could recognise it in your design, focusing on what is necessary rather than cosmetic. For each feature, explain why you chose it, linking the reason to your research and to any alternatives you rejected. For example, a sorted list supports binary search, which suits a large, frequently queried dataset. Explanations must be specific to your problem.

    (c) Explain the limitations of the proposed solution.

    This statement asks you to explain the limitations of your proposed solution: weaknesses, constraints or situations where it would not work well or fully meet the needs identified in your research. A limitation is not simply a missing feature. For each one, state it, describe the condition that causes it, and explain its effect on users or the organisation. For example, a proposed booking system that stores all data on one local computer has a limitation: a hardware failure could lose every booking, leaving staff unable to recover them. Linking cause to consequence, and tying it to your research, earns credit.

    Your focus

    1. Identify the users, inputs, outputs and constraints of a problem through research.
    2. Compare the strengths and weaknesses of solutions to similar problems.
    3. Justify selected approaches with reference to requirements and evidence.
    Show all 9 objectives
    1. Identify the essential features of a computational solution.
    2. Describe the role of each essential feature in meeting the problem.
    3. Explain the reason for each design choice with reference to requirements.
    4. Identify a limitation of a proposed solution from a given design description.
    5. Explain the cause and effect of a limitation in a proposed system.
    6. Distinguish a limitation of the solution from a limitation of the original problem.

    Research the problem exam tips

    Marking Points
    • Identifies the users, inputs, outputs and constraints of the problem from the research before proposing any approach.
    • Investigates at least one solution to a similar problem and records what it does well and where it falls short.
    • Identifies approaches that suit the stated problem rather than listing generic techniques.
    • Justifies each selected approach by linking it to the requirements and to the evidence gathered.
    • Keeps research sources traceable so that the reader can check where each finding came from.
    • Identifies the essential features of the solution, covering inputs, processing, outputs, data structures, algorithms and user interface where they apply.
    • Describes each essential feature in enough detail that its role in meeting the problem is clear.
    • Distinguishes essential features from optional or cosmetic features.
    • Explains the reason for each choice by linking it to the research and the requirements.
    • Gives a specific example of a choice and its effect on performance, usability or suitability for the problem.
    • Identifies a genuine limitation of the proposed solution rather than a general weakness of computing in the area.
    • Describes the condition or circumstance under which the limitation arises.
    • Explains the consequence of the limitation for users, data or the organisation.
    • Links the limitation to a need or finding from the research carried out for the problem.
    • Explains a second, distinct limitation where this strengthens the answer rather than repeating the first.
    Examiner Tips
    • 💡Write a short requirements list before researching solutions so that you have a clear benchmark for comparison.
    • 💡For each approach, write one sentence on why it fits the problem and one sentence on its main drawback.
    • 💡Keep a source log with the name, date and key finding of each item so that you can refer back to it in your write-up.
    • 💡Use a table with columns for feature, description and reason so that no essential element is missed.
    • 💡Test each feature against the requirements: if the problem cannot be met without it, it is essential.
    • 💡Name specific structures or algorithms and state why each suits the data volume or user need.
    • 💡Structure each limitation as cause, condition and consequence so that every point is complete.
    • 💡Check each limitation against your research findings so that the explanation is specific to your problem.
    • 💡Avoid generic limitations that would apply to any solution; use details from your own proposal.
    Common Mistakes
    • Describes a similar product without stating its strengths or weaknesses; evaluate each solution against the problem.
    • Lists popular techniques with no link to the user's problem; relate each technique to a specific requirement.
    • Asserts that an approach is good without citing evidence; name the requirement or observed strength that supports it.
    • Lists features without saying what each one does; state the role of each feature in meeting the problem.
    • Gives generic explanations, such as calling an algorithm efficient; name the property and explain why it suits this problem.
    • Treats cosmetic details such as colour schemes as essential features; keep the focus on what the solution must do.
    • Omits the reason for a feature; add a justification linked to the requirements.
    • Lists a missing feature without explaining why its absence matters to the user; state the consequence as well.
    • Describes limitations of the original problem or existing system instead of the proposed solution; keep the focus on the design you specified.
    • Offers a vague weakness such as slowness without saying when or why it occurs; name the condition and the effect.