CSC2123H
Book Presentations

What you must do

You must select a book, have it approved by the instructor, read it carefully cover-to-cover, and think critically about it. You are then to work up a presentation (using overhead slides) to give to the class. The presentation should explain what the book is saying, and critically evaluate the ideas. The presentation should take approximately 1/2 hour. As soon as you are ready, we will schedule you in.

Types of Books

You may select any book you wish on the topic of managing the software organization or something closely related. Avoid books that deal with specific technologies and books that deal with specific acitivites, such as requirmeents, programming, and so on. Books on managing these activities, however, are ok. Do not choose a book that you have previously read.

Suggestions

Please find some suggested books below. The books on the list are pre-approved. It is not necessary that you choose from this list. However, if you choose a boook not on the list, please ensure you get it approved by the instructor. Do not choose a book that has already been taken by somebody else.
 
nameauthorspublisherdatetaken by
Anti PatternsBrown et. al.Wiley1998
Applied Software Measurement, 2nd ed.Capers JonesMcGraw-Hill1991
Becoming a Technical LeaderGerald WeinbergDorset House1986
the Capability Maturity ModelPaulk et. al.Addison-Wesley1994
Crossing the ChasmGeoffrey MooreHarperBusiness1991
the DeadlineTom DeMarcoDorset House1997
Death MarchEdward YourdonPrentice Hall1997
Debugging the Development ProcessSteve MaguireMicrosoft Press1994
Decline & Fall of the American ProgrammerEdward YourdonPrentice-Hall1992
a Discipline for Software EngineeringWatts HumphreyAddison-Wesley1995
Dynamics of Software DevelopmentMcCarthyMicrosoft Press1995
Estimating Software CostsCapers JonesMcGraw-Hill1998
Exploiting ChaosOlsonVan Nostrand1993
Extreme Programming ExplainedBeckAddison-Wesley2000
Global Software TeamsCarmelPrentice Hall1999
the Healthy Software ProjectNorris et. al.Wiley1993
the H.P. Way   
Into the TornadoGeoffrey Moore  
Introduction to the Team Software ProcessWatts HumphreyAddison Wesley2000
Introduction to the Personal Software ProcessWatts HumphreyAddison Wesley1997
Introduction to Software Project Management and Quality AssuranceInce et. al.McGraw-Hill1993
Managing Programming PeopleMetzgerPrentice-Hall1987
Managing the Software ProcessWatts HumphreyAddison-Wesley1989
Managing the Testing ProcessBlackMicrosoft Press1999
the Mythical Man-MonthBrooksAddison-Wesley1975
On Time, Within Budget, 2nd ed.BennatanWiley1995
PeoplewareDeMarco & ListerDorset House1987
Practical Project ManagementMeilir Page-JonesDorset House1985
Practical Software MeasurementHughesMcGraw-Hill2000
Project Management: Best Practices for IT ProfessionalsMurch  
Program Smarter, Not HarderJohnson et. al.McGraw-Hill1995
Quality Software Management Vol.1Gerald WeinbergDorset House1992
Rapid DevelopmentSteve McConnellMicrosoft Press1996
Rise & Resurrection of the American ProgrammerEdward YourdonPrentice Hall1996
Seventy-Seven Sure-Fire Ways to Kill a Software ProjectFerry 2000
Software Assessments, Benchmarks, and Best PracticesCapers JonesAddison-Wesley2000
Software Cost Estimation with COCOMO IIBoem et. al.Prentice Hall2000
Software Configuration ManagementBerlackWiley1992
Software Engineering Metrics and ModelsConte et. al.Benjamin/Cummings1986
Software Inspection PorcessEbenau, StraussMcGraw Hill1994
Software MetricsGrady, CaswellPrentice-Hall1987
Software Project ManagementRoyceAddison-Wesley1998
Software Project Survival GuideSteve McConnellMicrosoft Press1998
Secrets of Software SuccessHoch et. al.McKinsey2000
Understanding the Professional ProgrammerGerald WeinbergDorset House1988
Why Does Software Cost so Much?Tom DeMArcoDorset House1995