NCEA Level 3 Digital Technologies flashcards

33 cards. Read the term and the definition here. The deck at the top of this page is optional.

Iterative development cycle

A repeated process of planning, designing, building, testing, and evaluating. Each cycle refines the outcome using evidence from the previous cycle rather than following a single linear sequence.

Fit for purpose

The outcome meets the stated brief and specifications and performs the intended task correctly for its identified end user in the intended context.

End user

The person or group who will actually use the digital outcome. Their needs, skills, and context drive design decisions and usability testing.

Functional testing

Testing that checks whether each feature produces the expected output for given inputs. Evidence records the input, the expected result, and the actual result.

Usability testing

Observing real users attempting realistic tasks with the outcome to find where they struggle. Findings inform design changes rather than only confirming the product works.

Test plan

A documented list of test cases covering normal, boundary, and invalid inputs, each with expected and actual results, used to show the outcome has been systematically checked.

Boundary value

An input exactly at the edge of an accepted range, such as the minimum or maximum allowed value. Errors commonly occur at boundaries, so they are explicitly tested.

Specifications

Measurable requirements derived from the brief, such as performance, function, and appearance criteria. They provide the standard against which the final outcome is evaluated.

Brief

The initial statement of a problem or opportunity, including the intended user and context. It is the reference point for judging whether the final outcome is appropriate.

Relevant implications

The social, ethical, legal, economic, or environmental consequences of a digital outcome for identified stakeholders. They must be explained with specific effects, not just named.

Stakeholder

Any person or group affected by the outcome, including users, the client, and third parties. Different stakeholders can have conflicting needs that must be balanced.

Intellectual property

Legal rights over created works such as code, images, and music. Using licensed or original assets avoids infringement and is a legal implication of digital outcomes.

Accessibility

Designing so people with varied abilities can use the outcome, for example through sufficient contrast, alternative text, keyboard navigation, and clear language.

Prototype

An early model built to test ideas or feasibility before full development. Feedback from a prototype reduces risk in later iterations.

Iteration

One pass through the development cycle that produces a refined version of the outcome. Evidence should show what changed and why the change was made.

Evaluation

A judgement of the outcome against the brief and specifications, supported by testing evidence, that identifies strengths, limitations, and justified deviations.

Version control

Tracking changes to files over time with labelled milestones so earlier states can be reviewed or restored. It makes design decisions and progress traceable.

Debugging

Locating and correcting errors by reproducing the fault, isolating the cause, fixing it, and retesting. The fix should be recorded to show the reasoning.

Algorithm

A finite, ordered set of unambiguous steps that solves a problem. It can be expressed as pseudocode or a flowchart before being implemented in code.

Pseudocode

A structured, language-independent description of an algorithm using plain statements for input, output, selection, and repetition, allowing logic to be checked before coding.

Variable scope

The region of a program where a variable can be accessed. Local scope limits access to a block or function; global scope allows access throughout the program.

Function

A named, reusable block of code that takes inputs, performs a task, and may return a value. Functions reduce duplication and make programs easier to test.

Parameter

A named input declared by a function. The matching value passed when the function is called is the argument; confusing the two is a common error.

Selection structure

A control structure that chooses between paths using a condition, such as if, else-if, and else. Conditions must evaluate to true or false.

Iteration structure

A control structure that repeats statements, such as a counted loop or a condition-controlled loop. The terminating condition must eventually be reached.

Data validation

Checking input against rules such as type, range, or format before it is used. It prevents invalid data from causing errors or corrupting stored information.

Data types

Categories of values such as integer, float, string, and boolean. Choosing appropriate types affects correctness and memory use, and mixing types can cause errors.

Array

An indexed collection of values of the same type stored under one name. Elements are accessed by position, usually starting at index zero.

Relational database

Data stored in tables of rows and columns, linked by keys. Relationships reduce duplication and support queries across related data.

Primary key

A column or set of columns that uniquely identifies each row in a table. It cannot contain duplicate or null values.

Foreign key

A column that references the primary key of another table, enforcing referential integrity and creating the relationship between the two tables.

Query

A request to retrieve or manipulate data from a database, often written in SQL, using clauses such as select, from, where, and order by.

Data integrity

The accuracy and consistency of stored data, maintained through constraints such as keys, validation rules, and controlled access.