NCEA Level 2 Digital Technologies study plan
NCEA Level 2 Digital Technologies · Give each week a clear focus.
8 weeks · About 6 hours per week
Software programming
Write, run, and debug at least six short programs that use variables, sequence, selection, and iteration, keeping each under 30 lines
Trace the execution of three supplied-style algorithms by hand, recording variable values at each step, then verify your trace by running the code
Convert three informal problem statements into pseudocode before coding, and annotate where each control structure appears
Set up a working development environment with a version control repository and commit each program with a descriptive message
Your checkpoint
A repository of six working programs plus hand traces and pseudocode for three problems
Software programming
Decompose two larger problems into functions or methods, each with a single clear responsibility, and document inputs and outputs
Implement input validation and error handling in at least three programs so invalid input produces a clear message rather than a crash
Choose appropriate data structures (list, dictionary, record) for three scenarios and justify each choice in one sentence
Write and run at least eight test cases, including boundary values, against your own code and record pass or fail results
Your checkpoint
A tested program of 80-150 lines that uses functions, validation, and a chosen data structure, with a test log
Software programming & Electronic environments and embedded systems
Refactor one earlier program to remove duplicated code and improve naming, then compare readability before and after
Describe how a program running on a microcontroller differs from one on a general-purpose computer in memory, timing, and input handling
Write a short program that reads a sensor-style input, applies a threshold, and triggers an output, explaining each line
Explain the role of compilers and interpreters in turning source code into executable instructions, using one concrete example of each
Your checkpoint
A refactored program plus a one-page comparison of microcontroller and general-purpose computing with a working threshold example
Electronic environments and embedded systems
Identify and label the components of a simple embedded system: input transducer, controller, output actuator, and power supply
Draw a circuit diagram for two input devices and two output devices connected to a microcontroller, showing correct pin assignments and current-limiting components
Convert between binary, decimal, and hexadecimal for at least ten values and explain why hexadecimal is used in hardware documentation
Explain the difference between digital and analog signals and describe how a sensor's analog reading is converted to a digital value
Your checkpoint
A labelled system diagram and circuit diagram with a worked number-conversion table of ten values
Electronic environments and embedded systems & Digital information systems
Build or simulate a microcontroller project that reads two inputs and controls two outputs according to a written specification
Write a test plan for the embedded project covering normal operation, boundary conditions, and one failure mode, then execute it
Describe the components of an information system (hardware, software, data, people, procedures) using your embedded project as the example
Compare local storage, cloud storage, and a database for three given scenarios, stating one advantage and one limitation of each
Your checkpoint
A working or simulated embedded project with a completed test plan and a component map of the information system
Digital information systems
Model a small dataset in at least two related tables, identifying primary and foreign keys and explaining each relationship
Write queries or filters to retrieve, sort, and summarise data, and explain what each query returns
Identify three security risks to stored data and describe one control for each, such as access levels, encryption, or backups
Explain how data integrity, accuracy, and relevance affect the usefulness of information for a stated purpose
Describe the privacy and legal obligations that apply when storing personal information in a school or workplace system
Your checkpoint
A two-table dataset with five documented queries and a risk-and-controls table covering three risks
Digital media
Plan a short digital media outcome by writing a brief that states purpose, audience, and at least three technical and aesthetic requirements
Create and edit the media outcome using appropriate tools, applying at least three design principles such as contrast, alignment, and hierarchy
Prepare and optimise assets for the intended delivery format, explaining how file format and compression choices affect quality and size
Apply correct attribution and licensing to every asset used, recording source and licence for each
Your checkpoint
A finished digital media outcome with a design brief, an asset register with licences, and a short justification of format choices
Software programming & Electronic environments and embedded systems & Digital information systems & Digital media
Complete two timed practice assessments mixing programming, embedded systems, information systems, and media questions, then mark them against the criteria
Review every error from the practice assessments and write a corrected explanation for each
Produce a one-page summary sheet per domain listing key terms, processes, and common pitfalls
Re-run your weakest practical task from weeks 2 to 7 and confirm the improvement against your earlier version
Your checkpoint
Two marked practice assessments with a corrections log and four domain summary sheets
Milestones
Week 2: You can write, run, and debug a 50-line program with functions and validation without referring to notes, and your test log shows boundary cases covered
Week 4: You can label an embedded system diagram from memory and convert values between binary, decimal, and hexadecimal with no errors
Week 6: You can design two related tables and write queries that retrieve and summarise the data, and you can name a control for each of three data risks
Week 8: Both timed practice assessments are complete, every error has a written correction, and your weakest practical task has been re-done to a higher standard