Developing a digital media outcome with complex techniques (internal)
Internal 4 credits Digital media UX principles Data integrity Testing Informed & refinedAS 91903, 4 credits. Achieved applies appropriate tools/techniques for the purpose and end-user requirements, appropriate data integrity/testing, USER EXPERIENCE PRINCIPLES, and addresses implications. Merit develops an INFORMED outcome — using testing information AND UX principles to improve quality. Excellence develops a REFINED one — iterative improvement THROUGHOUT, using efficient tools/techniques.
1 Reading the notation
Four Achieved elements, then the informed/refined additions.📖 Terms the schedule grades you on
3 terms- Develop a digital media outcome (Achieved)
- Apply tools/techniques for purpose and end-user requirements; apply data integrity/testing; apply UX principles; address implications.
- Develop an informed outcome (Merit)
- Use testing information AND UX principles to improve quality.
- Develop a refined outcome (Excellence)
- Iterative improvement throughout; efficient tools and techniques.
2 The complex techniques the standard names
Deliberate, parameterised techniques — not a default preset.The standard's own examples
- Non-core functionality beyond the basic requirement.
- Sophisticated digital effects, applied deliberately.
- Industry standards or guidelines followed.
- Responsive design working across multiple devices.
- Integration of ORIGINAL media assets you created.
- Dynamic data handling and interactivity, or automation through scripts.
3 Applying UX principles
A named, separate requirement from data integrity and testing. ✕Technically correct but not usable for the purpose
A video that plays back perfectly on every device is not automatically a good outcome — if the audience watches muted and the key message is audio-only, the UX principle (design for how users actually consume it) has not been applied even though the technical testing passed.4 Data integrity and testing
Preserve the master; test on the target devices.| Requirement | What to show | The evidence |
|---|---|---|
| Data integrity | Versioning, backups, master files, correct settings | File naming and version history; export settings |
| Testing procedures | Tested on target devices against each requirement | A test table: requirement, method, result, change made |
The test table is the highest-value artefact: it evidences testing AND the end-user requirement in one place.
5 Implications, addressed not just named
A decision that visibly follows from the implication.The standard's own implication list
- Social, cultural, legal, ethical, intellectual property, privacy.
- Accessibility, usability, functionality, aesthetics.
- Sustainability and future proofing.
- End-user requirements, health and safety.
Practice
Recall it first, then use it — testing yourself builds the memory, where rereading the notes above only feels easier.
Recall and application shuffled together — you have to work out what each item wants before you can answer it, which is the part the exam actually tests. Both kinds feed the same spacing schedule, so anything you miss comes back sooner.
Say the answer out loud before flipping — that attempt is where the learning happens, even when you get it wrong.
Exam-style only. Instant feedback, shuffled each attempt, best score saved on this device.