Years 5–6 Creating Digital Solutions Definitions Worksheet: Building visual programs and Evaluating digital solutions and their impact (Modules 61–74)
Name:
Date:
Class:
✎
Key terms
Write what each term means, in your own words.
1
counter ← counter + 1
2
if inside a loop
3
when this sprite clicked
4
switch backdrop to
5
step -> block
6
testing
7
debugging
8
requirements checklist
9
evaluate
10
improvement
11
community impact
12
user, need, feature, reason
Answer Key
Years 5–6 Creating Digital Solutions · Modules 61–74 · Student wording will vary for definitions
1counter ← counter + 1 — A counter is a variable that goes up by 1 each time a loop repeats, so it counts how many times something happened. Set it to 0 before the loop starts.
2if inside a loop — An if block placed inside a loop is checked again on every repeat, so the program makes a new decision each time round, like in forever or repeat until.
3when this sprite clicked — An event block that starts its script when the user clicks that sprite, so the sprite works like a button. Add a label to the sprite and a colour change to show it can be clicked.
4switch backdrop to — A Looks block that changes the stage picture. With show and hide blocks it gives a program several screens, like a start screen and a results screen, and hides sprites not needed.
5step -> block — Turn each algorithm step into a matching block: SET becomes set, ASK becomes ask and wait, IF becomes if, REPEAT becomes repeat. Then run it to check it does what the algorithm says.
6testing — Running your program with chosen test inputs and comparing what happens to the result you expected. Test every path, so each branch of the program gets checked.
7debugging — Finding the block that causes a wrong result in a program and fixing it, such as a block in the wrong order or a wrong condition.
8requirements 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.
9evaluate — 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.
10improvement — A change that helps when a system does not meet a user's need. Find the gap, suggest one new feature, and give your feedback in a kind, respectful way.
11community impact — How a digital solution affects other people, not just its user. It can help (benefits), cause problems (harms), or leave some people out.
12user, need, feature, reason — A good discussion names the user, then their need, then the feature that meets it, and ends with the reason it works. Starters like 'The system helps because...' can help.