Experiences with User-Centered Design for the Tigres Workflow API

Abstract

Scientific data volumes have been growing exponentially. This has resulted in the need for new tools that enable users to operate on and analyze data. Cyberinfrastructure tools, including workflow tools, that have been developed in the last few years has often fallen short of user needs and suffered from lack of wider adoption. User-centered Design (UCD) process has been used as an effective approach to develop usable software with high adoption rates. However, UCD has largely been applied for user-interfaces and there has been limited work in applying UCD to application program interfaces and cyberinfrastructure tools. We use an adapted version of UCD that we refer to as Scientist-Centered Design (SCD) to engage with users in the design and development of Tigres, a workflow application programming interface. Tigres provides a simple set of programming templates (e.g., sequence, parallel, split, merge) that can be can used to compose and execute computational and data transformation pipelines. In this paper, we describe Tigres and discuss our experiences with the use of UCD for the inital development of Tigres. Our experience-to-date is that the UCD process not only resulted in better requirements gathering but also heavily influenced the architecture design and implementation details. User engagement during the development of tools such as Tigres is critical to ensure usability and increase adoption.

GinFlow: A Decentralised Adaptive Workflow Execution Manager

“…Case study: Possible shapes of workflows are virtually infinite, however four major patterns, namely split, merge, sequence and parallel have been recognised to cover the basic needs of many scientific computational pipelines [13]. We consequently decided to conduct the experiments of Sections V-A, V-B and V-C using a diamond shape depicted in Fig.…”

A metadata reporting framework (FRAMES) for synthesis of ecohydrological observations

“…The approach we used to develop FRAMES involved a combination of agile development principles and scientist-centered design (Ramakrishnan et al, 2014). Agile development uses short incremental development cycles with reassessment of priorities and solicitation of feedback after each cycle.…”

ASCR Cybersecurity for Scientific Computing Integrity

“…Though provenance tools have been created, such as Harvard's PASS system [MRBH+09], and though provenance standards are beginning to be created, such as via W3C [PROV], these tools and standards need to be embedded within data centers in a way that is clearly cognizant of the use environments, particularly including performance issues, and be expressly examined for their applicability to the unique challenges of extreme scale scientific computing integrity. Therefore, the nuanced provenance information must be captured to enable reproduction and perhaps even replay via an executable scientific workflow such as the DOEfunded Tigres project [RPH+14].…”