Identified and explained with justification any limitations of the proposed solution [1].
Limitations are any ideas or features (possibly identified in your research) that you deliberately choose not to include in your solution.
When justifying not doing something, consider what the most important factors are in its exclusion: does another feature take priority? Why is this feature less important?
Be mindful that you have a lot of time to complete the NEA when thinking about these justifications—lack of time or coding ability is not an appropriate reason to list something as a limitation [1]. Your list of limitations should reflect the product you plan to create, not you as a developer nor the circumstances of your work.
There is no correct number of limitations. Your limitations might be informed by your stakeholder research and product research. It is common for projects to have fewer limitations than essential features.
Numbering your limitations can be helpful to quickly reference them later.
Specification links
References
-
[1]Cambridge OCR 2026. A Level Computer Science: A Guide to Creating Concise NEA Documentation.
-
[2]Cambridge OCR 2024. A Level Specification Computer Science H446. Cambridge OCR.