Complete product
A complete product means it works end to end for a real user, not only along the path its author remembers to take.
Everything, finished, documented, deployed and defended.
The final capstone is a complete product: designed, built, tested, deployed, documented in a README a stranger could follow, and defended in a viva where the student explains every significant decision.
This is the artefact a student carries forward into further study and applications. It proves capability far better than any mark.
Three core ideas, each taught with worked examples and then practised until it feels obvious.
A complete product means it works end to end for a real user, not only along the path its author remembers to take.
Documentation means a README covering what it does, how to run it, how it is structured and what the known limitations are.
Demo and viva mean presenting live and answering “why this way?” for every important choice.
Open-source maintainers consistently report that a clear README attracts more users than any feature. Explanation is part of the product.
“The code speaks for itself.” It never does. Undocumented projects are abandoned projects, including by the person who wrote them.
Sessions 65–72 of the 72-session year, at two one-hour sessions per week.
Where this module fits, what you will build, and a hands-on starter that gets everyone curious about complete product.
Guided teaching on complete product, worked through together with the teacher.
Independent practice, small challenges and one deliberate mistake to diagnose.
Guided teaching on documentation, building directly on the previous two sessions.
Applied tasks that combine complete product and documentation in one piece of work.
Demo and viva introduced and practised, completing the toolkit needed for the project.
Guided build session for the module project: Deployed capstone application.
Finish, test against the checklist, present the work and explain the decisions behind it.
Every module ends with something the student built themselves and can demonstrate. This is the piece that goes into their portfolio and gets explained out loud at the end of session 72.
Give your README to someone who has never seen the project and ask them to run it, unaided. Every question they ask is a gap.
Students finishing Module 9 can:
The vocabulary introduced here, in plain language:
6 quick questions drawn from this module — vocabulary, the project you build, and a myth-or-fact round. Every wrong answer explains itself, so a mistake still teaches you something.
Tell us your child’s class and what they enjoy. We will suggest the closest program fit—no pressure and no upfront payment.