NZ Scholarship Digital Technologies study plan

Map the full Digital Technologies scholarship assessment space into three strands: software/systems design, data and computation, and digital impacts/ethics, and write a one-page concept map that shows how the strands connect.

Audit your current skills against each strand by rating yourself 1-5 with a short evidence note per rating, so the plan targets real gaps rather than assumed ones.

Collect and read the official assessment specification and any published exemplars, then list the exact command words and performance descriptors used, so later practice matches the expected standard.

Set up a working environment (editor, version control, a scratch repository, and a notes system) and commit your first notes file, proving the toolchain works end to end.

Implement three small programs that each demonstrate a distinct core construct (iteration with state, recursion, and event-driven flow), and annotate each with a comment explaining the design trade-off chosen.

Analyse two of your own programs for correctness and efficiency by writing down input/output reasoning and a complexity estimate, then improve one of them measurably.

Practise reading unfamiliar code: take an open-source snippet of 50-100 lines, trace its execution by hand, and record a step-by-step trace that predicts its output before running it.

Draft a reusable checklist for code quality (naming, decomposition, error handling, testing) that you will apply to every later deliverable.

Model a small data set (at least 200 records) in a structured format and write queries or transformations that answer three specific analytical questions.

Explain, in writing, the difference between data, information, and inference using your own data set as the example, with one concrete misleading interpretation and why it is wrong.

Implement validation and error handling for messy input (missing fields, wrong types, duplicates) and demonstrate each failure case being caught.

Produce one visualisation or summary table that communicates a finding accurately, and justify the design choice in two sentences.

Design a system for a realistic scenario by writing requirements, a component diagram, and a data-flow description, then identify two risks and a mitigation for each.

Compare two plausible architectures for that scenario and write a decision record stating criteria, trade-offs, and the chosen option.

Implement a minimal working slice of the chosen design that exercises the riskiest component first, and record what you learned.

Write a short security and privacy review of your design covering at least three threats and their controls.

Argue both sides of two digital-ethics or societal-impact questions (for example algorithmic bias and data surveillance) in structured written form, with a claim, evidence, counter-argument, and rebuttal for each.

Identify the assumptions and limitations in one published claim about technology and state how you would test or qualify it.

Apply a recognised ethical framework to a case study and reach a defensible recommendation with stated trade-offs.

Draft a glossary of 15 key terms spanning technical and social dimensions, each defined in your own words with an example.

Complete a full timed practice task under exam conditions (no notes, fixed time), then self-mark against the specification descriptors and record the score.

Diagnose your three weakest areas from the timed attempt and write a targeted remediation action for each.

Re-attempt the weakest section after remediation and compare results to show measurable improvement.

Build a personal error log template and populate it with every mistake found so far, categorised by cause.

Complete a second full timed practice task of a different format or emphasis, again self-marked against descriptors.

Synthesise a one-page 'exam strategy' sheet covering time allocation, question sequencing, and how to handle unfamiliar scenarios.

Rehearse explaining a technical solution aloud in under three minutes, then refine the explanation based on a recorded playback.

Close out at least five open items from your error log and verify each fix with a fresh example.

Run a final timed mock covering the full breadth of the specification and mark it strictly to descriptors.

Consolidate all notes into a single revised summary of no more than four pages that you could revise from on exam day.

Review the error log end to end and confirm every category has a documented fix and a verification example.

Write a short readiness statement naming your strongest and weakest areas and the specific tactics you will use on the day.