Understanding dependencies: a study of the coordination challenges in software development

viii Chapter

[1]  Susan A. Dart,et al.  The Past, Present, and Future of Configuration Management , 1992, IFIP Congress.

[2]  S. Fagerhaugh,et al.  Participant Observation , 1979 .

[3]  Charles Richter,et al.  A review of the state of the practice in requirements modeling , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[4]  Jonathan Grudin,et al.  Interactive systems: bridging the gaps between developers and users , 1991, Computer.

[5]  Edward H. Bersoff,et al.  Elements of Software Configuration Management , 1984, IEEE Transactions on Software Engineering.

[6]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[7]  Wayne A. Babich,et al.  Software Configuration Management: Coordination for Team Productivity , 1986 .

[8]  Rebecca E. Grinter,et al.  Software Engineering and CSCW: A Common Research Ground , 1994, ICSE Workshop on SE-HCI.

[9]  Carla Simone,et al.  A notation for malleable and interoperable coordination mechanisms for CSCW systems , 1995, COCS '95.

[10]  Joseph A. Goguen,et al.  Requirements engineering: social and technical issues , 1994 .

[11]  Dennis Heimbigner,et al.  A generic, peer-to-peer repository for distributed configuration management , 1996, Proceedings of IEEE 18th International Conference on Software Engineering.

[12]  Wes Sharrock,et al.  Occasioned practices in the work of software engineers , 1994 .

[13]  David Lorge Parnas,et al.  A rational design process: How and why to fake it , 1986, IEEE Transactions on Software Engineering.

[14]  Paul Quintas.  Social dimensions of systems engineering: people, processes, policies and software development , 1993 .

[15]  Walt Scacchi,et al.  Managing Software Engineering Projects: A Social Analysis , 1984, IEEE Transactions on Software Engineering.

[16]  Kjeld Schmidt,et al.  Taking CSCW Seriously: Supporting Articulation Work * , 1992 .

[17]  Edward H. Bersoff,et al.  Software configuration management, an investment in product integrity , 1980 .

[18]  Stephen B. Compton,et al.  Configuration Management for Software , 1994 .

[19]  Steve Whittaker,et al.  CHI ' 95 MOSAIC OF CREATIVITY • May 7-11 1995 Papers Back To The Future : Pen And Paper Technology Supports Complex Group Coordination , 2011 .

[20]  A. Strauss.  Work and the Division of Labor , 1985 .

[21]  Paul Dourish,et al.  Technomethodology: paradoxes and possibilities , 1996, CHI.

[22]  A. Strauss.  THE ARTICULATION OF PROJECT WORK: AN ORGANIZATIONAL PROCESS , 1988 .

[23]  Thomas T. Samaras,et al.  Fundamentals of configuration management , 1971 .

[24]  Victor R. Basili,et al.  The Future Engineering of Software: A Management Perspective , 1991, Computer.

[25]  Jonathan Grudin,et al.  Groupware and social dynamics: eight challenges for developers , 1994, CACM.

[26]  David Lorge Parnas,et al.  A technique for software module specification with examples , 1972, CACM.

[27]  Dewayne E. Perry,et al.  People, organizations, and process improvement , 1994, IEEE Software.

[28]  Walter F. Tichy.  Programming-in-the-large: past, present, and future , 1992, International Conference on Software Engineering.

[29]  Colin Potts,et al.  Software-engineering research revisited , 1993, IEEE Software.

[30]  Axel Mahler,et al.  Variants: keeping things together and telling them apart , 1995 .

[31]  Brian Fromme.  CM hit list , 1994 .

[32]  Jonathan Grudin,et al.  Why Groupware Succeeds: Discretion or Mandate? , 1995, ECSCW.

[33]  Steve Woolgar,et al.  Rethinking requirements analysis: some implications of recent research into producer-consumer relationships in IT development , 1994 .

[34]  Frederick P. Brooks,et al.  The Mythical Man-Month: Essays on Softw , 1978 .

[35]  Lynda Davies,et al.  An Ethnographic Study of Configuration Management and Documentation Practices , 1992, The Impact of Computer Supported Technologies in Information Systems Development.

[36]  John Bowers,et al.  The work to make a network work: studying CSCW in action , 1994, CSCW '94.

[37]  J. King,et al.  Hardwiring Weak Ties: Interorganizational Computer-Mediated Communication, Occupational Communities, and Organizational Change , 1995 .

[38]  Anselm L. Strauss,et al.  Qualitative Analysis For Social Scientists , 1987 .

[39]  Ralph Johnson,et al.  design patterns elements of reusable object oriented software , 2019 .

[40]  M. Lynne Markus,et al.  Why CSCW applications fail: problems in the adoption of interdependent work tools , 1990, CSCW '90.

[41]  Jonathan Grudin,et al.  Supporting Indirect Collaborative Design With Integrated Knowledge-Based Design Environments , 1992, Hum. Comput. Interact..

[42]  Constance Perin,et al.  Electronic social fields in bureaucracies , 1991, CACM.

[43]  Mark Dowson,et al.  Software process themes and issues , 1993, [1993] Proceedings of the Second International Conference on the Software Process-Continuous Software Process Improvement.

[44]  Walt Scacchi,et al.  Understanding Software Maintenance Work , 1987, IEEE Transactions on Software Engineering.

[45]  Walter F. Tichy,et al.  Rcs — a system for version control , 1985, Softw. Pract. Exp..

[46]  Wanda J. Orlikowski,et al.  Learning from Notes: organizational issues in groupware implementation , 1992, CSCW '92.

[47]  L. Suchman.  Do categories have politics? The language/action perspective reconsidered , 1993 .

[48]  Anas N. Al-Rabadi,et al.  A comparison of modified reconstructability analysis and Ashenhurst‐Curtis decomposition of Boolean functions , 2004 .

[49]  Pamela Jordan.  Basics of qualitative research: Grounded theory procedures and techniques , 1994 .

[50]  Jonathan Grudin,et al.  Why CSCW applications fail: problems in the design and evaluationof organizational interfaces , 1988, CSCW '88.

[51]  David B. Leblang.  The CM challenge: configuration management that works , 1995 .

[52]  Nathan Rosenberg,et al.  Inside the Black Box: Technology and Economics , 1984 .

[53]  P. Kidwell,et al.  The mythical man-month: Essays on software engineering , 1996, IEEE Annals of the History of Computing.

[54]  Lucy A. Suchman,et al.  Plans and Situated Actions: The Problem of Human-Machine Communication (Learning in Doing: Social, , 1987 .

[55]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[56]  Christian Heath,et al.  Collaborative Activity and Technological Design: Task Coordination in London Underground Control Rooms , 1991, ECSCW.

[57]  David Garlan,et al.  Software architecture: practice, potential, and pitfalls , 1994, Proceedings of 16th International Conference on Software Engineering.

[58]  W. Wayt Gibbs,et al.  Software's Chronic Crisis , 1994 .

[59]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

[60]  Rebecca E. Grinter.  Using a configuration management tool to coordinate software development , 1995, COCS '95.

[61]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[62]  A. Strauss,et al.  The discovery of grounded theory: strategies for qualitative research aldine de gruyter , 1968 .

[63]  H. Bernard.  Research Methods in Cultural Anthropology , 1988 .

[64]  Lucy A. Suchman,et al.  Office procedure as practical action: models of work and system design , 1983, TOIS.

[65]  Robert R. Faulkner,et al.  Qualitative Sociology: A Method to the Madness , 1979, Contemporary Sociology: A Journal of Reviews.

[66]  Ruth Milkman,et al.  Microsoft Secrets: How the World's Most Powerful Software Company Creates Technology, Shapes Markets, and Manages People , 1995 .