← Years 5–6 Creating Digital Solutions

Evaluating your own solution

To check how well your solution works by testing it against the requirements, asking users to try it, and deciding what to improve. Be honest about any problems.

Part of: 5-6 Digital Technologies Vic Curric - Creating Digital Solutions — Module 72, 7-8 Digital Technologies: Sharing online and managing projects — Module 13, 7-8 Digital Technologies: Evaluating digital solutions — Module 5, 9-10 Digital Technologies: Evaluating solutions, impact and innovation — Module 5, QCE Digital Solutions Unit 2 — Prototype Data Solutions — Module 128

Understanding Evaluating your own solution in Years 5–6 Creating Digital Solutions

What it does: Checking each requirement one by one and recording the result is how you test a solution against what it was meant to do. Evaluation ends with a clear decision about what to improve, based on the problems found. Other people can find problems you did not notice because you already know how your solution works. Feedback helps you decide what to change next. Then you test again to check that the change worked. An honest evaluation says what works and what does not, using the requirements to check. If you give all the instructions, you will not see where real users get stuck.

Common mistakes: You evaluate by testing against the requirements, so you must read the requirements list first, not ignore it. Being honest means using all the feedback to decide what to change next. You should not ignore feedback you dislike.

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 Evaluating your own solution to a class →

This module's key terms are also in a printable crossword (Modules 61–74) and word search (Modules 41–74).

Take this worksheet further — free with Cloodit

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

Learning
Duo
You have finished your quiz app. What is a good way to evaluate it?
Decide it is perfect because you built itTest it against the requirements and ask a user to try it
Matches
Only the creator tests it. Result: Everything works perfectly!
↓
The creator did not ask any users to try it, so problems that other people would find were missed
Applying
Meanings
Term
evaluate
Meaning
To check how well your solution works by testing it against the requirements, asking users to try it, and deciding what to improve. Be honest about any problems.
Practice
EVALUATE my solution
Testing
Gaps
the user to try the solution
Check Answer
Spots
1Ignore the requirements list
2Test each requirement

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

The 'Kangaroo Rat' badge — Speed Typer, 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. You have finished your quiz app. What is a good way to evaluate it?
A. Test it against the requirements and ask a user to try it ✓
B. Decide it is perfect because you built it
Evaluating means checking how well your solution works. You test it against the requirements and get feedback from real users.
2. Which is the best way to get feedback on your solution?
A. Only test it yourself over and over
B. Ask a classmate to try it while you watch ✓
Other people can find problems you did not notice because you already know how your solution works.
3. Your game was meant to show the score after each round, but it does not. What should you do?
A. Write down that this requirement is not met ✓
B. Leave it out of your evaluation so it looks better
Being honest about problems is part of evaluating. You need to know what is not working before you can fix it.
4. A user says your buttons are too small to tap. What is the best next step?
A. Decide to make the buttons bigger and test again ✓
B. Tell the user they are wrong and change nothing
Feedback helps you decide what to change next. Then you test again to check that the change worked.
5. Which sentence is an honest evaluation?
A. It works great and has no problems at all
B. It meets 4 of the 5 requirements, but the timer sometimes freezes ✓
An honest evaluation says what works and what does not, using the requirements to check.

Match the Pairs

evaluate → Check how well your solution works by testing it against the requirements and asking users for feedback
user feedback → What people say after they try your solution, such as what was easy, confusing or missing
Test your solution against each requirement and record whether it passed → Requirement: Score shows on screen -> Pass
Decide what to change next after seeing the feedback → Next step: make the buttons bigger
Only the creator tests it. Result: Everything works perfectly! → The creator did not ask any users to try it, so problems that other people would find were missed
Problem found: the timer is too fast. Notes: Not worth mentioning. → The problem was hidden instead of being honest about it, so it will never be fixed

Key Term

evaluate
To check how well your solution works by testing it against the requirements, asking users to try it, and deciding what to improve. Be honest about any problems.

Fill in the Blanks

1. ASK the user to try the solution
Hint: Type the command word for getting a user to try your solution and give feedback
2. IF the button works THEN SET result ← "pass" ELSE SET result ← "problem"
Hint: Type the keyword for what happens when the test does not pass
3. SET problems ← 0 IF the test fails THEN CHANGE problems BY 1
Hint: Type the name of the variable that counts the problems you find
4. SET score ← 3 IF score < 5 THEN SET next_step ← "improve"
Hint: Type the comparison operator that checks if the score is below the target
5. IF problems > 0 THEN SHOW every problem to the user
Hint: Type the command word that displays the problems honestly instead of hiding them

Spot the Error

Question 1
A Ignore the requirements list
B Test each requirement
C Mark each one pass or fail
Line A — You evaluate by testing against the requirements, so you must read the requirements list first, not ignore it.
Question 2
A Ask a user to try the app
B Watch what they do
C Write down their feedback
D Ignore feedback you dislike
Line D — Being honest means using all the feedback to decide what to change next. You should not ignore feedback you dislike.
Question 3
A Test the quiz app
B IF button works THEN
C Add it to the problem list
D Be honest in your report
Line B — The problem list is for things that do not work. The condition should be IF button does not work THEN.
Question 4
A SET passed ← 0
B REPEAT for each requirement
C IF pass: passed ← passed - 1
D SHOW the passed count
Line C — Each passed requirement should add 1 to the count. It should be passed + 1, not passed - 1.
Question 5
A Only test it by yourself
B Note what each user says
C Look for problems that repeat
Line A — Evaluating means asking other users to try it. They notice problems the maker misses. Line 1 should ask users to try it.

Student with a class code? Join your class →