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/C01-2026/C01-essential-terms.md by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. -->
2
# Essential Terms — C01
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 C01. 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["C01 vocabulary<br/>21 terms"]
11
R --> G0["Problem-solving methodology<br/>5 terms"]
12
R --> G1["Design brief<br/>3 terms"]
13
R --> G2["Project management<br/>11 terms"]
14
R --> G3["Gantt chart<br/>2 terms"]
15
```
16
17
*Where the C01 vocabulary sits, and how much of it is in each group — the 4 sections below follow the same order. Revise the heavy groups first.*
18
19
---
20
21
## Problem-solving methodology
22
23
>| ### Analysis stage
24
>| The stage of the problem-solving methodology where solution requirements, constraints and scope are determined
25
26
>| ### Design stage
27
>| The stage of the problem-solving methodology where the function and appearance of a solution are planned, and evaluation criteria created
28
29
>| ### Development stage
30
>| The stage of the problem-solving methodology where the solution is coded, validated, tested and documented
31
32
>| ### Evaluation stage
33
>| The stage of the problem-solving methodology where the completed solution is evaluated against the evaluation criteria and the project plan is assessed
34
35
>| ### Problem-solving methodology (PSM)
36
>| An approach that develops the stages involved in solving a problem
37
38
---
39
40
## Design brief
41
42
>| ### Design brief
43
>| A document that identifies a problem, need or opportunity and describes the proposed software solution, its users, the programming language to be used, and how it is feasible and original
44
45
>| ### Feasibility
46
>| An assessment of whether a proposed solution is practical and achievable, commonly evaluated using the T.E.L.O.S. framework (Technical, Economic, Legal, Operational, Scheduling)
47
48
>| ### T.E.L.O.S.
49
>| A framework for assessing feasibility across five dimensions: Technical (can it be built?), Economic (can it be afforded?), Legal (is it lawful?), Operational (will it be used?), and Scheduling (can it be completed in time?)
50
51
---
52
53
## Project management
54
55
>| ### Concepts (project management)
56
>| The milestones and dependencies within a project timeline
57
58
>| ### Concurrently
59
>| When a task is carried out at the same time as another task
60
61
>| ### Critical path
62
>| The shortest possible time in which a project can be completed
63
64
>| ### Dependency
65
>| A relationship between two tasks in a project plan where one task cannot begin until another has been completed
66
67
>| ### Predecessor
68
>| A task that must be completed before another one can be performed
69
70
>| ### Processes (project management)
71
>| Task identification, sequencing and allocation of time and resources within a project timeline
72
73
>| ### Project management
74
>| A method of recording the progress of a project and managing resources to operate within time, resource and cost availability
75
76
>| ### Slack time
77
>| The length of time that a task can run overtime before affecting other tasks
78
79
>| ### Successor
80
>| A task that must be completed after another task
81
82
>| ### Work breakdown structure (WBS)
83
>| An often hierarchical breakdown of a project that organises the work to be done into manageable sections, often displayed as a visual outline or map
84
85
>| ### Monitoring
86
>| The ongoing process of tracking a project's progress against the plan, identifying delays or changes, and documenting adjustments made
87
88
---
89
90
## Gantt chart
91
92
>| ### Gantt chart
93
>| 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
94
95
>| ### Milestone
96
>| A significant point or event in a project timeline that marks the completion of a key deliverable or the start of a new phase
97
98
---
99
100
## See also
101
102
- [C01 home page](/sd/C01/C01-home) — everything else for this criterion