| chapters to read before class | |||
|---|---|---|---|
| date | McConnell | Sommerville | Topics | 
| 09-27 | introduction | ||
| 09-28 | requirements spec homework meeting (in discussion section) | ||
| 10-02 | (Read homework.) | initial project meeting (in lecture) | |
| 10-04 | 1, 2, 21 | 1–3 | software process models | 
| 10-09 | 3–3.4 | 4 | requirements engineering | 
| 10-11 | 5, 10 | system modeling and engineering | |
| 10-16 | 3.5 | 6, 18, 28 | architectural design | 
| 10-18 | 4, 5, 6 | 7, 17, 19 | component-level design | 
| 10-19 | requirements homework due on CourseWeb | ||
| 10-23 | 7–11 | routines and names | |
| 10-25 | 20 | 24, 25 | quality and change management | 
| 10-30 | 22, 29 | 8 | testing | 
| 11-01 | midterm (in lecture) | ||
| 11-06 | 28 | 22 | project management | 
| 11-08 | 3.6, 27 | 23 | project planning | 
| 11-09 | midterm presentations (in discussion section) | ||
| 11-13 |  11–15  (except 15.1)  | dependability and security | |
| 11-15 | 14–19 | control | |
| 11-20 | 23–26, 31 | 9 | debugging, refactoring, and tuning | 
| 11-27 | 30 | 15.1, 27 | tools and formal methods | 
| 11-29 | 32 | 29, 30 | user interface and documentation | 
| 12-04 | 33–35 | 16, 26 | reuse and process improvement | 
| 12-05 | project final report due (on CourseWeb) | ||
| 12-06 | (Read papers.) | legal aspects. Read: • Kizza JM. Intellectual property rights and computer technology, Texts in Computer Science, Springer, 2010, 103–28 • Samuelson P. Oracle v. Google: are APIs copyrightable? CACM. 2012;55(11):25–7, doi:10.1145/2366316.2366325 • Goldman E. The problems with software patents. Forbes 2012-11-28 • Gaff BM, Smedinghoff TJ, Sor S. Privacy and data security, Computer. 2012;45(3):8–10 • Boothby WH et al. When is a cyberattack a use of force or an armed attack? Computer. 2012;45(8):82–4 | |
| 12-07 | final presentations (in discussion section) | ||