Loading...
A reviewer needs to understand the structure and quality of the programmed solution. Present concise evidence of the important design and implementation decisions rather than a volume of unexplained screenshots.
What you'll be able to do
Use appropriate descriptions, diagrams and pseudocode to show the data model, difficult algorithms, component responsibilities and interfaces. A third party should understand how the core solution is structured without having to reconstruct every decision from the final listing.
Design can be refined during implementation. Record meaningful changes and why evidence led to them, rather than inventing a fictional once-only sequence. A user-interface image can explain a screen but does not replace a description of the underlying calculation or data relationships.
The technical solution includes completeness and demonstrated technique. In the specification’s allocation, 15 marks concern completeness and 27 techniques, making 42 in total. Evidence should show relevant functionality working and make important program sections easy to locate.
Use meaningful identifiers, clear modules, coherent responsibilities and explicit interfaces. Defensive checks, suitable exception handling and controlled dependencies support robust code. Comments are most useful when they explain a non-obvious decision; repeating every line in prose does not itself show quality.
The example technical-skill tables illustrate levels of demand rather than guaranteeing a mark whenever a named structure appears. Proficiency, appropriateness, coding quality and effectiveness matter. A superficially complicated feature that does not work can be weaker evidence than a well-designed justified technique.
A task below the required standard can restrict marks under the specification’s rules, so check suitability early through the centre’s process. Keep a reproducible way to run the solution with required dependencies and suitable test data. The goal is a reviewable programmed outcome, not an unsupported claim that a certain genre earns a certain grade.
| Evidence | What it should explain |
|---|---|
| Data model | Entities, structure and constraints |
| Algorithm design | The core method and important cases |
| Module interface | Inputs, outputs and effects |
| Annotated code reference | Where a significant technique is implemented |
| Execution guide | How the relevant outcome can be reproduced |
Attempt the task before opening its worked response. Record each change of state, explain the rule used, and check the result against the original requirements. Code examples labelled Python 3 use that language’s conventions; pseudocode states its own assumptions.
Common mistakes to avoid
Key takeaways
Test yourself
Answer a few questions, then review anything you missed.
Start with the quiz above to check the key ideas. You can also choose another topic from the practice library.