Teaching Decompose to Build: From Problem to Procedures in Grades 9-10 (Level 1): Oklahoma Standard L1.AP.M.01

Teaching decompose problems procedures in grades 9-10 (level 1) does not have to be complicated. Picture a software team extracting a repeated calculation into a single, reusable procedure instead of copying code across screens. That kind of thinking is exactly what Oklahoma's grades 9-10 (level 1) computer science standard L1.AP.M.01 asks students to practice — and it is very teachable with the right materials. This post walks through what the standard means, the misconceptions students bring to it, and discussion starters you can use tomorrow, whether you teach in a classroom or at your kitchen table.

What Does Standard L1.AP.M.01 Actually Ask?

Decompose problems into procedures using systematic analysis and design. — Oklahoma Academic Standards for Computer Science (February 2023)

In plain language: This standard asks Level 1 students (grades 9-10) to break a big problem down into smaller, named, reusable pieces called procedures, deciding what information each piece needs and how the pieces depend on one another, using a deliberate design process rather than guesswork.

In student-friendly terms, the learning target is: "I can decompose a problem into procedures using systematic analysis and design, and explain the parameters and dependencies each procedure requires."

What Students Should Be Able to Do

• I can break a complex, real-world problem into smaller, clearly separated subtasks.
• I can turn a subtask into a named procedure and identify the parameter(s) it needs to work correctly.
• I can identify a dependency between two procedures and explain why it exists.
• I can explain how decomposing a problem well affects debugging, scalability, and who can maintain a solution.

Along the way, students pick up the working vocabulary of the topic: decomposition, procedure, parameter, module, subroutine, reusability, pseudocode, flowchart, debugging, interface, scalability, dependency, abstraction.

Decompose Problems Procedures: Misconceptions to Watch For

These are the wrong turns students reliably take with this standard — knowing them ahead of time is half the lesson plan. Each correction strategy below comes straight from the unit's teacher guide (the paragraph and activity references point into the unit itself).

1. "Decomposition just means splitting a problem into any smaller pieces, in any way."

Return to paragraph 6. Systematic analysis means deliberately looking for tasks that repeat, tasks that stand alone, and information each piece needs — not splitting a problem arbitrarily.

2. "A procedure and the code inside it need to be understood in full by anyone who wants to use it."

Point back to paragraph 5's discussion of abstraction and interfaces. A well-designed procedure can be used correctly by only knowing its interface — what goes in and what comes out — not its internal logic.

3. "More parameters always make a procedure more useful."

Emphasize the trade-off named in paragraph 3: too few parameters limits what a procedure can handle, but too many parameters usually signals the procedure is trying to do more than one job.

4. "Decomposition is only a technical concern that does not affect who can work on a project."

Revisit paragraph 8's discussion of maintainability. A poorly decomposed program can often only be safely changed by its original author, while a well-decomposed one lets new team members contribute safely — decomposition is also an access and collaboration issue.

Discussion Starters You Can Use Tomorrow

• Think of an app you use daily. What is one task inside that app that you think is probably its own separate procedure, and why do you think so?
• Why might a team deliberately spend time mapping out dependencies between procedures before writing any code, instead of just starting to build?
• Describe a real-world problem where poor decomposition (bundling unrelated tasks together, or splitting related tasks too far apart) would cause real problems, even if every individual piece worked correctly.

Bringing It Home

This topic is a natural one for families. One ten-minute activity to try: Together, pick a repeated task your family does — packing lunches, planning weekly errands, or organizing a family event. Ask your student to break the task into smaller, named jobs, decide what information each job would need to work correctly, and explain out loud which jobs depend on which. There are no wrong answers — the goal is hearing their reasoning.

Where This Leads

Students who can decompose a problem into procedures using systematic analysis and design, and explain the parameters and dependencies each procedure requires are building skills used every day in software engineering, systems analysis, quality assurance / testing, and technical project management.

See the Unit in Action

Get the Complete L1.AP.M.01 Unit

I built a complete, no-prep unit for this standard — Decompose to Build: Breaking Problems into Procedures — covering 3-4 days of instruction across 44 pages:

• Teacher guide — day-by-day pacing, misconceptions to watch for, discussion questions, differentiation for support / ELL / extension, and a 4-point rubric
• Student learning target page — a kid-friendly "I can" statement with success criteria
• Full content lesson with 3 embedded "Check Your Understanding" checkpoints
• 12-question assessment (6 multiple choice, 4 true/false, 2 short answer) with a complete answer key, explanations, and exemplar responses
• Group activity — "Decompose It: The School Event Planning Challenge" (25-30 minutes)
• Individual activity — "My Procedure Design Log" (20 minutes)
• Crossword and word search built from all 13 vocabulary terms (with answer keys)
• Family connection letter — a plain-language page for parents, with dinner-table questions and a 10-minute home activity
• Certificate of achievement — ready to sign and send home
• Scenario Card Set: Decompose It (separate printable, 2 pages)
• Reference Sheet: Designing Procedures from a Decomposed Problem (separate printable, 2 pages)
• My Procedure Design Log (separate printable, 2 pages)

Get Decompose to Build: From Problem to Procedures on Teachers Pay Teachers →

Also aligned to CSTA 3A-AP-17: Decompose problems into smaller components through systematic analysis, using constructs such as procedures, modules, and/or classes.

Every Sooner Standards resource is built directly from the official Oklahoma Academic Standards for Computer Science (February 2023) — standard text verified, never paraphrased from memory.