Blame
|
1 | <!-- Generated from applied-computing-au vic/unit3-4/sat/C09-2026/C09-essential-terms.md by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. --> |
||||||
| 2 | # Essential Terms — C09 |
|||||||
|
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 C09. 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["C09 vocabulary<br/>16 terms"] |
|||||||
| 11 | R --> G0["Beta testing<br/>4 terms"] |
|||||||
| 12 | R --> G1["Data collection from beta testers<br/>4 terms"] |
|||||||
| 13 | R --> G2["Reporting results<br/>4 terms"] |
|||||||
| 14 | R --> G3["Modifications based on feedback<br/>4 terms"] |
|||||||
| 15 | ``` |
|||||||
|
16 | |||||||
|
17 | *Where the C09 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 | ## Beta testing |
||||||
|
22 | |||||||
|
23 | >| ### Beta testing |
||||||
| 24 | >| The phase of software testing where a sample of the intended audience tests the software in a real environment. |
|||||||
|
25 | |||||||
|
26 | >| ### Test scenario |
||||||
| 27 | >| A specific situation or workflow that a beta tester is asked to perform in order to evaluate the functionality, usability or reliability of the software. |
|||||||
|
28 | |||||||
|
29 | >| ### Test plan |
||||||
| 30 | >| A document that outlines the objectives, scope, schedule and approach for beta testing, including which features to test and what data to collect. |
|||||||
|
31 | |||||||
|
32 | >| ### Personas |
||||||
| 33 | >| Fictional characters created based on user research to represent the different user types that might use a service, application, product, site or brand. |
|||||||
|
34 | |||||||
|
35 | --- |
||||||
|
36 | |||||||
|
37 | ## Data collection from beta testers |
||||||
|
38 | |||||||
|
39 | >| ### Data collection |
||||||
| 40 | >| The systematic gathering of feedback, observations and measurements from beta testers during and after testing sessions. |
|||||||
|
41 | |||||||
|
42 | >| ### Observation (beta testing) |
||||||
| 43 | >| Watching beta testers interact with the software to identify usability issues, confusion points or unexpected behaviours. |
|||||||
|
44 | |||||||
|
45 | >| ### Survey |
||||||
| 46 | >| A structured set of questions given to beta testers to collect quantitative and qualitative feedback about their experience with the software. |
|||||||
|
47 | |||||||
|
48 | >| ### Feedback |
||||||
| 49 | >| Information provided by beta testers about their experience, including issues encountered, suggestions for improvement and overall satisfaction. |
|||||||
|
50 | |||||||
|
51 | --- |
||||||
| 52 | ||||||||
| 53 | ## Reporting results |
|||||||
| 54 | ||||||||
| 55 | >| ### Bug report |
|||||||
| 56 | >| A documented record of an error or defect found during beta testing, typically including steps to reproduce, expected behaviour and actual behaviour. |
|||||||
| 57 | ||||||||
| 58 | >| ### Reporting results |
|||||||
| 59 | >| The process of compiling and presenting beta testing findings, including issues discovered, tester feedback and recommendations for improvement. |
|||||||
| 60 | ||||||||
| 61 | >| ### Testing table |
|||||||
| 62 | >| A commonly used way to record evidence of functionality testing, documenting test cases, expected results and actual results. |
|||||||
| 63 | ||||||||
| 64 | >| ### Priority (bug classification) |
|||||||
| 65 | >| A ranking assigned to an issue found during beta testing that indicates how urgently it needs to be addressed before release. |
|||||||
| 66 | ||||||||
| 67 | --- |
|||||||
| 68 | ||||||||
| 69 | ## Modifications based on feedback |
|||||||
| 70 | ||||||||
| 71 | >| ### Modifications |
|||||||
| 72 | >| Changes made to the software based on feedback and issues identified during beta testing, aimed at improving functionality, usability or performance. |
|||||||
| 73 | ||||||||
| 74 | >| ### Functionality |
|||||||
| 75 | >| The range of operations that can be performed by a software system as defined by its requirements. |
|||||||
| 76 | ||||||||
| 77 | >| ### Usability |
|||||||
| 78 | >| The ease with which a user can interact with a software system to achieve their goals efficiently and satisfactorily. |
|||||||
| 79 | ||||||||
| 80 | >| ### Evaluation criteria |
|||||||
| 81 | >| Performance criteria made from the expectations and specification, used to judge whether the software meets its intended purpose. |
|||||||
| 82 | ||||||||
| 83 | --- |
|||||||
| 84 | ||||||||
| 85 | ## See also |
|||||||
| 86 | ||||||||
| 87 | - [C09 home page](/sd/C09/C09-home) — everything else for this criterion |
|||||||
