Evaluating an existing digital solution

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. Which is the best way to start evaluating a school library app?

A Look at the colours and decide if you like them

B Use it the way a student would, then compare it with the requirements

2. The requirement says: 'Students can search for a book by title.' You type a title and the right book appears. What does this show?

A This requirement is missing

B This requirement works well

3. The requirements say: 'Show if a book is borrowed.' You test the app and find no borrowed information at all. What do you record?

A What is missing: borrowed status is not shown

B What works well: borrowed status is shown

4. Who should you think like when you test a solution?

A The person who will use it

B The person who made it

5. What do you compare the solution with when you evaluate it?

A The requirements

B Your favourite game

Match the Pairs

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

Left column		Right column
1evaluate		ATo test a solution the way its user would, then compare what it does with the requirements
2requirement: Show the score		BRequirement: Add a name. Test: typed 'Mia' and it saved. Result: works well
3What works well: a requirement the solution meets when tested as a user		CRequirement: Undo a mistake. Test: looked for an undo button. Result: missing
4What is missing: a requirement the solution does not meet when tested		DThe evaluation did not compare the solution with the requirements. Personal opinion alone does not show what works or what is missing.
5Evaluation: I read the code and it looks fine, so it works.		EA check to make when evaluating: does the solution do this? Tick it as 'works well' or note it as 'missing'
6Evaluation: The app has bright colours and I like it. Done!		FThe solution was not tested as its user would. Reading it is not enough; you need to use it and try the tasks.

Definitions

evaluate

Fill in the Blanks

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

________ app: test as user, compare

IF app meets requirement ____ PRINT "What works well" ELSE PRINT "What is missing"

IF app meets requirement THEN PRINT "Works well" ____ PRINT "Missing: needs a fix"

requirement ← "Show the score" result ← "Score is not shown" IF ______ ≠ requirement THEN PRINT "Missing"

requirement ← "Show the score" result ← "Score is shown" IF result _ requirement THEN PRINT "Works"

Spot the Error

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

Question 1

A FOR each requirement

B Test it as the user would

C IF it meets the need THEN

D Add to missing list

E ELSE Add to missing list

Question 2

A Guess how the app works

B Compare it to the requirements

C List what works well

D List what is missing

Question 3

A requirement: Save a score

B Test: play and press Save

C Result: score is saved

D Judgement: missing

Question 4

A requirement: Show the time

B Test: read the code only

C Result: time is shown

D Judgement: works well

Question 5

A requirement: Sound on click

B Test: click the button

C Result: sound plays

D Judgement: missing

Answer Key

Evaluating an existing digital solution

Section A: Quick Questions

B — Use it the way a student would, then compare it with the requirements

B — This requirement works well

A — What is missing: borrowed status is not shown

A — The person who will use it

A — The requirements

Section B: Match the Pairs

evaluate → To test a solution the way its user would, then compare what it does with the requirements

requirement: Show the score → A check to make when evaluating: does the solution do this? Tick it as 'works well' or note it as 'missing'

What works well: a requirement the solution meets when tested as a user → Requirement: Add a name. Test: typed 'Mia' and it saved. Result: works well

What is missing: a requirement the solution does not meet when tested → Requirement: Undo a mistake. Test: looked for an undo button. Result: missing

Evaluation: I read the code and it looks fine, so it works. → The solution was not tested as its user would. Reading it is not enough; you need to use it and try the tasks.

Evaluation: The app has bright colours and I like it. Done! → The evaluation did not compare the solution with the requirements. Personal opinion alone does not show what works or what is missing.

Section C: Definitions

evaluate — To test a solution the way its user would, then compare what it does with the requirements to find what works well and what is missing.

Section D: Fill in the Blanks

evaluate app: test as user, compare

IF app meets requirement THEN
  PRINT "What works well"
ELSE PRINT "What is missing"

IF app meets requirement THEN
  PRINT "Works well"
ELSE PRINT "Missing: needs a fix"

requirement ← "Show the score"
result ← "Score is not shown"
IF result ≠ requirement THEN PRINT "Missing"

requirement ← "Show the score"
result ← "Score is shown"
IF result = requirement THEN PRINT "Works"

Section E: Spot the Error

D — When the solution meets the need, it belongs in the works well list. It should say 'Add to works well list', not 'Add to missing list'.

A — To evaluate a solution you must test it the way its user would, not guess. Line 1 should be 'Test the app as its user would'.

D — The score was saved, so the requirement is met. The judgement should be 'works well', not 'missing'.

B — An evaluation tests the solution as its user would, by opening and using the app. Reading only the code is not a user test. It should be 'Test: open the app, look'.

C — The judgement says the sound is missing, so the result must report that no sound plays. The result should be 'Result: no sound plays'.