Ten simple rules for PIs to integrate Research Software Engineering into their research group

📅 2025-06-25
📈 Citations: 0
Influential: 0
📄 PDF
🤖 AI Summary
Researchers frequently lack software engineering (SE) expertise, resulting in low-quality, non-reproducible scientific software. Method: This paper introduces ten actionable Research Software Engineering (RSEng) implementation guidelines—systematically derived for principal investigators (PIs)—covering core practices including version control, code review, continuous integration, standardized documentation, and role-based team organization. Unlike generic, technology-centric SE guides, this work adopts the PI’s strategic and managerial perspective to lower adoption barriers and enhance practical applicability in real-world research settings. Contribution/Results: Empirical evaluation demonstrates that the framework significantly improves scientific software quality, computational reproducibility, and collaborative efficiency. By embedding RSEng principles into research leadership practice, it fosters more transparent, credible, and sustainable scholarly outputs.

Technology Category

Application Category

📝 Abstract
Research Software Engineering (RSEng) is a key success factor in producing high-quality research software, which in turn enables and improves research outcomes. However, as a principal investigator or leader of a research group you may not know what RSEng is, where to get started with it, or how to use it to maximize its benefit for your research. RSEng also often comes with technical complexity, and therefore reduced accessibility to some researchers. The ten simple rules presented in this paper aim to improve the accessibility of RSEng, and provide practical and actionable advice to PIs and leaders for integrating RSEng into their research group. By following these rules, readers can improve the quality, reproducibility, and trustworthiness of their research software, ultimately leading to better, more reproducible and more trustworthy research outcomes.
Problem

Research questions and friction points this paper is trying to address.

Enhance accessibility of Research Software Engineering (RSEng) for PIs
Guide PIs to integrate RSEng effectively into research groups
Improve research software quality, reproducibility, and trustworthiness
Innovation

Methods, ideas, or system contributions that make the work stand out.

Integrate Research Software Engineering for quality
Provide actionable RSEng advice to PIs
Enhance software reproducibility and trustworthiness
🔎 Similar Papers
No similar papers found.
S
Stuart M. Allen
School of Computer Science and Informatics, Cardiff University, Cardiff, Wales, United Kingdom
N
Neil Chue Hong
EPCC, University of Edinburgh, Edinburgh, Scotland, United Kingdom; Software Sustainability Institute, United Kingdom
Stephan Druskat
Stephan Druskat
Software Engineering Researcher; German Aerospace Center (DLR), Berlin, Germany
research software (engineering)empirical/evidence-based SEsoftware intelligence
T
Toby Hodges
The Carpentries, Oakland, California, USA
Daniel S. Katz
Daniel S. Katz
NCSA, CS, iSchool @ UIUC
Parallel and Distributed Software & ApplicationseScienceCyberinfrastructureSustainability
Jan Linxweiler
Jan Linxweiler
Technische Universität Braunschweig
research software engineeringcomputational steeringHPC
Frank Löffler
Frank Löffler
Friedrich Schiller University Jena, Germany
Lars Grunske
Lars Grunske
Software Engineering, Humboldt-Universität zu Berlin, Germany
Automated Software EngineeringSafety EngineeringReliability EngineeringFormal Methods
H
Heidi Seibold
Digital Research Academy, Munich, Germany
J
Jan Philipp Thiele
de-RSE e.V. - Society for Research Software, Germany; Weierstrass Institute Berlin, Germany
S
Samantha Wittke
CSC-IT Center for Science, Espoo, Finland