Lesson Plan

Resources → Subject Notes → Computer Science → Notes
Lesson Plan
Grade: Date: 17/01/2026
Subject: Computer Science
Lesson Topic: Show understanding of the purpose of a development life cycle
Learning Objective/s:
  • Describe the purpose and benefits of a software development life cycle.
  • Identify and explain each stage of the PDLC.
  • Compare linear (waterfall) and iterative (agile) development models.
  • Apply the PDLC stages to a simple inventory‑management example.
  • Evaluate effort estimation using the basic COCOMO formula.
Materials Needed:
  • Projector or interactive whiteboard
  • Slide deck summarising PDLC stages
  • Handout with PDLC flowchart
  • Sample Python/Flask code for the inventory system
  • Worksheets for group activity
  • Sticky notes for brainstorming
  • Internet access for research
 Introduction:
Begin with a quick poll: how many students have worked on a group coding project and what challenges they faced. Discuss common issues such as missed requirements or late bugs. Explain that a structured development life cycle helps avoid these problems, and state the success criteria – students will be able to name each PDLC stage and select an appropriate model for a scenario.
Lesson Structure:
  1. Do‑Now (5'): Students write past project problems on sticky notes; teacher groups common themes. (Engage)
  2. Mini‑lecture (10'): Present PDLC overview, stages and benefits using slides. (Explain)
  3. Interactive comparison (8'): Show linear vs iterative table; class discusses flexibility and risk. (Analyze)
  4. Group activity (15'): Teams map the inventory‑management example to PDLC stages on a worksheet and create a brief timeline. (Apply)
  5. Coding demo (10'): Teacher demonstrates a simple Python/Flask function, linking it to the implementation stage. (Demonstrate)
  6. Formative check (7'): Quick Kahoot quiz on stage definitions and model selection. (Assess)
  7. Reflection & exit ticket (5'): Students write one way they will use a PDLC in future projects on a slip. (Conclude)
Conclusion:
Summarise how each PDLC stage builds toward reliable software and why model choice matters. Collect exit tickets to gauge understanding. For homework, ask students to draft a PDLC plan for a personal app idea, noting any risk‑mitigation strategies.