• Keine Ergebnisse gefunden

Research software landscape and stakeholders

N/A
N/A
Protected

Academic year: 2022

Aktie "Research software landscape and stakeholders"

Copied!
11
0
0

Wird geladen.... (Jetzt Volltext ansehen)

Volltext

(1)

GeoMünster 22.-25.09.2019

Research software landscape and stakeholders

Bernadette Fritzsch

Alfred Wegener Institute Helmholtz Center for Polar and Marine Research

Bremerhaven

(2)

Research Software – Tools for Research

• Empirical evidence – Scientific Theory – Computational Science – Data Science

• Growing importance of software – survey SSI 2014:

S. J. Hettrick et al, UK Research Software Survey 2014, DOI:10.5281/zenodo.14809)

• 92% of academics use research software

• 69% say that their research would not be practical without it

- further international surveys

(3)

GeoMünster 22.-25.09.2019 3

Research Software

• Tool for research work

• Reproducibility of scientific results

• Software as a result of scientific work

• Software as resource

• Sustainability

• FAIR Principles for software:

Findable, Accessible, Interoperable, Reusable

• activities: SSI, RDA Working Group, ReSA, …, EGU, … ,

FORCE11, …,

(4)

Research Software

Types of software

• Research codes

• Frameworks used in research, e.g. Matlab

• Services, e.g. Zenodo Stakeholders:

• Management

• Developers

• Users

• Infrastructure facilities

• Funding Agencies Relation to software

• Developing

• Using

• Providing

(5)

Helmholtz Association

• Working Group Open Science

• Taskgroup Research Software

• Position paper about Research Software (2017)

https://os.helmholtz.de/?id=2766

• „Dealing with research software: Recommendations for best practices“

(2019) http://doi.org/10.2312/os.helmholtz.003

• Guidelines for Sustainable Research Software Development

− Good practices in Software Development and Documentation

− Software Quality – incentives for writing well documented code

− Need for training and education in software developing skills

• Project HIFIS - Helmholtz Federated IT Services, working package on

Software

(6)

Alliance of German Research Organizations

Aims:

Increase awareness on importance of software use and development in the scientific process

• Identify open issues

• Provide recommendations to the various stakeholders in scientific software development

• Guidelines on the Development, Use and Provision of Research Software

• represents universities, research organisations, DFG and others

• Priority initiative “Digital Information”

• Working group “Digital tools: software and services” (2018-2022), former ad-hoc

working group “Scientific software” (2016- 2017)

(7)

GeoMünster 22.-25.09.2019 7

Good Scientific Practice - DFG

Some aspects:

• Open Access: all used data, materials, methods and software have to be made available

Software source code must be made persistent and citable, as well as

documented.

• Authorship in data and software

• books and journals repos for data and for software

New update of codex 01.08.2019

In contrast to earlier versions, software is mentioned

(8)

„Software is 95% human and only 5% code*“

* Eric Albers, CCC2019, https://media.ccc.de/v/thms-49-ber-die-nachhaltigkeit-von- software

The Researcher

Needs analysis scripts (or other software skills) for her research

Learns what she needs

The Software Person

● Is hired to work on software for a research project

The Geek

Writes software as part of her research

The Go-to Person in case if problems

Knows how to solve all kinds of computer problems

The Reproducibility Guru

Learns lots of software tools in order

to make his research reproducible

(9)

GeoMünster 22.-25.09.2019 9

de-RSE e.V. – Society for Research Software

• Founded 2018, www.de-rse.org

• Aim (statutes)

– Ensuring sustainability and verifiability of research software development as part of research processes

– Improved perception of the role of software in research

– Opening up of scientific software as a central building block in Open Science

– Publication of Software

– Professionalization of software development

– Integration into higher-level activities, for example in the context of e-science and e-infrastructures

– Increasing the attractiveness of the occupational field  career

paths

(10)

de-RSE

− First conference 04.-06.06.2019

deRSE19 in Potsdam (AWI, GFZ, PIK)

− More than 130 submissions (talks, posters, workshops)

− community building

CC BY 4.0Antonia Cozacu, Jan Philipp Dietrich, de-RSE e.V.

(11)

GeoMünster 22.-25.09.2019 11

Summary

• Increasing awareness for research software

• Policies and Guidelines – Support in daily work

– Responsibility of institution to provide training – infrastructure

• Community building – Take part – network – www.de-rse.org

(this presentation is licensed under CC BY 4.0

https://creativecommons.org/licenses/by/4.0/legalcode)

Referenzen

ÄHNLICHE DOKUMENTE

We evaluated the open Software Engineering course by comparing the performance of students in three types of teaching method: face-to-face course, online course, and hybrid

Three different 2D scenarios have been studied using OpenFOAM, namely low compressible flow with no flow boundary, low compressible flow with one flow boundary at constant

8 We will argue that a standardized platform is analogous to joint ownership (all parties in the standardization committee have veto powers 9 ) and that open source is analogous

Safety standards such as IEC 61508, DO-178B suggest development according to V-model.  Specification and implementation linked by verification and validation.  Variety of

Lecture 02: Concepts of Safety and Security, Norms and Standards Lecture 03: Quality of the Software Development Process.. Lecture 04:

 Variants of a product line share common features.  Feature models describe features and

Moreover, recent research as well as experience from practice shows companies utilizing different development approaches to assemble the best-fitting approach for the

To analyse gaps and opportunities for future research, this paper follows a qualitative, exploratory research approach to gather sufficient data on test management requirements