Home A - Z
Page Index

An Otter Wiki

Blame

0648ae lisa 2026-06-08 09:18:19
Add C05 student wiki pages: design tools, annotation, traceability Six DRAFT pages under /sd/C05 targeting common rubric-boundary errors: - Sketch vs Mock-up (C5-1) — embeds two videos - Data Dictionary — Format is not Type (C5-1) - IPO Charts — Process Means Steps (C5-1) - VCAA Pseudocode — Not Python (C5-1) - The Annotation Verb Ladder (C5-2) - Connect the Dots — design traceability (C5-3) Pages 2-6 have video slots pending teacher selection. Home index reorganised by indicator. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 
> **DRAFT** — under teacher review.
2
3
# IPO Charts — Process Means Steps, Not the Answer
4
5
The Hamilton and Alexandra College · Year 12 · 2026
6
7
An IPO chart has three columns — Input, Process, Output — and you write one chart per functional requirement. The chart connects directly to the rest of your design work: your inputs should already appear in your context diagram or DFD, and your Process column should express the same logic as your pseudocode.
8
9
The trap that caps students at the 5–6 band is writing the Process column as an outcome instead of as steps. This page shows you exactly what that looks like, and how to fix it.
10
11
---
12
13
## The core rule
14
15
> [!TIP]
16
> **Process = the steps your algorithm performs.**
17
> If your Process cell could also be your Output cell, it is wrong.
18
19
The three columns do different jobs:
20
21
- **Input** — the data that enters the functional requirement (trace these from your context diagram / DFD).
22
- **Process** — the numbered steps or operations performed on those inputs. Think of it as pseudocode in plain English.
23
- **Output** — the result produced after the inputs are processed.
24
25
---
26
27
## Wrong vs Right — the same requirement, two ways
28
29
The functional requirement below is: *calculate a sales bonus*.
30
31
| | Input | Process | Output |
32
|---|---|---|---|
33
| **WRONG** | Sales amount, Bonus percentage | Calculate the bonus | Bonus amount |
34
| **RIGHT** | Sales amount, Bonus percentage | 1. Check if sales amount > 10,000. 2. If true, bonus = sales amount × bonus percentage. 3. If false, bonus = 0. | Bonus amount |
35
36
Notice what went wrong in the WRONG row:
37
38
- "Calculate the bonus" is just a restatement of the Output.
39
- It tells you nothing about *how* the calculation works.
40
- A marker cannot award credit for logic that isn't shown.
41
42
The RIGHT row shows the decision and the two branches. That is what earns marks in the upper bands.
43
44
---
45
46
## How the three columns connect to your other design work
47
48
```mermaid
49
flowchart LR
50
CD["Context diagram / DFD<br/>(identifies data flows)"]
51
IPO["IPO chart<br/>(Input · Process · Output)"]
52
PS["Pseudocode<br/>(same logic, formal syntax)"]
53
CD -->|"inputs come from here"| IPO
54
IPO -->|"process mirrors this"| PS
55
```
56
57
Your Process column and your pseudocode should describe the same algorithm. If they contradict each other, one of them is wrong — check both.
58
59
---
60
61
## 🎬 Watch
62
63
> [!NOTE]
64
> Video coming soon.
65
66
**🎯 Watch for:** how a complete Process column maps directly onto a pseudocode IF–THEN–ELSE structure, making it obvious that the Process column is algorithm steps, not a label for the Output.
67
68
---
69
70
## Common mistakes
71
72
### Mistake 1: Process that copies the Output
73
74
> ~~"Work out the bonus amount."~~
75
76
This is just the Output column repeated. Replace it with the numbered decision steps.
77
78
### Mistake 2: Missing the decision branches
79
80
> ~~"1. Calculate bonus using sales × bonus percentage."~~
81
82
This ignores the condition. If there is a threshold or an IF in the logic, both branches must appear in the Process column.
83
84
### Mistake 3: Inputs not traced to diagrams
85
86
Your inputs should be data flows you have already documented in a context diagram or DFD. If an input appears in your IPO chart but nowhere in your diagrams, that is a consistency problem the marker will notice.
87
88
### Mistake 4: One IPO chart for everything
89
90
Write one chart per functional requirement. Each requirement has its own inputs, its own logic and its own output — cramming multiple requirements into one chart makes the Process column vague by design.
91
92
---
93
94
## Check Your Understanding
95
96
1. A student writes Process = "display the total price". What is wrong with this, and how should they fix it?
97
98
>| **Answer:** "Display the total price" is an outcome — it names the output, not the steps. The student should replace it with numbered operations: e.g. 1. Retrieve unit price and quantity. 2. Multiply unit price × quantity to get subtotal. 3. Add GST (subtotal × 0.10). 4. Display the result. The Process column must show the *how*, not the *what*.
99
100
2. Where should the inputs listed in your IPO chart already appear in your design documentation?
101
102
>| **Answer:** In your context diagram or data flow diagram. Inputs are data flows entering the system or a process — they should already be named and labelled in those diagrams. If an input appears in the IPO chart but not in any diagram, there is a consistency error to fix.
103
104
3. You have a functional requirement with a condition: "if the score is 50 or above, the student passes; otherwise they fail." How many branches should appear in your Process column?
105
106
>| **Answer:** Two branches. 1. Check if score ≥ 50. 2. If true, result = "Pass". 3. If false, result = "Fail". Both outcomes of the condition must be shown — leaving out the false branch means the algorithm is incomplete.
107
108
---
109
110
## See also
111
112
- [VCAA Pseudocode — Not Python](/sd/C05/VCAA%20Pseudocode%20Not%20Python)
113
- [Data Dictionary — Format is not Type](/sd/C05/Data%20Dictionary%20-%20Format%20is%20not%20Type)
114
- [Connect the Dots](/sd/C05/Connect%20the%20Dots)
115
116
← Back to [C05 Home](/sd/C05/C05-home) · [VCE Software Development Hub](/sd/VCE%20Software%20Development%20Hub)