An Eduspace Wiki
Changelog
Documentation
Toggle dark mode
Login
Home
A - Z
Page Index
sd
C01
AI Disclosure
C01-home
Critical Path
Essential Terms
Mr Chen's SAT GitHub Projects
Overflow
Problem-Solving Methodology
Roadmap View vs Gantt Chart
TELOS Feasibility
Testing vs Validation vs Evaluation
C02
Building Your C2-1 Poster
C02-home
Context Diagram
Context Diagram vs Data Flow Diagram
Data Collection Methods
Data Flow Diagram
Essential Terms
Excalidraw Diagram Starters
Explaining vs Describing Your Data Collection
Hand-Drawing Cheat-Sheet
Use Case Diagram
User Stories and MoSCoW
What Is an Entity
C03
Analytical Tools Template Guide
C03-home
Essential Terms
Evaluating Your Own Questions
Functional vs Non-Functional Requirements
Scope vs Constraints
Technical Environment — Five Categories
C04
Activity - Hot Cross Bun Matrix
Brainstorming
C04-home
C4-1 Checkpoint - Design Pack
C4-2 Checkpoint - Evaluation Matrix
CHOICE Headphones - Spotting Efficiency and Effectiveness
Design Sketches
Designing an Evaluation Matrix
Efficiency vs Effectiveness
Essential Terms
Evaluation Criteria and the SRS
Evaluation vs Testing
Mind Mapping
Mood Boards
C05
Annotated Mock-up in Excalidraw
C04 to C05 - Choose then Detail
C05-home
Connect the Dots
Creative Thinking for Your Godot Project
Data Dictionary
Design Principles
Design Principles vs UX Characteristics
Essential Terms
From SRS to Detailed Designs - Data and Logic
From SRS to Detailed Designs - Mock-ups
IPO Charts - Process Means Steps
Object Descriptions and Class Diagrams
Plan B Contingency Table
Plan B Ready
Shoulders of Giants
Sketch vs Mock-up
The Annotation Verb Ladder
UX Characteristics
VCAA Pseudocode Not Python
C06
C06-home
Control Structures
Data Sources
Data Structures
Data Type Characteristics
Data Types
Essential Terms
Functions and Methods
GUI and Controls
Instructions and Operators
Local and Global Variables
OOP Concepts
C07
C07-home
Essential Terms
Internal Documentation
Naming Conventions
Validation Techniques
C08
C08-home
Contingency Planning
Debugging with Breakpoints in Godot
Debugging with Tetris
Essential Terms
Godot Debugging Tools
Modifying Designs with Annotations
Software Testing Hierarchy
Testing Tables and Corrections
Types of Test Data
Updating Evaluation Criteria
C09
Beta Test Execution
Beta Testing Case Study Pocket Prep
Beta Testing Plan Example Godot Tetris
Beta Testing Plan Template
Beta Testing Plan Three Levels
Beta Testing Report Examples
Beta Testing Report Guide
C09-home
Data Collection Examples
Data Collection Methods
Data Collection Template
Essential Terms
Priority Matrix
Software Modifications Mindmap
Test Scenario FitTrack
Test Scenario Template
The Four-Step Beta Testing Journey
Timeline and Resource Considerations
C10
C10-home
Development Process Portfolio
Essential Terms
Future Evaluation Strategy
Project Plan Effectiveness
Reading a Git Log
Recording Project Progress
Tracking Plan Changes
C2 and C3 Assessment Explained
C4 Design Ideas and Evaluation Explained
Resources
C01-Resources
C02-Resources
C03-Resources
C04-Resources
C05-Resources
C06-Resources
C07-Resources
C08-Resources
C09-Resources
C10-Resources
SAT-Tools
Test-Excalidraw-Embed
U4O2 Cyber Security — Booklet 1 Videos
VCE Software Development Hub
An Otter Wiki
sd
C05
Page Index - C05
Toggle page headings
A
Annotated Mock-up in Excalidraw
What an annotated mock-up needs
Setting up the template in Excalidraw
Step 1 — Open a new file
Step 2 — Draw the screen frame
Step 3 — Place UI components
Step 4 — Add the annotation zone
Step 5 — Add callout arrows
Step 6 — Write annotation text
Standard annotation structure (copy and fill in)
Saving your template
Common mistakes
See also
C
C04 to C05 - Choose then Detail
The one-sentence rule
One picture
Side-by-side
The trap
Check Your Understanding
See also
C05-home
Foundations
C5-1 — Design tools
C5-2 — Design principles & UX
C5-3 — Critical & creative thinking
Templates and scaffolds
Resources
Connect the Dots
Level 1 — Annotate your designs
Level 2 — Link to your SRS requirements
Level 3 — Trace through to detailed designs
Performance ladder
Quick checklist
Check Your Understanding
See also
Creative Thinking for Your Godot Project
Move 1 — Diverge before you converge
Move 2 — Grey-box prototype to test a design idea
Move 3 — Remix and combine
Move 4 — Use a constraint as a creativity engine
Move 5 — Design the "game feel"
Move 6 — Stand on the Godot ecosystem's shoulders — creatively
Move 7 — Document your pivots
Capture it for your folio
Check Your Understanding
See also
D
Data Dictionary
When do you use a data dictionary?
Video 1 — What is a data dictionary?
The headings to include
A worked example
"Data format" is not "data type"
Video 2 — Data dictionaries in code
The VCAA levels
Activity — your turn
Common mistakes
Mistake 1: Format = Type
Mistake 2: Missing data sources at Level 7
Mistake 3: Vague sizes
Check Your Understanding
Extension — a data dictionary you can play with
Credits
See also
Design Principles vs UX Characteristics
The two lists, side by side
What VCAA asks for at each band
The slot-five validation trap
Common mistakes
Mistake 1: "UX" as a catch-all
Mistake 2: Listing design principles under UX and vice versa
Mistake 3: Describing usability once and assuming you have covered both lists
See also
Design Principles
The seven principles at a glance
How to apply each principle
🎬 Watch — the principles in action
Check Your Understanding
See also
E
Essential Terms
Design tools
Design principles
UX characteristics
Usability and accessibility
Evaluation words
Thinking styles
See also
F
From SRS to Detailed Designs - Data and Logic
The four tools are one design
Fully worked: "computed, never stored", through all four tools
Tool 1 — Data dictionary: a separate section for what is not stored
1. Criteria (CRITERIA)
2. Band scale (BANDS, BAND_LABELS)
4. Student record (MOCK_STUDENTS → one markdown file per student in Sprint 2)
5. Derived values (computed, never stored)
Tool 2 — Object descriptions: stored is an attribute, derived is a method
The same class as an object description table
Tool 3 — Pseudocode: how the derived value is actually computed
Tool 4 — IPO charts: it can recompute live because nothing is stored
Each tool, anchored to a requirement (your turn to finish each)
Data dictionary ← FR2 + SRS §7
IPO charts ← the context diagram
Pseudocode ← FR5 + corrections 06/07
Object descriptions ← the problem domain
Your turn — trace validation_gap through three tools
The real files
Check Your Understanding
See also
From SRS to Detailed Designs - Mock-ups
The chain in one picture
Trace 1 — FR3, fully worked
Trace 2 — FR9, with the guidance faded
Trace 3 — FR6, your turn
The real files
Check Your Understanding
See also
I
IPO Charts - Process Means Steps
The core rule
Video 1 — What is an IPO chart?
Check Your Understanding
The big idea: from DFD to IPO
(template) Name of the process
DFD process: Get Input
DFD process: Initialise Stored Credentials
DFD process: Validate User
Wrong vs Right
Common mistakes
Mistake 1: Process that copies the Output
Mistake 2: Missing the decision branches
Mistake 3: Inputs not traced to the DFD
Mistake 4: One IPO chart for everything
Check Your Understanding
Credits
See also
O
Object Descriptions and Class Diagrams
Reading a class diagram
The notation you need
Object descriptions — the written form
Example 1 — Animal and Dog
Example 2 — a Skill made of effects ("object descriptions about skills")
Properties, methods — and events
How it connects to your other design tools
Common mistakes
Mistake 1: An object description with no methods
Mistake 2: No visibility or data types
Mistake 3: Classes drawn with no relationships
Mistake 4 (Level 9): A class diagram but no method pseudocode
Check Your Understanding
Credits
See also
P
Plan B Contingency Table
The template
How to fill it in
What makes a good Contingency / Backup design entry
What makes a good Impact if triggered entry
Completed example (ClubTracker project)
Adding your own risks
See also
Plan B Ready
Identify design risks
Document contingency plans
Show the backup designs
Performance levels
Quick checklist
Check Your Understanding
See also
S
Shoulders of Giants
Why look at existing solutions?
What counts as an existing solution?
Analyse each solution in a table
Connect findings to your design
Performance levels
Quick checklist
Check Your Understanding
See also
Sketch vs Mock-up
What each one is
The progression: sketch → mock-up
🎬 Watch
Video 1 — Wireframe vs Mockup vs Prototype
Video 2 — Excalidraw in practice
For Level 9: completeness matters
Common mistakes
Mistake 1: Submitting a sketch and labelling it a mock-up
Mistake 2: A polished screen with no annotations
Mistake 3: Only the main screen
Mistake 4: Annotations that only describe
Check Your Understanding
See also
T
The Annotation Verb Ladder
The four rungs
The same entry, rewritten four times
The 6-slot structure
Build the design log NOW
Common mistakes
Mistake 1: Notes that stay at "identify"
Mistake 2: No journal entry reference
Mistake 3: Describing the feature instead of the principle
🎬 Watch
Check Your Understanding
See also
U
UX Characteristics
Affordance
Interoperability
Security
Three ways security is getting more usable
Usability
Everyday example — the ketchup bottle
Check Your Understanding
See also
V
VCAA Pseudocode Not Python
🎬 What is pseudocode?
The two rules that actually matter
Pseudocode ↔ Python comparison
Program structure and basics
Selection
Iteration
Operators
Subprograms (methods / functions / procedures)
Worked example 1 — a method inside a class
Worked example 2 — one algorithm, any machine
Common mistakes
Mistake 1 — Using = or == for assignment
Mistake 2 — Using != for not-equals
Mistake 3 — Python-only constructs leaking in
Mistake 4 — Forgetting closing keywords
Mistake 5 — Inconsistent block keywords
Check Your Understanding
Credits
See also
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9
