Lesson Plan

Resources → Subject Notes → Computer Science → Notes
Lesson Plan
Grade: Date: 17/01/2026
Subject: Computer Science
Lesson Topic: Describe the principles, benefits and drawbacks of each type of life cycle
Learning Objective/s:
  • Describe the core principles of at least four software development life‑cycle models.
  • Compare the benefits and drawbacks of each model.
  • Evaluate which model best fits given project scenarios.
  • Explain how risk analysis influences model selection.
  • Apply knowledge to select an appropriate life‑cycle for a classroom coding project.
Materials Needed:
  • Projector and screen
  • Whiteboard and markers
  • Printed handouts summarising each model
  • Laptop with IDE for demonstration
  • Sticky notes for the opening activity
  • Access to an online diagram of the six PDLC models
 Introduction:
Begin with a quick poll: which software development approach have you heard of? Review prior knowledge of linear versus iterative processes, then state that by the end of the lesson students will be able to articulate the principles, benefits and drawbacks of major life‑cycle models and choose the most appropriate one for a given scenario.
Lesson Structure:
  1. Do‑Now (5') – Students write any software development models they know on sticky notes and post them on the board.
  2. Mini‑lecture (15') – Slide presentation covering the six PDLC models, focusing on their core principles.
  3. Comparative analysis activity (20') – In groups, students receive a model card and fill a Venn diagram comparing its benefits and drawbacks with another model.
  4. Case‑study application (15') – Each group is given a project scenario and must justify the most suitable life‑cycle model.
  5. Whole‑class debrief (10') – Groups share decisions; teacher highlights key trade‑offs and risk considerations.
  6. Exit ticket (5') – Students write one benefit and one drawback of a model of their choice.
Conclusion:
Recap that each life‑cycle offers distinct trade‑offs and that model choice depends on project risk, requirements and stakeholder needs. Collect exit tickets as a quick retrieval check and assign homework: create a short diagram comparing two models and justify which would suit a chosen project.