Home A - Z
Page Index

An Otter Wiki

Blame

5c1696 lisa 2026-08-29 16:39:27
Add sd/C10: hub + guides for the in-class model Seven curated learning pages plus the C10 home hub, generated by the shared port script (new c10 config): the C100-* cluster, the tick sheet, the solutions booklet and the assessment paperwork stay out of the wiki. Each page gains a skill title, a lead naming the rubric band it serves, one earned mermaid visual and a Check Your Understanding fold. The git-log examples are anonymised (prior-cohort names, hostnames and repo URL removed). 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/C10-2026 by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. -->
2
# Essential Terms — C10
3
4
*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.*
5
6
```mermaid
7
flowchart TD
8
V["C10 vocabulary"] --> A["The judgement<br/>evaluation · evaluation criteria<br/>testing · beta testing"]
9
V --> B["What you judge against<br/>SRS · functional requirements<br/>non-functional requirements<br/>constraints · solution boundaries"]
10
V --> D["Quality factors defined here<br/>efficiency: functionality<br/>effectiveness: accuracy · usability<br/>accessibility · relevance · timeliness<br/>completeness · maintainability"]
11
V --> E["The plan<br/>project management · Gantt chart<br/>version control · PSM"]
12
V --> F["Why plans move<br/>scope creep · personnel changes<br/>technical issues"]
13
D -.-> G["Nearby, but NOT VCAA factors<br/>reliability · fit for purpose"]
14
```
15
16
*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.*
17
18
## Topics:
19
- Evaluation of solution against SRS and criteria
20
- Reviewing the development process
21
- Assessing plan modifications
22
- Evaluating plan effectiveness
23
- Scope creep, personnel changes and technical issues
24
25
26
>| ### Evaluation
27
>| 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.
28
29
>| ### Evaluation criteria
30
>| Performance criteria made from the expectations and specification.
31
32
>| ### Software requirements specification (SRS)
33
>| 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.
34
35
>| ### Functional requirements
36
>| The desired operations of a program that have specified inputs, behaviours and outputs.
37
38
>| ### Non-functional requirements
39
>| Qualitative requirements of a solution, often tied to solution constraints.
40
41
>| ### Completeness
42
>| The extent to which all necessary features and functionality are included in the software.
43
44
>| ### Functionality
45
>| The extent to which a solution is suited to its purpose.
46
47
>| ### Accuracy
48
>| The degree to which software correctly performs its intended functions without errors.
49
50
>| ### Usability
51
>| The extent to which a system is easy to learn and use.
52
53
>| ### Accessibility
54
>| Ensures that software can be used by people with a wide range of abilities and disabilities.
55
56
>| ### Relevance
57
>| The degree to which software meets the current needs and requirements of its users or market.
58
59
>| ### Timeliness
60
>| The ability of software to provide information or functionality when it is needed, without undue delay.
61
62
>| ### Scope creep
63
>| The tendency for a project's requirements to increase over time, often leading to delays and budget overruns.
64
65
>| ### Personnel changes
66
>| Modifications or transitions in the team composition that can impact the development process and timelines.
67
68
>| ### Technical issues
69
>| Challenges or problems related to the technology being used in software development, potentially impacting project progress.
70
71
>| ### Project management
72
>| A method of recording the progress of a project and managing resources to operate within time, resource and cost availability.
73
74
>| ### Gantt chart
75
>| 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.
76
77
>| ### Problem-solving methodology (PSM)
78
>| An approach that develops the stages involved in solving a problem.
79
80
>| ### Constraints
81
>| Factors that may limit or restrict solution requirements.
82
83
>| ### Solution boundaries
84
>| The limits or edges of what a project or solution will encompass.
85
86
>| ### Fit for purpose
87
>| To be well suited for a role or purpose.
88
89
>| ### Maintainability
90
>| How easy a solution is to look after once it has been put in place.
91
92
>| ### Reliability
93
>| How much a solution can be depended upon to function as designed, and for how long.
94
95
>| ### Version control
96
>| The method that keeps track of the current, most up-to-date document through a drafting process.
97
98
>| ### Testing
99
>| Checks the accuracy of information outputs.
100
101
>| ### Beta testing
102
>| The phase of software testing where a sample of the intended audience tests the software in a real environment.