Please use this identifier to cite or link to this item: http://dx.doi.org/10.25673/69605
Full metadata record
DC FieldValueLanguage
dc.contributor.authorHeumüller, Robert-
dc.contributor.authorNielebock, Sebastian-
dc.contributor.authorKrüger, Jacob-
dc.contributor.authorOrtmeier, Frank-
dc.date.accessioned2022-02-25T10:47:05Z-
dc.date.available2022-02-25T10:47:05Z-
dc.date.issued2020-
dc.date.submitted2020-
dc.identifier.urihttps://opendata.uni-halle.de//handle/1981185920/71557-
dc.identifier.urihttp://dx.doi.org/10.25673/69605-
dc.description.abstractOpen-science initiatives have gained substantial momentum in computer science, and particularly in software-engineering research. A critical aspect of open-science is the public availability of artifacts (e.g., tools), which facilitates the replication, reproduction, extension, and verification of results. While we experienced that many artifacts are not publicly available, we are not aware of empirical evidence supporting this subjective claim. In this article, we report an empirical study on software artifact papers (SAPs) published at the International Conference on Software Engineering (ICSE), in which we investigated whether and how researchers have published their software artifacts, and whether this had scientific impact. Our dataset comprises 789 ICSE research track papers, including 604 SAPs (76.6%), from the years 2007 to 2017. While showing a positive trend towards artifact availability, our results are still sobering. Even in 2017, only 58.5% of the papers that stated to have developed a software artifact made that artifact publicly available. As we did find a small, but statistically significant, positive correlation between linking to artifacts in a paper and its scientific impact in terms of citations, we hope to motivate the research community to share more artifacts. With our insights, we aim to support the advancement of open science by discussing our results in the context of existing initiatives and guidelines. In particular, our findings advocate the need for clearly communicating artifacts and the use of non-commercial, persistent archives to provide replication packages.eng
dc.description.sponsorshipProjekt DEAL 2020-
dc.language.isoeng-
dc.relation.ispartofhttp://link.springer.com/journal/10664-
dc.rights.urihttps://creativecommons.org/licenses/by/4.0/-
dc.subjectSoftwareeng
dc.subjectOpen scienceeng
dc.subjectOpen sourceeng
dc.subjectArtifactseng
dc.subjectPublishingeng
dc.subject.ddc000-
dc.titlePublish or perish, but do not forget your software artifactseng
dc.typeArticle-
dc.identifier.urnurn:nbn:de:gbv:ma9:1-1981185920-715576-
local.versionTypepublishedVersion-
local.bibliographicCitation.journaltitleEmpirical software engineering-
local.bibliographicCitation.volume25-
local.bibliographicCitation.pagestart4585-
local.bibliographicCitation.pageend4616-
local.bibliographicCitation.publishernameSpringer Science + Business Media B.V-
local.bibliographicCitation.publisherplaceDordrecht [u.a.]-
local.bibliographicCitation.doi10.1007/s10664-020-09851-6-
local.openaccesstrue-
dc.identifier.ppn1735992232-
local.bibliographicCitation.year2020-
cbs.sru.importDate2022-02-25T10:42:10Z-
local.bibliographicCitationEnthalten in Empirical software engineering - Dordrecht [u.a.] : Springer Science + Business Media B.V, 1996-
local.accessrights.dnbfree-
Appears in Collections:Fakultät für Informatik (OA)

Files in This Item:
File Description SizeFormat 
Heumüller et al._Publish_2020.pdfZweitveröffentlichung1.45 MBAdobe PDFThumbnail
View/Open