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
# Recording Project Progress — a 20-Minute Practice Task
3
4
*A worked scenario for practising the three C10-3 recording techniques on somebody else's project, before you apply them to your own.*
5
6
> [!NOTE]
7
> **The band this serves.** C10-3, 7–8: *"Uses adjustments or logs/journals to document and explain the modifications made to the initial project plan."* The three techniques below — annotation, task adjustment, log entry — are exactly the instruments that descriptor names.
8
9
## Task Overview
10
11
**Duration:** 20 minutes
12
**Skills:** SD41KS01 - Monitor, modify and annotate project plans as necessary
13
**Assessment:** C10-3 preparation
14
15
## Scenario
16
17
You're the cybersecurity developer for an online quiz application used by schools. Your original project plan estimated:
18
19
- User authentication system: 2 days
20
- Data encryption implementation: 2 days
21
- Security testing and vulnerability assessment: 1 day
22
- **Total: 5 days**
23
24
**Reality:** It's now Day 4, and you've discovered several critical security issues that will extend your timeline significantly.
25
26
```mermaid
27
gantt
28
title The quiz-app scenario — planned 5 days, actual 8
29
dateFormat YYYY-MM-DD
30
axisFormat Day %d
31
section Planned
32
Authentication :p1, 2025-01-01, 2d
33
Encryption :p2, 2025-01-03, 2d
34
Security testing :p3, 2025-01-05, 1d
35
section Actual
36
Authentication +1 (two-factor) :crit, a1, 2025-01-01, 3d
37
Encryption +1 (end-to-end) :crit, a2, 2025-01-04, 3d
38
Testing +1 (SQL injection) :crit, a3, 2025-01-07, 2d
39
```
40
41
*Read the slip off the bars: every task moved by one day, and because they run in sequence the finish date moved by three. This is the picture your annotations have to explain.*
42
43
44
## Your Task
45
46
Apply the three project recording techniques to document what's happening:
47
48
### 1. Annotations to Project Plans
49
50
**Tool:** Create a simple Gantt chart (GitHub Projects, Excel, or hand-drawn)
51
52
**Instructions:**
53
54
- Mark your original timeline
55
- Add annotations showing:
56
- Authentication took 3 days (not 2) due to implementing two-factor authentication for teacher accounts
57
- Data encryption will need 3 days (not 2) because quiz answers require end-to-end encryption
58
- Security testing needs 2 days (not 1) after discovering SQL injection vulnerabilities
59
60
**What to annotate:** Why security requirements changed, not just that they changed
61
62
### 2. Adjustments to Tasks
63
64
**Tool:** Create 3 GitHub Issues or log entries
65
66
**Record these cybersecurity task modifications:**
67
68
- **Original task:** "Basic user login system"
69
70
- **Modified task:** "Multi-factor authentication with role-based access (student/teacher/admin)"
71
72
- **Reason:** School district requires enhanced security after recent data breaches
73
74
- **Original task:** "Encrypt stored quiz data"
75
76
- **Modified task:** "Implement AES-256 encryption for data at rest and TLS 1.3 for data in transit"
77
78
- **Reason:** Compliance with student privacy regulations
79
80
81
### 3. Monitoring Progress Using Logs/Journals
82
83
**Tool:** OneNote page or simple document
84
85
**Create a 4-day cybersecurity progress log:**
86
87
- **Day 1:** "Basic login working, but district security officer requested two-factor authentication review"
88
- **Day 2:** "Implementing SMS-based 2FA, discovered need for backup codes for students without phones"
89
- **Day 3:** "Encryption module complete, but penetration testing revealed session hijacking vulnerability"
90
- **Day 4:** "Behind schedule but security compliance significantly improved - no data breach risks identified"
91
92
## Deliverables
93
94
1. Annotated cybersecurity project timeline showing changes
95
2. Three security task adjustment records with compliance reasoning
96
3. Four-day cybersecurity progress journal
97
98
## Success Criteria
99
100
✅ Demonstrates understanding of **why** security changes occurred, not just **what** changed
101
✅ Shows practical application of each recording technique in cybersecurity context
102
✅ Prepares evidence for C10-3 assessment requirements
103
✅ Reflects real-world cybersecurity project challenges
104
105
## Reflection Questions
106
107
1. Which technique gave you the clearest picture of cybersecurity project changes?
108
2. How would this security documentation help you plan future cybersecurity implementations?
109
3. What would happen if security modifications weren't properly recorded for compliance audits?
110
4. Why is thorough documentation especially critical in cybersecurity projects?
111
112
## Real-World Connection
113
114
**Cybersecurity projects often require extensive documentation because:**
115
116
- Compliance audits need detailed change records
117
- Security incidents require traceability of all modifications
118
- Budget justification for extended timelines due to security requirements
119
- Team handovers must include complete security implementation history
120
121
---
122
123
**Assessment Connection:** This task directly prepares you for demonstrating C10-3: "Documents the modifications made to the initial project plan throughout the duration of the project" while building cybersecurity awareness.