Computer Science Grade 3 Introduction to Scratch Block-Based Coding

Grade 3 Computer Science Study Guide: Introduction to Scratch – Block-Based Coding

1. The Driving Question

"If you could make a cat dance across the screen just by snapping together LEGO-like blocks—no typing, no mistakes—how would you tell it exactly what to do? And why does the cat sometimes do the wrong thing even when you think you gave the right instructions?"

2. The Core Idea – Built, Not Listed

Imagine you’re directing a play with a single actor: a bright orange cat on a stage (your computer screen). You can’t talk to the cat—you have to give it a script made of colored blocks that snap together like puzzle pieces. Each block is a command: "Move 10 steps," "Play a meow sound," "Turn 15 degrees." The cat follows the blocks in order, top to bottom, like reading a recipe. But here’s the catch: if you put the "Jump" block before the "Walk" block, the cat will jump first—even if that looks silly. Computers do exactly what you tell them, not what you mean.

This is block-based coding in Scratch: giving step-by-step instructions (a program) to make something happen on screen. The blocks are like training wheels—they let you focus on what you want to do (make a game, tell a story) without worrying about spelling or semicolons. But just like training wheels, they still force you to think like a programmer: break big ideas into tiny, precise steps.

Key Vocabulary:
- Sprite: A character or object in Scratch that you can program.
Definition: The thing on the screen that moves, talks, or changes when you run your code.
Example: The default orange cat, but also a soccer ball, a dragon, or even a slice of pizza you draw yourself.
Grade 3 Note: In later grades, you’ll learn that sprites can have costumes (different looks) and sounds—like a cat that turns into a ghost when you press the spacebar!

• Block: A single instruction in Scratch.
  Definition: A colored puzzle piece that tells a sprite what to do.
  Example: The green "say Hello! for 2 seconds" block makes a speech bubble pop up—like a cartoon thought bubble.
  Grade 3 Note: Blocks are grouped by color (e.g., blue for motion, purple for looks) so you can find them fast, like sorting crayons by shade.

• Script: A stack of blocks that runs in order.
  Definition: A set of instructions that tells a sprite what to do from start to finish.
  Example: A script that makes a shark swim in a circle: "Move 10 steps → Turn 15 degrees → Repeat 24 times." Grade 3 Note: If you forget the "Repeat" block, the shark will only turn once and stop—like a robot that quits halfway through a dance!

• Debugging: Fixing mistakes in your code.
  Definition: Figuring out why your program isn’t doing what you want and fixing it.
  Example: Your cat is supposed to glide to a mouse, but it walks through the mouse instead. You realize you forgot the "if touching mouse" block to make it stop.
  Grade 3 Note: Debugging isn’t about being "bad at coding"—it’s like proofreading a story. Even professional programmers spend most of their time fixing mistakes!

3. Assessment Translation

How this appears in Grade 3 assessments:
- Classroom Formative Assessments: Your teacher might give you a challenge like: "Make the cat draw a square. Show your script and explain why it works." - Proficient Response:
- Script: "Move 100 steps → Turn 90 degrees" (repeated 4 times).
- Explanation: "A square has 4 equal sides and 4 corners. Each turn is 90 degrees because 360° ÷ 4 = 90°. The cat moves the same distance each time to make the sides equal." - Developing Response:
- Script: "Move 100 steps → Turn 90 degrees" (only once).
- Explanation: "It’s a square because it turns." (Missing the repetition and angle reasoning.)

• What Teachers Look For:
• Correct Blocks: Using the right blocks for the task (e.g., "Repeat" for loops, "Turn" for angles).
• Logical Order: Blocks stacked in an order that makes sense (e.g., "Move" before "Turn").
• Explanation: Describing why the script works, not just what it does.

Model Proficient Response (Exit Ticket):
Prompt: "Make a script that makes the cat spin in a circle. Explain how you chose the numbers." Response:

My script has two blocks: "Turn 15 degrees" and "Repeat 24 times." I chose 15 degrees because 360° ÷ 24 = 15°, so the cat turns a little bit 24 times to make a full circle. If I used 90 degrees, it would only turn 4 times and look like a square!

4. Mistake Taxonomy

Mistake 1: The "Almost There" Loop
- Prompt: "Make the cat walk to the edge of the screen and stop." - Common Wrong Response: - Script: "Move 10 steps → Repeat 100 times." - Why It Loses Credit: The cat walks off the screen because the script doesn’t check if it’s at the edge. The student assumes the cat will "know" to stop.
- Correct Approach: - Use the "if on edge, bounce" block or add a "Repeat until touching edge" block. Explain: "The cat needs a rule to check where it is, like a robot vacuum that stops when it hits a wall."

Mistake 2: The "Backward Dance"
- Prompt: "Make the cat do a dance: spin, then jump, then spin again." - Common Wrong Response: - Script: "Turn 15 degrees → Change y by 100 → Turn 15 degrees" (but the cat spins after jumping).
- Why It Loses Credit: The blocks are in the wrong order. The student didn’t test the script to see the cat jumps first.
- Correct Approach: - Stack the blocks in the order of the dance: "Turn 15 degrees → Turn 15 degrees → Change y by 100." Test it! "Computers do exactly what you tell them—like a recipe where you can’t swap the steps."

Mistake 3: The "Invisible Glitch"
- Prompt: "Make the cat say 'Hello!' when you click the green flag." - Common Wrong Response: - Script: "Say Hello! for 2 seconds" (but not attached to the green flag).
- Why It Loses Credit: The script never runs because it’s not triggered. The student assumes the code starts automatically.
- Correct Approach: - Snap the "Say" block under the "when green flag clicked" block. Explain: "The green flag is like a light switch—it turns the script on. Without it, the code is just sitting there!"

5. Connection Layer

• Within Computer Science → Algorithms: A script in Scratch is an algorithm—a step-by-step plan to solve a problem. Later, you’ll write algorithms in text-based languages like Python, but the logic is the same: "Do this, then this, if that happens."
• Across Subjects → Writing a Story: A Scratch script is like a story’s plot. If you write "The cat sat. The cat jumped." out of order, the story doesn’t make sense. Coding forces you to think like an author: What happens first? What happens next?
• Outside School → Board Game Rules: The rules of a game like Candy Land are like a script. If the rules say "Move to the next red space," but you land on a blue one, you don’t move—just like a sprite only does what its blocks say. Debugging is like fixing a rule that lets players cheat!

6. The Stretch Question

"What if you wanted to make a Scratch project where two sprites—like a dog and a cat—have a conversation, but the dog only talks after the cat finishes? How would you make sure they don’t interrupt each other?"

Pointer Toward the Answer:
You’d need a way to tell the dog to "wait" until the cat’s speech bubble disappears. In Scratch, you could use the "broadcast" and "when I receive" blocks—like passing a talking stick. The cat "broadcasts" a message when it’s done, and the dog’s script starts only when it "receives" that message. This is how real apps handle turn-taking, like in a video call where only one person can talk at a time!