Note: The course schedule is subject to change. The major project milestones and due dates are reasonably stable, and any changes will be announced in class. The lecture schedule, on the other hand, is likely to change more suddenly depending on what seems most useful for the project, how the lectures and discussion are going, and the phase of the moon.
Week | Date |
Lecture Topics [*]
|
Project
|
---|---|---|---|
1 | Jan 4 | Introduction; Teamwork; Software Development Processes |
Form teams for project 1 |
2 | 11 | Software Development Processes; Architectural Design |
Project 1 Concept Documents due Friday |
3 | 18 | Martin Luther King Holiday (Monday) Configuration Management; Basic Coding Hygiene |
Initial teaching evaluation due Friday |
4 | 25 | Human Computer Interface | Project 1 due Friday Project presentations and discussion Friday Group Member Evaluations due Friday |
5 | Feb 1 | No lecture Monday, Wednesday (Michal is in Hawaii for meetings) Take-home midterm examination due Friday |
Form teams for project 2; turn in brief project proposals on Friday. |
6 | 8 | Requirements elicitation and specification | Project 2 Concept Documents due Friday |
7 | 15 | Documentation | Group member evaluations due Monday Second teaching evaluation due Monday |
8 | 22 | Evolution, maintenance, and reuse | |
9 | Mar 1 | Software quality; analysis and testing | Project 2 due Friday Group Member Evaluations due Friday |
10 | 8 |
|
|
11 | 15 |
|
My tentative plan is to give regular lectures on Monday and Wednesday of each week, and to use Friday for meetings with individual teams except in those weeks in which other activities are planned in class: team formation in weeks 1 and 5, discussions in week 4, and project presentations in week 9.