> [[describe|Described]] and [[justify|justified]] the features that make the problem solvable by computational methods, [[explain|explaining]] why it is amenable to a computational approach[^1]. This criterion poses the question of why your solution should be coded: what about it is well suited to computation and computational methods? Note that this criterion just requires description, explanation, and justification—it does not require you to perform any of the computational methods you discuss (this comes later), nor does it require you to provide a textbook-style description of computational methods. > [!info] Moderators' report > Moderators say "When discussing features that make the problem solvable by computational methods, we are looking for candidates to describe how their solution is better as a computerised solution rather than as something paper based"[^2]. They warn against merely describing computational methods on the specification, saying that such methods "must be applied to the given problem"[^2]. The mark scheme's focus is on describing and justifying the **features of your problem** and why the problem overall is amenable to computational approaches, rather than describing computational approaches and methods themselves. Some description of computational methods may be helpful when justifying suitability though you can assume the person reading your write-up is familiar with computational approaches and methods. There is a big difference between talking about applying computational methods to the process of completing your NEA compared to the features of the problem you are solving. The mark scheme only rewards the latter. The fact that you can use abstraction and decomposition as project management tools is irrelevant. What the mark scheme wants is for you to describe the features of the thing you are making that are well-suited to computational approaches. If you are making a game and are not sure where to begin describing and justifying features that are suitable for computational solving, this is a good read for some inspiration: [Board Game Vs Video Game Design](https://fourtatogames.medium.com/board-game-vs-video-game-design-7e3851f7167d)—but bear in mind the difference between features of the process of making a game versus features of games themselves. ## 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]: OCR, “A Level Computer Science Moderators’ Report H446/03/04 Summer 2024 Series,” OCR, 2024, 6, https://www.ocr.org.uk/Images/726389-moderators-report.pdf.