Blame

0648ae lisa 2026-06-08 09:18:19
Add C05 student wiki pages: design tools, annotation, traceability Six DRAFT pages under /sd/C05 targeting common rubric-boundary errors: - Sketch vs Mock-up (C5-1) — embeds two videos - Data Dictionary — Format is not Type (C5-1) - IPO Charts — Process Means Steps (C5-1) - VCAA Pseudocode — Not Python (C5-1) - The Annotation Verb Ladder (C5-2) - Connect the Dots — design traceability (C5-3) Pages 2-6 have video slots pending teacher selection. Home index reorganised by indicator. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1
> **DRAFT** — under teacher review.
2
3
# Sketch vs Mock-up — They Are Not the Same Thing
4
5
The Hamilton and Alexandra College · Year 12 · 2026
6
7
A lot of marks are lost at the 3–4 / 5–6 rubric boundary — and almost always for the same reason: submitting a sketch and calling it a mock-up. This page shows exactly what each artefact is, what separates them, and what "annotated" actually means in VCE terms.
8
9
---
10
11
## What each one is
12
13
| | Sketch | Mock-up |
14
|---|---|---|
15
| **Fidelity** | Low — rough, no colour, placeholder labels | High — real colours, real fonts, real content |
16
| **Content** | Shows layout and structure only | Shows the actual interface as it will look |
17
| **Annotation** | Optional notes on layout ideas | Compulsory — every key control labelled with *what it does* AND *why it is placed there* |
18
| **Tool** | Pencil and paper, Excalidraw (lo-fi mode) | Excalidraw with UX library, Figma, Canva |
19
| **VCE purpose** | Brainstorm multiple ideas (C04 design pack) | Evidence for C05 — this is what gets assessed |
20
21
> [!NOTE]
22
> The VCAA study design defines a mock-up as **"an annotated visual representation of the user interface"**. Annotation is part of the definition — not an optional extra. A polished screen design with no annotation labels is still not a valid mock-up.
23
24
---
25
26
## The progression: sketch → mock-up
27
28
Here is one idea progressed through the three stages. Notice how much *more* each step adds.
29
30
```mermaid
31
flowchart LR
32
A["🖊️ Sketch<br/>──────────<br/>Boxes + arrows<br/>No colour<br/>No real text<br/>Shows: where things go"]
33
B["🎨 Mock-up<br/>──────────<br/>Real colours + fonts<br/>Real button labels<br/>Real nav flow<br/>Shows: what it looks like"]
34
C["🏷️ Annotated Mock-up<br/>──────────<br/>Everything in mock-up<br/>PLUS: callout on every<br/>key control → what it<br/>does + why placed there<br/>Shows: design decisions"]
35
A -->|"add fidelity"| B
36
B -->|"add annotation"| C
37
style C fill:#d4edda,stroke:#28a745
38
```
39
40
The highlighted box is what C05 requires. You need both the high-fidelity visual **and** the annotations — neither alone is enough.
41
42
---
43
44
## 🎬 Watch
45
46
### Video 1 — Wireframe vs Mockup vs Prototype
47
48
**🎯 Watch for:** The video uses three tiers — wireframe, mockup, prototype. Map them onto our two VCE artefacts: their **wireframe ≈ our sketch** (lo-fi, layout only); their **mockup ≈ our annotated mock-up** (hi-fi, visual detail). Their **prototype** (clickable, working interactions) is **beyond what C05 asks for** — do not build a prototype for this task.
49
50
{{Video|src=https://www.youtube.com/watch?v=lJipkxgMSF0}}
51
52
**✍️ While you watch:** As the video describes each tier, write one sentence in your own words matching it to either "our sketch" or "our annotated mock-up" — or "beyond C05" for the prototype tier. This mapping question comes up in the annotation validation.
53
54
---
55
56
### Video 2 — Excalidraw in practice
57
58
**🎯 Watch for:** How Excalidraw's built-in wireframing libraries (Lo-Fi Wireframing Kit, Basic UX elements) let you drop in pre-built components — buttons, input fields, nav bars — so you spend time on design decisions, not drawing rectangles.
59
60
{{Video|src=https://www.youtube.com/watch?v=CjKpg_N42Cw}}
61
62
**✍️ While you watch:** Identify at least two components in the video that appear in your own interface (e.g. a text input, a navigation bar). Note the library name they come from — you may need to cite your tool in your design log.
63
64
---
65
66
## For Level 9: completeness matters
67
68
At Level 9 the mock-ups must represent the **complete interface** — not just the main screen.
69
70
That means:
71
72
- Every screen the user can reach is mocked up (login, dashboard, data entry, confirmation, error states).
73
- Navigation between screens is shown — either as a flow diagram or as directional arrows on the mock-up set.
74
- Each screen has its own annotations.
75
76
A single polished home-screen mock-up is a Level 5–6 submission, regardless of how good it looks.
77
78
---
79
80
## Common mistakes
81
82
### Mistake 1: Submitting a sketch and labelling it a mock-up
83
84
> ~~A pencil layout with grey boxes showing "button here" and "logo here"~~
85
86
A sketch shows structure. A mock-up shows what the interface actually looks like. If it has no colour, no real fonts, and no real content, it is a sketch.
87
88
### Mistake 2: A polished screen with no annotations
89
90
> ~~A beautiful Figma screen with no callout labels~~
91
92
Without annotations, it is a screen design, not a VCE mock-up. Annotations must explain what each key control does and why it is placed where it is.
93
94
### Mistake 3: Only the main screen
95
96
> ~~One annotated home screen, nothing else~~
97
98
C05 requires the complete interface. If your solution has four screens, you need four annotated mock-ups — plus navigation between them shown somewhere.
99
100
### Mistake 4: Annotations that only describe
101
102
> ~~"This is a blue Submit button."~~
103
104
A description states what is there. An annotation explains the design decision — what the control does for the user and why it is positioned and styled that way.
105
106
---
107
108
## Check Your Understanding
109
110
1. What two things make a high-fidelity screen design a valid VCE mock-up?
111
112
>| A valid VCE mock-up must (1) be **high-fidelity** — real colours, fonts, and content — and (2) be **annotated** — every key control labelled with what it does and why it is placed there. Both are required; either alone is insufficient.
113
114
2. A student submits a single beautifully annotated home screen. They are targeting Level 9. What is missing?
115
116
>| Level 9 requires the **complete interface** — all screens the user can reach, plus navigation between them shown. A single screen, however detailed, caps the submission at around Level 5–6.
117
118
3. What is the difference between an annotation that describes and one that justifies?
119
120
>| A describing annotation says what is there: "There is a blue Submit button." A justifying annotation says what it does for the user and why the design decision was made: "The Submit button uses a high-contrast blue to draw attention as the primary action, placed bottom-right to match the natural reading flow and reduce error submissions."
121
122
---
123
124
## See also
125
126
- [Annotated Mock-up in Excalidraw](/sd/C05/Annotated%20Mock-up%20in%20Excalidraw)
127
- [C04 → C05 — Choose, then Detail](/sd/C05/C04%20to%20C05%20-%20Choose%20then%20Detail)
31bafd lisa 2026-06-08 11:43:19
C05: rebuild Data Dictionary page; fix class-diagram notation table - Rename 'Data Dictionary - Format is not Type' → 'Data Dictionary' (now a full page): when-to-use (data sources), 7 headings, worked student example, three videos (Kalodikis), Wikipedia data/metadata image (CC0), student-example activity, ScotRail extension; keeps the format-vs-type section. Updated 4 inbound links. - Class-diagram page: fix broken 'notation' table — the `<|--` cell contained a pipe that corrupted the markdown table; moved inheritance into prose. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
128
- [Data Dictionary](/sd/C05/Data%20Dictionary)
0648ae lisa 2026-06-08 09:18:19
Add C05 student wiki pages: design tools, annotation, traceability Six DRAFT pages under /sd/C05 targeting common rubric-boundary errors: - Sketch vs Mock-up (C5-1) — embeds two videos - Data Dictionary — Format is not Type (C5-1) - IPO Charts — Process Means Steps (C5-1) - VCAA Pseudocode — Not Python (C5-1) - The Annotation Verb Ladder (C5-2) - Connect the Dots — design traceability (C5-3) Pages 2-6 have video slots pending teacher selection. Home index reorganised by indicator. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
129
- [Design Principles vs UX Characteristics](/sd/C05/Design%20Principles%20vs%20UX%20Characteristics)
130
131
---
132
133
← Back to [C05 Home](/sd/C05/C05-home) · [VCE Software Development Hub](/sd/VCE%20Software%20Development%20Hub)