HCI analysis in mobile, multimodal scenarios

The Android HCI Extractor (AHE11) is a Multimodal Human-Computer-Interaction extractor for Android. This tool is able to extract / monitor / track the interaction between the user and the system in multimodal Android environments. This tool was used in a real experiment to record multimodal interaction into a run-time model instance that can be used to implement both run-time --e.g. user monitoring in an infotainment vehicle system-- and off-line analysis --e.g. user interaction comparison using the same application in different Android-based devices--.
Different versions of this tool have been successfully integrated into a real Android multimodal applications, as a proof of concept for the PALADIN and CARIM projects.
+info & download
PALADIN provides a common, generic, and dynamic way to represent human-computer interaction in multimodal contexts. It is a parameter-based model in which multimodal interaction is dinamically described. Instances of such model represent multimodal human-computer interaction, and can be the basis for future analysis, comparison, transformation, and decision processes.
+info & downloads
CARIM aims at modeling quality of experience (QoE) in mobile environments. It is based on a meta-model that establishes a set of parameters to dynamically describe user/system interaction, as well as the context in which it is carried. The attractiveness of the interaction process is also represented by a set of parameters that denote how attractive and user friendly the system/application is.
+info & downloads

Software and GUI Testing

OPEN HMI TESTER is an Open Source GUI Testing tool which follows an open architecture that describes a non intrusive capture/replay tool based on GUI (and non-GUI) Events. Its aim is to give developers the possibility of testing HMIs (Human-Machine Interfaces) by performing both a recording (capturing the events generated by the tested HMI) and replay (executing the previously recorded events) processes over the tested application. +info & download

Usability Testing

The OHT+ Framework is completely open and portable. Its design describes a flexible architecture which can be adapted to many development and testing environments; even, this framework is also agnostic to the operating system and the windowing system... more

OHT+Behavior
It includes the basic functionality corresponding to the abstraction of the user interaction. The aim of this tool is to capture the mouse clicks and keyboard interaction on a GUI.
+info & download


OHT+Experience
The aim of this tool is to extract the user experience from the interaction with a software. It allows the testers to perform most of the whole process of a usability test: the briefing stage (composed of a set of test cases), guide the user during test-cases, and store comments and impression from the users.
+info & download


OHT+Inspector
The aim of this tool is to perform a reviewing process over a system or a GUI based on a set of constraints and guidelines. For this purpose, this tool uses evaluators which encapsulate the knowledge of usability experts and automate the inspection process.
+info & download

GUI Data RT Verification

This is a dynamic approach to analyze input data in graphical user interfaces (GUIs) during user interaction. This framework describes a verification layer located between the GUI and the business logic. When changes on GUI values are detected, a verification process is triggered to determine whether the data requirements in the SRS are met. To ease the process, verification rules are included in separate files, and the verification process (and its logic) is transparent to the developer.
+info & download

Agile Prototyping

This solution is aimed at supporting a sheer iterative prototyping and development approach. It proposes to reuse digital low-fi prototypes from the very beginning. Such prototypes are iteratively refined and developed into hi-fidelity prototypes towards the end-user application.
+info & download

Advanced Widget Features


GUI automatic arrangement
This algorithm automatically arranges the widgets composing a GUI depending on the relationships between them, and on the features of the container dialog. Initial widgets’ layout (if exist) is broken, and a new AutomaticLayout object is added in order to arrange all the elements in a container/dialog/window.
discussion thread
Restricted Layout
It is a GridLayout in which the internal widgets meet a set of size requirements. When some widgets can not be shown due to size restrictions, two flow-control buttons appear to allow us to show hidden ones. Those size requirements can be changed in runtime.
discussion thread