CS 851: FORENSIC SOFTWARE ENGINEERING

FALL 2002

John C. Knight with Kimberly S. Hanks
Department of Computer Science



Presentation Schedule





Class meetings will usually include a presentation by a student of (an) assigned chapter(s) or paper(s). These presentations are normally expected to run 50-60 minutes plus discussion, that is, a class period (though occasionally some will be shorter; presenters will be notified in advance). When you are scheduled to present, be sure to address at least the following issues as applied to your assigned material:
  • coverage of content (prioritize if necessary)
  • connection to forensic software engineering (is it about software itself, or an industry in which software plays a role, or does it provide a model or theory useful in the development of FSE, etc.?)
  • implications for how we study failure, investigate accidents, or should improve the software process
In addition, you must provide discussion leadership, that is, you must drive the discussion though statements and questions that enable your audience to participate, gain the exposure and understanding you want them to gain, and ideally generate insights benefiting the entire class.

Within 48 hours following your presentation, you must further provide a 200-300 word abstract-style summary highlighting the main points of value as well as insights contributed or arrived at by the class. This summary may be emailed in ASCII and will be posted on the webpage. Your slides should also be submitted and will be posted as well.

Presentations cumulatively account for 25% of your course grade.
Participation when you are not presenting accounts for 15% of your course grade.


Wednesday, Aug 28
  • Kimberly Hanks: Course Introduction
    [slides]
Monday, Sept 2 Wednesday, Sept 4
  • Elisabeth Strunk: Forensic Software Engineering (Johnson)
    [summary] [slides]
Monday, Sept 9 (rescheduled to Wed 9/11) Wednesday, Sept 11 (rescheduled to Fri 9/13) Monday, Sept 16 Wednesday, Sept 18 Monday, Sept 23 Wednesday, Sept 25
  • Nate Paul: Strauch, Perrow postscript (not the afterword!)
    [summary] [slides]
Monday, Sept 30
  • Jim Gunderson: Petroski, introduction and ch.2, ch.3
    [summary] [slides]
Wednesday, Oct 2 Monday, Oct 14 Wednesday, Oct 16
  • Tony Aiello: Petroski, ch.9, ch.10, ch.11
Friday, Oct 18 Monday, Oct 21
  • Mike Smoot: Reason, chapter 3
Wednesday, Oct 23 Monday, Oct 28
  • Pavel Sorokin: Reason, chapter 7
Wednesday, Oct 30
  • Billy Greenwell and Elisabeth Strunk: Reason, chapter 8
    [summary] [slides]
Monday, Nov 4
  • Joel Winstead and Gus Scheidt: Leveson (Safeware), chapters 5 and 6
    [summary] [slides]
Wednesday, Nov 6
  • Phil Varner and Dave Larochelle: Kletz, chapters 1, 2, and 3
    [summary] [slides]
Monday, Nov 11
  • Mike Tashbook and Nate Paul: Kletz, chapters 19 and 21
    [summary] [slides]
Wednesday, Nov 13
  • Rajat Tikoo: Leveson paper: "High-Pressure Steam Engines and Computer Software"
    [summary] [slides]
Monday, Nov 18
  • Michael Holloway from NASA Langley Research Center to visit and present on causality (packet)
    [slides]
Wednesday, Nov 20
  • Ganesh Pai and Hichem Boudali: Leveson (Safeware), chapter 12
Monday, Nov 25
  • Tony Aiello and Mike Smoot: Peterson, preface and chapters 1 and 3
Monday, Dec 2
  • Xiaohui Chen and Pavel Sorokin: Peterson, chapters 4 and 6
Wednesday, Dec 4
  • Jim Gunderson: Peterson, chapters 7, 8, and the afterword
No further presentations are scheduled at this time.


Last updated 12/17/02 Maintained by Kimberly S. Hanks