SS 3 First Term

Lesson objectives

By the close of the week, candidates should be able to:

1. List the six SDLC phases.
2. Name two deliverables per phase.
3. Compare waterfall and agile.
4. Write a test case.
5. Justify a model for a school system.

Key vocabulary

• SDLC: the staged process for building software.
• Requirement: a statement of what the system must do.
• Feasibility study: an assessment of technical and economic viability.
• Test case: a documented input, expected and actual result.
• Maintenance: correcting software after release.

Common misconceptions

• "Testing happens only after coding." Tests are written from requirements and run throughout.
• "Maintenance means repairing hardware." Software maintenance covers fixes and updates.

Teacher activities

1. Starter: list three causes of failure.
2. Teach the six phases.
3. Compare waterfall and agile.
4. Model three login test cases.
5. Set the result-system scenario.
6. Review two justifications.

Student activities

1. List three failure causes.
2. Order the phase cards.
3. Match deliverables to phases.
4. Write three login test cases.
5. Choose a model.
6. Defend the choice.

Phase	Main deliverable
Requirements	agreed requirement list
Design	data and screen designs
Implementation	working program code
Testing	test log and defect list
Deployment	installed system and guide
Maintenance	change and support record

Practical / learning evidence

ss3_test_plan_nwosu.docx lists six phases with two deliverables, a model comparison, three login test cases and a justified choice. Each case needs input, expected and actual results.

Resources and preparation

Phase cards, projector and a test-case template. Offline route: cards and paper test logs with the same rubric.

Assessment for learning

Check phase order and deliverable fit. Award marks for a complete test case.

Inclusion and homework

Supply phase cards with two starters; extend others to the cost of a late defect. Homework: add a wrong-password test case.