Using a configuration management tool to coordinate software development

ABSTRACT

I describe a naturalistic study of one organization's use of a configuration management tool to coordinate the development of a software product. In this organization, the developers use the tool routinely to reduce the complexities of coordinating their development efforts. I examine how the tool provides mechanisms of interaction that let the developers work with each other. I identify four aspects of these mechanisms: difficulties of representing work, the multiple levels that they operate at, the possibilities for coordination they provide, and their role in supporting a model of work.

REFERENCES

• 1: Mark S. Ackerman, Augmenting the organizational memory: a field study of answer garden, Proceedings of the 1994 ACM conference on Computer supported cooperative work, p.243-252, October 22-26, 1994, Chapel Hill, North Carolina, United States [doi>10.1145/192844.193019]
• 2: Wayne A. Babich, Software configuration management: coordination for team productivity, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1986
• 3: S. Bendifallah , W. Scacchi, Understanding software maintenance work, IEEE Transactions on Software Engineering, v.13 n.3, p.311-323, March 1987 [doi>10.1109/TSE.1987.233162]
• 4: Edward H. Bersoff , Stanley Siegel , Vilas Henderson, Software Configuration Management: An Investment in Product Integrity, Prentice Hall Professional Technical Reference, 1980
• 5: John Bowers, The work to make a network work: studying CSCW in action, Proceedings of the 1994 ACM conference on Computer supported cooperative work, p.287-298, October 22-26, 1994, Chapel Hill, North Carolina, United States [doi>10.1145/192844.193030]
• 6: Brooks Jr, F. P. (1974) "The Mythical Man-Month" Datamation (December).
• 7: Caballero, C. (1994) "Life Cycle: Now the Focus in UNIX CM Market" Application Development Trends (August), 49- 54,64,86.
• 8: 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]
• 9: Fischer, G., Grudin, J., Lemke, A., McCall, R., Ostwald, J., Reeves, B., & Shipman, F. (1992) "Supporting Indirect Collaborative Design with Integrated Knowledge-Based Design Environments" Human-Computer Interaction, 7(3), 281-314.
• 10: David Garlan , Dewayne Perry, Software architecture: practice, potential, and pitfalls, Proceedings of the 16th international conference on Software engineering, p.363-364, May 16-21, 1994, Sorrento, Italy
• 11: Elihu M. Gerson , Susan Leigh Star, Analyzing due process in the workplace, ACM Transactions on Information Systems (TOIS), v.4 n.3, p.257-270, July 1986 [doi>10.1145/214427.214431]
• 12: Grudin, J. (1989) "Why groupware applications fail: Problems in design and evaluation" Office: Technology and People, 4(3), 245-264.
• 13: Jonathan Grudin, Computer-Supported Cooperative Work: History and Focus, Computer, v.27 n.5, p.19-26, May 1994 [doi>10.1109/2.291294]
• 14: Heath, C., & Lull, P. (1991) "Collaborative Activity and Technological Design' Task Coordination in London Underground Control Rooms" In European Conference on Computer Supported Cooperative Work.
• 15: John Hughes , Val King , Tom Rodden , Hans Andersen, Moving out from the control room: ethnography in system design, Proceedings of the 1994 ACM conference on Computer supported cooperative work, p.429-439, October 22-26, 1994, Chapel Hill, North Carolina, United States [doi>10.1145/192844.193065]
• 16: Edwin Hutchins, The technology of team navigation, Intellectual teamwork: social and technological foundations of cooperative work, Lawrence Erlbaum Associates, Inc., Mahwah, NJ, 1990
• 17: Ingram, P (1994) "The Market for CM tools" In Proceedings of Unicom Conference London: England. October, 1994
• 18: Jorgenson, D. L. (1989) Participant Observation. Newbury Park, CA: Sage Publications.
• 19: Lubars, M., Potts, C. and C. Richter (1993) "A Review of the State of the Practice in Requirements Modeling" in Proceedings of the International Requirements Engineering Symposium IEEE CS Press, Los Alamitos, CA. 2-14.
• 20: Orlikowski, W. (1991) "Integrated Information Environment or Matrix of Control? The Contradictory Implications of Information Technology" Accounting, Management and Information Technology, 1 (1), 9-42.
• 21: Wanda J. Orlikowski, Learning from Notes: organizational issues in groupware implementation, Proceedings of the 1992 ACM conference on Computer-supported cooperative work, p.362-369, November 01-04, 1992, Toronto, Ontario, Canada [doi>10.1145/143457.143549]
• 22: Jeanne M. Pickering , Rebecca E. Grinter, Software Engineering and CSCW: A Common Research Ground, Proceedings of the Workshop on Software Engineering and Human-Computer Interaction, p.241-250, May 16-17, 1994
• 23: Robinson, M. (1991) "Computer Supported Co-Operative Work: Cases and Concepts" originally appeared in Proceedings of Groupware '91 reprinted in R. M. Baecker (Eds.), Readings in Groupware and Computer-Supported Cooperative Work: Assisting Human-Human Collaboration (29-,$9). San Mateo, C.A.: Morgan Kaufmann.
• 24: Schmidt, K., & Bannon, L. (1992) "Taking CSCW Seriously: Supporting Articulation Work" Computer Supported Cooperative Work: An International Journal, 1(1-2), 7-40.
• 25: Sommerville, I., Rodden, T., Sawyer, P., Bentley, R., & Twidale, M. (1993) "Integrating Ethnography in the Requirements Engineering Process" In A. Finkelstein & S. Fickas (Ed.), Requirements Engineering 1993. San Diego, California January 4-6, 1993: IEEE Computer Society Press.
• 26: Strauss, A. (1985) "Work and the Division of Labor" The Sociological Quarterly, 26(1 ), 1-19.
• 27: Strauss, A. (1988) "The Articulation of project Work: An Organizational Process" The Sociological Quarterly, 29(2),163-178.
• 28: Lucy A. Suchman, Office procedure as practical action: models of work and system design, ACM Transactions on Information Systems (TOIS), v.1 n.4, p.320-328, Oct. 1983 [doi>10.1145/357442.357445]
• 29: Shoshana Zuboff, In the age of the smart machine: the future of work and power, Basic Books, Inc., New York, NY, 1988

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.9 Management
          Subjects: Software configuration management

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.9 Management
          Subjects: Programming teams
      D.2.m Miscellaneous
          Subjects: Reusable software**

  H. Information Systems
  H.5 INFORMATION INTERFACES AND PRESENTATION (I.7)
      H.5.3 Group and Organization Interfaces
          Subjects: Organizational design

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

General Terms:
Design, Human Factors, Management