Limits...
ECCE Toolkit: Prototyping Sensor-Based Interaction

View Article: PubMed Central - PubMed

ABSTRACT

Building and exploring physical user interfaces requires high technical skills and hours of specialized work. The behavior of multiple devices with heterogeneous input/output channels and connectivity has to be programmed in a context where not only the software interface matters, but also the hardware components are critical (e.g., sensors and actuators). Prototyping physical interaction is hindered by the challenges of: (1) programming interactions among physical sensors/actuators and digital interfaces; (2) implementing functionality for different platforms in different programming languages; and (3) building custom electronic-incorporated objects. We present ECCE (Entities, Components, Couplings and Ecosystems), a toolkit for non-programmers that copes with these issues by abstracting from low-level implementations, thus lowering the complexity of prototyping small-scale, sensor-based physical interfaces to support the design process. A user evaluation provides insights and use cases of the kind of applications that can be developed with the toolkit.

No MeSH data available.


The Entity Runtime. Input events from sensor data and remote events from other entities are interpreted (Behavior Interpreter) and the corresponding output event to another remote endpoint (or to the same entity as well) is generated.
© Copyright Policy - open-access
Related In: Results  -  Collection

License
getmorefigures.php?uid=PMC5375724&req=5

sensors-17-00438-f009: The Entity Runtime. Input events from sensor data and remote events from other entities are interpreted (Behavior Interpreter) and the corresponding output event to another remote endpoint (or to the same entity as well) is generated.

Mentions: The Ecosystem Server acts as a central communication unit. All the messages from one object to another pass through it and it maintains the data structures for validating the interaction rules between physical and virtual objects. As implemented by the Entity Runtime (see Figure 9), the server receives events from remote sensors and dispatch the event to the corresponding entity. On the server side, the Behavior Interpreter checks if the event meets a specific trigger value defined in the interaction rules and, if there is any, it generates a message with the corresponding outcome to be routed to other devices (including the source device) that (i) will activate an actuator or (ii) will update an attribute of a digital element on a display-enabled device, according to the received output event.


ECCE Toolkit: Prototyping Sensor-Based Interaction
The Entity Runtime. Input events from sensor data and remote events from other entities are interpreted (Behavior Interpreter) and the corresponding output event to another remote endpoint (or to the same entity as well) is generated.
© Copyright Policy - open-access
Related In: Results  -  Collection

License
Show All Figures
getmorefigures.php?uid=PMC5375724&req=5

sensors-17-00438-f009: The Entity Runtime. Input events from sensor data and remote events from other entities are interpreted (Behavior Interpreter) and the corresponding output event to another remote endpoint (or to the same entity as well) is generated.
Mentions: The Ecosystem Server acts as a central communication unit. All the messages from one object to another pass through it and it maintains the data structures for validating the interaction rules between physical and virtual objects. As implemented by the Entity Runtime (see Figure 9), the server receives events from remote sensors and dispatch the event to the corresponding entity. On the server side, the Behavior Interpreter checks if the event meets a specific trigger value defined in the interaction rules and, if there is any, it generates a message with the corresponding outcome to be routed to other devices (including the source device) that (i) will activate an actuator or (ii) will update an attribute of a digital element on a display-enabled device, according to the received output event.

View Article: PubMed Central - PubMed

ABSTRACT

Building and exploring physical user interfaces requires high technical skills and hours of specialized work. The behavior of multiple devices with heterogeneous input/output channels and connectivity has to be programmed in a context where not only the software interface matters, but also the hardware components are critical (e.g., sensors and actuators). Prototyping physical interaction is hindered by the challenges of: (1) programming interactions among physical sensors/actuators and digital interfaces; (2) implementing functionality for different platforms in different programming languages; and (3) building custom electronic-incorporated objects. We present ECCE (Entities, Components, Couplings and Ecosystems), a toolkit for non-programmers that copes with these issues by abstracting from low-level implementations, thus lowering the complexity of prototyping small-scale, sensor-based physical interfaces to support the design process. A user evaluation provides insights and use cases of the kind of applications that can be developed with the toolkit.

No MeSH data available.