Commit 20e3bf
2026-04-27 20:00:52 lisa: Add C02 Essential Terms glossary Verbatim from C02-essential-terms.md (25 terms covering data collection, context/data-flow/use-case diagrams, qual/quant). House-style header + topics index + see-also footer added.| /dev/null .. sd/C02/Essential Terms.md | |
| @@ 0,0 1,108 @@ | |
| + | > **DRAFT** — under teacher review. |
| + | |
| + | # Essential Terms — C02 |
| + | |
| + | Hamilton College · Year 12 · 2026 |
| + | |
| + | 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. |
| + | |
| + | --- |
| + | |
| + | ## Topics covered |
| + | |
| + | - Data collection methods (interviews, surveys, observations, reports) |
| + | - User stories |
| + | - Context diagrams |
| + | - Data flow diagrams |
| + | - Use case diagrams |
| + | |
| + | --- |
| + | |
| + | ## Glossary |
| + | |
| + | > [!note]- Actor |
| + | > An entity that can interact with the software solution as shown in a use case diagram |
| + | |
| + | > [!note]- Association |
| + | > A relationship between two elements in a use case diagram |
| + | |
| + | > [!note]- Close-ended questions |
| + | > Questions that can be answered with a finite set of responses |
| + | |
| + | > [!note]- Context diagram |
| + | > A visualisation of a system in its entirety that indicates the data that is passed into and out of the system |
| + | |
| + | > [!note]- Data |
| + | > Raw, unprocessed facts and figures |
| + | |
| + | > [!note]- Data flow |
| + | > The movement of a piece or collection of data within an information system, as shown in context diagrams and data flow diagrams (DFDs) |
| + | |
| + | > [!note]- Data flow diagram (DFD) |
| + | > A graphical visualisation of the flow of information within a system, including data provided by external entities |
| + | |
| + | > [!note]- Data store |
| + | > A representation of a collection of data that is stored in some way within a system |
| + | |
| + | > [!note]- Entity |
| + | > The users or external systems that interact with the system being created |
| + | |
| + | > [!note]- Extend |
| + | > 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 |
| + | |
| + | > [!note]- Generalisation |
| + | > A parent-child relationship between two elements in a use case diagram |
| + | |
| + | > [!note]- Include |
| + | > A relationship between use cases where one use case is tied to, or relies upon, the functionality contained within another use case |
| + | |
| + | > [!note]- Interview |
| + | > A face-to-face meeting between people for consultative purposes |
| + | |
| + | > [!note]- Observation |
| + | > A method of data collection that involves physically observing how a system operates and how it is used |
| + | |
| + | > [!note]- Open-ended questions |
| + | > Questions where the number of potential answers is infinite |
| + | |
| + | > [!note]- Process (context diagram) |
| + | > An abstract representation of the whole system being created |
| + | |
| + | > [!note]- Process (data flow diagram) |
| + | > An abstract representation of a function within a system |
| + | |
| + | > [!note]- Qualitative data |
| + | > Data that consists of descriptive details, usually gathered via surveys or interviews |
| + | |
| + | > [!note]- Quantitative data |
| + | > Data that can be easily processed in a statistical manner, usually composed of definite numbers |
| + | |
| + | > [!note]- Relationship |
| + | > The connections between elements within a use case diagram |
| + | |
| + | > [!note]- Report |
| + | > A written document providing a summary or finding in relation to the context or system being analysed |
| + | |
| + | > [!note]- Survey |
| + | > A set of questions that ask for a response to be selected from a list of alternatives |
| + | |
| + | > [!note]- System boundary |
| + | > A rectangle around relevant use cases that indicates the use cases that are within the scope of the solution |
| + | |
| + | > [!note]- Unified Modeling Language (UML) |
| + | > A general-purpose visual modelling language |
| + | |
| + | > [!note]- Use case |
| + | > A representation of the transactions or functions a user (actor) can complete in a system, as shown in a use case diagram |
| + | |
| + | > [!note]- Use case diagram (UCD) |
| + | > A method of describing how a user interacts with a system, using Unified Modeling Language (UML) |
| + | |
| + | --- |
| + | |
| + | ## See also |
| + | |
| + | - [Context Diagram](Context%20Diagram.md) — the highest-level view of your system |
| + | - [Context Diagram vs Data Flow Diagram](Context%20Diagram%20vs%20Data%20Flow%20Diagram.md) — what changes between Level 0 and Level 1 |
| + | - [What Is an Entity](What%20Is%20an%20Entity.md) — entities aren't only people |
| + | - [Excalidraw Diagram Starters](Excalidraw%20Diagram%20Starters.md) — pre-framed canvases for rehearsing all three diagrams |