Seventh graders discover that the code they write is not what the computer runs directly, and trace how a program goes from typed text to translated instructions to a result on screen, then put the steps in order.
Students will be able to…
You type code in words people can read, but a computer only understands simple on-off instructions. What has to happen between pressing run and seeing a result?
Project this and put the steps of running a program in order — tap each one from writing the code to showing the output.
Tap any phase to open the teacher moves and student actions.
You type code in words a person can read, but a computer only understands simple on-off instructions. So what has to happen between pressing run and seeing a result?
Students put the steps of running a program in order.
Students name what handles each step.
Students diagram the journey.
Students reflect on running a program.
Aligned to the CSTA K-12 Computer Science Standards and ISTE Standards for Students.
Decompose problems and describe how a program is created and run.
Systematically test and refine programs.
Explain how programs run on computing systems.
Computational Thinker: model how a system turns input into output.
Preview the three formative checks. Tap “Sample answer” to see what mastery looks like — hide them before you print for students.
Have students draw the code, the translator, and the output, add arrows for each step, and label where translation happens, so the hidden process becomes visible. A printable how-a-program-runs worksheet is in the Computer Science library.
Tap a card to flip it, then rate whether you knew it. Built from this lesson’s vocabulary.
A quick self-check with instant feedback, drawn from this lesson’s key terms.
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.