Home > Articles > Programming

  • Print
  • + Share This
This chapter is from the book

This chapter is from the book


Boehm, B. (1981). Software Engineering Economics, Prentice Hall.

Brooks, F. P (1995). The Mythical Man Month: Anniversary Edition, Addison-Wesley. Brown, W. J., Malveau, R. C., McCormick, H. W., and Mowgray, T. J. (1998).

AntiPatterns, Wiley Computer Publishing.

Cockburn, A. and Williams, L. (2000). "The Costs and Benefits of Pair Programming," eXtreme Programming and Flexible Processes in Software Engineering—XP2000, Cagliari, Sardinia, Italy.

Humphrey, W. S. (1995). A Discipline for Software Engineering, Addison-Wesley. Humphrey, W. S. (1997). Introduction to the Personal Software Process, Addison-Wesley.

Jensen, R. W. (1996). "Management Impact on Software Cost and Schedule." Crosstalk, July, http://stsc.hill.af.mil/crosstalk/1996/jul/manageme.asp.

Krantz, M., and Iwata, E. (June 11, 2001). "Companies Bleed Cash when Computers Quit," USA Today, B1.

Nosek, J. T. (1998). "The Case for Collaborative Programming." Communications of the ACM, 105–108.

Weinberg, G. M. (1998). The Psychology of Computer Programming, Silver Anniversary Edition, Dorset House Publishing.

Williams, L. A. (2000). "The Collaborative Software Process," Ph.D. dissertation, University of Utah.

Williams, L., Kessler, R., Cunningham, W., and Jeffries, R. (2000). "Strengthening the Case for Pair-Programming." IEEE Software, July/August 2000, 19–25.

  • + Share This
  • 🔖 Save To Your Account