Digital Technologies - Systems, Complexity, and Iterative Development
NCEA Level 3 Digital Technologies tests whether you can explain and justify how digital information systems work and how a complex digital technologies outcome was developed, refined, and evaluated. Written explanation is judged on precise technical vocabulary and on reasoning about relationships between parts - not on feature lists.
Digital information systems
An information system is people, procedures, data, software, hardware, and networks working together to collect, process, store, and output information. At Level 3, the components must be discussed as interrelated: changing one changes the others. Adding a networked database, for instance, alters hardware requirements, data-entry procedures, staff training, and the privacy obligations on the people holding the data.
Complexity and iteration
A complex outcome is not simply a large one. It has multiple interrelated components, is built iteratively, and is tested by trialling - against the brief, with end users, in the intended context. Justify design decisions against the specifications and against user feedback, and describe what you changed and why.
Worked example
A school wants a system recording laptop loans. A weak answer lists "a database, a laptop, a scanner". A stronger answer: the database stores loan records; the scanner is the input device; the procedure is that students borrow through the librarian at interval; records sit on the school network so the dean can see overdue items; role-based permissions mean students see only their own loans. Complexity comes from the interrelation - restricting access needs permissions in the software, which changes the procedure and creates a training need. Testing is by trialling with ten students, comparing records against the paper log, and collecting librarian feedback; then iterate by defaulting the due date to three school days and retesting.
Traps that cost marks
Calling a big outcome "complex"; describing what you did without explaining why; ignoring the brief when justifying decisions; omitting legal and ethical obligations (Privacy Act 2020 principles, copyright, accessibility); claiming testing you cannot evidence; vague evaluation such as "it worked well" with no reference to the specifications.