BU CS 511 Team Presentations

Software Engineering -- CS511
Boston University -- Fall 1999

Team Presentations

General Notes

Your talk should be 15 to 20 minutes long (25 minutes maximum). This will allow time for questions and discussion afterward.

Practice your talk out load, standing alone in a room (or with team members). This helps to work out kinks. Time your talk as you practice.

Allow the whole team to review the outline, since the grade will apply to the whole team.

Hand in a hard copy of your outline during class, and email it to me so I can post it on the class web site. Send it in MS Word, HTML, RTF, or ASCII.

What am I looking for?... 1) The right amount of material. If you try to say too much, you will run long or be rushing. If you say too little, you won't use the available time. 2) Some technical depth. Most of us know the broad outlines of these topics already. Give us some technical insight. 3) Your analysis. Show that you thought about this topic and bring your own ideas to the talk. 4) Clarity of presentation. The talk should be well organized, move in a logical sequence, and teach us something.

Sept 8

No presentation.

Sept 15

No presentation.

Sept 22

No presentation.

Sept 29

Team #1 -- Y2K problems (www.mitre.org/research/y2k/docs/PROB.html), Y2K solutions (www.mitre.org/research/cots/Y2K_SOLUTIONS.html)

Here is the outline of the talk.

Oct 6

Team #2 -- Mythical Man Month (book), chaps 1-3.

Here is the outline of the talk.

Oct 13

Team #3 -- Death March (book): preface, chap 1, chap 5 (not email msgs).

Here is the outline of the talk.

Oct 20

Team #4 -- SEI Software Capability Maturity Model (chaps 1-3 of SEI CMM book), plus www.sei.cmu.edu/cmm/cmm.html and www.sei.cmu.edu/sema/pdf/1999aug.pdf. Be sure to include: a summary of the five maturity levels, advantages to CMM, drawbacks to using CMM (search the web for this). Don't be confused by the "other" CMMs. We are only interested in the Software CMM.

Here is the outline of the talk.

Oct 27

Team #5 -- Cleanroom method (SEPA Chap 25) and www.clearlake.ibm.com/MFG/solutions/cleanrm.html.

Nov 3

Team #6 -- Software re-use (SEPA Chap 26), and other readings from the web.

Here is the outline of the talk.

Nov 10

Team #7 -- Human risks from poorly engineered software. See Nancy Leveson's home page (http://sunnyday.mit.edu) for interesting links, and a long list of software accidents at news:comp.risks. Give a couple examples, summarize why these accidents happen, and suggest solutions.

Here is the outline of the talk.

Nov 17

Team #8 -- Risk management (SEPA Chap 6), and other readings from the web.

Here is the outline of the talk.

Nov 24

Thanksgiving vacation. No class.

Dec 1

Team #9 -- Open source development. What is it? What are its advantages and disadvantages. Examples where it has worked. Examples where it has failed(?). Find readings on the web (I can help if you need).

Here is the outline of the talk.

Dec 8

Team #10 -- Software engineering in the health-care field. What are the special problems (and solutions) faced by software development in this area?

Here is the outline of the talk.

Dec 15

Final exam.