Lecture slides will be posted here week-by-week, in PDF (Adobe Acrobat) format.
[Overview] [Teamwork] [Concept Document Requirements]
Reading: McConnel chapter 4. Chapter 5 is also worth a look, although the risks you face differ somewhat from those discussed by McConnel. Note particularly "buying information" as a risk resolution strategy --- something worth considering, even in a very small project.
Reading: Sommerville chapters 4,5,6,7. The chapters are short.
[Information hiding (examples)] [Notes on Sommerville]
Reading: McConnel pages 415-423 (design for change). Sommerville chapters 12,13,14,15. The Sommerville reading should take us through the next week.
[Process] (I use a fairly small subset of these slides in lecture)
[Process issues] (includes new slides used on 9 May)
Reading: Chapter 1 (Introduction) in Sommerville, especially sections 1.2 through 1.4. Chapter 3, sections 3.2, 3.3 and 3.4 should be useful. McConnell chapter 7.
Reading: Sommerville Chapter 17 (User Interface Design).
Recommended readings:
The Design of Everyday Things. Donald A. Norman. Doubleday 1990. (Previously published in 1988 as The Psychology of Everyday Things.)
Programming as if People Mattered: Friendly Programs, Software Engineering, and other Noble Delusions. Nathaniel S. Borenstein. Princeton University Press, 1991.
[Performance] (no required reading)
*PDF (portable document format) version 2, which requires Acrobat Reader or Acrobat Exchange version 3 or later. The Reader is available for several platforms (Solaris Sparc and x86, Linux, Mac OS, Windows 3.1, 95 and NT, HPUX, etc.) free from Adobe, http://www.adobe.com.
Last update:
Please report broken links and other problems to Michal Young