Supporting end-user debugging of trigger-action rules for IoT applications

•A method for supporting debugging of trigger-action rules.•A tool supporting the debugging method with the possibility to simulate the corresponding contexts of use.•A solution integrated in the tool for detecting possible conflicts amongst the trigger-action rules.•An empirical validation that the...

Full description

Saved in:
Bibliographic Details
Published in:International journal of human-computer studies Vol. 123; pp. 56 - 69
Main Authors: Manca, Marco, Paternò, Fabio, Santoro, Carmen, Corcella, Luca
Format: Journal Article
Language:English
Published: Elsevier Ltd 01.03.2019
Subjects:
Debugging
End user development
Internet of things
Trigger-Action Rules
Internet of things
End user development
Trigger-Action Rules
Debugging
ISSN:1071-5819, 1095-9300
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:•A method for supporting debugging of trigger-action rules.•A tool supporting the debugging method with the possibility to simulate the corresponding contexts of use.•A solution integrated in the tool for detecting possible conflicts amongst the trigger-action rules.•An empirical validation that the tool allows users to identify and correct mistakes in their trigger-action rules more accurately. End users need tools to enable them to control and personalise Internet of Things (IoT) applications, which may involve hundreds of interconnected objects. Trigger-action programming has shown to be a useful support for this purpose because it allows users to easily associate dynamic events with the activation of desired effects. End User Development (EUD) tools aim to allow even users without programming experience to define the behaviour of IoT applications. However, users may define rules triggering various actions that may be in conflict, or may specify rules that do not result in the intended behaviour. Although such situations can often occur, there seems to be a lack of tools able to help users understand whether the specified rules actually bring about the desired behaviour and, if not, the reasons why they fail. We present an original solution for filling this gap, which takes into account the specific aspects of trigger-action rules. We describe the design and implementation of this debugging support, and then discuss the results of a first user test.
ISSN:1071-5819
1095-9300
DOI:10.1016/j.ijhcs.2018.11.005