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.
- 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.Google Scholar
- 2 Adelson, B., and Soloway, E. The role of domain experience in software design. IEEE Trans. Softw. Eng. 11, 11 (Nov. 1985), 1351- 1360. Google ScholarDigital Library
- 3 Allen, T.J. Communication networks in R&D laboratories. R&D Manage. 1, 1 (Jan. 197o), 14-21.Google Scholar
- 4 Allen, T.J. Organizational structure, information technology, and R&D productivity. IEEE Trans. Eng. Manage. 33, 4 (Apr. 1986), 212- 217.Google Scholar
- 5 Barker, R.G. Ecological Psychology: Concepts and Methods for Studying the Environment of Human Behavior. Stanford Univ. Press, Pale Alto, Calif., 1986.Google Scholar
- 6 Barstow, D.R. Domain-specific automatic programming. IEEE Trans. Softw. Eng. 11, 11 (Nov. 1985), 1321-1336. Google ScholarDigital Library
- 7 Belady, L.A. The Japanese and software: Is it a good match? IEEE Comput. 19, 6 {June 1986), 57-61. Google ScholarDigital Library
- 8 Benbasat, I., Goldstein, D.K., and Mead, M. The case research strategy in studies of information systems. MIS Q.//, 3 (Mar. 1987), 369-386. Google ScholarDigital Library
- 9 Boehm, B.W. Software Engineering Economics. Prentice-Hall, Englewood Cliffs, N.J., 1981. Google ScholarDigital Library
- 10 Boehm, B.W. Improving software productivity. IEEE Comput. 20, 9 (Sept. 1987), 43-57. Google ScholarDigital Library
- 11 Boehm, B.W. A spiral model of software development and maintenance. IEEE Comput. 2/, 5 (May 1988}, 61-72. Google ScholarDigital Library
- 12 Bouchard, T.J. Field research methods. In Handb. Ind. Organ. Psychol., Ed. M.D. Dunnette. Rand-McNally, Chicago, (1976): pp. 363-413.Google Scholar
- 13 Brenner, M., Brown, J., and Canter, D. The Research Interview: Uses and Approaches. Academic Press, London, 1985.Google Scholar
- 14 Brooks, F.P. The Mythical Man-Month. Addison-Wesley, Reading, Mass., 1975. Google ScholarDigital Library
- 15 Brooks, F.P. No silver bullet. IEEE Comput. 20, 4 (Apr. 1987), 10-19. Google ScholarDigital Library
- 16 Card, D.N., McGarry, F.E., and Page, G.T. Evaluating software engineering technologies. IEEE Trans. Softw. Eng. 13, 7 (July 19871, 845- 851. Google ScholarDigital Library
- 17 Christiansen, D. On good designers. IEEE Spectrum 24, 5 (May 1987), 25.Google Scholar
- 18 Curtis, B. Measurement and experimentation in software engineering. Prec. IEEE 68, 9 (Sept. 1980), 1144-1157.Google ScholarCross Ref
- 19 Curtis, B. Substantiating programmer variability. Prec. IEEE 69, 7 (July 1981), 846.Google ScholarCross Ref
- 20 Curtis, B. Human Factors in Software Development. 2d ed. IEEE Computer Society, Wash., D.C., 1985. Google ScholarDigital Library
- 21 Curtis, B., Sheppard, S.B., Kruesi-Bailey, E., Bailey, J., and Boehm- Davis, D. Experimental evaluation of software documentation formats. J. Syst. Softw. In press. Google ScholarDigital Library
- 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.Google ScholarCross Ref
- 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.Google Scholar
- 24 DeMarco, T., and Lister, T.A. Peopleware. Dorset, New York, 1987.Google Scholar
- 25 Fenlason, A.F,, Ferguson, G.B., and Abrahamson, A.C. Essentials in Interviewing. Harper & Row, New York, 1962.Google Scholar
- 26 Fischer, B.A. Small Group Decision-Making. 2d ed. McGraw-Hill, New York, 1980.Google Scholar
- 27 Fox, ).M. Software and Its Development. Prentice-Hall, Englewood Cliffs, N.J., 1982. Google ScholarDigital Library
- 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.Google Scholar
- 29 Gould, J.D., and Lewis, C. Designing for usability: Key principles and what designers think. Commun. ACM 28, 3 (Mar. 1985), 300-311. Google ScholarDigital Library
- 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.Google Scholar
- 31 Guindon, R., and Curtis, B. Control of cognitive processes during design: What tools would support software designers? In Conference Proceedings of CHI'88, (Washington, D.C., May 1988}. ACM, New York, 1988, 263-268. Google ScholarDigital Library
- 32 Guindon, R., Krasner, H., and Curtis, B. Breakdowns and processes during the early activities of software design by professionals. In Empirical Studies of Programmers: Second Workshop, Ed. G. Olsen, et al., Ablex, Norwood, N.J., (1987), 65-82. Google ScholarDigital Library
- 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.Google Scholar
- 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.Google Scholar
- 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.Google Scholar
- 36 Kant, E., and Newell, A. Problem solving techniques for the design of algorithms, lnfo. Process. Manage. 28, 1 (Jan. 1984), 97-118.Google Scholar
- 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.Google Scholar
- 38 Kincaid, H.V., and Bright, M. The tandem interview: A trial of the two-interviewer team. Public Opin. Q. 21, {1957), 304-312.Google Scholar
- 39 Klatzky, R.L. Human Memory: Structures and Processes. San Francisco, W.H. Freeman, 1975.Google Scholar
- 40 Kling, R. The web of computing: Computer technology as social organization. Vol. 21, Adv. Comput. Addison-Wesley, Reading, Mass., 1982, pp. 1-90.Google Scholar
- 41 Magnusson, D. Toward a Psychology of Situations: An lnteractionist Perspective. Erlbaum, Hillsdale, N.J., 1981.Google Scholar
- 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.Google ScholarCross Ref
- 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.Google Scholar
- 44 Mills, J.A. A pragmatic view of the system architect. Commun. ACM 28, 7 (July 1985), 708-717. Google ScholarDigital Library
- 45 Moos, R.H., and Insel, P.M. Issues in Social Ecology: Human Milieus. National Press Books, Pale Alto, Calif., 1974.Google Scholar
- 46 Myers, W. MCC: Planning the revolution in software. IEEE Softw. 2, 6 (Nov. 1985), 68-73.Google ScholarDigital Library
- 47 Newell, A. Heuristic programming: Ill structured problems. Vol. 3, In Prog. Oper. Res., Ed. J. Aronofsky. Wiley, New York, 1969, pp. 360- 414.Google Scholar
- 48 Rich, C., and Waters, R.C. Automatic programming: Myths and prospects. IEEE Comput. 21, 8 (Aug. 1988), 40-51. Google ScholarDigital Library
- 49 Rittel, H.W.J., and Webber, M.M. Dilemmas in a general theory of planning. Policy Sci. 4, 1973, 155-169.Google ScholarCross Ref
- 50 Rogers, E.M., and Kincaid, D.L. Communication Networks: Toward a New Paradigm for Research. Free Press, New York, 1981.Google Scholar
- 51 Scacchi, W. Managing software engineering projects: A social analysis. IEEE Trans, Softw. Eng. 10, I (Jan. 1984), 49-59.Google Scholar
- 52 Sells, S.B. An interactionist looks at the environment. Am. Psychol. 18, 11 (Nov. 1963), 696-702.Google ScholarCross Ref
- 53 Sells, S.B. Ecology and the science of psychology. Multivariate Behav. Res. 1, 2 (Feb. 1966), 131-144.Google ScholarCross Ref
- 54 Swanson, E.B., and Beath, C.M. The use of case study data in software management research. J. Syst. Softw. 8, 1 (Jan. 1988), 63-71. Google ScholarDigital Library
- 55 Thamhain, H.J., and Wilemon, D.L. Building high performance engineering project teams. IEEE Trans. Eng. Manage. 34, 3 (Mar. 1987), 130-137.Google Scholar
- 56 Tushman, M.L. Special boundary roles in the innovation process. Adrn. Sci. Q. 22, 4 (Winter 1977), 587-605.Google ScholarCross Ref
- 57 Vosburgh, J., Curtis, B., Wolverton, R., Albert, B., Malec, H., Hoben, S., and Liu, Y. Productivity factors and programming environments. In Proceedings of the Seventh International Conference on Software Engineering (Orlando, Fla., Mar. 1984). IEEE Comput. Soc., Washington, D.C., 1984, pp. 143-152. Google ScholarDigital Library
- 58 Walston, C.E., and Felix, C.P. A method of programming measurement and estimation. IBM Syst. J. 16, 1 (Jan. 1977), 54-73.Google ScholarDigital Library
- 59 Walz, D., Elam, D., Krasner, H., and Curtis, B. A methodology for studying software design teams: An investigation of conflict behaviors in the requirements definition phase. In Empirical Studies of Programmers: Second Workshop, Ed. G. Olsen, et al. Ablex, Norwood, N.J., 1987, pp. 83-99. Google ScholarDigital Library
- 60 Warwick, D.P., and Lininger, C.A. The Sample Survey: Theory and Practice. McGraw-Hill, New York, 1975.Google Scholar
- 61 Weinberg, G.M. The Psychology of Computer Programming. Van Nostrand Reinhold, New York, 1971. Google ScholarDigital Library
- 62 Whyte, W.F. Interviewing in field research. In Human Organization Research, Eds. R.N. Adams and J.J. Priess. 1960.Google Scholar
- 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.Google ScholarDigital Library
Index Terms
- A field study of the software design process for large systems
Recommendations
A Study of Employee Competency in Software Process Management
ISESS '97: Proceedings of the 3rd International Software Engineering Standards Symposium (ISESS '97)This paper presents the findings of a questionnaire survey conducted in a company to assess its employees' competency in software process management. An overview of employee competency and its definition in the context of the survey are given. The ...
Software Project Managers under the Team Software Process: A Study of Competences
Despite the clear relevance of the Information and Communications Technologies ICT market in world economics and the evident lack of success of software projects, organizations devote little effort to the development and maturity of the software project ...
Comments