2020-12-07T14:30:00+00:00 2020-12-07T15:00:00+00:00 From experimental software to research infrastructure maturity The challenges facing research software development are manifold and have long been a major topic at RSE conferences. https://sorse.github.io//programme/talks/event-009/ SORSE.firstname.lastname@example.org SORSE
The challenges facing research software development are manifold and have long been a major topic at RSE conferences.
In the context of the covid-19 pandemic, debates about the use or rather re-use of research software for real word applications – with life-or-death implications – have occurred in broader contexts than RSE conferences. The discussions confirm what has long been known: sustaining software for long term use requires continued commitment and investment in quality and practices, see e.g. Report on the Workshop on Sustainable Software Sustainability 2019 (WOSSS19).
With the European Commission’s plan for a European Open Science Cloud (EOSC), foundations are being laid to build an ecosystem to enable digital research. One of the core requirements for offering a service in EOSC will be its technical maturity – it must reach an 8 on the 9-step Technology Readiness Level scale, designed by NASA to assess its technology’s space readiness.
In this talk I will explain what we at CESSDA, the Consortium of European Social Science Data Archives, do to ensure our technology is designed to build services that meet these maturity requirements. Starting from guidelines and agreement on best practices, automation plays an important role for quality analysis and testing and also provides evidence of this. Investing in the long term objective of sustainability for our cloud native infrastructure plays a fundamental part. At the core, we define repeated software releases – not just one-off demonstrators – with strict quality requirements as the fundamental deliverables that we can later turn into mature services we can reliably provide to our users.
We will show how our model can serve as a blueprint for EOSC and for moving from experimental code to infrastructure that is mature enough to serve its purpose in times of crisis.
Language: English Prerequisites: General familiarity with issues from software development including concepts such as testing and automation as well as project management with limitations in academia are advantageous.Register Slides Talks Download