SS 2 Third Term

Lesson objectives

By the end of the week, learners should be able to:

1. Plan a project combining SDLC stages with Python code.
2. Write a requirements document for the project.
3. Produce a Python artifact satisfying the requirements.
4. Add a README describing the project structure.
5. Save both the Python source and the README together.

Key vocabulary

• Mini-project: a small applied task exercising multiple skills.
• SDLC artifact: a product created through the software development life cycle.
• Requirements document: a short spec stating inputs, outputs and behaviour.
• Artifact: any produced output such as code, documentation or a design.
• README: a short file describing a project's structure.
• Source file: the primary code file holding programme logic.
• Structure: the layout of files and directories.
• Combine: merging several components into one deliverable.
• Plan: the documented outline before building.
• Verify: confirming the deliverable satisfies the requirements.

Common misconceptions

• "The project must reuse every skill learned this term." The project exercises enough skills to demonstrate understanding.
• "The README is optional fluff." The README helps reviewers understand the project structure quickly.
• "A draft is final immediately." Drafts are reviewed and refined before submission.

Teacher activities

1. Starter: display a requirements card and a project artifact and ask which reviewer prefers.
2. Explain the project requirement combining SDLC stages with Python.
3. Model drafting a requirements document on paper.
4. Demonstrate producing a Python artifact satisfying those requirements.
5. Add a README describing the project structure.
6. Close with the submission task and exit question.

Student activities

1. Choose the reviewer-preferred item and explain the reason.
2. Explain the project requirement in one paragraph.
3. Draft a requirements document with aim, inputs and outputs.
4. Produce a Python artifact satisfying those requirements.
5. Add a README describing the project structure.
6. Save both the Python source and the README together.
7. Answer the exit question in one sentence about documentation value.

Practical / learning evidence

A requirements document, a Python artifact satisfying the requirements and a README describing the structure. All three submitted together for marking.

Resources and preparation

Computers with Word or Writer and the Python interpreter, blank templates and sample artifacts. Check the computer starts reliably and that the interpreter exists. Provide sample requirements documents for learners needing scaffolding.

Assessment for learning

Inspect the requirements document for sensible aim, inputs and outputs. Check the Python artifact for the required behaviour. Evaluate the README for clear structure description. Flag any learner who treats the README as optional.

Inclusion and access

Provide the requirements template prefilled for aim, inputs and outputs and allow extra time on the Python artifact. Extend confident learners with three more requirements and a second homework revising the README with one strength and one weakness. Homework: extend the project artifact with a second feature satisfying a second requirement.