| Lesson Plan |
| Grade: |
Date: 25/02/2026 |
| Subject: Computer Science |
| Lesson Topic: Implement and write pseudocode from a given design presented as either a program flowchart or structured English |
Learning Objective/s:
- Describe the purpose and conventions of pseudocode.
- Translate flowchart symbols into correct pseudocode structures.
- Convert structured English statements into syntactically correct pseudocode.
- Identify and correct common pseudocode errors such as missing END statements or incorrect loop conditions.
|
Materials Needed:
- Projector or interactive whiteboard
- Printed flowchart and structured English handouts
- Student worksheets with practice questions
- Laptops or computers with a simple IDE or text editor
- Whiteboard and markers
|
Introduction:
Begin with a quick poll: who has written pseudocode before? Review the role of pseudocode as a bridge between design and code, recalling the conventions discussed last lesson. Explain that by the end of class students will be able to convert both flowcharts and structured English into accurate pseudocode.
|
Lesson Structure:
- Do‑Now (5’) – Students complete a short quiz on pseudocode conventions.
- Mini‑lecture (10’) – Review key conventions and mapping from flowchart symbols to pseudocode.
- Guided conversion (15’) – Teacher demonstrates converting the sample flowchart for the sum of the first n numbers into pseudocode, prompting student input.
- Pair activity (15’) – Students work in pairs to translate a provided flowchart (even numbers up to n) into pseudocode, using the worksheet.
- Structured English conversion (10’) – Whole‑class walkthrough of the maximum‑of‑three numbers example, highlighting conditional nesting.
- Check for understanding (5’) – Quick exit ticket where each student writes one common pitfall and its fix.
|
Conclusion:
Summarise how pseudocode captures algorithm logic while remaining language‑independent. Collect exit tickets to gauge understanding and address any lingering misconceptions. Assign homework: convert a new flowchart (factorial calculation) into pseudocode and bring it to the next lesson.
|