Ten simple rules for making a software tool workflow-ready

Crucially, one should not expect software to automate well simply because it is mature and from a reliable source—a prime example of this is Microsoft Office, which Microsoft specifically advises is not supported to be run unattended in a robotic process automation (RPA) environment [14]. [...]your...

Full description

Saved in:
Bibliographic Details
Published inPLoS computational biology Vol. 18; no. 3; p. e1009823
Main Authors 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
Format Journal Article
LanguageEnglish
Published United States Public Library of Science 01.03.2022
Public Library of Science (PLoS)
Subjects
Automation
biology
Biology and Life Sciences
Computational Biology
Computer and Information Sciences
Documentation
Engineering and Technology
Methods
Science Policy
Social Sciences
Software
Software development tools
Software engineering
Software quality
Workflow
Workflow software
United Kingdom
Online AccessGet full text

Cover

More Information
Summary:Crucially, one should not expect software to automate well simply because it is mature and from a reliable source—a prime example of this is Microsoft Office, which Microsoft specifically advises is not supported to be run unattended in a robotic process automation (RPA) environment [14]. [...]your software project must have some high-level project documentation, describing what your project is intended to do and who it will be useful for. [...]your project must include interface-level documentation. First and foremost, your software project must use source control software, such as Git [24] or Subversion [25].
Bibliography:SourceType-Other Sources-1
content type line 63
ObjectType-Editorial-2
ObjectType-Commentary-1
ObjectType-Article-3
The authors have declared that no competing interests exist.
ISSN:1553-7358
1553-734X
1553-7358
DOI:10.1371/journal.pcbi.1009823