← Summarising the development of a digital outcome

Preparing the three images and rehearsing the wording

Nothing here can be improvised on the day — the outcome and the internet are both unavailable, so every image and phrase must already exist before the assessment starts.

A checklist to run before the assessment

• Screenshot the FINISHED outcome — the view that best shows its purpose and key features at a glance.
• Screenshot a DIGITAL COMPONENT inside the authoring software — proof of what tool built it and how, not just the end result.
• Screenshot or photograph the DEVELOPMENT PROCESS — a planning document, an early draft, or a before/after comparison of a specific change.
• Draft short written notes in advance for: the two requirements (with their trade-off), the testing/expert consultation, and both reflections — so the writing on the day is expansion, not invention.

✕

A pretty final image is not enough evidence

A single polished screenshot of the finished outcome proves the outcome exists, but nothing about the DECISIONS made while building it. The image that shows a testing session, a rejected first attempt, or an annotated before/after is worth more marks, because it is evidence for the parts of the summary that are actually graded — the reasoning, not the result.

What each of the three images should specifically prove

• Image 1 (the outcome): proves the finished product exists and shows its purpose/key features at a glance.
• Image 2 (a digital component in the authoring software): proves what tool built it and gives a specific technical detail to reference.
• Image 3 (the development process): proves a genuine decision or iteration happened — a rejected attempt, a test session, or a before/after.

Practice for this standard covers the whole topic — flashcards and quiz.