Commit ec051f
2026-04-25 23:04:06 lisa: Add C05 wiki content (DRAFT) — landing page, Resources rows Light first pass: C05-home, 1 key-concept page marked DRAFT, external resource rows in C05-Resources.md. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>| /dev/null .. sd/C05/C05-home.md | |
| @@ 0,0 1,21 @@ | |
| + | # C05 — Skills in Producing Detailed Designs |
| + | |
| + | Hamilton College · Year 12 · 2026 |
| + | |
| + | 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. |
| + | |
| + | --- |
| + | |
| + | ## Key concepts |
| + | |
| + | Short explainers for the concepts most commonly confused or under-done at each rubric band: |
| + | |
| + | - [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 |
| + | |
| + | ## Resources |
| + | |
| + | - [C05 Resources](/sd/Resources/C05-Resources) — per-topic reading and external resources for design tools, design principles, UX characteristics, and critical and creative thinking |
| + | |
| + | --- |
| + | |
| + | ← Back to [VCE Software Development Hub](/sd/VCE%20Software%20Development%20Hub) |
| /dev/null .. sd/C05/Design Principles vs UX Characteristics.md | |
| @@ 0,0 1,88 @@ | |
| + | > **DRAFT** — under teacher review. |
| + | |
| + | # Design Principles vs UX Characteristics — Two Separate Lists |
| + | |
| + | Hamilton College · Year 12 · 2026 |
| + | |
| + | One of the most reliable ways to lose marks in C5-2 is to mix up the seven design principles with the four UX characteristics, or to count usability once in each list and assume you have covered both. These are two distinct frameworks defined in the study design — you must use the right name from the right list at the right time. |
| + | |
| + | --- |
| + | |
| + | ## The two lists, side by side |
| + | |
| + | | Design Principles (7 items) | UX Characteristics (4 items) | |
| + | |---|---| |
| + | | Alignment | Affordance | |
| + | | Balance | Interoperability | |
| + | | Contrast | Security | |
| + | | Space | Usability | |
| + | | Text formatting | | |
| + | | Usability | | |
| + | | Navigation | | |
| + | |
| + | Notice that **Usability appears in both lists** — but it means slightly different things in each context: |
| + | |
| + | - As a **design principle**, usability is about the visual and structural choices that make an interface easy to operate: consistency, clear feedback, error prevention. |
| + | - As a **UX characteristic**, usability is the overall ease-of-use measure across efficiency, effectiveness and satisfaction. |
| + | |
| + | If you annotate a mock-up by saying "I applied usability by making the buttons large", you have referenced the design principle. If your design log entry says "The high usability of this interface is demonstrated by the 3-second task completion in user testing", you are addressing the UX characteristic. |
| + | |
| + | --- |
| + | |
| + | ## What VCAA asks for at each band |
| + | |
| + | The C5-2 rubric builds from listing to identifying to describing to documenting to demonstrating. The key verb for each band applies to **both lists**: |
| + | |
| + | | Band | What you must do | |
| + | |---|---| |
| + | | 1–2 | List items from each list that you considered | |
| + | | 3–4 | Briefly **identify** how design principles appear in your mock-ups | |
| + | | 5–6 | **Describe** how design principles appear — with reference to appearance and functionality | |
| + | | 7–8 | **Document** how relevant UX characteristics have been applied — this is where you bring in affordance, interoperability, security and usability with specific evidence | |
| + | | 9–10 | **Demonstrate and explain** — argue that your choices produce the UX outcomes, not just that you made the choices | |
| + | |
| + | The 9–10 band specifically requires you to work across both lists in a connected way. An annotation that says "I used contrast (design principle) to make the login button more visible, improving affordance (UX characteristic) for first-time users" is the kind of cross-list reasoning VCAA is checking for. |
| + | |
| + | --- |
| + | |
| + | ## The slot-five validation trap |
| + | |
| + | The Annotation validation has six slots. Slot five requires you to use **one design principle and one UX characteristic** in a single annotation entry. If you write two design principles and call one of them a UX characteristic, the slot is marked empty regardless of the quality of your writing. |
| + | |
| + | Checklist for each annotation slot: |
| + | |
| + | - [ ] Named the design principle correctly (from the list of 7) |
| + | - [ ] Named the UX characteristic correctly (from the list of 4) — if required for this slot |
| + | - [ ] Described how the principle was applied in terms of **appearance or functionality** (not just "I used it") |
| + | - [ ] Used the correct verb level for the band you are targeting |
| + | |
| + | --- |
| + | |
| + | ## Common mistakes |
| + | |
| + | ### Mistake 1: "UX" as a catch-all |
| + | |
| + | > ~~"I considered UX in my design."~~ |
| + | |
| + | "UX" is not on either list. The study design names four specific UX characteristics. You must name the one you mean: affordance, interoperability, security or usability. |
| + | |
| + | ### Mistake 2: Listing design principles under UX and vice versa |
| + | |
| + | > ~~"The UX characteristics I used were: alignment, contrast, and affordance."~~ |
| + | |
| + | Alignment and contrast are design principles, not UX characteristics. A marker reading this loses confidence in your vocabulary immediately. |
| + | |
| + | ### Mistake 3: Describing usability once and assuming you have covered both lists |
| + | |
| + | Because usability appears in both lists, students sometimes write one sentence and consider both boxes ticked. You need separate evidence: one piece of annotation evidence for usability as a design-principle decision, and a different piece showing the UX-characteristic measure of how easy your system actually is to use. |
| + | |
| + | --- |
| + | |
| + | ## See also |
| + | |
| + | - [Isaac Computer Science — Design Principles (GCSE)](https://isaaccomputerscience.org/concepts/gcse_design_principles) — clear breakdown of individual design principles with self-test questions; UK origin, terminology maps directly to VCE |
| + | - C05 Resources: [external reading and resources](/sd/Resources/C05-Resources) |
| + | |
| + | --- |
| + | |
| + | ← Back to [C05 Home](/sd/C05/C05-home) · [VCE Software Development Hub](/sd/VCE%20Software%20Development%20Hub) |
| sd/Resources/C05-Resources.md .. | |
| @@ 19,6 19,9 @@ | |
| | [Lucidchart — UML Class Diagram Tutorial](https://www.lucidchart.com/pages/uml-class-diagram) | 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](https://studylib.net/doc/9259677/database-design-tools---vce-it-lecture-notes-by-mark-kelly) | 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](https://www.figma.com/) | 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](https://www.nngroup.com/articles/ux-prototype-hi-lo-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](https://isaaccomputerscience.org/concepts/gcse_prog_algorithm_writing) | 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](https://isaaccomputerscience.org/concepts/prog_func_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 | |
| @@ 40,6 43,14 @@ | |
| |----------|--------|--------|--------------|-----------------| | |
| | [Figma Resource Library — Design Principles](https://www.figma.com/resource-library/) | 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](https://www.nngroup.com/) | 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](https://isaaccomputerscience.org/concepts/gcse_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](/sd/C05/Design%20Principles%20vs%20UX%20Characteristics) wiki page for the two-list distinction. UK GCSE origin; all seven VCE-listed principles covered. | |
| + | | [Isaac Computer Science — Design Documentation](https://isaaccomputerscience.org/concepts/gcse_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](/sd/C05/Design%20Principles%20vs%20UX%20Characteristics) | 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 | |
| @@ 59,7 70,8 @@ | |
| | Resource | Source | Format | VCAA Mapping | Why It's Useful | | |
| |----------|--------|--------|--------------|-----------------| | |
| - | | No strong external resources found for this specific VCAA requirement. | — | — | — | — | |
| + | | [Isaac Computer Science — Wireframes and Prototyping](https://isaaccomputerscience.org/concepts/gcse_design_wireframes) | 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](https://isaaccomputerscience.org/concepts/gcse_sys_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 | |