Home A - Z
Page Index

An Otter Wiki

Blame

f049b1 lisa 2026-04-27 20:07:44
Add C02 Data Collection Methods wiki page Covers the four VCE SD methods: interview, survey, observation, reports/existing data. Adapted from EDUCBA overview with project- specific framing (file-naming, save formats, common pitfalls per method, recommended 3-method mix). Uses OtterWiki folded blocks for real-world examples and fancy info/ success/warning panels for callouts. Comparison table at top serves as the dual-coding visual anchor.
1 
> **DRAFT** — under teacher review.
2
3
# Data Collection Methods
4
5
Hamilton College · Year 12 · 2026
6
7
For C02 you must collect data using **at least three different methods** and explain *why* you chose each one. This page covers the four methods VCE Software Development recognises — what they are, when each works best, and how to use them in your SAT project.
8
9
The C2-1 rubric rewards **specific, justified method choice** at the 9–10 band. Picking interviews "because everyone uses interviews" will not score. Picking interviews "because I needed depth on three users' workflows that a survey couldn't capture" will.
10
11
---
12
5c916b lisa 2026-04-27 20:12:13
Data Collection Methods: add Primary/Secondary diagram + AI examples - Embed Data-Collection-Methods.png (primary vs secondary families) at the top, with a short framing of which 4 we use for VCE SD. - Replace COVID-era real-world examples with current AI-related ones: teachers + ChatGPT (interview), Pew 2024 AI adoption (survey), and GitHub's Copilot productivity study (observation).
13
## The big picture
14
15
![Data collection methods — primary and secondary](Data%20Collection%20Methods/Data-Collection-Methods.png)
16
17
Researchers split data collection into two families:
18
19
- **Primary** — data *you* collect, first-hand: surveys, interviews, observations, experiments.
20
- **Secondary** — data *someone else already collected*, repurposed for your question: literature reviews, government databases, commercial databases, web data.
21
22
For your VCE SD project we use **four** of these — surveys, interviews, observations, and the secondary group bundled together as **reports / existing data**. (Experiments are not a standard SAT method — your project is software design, not scientific research.)
23
24
---
25
f049b1 lisa 2026-04-27 20:07:44
Add C02 Data Collection Methods wiki page Covers the four VCE SD methods: interview, survey, observation, reports/existing data. Adapted from EDUCBA overview with project- specific framing (file-naming, save formats, common pitfalls per method, recommended 3-method mix). Uses OtterWiki folded blocks for real-world examples and fancy info/ success/warning panels for callouts. Comparison table at top serves as the dual-coding visual anchor.
26
## The four methods at a glance
27
28
| Method | Best for | Data type | Time cost | Save raw to |
29
|---|---|---|---|---|
30
| **Interview** | Depth, motivations, follow-up questions | Mostly qualitative | High (per person) | `C02/raw/interview-<name>-<date>.md` |
31
| **Survey** | Breadth, countable patterns across many people | Mostly quantitative + some qualitative | Low (per response) | `C02/raw/survey-results.csv` |
32
| **Observation** | What people *actually* do (vs what they say) | Mostly qualitative | Medium | `C02/raw/observation-<context>-<date>.md` |
33
| **Reports / existing data** | Context, constraints, technical environment | Mixed | Low | `C02/raw/report-<topic>.md` |
34
35
A strong project usually combines: **1 method for depth** (interview), **1 for breadth** (survey), and **1 for grounding** (observation or reports).
36
37
---
38
39
## 1. Interview
40
41
::: info
42
**What it is** — A structured or semi-structured conversation between you and one person (your client, a target user, an expert). You ask predetermined questions but follow up on interesting answers.
43
:::
44
45
**When to use it.** When you need *depth* — understanding why someone does something, what frustrates them, or what they would value most. Best for the first 1–3 stakeholders, before you know enough to design a survey.
46
47
**Strengths**
48
49
- Lets you ask follow-up questions and clarify confusing answers
50
- Captures rich detail and personal context a survey can't reach
51
- Adapts on the fly — you can probe an unexpected response
52
53
**Weaknesses**
54
55
- Slow — a serious interview is 20–45 minutes per person, plus prep and writing it up
56
- Your wording, body language, and tone affect what people say (interviewer bias)
57
- Hard to keep two interviews directly comparable
58
59
**In your project**
60
61
- Capture **key points and direct quotes**, not full transcripts. A short bulleted note file is enough.
62
- After each interview, write a 2-line summary of "biggest insight" and "thing I didn't expect" — these often become your strongest poster content.
63
- Plan **2–4 interviews**, not 10. The C2-1 rubric rewards depth of analysis, not interview count.
64
65
>| ### Real-world example
5c916b lisa 2026-04-27 20:12:13
Data Collection Methods: add Primary/Secondary diagram + AI examples - Embed Data-Collection-Methods.png (primary vs secondary families) at the top, with a short framing of which 4 we use for VCE SD. - Replace COVID-era real-world examples with current AI-related ones: teachers + ChatGPT (interview), Pew 2024 AI adoption (survey), and GitHub's Copilot productivity study (observation).
66
>| In 2024, university researchers interviewed teachers about how they use ChatGPT in lesson planning. The interviews revealed something a survey would have missed: most teachers used the tool to **draft rubrics and generate question variants**, not to write lesson content directly. They distrusted AI for content but trusted it for structure — a nuance that only emerged when interviewers asked follow-up questions like *"can you walk me through the last time you used it?"*
f049b1 lisa 2026-04-27 20:07:44
Add C02 Data Collection Methods wiki page Covers the four VCE SD methods: interview, survey, observation, reports/existing data. Adapted from EDUCBA overview with project- specific framing (file-naming, save formats, common pitfalls per method, recommended 3-method mix). Uses OtterWiki folded blocks for real-world examples and fancy info/ success/warning panels for callouts. Comparison table at top serves as the dual-coding visual anchor.
67
68
---
69
70
## 2. Survey
71
72
::: info
73
**What it is** — A short questionnaire (Google Forms, Microsoft Forms, etc.) sent to many people. Mostly **closed-ended** questions (multiple choice, scales) so you can count results; one or two **open-ended** for texture.
74
:::
75
76
**When to use it.** When you need *breadth* — to test whether something you heard in an interview is widely true, or to count preferences across a target user group.
77
78
**Strengths**
79
80
- Cheap and fast per response
81
- Reaches many people who would never agree to an interview
82
- Quantitative results are easy to summarise on a poster ("78% of Year 9 students said…")
83
84
**Weaknesses**
85
86
- People misread or skip questions you thought were clear (ambiguity = bias)
87
- You only get answers to the questions you asked — no follow-up
88
- Self-report; what people *say* they do is often not what they *actually* do
89
90
**In your project**
91
92
- Keep it short. **5–10 questions**, max 5 minutes to complete, or response rate collapses.
93
- Mix **closed** (countable) with **1–2 open** (texture) questions.
94
- Pilot it with 1–2 people before sending widely — you will catch ambiguous wording every time.
95
- Save the **raw CSV export**, not just a summary screenshot.
96
97
>| ### Real-world example
5c916b lisa 2026-04-27 20:12:13
Data Collection Methods: add Primary/Secondary diagram + AI examples - Embed Data-Collection-Methods.png (primary vs secondary families) at the top, with a short framing of which 4 we use for VCE SD. - Replace COVID-era real-world examples with current AI-related ones: teachers + ChatGPT (interview), Pew 2024 AI adoption (survey), and GitHub's Copilot productivity study (observation).
98
>| Pew Research's 2024 survey of US adults on AI tools reached over 11,000 respondents in a few weeks. They found roughly **1 in 4 adults had used ChatGPT**, with usage skewed strongly to younger and more-educated demographics. That kind of demographic spread can only be established by surveys — interviewing 11,000 people would take years.
f049b1 lisa 2026-04-27 20:07:44
Add C02 Data Collection Methods wiki page Covers the four VCE SD methods: interview, survey, observation, reports/existing data. Adapted from EDUCBA overview with project- specific framing (file-naming, save formats, common pitfalls per method, recommended 3-method mix). Uses OtterWiki folded blocks for real-world examples and fancy info/ success/warning panels for callouts. Comparison table at top serves as the dual-coding visual anchor.
99
100
---
101
102
## 3. Observation
103
104
::: info
105
**What it is** — Watching real people do the task your software will eventually replace or support. You note what works, what frustrates them, and what they do that contradicts what they told you in interview.
106
:::
107
108
**When to use it.** When you want to know what people *do*, not just what they *say* they do — these are usually different. Especially powerful for workflows people perform so often they no longer notice the friction.
109
110
**Strengths**
111
112
- Captures real behaviour in context
113
- Catches workarounds and unspoken steps people forget to mention
114
- Cuts through self-report bias — what you observe happened
115
116
**Weaknesses**
117
118
- Time-consuming; you usually need multiple sessions to spot patterns
119
- People behave differently when watched (observer effect)
120
- You can only see external behaviour, not motivation
121
122
**In your project**
123
124
- **Participant** observation: you join in (e.g. shadow a teacher running the canteen). **Non-participant**: you watch from the side (e.g. observe a library queue at lunch).
125
- Note **specific moments**, not generalities. "*At 12:47, a student gave up looking for the book and asked the librarian instead*" beats "*it took a while to find books*".
126
- Cross-check observations against interview claims. Contradictions are gold for your poster's *"explaining why"* section.
127
128
>| ### Real-world example
5c916b lisa 2026-04-27 20:12:13
Data Collection Methods: add Primary/Secondary diagram + AI examples - Embed Data-Collection-Methods.png (primary vs secondary families) at the top, with a short framing of which 4 we use for VCE SD. - Replace COVID-era real-world examples with current AI-related ones: teachers + ChatGPT (interview), Pew 2024 AI adoption (survey), and GitHub's Copilot productivity study (observation).
129
>| GitHub's 2023 controlled study observed developers completing the same coding task with and without GitHub Copilot (an AI coding assistant). Developers using Copilot finished **about 55% faster** on average — a number self-reports would have understated, because developers using AI assistants often *feel* slower (the tool interrupts their flow) even when measurement shows they're producing more working code.
f049b1 lisa 2026-04-27 20:07:44
Add C02 Data Collection Methods wiki page Covers the four VCE SD methods: interview, survey, observation, reports/existing data. Adapted from EDUCBA overview with project- specific framing (file-naming, save formats, common pitfalls per method, recommended 3-method mix). Uses OtterWiki folded blocks for real-world examples and fancy info/ success/warning panels for callouts. Comparison table at top serves as the dual-coding visual anchor.
130
131
---
132
133
## 4. Reports / existing data
134
135
::: info
136
**What it is** — Information that already exists, collected by someone else for some other purpose. Includes school policy documents, government statistics, industry reports, your school's IT device list, academic studies, and existing software documentation.
137
:::
138
139
**When to use it.** When you need to ground your project in **real constraints** — the technical environment, the regulatory environment, or population statistics that would take you months to collect yourself.
140
141
**Strengths**
142
143
- Free or cheap; you didn't pay to collect it
144
- Often covers populations or time spans you could never access yourself
145
- Excellent for the rubric's *constraints* and *technical environment* categories — areas students often have nothing to say about
146
147
**Weaknesses**
148
149
- Was collected for someone else's question, not yours — may not exactly fit
150
- Quality varies; you must judge the source
151
- Can be out of date (especially anything pre-2023)
152
153
**In your project**
154
155
- For *technical environment*: your school's IT device list, browser stats, OS versions, network policy.
156
- For *constraints*: school policy on student data, age-appropriate design code (UK ICO), accessibility guidelines (WCAG).
157
- For *user characteristics*: ABS census data, government education statistics, your school's enrolment breakdown.
158
- Always save **the source link plus your own one-paragraph summary** — examiners want to see you read it, not just cited it.
159
160
**Sub-types worth knowing**
161
162
- **Literature review** — academic papers, textbooks, OER like this wiki
163
- **Government databases** — ABS, Department of Education, ACMA
164
- **Industry reports** — Statista, Gartner, vendor white papers
165
- **Web data** — public APIs, open datasets (data.gov.au)
166
167
---
168
169
## Choosing your mix
170
171
For C02 you must use **three or more** methods. A balanced mix:
172
173
::: success
174
**Recommended pattern**
175
176
- **1 interview** with your client or primary user → depth, motivation, must-have features
177
- **1 survey** of target users → breadth, validation of interview claims
178
- **1 observation OR report set** → grounding in real behaviour or constraints
179
:::
180
181
::: warning
182
**Avoid these traps**
183
184
- **Three interviews and nothing else** — no breadth, no constraints, no observed behaviour. Caps at 6–7 on C2-1.
185
- **A survey of one class with no interviews** — no depth, no rationale beyond "*it was easy*".
186
- **Reports only** — you've researched the area but haven't engaged with real users; the rubric's *user characteristics* section will be weak.
187
:::
188
189
The 9–10 descriptor expects you to **explain why each method was chosen for its specific job** — what data it would yield that the others wouldn't. Practise that explanation out loud before your C2-1 station defence.
190
191
---
192
193
## See also
194
195
- [Essential Terms](Essential%20Terms.md) — definitions of *qualitative*, *quantitative*, *open-ended*, *close-ended*, and the four method names
196
- [Explaining vs Describing Your Data Collection](Explaining%20vs%20Describing%20Your%20Data%20Collection.md) — the verb ladder the C2-1 rubric uses to separate 7 from 9–10
197
- [Context Diagram](Context%20Diagram.md) — once you have data, the entities you discovered go on this diagram
198
- [What Is an Entity](What%20Is%20an%20Entity.md) — your data sources may themselves be entities (e.g. a payment gateway, an LMS)
199
200
---
201
202
*Adapted for VCE SD students from EDUCBA's [Data Collection Methods](https://www.educba.com/data-collection-methods/) overview, with project-specific framing for C02.*