-
Notifications
You must be signed in to change notification settings - Fork 53
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add list of definitions for research software
This page should list definitions of the term "research software" together with their sources and noteable uses. At the moment, this is a proposal, and thus, only available in English. Once accepted, a German version would need to be created as well. This PR depends on the PR #274 for the page not to show up in the main manu.
- Loading branch information
Showing
1 changed file
with
52 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
--- | ||
layout: default | ||
title: Definition Research Software | ||
weight: 0 | ||
--- | ||
|
||
# Definition Research Software | ||
|
||
At the moment, there is no single universally used or accepted definiton of research software. | ||
This is not for a lack of effort. | ||
A lot of discussions happend and still happen on this topic and so far resulted in a few definitons that all go in roughly the same direction, but put more emphasis on one or the other aspect. | ||
We are involved in those discussions as de-RSE e.V., but we did not (yet) single out a specific definition, but for the time being collect there what we consider some of the most often used definitions. | ||
|
||
## from: “Defining Research Software: a controversial discussion” | ||
|
||
A Summary Report of FAIR4RS Subgroup 3 activity and discussion, available on [zenodo](https://zenodo.org/records/5504016). | ||
|
||
_Research Software includes source code files, algorithms, scripts, computational workflows and executables that were created during the research process or for a research purpose. | ||
Software components (e.g., operating systems, libraries, dependencies, packages, scripts, etc.) that are used for research but were not created during or with a clear research intent should be considered software in research and not Research Software. | ||
This differentiation may vary between disciplines. | ||
The minimal requirement for achieving computational reproducibility is that all the computational components (Research Software, software used in research, documentation and hardware) used during the research are identified, described, and made accessible to the extent that is possible._ | ||
|
||
This definition was also used in | ||
|
||
- the [Amsterdam Declaration on Funding Research Software Sustainability](https://zenodo.org/records/8325436) | ||
- the [FAIR Principles for Research Software (FAIR4RS Principles)](https://zenodo.org/records/6623556), an RDA recommendation | ||
|
||
## from: “UK Research Software Survey 2014” | ||
|
||
Available on [zenodo](https://zenodo.org/records/14809). | ||
|
||
_Software that is used to generate, process or analyse results that you intend to appear in a publication (either in a journal, conference paper, monograph, book or thesis). | ||
Research software can be anything from a few lines of code written by yourself, to a professionally developed software package. | ||
Software that does not generate, process or analyse results - such as word processing software, or the use of a web search - does not count as ‘research software’ for the purposes of this survey._ | ||
|
||
## from: “Research Software – Quality Assured and Re-usable”, a call for proposals to increase the usability of existing Research Software by the DFG | ||
|
||
Available from the [DFG](https://www.dfg.de/en/news/news-topics/announcements-proposals/2022/info-wissenschaft-22-85). | ||
|
||
_Nowadays, the use of software is an integral part of research work in almost all disciplines. | ||
Typical areas of application include the generation, processing, analysis and visualisation of research data and, especially in the natural sciences and engineering, the control and execution of experiments. | ||
If software is developed for this purpose in the context of research, it is referred to as research software._ | ||
|
||
## from: “Research Software Sustainability”, a call for proposals by the DFG. | ||
|
||
Available from the [DFG](https://www.dfg.de/resource/blob/172676/861b6b46e50aef649ee6634c7a2d0b6a/161026-dfg-call-proposal-software-en-data.pdf). | ||
|
||
_In every phase of scientific work, many disciplines use research software, for example to | ||
generate, process, analyse and visualise research data. | ||
In this sense, the term “research | ||
software” refers to the software applications and software libraries specially created for | ||
scientific knowledge gain._ |