Home A - Z
Page Index

An Otter Wiki

Blame

764b19 lisa 2026-04-26 08:07:23
Source material C02-C05: 6 new DRAFT pages, verified external rows YouTube-first priority sourcing per CXX-WIKI-VIDEO-guide §7. All external resources verified rigorously (oEmbed for YouTube, browser DOM check via playwright-cli for Isaac CS); no curl-200-only links. New DRAFT wiki pages (6): - C02: Excalidraw Diagram Starters - C03: Analytical Tools Template Guide - C04: Efficiency vs Effectiveness; Evaluation Criteria and the SRS - C05: Annotated Mock-up in Excalidraw; Plan B Contingency Table Verified external rows added across CXX-Resources.md (MPT YouTube, NNgroup, VCAA Teaching and Learning, Isaac CS prog_cwk_evaluation_ocr, Ryan's Tutorials). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 
> **DRAFT** — under teacher review.
2
3
# Excalidraw Diagram Starters — C02
4
5
Hamilton College · Year 12 · 2026
6
7
Drawing from scratch each session costs 10–15 minutes of setup time and often produces inconsistent notation across the three diagrams. These Excalidraw starters give you pre-framed skeletons — correct shapes, correct labels — so you can focus on the content, not the canvas.
8
9
---
10
11
## Why consistent notation matters
12
13
All three C02 diagrams use the same cast of external entities. If the entity is named "Student" on your context diagram, it must be named "Student" (not "User" or "Person") on your DFD. Starting from a shared canvas makes this consistency automatic.
14
15
At **9–10**, the rubric requires *"no errors, inconsistencies or omissions"* across all three diagrams. Inconsistent entity names between diagrams is a named inconsistency — even if both diagrams are otherwise correct.
16
17
---
18
19
## Getting started in Excalidraw
20
21
Excalidraw is available free at [excalidraw.com](https://excalidraw.com). No account required. Your teacher may share a `.excalidraw` file directly — open it with File → Open.
22
23
---
24
25
## Skeleton: Context Diagram
26
27
The context diagram has **exactly one system circle**. Everything else is an external entity (rectangle) or a data flow (labelled arrow).
28
29
```
30
[Entity A] ──── label ────▶ ( Your System Name ) ──── label ────▶ [Entity B]
31
▲
32
label
33
│
34
[Entity C]
35
```
36
37
**Shape key:**
38
39
| Shape | What it represents |
40
|---|---|
41
| Rectangle | External entity (a person, organisation, or external system) |
42
| Circle / oval | The entire system — one only |
43
| Labelled arrow | Data flow — must carry a specific name (not "data" or "info") |
44
45
**Common setup errors to avoid before you start drawing:**
46
47
- Do not add any second circle — multiple circles make it a DFD, not a context diagram.
48
- Do not add data stores (double lines) — they do not exist at context level.
49
- Label every arrow with the specific data being exchanged, not a direction (wrong: "sends data"; right: "assignment submission form").
50
51
---
52
53
## Skeleton: Level-1 Data Flow Diagram
54
55
The Level-1 DFD **decomposes** the single system circle into 3–6 numbered processes. Use the same external entities as your context diagram.
56
57
```
58
[Entity A] ──── label ────▶ (1. Process Name) ────▶ ║ Data Store ║
59
│
60
label
61
▼
62
(2. Process Name) ──── label ────▶ [Entity B]
63
│
64
label
65
▼
66
(3. Process Name) ──── label ────▶ ║ Data Store ║
67
```
68
69
**Shape key:**
70
71
| Shape | What it represents |
72
|---|---|
73
| Rectangle | External entity — same names as context diagram |
74
| Circle / oval | A numbered process (verb–noun phrase, e.g. "1. Verify Login") |
75
| Double-line rectangle | Data store (named collection of stored data) |
76
| Labelled arrow | Data flow |
77
78
**Minimum check before you submit:**
79
80
- Each process has at least one input AND one output arrow.
81
- At least one data store is present.
82
- Every entity name matches your context diagram exactly.
83
- No entity ↔ entity arrows (all flows route through a process).
84
- No entity ↔ data store arrows (data stores only connect to processes).
85
86
---
87
88
## Skeleton: Use Case Diagram
89
90
The use case diagram shows **who** can do **what** with your system. Actors (stick figures) sit outside the system boundary; use cases (ovals) sit inside.
91
92
```
93
┌──────────────────────────────────────────┐
94
Actor A │ (Use Case 1) (Use Case 3) │
95
🧍─────┼──────────────────────────────────────────│
96
│ (Use Case 2) ──«include»──▶ (Use Case 4)│
97
🧍─────┼──────────────────────────────────────────│
98
Actor B │ │
99
└──────────────────────────────────────────┘
100
```
101
102
**Shape key:**
103
104
| Shape | What it represents |
105
|---|---|
106
| Stick figure (outside box) | Actor (a person or external system that uses the system) |
107
| Oval (inside box) | Use case (a function the system performs) |
108
| Rectangle | System boundary |
109
| Solid line | Association (actor participates in use case) |
110
| Dashed arrow «include» | Use case A *always* triggers use case B |
111
| Dashed arrow «extend» | Use case B *sometimes* triggers optional use case C |
112
113
**Arrow direction rules (the most common exam mistake):**
114
115
- **«include»:** arrow points FROM the base use case TO the included use case. ("Login" includes "Verify Credentials" — arrow: Login → Verify Credentials.)
116
- **«extend»:** arrow points FROM the extending use case TO the base use case. ("Display Error Message" extends "Login" — arrow: Display Error Message → Login.)
117
118
If in doubt: the arrow always points *towards* the use case that is being **used** or **extended into**.
119
120
---
121
122
## Practice check — before the hand-drawn validation
123
124
Run through this list with your Excalidraw diagrams before the timed hand-drawing session:
125
126
- [ ] Context diagram: exactly one system circle, no data stores, every arrow labelled.
127
- [ ] DFD: 3–6 numbered processes, at least one data store, entity names match context diagram.
128
- [ ] Use case diagram: all actors outside the boundary, all use cases inside, «include»/«extend» arrows pointing the correct direction.
129
- [ ] All three diagrams use identical names for the same entities and data stores.
130
131
If you can redraw all three from memory using only these skeletons as a prompt, you are ready for the hand-drawn validation.
132
133
---
134
135
## See also
136
137
- [Context Diagram vs Data Flow Diagram](/sd/C02/Context%20Diagram%20vs%20Data%20Flow%20Diagram) — what can appear on each diagram; the most common notation errors
138
- [What Is an Entity?](/sd/C02/What%20Is%20an%20Entity) — human and non-human entities; how to find all entities from your user stories
139
- C02 Resources: [external reading and videos](/sd/Resources/C02-Resources)
140
141
---
142
143
← Back to [VCE Software Development Hub](/sd/VCE%20Software%20Development%20Hub)