Blame
|
1 | # ๐ฌ C4 Design Ideas and Evaluation Explained |
||||||
| 2 | ||||||||
| 3 | Two short videos walking through how C4 works โ what you produce for your design pack, how the evaluation matrix supports the choice of which design proceeds, and what scores well at each VCAA band. |
|||||||
| 4 | ||||||||
| 5 | Watch in order. Each video pairs with one assessment package. |
|||||||
| 6 | ||||||||
|
7 | > [!TIP] |
||||||
| 8 | > **Don't just press play.** For each video: read the **๐ฏ Watch for** line first, keep the **โ๏ธ While you watch** artefact open beside you, hit pause at the **โธ** marks to predict before the narrator answers, then do the **Check Your Understanding** questions from memory. Unfold (`โธ`) only after you've answered. |
|||||||
| 9 | ||||||||
|
10 | --- |
||||||
| 11 | ||||||||
| 12 | ## 1. Design Ideas โ C4-1 |
|||||||
| 13 | ||||||||
| 14 | VCAA Criterion 4, Indicator 1 ยท Design defence presentation with your printed design pack |
|||||||
| 15 | ||||||||
|
16 | **๐ Two pictures to hold in your head** โ glance at these before you watch, then again after. |
||||||
| 17 | ||||||||
| 18 | *Five tools, one problem โ different lenses, not five copies:* |
|||||||
| 19 | ||||||||
| 20 | ```mermaid |
|||||||
| 21 | flowchart LR |
|||||||
| 22 | L1["Design-ideas list"] |
|||||||
| 23 | L2["Mood board"] |
|||||||
| 24 | L3["Brainstorm"] |
|||||||
| 25 | L4["Mind map"] |
|||||||
| 26 | L5["Annotated sketches"] |
|||||||
| 27 | P(("ONE design<br/>problem")) |
|||||||
| 28 | L1 --> P |
|||||||
| 29 | L2 --> P |
|||||||
| 30 | L3 --> P |
|||||||
| 31 | L4 --> P |
|||||||
| 32 | L5 --> P |
|||||||
| 33 | ``` |
|||||||
| 34 | ||||||||
| 35 | *The pack sets the ceiling; the pitch confirms how high you actually stand:* |
|||||||
| 36 | ||||||||
| 37 | ```mermaid |
|||||||
| 38 | flowchart LR |
|||||||
| 39 | A["Strong, original pack<br/>+ owns every decision"] --> A2(["9โ10"]) |
|||||||
| 40 | B["Strong pack<br/>+ vague pitch"] --> B2(["caps at a MIDDLE band"]) |
|||||||
| 41 | C["Thin pack<br/>+ eloquent pitch"] --> C2(["can't reach the top โ<br/>can't defend what isn't there"]) |
|||||||
| 42 | ``` |
|||||||
| 43 | ||||||||
|
44 | **๐ฏ Watch for:** this video reframes the assessment as a *design studio pitch* โ you're the junior designer, your teacher is the client. Listen for the one sentence-shape that proves you've *justified* a decision rather than just described it. |
||||||
| 45 | ||||||||
|
46 | โถ Watch on YouTube: https://youtu.be/Pfo-ksEHb64 |
||||||
| 47 | ||||||||
|
48 | **โ๏ธ While you watch:** have your design pack open. Pick one decision in it โ a layout, a colour, a flow โ and write a single sentence defending it as the video shows you how. |
||||||
| 49 | ||||||||
| 50 | **โธ Pause and predict** |
|||||||
| 51 | ||||||||
| 52 | - **1:50** โ You've just heard the five artefacts (ideas list, mood board, brainstorm, mind map, annotated sketches). Predict: are these five copies of the same thing, or something else? |
|||||||
| 53 | >| Five *different lenses on the same design problem* โ not duplicates. Each tool views the one design from a different angle. |
|||||||
| 54 | ||||||||
| 55 | - **5:05** โ A student has a strong design pack but pitches it vaguely. Predict the highest band they can reach. |
|||||||
| 56 | >| A middle band only. "The pack sets the ceiling, but the pitch confirms the level" โ you can't claim top marks for decisions you can't defend out loud. |
|||||||
| 57 | ||||||||
| 58 | **Check Your Understanding** |
|||||||
| 59 | ||||||||
| 60 | 1. In one sentence, what's the difference between an annotation that *describes* and one that *justifies*? |
|||||||
| 61 | >| Describing says how something looks or works; justifying names an alternative you rejected and gives the reason. |
|||||||
| 62 | ||||||||
| 63 | 2. A student's pitch is fluent and confident, but their design pack is thin. Can they reach 9โ10? Why or why not? |
|||||||
| 64 | >| No. You can't defend artefacts that don't exist โ the pack is the *floor* of the evidence, and the pitch only confirms the level the pack already supports. |
|||||||
| 65 | ||||||||
| 66 | 3. Fill in the trade-off sentence shape examiners listen for: "I considered ___, I chose ___, because ___." |
|||||||
| 67 | >| considered **X** / chose **Y** / because **Z** โ naming the rejected alternative is what lifts a decision from *describe* to *justify*. |
|||||||
|
68 | |||||||
| 69 | --- |
|||||||
| 70 | ||||||||
| 71 | ## 2. Evaluation Criteria โ C4-2 |
|||||||
| 72 | ||||||||
| 73 | VCAA Criterion 4, Indicator 2 ยท Written evaluation test with your printed evaluation outline and design pack |
|||||||
| 74 | ||||||||
|
75 | **๐ Two pictures to hold in your head** โ glance at these before you watch, then again after. |
||||||
| 76 | ||||||||
| 77 | *Each criterion is a bridge-plank between what the software MUST do and how it COULD be built:* |
|||||||
| 78 | ||||||||
| 79 | ```mermaid |
|||||||
| 80 | flowchart LR |
|||||||
| 81 | SRS["๐ SRS<br/>what it MUST do"] |
|||||||
| 82 | DES["๐จ Design ideas<br/>how it COULD be built"] |
|||||||
| 83 | SRS ==>|"efficiency criterion<br/>name ยท link ยท measure"| DES |
|||||||
| 84 | SRS ==>|"effectiveness criterion<br/>name ยท link ยท measure"| DES |
|||||||
| 85 | ``` |
|||||||
| 86 | ||||||||
| 87 | *The rubric is a staircase โ each step up unlocks a stronger verb:* |
|||||||
| 88 | ||||||||
| 89 | ```mermaid |
|||||||
| 90 | flowchart BT |
|||||||
| 91 | I["identify<br/>names measures, no matrix"] --> O["outline<br/>linked, basic matrix"] |
|||||||
| 92 | O --> DA["develop & apply<br/>matrix filled with evidence ยท bands 1โ6"] |
|||||||
| 93 | DA --> E["explain<br/>which elements proceed ยท bands 7โ8"] |
|||||||
| 94 | E --> J["justify<br/>names the rival + accepts the trade-off ยท bands 9โ10"] |
|||||||
| 95 | ``` |
|||||||
| 96 | ||||||||
|
97 | **๐ฏ Watch for:** this video reframes C4-2 as writing a *product review* (think Choice or Wirecutter). Listen for the difference between an *explain* statement and a *justify* statement โ it's the single highest-leverage move in the rubric. |
||||||
| 98 | ||||||||
|
99 | โถ Watch on YouTube: https://youtu.be/aQaV2Gb_CLE |
||||||
| 100 | ||||||||
|
101 | **โ๏ธ While you watch:** have your SRS and evaluation outline open. Take one vague criterion (e.g. "easy to use") and rewrite it as a measurable test as the video shows you how. |
||||||
| 102 | ||||||||
| 103 | **โธ Pause and predict** |
|||||||
| 104 | ||||||||
| 105 | - **2:46** โ The narrator says a good matrix needs *both* columns. Predict: what do you miss if you score only effectiveness? Only efficiency? |
|||||||
| 106 | >| Effectiveness-only: you don't know if the software actually *runs* well (speed, resource use). Efficiency-only: you ignore whether it actually works for the *humans* using it. |
|||||||
| 107 | ||||||||
| 108 | - **3:33** โ "The design must be user-friendly." Predict how you'd turn this into something you could actually score. |
|||||||
| 109 | >| Give it a measurable test โ e.g. "a new user completes the core task in under 90 seconds, unassisted." If you can't point to what you'd look at, you can't measure it. |
|||||||
| 110 | ||||||||
| 111 | - **8:15** โ A student explains why Design A scores well but never mentions Design B. Predict the highest band they can reach. |
|||||||
| 112 | >| Capped at 8. To reach 9โ10 you must *name the rival* โ weigh the competing design and explicitly accept the trade-off. |
|||||||
| 113 | ||||||||
| 114 | **Check Your Understanding** |
|||||||
| 115 | ||||||||
| 116 | 1. What three parts must every evaluation criterion contain? |
|||||||
| 117 | >| A **name** (what's measured), a **link** (to a specific SRS requirement), and a **measure** (the concrete, testable way you'll check it). |
|||||||
| 118 | ||||||||
| 119 | 2. Which column holds *speed of processing*, and which holds *usability*? |
|||||||
| 120 | >| Speed of processing โ **efficiency**. Usability โ **effectiveness**. VCAA names **3** efficiency measures and **11** effectiveness measures. See [Efficiency vs Effectiveness](/sd/C04/Efficiency%20vs%20Effectiveness). |
|||||||
| 121 | ||||||||
| 122 | 3. The matrix and the recommendation paragraph evidence different band ranges. Which is which? |
|||||||
| 123 | >| Matrix = the **floor**, evidences bands 1โ6. Recommendation paragraph = the **ceiling**, evidences bands 7โ10. You need both. |
|||||||
|
124 | |||||||
| 125 | --- |
|||||||
| 126 | ||||||||
| 127 | ## Related pages |
|||||||
| 128 | ||||||||
| 129 | - [C04 home](/sd/C04/C04-home) |
|||||||
|
130 | - [Efficiency vs Effectiveness](/sd/C04/Efficiency%20vs%20Effectiveness) |
||||||
| 131 | - [Evaluation Criteria and the SRS](/sd/C04/Evaluation%20Criteria%20and%20the%20SRS) |
|||||||
| 132 | - [C2 and C3 Assessment Explained](/sd/C2%20and%20C3%20Assessment%20Explained) |
|||||||
| 133 | - [VCE Software Development Hub](/sd/VCE%20Software%20Development%20Hub) |
|||||||
