Guiding Development Work Across a Software Ecosystem by Visualizing Usage Data
@article{Bogart2020GuidingDW, title={Guiding Development Work Across a Software Ecosystem by Visualizing Usage Data}, author={Christopher Bogart and James Howison and James D. Herbsleb}, journal={ArXiv}, year={2020}, volume={abs/2012.05987} }
Software is increasingly produced in the form of ecosystems, collections of interdependent components maintained by a distributed community. These ecosystems act as network organizations, not markets, and thus often lack actionable price-like signals about how the software is used and what impact it has. We introduce a tool, the Scientific Software Network Map, that collects and displays summarized usage data tailored to the needs of actors in software ecosystems. We performed a contextualized…
References
SHOWING 1-10 OF 36 REFERENCES
Understanding the scientific software ecosystem and its impact: Current and future measures
- Computer Science
- 2015
This article provides a framework by which to categorize different types of measures and their relationships as they reach around from funding, development, scientific use, and through to scientific impact, and concludes with policy recommendations designed to improve insight into the scientific software ecosystem, make it more understandable, and thereby contribute to the progress of science.
A Quantitative Analysis of Developer Information Needs in Software Ecosystems
- Computer ScienceECSAW '14
- 2014
It is discovered that tool support for developers working in an ecosystem context is even more meager than the authors thought: mailing lists and internet search are the most popular tools developers use to satisfy their ecosystem-related information needs.
When It Breaks, It Breaks: How Ecosystem Developers Reason about the Stability of Dependencies
- Computer Science2015 30th IEEE/ACM International Conference on Automated Software Engineering Workshop (ASEW)
- 2015
It is argued that awareness mechanisms based on various notions of stability can enable developers to make decisions that are independent yet wise and provide stewardship rather than disruption to the ecosystem.
A sense of community: A research agenda for software ecosystems
- Computer Science2009 31st International Conference on Software Engineering - Companion Volume
- 2009
This paper presents a research agenda on software ecosystems to study both the technical and the business aspects of software engineering in vibrant ecosystems to enable software vendors to develop software that is adaptable to new business models and new markets.
Software engineering beyond the project - Sustaining software ecosystems
- Computer ScienceInf. Softw. Technol.
- 2014
Scientific software production: incentives and collaboration
- Computer ScienceCSCW
- 2011
A multiple-case study of software development in three fields: high energy physics, structural biology, and microbiology identifies ways in which incentives are matched and mismatched with the needs of the science fields, especially with respect to collaboration.
Vertical interaction in open software engineering communities
- Business
- 2009
Software engineering is still a relatively young field, struggling to develop consistent standards and methods across the domain. For a given project, developers can choose from dozens of models,…
Supporting the Collaborative Appropriation of an Open Software Ecosystem
- Computer ScienceComputer Supported Cooperative Work (CSCW)
- 2011
By empirically studying the Eclipse software ecosystem and its appropriation, it is shown the improved flexibility users achieve at designing their workplaces, and outlined an alternative design methodology based on existing CSCW approaches, where the workplace design in the age of software ecosystems has to go beyond.
Incentives and integration in scientific software production
- EconomicsCSCW
- 2013
The software ecosystem surrounding BLAST, a key bioinformatics tool, is examined, finding that academic credit is a powerful motivator for the production and revealing of improvements, but also that improvements motivated by academic credit are less likely to be integrated than those with other motivations, including financial gain.