Blame
|
1 | <!-- 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. --> |
||||||
|
2 | # Essential Terms — C10 |
||||||
| 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 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. |
|||||||
|
7 | |||||||
| 8 | ```mermaid |
|||||||
| 9 | flowchart TD |
|||||||
|
10 | R["C10 vocabulary<br/>26 terms"] |
||||||
| 11 | R --> G0["The judgement<br/>4 terms"] |
|||||||
| 12 | R --> G1["What you judge against<br/>5 terms"] |
|||||||
| 13 | R --> G2["Quality factors defined here<br/>8 terms"] |
|||||||
| 14 | R --> G3["The plan<br/>4 terms"] |
|||||||
| 15 | R --> G4["Why plans move<br/>3 terms"] |
|||||||
| 16 | R --> G5["Nearby, but NOT VCAA factors<br/>2 terms"] |
|||||||
|
17 | ``` |
||||||
| 18 | ||||||||
|
19 | *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.* |
||||||
|
20 | |||||||
|
21 | --- |
||||||
|
22 | |||||||
|
23 | ## The judgement |
||||||
|
24 | |||||||
| 25 | >| ### Evaluation |
|||||||
| 26 | >| 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. |
|||||||
| 27 | ||||||||
| 28 | >| ### Evaluation criteria |
|||||||
| 29 | >| Performance criteria made from the expectations and specification. |
|||||||
| 30 | ||||||||
|
31 | >| ### Testing |
||||||
| 32 | >| Checks the accuracy of information outputs. |
|||||||
| 33 | ||||||||
| 34 | >| ### Beta testing |
|||||||
| 35 | >| The phase of software testing where a sample of the intended audience tests the software in a real environment. |
|||||||
| 36 | ||||||||
| 37 | --- |
|||||||
| 38 | ||||||||
| 39 | ## What you judge against |
|||||||
| 40 | ||||||||
|
41 | >| ### Software requirements specification (SRS) |
||||||
| 42 | >| 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. |
|||||||
| 43 | ||||||||
| 44 | >| ### Functional requirements |
|||||||
| 45 | >| The desired operations of a program that have specified inputs, behaviours and outputs. |
|||||||
| 46 | ||||||||
| 47 | >| ### Non-functional requirements |
|||||||
| 48 | >| Qualitative requirements of a solution, often tied to solution constraints. |
|||||||
| 49 | ||||||||
|
50 | >| ### Constraints |
||||||
| 51 | >| Factors that may limit or restrict solution requirements. |
|||||||
| 52 | ||||||||
| 53 | >| ### Solution boundaries |
|||||||
| 54 | >| The limits or edges of what a project or solution will encompass. |
|||||||
| 55 | ||||||||
| 56 | --- |
|||||||
| 57 | ||||||||
| 58 | ## Quality factors defined here |
|||||||
| 59 | ||||||||
|
60 | >| ### Completeness |
||||||
| 61 | >| The extent to which all necessary features and functionality are included in the software. |
|||||||
| 62 | ||||||||
| 63 | >| ### Functionality |
|||||||
| 64 | >| The extent to which a solution is suited to its purpose. |
|||||||
| 65 | ||||||||
| 66 | >| ### Accuracy |
|||||||
| 67 | >| The degree to which software correctly performs its intended functions without errors. |
|||||||
| 68 | ||||||||
| 69 | >| ### Usability |
|||||||
| 70 | >| The extent to which a system is easy to learn and use. |
|||||||
| 71 | ||||||||
| 72 | >| ### Accessibility |
|||||||
| 73 | >| Ensures that software can be used by people with a wide range of abilities and disabilities. |
|||||||
| 74 | ||||||||
| 75 | >| ### Relevance |
|||||||
| 76 | >| The degree to which software meets the current needs and requirements of its users or market. |
|||||||
| 77 | ||||||||
| 78 | >| ### Timeliness |
|||||||
| 79 | >| The ability of software to provide information or functionality when it is needed, without undue delay. |
|||||||
| 80 | ||||||||
|
81 | >| ### Maintainability |
||||||
| 82 | >| How easy a solution is to look after once it has been put in place. |
|||||||
|
83 | |||||||
|
84 | --- |
||||||
|
85 | |||||||
|
86 | ## The plan |
||||||
|
87 | |||||||
| 88 | >| ### Project management |
|||||||
| 89 | >| A method of recording the progress of a project and managing resources to operate within time, resource and cost availability. |
|||||||
| 90 | ||||||||
| 91 | >| ### Gantt chart |
|||||||
| 92 | >| 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. |
|||||||
| 93 | ||||||||
| 94 | >| ### Problem-solving methodology (PSM) |
|||||||
| 95 | >| An approach that develops the stages involved in solving a problem. |
|||||||
| 96 | ||||||||
|
97 | >| ### Version control |
||||||
| 98 | >| The method that keeps track of the current, most up-to-date document through a drafting process. |
|||||||
|
99 | |||||||
|
100 | --- |
||||||
| 101 | ||||||||
| 102 | ## Why plans move |
|||||||
| 103 | ||||||||
| 104 | >| ### Scope creep |
|||||||
| 105 | >| The tendency for a project's requirements to increase over time, often leading to delays and budget overruns. |
|||||||
| 106 | ||||||||
| 107 | >| ### Personnel changes |
|||||||
| 108 | >| Modifications or transitions in the team composition that can impact the development process and timelines. |
|||||||
| 109 | ||||||||
| 110 | >| ### Technical issues |
|||||||
| 111 | >| Challenges or problems related to the technology being used in software development, potentially impacting project progress. |
|||||||
| 112 | ||||||||
| 113 | --- |
|||||||
| 114 | ||||||||
| 115 | ## Nearby, but NOT VCAA factors |
|||||||
|
116 | |||||||
| 117 | >| ### Fit for purpose |
|||||||
| 118 | >| To be well suited for a role or purpose. |
|||||||
| 119 | ||||||||
| 120 | >| ### Reliability |
|||||||
| 121 | >| How much a solution can be depended upon to function as designed, and for how long. |
|||||||
| 122 | ||||||||
|
123 | --- |
||||||
|
124 | |||||||
|
125 | ## See also |
||||||
|
126 | |||||||
|
127 | - [C10 home page](/sd/C10/C10-home) — everything else for this criterion |
||||||
| 128 | - [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 |
|||||||
