Skip to content

mention SW-properties earlier #147

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
knarrff merged 1 commit into from
Aug 18, 2025
Merged

mention SW-properties earlier #147

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions paper.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,6 +102,7 @@ \section{Introduction}
We use the term central \emph{RSE unit} interchangeably with the term \emph{RSE hub} even though for large federated research organisations there might be a more complex arrangement such as a network of RSE hubs.

\section{Motivation for central RSE units}
\label{sec:motivation}
\begin{quotation}
\noindent \textit{Better Software, Better Research}\\(Mission statement of the UK Software Sustainability Institute)
\end{quotation}
Expand All @@ -112,7 +113,7 @@ \section{Motivation for central RSE units}

Research software is getting increasingly complex.
This is partly because the scientific problems being tackled using software are getting bigger.
However, the software is also expected to be reliable, secure and easy to use.
However, the software is also expected to rate high on a multitude of quality metrics such as correctness, reproducibility, maintainability, extensibility, usability, portability, interoperability, security, performance, and scalability~\autocite[Chapter 16]{Schulmeyer2008}.
Handling this increased complexity whilst ensuring timely delivery requires dedicated RSEs in central RSE units.

\subsection{Pooling: a necessary ingredient}
Expand Down Expand Up @@ -264,7 +265,7 @@ \subsection{Module 2: Consultation Services}%
\label{sec:consultation}

With the majority of researchers being self-taught programmers~\autocite{Carver2013}, there is a huge demand for expertise on how to develop better research software.
Here, “better” can refer to a number of quality metrics such as correctness, reproducibility, maintainability, extensibility, usability, portability, interoperability, performance or scalability~\autocite[Chapter 16]{Schulmeyer2008}.
Here, “better” can refer to a number of quality metrics as already mentioned in Section~\ref{sec:motivation}: correctness, reproducibility, maintainability, extensibility, usability, portability, interoperability, security, performance, or scalability~\autocite[Chapter 16]{Schulmeyer2008}.

In order to raise the quality standards for research that is based on research software, it is of great importance for research institutions to provide access to such expertise with a low barrier to entry.
The hub is a natural place to provide this central service.
Expand Down
Loading