---
title: "Ten simple rules for making a software tool workflow-ready"
url: "https://phil.ewels.co.uk/publications/2022/brack-plos-computational-biology"
site: "phil.ewels.co.uk"
author: "Phil Ewels"
section: "Publications"
journal: "PLOS Computational Biology"
published: "2022-03-24"
doi: "https://doi.org/10.1371/journal.pcbi.1009823"
authors: "Paul Brack, Peter Crowther, Stian Soiland-Reyes, Stuart Owen, Douglas Lowe, Alan R. Williams, Quentin Groom, Mathias Dillen, Frederik Coppens, Björn Grüning, Ignacio Eguinoa, Philip Ewels, Carole Goble"
---

# Ten simple rules for making a software tool workflow-ready

In recent years, the volumes of data to be analyzed, as well as the complexity of that analysis, across many scientific fields (from genomics through to exoplanet exploration) have increased massively. As a consequence, workflows (abstract representations of data flow between multiple analytic tools) have become a core part of computational scientific analysis. Automated computational workflows multiply the power of researchers, potentially turning "handcranked" 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 stand-alone 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 [3, 4]. The level of quality might range from “it works on my computer” to mature and robust projects with support across multiple operating systems.

---

From the personal website of Phil Ewels, a software developer and bioinformatician in Stockholm, Sweden: https://phil.ewels.co.uk/
The whole site as Markdown: https://phil.ewels.co.uk/llms.txt