Guide to non-exam assessment documentation exam tips

Exam tips

• Check every analysis requirement

  Before finalising an analysis, check for the problem statement, research outline, intended user or client, sufficient background, numbered measurable objectives and any necessary model.

  A fully scoped analysis must cover all relevant requirements and omit nothing needed for subsequent stages.

• Match the design evidence to the task

  Use the communication methods that clarify the actual solution: for example, relations for relational data, pseudo-code for processing, and screenshots when an interface is relevant.

  The specification allows a combination of methods as appropriate, so relevance and clarity matter more than including every possible format.

• Link every recommendation to the third-party reader

  When explaining a presentation feature, state how it helps a third party understand, navigate, run or investigate the solution.

  The requirement focuses on enabling a third party to discern the quality and purpose of the coding.

• Link tests to requirements

  When explaining a test, make clear which requirement or aspect of robustness it helps demonstrate.

  This shows that the tests were selected purposefully and that the evidence supports the achievement of the solution's requirements.

• Link every evaluation point to the requirements

  When discussing the outcome or feedback, state how it shows that the requirements were or were not met.

  The specification requires students to assess how well the outcome meets its requirements, not simply describe the outcome.