TL;DR
This paper investigates the challenges in sharing and using artifacts in software engineering research, analyzing community perspectives to identify issues and propose improvements for better artifact dissemination and quality.
Contribution
It provides a comprehensive understanding of artifact sharing challenges in software engineering through empirical surveys and offers actionable recommendations to enhance artifact quality and sharing practices.
Findings
Mismatched expectations hinder artifact usefulness
Lack of rewards discourages artifact sharing and review
Identifies key factors influencing artifact adoption and success
Abstract
In recent years, many software engineering researchers have begun to include artifacts alongside their research papers. Ideally, artifacts, including tools, benchmarks, and data, support the dissemination of ideas, provide evidence for research claims, and serve as a starting point for future research. However, in practice, artifacts suffer from a variety of issues that prevent the realization of their full potential. To help the software engineering community realize the full potential of artifacts, we seek to understand the challenges involved in the creation, sharing, and use of artifacts. To that end, we perform a mixed-methods study including a survey of artifacts in software engineering publications, and an online survey of 153 software engineering researchers. By analyzing the perspectives of artifact creators, users, and reviewers, we identify several high-level challenges…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Code & Models
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
