| Lesson Plan |
| Grade: |
Date: 25/02/2026 |
| Subject: Information Communication Technology ICT |
| Lesson Topic: Know and understand components of technical documentation including purpose of the system/program, limitations of the system, program listing, program language, program flowcharts/algorithms, system flowcharts, hardware and software requirements, fil |
Learning Objective/s:
- Describe the purpose and limitations of a system or program.
- Identify and explain each component of technical documentation.
- Produce a concise technical document that includes a program listing, flowcharts, requirements and validation routines.
- Evaluate sample runs to verify that documentation accurately reflects system behaviour.
- Apply documentation standards appropriately at different stages of the SDLC.
|
Materials Needed:
- Projector and screen
- ICT lab computers with a Python IDE
- Printed handout of the technical‑documentation checklist
- Sample source code (simple calculator program)
- Flowchart software (e.g., draw.io) or paper templates
- Worksheet for variable tables and requirements
|
Introduction:
Begin with a quick question: “What would happen if a developer tried to modify a program without any documentation?” Use students’ prior experience from earlier SDLC lessons to highlight the risks. Explain that today they will master the essential components of technical documentation and will be able to create a complete document that anyone can follow. Success will be measured by their ability to produce a correct documentation fragment for a given program.
|
Lesson Structure:
- Do‑now (5’) – Students list, on sticky notes, all components they recall from previous lessons.
- Mini‑lecture (10’) – Teacher presents each documentation component with brief examples (purpose, limitations, flowcharts, etc.).
- Guided practice (15’) – In pairs, students complete a documentation template for a simple calculator program (purpose, language, variable list, etc.). Teacher circulates to give feedback.
- Flowchart activity (10’) – Using draw.io or paper, learners create a program flowchart and a system flowchart for the same program.
- Review & quick quiz (10’) – Whole‑class review of sample runs and validation routines; Kahoot quiz to check understanding.
- Exit ticket (5’) – Each student writes one documentation component they found most challenging and why.
|
Conclusion:
Recap the key components of technical documentation and how they support each SDLC phase. Collect exit tickets and remind students that their homework is to finish a full technical document for the provided program, including all components discussed.
|