Ten Simple Rules for making a software tool workflow-readyCitation formats

  • External authors:
  • Paul Brack
  • Peter Crowther
  • Douglas Lowe
  • Quentin Groom
  • Mathias Dillen
  • Frederik Coppens
  • Björn Grüning
  • Ignacio Eguinoa
  • Philip Ewels

Standard

Ten Simple Rules for making a software tool workflow-ready. / Brack, Paul; Crowther, Peter; Soiland-Reyes, Stian; Owen, Stuart; Lowe, Douglas; Williams, Alan R; Groom, Quentin; Dillen, Mathias; Coppens, Frederik; Grüning, Björn; Eguinoa, Ignacio; Ewels, Philip; Goble, Carole.

In: PLoS computational biology, Vol. 18, No. 3, e1009823, 24.03.2022.

Research output: Contribution to journalArticlepeer-review

Harvard

Brack, P, Crowther, P, Soiland-Reyes, S, Owen, S, Lowe, D, Williams, AR, Groom, Q, Dillen, M, Coppens, F, Grüning, B, Eguinoa, I, Ewels, P & Goble, C 2022, 'Ten Simple Rules for making a software tool workflow-ready', PLoS computational biology, vol. 18, no. 3, e1009823. https://doi.org/10.5281/zenodo.5901220, https://doi.org/10.1371/journal.pcbi.1009823

APA

Brack, P., Crowther, P., Soiland-Reyes, S., Owen, S., Lowe, D., Williams, A. R., Groom, Q., Dillen, M., Coppens, F., Grüning, B., Eguinoa, I., Ewels, P., & Goble, C. (2022). Ten Simple Rules for making a software tool workflow-ready. PLoS computational biology, 18(3), [e1009823]. https://doi.org/10.5281/zenodo.5901220, https://doi.org/10.1371/journal.pcbi.1009823

Vancouver

Author

Brack, Paul ; Crowther, Peter ; Soiland-Reyes, Stian ; Owen, Stuart ; Lowe, Douglas ; Williams, Alan R ; Groom, Quentin ; Dillen, Mathias ; Coppens, Frederik ; Grüning, Björn ; Eguinoa, Ignacio ; Ewels, Philip ; Goble, Carole. / Ten Simple Rules for making a software tool workflow-ready. In: PLoS computational biology. 2022 ; Vol. 18, No. 3.

Bibtex

@article{079e4185bac74a90be68b86d44f78dbb,
title = "Ten Simple Rules for making a software tool workflow-ready",
abstract = "Workflows have become a core part of computational scientific analysis in recent years. Automated computational workflows multiply the power of researchers, potentially turning “hand-cranked” data processing by informaticians into robust factories for complex research output.However, in order for a piece of software to be usable as a workflow-ready tool, it may require alteration from its likely origin as a standalone tool. Research software is often created in response to the need to answer a research question with the minimum expenditure of time and money in resource-constrained projects. The level of quality might range from “it works on my computer” to mature and robust projects with support across multiple operating systems.Despite significant increase in uptake of workflow tools, there is little specific guidance for writing software intended to slot in as a tool within a workflow; or on converting an existing standalone research-quality software tool into a reusable, composable, well-behaved citizen within a larger workflow.In this paper we present 10 simple rules for how a software tool can be prepared for workflow use.",
author = "Paul Brack and Peter Crowther and Stian Soiland-Reyes and Stuart Owen and Douglas Lowe and Williams, {Alan R} and Quentin Groom and Mathias Dillen and Frederik Coppens and Bj{\"o}rn Gr{\"u}ning and Ignacio Eguinoa and Philip Ewels and Carole Goble",
note = "Accepted at PLOS Computational Biology (PCOMPBIOL-D-21-01704R1)",
year = "2022",
month = mar,
day = "24",
doi = "10.5281/zenodo.5901220",
language = "English",
volume = "18",
journal = "PL o S Computational Biology",
issn = "1553-7358",
publisher = "Public Library of Science",
number = "3",

}

RIS

TY - JOUR

T1 - Ten Simple Rules for making a software tool workflow-ready

AU - Brack, Paul

AU - Crowther, Peter

AU - Soiland-Reyes, Stian

AU - Owen, Stuart

AU - Lowe, Douglas

AU - Williams, Alan R

AU - Groom, Quentin

AU - Dillen, Mathias

AU - Coppens, Frederik

AU - Grüning, Björn

AU - Eguinoa, Ignacio

AU - Ewels, Philip

AU - Goble, Carole

N1 - Accepted at PLOS Computational Biology (PCOMPBIOL-D-21-01704R1)

PY - 2022/3/24

Y1 - 2022/3/24

N2 - Workflows have become a core part of computational scientific analysis in recent years. Automated computational workflows multiply the power of researchers, potentially turning “hand-cranked” data processing by informaticians into robust factories for complex research output.However, in order for a piece of software to be usable as a workflow-ready tool, it may require alteration from its likely origin as a standalone tool. Research software is often created in response to the need to answer a research question with the minimum expenditure of time and money in resource-constrained projects. The level of quality might range from “it works on my computer” to mature and robust projects with support across multiple operating systems.Despite significant increase in uptake of workflow tools, there is little specific guidance for writing software intended to slot in as a tool within a workflow; or on converting an existing standalone research-quality software tool into a reusable, composable, well-behaved citizen within a larger workflow.In this paper we present 10 simple rules for how a software tool can be prepared for workflow use.

AB - Workflows have become a core part of computational scientific analysis in recent years. Automated computational workflows multiply the power of researchers, potentially turning “hand-cranked” data processing by informaticians into robust factories for complex research output.However, in order for a piece of software to be usable as a workflow-ready tool, it may require alteration from its likely origin as a standalone tool. Research software is often created in response to the need to answer a research question with the minimum expenditure of time and money in resource-constrained projects. The level of quality might range from “it works on my computer” to mature and robust projects with support across multiple operating systems.Despite significant increase in uptake of workflow tools, there is little specific guidance for writing software intended to slot in as a tool within a workflow; or on converting an existing standalone research-quality software tool into a reusable, composable, well-behaved citizen within a larger workflow.In this paper we present 10 simple rules for how a software tool can be prepared for workflow use.

U2 - 10.5281/zenodo.5901220

DO - 10.5281/zenodo.5901220

M3 - Article

VL - 18

JO - PL o S Computational Biology

JF - PL o S Computational Biology

SN - 1553-7358

IS - 3

M1 - e1009823

ER -