Home A - Z
Page Index

An Otter Wiki

Blame

5c1696 lisa 2026-08-29 16:39:27
Add sd/C10: hub + guides for the in-class model Seven curated learning pages plus the C10 home hub, generated by the shared port script (new c10 config): the C100-* cluster, the tick sheet, the solutions booklet and the assessment paperwork stay out of the wiki. Each page gains a skill title, a lead naming the rubric band it serves, one earned mermaid visual and a Check Your Understanding fold. The git-log examples are anonymised (prior-cohort names, hostnames and repo URL removed). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RxqgYbTNNYrPNuko6xfbKs
1 
<!-- Generated from applied-computing-au vic/unit3-4/sat/C10-2026 by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. -->
2
# C10 — Skills in Evaluating the Solution and Assessing the Project Plan
3
4
The Hamilton and Alexandra College · Year 12 · 2026
5
6
C10 is the *lightest* criterion in the SAT: almost all of its evidence already exists in your repository. There is no checkpoint, no separate validation sitting and no interview. Each judgement is **taught** in a short slot, **written** by hand in class from printouts of your own work, and **graded** against what your repo already shows.
7
8
```mermaid
9
flowchart LR
10
H["At home<br/>C10 Booklet — The Last Mile<br/>practise on Godot Tetris"] --> T
11
T["In class · 3 instruction slots<br/>5–10 min each"] --> C
12
C["In class · 3 collected class writes<br/>handwritten · no internet"] --> G
13
R["Already in your repo<br/>C4 matrix · SRS, mockup and UI trail<br/>baseline Gantt · commit history"] --> G
14
G["Your C10 mark<br/>4 indicators × 25% = /40"]
15
```
16
17
*Two streams meet at your mark: what you write by hand on the day, and what your repository already proves. Neither carries C10 on its own.*
18
19
## How C10 runs
20
21
| Indicator | Taught — slot (5–10 min) | Written in class (collected) | Graded from |
22
|---|---|---|---|
23
| **C10-1** Solution evaluation | **Slot 1** — Use · Explain · Propose | Class write 1 — your solution (≈ half a lesson) | Your C4 matrix, and the repo evidence each verdict cites |
24
| **C10-2** Stages evaluation | **Slot 2** — evaluate, don't describe | Class write 2 — your process (≈ 20 min) | SRS versions, mockups and UI screenshots, timestamped |
25
| **C10-3** Plan modifications | **Slot 3** — annotate, then judge twice | Class write 3, side A — your plan, annotated (≈ 10 min) | Baseline Gantt, board snapshots, commit history |
26
| **C10-4** Plan effectiveness | **Slot 3** — same slot; the sheet walked through | Class write 3, side B — the effectiveness sheet (≈ 15 min) | The collected sheet and the dates it cites |
27
28
Each indicator is scored out of 10 and is worth **25%** of the criterion — **/40** in total.
29
30
> [!NOTE]
31
> **Conditions — all three class writes.** 🔒📱 Handwritten on the sheet provided: no internet, no devices, no notes. Your teacher hands you printouts of *your own* work — your C4 matrix, your SRS/mockup/UI trail, your plan. Sheets are collected at the end of the lesson.
32
33
::: info
34
# Two dates are checked before your marks are set
35
Your **C4 evaluation matrix** must have been committed *before* the C9 beta window opened, and your **SRS refresh** *before* the C6/7 validation. Your teacher reads those dates from the server — `git log`, or the commit page on GitHub, never a date typed inside a document. Criteria fixed before the results exist are predictions your evaluation genuinely tests; criteria written afterwards can be shaped to fit and prove nothing. You might lose marks if either is overdue.
36
:::
37
38
At home you practise each judgement in the **C10 Booklet — The Last Mile** on the worked Godot Tetris example, watch the set video, and complete the *commit-now* prep step before class write 3 — commit your plan's current state with an honest note of what has changed since your C01 baseline. Honest gaps count. The booklet and the full assessment package are in your `S-C10` folder.
39
40
## Foundations
41
42
- [Essential Terms](/sd/C10/Essential%20Terms)
43
44
## C10-1 — Evaluating the solution
45
46
- [Proposing a Future Evaluation Strategy](/sd/C10/Future%20Evaluation%20Strategy)
47
48
## C10-2 — Evaluating the analysis, design and development stages
49
50
- [Writing the Development Process Portfolio](/sd/C10/Development%20Process%20Portfolio)
51
52
## C10-3 — Documenting the modifications to your project plan
53
54
- [Tracking Plan Changes](/sd/C10/Tracking%20Plan%20Changes) — annotated Gantt charts and project logs
55
- [Recording Project Progress](/sd/C10/Recording%20Project%20Progress) — a 20-minute practice task
56
- [Reading a Git Log](/sd/C10/Reading%20a%20Git%20Log) — three real logs, anonymised
57
58
## C10-4 — Assessing the effectiveness of your project plan
59
60
- [Project Plan Effectiveness](/sd/C10/Project%20Plan%20Effectiveness)