Week 11 · Tuesday: Decomposition (Code Crew G3)

Tuesday: Take It Apart

Rocket wants to build a blanket fort. He grabs pillows, chairs and blankets all at once. The pile tumbles down!

Rocket laughs. "That was too fast." Raven asks, "What small jobs are inside a fort?"

Nova hovers over the pile. "Try finding four small jobs," she hints. Let's take some big tasks apart.

Decompose each big task into 4 subtasks.

BUILD A FORT:

• ____________________________________

MAKE A SANDWICH:

• ____________________________________

Try Without Paper

Pick a chore you HATE. Break it into 3 tiny pieces.
Do just ONE piece. Easier?

Sometimes a small part is still big. Then you break it apart again.

Keep going until each part is one clear step.

BREAK IT AGAIN

Pack for a trip has a part called pack clothes. Is that one clear step?

Which is a smaller part of pack clothes?

When do you stop breaking parts apart?

Decomposition is a lot like which earlier week?

Statement	True or false?
A part can be broken into even smaller parts.	?
Every part must be broken into exactly 4 pieces.	?
A good small part is easy to start.	?
Decomposing a chore can make it feel easier.	?

WHY THIS EXERCISEBreaking parts down again is how big programs stay simple.

A job has 3 parts. They have 2, 1 and 2 tiny steps. How many tiny steps in all?

A chore has 4 parts with 2 steps each. How many steps in all?

A big goal at the top, with parts branching below, makes a decomposition ____.

Try it

Pick the chore you like least.
Break it into parts. Then break one part again.
Do the tiniest step first.

Which part needed to be broken down again? What were its smaller steps?

MAKE A SANDWICH

WHY THIS EXERCISEProgrammers split a big task into subtasks. Then they put the subtasks in the right order.