| Lesson Plan |
| Grade: |
Date: 25/02/2026 |
| Subject: Information Communication Technology ICT |
| Lesson Topic: Know and understand components of user documentation including purpose of the system, limitations of the system, hardware and software requirements, how to load/run/install software, how to save a file, how to print data, how to add records, how to d |
Learning Objective/s:
- Describe the purpose, limitations and hardware/software requirements of an ICT system.
- Explain the steps to install, save, print, add, edit and delete records using the software.
- Apply error‑handling and troubleshooting procedures described in user documentation.
- Produce a concise user‑documentation component for a given scenario.
|
Materials Needed:
- Projector and screen
- Whiteboard and markers
- ICT lab computers with the sample software installed
- Printed handout of a user‑documentation template
- Example data files (CSV, PDF)
- Teacher’s checklist of error messages and solutions
|
Introduction:
Begin with a quick poll: “When you first open a new program, what information do you look for?” Connect responses to the need for clear user documentation. State that today learners will identify all essential components and practise creating a short documentation piece. Success will be shown by correctly completing a checklist of tasks.
|
Lesson Structure:
- Do‑Now (5'): Students list any missing information they have encountered in software manuals.
- Mini‑lecture (10'): Overview of the 8 documentation components (purpose, limitations, requirements, install, save, print, add records, edit/delete).
- Guided demo (15'): Teacher walks through installing the sample software, saving a file and printing a report while highlighting documentation notes.
- Group activity (15'): Teams create a draft user‑documentation section for “How to add a record” using the template handout.
- Check for understanding (5'): Teams exchange drafts, use a checklist to verify inclusion of all required elements.
- Error‑handling practice (5'): Quick quiz on matching error codes to solutions.
|
Conclusion:
Recap the eight components and why each is vital for end‑users. Students complete an exit ticket by writing one missing element they might add to improve the documentation. Assign homework: draft a full user‑documentation page for a chosen classroom application.
|