This table will be updated after each lecture to reflect what really happened in class.
| Week | Date | Lecture Notes [Reading] | Handouts, Problem Sets |
|---|---|---|---|
| 1 | 2/28, T | L1, Course introduction | Syllabus |
| 3/2, H | L2, Software lifecycle, project
discussion [A Brief History of Software Engineering by Amy Ko] | Project pitches, sign up for GitHub Education account | |
| 2 | 3/7, T | L3, Software lifecycle (cont.) | Present project idea |
| 3/9, H | L4, Requirements analysis, use case
modeling, use case activity [Tips for Working Successfully in a Group by Randy Pausch What Google Learned From Its Quest to Build the Perfect Team (Optional) ] | Create Team Assignment due | |
| 3 | 3/14, T | L5, User interfaces, UI mockup
activity [Rapid Prototyping (7 min video)] | |
| 3/16, H | L6, Group presentations | Draft of functional requirements + UI mockups due (tentative) | |
| 4 | 3/21, T | L7, Software architecture [Architecture by Amy Ko] | Due date to schedule individual SWE presentation |
| 3/23, H | L8, UML diagrams [notes] | Software requirements specification due [by 9pm on September 24] | |
| 5 | 3/28, T | L9, Group presentations, UML diagrams (cont'd) | Software requirements specificatiom presentations due |
| 3/30, H | L10, UML Sequence Diagrams,
student1 presenting on company1 [Database design example (note the multiple parts - read phases 1-3 (Optional) Mapping Objects to Relational Databases: O/R Mapping In Detail (Optional) 6 Rules of Thumb for MongoDB Schema Design] | ||
| 6 | 4/4, T | (catch up day or fill it in) | |
| 4/6, H | L11, Design reviews [Falsehoods Programmers Believe About Names by Patrick McKenzie Personal Names Around the World] | Bring data design draft to class for review | |
| 7 | 4/11, T | L12, API design [Web API Design] | Data design + web views due (briefly meet with instructor to show off web views) |
| 4/13, H | L13, Process, student2
presenting on company2 [The Joel Test: 12 steps to better code by Joel Spolsky] | ||
| 8 | 4/18, T | L14, In-class reviews | Software design document due |
| 4/20, H | L15, Group presentations | Software design presentations due | |
| 9 | 4/25, T | L16, Working effectively in software, student3 presenting on company3 [notes] | Project milestone 1 |
| 4/27, H | L17, Testing [Verification by Amy Ko] | Project milestone 2 | |
| 10 | 5/2, T | L18, Bug reporting [Debugging by Amy Ko Painless Bug Tracking by Joel Spolsky] | |
| 5/4, H | L19, Guest lecture by Youngmoo Yang on Zero Class Lab's software development process (tentative) | Project milestone 3 | |
| 11 | 5/9, T | L20, Guest lecture by Justin Hong, Senior Software Engineer at Google (tentative) | |
| 5/11, H | Project milestone discussions and beta release presentations | Project milestone 4: beta release + presentations | |
| 12 | 5/16, T | L22, Databases [notes] | |
| 5/18, H | Databases (cont'd) | ||
| 13 | 5/23, T | L23, Midterm exam | |
| 5/25, H | L25, Guest lecture by Elizabeth Salazar, Senior Engineering Manager at Nurx | ||
| 14 | 5/30, T | L26, In-class code reviews | |
| 6/1, H | L27, Beta release and final presentations | ||
| 15 | 6/6, T | Memorial Day Holiday | |
| 12/8, H | Reading Day | ||
| 16 | 6/15, H | 11:59am, KST: Final project due |