Everything you need before the bell rings
Learning Objectives
Students will be able to…
- ✓Trace code by hand.
- ✓Track variables.
- ✓Follow control flow.
- ✓Predict the output.
How can you figure out what code does without running it?
Order the Tracing Steps
Project this and have students put the code-tracing steps in order.
55 minutes, five moves
Tap any phase to open the teacher moves and student actions.
Hook — In Your Head
Can you predict a program’s output before you run it?
👩🏫 Teacher Moves
- Show a short program.
- Ask the question.
- Set the goal.
🎒 Student Actions
- Think.
- Share.
- Get ready.
Use — Tracing
Students learn.
👩🏫 Teacher Moves
- Send students to Order the Tracing Steps.
- Order the steps.
- Note track variables in a table.
🎒 Student Actions
- Order.
- Say.
- Note it.
Modify — Trace It
Students practice.
👩🏫 Teacher Moves
- Trace a short program.
- Fill a variable table.
- Predict the output.
🎒 Student Actions
- Trace.
- Table.
- Predict.
Create — Create
Students apply.
👩🏫 Teacher Moves
- Trace a program with a loop.
- Predict its result.
- Run it to check.
🎒 Student Actions
- Trace.
- Predict.
- Check.
Reflect — Reflect
Students close.
👩🏫 Teacher Moves
- What do you track while tracing?
- Why trace before running?
- Complete the exit ticket.
🎒 Student Actions
- Say it.
- Say it.
- Complete the exit ticket.
Built to the standards you report on
Aligned to the CSTA K-12 Computer Science Standards and the ISTE Standards for Students.
Evaluate and trace program execution.
Systematically test and debug.
Document and reason about code.
Reason about program behavior.
One lesson, every learner
Multilingual Learners
- Tracing-step cards.
- Frame: "I track each ___ in a table."
- Trace together slowly.
Support & Access
- Use 3 core steps.
- Trace a 3-line program.
- Use a variable table template.
Stretch & Extend
- Trace nested control flow.
- Find a bug by tracing.
- Trace recursion simply.
What to gather
- 📽️Screen / board
- 🔍Trace-step cards
- 💻Order the Tracing Steps
- 📋Variable-table worksheet
- 📓Notebooks
- 🎫Exit-ticket slips
Key terms — hover for a quick definition
Exit Ticket
Preview the three formative checks. Tap “Sample answer” to see what mastery looks like — hide them before you print for students.
Reflect: tracing code.
Have students trace a program and predict its output. A printable variable-table worksheet is in the CS library.
Study the key terms
Tap a card to flip it, then rate whether you knew it. Built from this lesson’s vocabulary.
Nice work!
Check your understanding
A quick self-check with instant feedback, drawn from this lesson’s key terms.
Nice work!
Printable worksheet
A print-and-go review sheet with a built-in answer key. Tap “Show answer key” to reveal answers, or print the clean version for students.
Part A · Write the word that matches each meaning
- a named stored value
- what a program displays
- say what will happen
- follow code by hand
- a chart of variable values
- go line by line
- the order code runs
- find and fix errors
Part B · Show what you learned
- What do you track while tracing code?
- What do you follow through loops and if/else?
- Why trace before running?
Part B: 1) Each variable’s value in a table. 2) The control flow. 3) To truly understand the code and catch bugs.