Most Mondays are for lectures, and most Wednesdays are primarily for Progress Reports. Depending on the pace, sometimes part of the Wednesday periods may include lecture material too.
Here's the plan:
Week | Monday | Wednesday | Required Reading |
---|---|---|---|
1 | 4/2 Course introduction |
4/4 Development processes |
Textbook chapters 1-2, 20-21, 28, 33-34, and sections 3.1-3.4
+ ProcessLarman.pdf, RequirementsLarman.pdf |
2 | 4/9 Requirements |
4/11 Progress Report 1 |
|
3 | 4/16 Domain analysis (start) |
4/18 Progress Report 2 |
Textbook sections 3.5-3.6, and chapters 4-6
+ ArchitectureLarman.pdf, InteractionLarman.pdf |
4 | 4/23 Analysis (cont.) System design (start) |
4/25 Progress Report 3 |
|
5 | 4/30 Design (cont.) |
5/2 Progress Report 4 |
|
6 | 5/7 Design (cont.) |
5/9 Progress Report 5 |
Textbook chapters 7-9, 22-23
+ Skim chapters 10-19 (focus on key points and coding horrors) |
7 | 5/14 Implementation/testing tips |
5/16 Progress Report 6 |
|
8 | 5/21 Exam |
5/23 Progress Report 7 |
|
9 | 5/28 Holiday |
5/30 Progress Report 8 |
|
10 | 6/4 System demonstrations |
6/6 More demonstrations Evaluate course |