Merge pull request #13 from DE-RSE/12-port-definition-block-from-the-competencies-paper

bring over definitions part

Author: dokempf

paper.tex

@@ -38,16 +38,41 @@ \section{Introduction}
 It has been established that most research requires research software for its results [REF].
 To solve pressing research challenges, better software is crucial [REF].
 During the past decade, it gained ever-growing attention and is becoming accepted as a research result on its own.
-The term “Research software” is still defined somewhat differently within the community.
-We follow here the definition: “Research Software includes source code files, algorithms, scripts, computational workflows and executables that were created during the research process or for a research purpose”, with full definition and discussion provided in~\autocite{Gruenpeter2021}.
+%We follow here the definition: “Research Software includes source code files, algorithms, scripts, computational workflows and executables that were created during the research process or for a research purpose”, with full definition and discussion provided in~\autocite{Gruenpeter2021}.
 
 The number of people developing software in academia is constantly rising [REF].
 Research Software Engineering are actions necessary to create, adapt or maintain Research Software or train others to do so.
 These actions are very diverse and so are the environments they are performed in.
-We refer by Research Software Engineer (RSE) to persons who regularly perform those actions as part of their work.
-We refer by researcher to all others involved in research, those that are at most sporadically performing RSE actions.
 This position paper focuses on (groups of) research software engineers and researchers who require RSE for their research.
 
+\subsection{Terminology}
+Depending on the national research
+environments and processes that readers are familiar with, the notion of the terms \emph{software} and \emph{research} might differ.
+The term “Research software” is also defined somewhat differently within the community.
+Therefore, to avoid ambiguities, we define them as follows:\\
+\textbf{Software:}\\
+Source code, documentation, tests, executables
+and all other artefacts that are created by humans during the development process
+that are necessary to understand its purpose.\\
+\textbf{Research software:}\\
+Foundational algorithms, the software itself,
+as well as scripts and computational workflows that were created
+during the research process or for a research purpose, across all domains of research.
+This definition is broader than in~\autocite{FAIR4RS} and is the outcome of a recent
+discussion in~\autocite{Gruenpeter2021}.\\
+\textbf{Research software engineers:}\\
+People who
+create or improve research software and/or the structures that the software interacts with
+in the computational ecosystem of a research domain.
+They are highly skilled team members who may also choose to conduct their own research as
+part of their role.
+However, we also recognise that many RSEs have chosen specifically to focus on a technical
+role as an alternative to a traditional research role because they enjoy and wish to focus
+on the development of research software.\\
+\textbf{Researchers:}\\
+We refer by researcher to all others involved in research or in research supporting organizations as \eg libraries,
+hence those that are at most sporadically performing RSE actions.
+
 \section{Motivation}
 
 In this chapter, we provide motivation for dedicated RSE groups in German research organizations.
@@ -73,6 +98,8 @@ \subsection{Tasks - Why do central software services make sense?}
 
 Cite for international comparison \autocite{Cosden2022} Princeton RSE group model
 
+
+
 \subsection{Structure}
 
 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.