Your CBA build or portfolio is well under way. Today is a checkpoint: you document what you have made so someone else can understand and judge it, note honestly where AI tools helped, check any ethical or legal issues, and package your evidence cleanly. You are not finishing the whole CBA today. You are making the work ready to be read, and ready for a partner to open and try in about 30 seconds.
Must-finish today: a short overview, your plan in the package, one test note, an AI note, an ethical note, and one package that opens in a single try and is saved to the class location. Extra polish (full renaming, multi-cycle tests, partner open-test detail) comes if time allows.
A judge or classmate who never saw you build this should still be able to follow it. Good documentation means:
Good enough looks like this:
Example overview: "This is a MakeCode Arcade sorting game for first years learning recycling. Open recycling_game in MakeCode Arcade and select Run. Arrow keys move the sorter; score rises when plastic hits the right bin."
Example AI note: "ChatGPT suggested a fix for my sprite overlap bug. I tested the change, kept only the overlap block, and rewrote the comment in my own words."
You will also work against the Features of Quality checklist your teacher shares. Package means one clear folder or portfolio layout a marker can open without guessing. Use the class package layout shown on the board (or your teacher's adapted version of it).
You're previewing this lesson. Get full access to this lesson and hundreds more — each one ready to teach, with interactive activities, printable resources and pupil progress tracking built in.