| Lesson Plan |
| Grade: |
Date: 01/12/2025 |
| Subject: Information Communication Technology ICT |
| Lesson Topic: Know and understand the use of live data |
Learning Objective/s:
- Describe what live (real‑time) data is and its key characteristics.
- Explain how live data is integrated into each phase of the systems life‑cycle.
- Identify appropriate technologies and protocols for handling live data.
- Evaluate challenges such as latency, volume, reliability and propose mitigation strategies.
- Design a simple prototype that retrieves and displays live data.
|
Materials Needed:
- Projector and screen
- Laptop with internet access (teacher and each group)
- Sample live‑data API (e.g., weather or stock feed)
- Worksheets with the systems life‑cycle table
- Code editor/IDE (e.g., VS Code)
- Handout of common live‑data protocols (WebSocket, MQTT, HTTP‑SSE)
- Sticky notes and markers
|
Introduction:
Begin with a quick video clip showing live traffic maps and stock tickers to hook students’ interest. Ask them how these services stay up‑to‑date and link the answer to the systems life‑cycle they have already studied. Explain that today’s success criteria are to recognise live‑data roles, choose suitable technologies, and create a simple live‑data demo.
|
Lesson Structure:
- Do‑now (5'): Quick quiz on the seven phases of the systems life‑cycle.
- Mini‑lecture (10'): Define live data, why it matters, and overview of common protocols.
- Group activity (15'): Using the worksheet, map live‑data tasks and considerations onto each life‑cycle phase.
- Live demo (10'): Show a real‑time API feed using WebSocket/JSON and discuss data flow.
- Hands‑on coding (20'): Students modify starter code to fetch and display live data on a web page.
- Testing challenge (10'): Simulate latency and data loss; groups suggest mitigation strategies.
- Review & exit ticket (5'): Each student writes one benefit and one challenge of using live data.
|
Conclusion:
Recap the key points: live data’s definition, its integration across the life‑cycle, and the trade‑offs between speed, accuracy, and security. Collect exit tickets and remind students to research a real‑world live‑data system for a one‑page reflection due next week.
|