2017
DOI: 10.6084/m9.figshare.5331814.v3
|View full text |Cite
|
Sign up to set email alerts
|

Track 1 Paper: Good Usability Practices in Scientific Software Development

Help me understand this report
View preprint versions

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2019
2019
2022
2022

Publication Types

Select...
2
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(3 citation statements)
references
References 0 publications
0
3
0
Order By: Relevance
“…WSSSPE5.1 included the presentation of four 12-minute talks based on accepted papers [10,11,12,13], and seven 6-minute lightning talks [14,15,16,17,18,19,20].…”
Section: Presentationsmentioning
confidence: 99%
“…WSSSPE5.1 included the presentation of four 12-minute talks based on accepted papers [10,11,12,13], and seven 6-minute lightning talks [14,15,16,17,18,19,20].…”
Section: Presentationsmentioning
confidence: 99%
“…The presence of a graphical user interface (GUI) is sometimes seen as an indication of usability (Remy, 2005;Rubin et al, 2018). However, a GUI does not necessarily make software more user-friendly, almost always limits flexibility, increases the programming effort, and makes reproducibility of results and workflows harder or even unfeasible (Queiroz et al, 2017). Also note that in recent years pow-erful tools emerged in data science to represent data along with code snippets, documentation and results in interactive computational notebooks provided by Jupyter (Perkel, 2018;Beg et al, 2021).…”
Section: Introductionmentioning
confidence: 99%
“…Hence, authors of this foundational layer in scientific software stacks need to take into account the continued use and possibly further development outside the field of mathematics. Best practices for mathematical software [6] and numerical software [20,3] are long known (yet still not established), and properties such as reliability, robustness or transportability [5], the numerical experiment attributes replicability, reproducibility and reusability [9], code as a form of scientific notation [11], as well as basic guidelines for research software [23] have been discussed in the literature, yet, sustainable hand-over strategies for (mathematical) research software projects have not been documented to the best knowledge of the authors.…”
Section: Introductionmentioning
confidence: 99%