Date: 18 Oct 1999
Originally collected by: cml@cs.UMD.EDU (Christopher Lott)
Summary: responses to "what should every software engineering have read?"

A. General
   1.  Read about 100 pages of comp.risks
   2.  Frederick P. Brooks, Jr., The Mythical Man-Month, 20th Anniversary
       Edition, Addison Wesley, 1995.
   3.  The anecdotal books of Robert L. Glass, from Computing Trends, P.O.Box
       213, State College, PA 16804, including: "Tales of Computing Folk: Hot
       Dogs and Mixed Nuts", "The Universal Elixir and other Computing Projects
       Which Failed", "The Second Coming: More Computing Projects Which
       Failed", "The Power of Peonage", "Computing Catastrophes", "Computing
       Shakeout", "Software Folklore"
   4.  Richard H. Thayer and Merlin Dorfman (editors), Software Engineering,
       Second Edition, IEEE Computer Society Press, Los Alamitos, CA, 1997.
   5.  Paul W. Oman & Ted G. Lewis, Milestones in Software Evolution, IEEE
       Computing Society, ISBN 0-8186-9033-X.
   6.  J.A. McDermid (editor), Software Engineer's Reference Book, Butterworth-
       Heinemann Ltd., 1991.  ISBN No: 0 750 61040 9.  Focuses on the
       foundations, and subject matter that is not volatile.  The book is
       divided into three major parts: Theory and Mathematics; Methods,
       Techniques, and Technology; Principles of Applications.  For a beginner,
       the first two parts are indispensible.  It does not provide details of
       current research, but points an interested reader to the right sources.
B. Programming in the large
   1.  Grady Booch, Software Engineering with Ada, second edition,
       Benjamin/Cummings, 1987
   2.  Bertrand Meyer.  Object-oriented software construction, Second Edition.
       Prentice-Hall, 1997.  Detailed information available at
       http://www.eiffel.com/doc/oosc.html.
   3.  David L. Parnas, On the Criteria to be Used in Decomposing Systems into
       Modules, Communications of the ACM 15,2 (December 1972).
C. Programming in the small
   1.  Jon Louis Bentley, Writing Efficient Programs, Prentice-Hall, 1982.
   2.  Jon Bentley, Programming Pearls, Addison-Wesley, 1986.
   3.  Jon Bentley, More Programming Pearls, Addison-Wesley, 1988.
   4.  O.-J. Dahl, E.W. Dijkstra, C.A.R. Hoare, Structured Programming,
       Academic Press, 1972.
   5.  Brian W. Kernighan, and P.J. Plauger, Software Tools, Addison-Wesley,
       1976.
   6.  Brian W. Kernighan & P.J. Plauger, The Elements of Programming Style,
       Second Edition, McGraw-Hill, 1978. ISBN 0-07-034207-5.
D. Mathematical Approaches
   1.  Edsger W. Dijkstra, A Discipline of Programming, Prentice-Hall, 1976.
   2.  E.W.Dijkstra.  Selected writings on computing: a personal perspective.
       Springer Verlag, 1982.
   3.  David Gries (editor), Programming methodology. A collection of articles
       by members of IFIP Working Group 2.3. Springer Verlag, 1978.
E. Other
   1.  Tom Demarco and Timothy Lister, Peopleware : Productive Projects and
       Teams, 2nd Ed.  Paperback 2nd edition (February 1, 1999) Dorset House;
       ISBN: 0932633439
   2.  Daniel P. Freedman and Gerald M. Weinberg, Handbook of Walkthoughs,
       Inspections and Technical Reviews, 3rd edition Dorset House Publishing,
       1990, ISBN 0-932633-19-6.  Originally published by Little, Brown &
       Company, 1982: ISBN 0-316-292826.
   3.  Tom Gilb, Principles of Software Engineering Management, Addison-Wesley,
       1988, ISBN 0-201-19246-2
   4.  Glenford J. Myers, The Art of Software Testing, Wiley, 1979.
   5.  Herb Simon, The Sciences of the Artificial, Second Edition, MIT Press,
       1981
   6.  Gerald M. Weinberg, The Psychology of Computer Programming, Silver
       Anniversary Edition.  ISBN: 0-932633-42-0, Dorset House Publishing, 1998

© 2008 FAQS.ORG. All rights reserved.