← Years 5–6 Creating Digital Solutions

Checking a solution against the requirements

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.

Part of: 5-6 Digital Technologies Vic Curric - Creating Digital Solutions — Module 68, VCE Data Analytics - U4O1 - Development and Evaluation — Module 94, 7-8 Digital Technologies: Evaluating digital solutions — Module 1, 9-10 Digital Technologies: Evaluating solutions, impact and innovation — Module 1, ACARA Digital Technologies Years 9–10 — Testing and Validating Programs — Module 63, QCE Digital Solutions Unit 1 — Programmed Solutions — Module 114, QCE Digital Solutions Unit 2 — Prototype Data Solutions — Module 126, WA Computer Science ATAR Year 11 — Pseudocode and Algorithm Design — Module 94

Understanding Checking a solution against the requirements in Years 5–6 Creating Digital Solutions

What it does: A requirements checklist has a separate row for each requirement or success criterion so none are missed. If testing shows the timer does not count down, the honest result is no, which shows what needs fixing. Evidence shows what really happened, such as a screenshot or a note about what you saw when you tested. Record what actually happened. If the requirement was not met, the result is no. A complete row has the requirement, a yes or no result, and evidence to support the result. A clear success criterion can be tested and answered with yes or no. 'Really good' is too vague to test.

Common mistakes: A checklist result must be YES or NO. The evidence shows the score appeared, so the line should be 'Result: YES'. 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'.

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 Checking a solution against the requirements 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 a quiz app. What is the best way to check it meets the requirements?

Test each requirement one by one and record yes or noLook at it quickly and say it seems fine

Matches

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.

Applying

Meanings

Term

requirements checklist

Meaning

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.

Practice

Requirement 1: Score shows on screen

Testing

Gaps

Result: - I saw the score go up

Check Answer

Spots

3Evidence: Screen showed 8/10

4Result: MAYBE

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

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 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

A requirements checklist means testing every requirement and recording a yes or no result for each one.

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 ✓

A checklist lists the functional requirements and success criteria that can be tested, not personal preferences.

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

If the solution does what the requirement says, you record yes and write down your evidence.

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 ✓

Evidence shows what really happened, such as a screenshot or a note about what you saw when you tested.

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

Record what actually happened. If the requirement was not met, the result is no.

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.

Key Term

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.

Fill in the Blanks

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

Hint: Type the result word that matches the evidence on this line

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

Hint: Type the result word that matches the evidence, showing the requirement was not met

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

Hint: Type the label for what you saw or a screenshot that proves the result

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

Hint: Type the label for the action you do to check a requirement

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

Hint: Type how many requirements got a yes result

Spot the Error

Question 1

A Requirement: Show the score

B Test: Play one full round

C Evidence: Screen showed 8/10

D Result: MAYBE

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

Question 2

A Requirement: Reset the score

B Test: Click the reset button

C Evidence: I think it works

D Result: YES

Line 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'.

Question 3

A Requirement: Timer counts down

B Test: Guess how timer works

C Evidence: Timer went 10 to 0

D Result: YES

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

Question 4

A Success: Loads in 3 seconds

B Test: Time it with a stopwatch

C Evidence: It took 9 seconds

D Result: YES

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

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

Line 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.

Student with a class code? Join your class →