Everything you need before the bell rings
Learning Objectives
Students will be able to…
- ✓Explain decomposition.
- ✓Tell a big problem from a smaller part.
- ✓Break a problem into steps.
- ✓Plan a project in parts.
How do you break a big problem into parts you can solve?
Big Problem or Smaller Part?
Project this and sort each into a Big problem (too big to solve at once) or A smaller part (a doable piece).
50 minutes, five moves
Tap any phase to open the teacher moves and student actions.
Hook — Too Big to Chew
How would you even start building a whole game?
👩🏫 Teacher Moves
- Show a huge goal.
- Ask “where do we begin?”
- Set the goal.
🎒 Student Actions
- Think.
- Guess.
- Get ready.
Use — Decomposition
Students decompose.
👩🏫 Teacher Moves
- Send students to Big Problem or Smaller Part?
- Sort each item.
- Note big goals split into pieces.
🎒 Student Actions
- Sort.
- Say.
- Note it.
Modify — Split It Further
Students modify.
👩🏫 Teacher Moves
- Take one part and split it again.
- Order the smaller parts.
- Spot the first step.
🎒 Student Actions
- Split.
- Order.
- Spot.
Create — Plan a Project
Students create.
👩🏫 Teacher Moves
- Pick a goal (make a comic).
- List 3–4 smaller parts.
- Mark which part is first.
🎒 Student Actions
- Pick.
- List.
- Mark.
Reflect — Reflect
Students close.
👩🏫 Teacher Moves
- Say what decomposition is.
- Name one benefit.
- Complete the exit ticket.
🎒 Student Actions
- Say it.
- Name one.
- 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.
Decompose problems into parts to design a program.
Use flowcharts/pseudocode to plan an algorithm.
Systematically test and refine a solution.
Break problems into manageable parts.
One lesson, every learner
Multilingual Learners
- Use a jigsaw-puzzle analogy.
- Label parts with pictures.
- Pair talk before sorting.
Support & Access
- Sort big vs part only.
- Use 3 items.
- Use picture cards.
Stretch & Extend
- Decompose a part into sub-parts.
- Diagram the whole breakdown.
- Assign parts to a team.
What to gather
- 📽️Screen / board
- 🧩Problem/part cards
- 💻Big Problem or Smaller Part?
- 🗂️Project planner
- 📓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: decomposition.
Have students break one goal into 3 smaller parts. A printable decomposition planner is in the Computer Science 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
- the order of parts to do
- a small job within a task
- breaking a problem into smaller parts
- the big goal to solve
- small enough to actually do
- the part you start with
- a smaller piece of the problem
- to arrange the parts clearly
Part B · Show what you learned
- What is decomposition?
- Is “build a whole game” a big problem or a small part?
- Why decompose?
Part B: 1) Breaking a big problem into smaller parts you can solve. 2) A big problem. 3) Smaller parts are easier to solve and share.