Skip to topic
    ← Back to course topics

    Describe the final product — OCR A-Level Computer Science

    Describe the final product explained

    This criterion asks you to provide annotated evidence of the usability features from your design, as built in the final solution, and to comment on how effective they are.

    Read the full explanation

    Evidence is material a moderator can check, such as screenshots or code extracts. Annotation labels each item with the feature it shows, such as clear error messages, and links it to the design. Commenting on effectiveness judges whether the feature achieves its design purpose, using evidence such as user observations. For example, label a form screenshot with its design source, then state whether testers completed it unaided.

    Your focus

    1. Select evidence from the final product that shows a specific usability feature.
    2. Annotate each item with the feature name and the section of the design it comes from.
    3. Comment on the effectiveness of each feature using observed user evidence.

    Describe the final product exam tips

    Marking Points
    • Links each piece of evidence to a named usability feature from the design.
    • Shows the feature in use through a screenshot, photograph or code extract that a moderator can check.
    • Annotates each item with a short label that explains what the feature does for the user.
    • Judges effectiveness against the design purpose rather than simply describing the feature.
    • Uses user testing or observation evidence to support any claim about effectiveness.
    Examiner Tips
    • 💡Number each piece of evidence and refer to its number in your commentary so the link between evidence and feature is clear.
    • 💡Take screenshots from the final product, not from earlier prototypes, so the evidence shows what was actually delivered.
    • 💡For each feature, write one sentence on its effectiveness and one sentence on any limitation you observed.
    Common Mistakes
    • Presents screenshots without any annotation, so the reader cannot tell which feature is shown; add a label naming the feature and its design source.
    • Describes a feature in the code without showing it in use; include evidence of the running interface or the specific output it produces.
    • Claims a feature is user-friendly without evidence; state the design aim it serves and cite what users were observed doing.