Developing a digital media outcome (internal)
Internal 4 credits Digital media End-user requirements Testing Data integrity CopyrightAS 91893, 4 credits. Advanced media techniques applied to meet the purpose and end-user requirements, with data integrity and testing procedures, relevant CONVENTIONS for the media type, and relevant implications addressed — on the shared develop → informed → refined ladder.
1 Reading the notation
Conventions for the media type are a named component, separate from technique.📖 Terms the schedule grades you on
4 terms- Develop (Achieved)
- Tools/techniques for purpose/end users; data integrity and testing; use conventions for the media type; explain implications.
- Informed (Merit)
- Use testing info to improve quality; APPLY conventions to improve quality; address implications.
- Refined (Excellence)
- Iterative improvement throughout; EFFICIENT tools and techniques in production.
- Relevant implications (closed list)
- Social, cultural, legal, ethical, intellectual property, privacy, accessibility, usability, functionality, aesthetics, sustainability & future-proofing, end-user considerations, health and safety.
2 What each grade requires
The develop → informed → refined ladder shared across the "advanced techniques" family.| Grade | What it takes | The half people drop |
|---|---|---|
| Achieved | Advanced techniques for the purpose/end users; data integrity and testing; EXPLAIN implications | Explaining an implication in the abstract, unconnected to this outcome |
| Merit ("informed") | Use information FROM TESTING to improve quality; ADDRESS implications with a visible decision | Testing that never feeds back into an actual change |
| Excellence ("refined") | ITERATIVE improvement across design/development/testing; JUSTIFY the choices made | One single round of testing, not a genuine iteration loop |
The verb escalates every time: explain → address → justify. Each is a distinct, checkable action, not just "more effort".
3 Advanced techniques and efficiency
A deliberate combination of steps, plus a workflow that avoids redoing work.| Requirement | What to show | Evidence |
|---|---|---|
| Tools and techniques for the users | The technique and the requirement it serves | Screenshots plus the requirement list |
| Efficient production (Excellence) | Templates, stylesheets, reusable assets | A style guide or template file |
4 Data integrity and testing
Versioning, master files, and testing on the devices users will actually use. ✕Generational quality loss
Exporting a compressed file, reopening it, and re-exporting degrades the media a little more each time. Always keep and work from an uncompressed or project master, and export the final compressed version once.5 Implications and legal requirements
Copyright, licensing and privacy — the ones with real consequences for media specifically.What addressing an implication looks like
- A source-and-licence log kept as assets are gathered.
- Releases obtained for identifiable people.
- A visible decision, not just a naming of the concern.
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.