Specify the proposed solution — OCR A-Level Computer Science
Specify the proposed solution explained
Specify the proposed solution covers 2 specification points, including (a) Specify and justify the solution… and (b) Identify and justify measurable success….
Read the full explanation
Open a point below for its explanation and revision guidance.
(a) Specify and justify the solution requirements including hardware and software configuration (if appropriate).
This statement asks you to specify your solution's requirements, justify them, and include hardware and software configuration where appropriate. To specify is to state each requirement in testable form, such as storing records for up to 500 customers, not a vague aim like being easy to use. To justify is to explain why each requirement is needed, linking it to research or a user need. The configuration names the processor, memory, storage, operating system, language or database required. It is included only if appropriate: a standalone program may need little beyond a standard computer, while a web system needs a server and browser support. Every component should trace back to a stated requirement.
(b) Identify and justify measurable success criteria for the proposed solution.
This statement asks you to name measurable success criteria for your proposed solution and to justify each one. A success criterion is a condition that, if met, shows the solution meets its requirements. Measurable means the criterion can be checked with a number, a yes or no test, or an observable result. For a revision timetable app, 'easy to use' cannot be checked, but 'a new task can be added in three taps or fewer' can. Identify each criterion from the requirements in your specification rather than from features you happened to build. Then justify it: explain why meeting the criterion shows the solution is successful, and state how you will test it, for example with a test plan that records expected and actual results for each criterion. Keep every criterion linked to the proposed solution, so an examiner can see how your planned requirements will be judged.
Your focus
- Specify testable requirements for a proposed solution from a research summary.
- Justify each requirement by linking it to a research finding or user need.
- Select appropriate hardware and software configuration for a stated set of requirements.
Show all 6 objectives
- Identify at least three measurable success criteria for a proposed solution.
- Justify each criterion by explaining how meeting it shows the solution is successful.
- Describe a planned test that would show whether each criterion has been met.
Specify the proposed solution exam tips
Marking Points
- Lists solution requirements that are specific, clear and testable rather than vague aims.
- Gives a justification for each requirement by linking it to a research finding or user need.
- States the hardware configuration needed, such as processor, memory and storage, where this is appropriate to the solution.
- States the software configuration needed, such as operating system, programming language or database, and justifies each choice.
- Explains the reason behind a configuration choice rather than only naming components.
- Sets each criterion as a measurable condition, using a number, threshold or observable outcome.
- Links each criterion to a specific requirement in the proposed solution.
- Justifies each criterion by explaining what meeting it shows about the solution's success.
- Describes how each criterion will be tested, such as through a test plan or user trial.
- Avoids subjective criteria that cannot be checked, such as 'looks good'.
Examiner Tips
- 💡Write each requirement as a numbered statement, then add its justification beneath it.
- 💡Decide early whether hardware and software configuration are appropriate, and say briefly why if they are not.
- 💡Make every component traceable to a requirement so a reader can see why each choice was made.
- 💡Write each criterion as one sentence containing a threshold, then check that a tester could measure it without guessing.
- 💡Give one justification per criterion, linking it to a named requirement in your specification.
- 💡Cross-check your criteria list against your requirements list and remove any criterion that has no matching requirement.
Common Mistakes
- Lists vague requirements such as a user-friendly interface without measurable detail; rewrite each one as a testable statement.
- Specifies hardware and software without justifying why each item is needed for a stated requirement.
- Ignores whether configuration is appropriate, either omitting a needed configuration or adding unnecessary hardware detail; decide and state the reason briefly.
- Lists subjective criteria such as 'user-friendly'; replace each with a testable measure, such as a maximum number of steps.
- Gives criteria without any justification; add a sentence explaining why meeting the criterion shows success.
- Identifies features the solution already has rather than requirements; derive criteria from the requirements in the specification.
- Names criteria that are never tested; include a planned test for every criterion.