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/C07-2026/C07-essential-terms.md by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. -->
2
# Essential Terms — C07
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 C07. Click a term to expand its definition. All three C07 indicators are assessed live in Part B of the Live Coding Validation, without notes, so this vocabulary has to be in your head.
7
8
```mermaid
9
flowchart TD
10
R["C07 vocabulary<br/>14 terms"]
11
R --> G0["Naming conventions<br/>4 terms"]
12
R --> G1["Internal documentation<br/>6 terms"]
13
R --> G2["Validation techniques<br/>4 terms"]
14
```
15
16
*Where the C07 vocabulary sits, and how much of it is in each group — the 3 sections below follow the same order. Revise the heavy groups first.*
17
18
---
19
20
## Naming conventions
21
22
>| ### Naming convention
23
>| An agreed set of rules by which to name source code elements such as variables, functions, classes, methods and objects.
24
25
>| ### Camel case
26
>| A naming convention in programming where each word or abbreviation after the first in a phrase begins with a capital letter; there are no spaces or punctuation.
27
28
>| ### Snake case
29
>| A naming convention in programming where each word or abbreviation in the middle of a phrase is joined using an underscore.
30
31
>| ### Hungarian notation
32
>| A naming convention in computer programming where the name of the variable or function determines its purpose and its data type or structure.
33
34
---
35
36
## Internal documentation
37
38
>| ### Internal documentation
39
>| Notes and code comments contained within source code that describe the code.
40
41
>| ### Header comment
42
>| A set of meaningful comments at the top of a source code file, outlining information such as the name of the file, its purpose, the author's name and the date of creation.
43
44
>| ### Readability
45
>| The ease with which text (including code) can be read and understood.
46
47
>| ### Clear and concise code
48
>| Code that is written in a straightforward and easily understandable manner, avoiding unnecessary complexity.
49
50
>| ### Hard-coding
51
>| Including fixed data directly in a program's source code, so that it cannot be changed at runtime and can only be updated by editing and re-running the program.
52
53
>| ### Magic number
54
>| A hardcoded numeric (or string) literal whose meaning isn't clear from context, and which should usually be replaced with a named constant (e.g. `18200` instead of `TAX_FREE_THRESHOLD`).
55
56
---
57
58
## Validation techniques
59
60
>| ### Validation
61
>| Checks the reasonableness of data inputs.
62
63
>| ### Existence check
64
>| A test to see if a value has been entered as input or not.
65
66
>| ### Range check
67
>| Tests to see if a value is within a given range of acceptable values.
68
69
>| ### Type check
70
>| Tests to see if a value is of the specified data type or structure.
71
72
---
73
74
## See also
75
76
- [C07 home page](/sd/C07/C07-home) — everything else for this criterion