You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: paper.tex
+29-2Lines changed: 29 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -44,10 +44,35 @@ \section{Introduction}
44
44
The number of people developing software in academia is constantly rising [REF].
45
45
Research Software Engineering are actions necessary to create, adapt or maintain Research Software or train others to do so.
46
46
These actions are very diverse and so are the environments they are performed in.
47
-
We refer by Research Software Engineer (RSE) to persons who regularly perform those actions as part of their work.
48
-
We refer by researcher to all others involved in research, those that are at most sporadically performing RSE actions.
49
47
This position paper focuses on (groups of) research software engineers and researchers who require RSE for their research.
50
48
49
+
\subsection{Terminology}
50
+
Depending on the national research
51
+
environments and processes that readers are familiar with, the notion of the terms \emph{software} and \emph{research} might differ.
52
+
Therefore, to avoid ambiguities, we define them as follows:\\
53
+
\textbf{Software:}\\
54
+
Source code, documentation, tests, executables
55
+
and all other artefacts that are created by humans during the development process
56
+
that are necessary to understand its purpose.\\
57
+
\textbf{Research software:}\\
58
+
Foundational algorithms, the software itself,
59
+
as well as scripts and computational workflows that were created
60
+
during the research process or for a research purpose, across all domains of research.
61
+
This definition is broader than in~\autocite{FAIR4RS} and is the outcome of a recent
62
+
discussion in~\autocite{Gruenpeter2021}.\\
63
+
\textbf{Research software engineers:}\\
64
+
People who
65
+
create or improve research software and/or the structures that the software interacts with
66
+
in the computational ecosystem of a research domain.
67
+
They are highly skilled team members who may also choose to conduct their own research as
68
+
part of their role.
69
+
However, we also recognise that many RSEs have chosen specifically to focus on a technical
70
+
role as an alternative to a traditional research role because they enjoy and wish to focus
71
+
on the development of research software.\\
72
+
\textbf{Researchers:}\\
73
+
We refer by researcher to all others involved in research or in research supporting organizations as \eg libraries,
74
+
hence those that are at most sporadically performing RSE actions.
75
+
51
76
\section{Motivation}
52
77
53
78
In this chapter, we provide motivation for dedicated RSE groups in German research organizations.
@@ -72,6 +97,8 @@ \subsection{Tasks - Why do central software services make sense?}
72
97
73
98
Cite for international comparison \autocite{Cosden2022} Princeton RSE group model
74
99
100
+
101
+
75
102
\subsection{Structure}
76
103
77
104
A central RSE team on long-term contracts will act as a knowledge hub due to their experience in and support of several disciplines as well as established contacts within the organisation.
0 commit comments