C05 Resources — Detailed Designs, Design Principles & Critical/Creative Thinking
Criterion scope: Design tools (mock-ups, data dictionary, IPO charts, pseudocode, object descriptions), design principles (alignment, balance, contrast, space, text formatting, usability, navigation), UX characteristics (affordance, interoperability, security, usability), critical and creative thinking (existing solutions research, connecting ideas to requirements, contingencies).
C5-1: Design Tools
Existing Materials (CriterionXX/)
Criterion05/ has step-by-step guides for mock-ups, data dictionary, IPO charts, pseudocode, class diagrams, and object descriptions. Well-structured.
External Resources
| Resource | Source | Format | VCAA Mapping | Why It's Useful |
|---|---|---|---|---|
| Ryan's Tutorials — Input Process Output Tables | Ryan's Tutorials | Reading + examples | IPO charts: input, process, output | Free, clear explanation of IPO charts aimed at secondary students. Good supplement to existing materials. Explains why IPO charts are useful, not just how to create them. |
| Codecademy — Pseudocode and Flowchart: Complete Beginner's Guide | Codecademy | Reading | Pseudocode — structured English, algorithm representation | Beginner-friendly guide to pseudocode with examples. Helps students understand the conventions. |
| Lucidchart — UML Class Diagram Tutorial | Lucidchart | Reading + interactive | Object descriptions, class diagrams — OOP design | Tutorial on creating UML class diagrams. Directly supports the object descriptions and class diagram requirements. Students can use Lucidchart's free tier to create their diagrams. |
| StudyLib — Database Design Tools: IPO Charts, Data Tables | Mark Kelly (VCE) | Reading | IPO charts, data dictionaries — VCE-specific | VCE-specific lecture notes on design tools by Mark Kelly. Directly aligned to study design expectations. |
| Figma | Figma | Interactive (free tier) | Mock-ups, UI design | Industry-standard UI design tool with a free tier. Students can create professional mock-ups. More powerful than hand-drawing for detailed designs. |
| UX Prototypes: Low Fidelity vs. High Fidelity | Nielsen Norman Group (US) | Reading + visual examples | Mock-ups — sketch vs annotated mock-up distinction; 3–4 / 5–6 rubric boundary | Explains the full fidelity spectrum from rough pencil sketch through to high-fidelity annotated mock-up with real content, colour and fonts. Directly addresses the most common C5-1 boundary error: submitting a layout sketch and calling it a mock-up. Authoritative UX source; terminology matches VCAA usage. |
| Isaac Computer Science — Writing Algorithms | Isaac Computer Science (UK) | Reading + self-test questions | IPO charts — Process column: numbered algorithm steps, not outcome labels | Covers what an algorithm process is — a sequence of specific steps — versus what it produces. Directly targets the most common IPO process-column error: writing "calculate total" (an output label) instead of numbered steps. UK GCSE origin; the algorithm-as-steps concept is identical to VCE. |
| Isaac Computer Science — Pseudocode | Isaac Computer Science (UK) | Reading + self-test questions | Pseudocode — structured English syntax, BEGIN/END block structure, OOP methods | Covers pseudocode conventions including function/method block structure with BEGIN … RETURN … END, assignment arrows, and <> for not-equals. Helps students who code fluently in Python to shift to language-independent syntax. UK origin; cross-check any specific VCAA syntax differences with C051-Step-4-Pseudocode-Guide.md. |
Gaps — C5-1
- No video walkthrough of creating a complete set of design tools (mock-up + data dictionary + IPO chart + pseudocode + object descriptions) for a single VCE project.
- Object descriptions — very few external resources explain object descriptions in the VCAA format (properties, methods, events). Most OOP resources focus on class diagrams rather than object descriptions.
- Data dictionary format — the VCE-specific format (variable name, data type, data structure, data source, description) is not well-represented in generic resources. The Criterion05/ materials are the best source.
C5-2: Design Principles & UX
Existing Materials (CriterionXX/)
Criterion05/ has a UX characteristics and design principles guide, a Nelson activity on investigating usability, and design log templates. Good foundation.
External Resources
| Resource | Source | Format | VCAA Mapping | Why It's Useful |
|---|---|---|---|---|
| Figma Resource Library — Design Principles | Figma | Reading + visual examples | Design principles: alignment, balance, contrast, space | Professional design principles explained with visual examples. Students can see how real designers apply these principles. |
| Nielsen Norman Group — UX Research | Nielsen Norman Group | Reading + video | UX characteristics: usability, affordance | The world authority on UX/usability. Articles and videos on usability principles. Some content free, some paid. |
| Isaac Computer Science — Design Principles | Isaac Computer Science (UK) | Reading + self-test questions | Design principles — the seven principles and how they affect interface design; 3–4 / 5–6 / 7–8 annotation verb boundary | Names and defines each design principle with self-test questions. Crucial for C5-2 students who conflate design principles with UX characteristics — see also the Design Principles vs UX Characteristics wiki page for the two-list distinction. UK GCSE origin; all seven VCE-listed principles covered. |
| Isaac Computer Science — Design Documentation | Isaac Computer Science (UK) | Reading + self-test questions | Design log annotations — verb-level distinction: identify / describe / document / explain | Covers what good design documentation looks like and why annotation depth matters. Supports the annotation verb ladder (identify → describe → document → explain) central to moving up through the C5-2 bands. UK GCSE; concept maps directly to VCE annotation requirements. |
Wiki pages for C5-2
| Page | What it covers |
|---|---|
| Design Principles vs UX Characteristics | Why the seven design principles and four UX characteristics are two separate lists; the usability double-count trap; what the slot-five annotation validation is checking (DRAFT) |
Gaps — C5-2
- Design principles applied to software (not graphic design or web design) — most design principle tutorials are for web/graphic design. A VCE-specific resource showing how alignment, balance, contrast, space, and text formatting apply to a Python GUI application would be valuable.
- Affordance in software UX — a concept students find abstract. Need concrete examples of good and bad affordance in software interfaces.
- Annotations explaining design principle application — no external resource shows how to annotate a mock-up with design principle justifications in the VCAA format.
C5-3: Critical & Creative Thinking
Existing Materials (CriterionXX/)
Criterion05/ has a well-structured three-step process: Shoulders of Giants (research), Connect the Dots (link to requirements), Plan B Ready (contingencies), plus reflection activities.
External Resources
| Resource | Source | Format | VCAA Mapping | Why It's Useful |
|---|---|---|---|---|
| Isaac Computer Science — Wireframes and Prototyping | Isaac Computer Science (UK) | Reading + self-test questions | C5-3 Step 2 (Connect the Dots) — tracing a design idea from sketch through to IPO chart | Covers what wireframe/mock-up annotations should communicate between design layers: not just what an element is, but what it does, why it is there, and how it connects to a requirement. Supports the C5-3 Step 2 traceability requirement. UK GCSE origin; concept maps cleanly to VCE design-layer traceability. |
| Isaac Computer Science — Project Management | Isaac Computer Science (UK) | Reading + self-test questions | C5-3 Step 3 (Plan B Ready) — contingencies and mitigations; 7–8 / 9–10 band boundary | Covers risk identification and mitigation in project planning. Introduces the discipline of naming a specific risk and pairing it with a concrete mitigation — exactly what separates a vague contingency ("I will try another approach") from a rubric-level response. UK GCSE origin; risk/mitigation framing is curriculum-agnostic. |
Gaps — C5-3
- This is a VCAA-specific requirement. The existing Criterion05/ materials are well-designed for this purpose. External resources on "critical and creative thinking in software design" are either too generic or too academic.
Recommended Actions
- Figma (free tier) is recommended as the mock-up tool — more professional than hand-drawing and students learn an industry tool.
- Ryan's Tutorials IPO page is a good supplementary resource for IPO charts.
- Consider creating a design principles in software resource showing how alignment, balance, contrast, space, and text formatting apply specifically to GUI applications (not web/graphic design).