Skip to main content

Semester 3 workload and progression

Plan 473–688 focused hours for the required semester. These are author planning estimates, not measured learner completion times. The six-week label is a legacy ordering coordinate. At 10 focused hours weekly, round up to about 48–69 study weeks; at 20, 24–35. Calendar waiting for participants and delayed checks can extend elapsed time.

Non-overlapping allocations​

  • Module 1 — 88–127 hours: retain the original 80–115-hour allocation and add the 8–12-hour construction/semantics clinic, including three lessons, experiment and DS1–DS4.
  • Module 2 — 90–130 hours: retain its existing refactoring, compatibility, lab and assessment allocation.
  • Module 3 — 110–161 hours: the 19-lesson core, seven labs, practice, experiments and project take 100–145; the four runtime comparison lessons, EventBus/Editor implementation and BD review add 10–16 after reusing common instruction and evidence. The earlier 70–100-hour module estimate is superseded. Do not add the runtime package's original standalone 18–26-hour estimate again.
  • Module 4 — 65–95 hours: original concepts and selective reading 18–26, original practice and integration 21–31 (core reasoning 10–14, five-group kit 8–12, experiments 3–5; replaces the implementation inventory), core review/repair 8–12, plus composition extension 18–26. The old two-hour quote lab is excluded.
  • Module 5 — 90–130 hours: original design/review concepts, workshops, documentation and history practice 30–44, review-and-repair extension 20–28, discovery/usability/accessibility including retest and transfer 30–44, and remaining core module assessment/repair 10–14. The old 2–3-hour lookup lab is excluded. Extension assessment is already inside its own allocation.
  • Semester integration — 30–45 hours: assemble and verify the existing project packets 12–18, cumulative review and checkpoint 8–12, exam/defense and bounded repair 10–15. Do not rebuild completed module projects or repeat the user study for packaging credit.

The five modules total 443–643 hours; integration adds 30–45, giving 473–688. Reading, practice and module-local evidence preparation belong to module hours. Cross-module verification and final assessment belong to integration. Optional full-book study, substantial prerequisite repair and repeated failed attempts fall outside these ranges; record them rather than hiding them in an optimistic calendar.

Reuse without losing evidence​

Use one evolving project where practical. Link the OOD/refactoring packets and BD, SC and AR lab packets into its evidence index. A separate small fixture is acceptable when the project does not exercise a particular contract. One artifact may support several gates if each claim is independently demonstrated; count its actual work time once. Never claim that the console lookup lab meets the required human-centered/accessibility workflow.

Every two study blocks, record estimated versus actual hours for reading, implementation, evidence and repair. Reforecast from remaining work. Finishing the scheduled hours is not passing; finishing early with independent evidence does not require filler work.

Single progression rule​

The rubric is authoritative. Pass Module 1 DS1–DS4 plus all three C01–C10 sets in Modules 1, 2 and 3, Module 4 C01–C06, all BD1–BD6, SC1–SC6 and AR1–AR6 gates at level 2 or above, and every required HCI/accessibility category. Also meet the semester exam, checkpoint, project and integrity requirements. Aggregate percentages are additional checks, never substitutes for a missing gate.

“Repair required” means incomplete and does not authorize progression. Reassess weak gates with fresh cases and preserve the required delayed rechecks. Label self-assessment honestly; independent review and learner calibration of this curriculum remain pending.