> [[considered|Considered]] maintenance issues and limitations of the solution[^1] When describing limitations and maintenance issues, you could tabulate them, write them in bullet points, or write them in prose. However, OCR say that consideration of limitations and maintenance issues is "generally better done by using short statements and paragraphs and doesn't necessarily suit a tabulated approach"[^2]. That the higher mark bands expect 'consideration' means that an [[evaluate|evaluative]] approach is important rather than just describing everything wrong with your solution[^2] When considering limitations and maintenance issues, you might discuss: - their effect; and - their impact on the project as it stands[^2]. You should focus on limitations and maintenance issues with the solution, not you as a developer—so lack of time or coding ability should not be included in your discussion[^2] You could discuss the following if they are appropriate: - code maintenance issues; - ease of future development; - server maintenance; - updates; and - backups[^2]. The higher mark bands require you to go beyond discussion of limitations and maintenance issues and to provide [[Comments on future development including limitations and maintenance issues|comments on future development including limitations and maintenance issues]]. ## Notes [^1]: OCR, “Computer Science H446 A Level Specification,” OCR, March 2024, 25, 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.