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