Albrecht, Allan J. 1979. "Measuring Application Development Productivity." Proceedings of the Joint SHARE/GUIDE/IBM Application Development Symposium, October: 83–92.

Albrecht, A., and J. Gaffney. 1983. "Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation." IEEE Transactions on Software Engineering, SE-9 (6): 639–648.

Andriole, Stephen J. 1992. Rapid Application Prototyping. Mass.: QED Information Systems.

Andriole, Stephen J. 1994. "Fast, Cheap Requirements: Prototype or Else!" IEEE Software, March: 85–87.

August, Judy. 1991. Joint Application Design. Englewood Cliffs, N.J.: Yourdon Press.

Augustine, Norman R. 1979. "Augustine's Laws and Major System Development Programs." Defense Systems Management Review: 50–76. Cited in Boehm 1981.

Babich, W. 1986. Software Configuration Management. Reading, Mass.: Addison-Wesley.

Bach, James. 1995. "Enough About Process: What We Need Are Heroes." IEEE Software, March: 96–98.

Baker, F. Terry. 1972. "Chief Programmer Team Management of Production Programming." IBM Systems Journal, vol. 11, no. 1: 56–73.

Baker, F. Terry, and Harlan D. Mills. 1973. "Chief Programmer Teams." Datamation, vol. 19, no. 12 (December): 58–61.

Basili, Victor R., and Albert J. Turner. 1975. "Iterative Enhancement: A Practical Technique for Software Development." IEEE Transactions on Software Engineering SE-1, no. 4 (December): 390–396.

Basili, Victor R., and David M. Weiss. 1984. "A Methodology for Collecting Valid Software Engineering Data." IEEE Transactions on Software Engineering SE-10, no. 6 (November): 728–738.

Basili, Victor R., Richard W. Selby, and David H. Hutchens. 1986. "Experimentation in Software Engineering." IEEE Transactions on Software Engineering SE-12, no. 7 (July): 733–743.

Basili, Victor R., and Frank McGarry. 1995. "The Experience Factory: How to Build and Run One." Tutorial M1, 17th International Conference on Software Engineering, Seattle, Washington, April 24.

Baumert, John. 1995. "SEPG Spotlights Maturing Software Industry." IEEE Software, September: 103–104.

Bayer, Sam, and Jim Highsmith. 1994. "RADical Software Development." American Programmer, June: 35–42.

Beardsley, Wayne. 1995. Private communication: November 17.

Bentley, Jon. 1986. Programming Pearls. Reading, Mass.: Addison-Wesley.

Bentley, Jon. 1988. More Programming Pearls: Confessions of a Coder. Reading, Mass.: Addison-Wesley.

Bersoff, Edward H., and Alan M. Davis. 1991. "Impacts of Life Cycle Models on Software Configuration Management." Communications of the ACM, vol. 34, no. 8 (August): 104–118.

Bersoff, Edward H., et al. 1980. Software Configuration Management. Englewood Cliffs, N.J.: Prentice Hall.

Boddie, John. 1987. Crunch Mode. New York: Yourdon Press.

Boehm, Barry W. 1981. Software Engineering Economics. Englewood Cliffs, N.J.: Prentice Hall.

Boehm, Barry W. 1987a. "Improving Software Productivity." IEEE Computer, September: 43–57.

Boehm, Barry W. 1987b. "Industrial Software Metrics Top 10 List." IEEE Software, vol. 4, no. 9 (September): 84–85.

Boehm, Barry W. 1988. "A Spiral Model of Software Development and Enhancement." Computer, May: 61–72.

Boehm, Barry W. 1991. "Software Risk Management: Principles and Practices." IEEE Software, January: 32–41.

Boehm, Barry W., ed. 1989. Software Risk Management. Washington, D.C.: IEEE Computer Society Press.

Boehm, Barry W., et al. 1984. "A Software Development Environment for Improving Productivity." Computer, 17 (6): 30–44.

Boehm, Barry, et al. 1995. "Cost Models for Future Software Life Cycle Processes: COCOMO 2.0." Annals of Software Engineering, Special Volume on Software Process and Product Measurement, J.D. Arthur and S.M. Henry, eds. Amsterdam: J.C. Baltzer AG, Science Publishers.

Boehm, Barry W., T. E. Gray, and T. Seewaldt. 1984. "Prototyping Versus Specifying: A Multiproject Experiment." IEEE Transactions on Software Engineering SE-10 (May): 290–303. (Also in Jones 1986b.)

Boehm, Barry, and F. C. Belz. 1988. "Applying Process Programming to the Spiral Model." Proceedings of the 4th International Software Process Workshop, May.

Boehm, Barry W., and Philip N. Papaccio. 1988. "Understanding and Controlling Software Costs." IEEE Transactions on Software Engineering, vol. 14, no. 10 (October): 1462–1477.

Boehm, Barry, and Rony Ross. 1989. "Theory-W Software Project Management: Principles and Examples," IEEE Transactions on Software Engineering SE-15 (July): 902–916.

Booch, Grady. 1994. Object Oriented Analysis and Design: With Applications, 2d ed. Redwood City, Calif.: Benjamin/Cummings.

Brady, Sheila, and Tom DeMarco. 1994. "Management-Aided Software Engineering." IEEE Software, November: 25–32.

Brodman, Judith G., and Donna L. Johnson. 1995. "Return on Investment (ROI) from Software Process Improvement as Measured by US Industry." Software Process, August: 36–47.

Brooks, Frederick P., Jr. 1975. The Mythical Man-Month. Reading, Mass.: Addison-Wesley.

Brooks, Frederick P., Jr. 1987. "No Silver Bullets—Essence and Accidents of Software Engineering." Computer, April: 10–19.

Brooks, Frederick P., Jr. 1995. The Mythical Man-Month, Anniversary Edition. Reading, Mass.: Addison-Wesley.

Brooks, Ruven. 1977. "Towards a Theory of the Cognitive Processes in Computer Programming." International Journal of Man-Machine Studies, vol. 9: 737–751.

Bugsy. 1991. TriStar Pictures. Produced by Mark Johnson, Barry Levinson, and Warren Beatty and directed by Barry Levinson.

Burlton, Roger. 1992. "Managing a RAD Project: Critical Factors for Success." American Programmer, December: 22–29.

Bylinsky, Gene. 1967. "Help Wanted: 50,000 programmers." Fortune, March: 141ff.

Card, David N. 1987. "A Software Technology Evaluation Program." Information and Software Technology, vol. 29, no. 6 (July/August): 291–300.

Card, David, and Ed Comer. 1994. "Why Do So Many Reuse Programs Fail?" IEEE Software, September: 114–115.

Carnegie Mellon University/Software Engineering Institute. 1995. The Capability Maturity Model: Guidelines for Improving the Software Process. Reading, Mass.: Addison-Wesley.

Carroll, Paul B. 1990. "Creating New Software Was Agonizing Task for Mitch Kapor Firm." The Wall Street Journal, May 11: A1, A5

Chow, Tsun S., ed. 1985. Tutorial: Software Quality Assurance: A Practical Approach. Silver Spring, Md.: IEEE Computer Society Press.

Coad, Peter, and Edward Yourdon. 1991. Object-Oriented Design. Englewood Cliffs, N.J.: Yourdon Press.

Connell, John, and Linda Shafer. 1995. Object-Oriented Rapid Prototyping. Englewood Cliffs, N.J.: Yourdon Press.

Constantine, Larry L. 1990b. "Objects, Functions, and Program Extensibility." Computer Language, January: 34–56.

Constantine, Larry L. 1995a. Constantine on Peopleware. Englewood Cliffs, N.J.: Yourdon Press.

Constantine, Larry. 1995b. "Under Pressure." Software Development, October: 111–112.

Constantine, Larry. 1996. "Re: Architecture." Software Development, January: 87–88.

Conte, S. D., H. E. Dunsmore, and V. Y. Shen. 1986. Software Engineering Metrics and Models. Menlo Park, Calif.: Benjamin/Cummings.

Costello, Scott H. 1984. "Software Engineering Under Deadline Pressure." ACM Sigsoft Software Engineering Notes, 9:5 October: 15–19.

Curtis, Bill. 1981. "Substantiating Programmer Variability." Proceedings of the IEEE, vol. 69, no. 7 (July): 846.

Curtis, Bill. 1990. "Managing the Real Leverage in Software Productivity and Quality." American Programmer, vol. 3, nos. 7-8 (July-August): 4–14.

Curtis, Bill. 1994. "A Mature View of the CMM." American Programmer, September: 19–28.

Curtis, Bill, et al. 1986. "Software Psychology: The Need for an Interdisciplinary Program." Proceedings of the IEEE, vol. 74, no. 8 (August): 1092–1106.

Cusumano, Michael, and Richard Selby. 1995. Microsoft Secrets: How the World's Most Powerful Software Company Creates Technology, Shapes Markets, and Manages People. New York: Free Press.

Davis, Alan M. 1994. "Rewards of Taking the Path Less Traveled." IEEE Software, July: 100–101, 103.

Dedene, Guido, and Jean-Pierre De Vreese. 1995. "Realities of Off-Shore Reengineering." IEEE Software, January: 35–45.

DeGrace, Peter, and Leslie Stahl. 1990. Wicked Problems, Righteous Solutions. Englewood Cliffs, N.J.: Yourdon Press.

DeMarco, Tom. 1979. Structured Analysis and Systems Specification: Tools and Techniques. Englewood Cliffs, N.J.: Prentice Hall.

DeMarco, Tom. 1982. Controlling Software Projects. New York: Yourdon Press.

DeMarco, Tom. 1995. Why Does Software Cost So Much? New York: Dorset House.

DeMarco, Tom, and Timothy Lister. 1985. "Programmer Performance and the Effects of the Workplace." Proceedings of the 8th International Conference on Software Engineering. Washington, D.C.: IEEE Computer Society Press, 268–272.

DeMarco, Tom, and Timothy Lister. 1987. Peopleware: Productive Projects and Teams. New York: Dorset House.

DeMarco, Tom, and Timothy Lister. 1989. "Software Development: State of the Art vs. State of the Practice." Proceedings of the 11th International Conference on Software Engineering: 271–275.

Dreger, Brian. 1989. Function Point Analysis. Englewood Cliffs, N.J.: Prentice Hall.

Dunn, Robert H. 1984. Software Defect Removal. New York: McGraw-Hill.

Dyer, W. G. 1987. Teambuilding. Reading, Mass.: Addison-Wesley.

Emery, Fred, and Merrelyn Emery. 1975. Participative Design—Work and Community. Canberra: Center for Continuing Education, Australian National University.

Fagan, M. E. 1976. "Design and Code Inspections to Reduce Errors in Program Development." IBM Systems Journal, vol. 15, no. 3: 182–211.

Fagan, M. E. 1986. "Advances in Software Inspections." IEEE Transactions on Software Engineering, July: 744–751.

Fisher, Roger, and William Ury. 1981. Getting to Yes. New York: Penguin Books.

Fitz-enz, Jac. 1978. "Who is the DP Professional?" Datamation, September: 124–129.

Frakes, William B., and Christopher J. Fox. 1995. "Sixteen Questions about Software Reuse." Communications of the ACM, vol. 38, no. 6 (June): 75–87.

Freedman, Daniel P., and Gerald M. Weinberg. 1990. Handbook of Walkthroughs, Inspections and Technical Reviews, 3d ed. New York: Dorset House.

Freeman, Peter, and Anthony I. Wasserman, eds. 1983. Tutorial on Software Design Techniques, 4th ed. Silver Spring, Md.: IEEE Computer Society Press.

Freeman, Peter, ed. 1987. Tutorial: Software Reusability. Washington, D.C.: IEEE Computer Society Press.

Gause, Donald C., and Gerald Weinberg. 1989. Exploring Requirements: Quality Before Design. New York: Dorset House.

Gibbs, W. Wayt. 1994. "Software's Chronic Crisis." Scientific American, September: 86–95.

Gilb, Tom. 1988. Principles of Software Engineering Management. Wokingham, England: Addison-Wesley.

Gilb, Tom, and Dorothy Graham. 1993. Software Inspection. Wokingham, England: Addison-Wesley.

Glass, Robert L. 1992. Building Quality Software. Englewood Cliffs, N.J.: Prentice Hall.

Glass, Robert L. 1993. "Software Principles Emphasize Counterintuitive Findings." Software Practitioner, Mar/Apr: 10.

Glass, Robert L. 1994a. Software Creativity. Englewood Cliffs, N.J.: Prentice Hall PTR.

Glass, Robert L. 1994b. "Object-Orientation is Least Successful Technology." Software Practitioner, January: 1.

Glass, Robert L. 1994c. "IS Field: Stress Up, Satisfaction Down." Software Practitioner, November: 1, 3

Glass, Robert L. 1995. "What are the Realities of Software Productivity/Quality Improvements:" Software Practitioner, November: 1, 4–9.

Gordon, V. Scott, and James M. Bieman. 1995. "Rapid Prototyping: Lessons Learned." IEEE Software, January: 85–95.

Grady, Robert B. 1992. Practical Software Metrics for Project Management and Process Improvement. Englewood Cliffs, N.J.: Prentice Hall PTR.

Grady, Robert B., and Deborah L. Caswell. 1987. Software Metrics: Establishing a Company-Wide Program. Englewood Cliffs, N.J.: Prentice Hall.

Grove, Andrew S. 1983. High Output Management. New York: Random House.

Hackman, J. Richard, and Greg R. Oldham. 1980. Work Redesign. Reading, Mass.: Addison-Wesley.

Hall, Tracy, and Norman Fenton. 1994. "What do Developers Really Think About Software Metrics?" Fifth International Conference on Applications of Software Measurement, November 6–10, La Jolla, Calif., Software Quality Engineering: 721–729.

Hatley, Derek J., and Imtiaz A. Pirbhai. 1988. Strategies for Real-Time System Specification. New York: Dorset House Publishing.

Heckel, Paul. 1991. The Elements of Friendly Software Design. New York: Warner Books.

Henry, Emmanuel, and Benoît Faller. 1995. "Large-Scale Industrial Reuse to Reduce Cost and Cycle Time." IEEE Software, September: 47–53.

Herbsleb, James, et al. 1994. "Software Process Improvement: State of the Payoff." American Programmer, September: 2–12.

Herzberg, Frederick. 1987. "One More Time: How Do You Motivate Employees?" Harvard Business Review, September-October: 109–120.

Hetzel, Bill. 1988. The Complete Guide to Software Testing, 2nd ed. Wellesley, Mass.: QED Information Systems.

Hetzel, Bill. 1993. Making Software Measurement Work: Building an Effective Measurement Program. New York: John Wiley & Sons.

Humphrey, Watts S. 1989. Managing the Software Process. Reading, Mass.: Addison-Wesley.

Humphrey, Watts S. 1995. A Discipline for Software Engineering. Reading, Mass.: Addison-Wesley.

Iansiti, Marco. 1994. "Microsoft Corporation: Office Business Unit," Harvard Business School Case Study 9-691-033, revised May 31. Boston: Harvard Business School.

Jones, Capers. 1986a. Programming Productivity. New York: McGraw-Hill.

Jones, Capers, ed. 1986b. Tutorial: Programming Productivity: Issues for the Eighties, 2nd ed. Los Angeles: IEEE Computer Society Press.

Jones, Capers. 1991. Applied Software Measurement: Assuring Productivity and Quality. New York: McGraw-Hill.

Jones, Capers. 1994. Assessment and Control of Software Risks. Englewood Cliffs, N.J.: Yourdon Press.

Jones, Capers. 1994b. "Revitalizing Software Project Management." American Programmer, June: 3–12.

Jones, Capers. 1995a. "Software Productivity Research Programming Languages Table," 7th ed. March 1995. Burlington, Mass.: Software Productivity Research. (The full table can be accessed on the Internet at http://www.spr.com/library/langtbl.htm.)

Jones, Capers. 1995b. "Patterns of Large Software Systems: Failure and Success." IEEE Software, March: 86–87.

Jones, Capers. 1995c. "Determining Software Schedules." IEEE Software, February: 73–75.

Jones, Capers. 1995d. "Why Is Technology Transfer So Hard?" IEEE Computer, June: 86–87.

Joos, Rebecca. 1994. "Software Reuse at Motorola," IEEE Software, September: 42–47.

Karten, Naomi. 1994. Managing Expectations. New York: Dorset House.

Katzenbach, Jon, and Douglas Smith. 1993. The Wisdom of Teams. Boston: Harvard Business School Press.

Kemerer, C. F. 1987. "An Empirical Validation of Software Cost Estimation Models." Communications of the ACM, 30 (5): 416–429.

Kerr, James, and Richard Hunter. 1994. Inside RAD: How to Build Fully Functional Computer Systems in 90 Days or Less. New York: McGraw-Hill. (Includes an interview with Scott Scholz, among other things.)

Kidder, Tracy. 1981. The Soul of a New Machine. Boston: Atlantic Monthly/Little Brown.

Kitson, David H., and Stephen Masters. 1993. "An Analysis of SEI Software Process Assessment Results, 1987–1991." In Proceedings of the Fifteenth International Conference on Software Engineering: 68–77. Washington, D.C.: IEEE Computer Society Press.

Klepper, Robert, and Douglas Bock. 1995. "Third and Fourth Generation Language Productivity Differences." Communications of the ACM, vol. 38, no. 9 (September): 69–79.

Kohen, Eliyezer. 1995. Private communication: June 24.

Kohn, Alfie. 1993. "Why Incentive Plans Cannot Work," Harvard Business Review, September/October: 54–63.

Korson, Timothy D., and Vijay K. Vaishnavi. 1986. "An Empirical Study of Modularity on Program Modifiability." In Soloway and Iyengar 1986: 168–186.

Krantz, Les. 1995. The National Business Employment Weekly Jobs Rated Almanac. New York: John Wiley & Sons.

Lakhanpal, B. 1993. "Understanding the Factors Influencing the Performance of Software Development Groups: An Exploratory Group-Level Analysis." Information and Software Technology, 35 (8): 468–473.

Laranjeira, Luiz A. 1990. "Software Size Estimation of Object-Oriented Systems." IEEE Transactions on Software Engineering, May.

Larson, Carl E., and Frank M. J. LaFasto. 1989. Teamwork: What Must Go Right; What Can Go Wrong. Newbury Park, Calif.: Sage.

Lederer, Albert L., and Jayesh Prasad. 1992. "Nine Management Guidelines for Better Cost Estimating." Communications of the ACM, February: 51–59.

Lyons, Michael L. 1985. "The DP Psyche." Datamation, August 15: 103–109.

Maguire, Steve. 1993. Writing Solid Code. Redmond, Wash.: Microsoft Press.

Maguire, Steve. 1994. Debugging the Development Process. Redmond, Wash.: Microsoft Press.

Marciniak, John J., and Donald J. Reifer. 1990. Software Acquisition Management. New York: John Wiley & Sons.

Marcotty, Michael. 1991. Software Implementation. New York: Prentice Hall.

Martin, James. 1991. Rapid Application Development. New York: Macmillan.

McCarthy, Jim. 1995a. Dynamics of Software Development. Redmond, Wash.: Microsoft Press.

McCarthy, Jim. 1995b. "Managing Software Milestones at Microsoft." American Programmer, February: 28–37.

McCarthy, Jim. 1995c. "21 Rules of Thumb for Delivering Quality Software on Time." (Available on audiotape or videotape.) Conference Copy (717) 775-0580 (Session 04, Conf. #698D).

McConnell, Steve. 1993. Code Complete. Redmond, Wash.: Microsoft Press.

McCue, Gerald M. 1978. "IBM's Santa Teresa Laboratory—Architectural Design for Program Development." IBM Systems Journal, vol. 17, no. 1: 4–25.

McGarry, Frank, Sharon Waligora, and Tim McDermott. 1989. "Experiences in the Software Engineering Laboratory (SEL) Applying Software Measurement." Proceedings of the Fourteenth Annual Software Engineering Workshop, November 29. Greenbelt, Md.: Goddard Space Flight Center, document SEL-89-007.

Metzger, Philip W. 1981. Managing a Programming Project, 2d ed. Englewood Cliffs, N.J.: Prentice Hall.

Millington, Don, and Jennifer Stapleton. 1995. "Developing a RAD Standard." IEEE Software, January: 54–55.

Mills, Harlan D. 1983. Software Productivity. Boston, Mass.: Little, Brown. 71–81.

Myers, Glenford J. 1978. "A Controlled Experiment in Program Testing and Code Walkthroughs/Inspections." Communications of the ACM, vol. 21, no. 9: 760–768.

Myers, Glenford J. 1979. The Art of Software Testing. New York: John Wiley & Sons.

Myers, Ware. 1992. "Good Software Practices Pay Off—Or Do They?" IEEE Software, March: 96–97.

Naisbitt, John. 1982. Megatrends. New York: Warner Books.

Naisbitt, John, and Patricia Aburdene. 1985. Reinventing the Corporation. New York: Warner Books.

NASA. 1990. Manager's Handbook for Software Development, revision 1. Document number SEL-84-101. Greenbelt, Md.: Goddard Space Flight Center, NASA.

NASA. 1994. Software Measurement Guidebook. Document number SEL-94-002. Greenbelt, Md.: Goddard Space Flight Center, NASA.

O'Brien, Larry. 1995. "The Ten Commandments of Tool Selection." Software Development, November: 38–43.

O'Grady, Frank. 1990. "A Rude Awakening." American Programmer, July/August: 44–49.

Olsen, Neil C. 1995. "Survival of the Fastest: Improving Service Velocity." IEEE Software, September: 28–38.

Page-Jones, Meilir. 1988. The Practical Guide to Structured Systems Design. Englewood Cliffs, N.J.: Yourdon Press.

Parnas, David L. 1972. "On the Criteria to Be Used in Decomposing Systems into Modules." Communications of the ACM, vol. 5, no. 12 (December): 1053–1058.

Parnas, David L. 1976. "On the Design and Development of Program Families." IEEE Transactions on Software Engineering SE-2, 1 (March): 1–9.

Parnas, David L. 1979. "Designing Software for Ease of Extension and Contraction." IEEE Transactions on Software Engineering SE-5 (March): 128–138.

Parnas, David L., Paul C. Clements, and D. M. Weiss. 1985. "The Modular Structure of Complex Systems." IEEE Transactions on Software Engineering, March: 259–266.

Parsons, H. M. 1974. "What Happened at Hawthorne." Science, vol. 183 (March 8): 922–32.

Paulk, M. C., et al. 1993. Key Practices of the Capability Maturity Model, Version 1.1, Software Engineering Institute, CMU/SEI-93-TR-25, February.

Perry, Dewayne E., Nancy A. Staudenmayer, and Lawrence G. Votta. 1994. "People, Organizations, and Process Improvement." IEEE Software, July: 36–45.

Peters, Chris. 1995. "Microsoft Tech Ed '95." March 27.

Peters, Tom. 1987. Thriving on Chaos: Handbook for a Management Revolution. New York: Alfred A. Knopf.

Peters, Tom. 1988. "Letter to the Editor." Inc. magazine, April: 80.

Peters, Tomas J., and Robert H. Waterman, Jr. 1982. In Search of Excellence. New York: Warner Books.

Pfleeger, Shari Lawrence. 1994a. "Applications of Software Measurement `93: A Report from an Observer." Software Practitioner, March: 9–10.

Pfleeger, Shari Lawrence. 1994b. "Attendance Down, Practitioner Value Up at ICSE (May, in Sorrento, Italy). Software Practitioner, November: 9–11.

Pietrasanta, Alfred M. 1990. "Alfred M. Pietrasanta on Improving the Software Process." Software Engineering: Tools, Techniques, Practices, vol. 1, no. 1 (May/June): 29–34.

Pietrasanta, Alfred M. 1991a. "A Strategy for Software Process Improvement." Ninth Annual Pacific Northwest Software Quality Conference, October 7–8, Oregon Convention Center, Portland, Ore.

Plauger, P.J. 1993a. Programming on Purpose: Essays on Software Design. Englewood Cliffs, N.J.: Prentice Hall PTR.

Plauger, P.J. 1993b. Programming on Purpose II: Essays on Software People. Englewood Cliffs, N.J.: Prentice Hall PTR.

Pressman, Roger S. 1988. Making Software Engineering Happen: A Guide for Instituting the Technology. Englewood Cliffs, N.J.: Prentice Hall.

Pressman, Roger S. 1992. Software Engineering: A Practitioner's Approach, 3d ed. New York: McGraw-Hill.

Pressman, Roger S. 1993. A Manager's Guide to Software Engineering. New York: McGraw-Hill.

Putnam, Lawrence H. 1994. "The Economic Value of Moving Up the SEI Scale." Managing System Development, July: 1–6.

Putnam, Lawrence H., and Ware Myers. 1992. Measures for Excellence: Reliable Software On Time, Within Budget. Englewood Cliffs, N.J.: Yourdon Press.

Raytheon Electronic Systems. 1995. Advertisement, IEEE Software, September: back cover.

Rich, Charles, and Richard C. Waters. 1988. "Automatic Programming: Myths and Prospects." IEEE Computer, August.

Rifkin, Stan, and Charles Cox. 1991. "Measurement in Practice." Report CMU/SEI-91-TR-16, Pittsburgh: Software Engineering Institute.

Rothfeder, Jeffrey. 1988. "It's Late, Costly, Incompetent—But Try Firing a Computer System." Business Week, November 7: 164–165.

Rush, Gary. 1985. "The Fast Way to Define System Requirements." Computer-world, October 7.

Russell, Glen W. 1991. "Experience with Inspection in Ultralarge-Scale Developments." IEEE Software, vol. 8, no. 1 (January): 25–31.

Sackman, H., W. J. Erikson, and E. E. Grant. 1968. "Exploratory Experimental Studies Comparing Online and Offline Programming Performance." Communications of the ACM, vol. 11, no. 1 (January): 3–11.

Saiedian, Hossein, and Scott Hamilton. 1995. "Case Studies of Hughes and Raytheon's CMM Efforts." IEEE Computer, January: 20–21.

Scherr, Allen. 1989. "Managing for Breakthroughs in Productivity." Human Resources Management, vol. 28, no. 3 (Fall): 403–424.

Scholtz, et al. 1994. "Object-Oriented Programming: the Promise and the Reality." Software Practitioner, January: 1, 4–7.

Sherman, Roger. 1995a. "Balancing Product-Unit Autonomy and Corporate Uniformity." IEEE Software, January: 110–111.

Sims, James. 1995. "A Blend of Technical and Mediation Skills Sparks Creative Problem-Solving." IEEE Software, September: 92–95.

Smith, P.G., and D.G. Reinertsen. 1991. Developing Products in Half the Time. New York: Van Nostrand Reinhold.

Sommerville, Ian. 1996. Software Engineering, 6th ed. Reading, Mass.: Addison-Wesley.

Standish Group, The. 1994. "Charting the Seas of Information Technology." Dennis, Mass.: The Standish Group.

Symons, Charles. 1991. Software Sizing and Estimating: Mk II FPA (Function Point Analysis). Chichester: John Wiley & Sons.

Tesch, Deborah B., Gary Klein, and Marion G. Sobol. 1995. "Information System Professionals' Attitudes." Journal of Systems and Software, January: 39–47.

Thayer, Richard H., ed. 1990. Tutorial: Software Engineering Project Management. Los Alamitos, Calif.: IEEE Computer Society Press.

Thomsett, Rob. 1990. "Effective Project Teams: A Dilemma, A Model, A Solution." American Programmer, July-August: 25–35.

Thomsett, Rob. 1993. Third Wave Project Management. Englewood Cliffs, N.J.: Yourdon Press.

Thomsett, Rob. 1994. "When the Rubber Hits the Road: A Guide to Implementing Self-Managing Teams." American Programmer, December: 37–45.

Thomsett, Rob. 1995. "Project Pathology: A Study of Project Failures." American Programmer, July: 8–16.

Townsend, Robert. 1970. Up the Organization. New York: Alfred A. Knopf.

Tracz, Will. 1995. Confessions of a Used Program Salesman. Reading, Mass.: Addison-Wesley.

Udell, John. 1994. "Component Software." Byte magazine, May: 45–55.

Valett, J., and F. E. McGarry. 1989. "A Summary of Software Measurement Experiences in the Software Engineering Laboratory." Journal of Systems and Software, 9 (2): 137–148.

van Genuchten, Michiel. 1991. "Why is Software Late? An Empirical Study of Reasons for Delay in Software Development." IEEE Transactions on Software Engineering, vol. 17, no. 6 (June): 582–590.

Vosburgh, J. B., et al. 1984. "Productivity Factors and Programming Environments." Proceedings of the 7th International Conference on Software Engineering, Los Alamitos, Calif.: IEEE Computer Society: 143–152.

Weinberg, Gerald M. 1971. The Psychology of Computer Programming. New York: Van Nostrand Reinhold.

Weinberg, Gerald. 1982. Becoming a Technical Leader. New York: Dorset House.

Weinberg, Gerald M. 1992. Quality Software Management, Volume 1: Systems Thinking. New York: Dorset House.

Weinberg, Gerald M. 1993. Quality Software Management, Volume 2: First-Order Measurement. New York: Dorset House.

Weinberg, Gerald M. 1994. Quality Software Management, Volume 3: Congruent Action. New York: Dorset House.

Weinberg, Gerald M., and Edward L. Schulman. 1974. "Goals and Performance in Computer Programming." Human Factors, vol. 16, no. 1 (February): 70–77.

Whitaker, Ken. 1994. Managing Software Maniacs. New York: John Wiley & Sons.

Wiener, Lauren Ruth. 1993. Digital Woes: Why We Should Not Depend on Software. Reading, Mass.: Addison-Wesley.

Wirth, Niklaus. 1995. "A Plea for Lean Software." IEEE Computer, February: 64–68.

Witness. 1985. Paramount Pictures. Produced by Edward S. Feldman and directed by Peter Weir.

Wood, Jane, and Denise Silver. 1995. Joint Application Development, 2nd ed. New York: John Wiley & Sons.

Yourdon, Edward. 1982, ed. Writings of the Revolution: Selected Readings on Software Engineering. New York: Yourdon Press.

Yourdon, Edward. 1989a. Modern Structured Analysis. New York: Yourdon Press.

Yourdon, Edward. 1989b. Structured Walk-Throughs, 4th ed. New York: Yourdon Press.

Yourdon, Edward. 1992. Decline & Fall of the American Programmer. Englewood Cliffs, N.J.: Yourdon Press.

Yourdon, Edward, and Constantine, Larry L. 1979. Structured Design: Fundamentals of a Discipline of Computer Program and Systems Design. Englewood Cliffs, N.J.: Yourdon Press.

Yourdon, Edward, ed. 1979. Classics in Software Engineering. Englewood Cliffs, N.J.: Yourdon Press.

Zachary, Pascal. 1994. Showstopper! The Breakneck Race to Create Windows NT and the Next Generation at Microsoft. New York: Free Press.

Zahniser, Rick. 1995. "Controlling Software Projects with Timeboxing." Software Development, March.

Zawacki, Robert A. 1993. "Key Issues in Human Resources Management." Information Systems Management, Winter: 72–75.

Zelkowitz, et al. 1984. "Software Engineering Practice in the US and Japan." IEEE Computer, June: 57–66.