Blame
|
1 | > **DRAFT** — under teacher review. |
||||||
| 2 | ||||||||
| 3 | # Essential Terms — C02 |
|||||||
| 4 | ||||||||
| 5 | Hamilton College · Year 12 · 2026 |
|||||||
| 6 | ||||||||
| 7 | A glossary of every term you need to recognise and use correctly across C02. Click a term to expand its definition. Use this as a vocabulary self-check before your C2-1 (Poster Peer-Assessment) and C2-2 (Hand-Drawn Diagrams) validations — if you can't define a term in your own words, you can't defend it under questioning. |
|||||||
| 8 | ||||||||
| 9 | --- |
|||||||
| 10 | ||||||||
| 11 | ## Topics covered |
|||||||
| 12 | ||||||||
| 13 | - Data collection methods (interviews, surveys, observations, reports) |
|||||||
| 14 | - User stories |
|||||||
| 15 | - Context diagrams |
|||||||
| 16 | - Data flow diagrams |
|||||||
| 17 | - Use case diagrams |
|||||||
| 18 | ||||||||
| 19 | --- |
|||||||
| 20 | ||||||||
| 21 | ## Glossary |
|||||||
| 22 | ||||||||
|
23 | >| ### Actor |
||||||
| 24 | >| An entity that can interact with the software solution as shown in a use case diagram |
|||||||
|
25 | |||||||
|
26 | >| ### Association |
||||||
| 27 | >| A relationship between two elements in a use case diagram |
|||||||
|
28 | |||||||
|
29 | >| ### Close-ended questions |
||||||
| 30 | >| Questions that can be answered with a finite set of responses |
|||||||
|
31 | |||||||
|
32 | >| ### Context diagram |
||||||
| 33 | >| A visualisation of a system in its entirety that indicates the data that is passed into and out of the system |
|||||||
|
34 | |||||||
|
35 | >| ### Data |
||||||
| 36 | >| Raw, unprocessed facts and figures |
|||||||
|
37 | |||||||
|
38 | >| ### Data flow |
||||||
| 39 | >| The movement of a piece or collection of data within an information system, as shown in context diagrams and data flow diagrams (DFDs) |
|||||||
|
40 | |||||||
|
41 | >| ### Data flow diagram (DFD) |
||||||
| 42 | >| A graphical visualisation of the flow of information within a system, including data provided by external entities |
|||||||
|
43 | |||||||
|
44 | >| ### Data store |
||||||
| 45 | >| A representation of a collection of data that is stored in some way within a system |
|||||||
|
46 | |||||||
|
47 | >| ### Entity |
||||||
| 48 | >| The users or external systems that interact with the system being created |
|||||||
|
49 | |||||||
|
50 | >| ### Extend |
||||||
| 51 | >| A relationship between use cases where one use case has optional or additional functionality, which is represented in a use case diagram as a second use case |
|||||||
|
52 | |||||||
|
53 | >| ### Generalisation |
||||||
| 54 | >| A parent-child relationship between two elements in a use case diagram |
|||||||
|
55 | |||||||
|
56 | >| ### Include |
||||||
| 57 | >| A relationship between use cases where one use case is tied to, or relies upon, the functionality contained within another use case |
|||||||
|
58 | |||||||
|
59 | >| ### Interview |
||||||
| 60 | >| A face-to-face meeting between people for consultative purposes |
|||||||
|
61 | |||||||
|
62 | >| ### Observation |
||||||
| 63 | >| A method of data collection that involves physically observing how a system operates and how it is used |
|||||||
|
64 | |||||||
|
65 | >| ### Open-ended questions |
||||||
| 66 | >| Questions where the number of potential answers is infinite |
|||||||
|
67 | |||||||
|
68 | >| ### Process (context diagram) |
||||||
| 69 | >| An abstract representation of the whole system being created |
|||||||
|
70 | |||||||
|
71 | >| ### Process (data flow diagram) |
||||||
| 72 | >| An abstract representation of a function within a system |
|||||||
|
73 | |||||||
|
74 | >| ### Qualitative data |
||||||
| 75 | >| Data that consists of descriptive details, usually gathered via surveys or interviews |
|||||||
|
76 | |||||||
|
77 | >| ### Quantitative data |
||||||
| 78 | >| Data that can be easily processed in a statistical manner, usually composed of definite numbers |
|||||||
|
79 | |||||||
|
80 | >| ### Relationship |
||||||
| 81 | >| The connections between elements within a use case diagram |
|||||||
|
82 | |||||||
|
83 | >| ### Report |
||||||
| 84 | >| A written document providing a summary or finding in relation to the context or system being analysed |
|||||||
|
85 | |||||||
|
86 | >| ### Survey |
||||||
| 87 | >| A set of questions that ask for a response to be selected from a list of alternatives |
|||||||
|
88 | |||||||
|
89 | >| ### System boundary |
||||||
| 90 | >| A rectangle around relevant use cases that indicates the use cases that are within the scope of the solution |
|||||||
|
91 | |||||||
|
92 | >| ### Unified Modeling Language (UML) |
||||||
| 93 | >| A general-purpose visual modelling language |
|||||||
|
94 | |||||||
|
95 | >| ### Use case |
||||||
| 96 | >| A representation of the transactions or functions a user (actor) can complete in a system, as shown in a use case diagram |
|||||||
|
97 | |||||||
|
98 | >| ### Use case diagram (UCD) |
||||||
| 99 | >| A method of describing how a user interacts with a system, using Unified Modeling Language (UML) |
|||||||
|
100 | |||||||
| 101 | --- |
|||||||
| 102 | ||||||||
| 103 | ## See also |
|||||||
| 104 | ||||||||
| 105 | - [Context Diagram](Context%20Diagram.md) — the highest-level view of your system |
|||||||
| 106 | - [Context Diagram vs Data Flow Diagram](Context%20Diagram%20vs%20Data%20Flow%20Diagram.md) — what changes between Level 0 and Level 1 |
|||||||
| 107 | - [What Is an Entity](What%20Is%20an%20Entity.md) — entities aren't only people |
|||||||
| 108 | - [Excalidraw Diagram Starters](Excalidraw%20Diagram%20Starters.md) — pre-framed canvases for rehearsing all three diagrams |
|||||||
