<!-- Generated from applied-computing-au vic/unit3-4/sat/C08-2026/C08-essential-terms.md by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. --> # Essential Terms — C08 The Hamilton and Alexandra College · Year 12 · 2026 A glossary of every term you need to recognise and use correctly across C08. Click a term to expand its definition. If you cannot define a term in your own words, you cannot use it with confidence when it counts. ```mermaid flowchart TD R["C08 vocabulary<br/>22 terms"] R --> G0["Debugging techniques<br/>6 terms"] R --> G1["Alpha testing<br/>2 terms"] R --> G2["Test cases, test data, expected results<br/>5 terms"] R --> G3["Error types<br/>8 terms"] R --> G4["Design modifications<br/>1 term"] ``` *Where the C08 vocabulary sits, and how much of it is in each group — the 5 sections below follow the same order. Revise the heavy groups first.* --- ## Debugging techniques >| ### Breakpoint >| A debugging tool that allows the execution of a program to be paused at a specific point to allow a programmer to inspect the current state of the program and diagnose any issues. >| ### Debugging >| The process of identifying, analysing and removing errors or bugs from software. >| ### Debugging statement >| A line of code inserted into a program to output information about the program's execution. >| ### Desk checking >| A manual process where a programmer reviews and traces through their code to verify its correctness and logic. >| ### Trace table >| A tool used in programming and algorithm analysis to track the values of variables at each step of the execution of a program or algorithm. >| ### Truth table >| A table used to represent all of the combinations of values for inputs and their outputs, typically used to test conditional statements. --- ## Alpha testing >| ### Alpha testing >| An early stage of testing conducted by the development team within the development environment. >| ### Testing table >| A commonly used way to record evidence of functionality testing. --- ## Test cases, test data, expected results >| ### Boundary values >| The maximum and minimum edge values possible for a given input. >| ### Expected results >| The output expected from an algorithm, assuming it is logically correct. >| ### Test case >| A set of steps that a tester uses to determine if the element being tested works correctly, often outlining test data, testing procedures, and expected results. >| ### Test data >| Data that has been specifically identified to be used in a test case. >| ### Validation >| Checks the reasonableness of data inputs. --- ## Error types >| ### Divide by zero error >| An error occurring when an arithmetic equation is attempting to divide by 0. >| ### Index out of range >| An error that occurs when attempting to access an element of an array using an index that is outside the valid range of indices for that array. >| ### Infinite loop >| An iteration that will never reach the condition upon which it can terminate. >| ### Logic error >| When source code is syntactically correct but contains an error resulting in unintended, undesirable, or incorrect output. >| ### Overflow error >| An error that occurs when a calculation exceeds the maximum limit that a data type can represent. >| ### Runtime error >| An error that occurs while a program is running, including overflow, index out of range, type mismatch, and divide by zero. >| ### Syntax error >| Often a typographical error in source code that violates the set of rules that define a programming language. >| ### Type mismatch >| When a function or method receives an argument of an unexpected data type leading to errors or unintended behavior. --- ## Design modifications >| ### Design modification >| A change made to the planned design of a solution during the development stage in response to issues identified through testing, debugging or changing requirements. --- ## See also - [C08 home page](/sd/C08/C08-home) — everything else for this criterion