Lesson Plan

• Describe the purpose and key activities of the analysis, design, and testing phases of the system life cycle.
• Explain the artefacts and tools associated with each phase and how they feed into the next stage.
• Apply traceability and documentation techniques to manage phase transitions and stakeholder sign‑offs.
• Evaluate test plans and defect logs to ensure system requirements are met.

• Projector and screen
• Whiteboard and markers
• Printed handouts of phase diagrams and worksheets
• Laptops with modelling software (Visio or Lucidchart)
• UML tool (e.g., StarUML) and database design tool (MySQL Workbench)
• Demo testing tool (Selenium or JUnit)

Begin with a quick question: “What steps would you take to turn a simple idea into a working app?” Connect this to students’ prior experience of group projects and highlight that today they will master the three core phases that turn ideas into reliable systems. By the end of the lesson they will be able to identify each phase’s purpose, key artefacts, and how to manage the hand‑over between them.

1. Do‑now (5'): Quick quiz on the names and order of SLC phases.
2. Mini‑lecture (10'): Overview of the analysis phase – activities, artefacts, and tools.
3. Group activity (15'): Using a worksheet, students draft a simple requirements specification for a given scenario.
4. Design demo (10'): Teacher models creating an ER diagram and a low‑fidelity UI mock‑up with UML/Prototyping tools.
5. Testing simulation (15'): Teams develop test cases, run a mock test in Selenium, and record defects.
6. Plenary (5'): Recap key points, students complete an exit‑ticket stating one thing they will apply in future projects.

We reviewed how analysis defines “what,” design defines “how,” and testing confirms that the system does it correctly. Students submit an exit ticket summarising the most critical artefact for each phase. For homework, they research an alternative SDLC model (e.g., agile) and prepare a short comparison to the waterfall approach covered today.