SACE Stage 2 Digital Technologies key terms

A finite, ordered set of unambiguous steps that transforms given inputs into a desired output, so that the same procedure can be followed repeatedly and checked for correctness.

Breaking a large, complex problem into smaller subproblems that can be solved, tested and understood separately, then combined to produce a complete solution.

Removing or hiding detail that is not needed for the current purpose so that the essential features of a problem or system can be modelled and reasoned about more simply.

Identifying similarities, repetition or regular structure across problems or data so that a general rule or reusable solution can be applied instead of treating each case separately.

A structured, language-independent description of an algorithm using plain keywords and indentation, written for human readers rather than for direct execution by a computer.

Repeating a block of instructions while a condition holds or for a set number of times, allowing compact code to process many items or repeat an action until a goal is reached.

Choosing between alternative paths of execution using a condition, so that different instructions run depending on whether a test evaluates to true or false.

An expression that evaluates to exactly one of two values, true or false, typically built from comparison operators combined with AND, OR and NOT.

A manual table recording the values of variables and outputs after each step of an algorithm, used to test logic, follow execution and locate errors.

A technique where a function calls itself on a smaller version of the same problem, with a base case that stops the repeated calls and returns a result.

A measure of how the time or memory needed by an algorithm grows as input size increases, often expressed with big-O notation to compare the efficiency of approaches.

Designing a system as separate, self-contained modules with clear responsibilities and boundaries, so parts can be developed, tested, replaced or reused independently.

The defined boundary through which components, users or systems interact, specifying what inputs are accepted, what outputs are produced and what is hidden behind the boundary.

An early, often simplified version of a product built to test ideas, gather feedback and reduce risk before committing to full development.

An approach that builds a solution in repeated cycles of planning, designing, implementing and reviewing, refining the product after each cycle based on feedback and testing.

Documented statements of what a system must do (functional) and how well it must do it (non-functional), forming the basis for design decisions and acceptance testing.

Observing representative users attempting realistic tasks with a product to identify confusion, errors and improvement opportunities before final release.

The overall quality of a person's interaction with a product, covering ease of learning, efficiency, accessibility, clarity and satisfaction across the whole journey.

A system that records changes to files over time, allowing developers to review history, revert mistakes and merge contributions from multiple people working in parallel.

Systematically locating, diagnosing and correcting faults in a program by reproducing the problem, forming hypotheses, inspecting state and verifying the fix.

Purposefully chosen inputs, including normal, boundary and invalid cases, used to check that a solution behaves correctly and handles errors as intended.

A structured description of the entities in a system, their attributes and the relationships between them, guiding how information is stored and queried.

A distinct real-world thing or concept about which data is stored, such as a customer, product or enrolment, usually represented as a table in a relational database.

An attribute or combination of attributes that uniquely identifies each record in a table, preventing duplicate rows and providing a reliable reference point.

An attribute in one table that references the primary key of another table, creating a link between records and enforcing referential integrity across the database.

An association between entities describing how their records are connected, commonly one-to-one, one-to-many or many-to-many, and implemented through keys or junction tables.

Organising tables to reduce duplicated data and update anomalies by assigning attributes to tables according to dependencies, typically progressing through first, second and third normal forms.

The accuracy, consistency and completeness of stored data over its lifecycle, protected by constraints, validation rules, access controls and reliable backup procedures.

Automated checks applied to input to confirm it is reasonable and acceptable, such as range, type, length and format checks, before the data is stored or processed.

A precise request for information from a data store, often written in a structured language, that selects, filters, sorts or aggregates records matching stated criteria.

Presenting data graphically through charts, maps or dashboards so that patterns, trends and outliers become easier to perceive and communicate than in raw tables.

Data that describes other data, such as its origin, format, creation date, author and meaning, supporting discovery, correct interpretation and reliable management.

The physical components of a computing system, including processors, memory, storage, input and output devices, and the connections that let them communicate.

The programs, instructions and associated data that direct hardware to perform tasks, ranging from operating systems and utilities to applications and the code users write.

System software that manages hardware resources, schedules processes, handles memory and storage, and provides services and a consistent interface for application programs.

Two or more devices connected so they can exchange data, using agreed protocols over wired or wireless links, with addressing and routing to deliver messages.

An agreed set of rules governing how data is formatted, addressed, transmitted and acknowledged between devices, enabling reliable communication across different systems.

Transforming readable data into an unreadable form using a key, so that only authorised parties can reverse the process and recover the original information.

Verifying that a user or system is who they claim to be, commonly through something they know, possess or are, before granting access to resources.

Rules and mechanisms deciding which users or processes may view or change particular resources, following principles such as least privilege and separation of duties.

Delivering computing resources such as storage, processing and software over a network on demand, shifting responsibility for maintenance to a provider and raising data-location questions.

Running multiple isolated simulated computer environments on one physical machine, improving hardware utilisation and allowing flexible deployment, testing and recovery.

The ability of a system to handle growing amounts of work by adding resources, without unacceptable loss of performance or major redesign.

The gap between people who have affordable access, skills and confidence to use digital technology effectively and those who do not, shaped by income, location, age and education.

Meeting present needs without compromising future generations, applied to technology through energy use, device lifetimes, repairability, recycling and responsible sourcing of materials.