Blame
|
1 | # C05 — Skills in Producing Detailed Designs |
||||||
| 2 | ||||||||
|
3 | The Hamilton and Alexandra College · Year 12 · 2026 |
||||||
|
4 | |||||||
| 5 | Criterion 5 covers three linked indicators: producing detailed designs using the full set of design tools (mock-ups, data dictionary, IPO charts, pseudocode, object descriptions); documenting how design principles and UX characteristics are applied; and showing evidence of critical and creative thinking through research, traceability between design layers, and contingency planning. |
|||||||
| 6 | ||||||||
| 7 | --- |
|||||||
| 8 | ||||||||
|
9 | ## C5-1 — Design tools |
||||||
|
10 | |||||||
|
11 | Turning the chosen idea into designs another person could build from. Each page below targets a specific point where marks are commonly lost. |
||||||
|
12 | |||||||
|
13 | - [C04 → C05 — Choose, then Detail](/sd/C05/C04%20to%20C05%20-%20Choose%20then%20Detail) — how C05 (detail the chosen idea) differs from C04 (choose *which* idea); why C05 means "buildable", not "prettier" |
||||||
|
14 | - [From SRS to Detailed Designs — Mock-ups](/sd/C05/From%20SRS%20to%20Detailed%20Designs%20-%20Mock-ups) — one real project (the SAT grader) traced from SRS requirement → C04 wireframe → C05 detailed design → build → correction; one trace fully worked, two faded for you to finish |
||||||
|
15 | - [Sketch vs Mock-up](/sd/C05/Sketch%20vs%20Mock-up) — why a rough sketch is not a mock-up, and what "annotated" actually means (the 3–4 / 5–6 boundary) |
||||||
|
16 | - [Data Dictionary](/sd/C05/Data%20Dictionary) — when to use it, the headings to include, a worked example, and why "format" is not "type" |
||||||
|
17 | - [IPO Charts — Process Means Steps](/sd/C05/IPO%20Charts%20-%20Process%20Means%20Steps) — why the Process column must be numbered algorithm steps, not a label for the output |
||||||
| 18 | - [VCAA Pseudocode — Not Python](/sd/C05/VCAA%20Pseudocode%20Not%20Python) — write language-independent Structured English (`←`, `<>`, `ENDIF`), not Python-flavoured pseudocode |
|||||||
|
19 | - [Object Descriptions and Class Diagrams](/sd/C05/Object%20Descriptions%20and%20Class%20Diagrams) — the fifth design tool for OOP projects: a class's properties, methods and events, and how to read a class diagram (Level 7–9) |
||||||
|
20 | |||||||
| 21 | ## C5-2 — Design principles & UX |
|||||||
| 22 | ||||||||
|
23 | - [Design Principles vs UX Characteristics](/sd/C05/Design%20Principles%20vs%20UX%20Characteristics) — why these are two separate lists, why usability appearing in both is a trap, and what the slot-five validation is actually checking |
||||||
|
24 | - [Design Principles](/sd/C05/Design%20Principles) — the seven VCAA design principles, with a demonstration video and a map-it-to-VCAA activity |
||||||
| 25 | - [UX Characteristics](/sd/C05/UX%20Characteristics) — the four UX characteristics (affordance, interoperability, security, usability), each with videos and worked examples |
|||||||
|
26 | - [The Annotation Verb Ladder](/sd/C05/The%20Annotation%20Verb%20Ladder) — climbing Identify → Describe → Document → Explain so your design-log notes don't stall at "identify" in the no-AI Annotation validation |
||||||
| 27 | ||||||||
|
28 | ## C5-3 — Critical & creative thinking |
||||||
| 29 | ||||||||
| 30 | The three steps that make your design thinking visible, plus extra creative-thinking moves for the Godot cohort: |
|||||||
| 31 | ||||||||
| 32 | - [Shoulders of Giants](/sd/C05/Shoulders%20of%20Giants) — Step 1: research existing and possible solutions to inform your design |
|||||||
| 33 | - [Connect the Dots](/sd/C05/Connect%20the%20Dots) — Step 2: trace one feature from mood board → mock-up → data dictionary → IPO → pseudocode, linked to your SRS |
|||||||
| 34 | - [Plan B Ready](/sd/C05/Plan%20B%20Ready) — Step 3: document design risks and specific contingencies |
|||||||
| 35 | - [Creative Thinking for Your Godot Project](/sd/C05/Creative%20Thinking%20for%20Your%20Godot%20Project) — extra moves to show creative thinking, tailored to a Godot game |
|||||||
| 36 | ||||||||
|
37 | ## Templates and scaffolds |
||||||
| 38 | ||||||||
| 39 | Reusable starting points for C05 deliverables: |
|||||||
| 40 | ||||||||
| 41 | - [Annotated Mock-up in Excalidraw](/sd/C05/Annotated%20Mock-up%20in%20Excalidraw) — blank screen frame, annotation zone, and callout arrows ready to fill in; saves 10+ minutes of setup and produces consistent annotations (DRAFT) |
|||||||
| 42 | - [Plan B Contingency Table](/sd/C05/Plan%20B%20Contingency%20Table) — pre-filled risk-prompt table for C05-3 contingency planning; prompts force specificity without hinting at solutions (DRAFT) |
|||||||
| 43 | ||||||||
|
44 | ## Resources |
||||||
| 45 | ||||||||
| 46 | - [C05 Resources](/sd/Resources/C05-Resources) — per-topic reading and external resources for design tools, design principles, UX characteristics, and critical and creative thinking |
|||||||
| 47 | ||||||||
| 48 | --- |
|||||||
| 49 | ||||||||
| 50 | ← Back to [VCE Software Development Hub](/sd/VCE%20Software%20Development%20Hub) |
|||||||