Commit 3a78e1

2026-08-29 17:10:44 lisa: 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

sd/C01/C01-home.md ..
@@ 6,6 6,10 @@
	---
+	## Foundations
+
+	- [Essential Terms](/sd/C01/Essential%20Terms) — the C01 glossary; click a term to expand its definition
+
	## Key concepts
	Short explainers with diagrams and videos for the concepts you'll be quizzed on at validation:
/dev/null .. sd/C01/Essential Terms.md
@@ 0,0 1,102 @@
+	<!-- Generated from applied-computing-au vic/unit3-4/sat/C01-2026/C01-essential-terms.md by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. -->
+	# Essential Terms — C01
+
+	The Hamilton and Alexandra College · Year 12 · 2026
+
+	A glossary of every term you need to recognise and use correctly across C01. 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["C01 vocabulary<br/>21 terms"]
+	R --> G0["Problem-solving methodology<br/>5 terms"]
+	R --> G1["Design brief<br/>3 terms"]
+	R --> G2["Project management<br/>11 terms"]
+	R --> G3["Gantt chart<br/>2 terms"]
+	```
+
+	*Where the C01 vocabulary sits, and how much of it is in each group — the 4 sections below follow the same order. Revise the heavy groups first.*
+
+	---
+
+	## Problem-solving methodology
+
+	>| ### Analysis stage
+	>| The stage of the problem-solving methodology where solution requirements, constraints and scope are determined
+
+	>| ### Design stage
+	>| The stage of the problem-solving methodology where the function and appearance of a solution are planned, and evaluation criteria created
+
+	>| ### Development stage
+	>| The stage of the problem-solving methodology where the solution is coded, validated, tested and documented
+
+	>| ### Evaluation stage
+	>| The stage of the problem-solving methodology where the completed solution is evaluated against the evaluation criteria and the project plan is assessed
+
+	>| ### Problem-solving methodology (PSM)
+	>| An approach that develops the stages involved in solving a problem
+
+	---
+
+	## Design brief
+
+	>| ### Design brief
+	>| A document that identifies a problem, need or opportunity and describes the proposed software solution, its users, the programming language to be used, and how it is feasible and original
+
+	>| ### Feasibility
+	>| An assessment of whether a proposed solution is practical and achievable, commonly evaluated using the T.E.L.O.S. framework (Technical, Economic, Legal, Operational, Scheduling)
+
+	>| ### T.E.L.O.S.
+	>| A framework for assessing feasibility across five dimensions: Technical (can it be built?), Economic (can it be afforded?), Legal (is it lawful?), Operational (will it be used?), and Scheduling (can it be completed in time?)
+
+	---
+
+	## Project management
+
+	>| ### Concepts (project management)
+	>| The milestones and dependencies within a project timeline
+
+	>| ### Concurrently
+	>| When a task is carried out at the same time as another task
+
+	>| ### Critical path
+	>| The shortest possible time in which a project can be completed
+
+	>| ### Dependency
+	>| A relationship between two tasks in a project plan where one task cannot begin until another has been completed
+
+	>| ### Predecessor
+	>| A task that must be completed before another one can be performed
+
+	>| ### Processes (project management)
+	>| Task identification, sequencing and allocation of time and resources within a project timeline
+
+	>| ### Project management
+	>| A method of recording the progress of a project and managing resources to operate within time, resource and cost availability
+
+	>| ### Slack time
+	>| The length of time that a task can run overtime before affecting other tasks
+
+	>| ### Successor
+	>| A task that must be completed after another task
+
+	>| ### Work breakdown structure (WBS)
+	>| An often hierarchical breakdown of a project that organises the work to be done into manageable sections, often displayed as a visual outline or map
+
+	>| ### Monitoring
+	>| The ongoing process of tracking a project's progress against the plan, identifying delays or changes, and documenting adjustments made
+
+	---
+
+	## Gantt chart
+
+	>| ### Gantt chart
+	>| A type of bar chart or graphic timeline that shows the progress of a project by placing tasks on a timeline, often with comments or annotations
+
+	>| ### Milestone
+	>| A significant point or event in a project timeline that marks the completion of a key deliverable or the start of a new phase
+
+	---
+
+	## See also
+
+	- [C01 home page](/sd/C01/C01-home) — everything else for this criterion
sd/C02/Essential Terms.md ..
@@ 1,3 1,4 @@
+	<!-- Generated from applied-computing-au vic/unit3-4/sat/C02-2026/C02-essential-terms.md by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. -->
	> **DRAFT** — under teacher review.
	# Essential Terms — C02
@@ 6,16 7,19 @@
	A glossary of every term you need to recognise and use correctly across C02. Click a term to expand its definition. Use this as a vocabulary self-check before your C2-1 (Poster Peer-Assessment) and C2-2 (Hand-Drawn Diagrams) validations — if you can't define a term in your own words, you can't defend it under questioning.
-	---
-
-	## Topics covered
+	```mermaid
+	flowchart TD
+	R["C02 vocabulary<br/>26 terms"]
+	R --> G0["Data collection<br/>9 terms"]
+	R --> G1["Context diagrams and DFDs<br/>7 terms"]
+	R --> G2["Use case diagrams (UML)<br/>10 terms"]
+	```
-	- **Data collection** — interviews, surveys, observations, reports; qualitative vs quantitative data
-	- **Analytical tools** — context diagrams, data flow diagrams, use case diagrams
+	*Where the C02 vocabulary sits, and how much of it is in each group — the 3 sections below follow the same order. Revise the heavy groups first.*
	---
-	## Data Collection
+	## Data collection
	>| ### Close-ended questions
	>| Questions that can be answered with a finite set of responses
@@ 46,13 50,7 @@
	---
-	## Analytical Tools
-
-	>| ### Actor
-	>| An entity that can interact with the software solution as shown in a use case diagram
-
-	>| ### Association
-	>| A relationship between two elements in a use case diagram
+	## Context diagrams and DFDs
	>| ### Context diagram
	>| A visualisation of a system in its entirety that indicates the data that is passed into and out of the system
@@ 69,6 67,22 @@
	>| ### Entity
	>| The users or external systems that interact with the system being created
+	>| ### Process (context diagram)
+	>| An abstract representation of the whole system being created
+
+	>| ### Process (data flow diagram)
+	>| An abstract representation of a function within a system
+
+	---
+
+	## Use case diagrams (UML)
+
+	>| ### Actor
+	>| An entity that can interact with the software solution as shown in a use case diagram
+
+	>| ### Association
+	>| A relationship between two elements in a use case diagram
+
	>| ### Extend
	>| A relationship between use cases where one use case has optional or additional functionality, which is represented in a use case diagram as a second use case
@@ 78,12 92,6 @@
	>| ### Include
	>| A relationship between use cases where one use case is tied to, or relies upon, the functionality contained within another use case
-	>| ### Process (context diagram)
-	>| An abstract representation of the whole system being created
-
-	>| ### Process (data flow diagram)
-	>| An abstract representation of a function within a system
-
	>| ### Relationship
	>| The connections between elements within a use case diagram
@@ 103,7 111,8 @@
	## See also
-	- [Context Diagram](Context%20Diagram.md) — the highest-level view of your system
-	- [Context Diagram vs Data Flow Diagram](Context%20Diagram%20vs%20Data%20Flow%20Diagram.md) — what changes between Level 0 and Level 1
-	- [What Is an Entity](What%20Is%20an%20Entity.md) — entities aren't only people
-	- [Excalidraw Diagram Starters](Excalidraw%20Diagram%20Starters.md) — pre-framed canvases for rehearsing all three diagrams
+	- [C02 home page](/sd/C02/C02-home) — everything else for this criterion
+	- [Context Diagram](/sd/C02/Context%20Diagram) — the highest-level view of your system
+	- [Context Diagram vs Data Flow Diagram](/sd/C02/Context%20Diagram%20vs%20Data%20Flow%20Diagram) — what changes between Level 0 and Level 1
+	- [What Is an Entity](/sd/C02/What%20Is%20an%20Entity) — entities aren't only people
+	- [Excalidraw Diagram Starters](/sd/C02/Excalidraw%20Diagram%20Starters) — pre-framed canvases for rehearsing all three diagrams
sd/C03/C03-home.md ..
@@ 6,6 6,10 @@
	---
+	## Foundations
+
+	- [Essential Terms](/sd/C03/Essential%20Terms) — the C03 glossary; click a term to expand its definition
+
	## Start here
	- [🎬 C2+C3 Assessment Explained](/sd/C2%20and%20C3%20Assessment%20Explained) — short videos covering the C3-1 (SRS Document) and C3-2 (Critical Thinking) validation formats
/dev/null .. sd/C03/Essential Terms.md
@@ 0,0 1,105 @@
+	<!-- Generated from applied-computing-au vic/unit3-4/sat/C03-2026/C03-essential-terms.md by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. -->
+	# Essential Terms — C03
+
+	The Hamilton and Alexandra College · Year 12 · 2026
+
+	A glossary of every term you need to recognise and use correctly across C03. 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["C03 vocabulary<br/>20 terms"]
+	R --> G0["The SRS<br/>3 terms"]
+	R --> G1["Requirements<br/>2 terms"]
+	R --> G2["Constraints<br/>6 terms"]
+	R --> G3["Solution boundaries and scope<br/>2 terms"]
+	R --> G4["Quality words used in non-functional requirements<br/>7 terms"]
+	```
+
+	*Where the C03 vocabulary sits, and how much of it is in each group — the 5 sections below follow the same order. Revise the heavy groups first.*
+
+	---
+
+	## The SRS
+
+	>| ### Software requirements specification (SRS)
+	>| A single document that contains the outcomes of the analysis stage of the problem-solving methodology, including scope, constraints, functional requirements and non-functional requirements.
+
+	>| ### Solution requirements
+	>| What the client needs from the solution in relation to its features.
+
+	>| ### Analysis stage
+	>| The stage of the problem-solving methodology where solution requirements, constraints and scope are determined.
+
+	---
+
+	## Requirements
+
+	>| ### Functional requirements
+	>| The desired operations of a program that have specified inputs, behaviours and outputs.
+
+	>| ### Non-functional requirements
+	>| Qualitative requirements of a solution, often tied to solution constraints.
+
+	---
+
+	## Constraints
+
+	>| ### Constraints
+	>| Factors that may limit or restrict solution requirements.
+
+	>| ### Technical constraints
+	>| The limitations and restrictions related to the technology used in a project.
+
+	>| ### Economic constraints
+	>| The limitations on a project or decision imposed by financial factors.
+
+	>| ### Legal constraints
+	>| The limitations and requirements imposed on a project or decision by laws, regulations and legal standards.
+
+	>| ### Social constraints
+	>| The limitations imposed on a project or decision by societal norms, values and expectations.
+
+	>| ### Non-technical constraints
+	>| Limitations relating to areas other than hardware and software: social, legal and usability.
+
+	---
+
+	## Solution boundaries and scope
+
+	>| ### Scope
+	>| The boundaries or parameters of the solution - what it will do and what it will not do.
+
+	>| ### Solution boundaries
+	>| The limits or edges of what a project or solution will encompass.
+
+	---
+
+	## Quality words used in non-functional requirements
+
+	>| ### Fit for purpose
+	>| To be well suited for a role or purpose.
+
+	>| ### Functionality
+	>| The extent to which a solution is suited to its purpose.
+
+	>| ### Usability
+	>| The extent to which a system is easy to learn and use.
+
+	>| ### Reliability
+	>| How much a solution can be depended upon to function as designed, and for how long.
+
+	>| ### Portability
+	>| How easily a solution is able to be used in different operating environments.
+
+	>| ### Robustness
+	>| How well a software solution responds to errors that occur when the software is being used.
+
+	>| ### Maintainability
+	>| How easy a solution is to look after once it has been put in place.
+
+	---
+
+	## See also
+
+	- [C03 home page](/sd/C03/C03-home) — everything else for this criterion
+	- [Efficiency vs Effectiveness](/sd/C04/Efficiency%20vs%20Effectiveness) — the full VCAA lists: exactly 3 efficiency factors and 11 effectiveness factors; only the ones this glossary defines appear above
sd/C04/C04-home.md ..
@@ 6,6 6,10 @@
	---
+	## Foundations
+
+	- [Essential Terms](/sd/C04/Essential%20Terms) — the C04 glossary; click a term to expand its definition
+
	## 🎬 Walkthrough videos
	- [C4 Design Ideas and Evaluation Explained](/sd/C4%20Design%20Ideas%20and%20Evaluation%20Explained) — two short videos on the C4-1 design pack (design defence) and C4-2 evaluation matrix (criteria, efficiency vs effectiveness, explain vs justify)
/dev/null .. sd/C04/Essential Terms.md
@@ 0,0 1,88 @@
+	<!-- Generated from applied-computing-au vic/unit3-4/sat/C04-2026/C04-essential-terms.md by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. -->
+	# Essential Terms — C04
+
+	The Hamilton and Alexandra College · Year 12 · 2026
+
+	A glossary of every term you need to recognise and use correctly across C04. 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["C04 vocabulary<br/>16 terms"]
+	R --> G0["Ideation techniques<br/>5 terms"]
+	R --> G1["Design ideas<br/>2 terms"]
+	R --> G2["Convergent and divergent thinking<br/>2 terms"]
+	R --> G3["Evaluation criteria<br/>7 terms"]
+	```
+
+	*Where the C04 vocabulary sits, and how much of it is in each group — the 4 sections below follow the same order. Revise the heavy groups first.*
+
+	---
+
+	## Ideation techniques
+
+	>| ### brainstorming
+	>| A technique that allows for non-judgemental, spontaneous design ideation; ideas should not be rejected too soon.
+
+	>| ### graphic organisers
+	>| Visual methods of organising ideas; can extend upon mind-mapping techniques.
+
+	>| ### mind mapping
+	>| A technique that involves quickly generating and linking ideas together; complements brainstorming.
+
+	>| ### mood boards
+	>| Allow designers to communicate the general feeling of a solution; help to establish the creative direction and potential look and feel of a software solution.
+
+	>| ### sketches and annotations
+	>| Fast tools to brainstorm and communicate ideas visually.
+
+	---
+
+	## Design ideas
+
+	>| ### design ideas
+	>| Conceptual solutions or creative approaches intended to address a specific problem or requirement in a design process.
+
+	>| ### pseudocode
+	>| Code that designs algorithms in a clear, human-readable, language-independent format.
+
+	---
+
+	## Convergent and divergent thinking
+
+	>| ### convergent thinking
+	>| Involves coming up with a single, well-established answer to a problem; results in design ideas that are based on other, proven ideas.
+
+	>| ### divergent thinking
+	>| Involves exploring many possible solutions using spontaneous, free-flowing techniques; more creative than convergent thinking.
+
+	---
+
+	## Evaluation criteria
+
+	>| ### evaluation
+	>| An assessment of whether a solution achieves the goals for which it was originally designed; not the same as testing.
+
+	>| ### evaluation criteria
+	>| Rules set out during design that include effectiveness and efficiency criteria; based on the solution's requirements, which were defined during analysis.
+
+	>| ### effectiveness
+	>| Produces the expected result.
+
+	>| ### effectiveness of a solution
+	>| How well the software works to produce the desired result.
+
+	>| ### efficiency
+	>| Economic use of resources with minimum waste.
+
+	>| ### efficiency of a solution
+	>| Whether the result is produced quickly and simply.
+
+	>| ### usability
+	>| Ease of use to achieve specified goals in terms of efficiency, effectiveness and satisfaction.
+
+	---
+
+	## See also
+
+	- [C04 home page](/sd/C04/C04-home) — everything else for this criterion
+	- [Efficiency vs Effectiveness](/sd/C04/Efficiency%20vs%20Effectiveness) — the full VCAA lists: exactly 3 efficiency factors and 11 effectiveness factors; only the ones this glossary defines appear above
sd/C05/C05-home.md ..
@@ 6,6 6,10 @@
	---
+	## Foundations
+
+	- [Essential Terms](/sd/C05/Essential%20Terms) — the C05 glossary; click a term to expand its definition
+
	## C5-1 — Design tools
	Turning the chosen idea into designs another person could build from. Each page below targets a specific point where marks are commonly lost.
/dev/null .. sd/C05/Essential Terms.md
@@ 0,0 1,143 @@
+	<!-- Generated from applied-computing-au vic/unit3-4/sat/C05-2026/C05-essential-terms.md by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. -->
+	# Essential Terms — C05
+
+	The Hamilton and Alexandra College · Year 12 · 2026
+
+	A glossary of every term you need to recognise and use correctly across C05. 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["C05 vocabulary<br/>31 terms"]
+	R --> G0["Design tools<br/>7 terms"]
+	R --> G1["Design principles<br/>7 terms"]
+	R --> G2["UX characteristics<br/>4 terms"]
+	R --> G3["Usability and accessibility<br/>5 terms"]
+	R --> G4["Evaluation words<br/>6 terms"]
+	R --> G5["Thinking styles<br/>2 terms"]
+	```
+
+	*Where the C05 vocabulary sits, and how much of it is in each group — the 6 sections below follow the same order. Revise the heavy groups first.*
+
+	---
+
+	## Design tools
+
+	>| ### Annotate
+	>| Add comments to a document or diagram.
+
+	>| ### Data dictionary (software design)
+	>| Used to plan storage structure; provides specifications of variables, arrays and GUI objects, with reference to data types, data structures and data sources.
+
+	>| ### Design ideas
+	>| Conceptual solutions or creative approaches intended to address a specific problem or requirement in a design process.
+
+	>| ### IPO chart
+	>| A tabular method of conceptualising how data is received, processed and returned, typically presented in a three-column table.
+
+	>| ### Mock-up
+	>| An annotated visual representation of the user interface of a software solution, used to aid in the design of an interface.
+
+	>| ### Object description
+	>| A design tool that describes all of the relevant properties, methods and events in an object or class.
+
+	>| ### Pseudocode
+	>| Code that designs algorithms in a clear, human-readable, language-independent format using Structured English.
+
+	---
+
+	## Design principles
+
+	>| ### Alignment
+	>| A design principle concerned with how elements are positioned relative to each other and the page, improving clarity and readability.
+
+	>| ### Balance
+	>| A design principle concerned with the distribution of visual weight across an interface, contributing to attractiveness and usability.
+
+	>| ### Contrast
+	>| A design principle concerned with the difference between elements that makes them stand out from each other, essential for accessibility and readability.
+
+	>| ### Design principles
+	>| Principles that influence the appearance and functionality of a solution, including alignment, balance, contrast, space, text formatting, usability and navigation.
+
+	>| ### Navigation
+	>| A design principle concerned with how users move through software, directly impacting efficiency and usability.
+
+	>| ### Space (white space)
+	>| A design principle concerned with the empty areas between and around elements, improving clarity, readability and reducing cognitive load.
+
+	>| ### Text formatting
+	>| A design principle concerned with how text appears and is structured in an interface, enhancing readability and supporting accessibility.
+
+	---
+
+	## UX characteristics
+
+	>| ### Affordance
+	>| The visual clues in an interface that tell users how they can interact with elements, making the software intuitive and self-explanatory through design.
+
+	>| ### Interoperability
+	>| The ability of software to work seamlessly with other systems, applications and devices, supporting efficiency by allowing smooth integration into existing workflows.
+
+	>| ### Usability
+	>| Ease of use to achieve specified goals in terms of efficiency, effectiveness and satisfaction.
+
+	>| ### User experience (UX)
+	>| The overall experience a user has when interacting with software, influenced by factors including affordance, interoperability, security and usability.
+
+	---
+
+	## Usability and accessibility
+
+	>| ### Accessibility
+	>| How easily the software can be used by those who experience disabilities.
+
+	>| ### Assistive technology
+	>| Any device or system that is designed for individuals who would otherwise find the task difficult or impossible.
+
+	>| ### Clarity
+	>| Ease of understanding.
+
+	>| ### Readability
+	>| The ease of understanding the text.
+
+	>| ### Universal design
+	>| Designing products that can be used by people with a wide range of abilities and disabilities.
+
+	---
+
+	## Evaluation words
+
+	>| ### Attractiveness
+	>| How pleasing something is to the viewer.
+
+	>| ### Communication of message
+	>| The process through which meaning is transferred.
+
+	>| ### Completeness
+	>| Nothing left out.
+
+	>| ### Effectiveness
+	>| Produces the expected result.
+
+	>| ### Efficiency
+	>| Economic use of resources with minimum waste.
+
+	>| ### Evaluation criteria
+	>| Rules set out during design that include effectiveness and efficiency criteria; based on the solution's requirements, which were defined during analysis.
+
+	---
+
+	## Thinking styles
+
+	>| ### Convergent thinking
+	>| Involves coming up with a single, well-established answer to a problem.
+
+	>| ### Divergent thinking
+	>| Involves exploring many possible solutions using spontaneous, free-flowing techniques.
+
+	---
+
+	## See also
+
+	- [C05 home page](/sd/C05/C05-home) — everything else for this criterion
+	- [Efficiency vs Effectiveness](/sd/C04/Efficiency%20vs%20Effectiveness) — the full VCAA lists: exactly 3 efficiency factors and 11 effectiveness factors; only the ones this glossary defines appear above
sd/C06/C06-home.md ..
@@ 7,6 7,10 @@
	Each page covers one topic: the VCE definition, the GDScript syntax, a minimal worked example in the shared **Myki fare app** domain, and the **evidence standard** — what earns each skill-code tick and what does not. Your checkpoint and validation feedback — from your teacher or an AI reviewer — is graded against these pages, so what they say *is* the standard.
+	## Foundations
+
+	- [Essential Terms](/sd/C06/Essential%20Terms) — the C06 glossary; click a term to expand its definition
+
	## Using these pages for your checkpoint
	1. Pick a nominated feature you have built.
/dev/null .. sd/C06/Essential Terms.md
@@ 0,0 1,262 @@
+	<!-- Generated from applied-computing-au vic/unit3-4/sat/C06-2026/C06-essential-terms.md by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. -->
+	# Essential Terms — C06
+
+	The Hamilton and Alexandra College · Year 12 · 2026
+
+	A glossary of every term you need to recognise and use correctly across C06. Click a term to expand its definition. The C06 pages — and the feedback graded against them — use these words, so learn them in the language the rubric uses.
+
+	```mermaid
+	flowchart TD
+	R["C06 vocabulary<br/>66 terms"]
+	R --> G0["Language and execution<br/>8 terms"]
+	R --> G1["Operators<br/>3 terms"]
+	R --> G2["Control structures<br/>11 terms"]
+	R --> G3["Variables and constants<br/>5 terms"]
+	R --> G4["Data types<br/>6 terms"]
+	R --> G5["Data structures<br/>7 terms"]
+	R --> G6["Data sources<br/>8 terms"]
+	R --> G7["Functions and methods<br/>10 terms"]
+	R --> G8["OOP features<br/>8 terms"]
+	```
+
+	*Where the C06 vocabulary sits, and how much of it is in each group — the 9 sections below follow the same order. Revise the heavy groups first.*
+
+	---
+
+	## Language and execution
+
+	>| ### compiler
+	>| A program that turns source code into machine language that can be executed by a computer processor.
+
+	>| ### event
+	>| A special type of method that is called when an object's state changes.
+
+	>| ### flow of execution
+	>| The order in which instructions, conditions, and iterations are executed or evaluated.
+
+	>| ### graphical user interface (GUI)
+	>| A type of user interface that allows users to interact through visual elements such as windows, icons, and buttons.
+
+	>| ### hard-coding
+	>| To include fixed data in a program that cannot be changed during runtime and can only be changed by modifying the program source code.
+
+	>| ### instruction
+	>| A unit of code that can be executed by a compiler or interpreter.
+
+	>| ### interpreter
+	>| A computer program that directly executes source code without needing to have it compiled beforehand.
+
+	>| ### prolog
+	>| The information in an XML file that appears before the start of the document's contents, including information such as the XML version and character encoding that is being used.
+
+	---
+
+	## Operators
+
+	>| ### arithmetic operator
+	>| A symbol in programming that performs basic mathematical operations such as addition, subtraction, multiplication, and division.
+
+	>| ### conditional operator
+	>| A symbol used to compare two values within a condition, such as equals (`==`), not equals (`!=`), greater than (`>`), less than (`<`), greater than or equal to (`>=`), or less than or equal to (`<=`). Used inside selection and iteration conditions to decide whether a branch runs or a loop continues. (Not to be confused with the ternary conditional *expression*, e.g. `x if condition else y` in Python — that's shorthand for an if/else selection, not a comparison.)
+
+	>| ### logical operator
+	>| A Boolean operator used to combine expressions, such as AND, OR.
+
+	---
+
+	## Control structures
+
+	>| ### alternative execution
+	>| Code that is run if a condition is not met.
+
+	>| ### chained selection
+	>| A selection structure with more than one condition checked in sequence (e.g. `if` / `elif` / `elif` / `else`), where each branch can test a different condition. Execution stops at the first branch whose condition is true.
+
+	>| ### DO/WHILE
+	>| An iteration over a set of instructions, conditions, and/or iterations that is repeated for as long as a condition is met; it is always run at least once.
+
+	>| ### FOR
+	>| An iteration over a set of instructions that is repeated a predefined number of times.
+
+	>| ### infinite loop
+	>| An iteration that will never reach the condition upon which it can terminate.
+
+	>| ### nested selection
+	>| When a selection contains one or more additional conditions within its structure.
+
+	>| ### REPEAT/UNTIL
+	>| An iteration over a set of instructions that is repeated for as long as a condition is not met; it will always execute at least once.
+
+	>| ### selection statement
+	>| A control structure that allows a programmer to write lines of code that are only run when a particular requirement is met.
+
+	>| ### sequence
+	>| A set of instructions that executes line by line in the order that it is written.
+
+	>| ### switch/case
+	>| A selection structure that compares a single value or expression against a list of specific possible values (cases), running the matching branch's code (e.g. `match`/`case` in Python, `switch`/`case` in TypeScript). Unlike chained selection, every case tests the *same* expression for equality against a different value, rather than evaluating independent conditions per branch.
+
+	>| ### WHILE
+	>| An iteration over a set of instructions that is repeated for as long as a condition is met.
+
+	---
+
+	## Variables and constants
+
+	>| ### casting
+	>| Converting a variable from one data type to another, such as converting a string to an integer.
+
+	>| ### constant
+	>| A fixed value that, once defined, cannot be altered during the execution of a program.
+
+	>| ### global variables
+	>| Variables that are defined outside any function and can be accessed by all functions throughout the source code.
+
+	>| ### local variables
+	>| Variables that are defined inside a function that can only be accessed by that function.
+
+	>| ### variable
+	>| A method of storing and labelling data to be referenced and manipulated in a computer program.
+
+	---
+
+	## Data types
+
+	>| ### Boolean
+	>| A data type with one of two possible values, 0 and 1, usually referred to as False and True, respectively.
+
+	>| ### character
+	>| A data type representing any single meaningful unit, such as a letter, a number, a punctuation mark, a symbol or even a space.
+
+	>| ### data type
+	>| A method of classifying a variable to determine the data that variable can contain, as well as how that variable can be manipulated.
+
+	>| ### floating point
+	>| Computer representation of real numbers, with decimal places.
+
+	>| ### integer
+	>| A data type representing whole positive and negative numbers.
+
+	>| ### numeric
+	>| A data type consisting of whole numbers, referred to as integers, and decimal numbers, referred to as floating points.
+
+	---
+
+	## Data structures
+
+	>| ### array
+	>| A list of elements indexed by position. In most programming languages, the first element has index zero.
+
+	>| ### data structure
+	>| A method of organising data to allow particular operations to be performed on it efficiently.
+
+	>| ### dimension
+	>| The direction or the level of organisation within a data structure, such as an array.
+
+	>| ### field
+	>| A single data item in a record (e.g. FamilyName).
+
+	>| ### record
+	>| A complete set of fields relating to an entity, such as a person.
+
+	>| ### tree
+	>| The structure of an XML file that contains a root element and all of its sub-elements.
+
+	>| ### two-dimensional array
+	>| A data structure that stores elements in a grid-like format, organised into rows and columns, allowing access using two indices.
+
+	---
+
+	## Data sources
+
+	>| ### child element
+	>| Any sub-element of a parent element in an XML file.
+
+	>| ### CSV
+	>| A comma-separated value file, which is a delimited file separated by commas.
+
+	>| ### delimiter
+	>| The character used to separate data values in a delimited file.
+
+	>| ### parent element
+	>| Any element in an XML file that contains at least one sub-element.
+
+	>| ### plain text (TXT) file
+	>| A structured file that contains characters of readable data.
+
+	>| ### root element
+	>| A parent element to all other elements in an XML file.
+
+	>| ### text file
+	>| A structured file containing sequences of characters that are not encrypted, such as a plain text file or CSV file.
+
+	>| ### XML
+	>| Extensible Markup Language; a metalanguage that allows for user-defined tags and rules for encoding documents in a format that is readable by humans and machines.
+
+	---
+
+	## Functions and methods
+
+	>| ### arguments
+	>| Specific inputs passed into a function that act as local, temporary variables.
+
+	>| ### function
+	>| A sequence of related code that has been given a name that can be called from other points in the source code.
+
+	>| ### function call
+	>| To execute the contents of a function.
+
+	>| ### function declaration
+	>| To name a function and its arguments.
+
+	>| ### function definition
+	>| To define (write) the contents of a function.
+
+	>| ### method
+	>| An action an object can carry out (e.g., window.refresh, golfClub.swing).
+
+	>| ### parameters
+	>| See arguments.
+
+	>| ### pass by reference
+	>| To pass data into a function as an argument so that it can be modified without needing to be returned.
+
+	>| ### pass by value
+	>| To pass data into a function as an argument so that it cannot be modified without needing to be returned.
+
+	>| ### return value
+	>| A value or set of values that is passed back to the origin of a calling function, often to be assigned to a variable, used in an equation, or tested within a conditional statement.
+
+	---
+
+	## OOP features
+
+	>| ### abstraction
+	>| An object-oriented programming language principle that allows programmers to manage complexity by hiding implementation details and exposing only the essential features of an object.
+
+	>| ### class
+	>| A program code template for creating objects in object-oriented programming languages.
+
+	>| ### encapsulation
+	>| An object-oriented programming principle that involves bundling the data and methods that operate on the data into a single unit or class.
+
+	>| ### generalization
+	>| The process of defining a general class (superclass) that encapsulates common attributes and behaviors of more specific classes (subclasses).
+
+	>| ### inheritance
+	>| A method of basing an object or class on another object or class, taking on its attributes and methods and potentially extending upon them.
+
+	>| ### instantiation
+	>| In object-oriented programming, the process by which an object is created from a class.
+
+	>| ### object
+	>| Any instantiated class that a program can inspect and/or change, in terms of appearance, behavior, or data.
+
+	>| ### object-oriented programming (OOP)
+	>| A programming language based on the concept of objects that contain data in the form of fields or attributes and code in the form of methods.
+
+	---
+
+	## See also
+
+	- [C06 home page](/sd/C06/C06-home) — everything else for this criterion
sd/C07/C07-home.md ..
@@ 9,6 9,10 @@
	**Where C7 is assessed:** C7 does not run its own validation. All three indicators are assessed **live in Part B** of the single 100-minute Live Coding Validation, on your comment-stripped copy of the one feature the teacher picks: a **naming audit** (C7-1), writing the **internal documentation from scratch** (C7-2), and adding **input validation** with a test run to show the checks fire (C7-3).
+	## Foundations
+
+	- [Essential Terms](/sd/C07/Essential%20Terms) — the C07 glossary; click a term to expand its definition
+
	## Using these pages for your checkpoint
	1. Pick a nominated feature you have built.
/dev/null .. sd/C07/Essential Terms.md
@@ 0,0 1,76 @@
+	<!-- 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
sd/C08/C08-home.md ..
@@ 14,6 14,10 @@
	The checkpoint is the gateway: arrive with a genuine plan and portfolio, and the validation is a walk-through of work you already own.
+	## Foundations
+
+	- [Essential Terms](/sd/C08/Essential%20Terms) — the C08 glossary; click a term to expand its definition
+
	## Pages
	**Debugging (C8-1)**
/dev/null .. sd/C08/Essential Terms.md
@@ 0,0 1,110 @@
+	<!-- 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
sd/C09/Essential Terms.md ..
@@ 1,57 1,87 @@
-	<!-- Generated from applied-computing-au vic/unit3-4/sat/C09-2026 by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. -->
-	## Topics:
-	- Beta Testing
-	- Test Scenarios
-	- Data Collection from Beta Testers
-	- Reporting Results
-	- Modifications Based on Feedback
-	- Personas
+	<!-- Generated from applied-computing-au vic/unit3-4/sat/C09-2026/C09-essential-terms.md by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. -->
+	# Essential Terms — C09
+	The Hamilton and Alexandra College · Year 12 · 2026
-	> [!note]- Beta testing
-	> The phase of software testing where a sample of the intended audience tests the software in a real environment.
+	A glossary of every term you need to recognise and use correctly across C09. 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.
-	> [!note]- Test scenario
-	> A specific situation or workflow that a beta tester is asked to perform in order to evaluate the functionality, usability or reliability of the software.
+	```mermaid
+	flowchart TD
+	R["C09 vocabulary<br/>16 terms"]
+	R --> G0["Beta testing<br/>4 terms"]
+	R --> G1["Data collection from beta testers<br/>4 terms"]
+	R --> G2["Reporting results<br/>4 terms"]
+	R --> G3["Modifications based on feedback<br/>4 terms"]
+	```
-	> [!note]- Test plan
-	> A document that outlines the objectives, scope, schedule and approach for beta testing, including which features to test and what data to collect.
+	*Where the C09 vocabulary sits, and how much of it is in each group — the 4 sections below follow the same order. Revise the heavy groups first.*
-	> [!note]- Personas
-	> Fictional characters created based on user research to represent the different user types that might use a service, application, product, site or brand.
+	---
-	> [!note]- Data collection
-	> The systematic gathering of feedback, observations and measurements from beta testers during and after testing sessions.
+	## Beta testing
-	> [!note]- Observation (beta testing)
-	> Watching beta testers interact with the software to identify usability issues, confusion points or unexpected behaviours.
+	>| ### Beta testing
+	>| The phase of software testing where a sample of the intended audience tests the software in a real environment.
-	> [!note]- Survey
-	> A structured set of questions given to beta testers to collect quantitative and qualitative feedback about their experience with the software.
+	>| ### Test scenario
+	>| A specific situation or workflow that a beta tester is asked to perform in order to evaluate the functionality, usability or reliability of the software.
-	> [!note]- Bug report
-	> A documented record of an error or defect found during beta testing, typically including steps to reproduce, expected behaviour and actual behaviour.
+	>| ### Test plan
+	>| A document that outlines the objectives, scope, schedule and approach for beta testing, including which features to test and what data to collect.
-	> [!note]- Reporting results
-	> The process of compiling and presenting beta testing findings, including issues discovered, tester feedback and recommendations for improvement.
+	>| ### Personas
+	>| Fictional characters created based on user research to represent the different user types that might use a service, application, product, site or brand.
-	> [!note]- Modifications
-	> Changes made to the software based on feedback and issues identified during beta testing, aimed at improving functionality, usability or performance.
+	---
-	> [!note]- Functionality
-	> The range of operations that can be performed by a software system as defined by its requirements.
+	## Data collection from beta testers
-	> [!note]- Usability
-	> The ease with which a user can interact with a software system to achieve their goals efficiently and satisfactorily.
+	>| ### Data collection
+	>| The systematic gathering of feedback, observations and measurements from beta testers during and after testing sessions.
-	> [!note]- Evaluation criteria
-	> Performance criteria made from the expectations and specification, used to judge whether the software meets its intended purpose.
+	>| ### Observation (beta testing)
+	>| Watching beta testers interact with the software to identify usability issues, confusion points or unexpected behaviours.
-	> [!note]- Testing table
-	> A commonly used way to record evidence of functionality testing, documenting test cases, expected results and actual results.
+	>| ### Survey
+	>| A structured set of questions given to beta testers to collect quantitative and qualitative feedback about their experience with the software.
-	> [!note]- Feedback
-	> Information provided by beta testers about their experience, including issues encountered, suggestions for improvement and overall satisfaction.
+	>| ### Feedback
+	>| Information provided by beta testers about their experience, including issues encountered, suggestions for improvement and overall satisfaction.
-	> [!note]- Priority (bug classification)
-	> A ranking assigned to an issue found during beta testing that indicates how urgently it needs to be addressed before release.
+	---
+
+	## Reporting results
+
+	>| ### Bug report
+	>| A documented record of an error or defect found during beta testing, typically including steps to reproduce, expected behaviour and actual behaviour.
+
+	>| ### Reporting results
+	>| The process of compiling and presenting beta testing findings, including issues discovered, tester feedback and recommendations for improvement.
+
+	>| ### Testing table
+	>| A commonly used way to record evidence of functionality testing, documenting test cases, expected results and actual results.
+
+	>| ### Priority (bug classification)
+	>| A ranking assigned to an issue found during beta testing that indicates how urgently it needs to be addressed before release.
+
+	---
+
+	## Modifications based on feedback
+
+	>| ### Modifications
+	>| Changes made to the software based on feedback and issues identified during beta testing, aimed at improving functionality, usability or performance.
+
+	>| ### Functionality
+	>| The range of operations that can be performed by a software system as defined by its requirements.
+
+	>| ### Usability
+	>| The ease with which a user can interact with a software system to achieve their goals efficiently and satisfactorily.
+
+	>| ### Evaluation criteria
+	>| Performance criteria made from the expectations and specification, used to judge whether the software meets its intended purpose.
+
+	---
+
+	## See also
+
+	- [C09 home page](/sd/C09/C09-home) — everything else for this criterion
sd/C10/Essential Terms.md ..
@@ 1,27 1,26 @@
-	<!-- Generated from applied-computing-au vic/unit3-4/sat/C10-2026 by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. -->
+	<!-- Generated from applied-computing-au vic/unit3-4/sat/C10-2026/C10-essential-terms.md by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. -->
	# Essential Terms — C10
-	*Every term you need to recognise and use correctly across C10. Click a term to reveal its definition — if you cannot define it in your own words, you cannot use it in a class write.*
+	The Hamilton and Alexandra College · Year 12 · 2026
+
+	A glossary of every term you need to recognise and use correctly across C10. Click a term to expand its definition. The three class writes are handwritten with no internet and no notes, so this vocabulary has to be in your head.
	```mermaid
	flowchart TD
-	V["C10 vocabulary"] --> A["The judgement<br/>evaluation · evaluation criteria<br/>testing · beta testing"]
-	V --> B["What you judge against<br/>SRS · functional requirements<br/>non-functional requirements<br/>constraints · solution boundaries"]
-	V --> D["Quality factors defined here<br/>efficiency: functionality<br/>effectiveness: accuracy · usability<br/>accessibility · relevance · timeliness<br/>completeness · maintainability"]
-	V --> E["The plan<br/>project management · Gantt chart<br/>version control · PSM"]
-	V --> F["Why plans move<br/>scope creep · personnel changes<br/>technical issues"]
-	D -.-> G["Nearby, but NOT VCAA factors<br/>reliability · fit for purpose"]
+	R["C10 vocabulary<br/>26 terms"]
+	R --> G0["The judgement<br/>4 terms"]
+	R --> G1["What you judge against<br/>5 terms"]
+	R --> G2["Quality factors defined here<br/>8 terms"]
+	R --> G3["The plan<br/>4 terms"]
+	R --> G4["Why plans move<br/>3 terms"]
+	R --> G5["Nearby, but NOT VCAA factors<br/>2 terms"]
	```
-	*The glossary is one long list; the clusters above are the five jobs those words do in C10. The full VCAA lists are **3 efficiency factors** and **11 effectiveness factors** — see [Efficiency vs Effectiveness](/sd/C04/Efficiency%20vs%20Effectiveness) for the complete table. Only the factors this glossary defines are shown.*
+	*Where the C10 vocabulary sits, and how much of it is in each group — the 6 sections below follow the same order. Revise the heavy groups first.*
-	## Topics:
-	- Evaluation of solution against SRS and criteria
-	- Reviewing the development process
-	- Assessing plan modifications
-	- Evaluating plan effectiveness
-	- Scope creep, personnel changes and technical issues
+	---
+	## The judgement
	>| ### Evaluation
	>| The final stage of the problem-solving methodology. It checks how well the solution is satisfying the needs of the user for which it was originally created.
@@ 29,6 28,16 @@
	>| ### Evaluation criteria
	>| Performance criteria made from the expectations and specification.
+	>| ### Testing
+	>| Checks the accuracy of information outputs.
+
+	>| ### Beta testing
+	>| The phase of software testing where a sample of the intended audience tests the software in a real environment.
+
+	---
+
+	## What you judge against
+
	>| ### Software requirements specification (SRS)
	>| A single document that contains the outcomes of the analysis stage of the problem-solving methodology, including scope, constraints, functional requirements and non-functional requirements.
@@ 38,6 47,16 @@
	>| ### Non-functional requirements
	>| Qualitative requirements of a solution, often tied to solution constraints.
+	>| ### Constraints
+	>| Factors that may limit or restrict solution requirements.
+
+	>| ### Solution boundaries
+	>| The limits or edges of what a project or solution will encompass.
+
+	---
+
+	## Quality factors defined here
+
	>| ### Completeness
	>| The extent to which all necessary features and functionality are included in the software.
@@ 59,14 78,12 @@
	>| ### Timeliness
	>| The ability of software to provide information or functionality when it is needed, without undue delay.
-	>| ### Scope creep
-	>| The tendency for a project's requirements to increase over time, often leading to delays and budget overruns.
+	>| ### Maintainability
+	>| How easy a solution is to look after once it has been put in place.
-	>| ### Personnel changes
-	>| Modifications or transitions in the team composition that can impact the development process and timelines.
+	---
-	>| ### Technical issues
-	>| Challenges or problems related to the technology being used in software development, potentially impacting project progress.
+	## The plan
	>| ### Project management
	>| A method of recording the progress of a project and managing resources to operate within time, resource and cost availability.
@@ 77,26 94,35 @@
	>| ### Problem-solving methodology (PSM)
	>| An approach that develops the stages involved in solving a problem.
-	>| ### Constraints
-	>| Factors that may limit or restrict solution requirements.
+	>| ### Version control
+	>| The method that keeps track of the current, most up-to-date document through a drafting process.
-	>| ### Solution boundaries
-	>| The limits or edges of what a project or solution will encompass.
+	---
+
+	## Why plans move
+
+	>| ### Scope creep
+	>| The tendency for a project's requirements to increase over time, often leading to delays and budget overruns.
+
+	>| ### Personnel changes
+	>| Modifications or transitions in the team composition that can impact the development process and timelines.
+
+	>| ### Technical issues
+	>| Challenges or problems related to the technology being used in software development, potentially impacting project progress.
+
+	---
+
+	## Nearby, but NOT VCAA factors
	>| ### Fit for purpose
	>| To be well suited for a role or purpose.
-	>| ### Maintainability
-	>| How easy a solution is to look after once it has been put in place.
-
	>| ### Reliability
	>| How much a solution can be depended upon to function as designed, and for how long.
-	>| ### Version control
-	>| The method that keeps track of the current, most up-to-date document through a drafting process.
+	---
-	>| ### Testing
-	>| Checks the accuracy of information outputs.
+	## See also
-	>| ### Beta testing
-	>| The phase of software testing where a sample of the intended audience tests the software in a real environment.
\	No newline at end of file
+	- [C10 home page](/sd/C10/C10-home) — everything else for this criterion
+	- [Efficiency vs Effectiveness](/sd/C04/Efficiency%20vs%20Effectiveness) — the full VCAA lists: exactly 3 efficiency factors and 11 effectiveness factors; only the ones this glossary defines appear above