Recording user prompts and INPUT values in a trace table
A prompt is written in the OUTPUT column. The value the user types for an INPUT is written in that variable's column on that step, taken from the test data.
Understanding Recording user prompts and INPUT values in a trace table in IGCSE Computer Science Paper 2
What it does: The OUTPUT statement displays the prompt, so its text is written in the OUTPUT column. The INPUT statement stores the typed test value in Mark, so the value goes in the Mark column on that step. In a dry run you must use the test data you are given. The inputs are taken from that data in order.
Common mistakes: The command is INPUT Score. The value typed from the test data is stored in Score, so it is written in the Score column on that step. Score ← INPUT is not valid pseudocode. INPUT must be followed by a variable name, so it should be INPUT Num2. The test value (such as 7) is not written in the code. It goes in the Num2 column of the trace table.
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 83–92) and word search (Modules 71–92).
Take this worksheet further — free with Cloodit
Each concept is reinforced from every angle — learned, then applied, then tested.
Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.
Over 100 of them, across seven natural biomes.
Turns their work into revision material ready for Flash Cards and Exam study.
Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.
Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.
Quick Questions
Match the Pairs
Key Term
Trace table INPUTFill in the Blanks
Spot the Error
Student with a class code? Join your class →