<!-- 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 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 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"] ``` *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.* --- ## 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. >| ### 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. >| ### 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 >| 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. >| ### Functionality >| The extent to which a solution is suited to its purpose. >| ### Accuracy >| The degree to which software correctly performs its intended functions without errors. >| ### Usability >| The extent to which a system is easy to learn and use. >| ### Accessibility >| Ensures that software can be used by people with a wide range of abilities and disabilities. >| ### Relevance >| The degree to which software meets the current needs and requirements of its users or market. >| ### Timeliness >| The ability of software to provide information or functionality when it is needed, without undue delay. >| ### Maintainability >| How easy a solution is to look after once it has been put in place. --- ## The plan >| ### Project management >| A method of recording the progress of a project and managing resources to operate within time, resource and cost availability. >| ### 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. >| ### Problem-solving methodology (PSM) >| An approach that develops the stages involved in solving a problem. >| ### Version control >| The method that keeps track of the current, most up-to-date document through a drafting process. --- ## 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. >| ### Reliability >| How much a solution can be depended upon to function as designed, and for how long. --- ## See also - [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