A rational design process: How and why to fake it
IEEE Transactions on Software Engineering
A field study of the software design process for large systems
Communications of the ACM
Fundamentals of software engineering
Fundamentals of software engineering
People, Organizations, and Process Improvement
IEEE Software
Designing engineers
Software engineering (5th ed.)
Software engineering (5th ed.)
Project work: the organisation of collaborative design and development in software engineering
Computer Supported Cooperative Work - Special issue on studies of cooperative design
Collaborative conceptual design: a large software project case study
Computer Supported Cooperative Work - Special issue on studies of cooperative design
Negotiating Boundaries. Configuration Management in Software DevelopmentTeams
Computer Supported Cooperative Work
Recomposition: putting it all back together again
CSCW '98 Proceedings of the 1998 ACM conference on Computer supported cooperative work
Splitting the organization and integrating the code: Conway's law revisited
Proceedings of the 21st international conference on Software engineering
Social, individual and technological issues for groupware calendar systems
Proceedings of the SIGCHI conference on Human Factors in Computing Systems
Computer Supported Cooperative Work
A case study of open source software development: the Apache server
Proceedings of the 22nd international conference on Software engineering
Distance, dependencies, and delay in a global collaboration
CSCW '00 Proceedings of the 2000 ACM conference on Computer supported cooperative work
On the criteria to be used in decomposing systems into modules
Communications of the ACM
The Mythical Man-Month: Essays on Softw
The Mythical Man-Month: Essays on Softw
Microsoft Secrets: How the World's Most Powerful Software Company Creates Technology, Shapes Markets, and Manages People
Object-oriented analysis and design in software project teams
Human-Computer Interaction
Bridging the gap between technical and social dependencies with Ariadne
eclipse '05 Proceedings of the 2005 OOPSLA workshop on Eclipse technology eXchange
Editorial: For the Special issue on Qualitative Software Engineering Research
Information and Software Technology
Proceedings of the 2007 international ACM conference on Supporting group work
An empirical study of software developers' management of dependencies and changes
Proceedings of the 30th international conference on Software engineering
On The Roles of APIs in the Coordination of Collaborative Software Development
Computer Supported Cooperative Work
Software architecture awareness in long-term software product evolution
Journal of Systems and Software
Software reuse through methodical component reuse and amethodical snippet remixing
Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work
Work-to-rule: the emergence of algorithmic governance in Wikipedia
Proceedings of the 6th International Conference on Communities and Technologies
| Hi-index | 0.00 |
In this paper, I revisit theconcept of recomposition – all the work thatdevelopment organizations do to make sure thattheir product fits together and into a broaderenvironment of other technologies. Technologies, such as Configuration Management(CM) systems, can ameliorate some of a softwaredevelopment team's need to engage inrecomposition. However, technologicalsolutions do not scale to address other kindsof recomposition needs. This paper focuses onvarious organizational responses to the needfor recomposition. By organizational response,I mean how individuals engage in recompositionso that the organization can assemble softwaresystems from parts. Specifically, I describehow those responses are manifested in theday-to-day communications and responsibilitiesof individuals throughout the organization. Ialso highlight how changes in an organizationcomplicate recomposition. The paper concludeswith a discussion of three features of softwaredevelopment work that are revealed byrecomposition: the affects of environmentaldisturbances on development work, the types ofdependencies that require recomposition, andthe images of organizations required to managethe recomposition.