<!-- 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