| Lesson Plan |
| Grade: |
Date: 25/02/2026 |
| Subject: Computer Science |
| Lesson Topic: Use a structure chart to decompose a problem into sub-tasks and express the parameters passed between the various modules/procedures/functions which are part of the algorithm design |
Learning Objective/s:
- Describe the purpose and components of a structure chart.
- Identify and classify input, output, and in‑out parameters for modules.
- Apply a top‑down approach to decompose a problem into modules and create a correct structure chart.
- Validate parameter flow to ensure each data item is passed exactly once.
|
Materials Needed:
- Projector or interactive whiteboard
- Whiteboard and markers
- Printed worksheet with example problem and blank chart template
- Laptops with a simple diagramming tool (e.g., draw.io) or IDE
- Sample structure chart handout
- Sticky notes for group brainstorming
|
Introduction:
Begin with a quick discussion: ask students how they would break down the task of calculating student grades into smaller steps. Review prior knowledge of modular programming and top‑down design, linking it to the upcoming structure chart activity. Explain that by the end of the lesson they will be able to produce a clear hierarchy of modules and correctly specify the parameters passed between them.
|
Lesson Structure:
- Do‑now (5'): Students list sub‑tasks for a familiar problem (e.g., making a sandwich) on sticky notes; teacher collects examples to segue into modular decomposition.
- Mini‑lecture (10'): Explain structure charts, hierarchy, and parameter types using the grade‑calculation example; demonstrate reading the chart.
- Guided practice (15'): In pairs, students create a structure chart for the grade‑calculation problem on the worksheet and fill the parameter table; teacher circulates with feedback.
- Independent practice (15'): Students design a structure chart for the library‑system problem, completing the parameter table on laptops or paper.
- Check for understanding (5'): Groups present one module’s interface; peers verify correct parameter flow; teacher summarises key points.
|
Conclusion:
Recap the steps of top‑down decomposition and the importance of precise parameter specification. Collect an exit ticket where each student writes one rule for good parameter design. Assign homework to refine the library system chart and add comments describing each module’s purpose.
|