Tip: Choose Save as PDF in the print dialog to download. Use A4 paper size.
Shade in the A or B circle for each question.
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1evaluate | ATo judge how well a system meets a user's need by checking it against criteria and giving a reason with evidence | |
| 2criteria: easy to use, quick, reliable | BThe rating does not say which criterion it is for, so we can't tell what was judged. | |
| 3Rate a criterion and give a reason with evidence | CQuick: 4/5 - it loaded in 3 seconds | |
| 4Use a success criterion to check if the system meets the user's need | DNeed: read the bus times. Easy to use? Yes | |
| 5Reliable: 5/5 - I just like it | EThe checklist of things we use to judge whether a system meets the user's need | |
| 6Rating: 4/5 (no criterion named) | FThe reason is an opinion. It gives no evidence, such as how often the app worked without crashing. |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
evaluate — To judge how well a system meets a user's need by checking it against criteria like easy to use, quick and reliable, then rating each one and giving a reason with evidence.result ← evaluate(system, need)criteria ← [easy, quick, reliable]criterion ← "reliable"
rating ← 2
OUTPUT ratingevidence ← "Crashed 3 times in 10 tries"
OUTPUT evidenceIF rating ≥ 4 THEN
OUTPUT "Meets the need"
ELSE OUTPUT "Needs improving"