Why this lesson matters
Combine OOP, JSON or CSV persistence, reusable functions, dictionaries, console commands, and Matplotlib into a complete item-listing project that can be demonstrated.
The goal is not to memorize vocabulary. By the end of the lesson, you should be able to use the ideas in a realistic situation, explain the reason for your choices, and check whether the result actually works for the intended person or task.
Learning objectives
- Explain Decomposition in your own words.
- Apply Persistence to a realistic classroom or community example.
- Connect Decomposition with Data visualization when making a decision.
- Complete the practice task and reflect on one improvement.
Core ideas
1. Decomposition
Breaking a large project into small, testable responsibilities with clear inputs, outputs, and order of implementation.
In practice: Look for this idea while you complete the lesson task. Pause before each major step and explain how Decomposition changes what you choose, create, or check.
2. Persistence
Saving application state to a file or database so information remains available after the program stops.
In practice: Look for this idea while you complete the lesson task. Pause before each major step and explain how Persistence changes what you choose, create, or check.
3. Data visualization
Encoding values as a chart so patterns, comparisons, and outliers are easier to understand than in raw records.
In practice: Look for this idea while you complete the lesson task. Pause before each major step and explain how Data visualization changes what you choose, create, or check.
How the ideas connect
Start with Decomposition to understand the foundation of the lesson. Use Persistence to turn that understanding into an action. Then apply Data visualization to check the quality, safety, or usefulness of the result. The three ideas are strongest when you can explain their relationship rather than treating them as separate definitions.
Guided walkthrough
- Name the goal. In one sentence, write what you are trying to understand, create, or improve.
- Make a prediction. Before touching a device, use Decomposition and Persistence to predict what a strong result should look like.
- Complete the task. Plan the project before coding: define commands, an Item class, storage format, validation rules, and a chart function. Build and test one thin end-to-end path first.
- Check the outcome. Use Data visualization to inspect the result. Ask what worked, what did not, and what evidence supports your judgment.
- Explain and revise. Tell a partner what you changed and why. Make one small improvement, then compare the new result with the first one.
Worked classroom scenario
Imagine two learners sharing one device. The first learner is the driver and performs the steps; the second is the navigator and reads the goal, predicts the next step, and checks the result. Halfway through the task, switch roles. Both learners should be able to explain how Decomposition, Persistence, and Data visualization appeared in the work.
If no device is available, complete the same reasoning on paper: sketch the screen or result, label each decision, and describe what you would test when a device becomes available.
Common mistakes and fixes
- Rushing into the tool: Write the goal and prediction first so every click or step has a reason.
- Copying without understanding: After each major step, explain it in your own words to a partner.
- Accepting the first result: Compare the outcome with the goal and make at least one deliberate improvement.
- Letting one person control a shared device: Rotate driver and navigator roles so both learners think and practice.
Independent practice
Plan the project before coding: define commands, an Item class, storage format, validation rules, and a chart function. Build and test one thin end-to-end path first.
For an extra challenge, adapt the task for a different audience or community need. Write two sentences explaining what changed and which lesson idea guided your decision.
Check your understanding
- How would you explain Decomposition to someone new to the topic?
- What is one realistic example of Persistence outside this classroom?
- When might Data visualization prevent a weak, unsafe, or confusing result?
- How are Decomposition and Persistence connected?
- What evidence would convince you that your practice result works?
- If you repeated the activity tomorrow, what would you improve first and why?
Key takeaway
Combine OOP, JSON or CSV persistence, reusable functions, dictionaries, console commands, and Matplotlib into a complete item-listing project that can be demonstrated.
You are ready to move on when you can explain the three core ideas, complete the practice without copying, and describe one improvement using evidence from your result.