<!-- 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. --> # Essential Terms — C01 The Hamilton and Alexandra College · Year 12 · 2026 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. ```mermaid flowchart TD R["C01 vocabulary<br/>21 terms"] R --> G0["Problem-solving methodology<br/>5 terms"] R --> G1["Design brief<br/>3 terms"] R --> G2["Project management<br/>11 terms"] R --> G3["Gantt chart<br/>2 terms"] ``` *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.* --- ## Problem-solving methodology >| ### Analysis stage >| The stage of the problem-solving methodology where solution requirements, constraints and scope are determined >| ### Design stage >| The stage of the problem-solving methodology where the function and appearance of a solution are planned, and evaluation criteria created >| ### Development stage >| The stage of the problem-solving methodology where the solution is coded, validated, tested and documented >| ### Evaluation stage >| The stage of the problem-solving methodology where the completed solution is evaluated against the evaluation criteria and the project plan is assessed >| ### Problem-solving methodology (PSM) >| An approach that develops the stages involved in solving a problem --- ## Design brief >| ### Design brief >| 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 >| ### Feasibility >| 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) >| ### T.E.L.O.S. >| 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?) --- ## Project management >| ### Concepts (project management) >| The milestones and dependencies within a project timeline >| ### Concurrently >| When a task is carried out at the same time as another task >| ### Critical path >| The shortest possible time in which a project can be completed >| ### Dependency >| A relationship between two tasks in a project plan where one task cannot begin until another has been completed >| ### Predecessor >| A task that must be completed before another one can be performed >| ### Processes (project management) >| Task identification, sequencing and allocation of time and resources within a project timeline >| ### Project management >| A method of recording the progress of a project and managing resources to operate within time, resource and cost availability >| ### Slack time >| The length of time that a task can run overtime before affecting other tasks >| ### Successor >| A task that must be completed after another task >| ### Work breakdown structure (WBS) >| 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 >| ### Monitoring >| The ongoing process of tracking a project's progress against the plan, identifying delays or changes, and documenting adjustments made --- ## Gantt chart >| ### Gantt chart >| 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 >| ### Milestone >| A significant point or event in a project timeline that marks the completion of a key deliverable or the start of a new phase --- ## See also - [C01 home page](/sd/C01/C01-home) — everything else for this criterion