Checking a solution against the requirements

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. You have finished a quiz app. What is the best way to check it meets the requirements?

A Test each requirement one by one and record yes or no

B Look at it quickly and say it seems fine

2. Which item belongs on a requirements checklist?

A The app should have my favourite colour

B The app must show the score at the end of the quiz

3. You tested the requirement 'The timer counts down from 30'. The timer started at 30 and reached 0. What do you record?

A Yes, and note what you saw

B No, because it was too easy to test

4. Which is the best evidence for the requirement 'The Start button begins the game'?

A A note saying 'I think it works'

B A screenshot of the game running after clicking Start

5. The requirement says 'The app must save the player's name'. When you tested it, the name disappeared. What do you record?

A No, and note that the name disappeared

B Yes, because I typed the name in

Match the Pairs

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

Left column		Right column
1Requirement 1: Score shows on screen \| Met? YES		AThe result was recorded without testing the solution, so there is no real evidence.
2Evidence: screenshot of score at 10		BRequirement: Timer counts down \| Met? NO
3Test every requirement and success criterion, one row at a time		CSome requirements were left out, so the solution was not fully checked.
4Record a no result when the solution does not meet the requirement		DA checklist row where the student tested one requirement and recorded yes because it worked
5Requirement: Quiz asks 5 questions \| Met? YES (did not test it)		EA note that shows proof of what the tester saw when checking the requirement
6Checklist: only Requirement 1 and 2 checked, 3 and 4 skipped		FRow 1: Button starts game \| Row 2: Game ends in 60 s

Definitions

requirements checklist

Fill in the Blanks

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

Requirement: Score shows on screen Test: Play the game and look at the score Result: ___ - I saw the score go up

Requirement: Game ends after 3 lives Test: Lose 3 lives Result: __ - the game kept going

Requirement: Quiz shows 5 questions Result: yes ________: screenshot of question 5

____: Press the space bar to jump Result: yes - the sprite jumped Evidence: photo of the jump

Req 1: Timer counts down - yes Req 2: Sound plays on win - no Met: _ out of 2

Spot the Error

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

Question 1

A Requirement: Show the score

B Test: Play one full round

C Evidence: Screen showed 8/10

D Result: MAYBE

Question 2

A Requirement: Reset the score

B Test: Click the reset button

C Evidence: I think it works

D Result: YES

Question 3

A Requirement: Timer counts down

B Test: Guess how timer works

C Evidence: Timer went 10 to 0

D Result: YES

Question 4

A Success: Loads in 3 seconds

B Test: Time it with a stopwatch

C Evidence: It took 9 seconds

D Result: YES

Question 5

A Success: Text is easy to read

B Test: Ask a Year 3 to read it

C Evidence: I like the colours

D Result: YES

Answer Key

Checking a solution against the requirements

Section A: Quick Questions

A — Test each requirement one by one and record yes or no

B — The app must show the score at the end of the quiz

A — Yes, and note what you saw

B — A screenshot of the game running after clicking Start

A — No, and note that the name disappeared

Section B: Match the Pairs

Requirement 1: Score shows on screen | Met? YES → A checklist row where the student tested one requirement and recorded yes because it worked

Evidence: screenshot of score at 10 → A note that shows proof of what the tester saw when checking the requirement

Test every requirement and success criterion, one row at a time → Row 1: Button starts game | Row 2: Game ends in 60 s

Record a no result when the solution does not meet the requirement → Requirement: Timer counts down | Met? NO

Requirement: Quiz asks 5 questions | Met? YES (did not test it) → The result was recorded without testing the solution, so there is no real evidence.

Checklist: only Requirement 1 and 2 checked, 3 and 4 skipped → Some requirements were left out, so the solution was not fully checked.

Section C: Definitions

requirements checklist — A list of every functional requirement and success criterion. You test the solution against each one, then record yes or no and note your evidence, such as what you saw or a screenshot.

Section D: Fill in the Blanks

Requirement: Score shows on screen
Test: Play the game and look at the score
Result: yes - I saw the score go up

Requirement: Game ends after 3 lives
Test: Lose 3 lives
Result: no - the game kept going

Requirement: Quiz shows 5 questions
Result: yes
Evidence: screenshot of question 5

Test: Press the space bar to jump
Result: yes - the sprite jumped
Evidence: photo of the jump

Req 1: Timer counts down - yes
Req 2: Sound plays on win - no
Met: 1 out of 2

Section E: Spot the Error

D — A checklist result must be YES or NO. The evidence shows the score appeared, so the line should be 'Result: YES'.

C — Evidence must be something you saw or captured, like what happened on screen. 'I think it works' is a guess. It should be 'Evidence: Score went back to 0'.

B — You must actually run the solution and watch what happens. Guessing is not testing. It should be 'Test: Start and watch timer'.

D — The evidence shows 9 seconds, which is slower than the 3 second success criterion. The result should be 'Result: NO'.

C — The evidence must match the criterion being checked, which is easy-to-read text. Liking the colours says nothing about reading. It should describe what the reader did.