|
| 1 | +--- |
| 2 | +hide: |
| 3 | + - toc |
| 4 | + - navigation |
| 5 | +--- |
| 6 | + |
| 7 | +# A guidelines and policy template for the development of research software at German research institutions |
| 8 | +### A recommendation by GI, RSE working group and de-RSE |
| 9 | + |
| 10 | +Research Software Engineering (abbreviated: RSE) is the application of software engineering practices to research software, |
| 11 | +i.e., software created for and primarily used in scientific research projects. |
| 12 | +RSE is not High-Performance Computing (HPC), Computational Science Engineering (CSE), Artificial Intelligence, or Data Science. |
| 13 | +It has different goals and a distinct professional profile for Research Software Engineers. |
| 14 | + |
| 15 | +Due to the increased relevance and complexity of research software, efficient and high-quality software development for research software also requires a range of organizational, methodological, and legal measures. |
| 16 | +This results in consequences both for the leadership to provide organizational support and for the individuals involved in software development to adhere to certain methodological guidelines. |
| 17 | +These guidelines were created based on the distilled knowledge (as of 2024) about software development in general (Software Engineering) and research software in particular (Research Software Engineering). |
| 18 | +It is planned to regularly update these guidelines and incorporate new insights. |
| 19 | + |
| 20 | +The authors propose these guidelines as a template to aid universities, colleges, and research institutions in the adaptation of fundamental policies and recommendations for research projects involving research software. |
| 21 | + |
| 22 | +[View Guidelines](https://todo){.md-button} |
| 23 | + |
| 24 | +# Purpose |
| 25 | + |
| 26 | +This guidelines template proposes the establishment of specific guidelines within universities, colleges, and research institutions. |
| 27 | +It aims to provide concrete assistance for defining their own guidelines while allowing for flexibility to accommodate the different cultures in various disciplines and research institutions through explicit variability for refinement. |
| 28 | + |
| 29 | +The guidelines template developed by the GI, the RSE working group, and de-RSE should therefore be used to create an independent document that can ideally be declared binding within one's own university, college, or research institution. |
| 30 | + |
| 31 | +# Contact |
| 32 | + |
| 33 | +For comments and suggestions, please contact the coordination team of the 'Software Guidelines' working group of the RSE section, |
| 34 | + currently Sebastian Nielebock, Bernhard Rumpe, and Inga Ulusoy, at the email address [email protected]. |
| 35 | +We would also appreciate feedback on which university, college, or research center the text is being used and in what form. |
| 36 | + |
| 37 | +# Institutions that have adopted the guidelines |
| 38 | + |
| 39 | + |
| 40 | + |
| 41 | +# RSE-Website template |
| 42 | + |
| 43 | +A template for an institute's RSE website can be found [here](website_template/). |
| 44 | + |
| 45 | +# Glossary |
| 46 | + |
| 47 | +A glossary (currently only available in German) to the terms used in the policy template can be found [here](glossar.md). |
0 commit comments