← VCE Software Development U4O1

Modifying and refining evaluation criteria

Review and reword evaluation criteria as the solution develops, so they stay measurable and relevant, such as making vague wording specific or updating them after changes.

Understanding Modifying and refining evaluation criteria in VCE Software Development U4O1

What it does: The reworded version has a percentage and a count, so the evaluator can collect data and judge whether it was met. A criterion about a feature that no longer exists is not relevant. Reviewing and updating the criteria removes or replaces it. Vague wording cannot be measured. Refining the criterion adds a specific, testable target. Criteria are reviewed and refined during development. They are not fixed forever. Update criteria after changes so they still match the solution you are evaluating. The first has a clear number that can be measured. 'Easy to use' is a matter of opinion. Refining makes criteria measurable. Length and style do not matter.

Common mistakes: A refined criterion must be measurable. 'Loads quickly' is still vague. It should give a specific target such as 'Page loads in <= 2 s'. Rewording an unclear criterion should add a measurable value. 'A small amount' is vague. It should state a limit such as 'Uses < 50 MB of memory'.

Class: _____________________  ·  Name: _____________________  ·  Date: _________

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

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
A criterion says 'The program should run fast.' How should it be refined?
Leave it as it is, because fast is clear enough to judge.Reword it to be measurable: 'Search results display in under 2 seconds with 500 records.'
Matches
Refined criterion: "The program should run quite quickly"
↓
The refined wording is still vague. 'Quite quickly' has no measurable target such as a time limit, so it cannot be judged.
Applying
Meanings
Term
refine evaluation criteria
Meaning
Review and reword evaluation criteria as the solution develops, so they stay measurable and relevant, such as making vague wording specific or updating them after changes.
Practice
Original: The app should be fast.
Testing
Gaps
criteria.("Error rate is below 2%")
Check Answer
Spots
1Revised: Page loads quickly
2Reason: old wording was vague

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

The 'Flamingo' badge — Balanced 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.

Quick Questions

1. A criterion says 'The program should run fast.' How should it be refined?
A. Leave it as it is, because fast is clear enough to judge.
B. Reword it to be measurable: 'Search results display in under 2 seconds with 500 records.' ✓
Vague wording cannot be measured. Refining the criterion adds a specific, testable target.
2. When should evaluation criteria be reviewed?
A. As the solution develops, so they stay relevant to what is being built. ✓
B. Only once, before any development starts, and then never again.
Criteria are reviewed and refined during development. They are not fixed forever.
3. The client adds a new feature to the app part-way through development. What should happen to the criteria?
A. Keep the original criteria and ignore the new feature.
B. Update the criteria to cover the new feature. ✓
Update criteria after changes so they still match the solution you are evaluating.
4. Which criterion is better after being reworded?
A. 'At least 90% of beta testers can add a task without help.' ✓
B. 'The app should be easy to use.'
The first has a clear number that can be measured. 'Easy to use' is a matter of opinion.
5. Why do we refine unclear evaluation criteria?
A. So the solution can be judged using evidence, such as numbers or yes/no results. ✓
B. So the criteria are longer and sound more professional.
Refining makes criteria measurable. Length and style do not matter.

Match the Pairs

Old: "The app should be fast" → New: "The report loads in under 2 seconds" → Rewording a vague criterion so it becomes specific and measurable
Criterion updated after the client added a search feature: "Search returns results in under 3 seconds" → Updating the criteria after a change so they stay relevant to the solution
A criterion that is too vague should be reworded with a measurable target → "Easy to use" → "90% of testers finish a booking in under 3 clicks"
Criteria must be reviewed as the solution develops so they stay relevant after a change in scope → Criterion "Exports to PDF in under 5 seconds" removed after PDF export was dropped from the project
Refined criterion: "The program should run quite quickly" → The refined wording is still vague. 'Quite quickly' has no measurable target such as a time limit, so it cannot be judged.
Criteria written in week 1 and never revisited, even though the client changed the requirements in week 6 → The criteria were not updated after the changes, so they no longer match the solution being built and are no longer relevant.

Key Term

refine evaluation criteria
Review and reword evaluation criteria as the solution develops, so they stay measurable and relevant, such as making vague wording specific or updating them after changes.

Fill in the Blanks

1. criteria.append("Error rate is below 2%")
Hint: Type the list method that adds a new criterion to the end after a change to the solution.
2. criteria[0] = "Search runs in under 2 s"
Hint: Type the index of the first item, so the vague wording in that position is replaced with measurable wording.
3. criteria.remove("Looks nice")
Hint: Type the list method that deletes a criterion that can no longer be measured or is no longer relevant.
4. if actual_time <= target_time: print("Criterion met")
Hint: Type the keyword that starts a decision, checking the actual result against the measurable target.
5. for criterion in criteria: print(criterion)
Hint: Type the name of the list that holds every criterion, so each one can be reviewed in turn.

Spot the Error

Question 1
A Revised: Page loads quickly
B Reason: old wording was vague
C Measure: stopwatch on 5 trials
Line A — A refined criterion must be measurable. 'Loads quickly' is still vague. It should give a specific target such as 'Page loads in <= 2 s'.
Question 2
A Old: The app is efficient
B Problem: no number to measure
C New: Uses a small amount of RAM
Line C — Rewording an unclear criterion should add a measurable value. 'A small amount' is vague. It should state a limit such as 'Uses < 50 MB of memory'.
Question 3
A Change: login added in week 3
B Review: criteria miss login
C Action: add a login criterion
D New: Search returns in <= 1 s
Line D — After a change, the criteria must be updated to match it. The login feature was added, so the new criterion should measure login, such as 'Login succeeds in <= 3 s'.
Question 4
A criteria = {
B "load_time": "<= 2 s",
C "accuracy": ">= 98%",
D "errors": "Not many errors"
E }
Line D — 'Not many errors' cannot be measured or tested. The criterion should be refined with a number, such as '< 1 per 100 uses'.
Question 5
A 1. Review criteria each sprint
B 2. Find vague wording
C 3. Delete the criterion
D 4. Record the change
Line C — Refining means rewording unclear criteria so they are measurable, not deleting them. Step 3 should be 'Reword with a number'.

Student with a class code? Join your class →