Role of General Users in the Lifecycle of Scientific Software
Bjorn Emonts (1), and the CASA Team (1,2,3,4) ((1) NRAO, (2) ESO, (3) NAOJ, (4) JIVE)

TL;DR
This paper discusses the importance of involving general users throughout the software lifecycle to improve scientific software reach and effectiveness, using CASA as a case study.
Contribution
It presents practical avenues for software teams to engage general users despite limited resources, enhancing software development and user satisfaction.
Findings
User involvement improves software relevance and usability.
Engagement strategies benefit both users and development teams.
Case study of CASA illustrates effective user interaction methods.
Abstract
In science, the lifecycle of software products is typically managed with limited resources while facing unlimited demand. Scientific software requirements are necessarily often dominated by internal project specifications and deadlines, but these internal priorities, while beneficial for the community as a whole, do not always align with the individual needs of our ultimate customers: general users. For software products to have the broadest reach, ideally the general user community should be involved in all aspects of the data lifecycle, but reality is that user expectations need to be managed. Based on the lifecycle of the Common Astronomy Software Applications for radio astronomy (CASA), we will show avenues for software teams to interact with general users, even when facing limited resources for user support. We will discuss how involvement of users and user groups in prioritizing…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
