Question 1

What is NCEA AS 91884 about?

Accepted Answer

This standard asks you to build a digital product (like an app, game, website, or program) by testing and improving it step by step. You need to show that you can plan what you're building, break it into smaller pieces, test those pieces, fix problems as you find them, and explain how your final product affects people (things like privacy, ease of use, or accessibility).

Question 2

What do students need to do for AS 91884?

Accepted Answer

1. Plan your digital product by writing descriptions, sketches, or code outlines that show what you're building and why 2. Break your product down into smaller components and test each one separately 3. Trial your components multiple times, make changes based on what doesn't work, and keep testing until it functions properly 4. Describe what implications your product has—such as privacy, accessibility, usability, or how it affects users 5. Keep evidence of your testing process, changes, and reasoning throughout development

Question 3

What's the difference between Achieved, Merit, and Excellence for AS 91884?

Accepted Answer

Achieved: You plan a digital outcome, test components, fix problems you find, and briefly explain at least one implication (like ease of use or accessibility). Merit: You use feedback from testing to actively improve your components, try out different techniques and pick the best one, and discuss multiple relevant implications thoughtfully. Excellence: You create a polished, high-quality outcome by applying lessons from planning, testing, and trialling throughout the whole development process, showing refined decision-making at every step.

Question 4

What mistakes do students typically make in AS 91884?

Accepted Answer

1. Not showing clear evidence of iterative testing and improvement—students code once and submit rather than testing components multiple times and fixing issues 2. Ignoring or skimming implications; students describe one implication superficially instead of actually discussing relevant impacts like privacy, accessibility, or user experience 3. Failing to break the outcome into manageable pieces; students try to build everything at once without testing components separately first

Iterative digital outcome · AS 91884

Documents (6)

The standard itself

Reports & guidance

Bundles

More in this subject

Other Technology - Digital Technologies and Hangarau Matihiko standards · Level 1 · Year 11

Next year — Technology - Digital Technologies and Hangarau Matihiko Level 2 · Year 12

Related standards