Decomposing a Problem Into Parts

Break any big, tricky problem into smaller, easier pieces so you can solve one piece at a time.

Reading is good — doing is better. Practice Decomposing a Problem Into Parts as an interactive lesson.

Definition

Decomposing a problem means splitting a large or complicated task into smaller, more manageable steps or parts. Instead of trying to tackle everything at once, you figure out what the smaller jobs are, do them one by one, and then put your solutions together to solve the whole problem. This is one of the four key ideas in computational thinking, and computers (and programmers) use it every single day.

Remember the rule

Big Problem → List the Parts → Solve Each Part → Put It All Together

Key words

Decomposition: Breaking a big problem into smaller, easier-to-handle parts.
Computational Thinking: A way of solving problems by thinking like a computer scientist — breaking things down, finding patterns, and making step-by-step plans.
Sub-problem: One of the smaller pieces you get after you break apart a big problem.
Algorithm: A step-by-step set of instructions for solving a problem or completing a task.
Input: The information or materials you start with before solving a problem.
Output: The result or answer you get after solving a problem.
Sequence: Doing steps in a specific order, one after another.
Debug: Finding and fixing mistakes in a plan or a program.

Worked examples

You need to build a website for a school project about dolphins. Where do you start?

→ Break it into parts: 1) Research facts about dolphins. 2) Write the text for each page. 3) Find or draw images. 4) Build the home page. 5) Build the facts page. 6) Add links between pages. 7) Test that everything works. Now you have 7 small tasks instead of one giant scary one. · Each sub-problem is something you can actually finish in one sitting.

You are writing a program that asks a user their name and says hello. What are the parts?

→ Part 1: Show a prompt asking for the user's name. Part 2: Store what the user types. Part 3: Combine 'Hello, ' with their name. Part 4: Display the greeting on screen. Code each part separately and test it before moving on. · Programmers almost always write code in small pieces and test each piece right away.

Your teacher asks you to make a slideshow presentation with 5 slides, a title, pictures, and speaker notes. How do you decompose it?

→ Sub-problems: 1) Choose a topic. 2) Write an outline of 5 slide topics. 3) Write the text for each slide. 4) Find one picture per slide. 5) Write speaker notes for each slide. 6) Format and check spelling. Finish each sub-problem before starting the next. · Decomposing keeps you from feeling overwhelmed and helps you track your progress.

A spreadsheet formula =A1+B1+C1 is giving the wrong answer. How do you decompose the debugging task?

→ Break it down: 1) Check what number is in cell A1. 2) Check what number is in cell B1. 3) Check what number is in cell C1. 4) Add them by hand to see what the correct answer should be. 5) Compare your hand answer to the spreadsheet answer to find the error. You fixed a confusing problem by checking one cell at a time. · Checking one small part at a time is much faster than staring at the whole formula.

You want to create a quiz game in Scratch with 3 questions. What are the parts?

→ 1) Make the opening screen with the title. 2) Write Question 1 and program its right/wrong check. 3) Write Question 2 and program its right/wrong check. 4) Write Question 3 and program its right/wrong check. 5) Keep score and display the final score at the end. Build and test each question block before adding the next one. · Decomposing a Scratch project this way means a bug in Question 2 does not break Question 3.

Common mistakes

Trying to solve the whole problem at once without listing the parts first — this leads to feeling stuck or skipping important steps.
Making sub-problems that are still too big, like writing 'build the whole app' as one step instead of breaking it down further.
Forgetting to put the parts back together at the end — solving every piece but never combining them into a final answer.
Doing the sub-problems in the wrong order, such as trying to add pictures to a slide before you have written the text.
Skipping the testing step after finishing each part, so small mistakes pile up and become hard to find later.

FAQs

Is decomposition only used in computer class?

No! You use it all the time. Cleaning your room means: pick up clothes, put away books, vacuum, make the bed. Cooking dinner means: gather ingredients, chop vegetables, cook, plate the food. Any big task can be decomposed.

How do I know if I have broken a problem into small enough pieces?

A sub-problem is small enough when you can describe exactly how to solve it in two or three sentences. If you still feel confused about how to start a sub-problem, break it down one more time.

Does the order of the sub-problems always matter?

Not always, but often yes. Some steps depend on earlier steps being done first. For example, you cannot test a program before you write it. Always ask yourself: 'Does this step need another step to be finished first?'

What if I miss a sub-problem when I decompose?

That is okay and very normal! When you realize a piece is missing, just add it to your list and solve it. Decomposition is a plan, not a law — you can update it as you go.

How is decomposition different from just making a to-do list?

A to-do list can be random tasks. Decomposition means every item on the list is a part of one specific bigger problem, and together all those parts add up to the complete solution.

Can a computer decompose problems by itself?

Computers follow instructions written by programmers who already did the decomposition. Artificial intelligence tools are getting better at breaking down tasks automatically, but a human programmer almost always decides how to split up a big program into parts first.

Want the whole picture for your child?

Every K–6 subject, an AI tutor that teaches step by step, unlimited practice, and a reward world.

Start a 3-day free trial