Home A - Z
Page Index

An Otter Wiki

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/C03-2026/C03-essential-terms.md by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. -->
2
# Essential Terms — C03
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 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.
7
8
```mermaid
9
flowchart TD
10
R["C03 vocabulary<br/>20 terms"]
11
R --> G0["The SRS<br/>3 terms"]
12
R --> G1["Requirements<br/>2 terms"]
13
R --> G2["Constraints<br/>6 terms"]
14
R --> G3["Solution boundaries and scope<br/>2 terms"]
15
R --> G4["Quality words used in non-functional requirements<br/>7 terms"]
16
```
17
18
*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.*
19
20
---
21
22
## The SRS
23
24
>| ### Software requirements specification (SRS)
25
>| 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.
26
27
>| ### Solution requirements
28
>| What the client needs from the solution in relation to its features.
29
30
>| ### Analysis stage
31
>| The stage of the problem-solving methodology where solution requirements, constraints and scope are determined.
32
33
---
34
35
## Requirements
36
37
>| ### Functional requirements
38
>| The desired operations of a program that have specified inputs, behaviours and outputs.
39
40
>| ### Non-functional requirements
41
>| Qualitative requirements of a solution, often tied to solution constraints.
42
43
---
44
45
## Constraints
46
47
>| ### Constraints
48
>| Factors that may limit or restrict solution requirements.
49
50
>| ### Technical constraints
51
>| The limitations and restrictions related to the technology used in a project.
52
53
>| ### Economic constraints
54
>| The limitations on a project or decision imposed by financial factors.
55
56
>| ### Legal constraints
57
>| The limitations and requirements imposed on a project or decision by laws, regulations and legal standards.
58
59
>| ### Social constraints
60
>| The limitations imposed on a project or decision by societal norms, values and expectations.
61
62
>| ### Non-technical constraints
63
>| Limitations relating to areas other than hardware and software: social, legal and usability.
64
65
---
66
67
## Solution boundaries and scope
68
69
>| ### Scope
70
>| The boundaries or parameters of the solution - what it will do and what it will not do.
71
72
>| ### Solution boundaries
73
>| The limits or edges of what a project or solution will encompass.
74
75
---
76
77
## Quality words used in non-functional requirements
78
79
>| ### Fit for purpose
80
>| To be well suited for a role or purpose.
81
82
>| ### Functionality
83
>| The extent to which a solution is suited to its purpose.
84
85
>| ### Usability
86
>| The extent to which a system is easy to learn and use.
87
88
>| ### Reliability
89
>| How much a solution can be depended upon to function as designed, and for how long.
90
91
>| ### Portability
92
>| How easily a solution is able to be used in different operating environments.
93
94
>| ### Robustness
95
>| How well a software solution responds to errors that occur when the software is being used.
96
97
>| ### Maintainability
98
>| How easy a solution is to look after once it has been put in place.
99
100
---
101
102
## See also
103
104
- [C03 home page](/sd/C03/C03-home) — everything else for this criterion
105
- [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