← VCE Software Development U4O1

Evaluation strategy: responsibility

The part of an evaluation strategy that names who collects the data and who judges each criterion, so every task has a clear owner.

Part of: VCE Software Development - U4O1 - development and evaluation — Module 178

Understanding Evaluation strategy: responsibility in VCE Software Development U4O1

What it does: This shows the collector and the evaluator named separately, so each task has a clear owner. A named role is linked to the criterion, so it is clear who is accountable for collecting and judging. Responsibility names the people involved. The time frame covers when the evaluation happens. If nobody owns a task, it may be forgotten or done twice. Responsibility can be split. A tester may gather results while the client or developer judges them. A good entry names a specific person or role, and says whether they collect or judge. The beta testers collect the data. The developer judges it against the criterion.

Common mistakes: A dictionary holding who collects data and who judges is created with a single = for assignment. == compares values and causes an error here. It should be strategy = {. The person who judges the criterion is text, so it must be in quotes. Without quotes Python looks for a variable called Client and gives a NameError. It should be judge = "Client".

Class: _____________________  ·  Name: _____________________  ·  Date: _________

Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.

🖨 Print worksheet + answer key Add Evaluation strategy: responsibility to a class →

This module's key terms are also in a printable crossword (Modules 172–182) and word search (Modules 172–198).

Take this worksheet further — free with Cloodit

Each concept is reinforced from every angle — learned, then applied, then tested.

Learning
Duo
In an evaluation strategy, what does the responsibility part state?
Who collects the data and who judges each criterionHow long the evaluation will take to finish
Matches
Responsibility: Everyone will check it somehow
↓
Responsibility is vague. It names no specific person or role, so no one clearly owns collecting the data or judging the criterion.
Applying
Meanings
Term
responsibility
Meaning
The part of an evaluation strategy that names who collects the data and who judges each criterion, so every task has a clear owner.
Practice
Criterion: Report loads in under 3 seconds
Testing
Gaps
= "Sam"
Check Answer
Spots
1strategy = {
2strategy == {

Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.

The 'Firefly' badge — Night Coder, one of Cloodit's 106 collectible badges
Students earn collectable badges

Over 100 of them, across seven natural biomes.

Study Buddy
Students build a real study resource

Turns their work into revision material ready for Flash Cards and Exam study.

Diamond Dash — one of Cloodit's live, competitive Sprint games
Students lock in with Sprints

Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.

A Cloodit certificate of achievement, ready to personalise and print
Custom printable certificates

Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.

Add to class →

Quick Questions

1. In an evaluation strategy, what does the responsibility part state?
A. How long the evaluation will take to finish
B. Who collects the data and who judges each criterion ✓
Responsibility names the people involved. The time frame covers when the evaluation happens.
2. Which entry is a clear responsibility for the criterion 'The program runs in under 2 seconds'?
A. Priya times 5 runs; the project manager judges the results ✓
B. The program will be timed during Term 3
A responsibility names a person or role. 'During Term 3' is a time frame, not a person.
3. Why do strategies name who collects data for each criterion?
A. So every data collection task has a clear owner and is not missed ✓
B. So the data can be collected without any methods
If nobody owns a task, it may be forgotten or done twice.
4. Which sentence describes the 'who evaluates' sub-theme?
A. The client decides if the data shows the criterion was met ✓
B. The tester writes down each run time in a table
Evaluating is judging the data against the criterion. Writing down the times is collecting data.
5. Can the person who collects the data be different from the person who evaluates it?
A. No, one person must always do both jobs
B. Yes, for example a tester collects and the client judges ✓
Responsibility can be split. A tester may gather results while the client or developer judges them.

Match the Pairs

Responsibility: Dev team collects load times → Names who collects the data for a criterion, so the measuring task has a clear owner
Responsibility: Client judges if the outputs are correct → Names who evaluates the results and decides whether the criterion has been met
Responsibility can split the work: one person collects the data and a different person judges it → Responsibility: Tester records error counts; project manager judges against the criterion
Responsibility should name a specific person or role for each criterion, not just 'everyone' → Criterion 2 Responsibility: Lead developer measures and evaluates response time
Responsibility: Everyone will check it somehow → Responsibility is vague. It names no specific person or role, so no one clearly owns collecting the data or judging the criterion.
Responsibility: Developer collects the data (no one named to judge it) → Only who collects the data is stated. It does not say who evaluates the data against the criterion.

Key Term

responsibility
The part of an evaluation strategy that names who collects the data and who judges each criterion, so every task has a clear owner.

Fill in the Blanks

1. collector = "Mia" judge = "Sam"
Hint: Type the variable name that stores the person who judges the criterion.
2. collector = "Mia" judge = "Sam" print("Data collected by", collector)
Hint: Type the variable name that stores the person who gathers the data.
3. owner = {"collect": "Mia", "judge": "Sam"} print(owner["judge"])
Hint: Type the dictionary key, without the quote marks, for the person who decides if the criterion is met.
4. judge = "" if judge == "": print("No owner for this criterion!")
Hint: Type the comparison operator that checks whether the judge's name is empty.
5. def showowner(collector, judge): print("Collects:", collector) print("Judges:", judge)
Hint: Type the keyword that starts a function definition.

Spot the Error

Question 1
A strategy = {
B strategy == {
C "collects": "Tester",
D "judges": "Client"
E }
Line B — A dictionary holding who collects data and who judges is created with a single = for assignment. == compares values and causes an error here. It should be strategy = {.
Question 2
A criterion = "Search under 2 sec"
B collector = "Tester"
C judge = Client
D print("Collects:", collector)
E print("Judges:", judge)
Line C — The person who judges the criterion is text, so it must be in quotes. Without quotes Python looks for a variable called Client and gives a NameError. It should be judge = "Client".
Question 3
A responsibility = []
B responsibility["collect"] = "QA"
C responsibility["judge"] = "Client"
Line A — Roles such as collect and judge are stored by name, so a dictionary is needed. A list cannot take a string key and causes a TypeError. It should be responsibility = {}.
Question 4
A tasks = ["Survey", "Timing"]
B owners = ["Tester", "Dev"]
C for i in range(len(tasks)):
D print(tasks[i], owners[i+1])
Line D — Each task must be paired with its own owner at the same index. owners[i+1] shows the wrong owner and runs off the end of the list on the last task. It should be owners[i].
Question 5
A collector = "Beta tester"
B evaluator = "Project manager'
C if collector == evaluator:
D print("Check for bias")
Line B — The string starts with a double quote but ends with a single quote, so it is never closed. It should end with a double quote: evaluator = "Project manager".

Student with a class code? Join your class →