Proceedings of the 12th ACM SIGSOFT twelfth international symposium on Foundations of software engineering
Sometimes you need to see through walls: a field study of application programming interfaces
CSCW '04 Proceedings of the 2004 ACM conference on Computer supported cooperative work
Process model and awareness in SCM
Proceedings of the 12th international workshop on Software configuration management
Bridging the gap between technical and social dependencies with Ariadne
eclipse '05 Proceedings of the 2005 OOPSLA workshop on Eclipse technology eXchange
Computer Supported Cooperative Work
Information Needs in Collocated Software Development Teams
ICSE '07 Proceedings of the 29th international conference on Software Engineering
Proceedings of the 2007 international ACM conference on Supporting group work
Balancing Agility and Formalism in Software Engineering
The secret life of bugs: Going past the errors and omissions in software repositories
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
Using Developer Activity Data to Enhance Awareness during Collaborative Software Development
Computer Supported Cooperative Work
Using ethnographic methods in software engineering research
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 2
A review of awareness in distributed collaborative software engineering
Software—Practice & Experience - Focus on Selected PhD Literature Reviews in the Practical Aspects of Software Technology
Reducing the effort of bug report triage: Recommenders for development-oriented decisions
ACM Transactions on Software Engineering and Methodology (TOSEM)
Hi-index | 0.00 |
In this paper we report results of an informal field studyof a software development team conducted during aneight week internship at the NASA/Ames Research Center.The team develops a suite of tools called MVP, and iscomposed of 31 co-located software engineers, who design, test, document, and maintain the different MVPtools. We describe the formal and informal approachesused by this group to manage the interdependencies thatoccur during the software development process. Formalapproaches are legitimated by the organization, whereasinformal approaches emerge due to the needs of the developers. We also describe how the software developmenttools used by this team support these approaches andexplore where explicit support is needed. Finally, basedon our findings, we discuss implications for software engineering research.