← ACARA Digital Technologies Years 5–6

Following one action through the parts: tapping a game button

Follow one action, like a game tap: the screen senses it, the CPU decides, RAM holds the game, storage keeps the saved score and the screen shows the result.

Understanding Following one action through the parts: tapping a game button in ACARA Digital Technologies Years 5–6

What it does: RAM is the short-term memory that keeps the game open and ready while it is being used. Storage is long-term, so the saved score is still there next time you switch on. The touchscreen is an input device. It senses your finger and sends the tap to the rest of the system. The CPU processes the tap and decides what the game should do next, like making your character jump. RAM holds the game and the things it is using right now, so the CPU can get to them fast. Storage keeps data even when the power is off. RAM is cleared when the device turns off.

Common mistakes: A speaker is an output device, so it cannot sense a tap. The touchscreen is the input device that senses it: tap <- screen.sense(). The CPU decides what happens, but it is RAM that holds the game while you play. The line should be RAM.hold(game).

Class: _____________________  ·  Name: _____________________  ·  Date: _________

Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.

This module's key terms are also in a printable crossword (Modules 5–26) and word search (Modules 5–43).

Take this worksheet further — free with Cloodit

Each concept is reinforced from every angle — learned, then applied, then tested.

Learning
Duo
You tap a button on a game screen. Which part first senses the tap?
The storage driveThe touchscreen (input device)
Matches
cpu.sense(tap)
↓
The CPU does not sense taps. The touchscreen (input device) senses the tap, and then the CPU decides what to do with it.
Applying
Meanings
Term
trace an action
Meaning
Follow one action, like a game tap: the screen senses it, the CPU decides, RAM holds the game, storage keeps the saved score and the screen shows the result.
Practice
INPUT: screen senses the tap
Testing
Gaps
The senses the tap (input)
Check Answer
Spots
1tap <- speaker.sense()
2action <- CPU.decide(tap)

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

The 'Gazelle' badge — Tuple Sprinter, one of Cloodit's 106 collectible badges
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.

Quick Questions

1. You tap a button on a game screen. Which part first senses the tap?
A. The touchscreen (input device) ✓
B. The storage drive
The touchscreen is an input device. It senses your finger and sends the tap to the rest of the system.
2. Which part decides what happens after you tap the jump button?
A. The CPU ✓
B. The speaker
The CPU processes the tap and decides what the game should do next, like making your character jump.
3. Where is the game kept while you are playing it?
A. In RAM, so the CPU can reach it quickly ✓
B. Only inside the screen
RAM holds the game and the things it is using right now, so the CPU can get to them fast.
4. Your game saves your high score so it is still there tomorrow. Which part keeps it?
A. RAM
B. Storage ✓
Storage keeps data even when the power is off. RAM is cleared when the device turns off.
5. After the CPU decides your character jumps, which part shows you the jump?
A. The CPU
B. The screen (output device) ✓
The screen is an output device. It displays the result so you can see what happened.

Match the Pairs

tap = screen.sense() → The touchscreen is the input device. It senses your finger tap on the game button.
result = cpu.decide(tap) → The CPU works out what the tap means and decides what the game should do next.
RAM holds the running game and its current score while you play, so the CPU can reach them quickly. → ram.hold(game)
Storage keeps the saved score even after the device is turned off. → storage.save(score)
cpu.sense(tap) → The CPU does not sense taps. The touchscreen (input device) senses the tap, and then the CPU decides what to do with it.
screen.save(score) → The screen only shows the result. Storage is the part that keeps the saved score.

Key Term

trace an action
Follow one action, like a game tap: the screen senses it, the CPU decides, RAM holds the game, storage keeps the saved score and the screen shows the result.

Fill in the Blanks

1. Tap the game button The screen senses the tap (input)
Hint: Type the part that senses the tap as the input device.
2. Tap sensed The CPU decides what happens next
Hint: Type the short name of the part that processes the tap and decides what to do.
3. Game is running RAM holds the game while you play
Hint: Type the short name of the memory that holds the game while it runs.
4. Level finished storage keeps the saved score
Hint: Type the part that keeps the score even when the device is off.
5. Score changes The screen shows the result (output)
Hint: Type the word for the step where the device shows you the result.

Spot the Error

Question 1
A tap <- speaker.sense()
B action <- CPU.decide(tap)
C RAM.hold(game)
D storage.save(score)
E screen.show(action)
Line A — A speaker is an output device, so it cannot sense a tap. The touchscreen is the input device that senses it: tap <- screen.sense().
Question 2
A tap <- screen.sense()
B result <- CPU.decide(tap)
C CPU.hold(game)
D screen.show(result)
Line C — The CPU decides what happens, but it is RAM that holds the game while you play. The line should be RAM.hold(game).
Question 3
A tap <- screen.sense()
B choice <- RAM.decide(tap)
C storage.save(score)
D screen.show(choice)
Line B — RAM only holds things for now. The CPU is the part that decides what the tap does. It should be CPU.decide(tap).
Question 4
A tap <- screen.sense()
B result <- CPU.decide(tap)
C RAM.hold(game)
D RAM.keep(saved_score)
E screen.show(result)
Line D — RAM is temporary and forgets everything when the power goes off. A saved score is kept in storage, so it should be storage.save(score).
Question 5
A tap <- screen.sense()
B if tap = jump_button then
C screen.decide(jump)
D screen.show(jump)
E end if
Line C — The screen shows results, it does not make decisions. The CPU decides that the character will jump: CPU.decide(jump).

Student with a class code? Join your class →