<!-- 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. --> # Essential Terms — C07 The Hamilton and Alexandra College · Year 12 · 2026 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. ```mermaid flowchart TD R["C07 vocabulary<br/>14 terms"] R --> G0["Naming conventions<br/>4 terms"] R --> G1["Internal documentation<br/>6 terms"] R --> G2["Validation techniques<br/>4 terms"] ``` *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.* --- ## Naming conventions >| ### Naming convention >| An agreed set of rules by which to name source code elements such as variables, functions, classes, methods and objects. >| ### Camel case >| 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. >| ### Snake case >| A naming convention in programming where each word or abbreviation in the middle of a phrase is joined using an underscore. >| ### Hungarian notation >| A naming convention in computer programming where the name of the variable or function determines its purpose and its data type or structure. --- ## Internal documentation >| ### Internal documentation >| Notes and code comments contained within source code that describe the code. >| ### Header comment >| 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. >| ### Readability >| The ease with which text (including code) can be read and understood. >| ### Clear and concise code >| Code that is written in a straightforward and easily understandable manner, avoiding unnecessary complexity. >| ### Hard-coding >| 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. >| ### Magic number >| 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`). --- ## Validation techniques >| ### Validation >| Checks the reasonableness of data inputs. >| ### Existence check >| A test to see if a value has been entered as input or not. >| ### Range check >| Tests to see if a value is within a given range of acceptable values. >| ### Type check >| Tests to see if a value is of the specified data type or structure. --- ## See also - [C07 home page](/sd/C07/C07-home) — everything else for this criterion