Abstract

There is a huge variety of types of research software, at different stages of evolution. This often confuses potential software users, developers, funders, and other stakeholders who need to understand a particular software project, such as when deciding to use them, contribute to them, or fund them. This talk presents work performed by a group who met at a Dagstuhl seminar consisting of both software engineering researchers (SERs) and research software engineers (RSEs). It includes an initial categorization of research software types, and an initial presentation of an abstract research software lifecycle that can be applied and customized to suit a wide variety of research software types, which then can be used to make decisions and guide development standards that may vary per stage. We also seek community input on improvements of these two artifacts for future iterations.

In addition, because terminologies and definitions often vary, e.g., one person may consider a software project to be early-stage or in “maintenance mode”, whilst another project might consider the same software to be inactive or failed. Because of this, we explore and explains concept such as software maturity, intended audience, and intended future use.

The zoom link is https://cam-ac-uk.zoom.us/j/81161988457?pwd=TB5DgLyL0RLQROGBA4LC9jLnlKAh5p.1 (Password 355996)