Calendar¶
This reference course uses a 16-week sequence in three acts. The Syllabus defines the learning goals and assessment; this page shows one way to sequence the curriculum.
Act I — Foundations¶
What are the fundamental activities and structures of software engineering?
| Week | Topic |
|---|---|
| 1 | Engineering & GenAI |
| 2 | Process · Teamwork |
| 3 | Requirements · Specification |
| 4 | Architecture · Design |
| 5 | Validation · Engineering Decision-Making and Metrics |
Act II — Delegation and Control¶
How do we delegate realization, govern what is produced, and learn when reality contradicts our expectations?
Act III — Engineering Software Systems¶
What must engineers understand and control as software systems grow, operate, and evolve?
Seven units across nine lectures, developed through one running example: a small campus room reservation service that acquires a new engineering obligation in each unit.
| Week | Topic |
|---|---|
| 11 | Compute Environments & Deployment · Data Management |
| 12 | (Agentic) Technical Debt: Architecture and Dependencies · Performance Engineering |
| 13 | Reliability Engineering · Security I: Threat Modeling |
| 14 | Security II: Controls & Assurance · Thanksgiving recess; no class |
| 15 | Operations, Observability & Incident Response · Course in Review: Engineering Controlled Change |
| 16 | Oral Exam 2 / course closure |
The act fits a term whose teaching weeks end before the final-exam period, with one recess day taken out of week 14. Two units are delivered as single lectures so that nine lectures fit the nine remaining class meetings; adopters with a different recess or a longer term can restore the second lecture of either.
Adopters can compress, expand, or reorder modules. Dates, project milestones, breaks, and institutional requirements belong to the local course offering.