A field study of the software design process for large systems

ABSTRACT

The problems of designing large software systems were studied through interviewing personnel from 17 large projects. A layered behavioral model is used to analyze how three of these problems—the thin spread of application domain knowledge, fluctuating and conflicting requirements, and communication bottlenecks and breakdowns—affected software productivity and quality through their impact on cognitive, social, and organizational processes.

REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

	1	Adams, J.S. The structure and dynamics of behavior in organizational boundary roles. In Handb. Ind. Organ. Psychot., Ed. M.D. Dunnette. Rand-McNally, Chicago, (1976), pp. 1175-1199.
	2	Beth Adelson , Elliot Soloway, The role of domain experience in software design, IEEE Transactions on Software Engineering, v.11 n.11, p.1351-1360, Nov. 1985 [doi>10.1109/TSE.1985.231883]
	3	Allen, T.J. Communication networks in R&D laboratories. R&D Manage. 1, 1 (Jan. 197o), 14-21.
	4	Allen, T.J. Organizational structure, information technology, and R&D productivity. IEEE Trans. Eng. Manage. 33, 4 (Apr. 1986), 212- 217.
	5	Barker, R.G. Ecological Psychology: Concepts and Methods for Studying the Environment of Human Behavior. Stanford Univ. Press, Pale Alto, Calif., 1986.
	6	David R. Barstow, Domain-specific automatic programming, IEEE Transactions on Software Engineering, v.11 n.11, p.1321-1336, Nov. 1985 [doi>10.1109/TSE.1985.231881]
	7	Laszlo A. Belady, The Japanese and software: is it a good match?, Computer, v.19 n.6, p.57-61, June 1986 [doi>10.1109/MC.1986.1663254]
	8	Izak Benbasat , David K. Goldstein , Melissa Mead, The case research strategy in studies of information systems, MIS Quarterly, v.11 n.3, p.369-386, Sept. 1987 [doi>10.2307/248684]
	9	Barry W. Boehm, Software Engineering Economics, Prentice Hall PTR, Upper Saddle River, NJ, 1981
	10	Barry W. Boehm, Improving software productivity, Computer, v.20 n.9, p.43-57, Sept. 1987 [doi>10.1109/MC.1987.1663694]
	11	Barry W. Boehm, A Spiral Model of Software Development and Enhancement, Computer, v.21 n.5, p.61-72, May 1988 [doi>10.1109/2.59]
	12	Bouchard, T.J. Field research methods. In Handb. Ind. Organ. Psychol., Ed. M.D. Dunnette. Rand-McNally, Chicago, (1976): pp. 363-413.
	13	Brenner, M., Brown, J., and Canter, D. The Research Interview: Uses and Approaches. Academic Press, London, 1985.
	14	Frederick P. Brooks, Jr., The Mythical Man-Month: Essays on Softw, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1978
	15	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]
	16	D. N. Card , F. E. McGarry , G. T. Page, Evaluating software engineering technologies, IEEE Transactions on Software Engineering, v.13 n.7, p.845-851, July 1987 [doi>10.1109/TSE.1987.233495]
	17	Christiansen, D. On good designers. IEEE Spectrum 24, 5 (May 1987), 25.
	18	Curtis, B. Measurement and experimentation in software engineering. Prec. IEEE 68, 9 (Sept. 1980), 1144-1157.
	19	Curtis, B. Substantiating programmer variability. Prec. IEEE 69, 7 (July 1981), 846.
	20	Bill Curtis, Tutorial, Human Factors in Software Development, IEEE Computer Society Press, Los Alamitos, CA, 1990
	21	B. Curtis , S. B. Sheppard , E. Kruesi-Bailey , J. Bailey , D. A. Boehm-Davis, Experimental evaluation of software documentation formats, Journal of Systems and Software, v.9 n.2, p.167-207, February 1, 1989 [doi>10.1016/0164-1212(89)90019-8]
	22	Curtis, B., Soloway, E., Brooks, R., Black, J., Ehrlich, K., and Ramsey, H.R. Software psychology: The need for an interdisciplinary program. Prec. IEEE 74, 8 (Aug. 1986), 1092-1106.
	23	Dailey, R.C. The role of team and task characteristics in R&D team collaborative problem solving and productivity. Manage. Sci. 24, 15 (Nov. 1978), 1579-1588.
	24	DeMarco, T., and Lister, T.A. Peopleware. Dorset, New York, 1987.
	25	Fenlason, A.F,, Ferguson, G.B., and Abrahamson, A.C. Essentials in Interviewing. Harper & Row, New York, 1962.
	26	Fischer, B.A. Small Group Decision-Making. 2d ed. McGraw-Hill, New York, 1980.
	27	Joseph M. Fox, Software and Its Development, Prentice Hall PTR, Upper Saddle River, NJ, 1982
	28	French, J.R.P., and Raven, B. The bases of social power. In Studies in Social Power, Ed. D. Cartwright, Institute for Social Research, Ann Arbor, Mich., 1959, pp. 150-167.
	29	John D. Gould , Clayton Lewis, Designing for usability: key principles and what designers think, Communications of the ACM, v.28 n.3, p.300-311, March 1985 [doi>10.1145/3166.3170]
	30	Guinan, P.J., and Bostrom, R.P. Communication Behaviors of Highly- Rated Versus Lowly-Rated System Developers: A Field Experiment. The Institute for Resesrch on the Management of Information Systems, Indiana Univ., 1987.
	31	R. Guindon , B. Curtis, Control of cognitive processes during software design: what tools are needed?, Proceedings of the SIGCHI conference on Human factors in computing systems, p.263-268, May 15-19, 1988, Washington, D.C., United States [doi>10.1145/57167.57211]
	32	Raymonde Guindon , Herb Krasner , Bill Curtis, Breakdowns and processes during the early activities of software design by professionals, Empirical studies of programmers: second workshop, Ablex Publishing Corp., Norwood, NJ, 1987
	33	Hastie, R. Experimental evidence on group accuracy. In Information Processing and Group Decision-Making, Ed. G. Owen, and B. Grofman. JAI Press, Westport, Conn., 1987, 129-157.
	34	Jeffries, R., Turner, A.A., Poison, P.G., and Atwood, M.E. The processes involved in designing software. In Cognitive Skills and Their Acquisition, Ed. J.R. Anderson. Erlbaum, Hillsdale, N.J., 1981, pp. 255-283.
	35	Jones, T.C. The limits to programmer productivity. In Proceedings of the Joint SHARE/GUIDE/IBM Applications Symposium, SHARE/ GUIDE, Chicago, (1979), pp. 77-82.
	36	Kant, E., and Newell, A. Problem solving techniques for the design of algorithms, lnfo. Process. Manage. 28, 1 (Jan. 1984), 97-118.
	37	Kernaghan, J. A., and Cooke, R.A. The contribution of the group process to successful group planning in R&D settings. IEEE Trans. Eng. Manage. 33, 3 (Mar. 1986), 134-I40.
	38	Kincaid, H.V., and Bright, M. The tandem interview: A trial of the two-interviewer team. Public Opin. Q. 21, {1957), 304-312.
	39	Klatzky, R.L. Human Memory: Structures and Processes. San Francisco, W.H. Freeman, 1975.
	40	Kling, R. The web of computing: Computer technology as social organization. Vol. 21, Adv. Comput. Addison-Wesley, Reading, Mass., 1982, pp. 1-90.
	41	Magnusson, D. Toward a Psychology of Situations: An lnteractionist Perspective. Erlbaum, Hillsdale, N.J., 1981.
	42	Malhotra, A., Thomas, j.C., Carroll, J.M., and Miller, L.A. Cognitive processes in design. Int. J. Man-Machine Stud. 12, (1980), 119-140.
	43	McGarry, F.E. What have we learned in the last six years? In Proceedings of the Seventh Annual Software Engineering Workshop (Greenbelt, Md., Dec. 1982), NASA-GSFC, Greenbelt, Md., 1982.
	44	John A. Mills, A pragmatic view of the system architect, Communications of the ACM, v.28 n.7, p.708-717, July 1985 [doi>10.1145/3894.3897]
	45	Moos, R.H., and Insel, P.M. Issues in Social Ecology: Human Milieus. National Press Books, Pale Alto, Calif., 1974.
	46	Myers, W. MCC: Planning the revolution in software. IEEE Softw. 2, 6 (Nov. 1985), 68-73.
	47	Newell, A. Heuristic programming: Ill structured problems. Vol. 3, In Prog. Oper. Res., Ed. J. Aronofsky. Wiley, New York, 1969, pp. 360- 414.
	48	Charles Rich , Richard C. Waters, Automatic Programming: Myths and Prospects, Computer, v.21 n.8, p.40-51, August 1988 [doi>10.1109/2.75]
	49	Rittel, H.W.J., and Webber, M.M. Dilemmas in a general theory of planning. Policy Sci. 4, 1973, 155-169.
	50	Rogers, E.M., and Kincaid, D.L. Communication Networks: Toward a New Paradigm for Research. Free Press, New York, 1981.
	51	Scacchi, W. Managing software engineering projects: A social analysis. IEEE Trans, Softw. Eng. 10, I (Jan. 1984), 49-59.
	52	Sells, S.B. An interactionist looks at the environment. Am. Psychol. 18, 11 (Nov. 1963), 696-702.
	53	Sells, S.B. Ecology and the science of psychology. Multivariate Behav. Res. 1, 2 (Feb. 1966), 131-144.
	54	E. Burton Swanson , Cynthia M. Beath, The use of case study data in software management research, Journal of Systems and Software, v.8 n.1, p.63-71, January 1988 [doi>10.1016/0164-1212(88)90045-3]
	55	Thamhain, H.J., and Wilemon, D.L. Building high performance engineering project teams. IEEE Trans. Eng. Manage. 34, 3 (Mar. 1987), 130-137.
	56	Tushman, M.L. Special boundary roles in the innovation process. Adrn. Sci. Q. 22, 4 (Winter 1977), 587-605.
	57	J. Vosburgh , B. Curtis , R. Wolverton , B. Albert , H. Malec , S. Hoben , Y. Liu, Productivity factors and programming environments, Proceedings of the 7th international conference on Software engineering, p.143-152, March 26-29, 1984, Orlando, Florida, United States
	58	Walston, C.E., and Felix, C.P. A method of programming measurement and estimation. IBM Syst. J. 16, 1 (Jan. 1977), 54-73.
	59	Joyce J. Elam , Diane B. Walz , Herb Krasner , Bill Curtis, A methodology for studying software design teams: an investigation of conflict behaviors in the requirements definition phase, Empirical studies of programmers: second workshop, Ablex Publishing Corp., Norwood, NJ, 1987
	60	Warwick, D.P., and Lininger, C.A. The Sample Survey: Theory and Practice. McGraw-Hill, New York, 1975.
	61	G. M. Weinberg, The psychology of computer programming, Van Nostrand Reinhold Co., New York, NY, 1988
	62	Whyte, W.F. Interviewing in field research. In Human Organization Research, Eds. R.N. Adams and J.J. Priess. 1960.
	63	Zelkowitz, M., Yeh, R., Hamlet, R., Gannon, J., and Basili, V. Software engineering practices in the U.S. and Japan. IEEE Comput. 17, 6 (June 1984), 57-66.