Coordination in software development

ABSTRACT

Since its inception, the software industry has been in crisis. As Blazer noted 20 years ago, “[Software] is unreliable, delivered late, unresponsive to change, inefficient, and expensive … and has been for the past 20 years” [4]. In a survey of software contractors and government contract officers, over half of the respondents believed that calendar overruns, cost overruns, code that required in-house modifications before being usable, and code that was difficult to modify were common problems in the software projects they supervised [22]. Even today, problems with software systems are common and highly-publicized occurrences.

REFERENCES

• 1: Adams, j,S. fhe structure and dynamics of behavior m organizational boundary roles. In M,D. Dtumette, Ed. Handbook of Industrial and Organizational Psychology. Rand-McNally, Chicago 1976, 1175-1199.
• 2: Allen, T.J, Managing the Flow of Technology. M IT Press, Cambridge, Mass., 1977.
• 3: Blau, P. and Scott, W.R. Formal organizations, Scott, Foresman, San Francisco, 1962.
• 4: Blazer, R. Imprecise program ,specification. Report ISI/RR-75-36, Information Science Institute, December, 1975.
• 5: Barry W. Boehm, Software Engineering Economics, Prentice Hall PTR, Upper Saddle River, NJ, 1981
• 6: Barry W. Boehm, Software Engineering Economics, Prentice Hall PTR, Upper Saddle River, NJ, 1981
• 7: Brewer, M.B. and Kramer, R.M. The psychology of intergroup attitudes and behavior. Annual Review of Psychology 36, 1985, 219-243.
• 8: Frederick P. Brooks, Jr., The mythical man-month (anniversary ed.), Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1995
• 9: Frederick P. Brooks, Jr., No silver bullet: essence and accidents of software engineering, Computer, v.20 n.4, p.10-19, April 1987 [doi>10.1109/MC.1987.1663532]
• 10: Culnan, M.J. Envircmmental scanning: The eflects of task complexity and source accessibility on information gathering behavior. Decis. Sci. 14 (1983), 194-206.
• 11: Bill Curtis , Herb Krasner , Neil Iscoe, A field study of the software design process for large systems, Communications of the ACM, v.31 n.11, p.1268-1287, Nov. 1988 [doi>10.1145/50087.50089]
• 12: Joseph M. Fox, Software and Its Development, Prentice Hall PTR, Upper Saddle River, NJ, 1982
• 13: Georgopoulos, B.S,, and Mann, F.C.. The Community General Hospital. Macmillan, NY, 1962.
• 14: John D. Gould , Clayton Lewis, Designing for usability—key principles and what designers think, Proceedings of the SIGCHI conference on Human Factors in Computing Systems, p.50-53, December 12-15, 1983, Boston, Massachusetts, United States [doi>10.1145/800045.801579]
• 15: Starr Roxanne Hiltz , Murray Turoff, The network nation: human communication via computer, MIT Press, Cambridge, MA, 1993
• 16: Morten Kyng, Designing for cooperation: cooperating in design, Communications of the ACM, v.34 n.12, p.65-73, Dec. 1991 [doi>10.1145/125319.125323]
• 17: McCloud, P. An assessment of tim experimental literature on electronic support of group work: Results of a meta analysis. Human-Comput. Interaction 7, 3 (1992), 251-280.
• 18: Newcomb, T.R. The Acquaintance Proces. Holt, Rinehart and Winston, New York, I961.
• 19: Pelz, D.C. and Andrews, F.M. Scientist. in Organizations: Productive Climates for Research and Development. Wiley, New York, I966.
• 20: Travis, P. Why the AT&T network crashed. Telephony 218, 4 (January 22, 1990), 11.
• 21: Tushman, M.I. Special boundary roles in the innovation process, Admin. Sei. Q. 22, ,i (1977), 587-605.
• 22: U,S. General Accounting Otlice+ Contracting for Computer Software Development-Serious Problems Require Management Attention to Avoid Wasting Additional Million.,. U.S. Department of Commerce, National Technical Information Service, P880-105638, Washington, D.C,, 1979.
• 23: Van de Ven, A.H., Delbecq, A.L., and Koenig, R. Jr. Determinants of coordination modes within orga.nizations+ Amer+ Soc+ Rev. 41 (1976), 322-338.
• 24: Zajonc, R+B. Attitudi.ual effects of mere exposu re..}+ Pe~:v+nudit~ and Soc. Psych. 9, 1968, 1-28.
• 25: Zipf. G.K. Human. Behavior and the Principle of Least Effort. Addison- Wesley, Cambridge, Mass., I949.

INDEX TERMS

Primary Classification:
  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.3 Software Management
          Subjects: Software development

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING

  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS

General Terms:
Management