Choose it. Define one workflow.
Build it. Explain why it works.
Introduction to Programming · Nova SBE
Read the instructions, run the tests, review the change.
Read the product brief, choose a workflow, state what must be true.
The same loop: instructions → build → check → revise.
A mystery with items, locked choices, and multiple endings.
Buy stock, set prices, and run a business for five days.
Book artists and build a feasible festival lineup.
You are in an office.
A key is in the drawer.
The door is locked.
What happens when you try the door?
Inventory: empty.
Rule: the player must have the key.
Inventory: empty. Explain why the route is blocked.
Rejecting an action must not change the saved game.
Office
Inventory: key
Check the inventory.
The condition now holds.
Corridor
Inventory: key
Return to the drawer. Can you collect the key again?
Scenes, item locations, and the rules for each choice.
Current room, inventory, remembered choices, ending.
Store accepted changes. Load them when the app starts again.
A Python variable is not automatically saved. Git history is not player progress.
Five scenes, two items, two endings, saved progress.
Collect a key, open the route, and resume after a restart.
The first task proves one complete workflow. Later tasks complete the brief.
What can the user accomplish?
Which actions and rules must work?
Which parts of the product wait?
What concrete checks prove this task works?
| Starting state | Action | Expected result |
|---|---|---|
| No key | Try locked route | Blocked; state unchanged |
| Key collected | Use route | Corridor; key retained |
| Progress saved | Stop and restart | Same room and inventory |
Review these expectations before AI writes the tests.
Read the proposal against the brief. Then build only the reviewed task.
Where does the user action enter the program?
What makes it valid or invalid?
What is written, and what is loaded later?
Read the test output. Click both paths. Stop the process, restart, and resume.
20 minutes · Open the planning sheet →
Collect → unlock → save → resume.
Buy → trade → reconcile → reload.
Schedule → reject overlap → reload.
Ready? Start your own repo and first-feature branch. Still planning? Test the spec with a neighbour.
Your project: 30% of the course grade. Read the public question template →
W6–W7: build the product. W8: choose a starting point for the team project.