Unit 2.8 — Synthesis (Game Capstone)

Quarter 2 · ~3.5 contact hours in class + homework Environment: q5play in-app editor.

Renumber note: Was Unit 2.7 before Unit 2.5 was split into 2.5 (Game Saves) and 2.6 (Game States). Cascaded to 2.8.

SLO Focus

SLO 3 PRIMARY Sem 1 evidence (A18.1 Game Capstone) — design + implement + test cycle
Contributes to SLO 1 (lived SDLC)
Contributes to SLO 2 (classes + state machines in a shipped product)

Unit Goal

Students ship a complete game that they designed themselves. The unit is entirely build + test + iterate + showcase. This is the Semester 1 closing artifact — the teacher retains design docs, testing logs, and reflections for dual-enrollment documentation.

Modules in this unit

ID	Title	Primary SLO	Key Artifact
2.8.1	Capstone Game (design → implement → test → iterate)	SLO 1, 2, 3 primary	A18.1 Game Capstone (Sem 1 SLO 3 primary evidence)

Inter-module bridges

Unit 2.1–2.7 → 2.8.1: Every prior q5play unit contributes directly. The capstone rubric requires a custom class (2.2), a Group (2.3), persistent storage (2.5), and multiple game states (2.6).
Unit 2.8 → Sem 2 (Q3): None — clean quarter break. Semester 2 starts with a fresh environment (JSCAD).

Pre-requisite snapshot

All of Q2 content (Units 2.1–2.7).
A capstone design doc drafted as the prior unit's evening homework.

Post-requisite snapshot

Student has shipped a working game.
Student has written design doc, testing log, and 1-page SDLC reflection.
Student has presented a 3-minute showcase to the class.
Teacher's SLO 3 evidence folder contains the A18.1 artifact.

Unit-level assessments

A18.1 Capstone Game (major grade — 15% of course total).
Semester 1 Final exam (scheduled alongside the capstone unit, separate day): 1.5 hour cumulative coverage of JS fundamentals + q5play + OOP across all Semester 1 units.

Module 2.8 — Synthesis — Game Capstone

Lessons in this module