Reproducibility Debt: Challenges and Future Pathways

Zara Hassan, Christoph Treude, Michael Norrish, Graham J. Williams, Alex Potanin

Research output: Chapter in Book/Report/Conference proceedingConference Paperpeer-review

2 Citations (Scopus)

Abstract

Reproducibility of scientific computation is a critical factor in validating its underlying process, but it is often elusive. Complexity and continuous evolution in software systems have introduced new challenges for reproducibility across a myriad of computational sciences, resulting in growing debt. This requires a comprehensive domain-agnostic study to define and asses Reproducibility Debt (RpD) in scientific software, thus uncovering and classifying all underlying factors attributed towards its emergence and identification i.e., causes and effects. Moreover, an organised map of prevention strategies is imperative to guide researchers for its proactive management. This vision paper highlights the challenges that hinder effective management of RpD in scientific software, with preliminary results from our ongoing work and an agenda for future research.

Original languageEnglish
Title of host publicationFSE 2024: Companion Proceedings of the 32nd ACM International Conference on the Foundations of Software Engineering
EditorsMarcelo d'Amorim
Place of PublicationNew York, NY
PublisherAssociation for Computing Machinery (ACM)
Pages462-466
Number of pages5
ISBN (Electronic)9798400706585
DOIs
Publication statusPublished - 10 Jul 2024
Event32nd ACM International Conference on the Foundations of Software Engineering - Porto de Galinhas, Brazil
Duration: 15 Jul 202419 Jul 2024
https://dl-acm-org.virtual.anu.edu.au/doi/proceedings/10.1145/3663529 (Proceedings)

Conference

Conference32nd ACM International Conference on the Foundations of Software Engineering
Country/TerritoryBrazil
CityPorto de Galinhas
Period15/07/2419/07/24
Internet address

Fingerprint

Dive into the research topics of 'Reproducibility Debt: Challenges and Future Pathways'. Together they form a unique fingerprint.

Cite this