Home A - Z
Page Index

An Otter Wiki

Blame

3a78e1 lisa 2026-08-29 17:10:44
Essential Terms: interactive pages for C01-C10 One mechanism in the shared port script builds all ten glossaries from CXX-2026/CXX-essential-terms.md. Obsidian's [!note]- callouts do not render in OtterWiki, so every page is rebuilt to the C02 click-to-reveal shape (>| ### Term / >| definition): C01 and C03-C08 are new, C09 converts from the non-rendering form, C02 and C10 are regenerated. 258 terms, definitions verbatim from source, sorted into the groups named by each source's own Topics list; the port asserts the grouping covers every term exactly once. Each page opens with a compact vocabulary map and closes on a See also. Seven criterion home pages gain a Foundations link. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RxqgYbTNNYrPNuko6xfbKs
1 
<!-- 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. -->
2
# Essential Terms — C08
3
4
The Hamilton and Alexandra College · Year 12 · 2026
5
6
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.
7
8
```mermaid
9
flowchart TD
10
R["C08 vocabulary<br/>22 terms"]
11
R --> G0["Debugging techniques<br/>6 terms"]
12
R --> G1["Alpha testing<br/>2 terms"]
13
R --> G2["Test cases, test data, expected results<br/>5 terms"]
14
R --> G3["Error types<br/>8 terms"]
15
R --> G4["Design modifications<br/>1 term"]
16
```
17
18
*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.*
19
20
---
21
22
## Debugging techniques
23
24
>| ### Breakpoint
25
>| 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.
26
27
>| ### Debugging
28
>| The process of identifying, analysing and removing errors or bugs from software.
29
30
>| ### Debugging statement
31
>| A line of code inserted into a program to output information about the program's execution.
32
33
>| ### Desk checking
34
>| A manual process where a programmer reviews and traces through their code to verify its correctness and logic.
35
36
>| ### Trace table
37
>| 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.
38
39
>| ### Truth table
40
>| A table used to represent all of the combinations of values for inputs and their outputs, typically used to test conditional statements.
41
42
---
43
44
## Alpha testing
45
46
>| ### Alpha testing
47
>| An early stage of testing conducted by the development team within the development environment.
48
49
>| ### Testing table
50
>| A commonly used way to record evidence of functionality testing.
51
52
---
53
54
## Test cases, test data, expected results
55
56
>| ### Boundary values
57
>| The maximum and minimum edge values possible for a given input.
58
59
>| ### Expected results
60
>| The output expected from an algorithm, assuming it is logically correct.
61
62
>| ### Test case
63
>| 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.
64
65
>| ### Test data
66
>| Data that has been specifically identified to be used in a test case.
67
68
>| ### Validation
69
>| Checks the reasonableness of data inputs.
70
71
---
72
73
## Error types
74
75
>| ### Divide by zero error
76
>| An error occurring when an arithmetic equation is attempting to divide by 0.
77
78
>| ### Index out of range
79
>| 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.
80
81
>| ### Infinite loop
82
>| An iteration that will never reach the condition upon which it can terminate.
83
84
>| ### Logic error
85
>| When source code is syntactically correct but contains an error resulting in unintended, undesirable, or incorrect output.
86
87
>| ### Overflow error
88
>| An error that occurs when a calculation exceeds the maximum limit that a data type can represent.
89
90
>| ### Runtime error
91
>| An error that occurs while a program is running, including overflow, index out of range, type mismatch, and divide by zero.
92
93
>| ### Syntax error
94
>| Often a typographical error in source code that violates the set of rules that define a programming language.
95
96
>| ### Type mismatch
97
>| When a function or method receives an argument of an unexpected data type leading to errors or unintended behavior.
98
99
---
100
101
## Design modifications
102
103
>| ### Design modification
104
>| 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.
105
106
---
107
108
## See also
109
110
- [C08 home page](/sd/C08/C08-home) — everything else for this criterion