> [[identify|Identified]] and [[explain|explained]] with [[justify|justification]] any limitations of the proposed solution[^1] [[limitation|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[^2]. 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 [[Stakeholders and how they relate to the solution|stakeholder research]] and [[Existing solution research|product research]]. It is common for projects to have fewer limitations than [[Essential features|essential features]]. Numbering your limitations can be helpful to quickly reference them later. ## Notes [^1]: OCR, “Computer Science H446 A Level Specification,” OCR, March 2024, 22, https://www.ocr.org.uk/Images/170844-specification-accredited-a-level-gce-computer-science-h446.pdf. [^2]: Cambridge OCR, A Level Computer Science: A Guide to Creating Concise NEA Documentation, 2026, video, 39:05, https://train.ocr.org.uk/mod/scorm/view.php?id=1893.