| chapters to read before class |
date | McConnell | Sommerville | Topics |
09-22 | | | introduction |
09-23 | | | requirements spec homework meeting (in discussion section) |
09-27 | 1, 2, 21 | 1–3 | software process models |
09-29 | | | initial project meeting (in lecture) |
10-04 | 3–3.4 | 4 | requirements engineering |
10-06 | | 5, 10 | system modeling and engineering |
10-07 | | | requirements spec due (on CourseWeb) |
10-11 | 3.5 | 6, 18, 28 | architectural design |
10-13 | 4, 5, 6 | 7, 17, 19 | component-level design |
10-18 | 7–11 | | routines and names |
10-20 | 20 | 24, 25 | quality and change management |
10-25 | 22, 29 | 8 | testing |
10-27 | | | midterm (in lecture) |
11-01 | 28 | 22 | project management |
11-03 | 3.6, 27 | 23 | project planning |
11-04 | | | midterm presentations (in discussion section) |
11-08 | | 11–15 | dependability and security |
11-10 | 14–19 | | control |
11-15 | 23–26, 31 | 9 | debugging, refactoring, and tuning |
11-17 | 30 | 27 | tools and formal methods |
11-22 | 32 | 29, 30 | user interface and documentation |
11-29 | 33–35 | 16, 26 | reuse and process improvement |
11-30 | | | project final report due (on CourseWeb) |
12-01 | | | legal aspects (read: Kizza JM. Intellectual property rights and computer technology, Texts in Computer Science, Springer, 2010, 103–28) |
12-02 | | | final presentations (in discussion section) |