Skip to aside Skip to content Skip to footer

roles: Research Software User

Introduction

A Research Software user in a very broad sense could be anyone who uses a piece of research software. However, though it is obviously important and necessary that software has all types of users, in this case we are talking more about those users who contribute to increasing the quality of research software by their experience of using it. Such users are, to use another term, often seen as stakeholders in the research software, and are in some cases included in any projects aimed at developing the research software. Users often drive development and therefore quality by reporting unexpected results, bugs and issues, and by influencing the priority levels for additions or enhancements to a current piece of research software.

A Product Owner is in this regard usually seen as the stakeholder-in-chief; they are responsible for collaborating with user stakeholders, identifying relevant items to be developed in the software, creating some kind of prioritisation of the issues, and ensuring that developers (such as research software engineers or researchers who code) are then able to work on solving such issues, perhaps in conjunction with a project manager.

A Research Software user is also tied into what Research Software is; in the three-tier model users become more common as the reach of the software grows through prototype tools and increased infrastructure. As the software grows, users more easily coalesce into a community and the shared experience can often drive further enhancements.

Software development & quality responsibilities, challenges & tasks

The responsibilities here are similar to those of the Product Owner, who is focused on defining goals and prioritising the development of high-quality research software. The tasks a user could be required to perform include:

  • Considering whether a piece of research software is reliable and produces results in a transparent manner.
  • Providing requirements and ongoing feedback via focus/user groups and workshops to ensure the research software supports real workflows.
  • Providing feedback on the user interface design and user experience of the research software.
  • Translating research goals into actionable requirements — working with product owners and developers to convert objectives into implementable software tasks.
  • Engaging with the development process used by the product owner and developers so that their voices are heard at opportune moments.
  • Engage with the product owner and developers to produce user manuals and guides for the research software.
  • Disseminate articles describing the research software, make presentations at conferences and other workshops with a view to initiate and grow a user community.

Software development & quality guidance