SE 362 Winter 2005
Software Project Management

1. The Tar Pit
2. The Mythical Man-Month

3. The Surgical Team

4. Aristocracy, Democracy and System Design
   
5. The Second-System Effect

6. Passing the Word
7. Why Did the Tower of Babel Fail?

8. Calling the Shot
9. Ten Pounds in a Five-Pound Sack

10. The Documentary Hypothesis
11. Plan to Throw One Away

12. Sharp Tools
13. The Whole and the Parts

14. Hatching a Catastrophe
15. The Other Face

16. No Silver Bullet — Essence and Accident in Software Engineering

Textbook

Notes

Tutorials

Lecture resources

Project resources

Midterm

All corrections and appeals must be:

• Prepared in hardcopy (*not* email!)
• Stapled to the front of the exam paper
• Submitted:
  • In person, or under Norm's office door
  • After the solutions are discussed in class
  • Before 4:30 pm Wed Mar 9
  • Only once per paper

Corrections: All clerical errors, no matter how small, will be corrected, without question.

Appeals: Differences in opinion about what comprises a correct solution, or about how a solution was evaluated by the marker, must meet the following criteria before we will consider them.

Significant: The change in grade that will result from each individual change must equal or exceed 3/90 (i.e., 1% of the course).

Substantial: The basis for the appeal must be clearly described in writing, with accompanying figures or calculations, as appropriate.

Corroborated: Appeals that cite other students' solutions for comparison must include photocopies of the relevant pages from the other paper, with the owner's name and student number indicated.

Papers submitted for appeal might be entirely remarked. Remarking might reveal other errors that compensate for or exceed the value of the submitted appeal. Your paper's overall grade might actually go down.

Final