Lesson Plan

• Describe the difference between verification and validation in ICT projects.
• Explain why both verification and validation are essential for document and software quality.
• Apply at least two verification techniques and two validation techniques to a sample document.
• Design simple data‑validation rules for a spreadsheet and justify their purpose.

• Projector or interactive whiteboard
• Computer lab with word processor and spreadsheet software
• Sample school report document (digital copy)
• Printed proofing checklist handout
• Sticky notes for peer‑review activity

Begin with a quick poll: “What mistakes have you ever found after publishing a document?” Use responses to highlight real‑world costs of errors. Review prior knowledge of spell‑check and basic testing. State that today’s success criteria are to distinguish verification from validation and to demonstrate both in practice.

1. Do‑Now (5’) – Students list three errors they have seen in a recent report.
2. Mini‑lecture (10’) – Define verification vs. validation, show comparison table.
3. Guided demo (12’) – Teacher runs spell‑check, formatting check (verification) then checks grading scale against policy (validation).
4. Hands‑on activity (15’) – In pairs, students use the sample report to complete a proofing checklist, marking verified and validated items.
5. Peer review (8’) – Pairs exchange reports, use sticky notes to add any missed validation issues.
6. Plenary (5’) – Whole‑class debrief: share key differences and why both matter.

Recap the definitions and the two‑step proofing cycle, emphasizing how verification ensures technical accuracy while validation confirms user needs. Students complete an exit ticket by writing one verification and one validation activity they will use in future work. Assign homework: create three data‑validation rules for a spreadsheet of their choice and explain the rationale.