skip to main content
10.1145/2501585.2501586acmconferencesArticle/Chapter ViewAbstractPublication PagesfseConference Proceedingsconference-collections
Article

Categorizing developer information needs in software ecosystems

Published:19 August 2013Publication History

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.

References

  1. David G. Messerschmitt and Clemens Szyperski. Software Ecosystem: Understanding an Indispensable Technology and Industry. MIT Press, Cambridge, MA, USA, 2003. Google ScholarGoogle ScholarDigital LibraryDigital Library
  2. Jan Bosch. From software product lines to software ecosystems. In Proceedings of the 13th International Software Product Line Conference, SPLC ’09, pages 111–119, Pittsburgh, PA, USA, 2009. Carnegie Mellon University. Google ScholarGoogle ScholarDigital LibraryDigital Library
  3. Mircea F. Lungu. Reverse Engineering Software Ecosystems. PhD thesis, University of Lugano, 2009.Google ScholarGoogle Scholar
  4. Jonathan Sillito, Gail C. Murphy, and Kris De Volder. Questions programmers ask during software evolution tasks. In Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering, SIGSOFT ’06/FSE-14, pages 23–34, New York, NY, USA, 2006. ACM. Google ScholarGoogle ScholarDigital LibraryDigital Library
  5. Andrew J. Ko, Robert DeLine, and Gina Venolia. Information needs in collocated software development teams. In Proceedings of the 29th international conference on Software Engineering, ICSE ’07, pages 344–353, Washington, DC, USA, 2007. IEEE Computer Society. Google ScholarGoogle ScholarDigital LibraryDigital Library
  6. Dominik Seichter, Deepak Dhungana, Andreas Pleuss, and Benedikt Hauptmann. Knowledge management in software ecosystems: software artefacts as first-class citizens. In Proceedings of the Fourth European Conference on Software Architecture: Companion Volume, pages 119–126. ACM, 2010. Google ScholarGoogle ScholarDigital LibraryDigital Library
  7. Shaun Phillips, Guenther Ruhe, and Jonathan Sillito. Information needs for integration decisions in the release process of large-scale parallel development. In Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work, pages 1371–1380. ACM, 2012. Google ScholarGoogle ScholarDigital LibraryDigital Library
  8. Andrew Begel, Yit Phang Khoo, and Thomas Zimmermann. Codebook: discovering and exploiting relationships in software repositories. In Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1, ICSE ’10, pages 125–134, New York, NY, USA, 2010. ACM. Google ScholarGoogle ScholarDigital LibraryDigital Library
  9. Anselm Strauss and Juliet Corbin. Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory. SAGE Publications Inc., 1998.Google ScholarGoogle Scholar
  10. Paul Cairns and Anna L. Cox. Research Methods for Human-Computer Interactions. Cambridge University Press, 2008. Chapter 2, 7, 9. Google ScholarGoogle ScholarDigital LibraryDigital Library
  11. Jonathan Lazar, Jinjuan Heidi Feng, and Harry Hochheiser. Research methods in Human-Computer Interaction. Wiley, 2010. Google ScholarGoogle ScholarDigital LibraryDigital Library

Index Terms

  1. Categorizing developer information needs in software ecosystems

                Recommendations

                Comments

                Login options

                Check if you have access through your login credentials or your institution to get full access on this article.

                Sign in
                • Published in

                  cover image ACM Conferences
                  WEA 2013: Proceedings of the 2013 International Workshop on Ecosystem Architectures
                  August 2013
                  30 pages
                  ISBN:9781450323147
                  DOI:10.1145/2501585

                  Copyright © 2013 ACM

                  Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than the author(s) must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected].

                  Publisher

                  Association for Computing Machinery

                  New York, NY, United States

                  Publication History

                  • Published: 19 August 2013

                  Permissions

                  Request permissions about this article.

                  Request Permissions

                  Check for updates

                  Qualifiers

                  • Article

                PDF Format

                View or Download as a PDF file.

                PDF

                eReader

                View online with eReader.

                eReader