Evaluating your own solution

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

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

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

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

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

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

Match the Pairs

Draw a line connecting each item on the left to its match on the right.

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

Definitions

evaluate

Fill in the Blanks

Complete each line of code by filling in the missing parts.

___ the user to try the solution

IF the button works THEN SET result ← "pass" ____ SET result ← "problem"

SET ________ ← 0 IF the test fails THEN CHANGE problems BY 1

SET score ← 3 IF score _ 5 THEN SET next_step ← "improve"

IF problems > 0 THEN ____ every problem to the user

Spot the Error

Shade in the letter of the line that contains an error.

Question 1

A Ignore the requirements list

B Test each requirement

C Mark each one pass or fail

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

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

Question 4

A SET passed ← 0

B REPEAT for each requirement

C IF pass: passed ← passed - 1

D SHOW the passed count

Question 5

A Only test it by yourself

B Note what each user says

C Look for problems that repeat

Answer Key

Evaluating your own solution

Section A: Quick Questions

A — Test it against the requirements and ask a user to try it

B — Ask a classmate to try it while you watch

A — Write down that this requirement is not met

A — Decide to make the buttons bigger and test again

B — It meets 4 of the 5 requirements, but the timer sometimes freezes

Section B: 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

Section C: Definitions

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.

Section D: Fill in the Blanks

ASK the user to try the solution

IF the button works THEN
  SET result ← "pass"
ELSE SET result ← "problem"

SET problems ← 0
IF the test fails THEN
  CHANGE problems BY 1

SET score ← 3
IF score < 5 THEN
  SET next_step ← "improve"

IF problems > 0 THEN
  SHOW every problem to the user

Section E: Spot the Error

A — You evaluate by testing against the requirements, so you must read the requirements list first, not ignore it.

D — Being honest means using all the feedback to decide what to change next. You should not ignore feedback you dislike.

B — The problem list is for things that do not work. The condition should be IF button does not work THEN.

C — Each passed requirement should add 1 to the count. It should be passed + 1, not passed - 1.

A — Evaluating means asking other users to try it. They notice problems the maker misses. Line 1 should ask users to try it.