Reading List for Course

  1. W. Gibbs, “Software Chronic Crisis,” Scientific American,” September 1994, pp. 86-95.
  2. Mary Shaw, "Prospects for an Engineering Discipline of Softtware," IEEE Software, Vol. 7, No. 6, November 1990, pp. 15-24.
  3. Frederick Brooks, Jr, "No Silver Bullet: Essence and Accidents of Software Engineering," IEEE Computer, Vol. 20, No. 4, April 1987, pp. 10-19.
  4. B. Boehm, “A Spiral Model of Software Development and Enhancement,” IEEE Computer, Vol. 21, No. 5, May 1988, pp. 61-72.
  5. B. Boehm, "Software Risk Management: Principles and Practices," IEEE Software, Vol.. 8, No. 1, January 1991, pp. 32-41.
  6. Albert L. Lederer and Jayesh Prasad, "Nine Management Guidelines for Better Cost Estimating," Communications of the ACM, Vol. 35, No. 2, February 1992, pp. 51-59.
  7. B. Boehm, “Software Engineering Economics,” IEEE Transactions on Software Engineering, Vol. 10, No. 1, January 1984, pp. 4-21.
  8. B.W. A. Davis, “A Comparison of Techniques for the Specification of External System Behavior,” Communications of the ACM, Vol. 31, No. 9, September 1988, pp. 1098-1115.
  9. B. Boehm, “Verifying and Validating Software Requirements and Design Specifications,” IEEE Software, Vg,. 1, No. 1, January 1984, pp. 75-88.
  10. H. Mills, R.C. Linger, and A.R. Hevner, “Box Structured Information Systems,” IBM Systems Journal, Vol. 26, No. 4, 1987, pp. 395-413.
  11. H. Mills, “The New Math of Computer Programming,” Communications of the ACM, Vol. 18, No. 1, January 1975.
  12. Tim Korson and J.D. McGregor, “Understanding Object-Oriented: A Unifying Paradigm,” Communications of the ACM, Vg,. 33, No. 9, September 1990, pp. 40-60.
  13. M. Fagan, "Design and Code Inspections to Reduce Errors in Program Development," IBM Systems Journal, Vol. 15, No. 3, 1976, pp. 182-211.
  14. M. Fagan, "Advances in Software Inspections," IEEE Transactions on Software Engineering, Vol. 12, No. 7, July 1986, pp. 744-751.
  15. A. Ackerman, L.S. Buchwald, and F.H. Lewski, "Software Inspections: An Effective Verification. Process," IEEE Software, Vol. 6, No. 3, May 1989, pp. 31-36.
  16. Richard Hamlet, “Special Section on Software Testing,” Communications of the ACM, Vg,. 31, No. 6, June 1998, pp.662-667.
  17. J. Musa and A.F. Ackerman, "Quantifying Software Validation: When to Stop Testing?" IEEE Software, Vol,. 6, No. 3, May 1989, pp. 19- 27.
  18. Robert B. Grady, "Successfully Applying Software Metrics," IEEE Computer, Vol,. 27, No. 9, September 1994, pp. 18-26.
  19. P. Hausler, R.C. Linger, and C.J. Trammell, “Adopting Cleanroom Software Engineering with a Phased Approach,” IBM Systems Journal, Vol,. 33, No. 1, 1994, pp. 89-109.
  20. Watts S. Humphrey, "Characterizing the Software Process," IEEE Software, Vol. 5, No. 2, March 1988, pp. 73-79.
  21. Mark C. Paulk, Bill Curtis, Mary Beth Chrissis, and Charles V. Weber, "Capability Maturity Model, Version 1.1," IEEE Software, Vol. 10, No. 4, July 1993, pp. 18-27.
  22. C. Argyris, "Teaching Smart People How to Learn," Harvard Business Review, May/June 1991, pp. 99-109.
  23. David A. Garvin, "Building a Learning Organization," Harvard Business Review, July/August 1993, pp. 78-91.


Philip Hausler, hausler@vnet.ibm.com
Last Update: 2 November 1996