Categorizing developer information needs in software ecosystems

Authors:
Nicole Haenni;Mircea Lungu;Niko Schwarz;Oscar Nierstrasz
Affiliations:
University of Bern, Switzerland;University of Bern, Switzerland;University of Bern, Switzerland;University of Bern, Switzerland
Venue:
Proceedings of the 2013 International Workshop on Ecosystem Architectures
Year:
2013

Citing 9
Cited 0

Software Ecosystem: Understanding an Indispensable Technology and Industry

Software Ecosystem: Understanding an Indispensable Technology and Industry
Questions programmers ask during software evolution tasks

Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering
Information Needs in Collocated Software Development Teams

ICSE '07 Proceedings of the 29th international conference on Software Engineering
Research Methods for Human-Computer Interaction

Research Methods for Human-Computer Interaction
From software product lines to software ecosystems

Proceedings of the 13th International Software Product Line Conference
Codebook: discovering and exploiting relationships in software repositories

Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Research Methods in Human-Computer Interaction

Research Methods in Human-Computer Interaction
Knowledge management in software ecosystems: software artefacts as first-class citizens

Proceedings of the Fourth European Conference on Software Architecture: Companion Volume
Information needs for integration decisions in the release process of large-scale parallel development

Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work

Quantified Score

Hi-index	0.00

Visualization

Abstract

We present the results of an investigation into the nature of the information needs of software developers who work in projects that are part of larger ecosystems. In an open-question survey we asked framework and library developers about their information needs with respect to both their upstream and downstream projects. We investigated what kind of information is required, why is it necessary, and how the developers obtain this information. The results show that the downstream needs are grouped into three categories roughly corresponding to the different stages in their relation with an upstream: selection, adoption, and co-evolution. The less numerous upstream needs are grouped into two categories: project statistics and code usage. The current practices part of the study shows that to satisfy many of these needs developers use non-specific tools and ad hoc methods. We believe that this is a largely unexplored area of research.