Software development: Processes and performance

IBM Systems Journal

Volumn 37, Issue 4, 1998, Pages 552-568

  Sawyer, S ^a   Guinan, P J ^a  

^a NONE

Author keywords

[No Author keywords available]

Indexed keywords

INDUSTRIAL RELATIONS; QUALITY ASSURANCE;

SOFTWARE PRODUCT QUALITY;

SOFTWARE ENGINEERING;

EID: 0032289690     PISSN: 00188670     EISSN: None     Source Type: Journal    
DOI: 10.1147/sj.374.0552     Document Type: Article

References (88)

1. G. Weinberg, The Psychology of Computer Programming, Van Nostrand Reinhold Co., New York (1971).
2. F. Brooks, The Mythical Man-Month: Essays on Software Engineering, Addison-Wesley Publishing Co., Reading, MA (1975).
3. G. Zachary, "Armed Truce: Software in the Age of Teams," Information Technology & People 11, No. 1, 59-66 (1998).
4. S. Roach, "Services Under Siege-the Restructuring Imperative," Harvard Business Review 70,5,82-92 (September-October 1991).
5. J. Hartmanis and L. Herbert, Computing the Future: A Broader Agenda for Computer Science and Engineering, National Academy Press, Washington, D.C. (1992).
6. R. Glass, "The Ups and Downs of Programmer Stress," Communications of the ACM 40, No. 4, 17-19 (1997).
7. R. Stengel, "An Overtaxed IRS," Time 67, No. 20, 58-62 (1997).
8. L. Fisher, "Data Network Suffers Biggest Blackout Ever," The New York Times, C5 (August 8, 1996).
9. L. Fisher, "Human Error and Software Created Data Network Glitch," The New York Times, C1-3 (August 9, 1996).
10. M. Wald, "Future Hazy for Systems to Guide Ship Traffic," The New York Times, C19 (November 25, 1996).
11. K. Lantz, The Prototyping Methodology, Prentice-Hall, Inc., Englewood Cliffs, NJ (1989).
12. D. Card, "The RAD Fad: Is Timing Really Everything?," IEEE Computer 12, No. 5, 19-23 (1981).
13. H. Mills, M. Dyer, and R. Linger, "Cleanroom Software Engineering," IEEE Software 2, No. 9, 19-24 (1984).
14. G. Booch and J. Rumbaugh, Unified Method for Object-Oriented Development, Documentation Set 0.8, Rational Software Corporation (1996).
15. C. Fidge, P. Kearney, and M. Utting, "A Formal Method for Building Concurrent Real-Time Software," IEEE Software 14, No. 2, 99-106 (1997).
16. J. Wood and D. Silver, Joint Application Design, John Wiley & Sons, Inc., New York (1989).
17. D. Freedman and G. Weinberg, Handbook of Walkthroughs, Inspections and Technical Reviews, Little, Brown & Co., Boston, MA (1982).
18. C. Susskind, Understanding Technology, The Johns Hopkins University Press, Baltimore, MD (1973).
19. P. Guinan, J. Cooprider, and S. Sawyer, "The Effective Use of Automated Application Development Tools," IBM Systems Journal 36, No. 1, 124-139 (1997).
20. J. Iivari, "Why Are CASE Tools Not Used?," Communications of the ACM 39, No. 10, 94-103 (1996).
21. W. Curtis, W. Hefley, and S. Miller, The People Capability Maturity Model: P-CMM, Software Engineering Institute Report, CMU/SEI-95-MM-01, Pittsburgh, PA (1995).
22. D. Perry and W. Schafer, "Editorial," Software Process: Improvements and Practice 1, No. 1, 1 (1995).
23. R. Marciniak, Software Engineering, IEEE Press, Thousand Oaks, CA (1994).
24. W. Humphrey, A Discipline for Software Engineering, Addison-Wesley Publishing Co., Reading, MA (1995).
25. W. Humphrey, Managing the Software Process, Addison-Wesley Publishing Co., Reading, MA (1989).
26. M. Paulk, "The Evolution of the SEI's Capability Maturity Model for Software," Software Process: Improvements and Practice 1, No. 1, 3-16 (1995).
27. A. Davis, "It Feels Like Deja Vu All Over Again," IEEE Soft-ware 13, No. 4, 4 (1996).
28. A. Wasserman, "Toward a Discipline of Software Engineering," IEEE Software 13, No. 6, 23-32 (1996).
29. V. Basili and J. Musa, "The Future Engineering of Software: A Management Perspective," Computer 6, No. 5, 90-96 (1991).
30. M. Newman and D. Robey, "A Social Process Model of User-Analyst Relationships," MIS Quarterly 16, 249-266 (1992).
31. R. Hirschheim, H. Klein, and M. Newman, "Information Systems Development as Social Action: Theoretical Perspectives and Practice," Omega 19, 587-608 (1991).
32. D. Robey and R. Newman, "Sequential Patterns in Information Systems Development: An Application of a Social Process Model," ACM Transactions on Information Systems 14, No. 1, 30-63 (1996).
33. S. Sawyer, J. Farber, and R. Spillers, "Supporting the Social Processes of Software Development," Information Technology & People 10, No. 1, 46-62 (1997).
34. W. Curtis, H. Krasner, and N. Iscoe, "A Field Study of the Software Design Process for Large Systems," Communications of the ACM 31, No. 11, 1268-1287 (1988).
35. F. Brooks, "No Silver Bullet: Essence and Accidents of Software Engineering," IEEE Computer 20, No. 4, 10-19 (1987).
36. D. Robey, "Conflict Models for Implementation Research," Applications of Management Science, R. Schultz and M. Ginzberg, Editors, JAI Press, Greenwich, CT (1984).
37. D. Robey, D. Farrow, and C. Franz, "Group Process and Conflict in Systems Development," Management Science 35, No. 10, 1172-1191 (1989).
38. D. Walz, J. Elam, and W. Curtis, "The Dual Role of Conflict in Group Software Requirements and Design Activities," Communications of the ACM 36, No. 10, 63-76 (1993).
39. E. Carmel, "American Hegemony in Packages Software Trade and the 'Culture of Software'," The Information Society 13, No. 1, 124-142 (1997).
40. G. Zachary, Show-stopper!, The Free Press, New York (1994).
41. L. Kirsch, "The Management of Complex Tasks in Organizations: Controlling the Systems Development Process," Information Systems Research 7, No. 1, 1-21 (1996).
42. L. Suchman, "Making Work Visible," Communications of the ACM 38, No. 9, 56-65 (1995).
43. K. Thomas, "Conflict and Conflict Management," Handbook of Industrial and Organizational Psychology, M. Dunnette, Editor, John Wiley & Sons, Inc., New York (1983).
44. L. Pondy, "Organizational Conflict: Concepts and Models," Administrative Science Quarterly 12, 296-320 (1967).
45. J. McGrath, "Time Matters in Groups," Intellectual Teamwork: Social and Technological Foundations of Cooperative Work, J. Galegher, R. Kraut, and C. Egido, Editors, Lawrence Erlbaum Associates, Inc., Hillsdale, NJ (1990), pp. 1-23.
46. J. McGrath and A. Hollingshead, Groups Interacting with Technology, Sage, San Francisco, CA (1993).
47. E. Carmel and S. Sawyer, "Packaged Software Development Teams: What Makes Them Different?," Information Technology & People 11, No. 1, 7-19 (1998).
48. M. Keil and E. Carmel, "Customer-Developer Links in Software Development," Communications of the ACM 38, No. 5, 33-44 (1995).
49. E. Carmel and S. Becker, "A Process Model for Packaged Software Development," IEEE Transactions on Engineering Management 41, 5, 50-61 (1995).
50. M. Cusumano and R. Selby, Microsoft Secrets: How the World's Most Powerful Software Company Creates Technology, Shapes Markets, and Manages People, The Free Press/Simon & Schuster, New York (1995).
51. C. Kemerer, "An Agenda for Research in the Managerial Evaluation of Computer-Aided Software Engineering (CASE) Tool Impacts," Proceedings of the 22nd Annual Hawaii International Conference on Systems Science, IEEE Press (1989), pp. 219-228.
52. W. Delone and E. McLean, "Information Systems Success: The Quest for the Dependent Variable," Information Systems Research 3, No. 1, 60-95 (1992).
53. J. Seidler, "On Using Informants: A Technique for Collecting Quantitative Data and Controlling Measurement Error in Organization Analysis," American Sociological Review 39, No. 12, 816-831 (1974).
54. S. Lee, D. Goldstein, and P. Guinan, "Informant Bias in I/S Design Team Research," Information Systems Research: Contemporary Approaches & Emergent Trends, H. Nissen, H. Klein, and R. Hirschheim, Editors, North-Holland Publishing Co., Amsterdam (1991).
55. J. Henderson and S. Lee, "Managing I/S Design Teams: A Control Theories Perspective," Management Science 38, No. 6, 757-777 (1992).
56. L. James, "Aggregation Bias in Estimates of Perceptual Agreement," Journal of Applied Psychology 67, No. 2, 219-229 (1982).
57. D. Amick and H. Wahlberg, Introductory Multivariate Analysis, MrCutchan Publishing Co., Berkeley, CA (1975).
58. W. Dillon and M. Goldstein, Multivariate Analysis: Methods and Applications, John Wiley & Sons, Inc., New York (1984).
59. J. Cohen and P. Cohen, Applied Multiple Regression/ Correlation Analysis for the Behavioral Sciences, Lawrence Erlbaum Associates, Inc., Hillsdale, NJ (1983).
60. E. Pedhazur and L. Schmelkin, Measurement, Design, and Analysis, Lawrence Erlbaum Associates, Inc., Hillsdale, NJ (1991).
61. R. Bogdan and S. Bicklen, Qualitative Research for Education, Allyn and Bacon, New York (1982).
62. D. Dillman, Mail and Telephone Surveys: The Total Design Method, John Wiley & Sons, Inc., New York (1978).
63. K. Klein, F. Dansereau, and R. Hall, "Levels Issues in Theory Development, Data Collection, and Analysis," Academy of Management Review 19, No. 2, 195-229 (1994).
64. T. DeMarco and T. Lister, Peopleware: Productive Projects and Teams, Dorset House, New York (1987).
65. N. Venkatraman, "The Concept of Fit in Strategy Research: Toward Verbal and Statistical Correspondence," Academy of Management Review 14, No. 3, 423-444 (1989).
66. I. Vessey and P. Sravanapudi, "CASE Tools as Collaborative Support Technologies," Communications of the ACM 38, No. 1, 83-95 (1995).
67. Luqi and J. Goguen, "Formal Methods: Promises and Problems," IEEE Software 14, No. 1, 73-85 (1997).
68. T. DeMarco, Why Does Software Cost So Much? And Other Puzzles of the Information Age, Dorset House, New York (1995).
69. W. Curtis, "Three Problems Overcome with Behavioral Models of the Software Development Process," Proceedings of the 11th International Conference on Software Engineering, IEEE Press (1989), pp. 398-399.
70. M. Cusumano and R. Selby, "How Microsoft Builds Software," Communications of the ACM 40, No. 6, 53-61 (1997).
71. G. Hidding, "Reinventing Methodology: Who Reads It and Why?," Communications of the ACM 40, No. 11, 102-109 (1997).
72. B. Boehm, Software Engineering Economics, Prentice-Hall, Inc., New York (1981).
73. I. Steiner, Group Process and Productivity, Academic Press, New York (1972).
74. D. Cougar, "New Challenges in Motivating MIS Personnel," Journal of Information Systems Management 9, 36-41 (1989).
75. R. Zawacki, "Motivating IT People in the '90s: An Alarming Drop in Job Satisfaction," Software Practitioner 3, No. 6, 1, 4-5 (1993).
76. R. Pressman, "Software Process Perceptions," IEEE Software 13, No. 6, 16-19 (1996).
77. D. Avison and M. Meyers, "Information Systems and Anthropology: An Anthropological Perspective on IT and Organizational Culture," Information Technology & People 8, No. 3, 43-56 (1995).
78. G. Yukl, Leadership in Organizations, Prentice-Hall, Inc., Englewood Cliffs, NJ (1989).
79. P. Nutt, "Tactics of Implementation," Academy of Management Journal 29, No. 2, 230-261 (1986).
80. D. Ancona and D. Caldwell, "Information Technology and Work Groups: The Case of New Product Teams," Intellectual Teamwork: Social and Technological Foundations of Cooperative Work, J. Galegher, R. Kraut, and C. Egido, Editors, Lawrence Erlbaum Associates, Hillsdale, NJ (1990).
81. M. Markus, "Power, Politics, and MIS Implementation," Communications of the ACM 26, No. 6, 430-444 (1983).
82. S. Sawyer and P. Guinan, "Application Development as Culture," Proceedings of the 1995 AIS Americas Conference, M. Ahuja, D. Galletta, and H. Watson, Editors, ACM Press, New York (1995), pp. 54-56.
83. P. Guinan, J. Cooprider, and S. Faraj, "Enabling Software Development Team Performance During Requirements Definition: A Behavioral Versus Technical Approach," Information Systems Research 9, No. 2, 101-125 (1998).
84. S. Green and T. Taber, "The Effects of Three Social Decision Schemes on Decision Group Process," Organizational Performance and Human Behavior 25, 97-106 (1980).
85. J. Hackman, A Set of Methods for the Research on Work Teams, Technical Report 1, Yale School of Organization and Management, New Haven, CT (1982).
86. J. Slocum and H. Sims, Jr., "A Typology for Integrating Technology, Organization, and Job Design," Human Relations 33, No. 3, 193-212 (1980).
87. J. Henderson and J. Cooprider, "Dimensions of I/S Planning and Design Aids: A Functional Model of CASE Technology," Information Systems Research 1, No. 3, 227-252 (1990).
88. R. Kraut and L. Streeter, "Coordination in Software Development," Communications of the ACM 38, No. 3, 69-81 (1995).