| Wk | Date | Due | Read | Who | Topic |
| 0 | 9/2 | B | Introduction to the course | ||
| 0 | 9/3 | 1-3 | M | Problem statements | |
| 1 | 9/6 | H1 | M | Brainstorming | |
| 1 | 9/7 | 4 | S | Teaming | |
| 1 | 9/9 | H2 | 5-7 | M | Requirements process |
| 1 | 9/10 | 8 | M | Elicitation and interviewing | |
| 2 | 9/13 | H3 | 9-12 | M | Interviewing a client |
| 2 | 9/14 | 13 | S | Story boards | |
| 2 | 9/16 | H4 | M | Requirements workshops | |
| 2 | 9/17 | 14 | M | Use cases 1 | |
| 3 | 9/20 | H5 | 21 | M | Use cases 2 |
| 3 | 9/21 | 22 | S | Non-functional requirements | |
| 3 | 9/23 | P1 | B | Client: interviewing | |
| 3 | 9/24 | M | Client: interviewing | ||
| 4 | 9/27 | P2 | 16-17 | S | Vision statement |
| 4 | 9/28 | M | Paper prototyping | ||
| 4 | 9/30 | No class: WWW@10 | |||
| 4 | 10/1 | No class: WWW@10 | |||
| 5 | 10/4 | H6 | M | Review | |
| 5 | 10/5 | M | Exam 1 | ||
| 5 | 10/7 | P3 | B | Client: use cases, paper prototypes | |
| 5 | 10/8 | M | Client: use cases, paper prototypes | ||
| 6 | 10/11 | P4 | 18-19 | M | Scope |
| 6 | 10/12 | 24 | M | Other notations | |
| Break |
|||||
| 7 | 10/18 | P5 | 20 | S | Requirements documents |
| 7 | 10/19 | 23 | S | Ambiguity and specificity | |
| 7 | 10/21 | H9 | 25-26 | S | Elaboration of use cases |
| 7 | 10/22 | 27-28 | S | Traceability | |
| 8 | 10/25 | H10 | 29 | M | Quality |
| 8 | 10/26 | 30-31 | M | Agile methods | |
| 8 | 10/28 | P6 | B | Client: requirements document | |
| 8 | 10/29 | M | Client: requirements document | ||
| 9 | 11/1 | P7 | 15 | M | Product lines 1 |
| 9 | 11/2 | M | Product lines 2 | ||
| 9 | 11/4 | H11 | M | Review | |
| 9 | 11/5 | M | Exam 2 | ||
| 10 | 11/8 | P8 | B | Presentations (teams 2, 3, 8, 9, 14 and 15) | |
| 10 | 11/9 | B | Presentations (teams 1, 6, 7, 12, and 13) | ||
| 10 | 11/11 | B | Presentations (teams 4, 5, 10 and 11) | ||
| 10 | 11/12 | P9 | No class | ||