Defining usability heuristics for adoption and efficiency of an electronic workflow document management system

Usability heuristics have been established for different uses and applications as general guidelines for user interfaces. These can affect the implementation of industry solutions and play a significant role regarding cost reduction and process efficiency. The area of electronic workflow document management (EWDM) solutions, also known as workflow, lacks a formal definition of usability heuristics. With the advent of new technologies such as mobile devices, defining a set of usability heuristics contributes to the adoption and efficiency of an EWDM system. Workflow usability has been evaluated for various industries. Most significantly research has been done for electronic healthcare records (EHR). In other areas such as the financial sector and educational institutions there is also some literature available but not as abundant as for EHR. This was identified as a possible research limitation. The general purpose of this research was to establish and validate an overarching set of usability heuristics for EWDM in general. This was approached by conducting a literature review and a survey on 32 workflow consultants from Hyland Software, Inc. Quantitative and qualitative data was collected focusing on the study’s main research question: “what usability heuristics should be defined to ensure the adoption and efficiency of a workflow implementation? Findings based on regression testing and expert opinions have suggested a proposed set of usability heuristics. The final list consists of: adaptability to diverse platforms, user control, system feedback, intuitive interfaces, visibility on mobile devices, error management, help, and documentation

Tackling complexity in high performance computing applications

We present a software framework that supports the specification of userdefinable configuration options in HPC applications independently of the application code itself. Such options include model parameter values, the selection of numerical algorithm, target platform etc. and additional constraints that prevent invalid combinations of options from being made. Such constraints, which are capable of describing complex cross-domain dependencies, are often crucial to the correct functioning of the application and are typically either completely absent from the code or a hard to recover from it. The framework uses a combination of functional workflows and constraint solvers. Application workflows are built from a combination of functional components: higher-order co-ordination forms and first-order data processing components which can be either concrete or abstract, i.e. without a specified implementation at the outset. A repository provides alternative implementations for these abstract components. A constraint solver, written in Prolog, guides a user in making valid choices of parameters, implementations, machines etc. for any given context. Partial designs can be stored and shared providing a systematic means of handling application use and maintenance. We describe our methodology and illustrate its application in two classes of application: a data intensive commercial video transcoding example and a numerically intensive incompressible Navier–Stokes solver