Lesson Plan

• Describe the three components (inputs, processing, outputs) of an existing manual or computer‑based system.
• Analyse and categorise problems with the current system (technical, organisational, human).
• Formulate clear, testable user requirements for a new system.
• Specify information requirements including data types, formats and validation rules.
• Apply a checklist to verify completion of the analysis stage.

• Projector and screen
• Whiteboard and markers
• Printed case‑study worksheet with the I‑P‑O table
• Checklist handout (analysis stage)
• Laptops with spreadsheet software (or Google Sheets)
• Sticky notes for brainstorming problems

Begin with a quick “what’s the last thing you did on paper before using a computer?” hook, then link that experience to the need to understand existing processes. Review briefly the I‑P‑O model from the previous lesson and state that today students will learn how to document it, spot problems, and write requirements. Success criteria: students will produce a completed analysis table and at least three user requirements.

1. Do‑now (5'): Students list inputs, processing steps and outputs for a familiar manual task (e.g., ordering a pizza).
2. Mini‑lecture (10'): Explain why analysing the current system is essential; revisit I‑P‑O components and problem categories.
3. Guided practice (15'): Using the printed worksheet, students fill the I‑P‑O table for the provided case study, teacher circulates to check understanding.
4. Problem identification (10'): In pairs, students brainstorm technical, organisational and human problems; record on sticky notes and attach to the table.
5. Requirements drafting (15'): Groups write three user requirements and three information requirements, ensuring they are plain‑language and testable.
6. Checklist verification (10'): Whole‑class review of the analysis checklist; students mark completed items on their handouts.
7. Recap & exit ticket (5'): Quick verbal recap; students write one key takeaway and one question on a slip of paper.

Summarise how documenting inputs, processing, outputs, problems and requirements creates a solid foundation for system design. Collect exit tickets as a retrieval check and assign homework: students must interview a family member about a simple manual process and produce an I‑P‑O analysis with identified problems.