The Evolution of Project Inter-Dependencies in a Software Ecosystem: The Case of Apache. Bavota, G.; Canfora, G.; Di Penta, M.; Oliveto, R.; and Panichella, S. In Software Maintenance (ICSM), 2013 29th IEEE International Conference On, pages 280–289. IEEE / Univ. of Sannio, Benevento, Italy.
The Evolution of Project Inter-Dependencies in a Software Ecosystem: The Case of Apache [link]Paper  doi  abstract   bibtex   
Software ecosystems consist of multiple software projects, often interrelated each other by means of dependency relations. When one project undergoes changes, other projects may decide to upgrade the dependency. For example, a project could use a new version of another project because the latter has been enhanced or subject to some bug-fixing activities. This paper reports an exploratory study aimed at observing the evolution of the Java subset of the Apache ecosystem, consisting of 147 projects, for a period of 14 years, and resulting in 1,964 releases. Specifically, we analyze (i) how dependencies change over time, (ii) whether a dependency upgrade is due to different kinds of factors, such as different kinds of API changes or licensing issues, and (iii) how an upgrade impacts on a related project. Results of this study help to comprehend the phenomenon of library/component upgrade, and provides the basis for a new family of recommenders aimed at supporting developers in the complex (and risky) activity of managing library/component upgrade within their software projects.
@inproceedings{bavotaEvolutionProjectInterdependencies2013,
  title = {The {{Evolution}} of {{Project Inter}}-Dependencies in a {{Software Ecosystem}}: {{The Case}} of {{Apache}}},
  booktitle = {Software {{Maintenance}} ({{ICSM}}), 2013 29th {{IEEE International Conference}} On},
  author = {Bavota, G. and Canfora, G. and Di Penta, M. and Oliveto, R. and Panichella, S.},
  date = {2013},
  pages = {280--289},
  publisher = {{IEEE / Univ. of Sannio, Benevento, Italy}},
  issn = {1063-6773},
  doi = {10.1109/icsm.2013.39},
  url = {https://doi.org/10.1109/icsm.2013.39},
  abstract = {Software ecosystems consist of multiple software projects, often interrelated each other by means of dependency relations. When one project undergoes changes, other projects may decide to upgrade the dependency. For example, a project could use a new version of another project because the latter has been enhanced or subject to some bug-fixing activities. This paper reports an exploratory study aimed at observing the evolution of the Java subset of the Apache ecosystem, consisting of 147 projects, for a period of 14 years, and resulting in 1,964 releases. Specifically, we analyze (i) how dependencies change over time, (ii) whether a dependency upgrade is due to different kinds of factors, such as different kinds of API changes or licensing issues, and (iii) how an upgrade impacts on a related project. Results of this study help to comprehend the phenomenon of library/component upgrade, and provides the basis for a new family of recommenders aimed at supporting developers in the complex (and risky) activity of managing library/component upgrade within their software projects.},
  keywords = {*imported-from-citeulike-INRMM,~INRMM-MiD:c-13116370,complexity,ecosystem,ecosystem-change,evolution,free-software,software-evolution}
}
Downloads: 0