Towards Canonical Task Types for User Interface Design

Calleros, Juan Manuel Gonzalez; Guerrero-García, Josefina; Vanderdonckt, Jean; Muñoz-Arteaga, Jaime

doi:10.1109/la-web.2009.33

Cited by 6 publications

(4 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In software engineering, a specification-based (or model-driven) approach relies on the power of models to construct and reason about software systems. Our approach to build the architecture is based on models, and we use UML diagrams to express them, as well as task models [43] with canonical task definitions [44] as a baseline to document user needs and interaction in the user interface. The benefit of developing software with a rational set of principles includes, but is not limited to, reproducibility and its orientation towards quality criteria.…”

Section: Home Energy Management System With Iot Demand System Archite...mentioning

confidence: 99%

See 1 more Smart Citation

Methodology for Designing an Electricity Demand System in the Context of IoT Household

et al. 2022

View full text Add to dashboard Cite

Many efforts have been made to create scenarios whereby interconnecting IoT can be used. The primary objective of these efforts has been to centralize its access as a single list and to monitor its use and trigger its different functionalities from apps. However, few efforts have addressed the problem of electricity consumption from those devices in the context of a residence. Existing datasets for machine predictive systems are focused on data analytics for global consumption but neglect the use of such solutions by the common citizen as a means of re-educating our citizens and optimizing electricity consumption. Without considering the environmental impact and the urgent need to address this growing global emergency, ordinary citizens require systems that help them be aware of what they consume and thus aspire to make a change. In this work, we propose a methodology that builds on the formal mathematical modeling and development of a simulator to substitute the need to collect real data from real world context of use, as well as an interactive system that integrates the whole process. By adding this module to the architecture our prior work, this work is ready for use in real-life scenarios where electrical consumption could be significantly reduced.

show abstract

Section: Home Energy Management System With Iot Demand System Archite...mentioning

confidence: 99%

“…The results of the process are the vision board of the project, PERSONAS, user need, and functionalities, and the value added to user's life is written at the end. Functionality is defined by working around ca nonical task types [44]. Tasks were defined in the previous steps; at this point, the question is how they are going to be implemented.…”

mentioning

confidence: 99%

Methodology for Designing an Electricity Demand System in the Context of IoT Household

et al. 2022

View full text Add to dashboard Cite

show abstract

“…For our study, we selected a set of 30 commands for common interactions from the current literature, which were divided into four groups, along with their referents, which were presented with a stimulus before and after the command ( Fig. 12): a group of 4 basic commands (''Turn light on/off'' and ''Brighten/dim light'') [23], [47], a group of 13 selection commands (e.g., ''Select a date in digital/analog format'') [48], a group of 9 commands that are based on sets (e.g., ''Expand/collapse a set of menu items'', ''Select an item from the full set of data'', and ''Select (again) from the selected subset'') [48], [49], and a group of 4 referents for specification (''Specify a position, a direction, a translation, and a rotation'') [50]. These tasks have been chosen to cover an increasing number of dimensions, from 0D (e.g., ''Turn light on''), 1D (e.g., ''Dim light''), and 2D (e.g., ''Specify a position''), to 2D1/2 (e.g., ''Specify a translation'').…”

Section: Confirmatory Studymentioning

confidence: 99%

Eliciting Contact-Based and Contactless Gestures With Radar-Based Sensors

et al. 2019

Self Cite

View full text Add to dashboard Cite

Radar sensing technologies now offer new opportunities for gesturally interacting with a smart environment by capturing microgestures via a chip that is embedded in a wearable device, such as a smartwatch, a finger or a ring. Such microgestures are issued at a very small distance from the device, regardless of whether they are contact-based, such as on the skin, or contactless. As this category of microgestures remains largely unexplored, this paper reports the results of a gesture elicitation study that was conducted with twenty-five participants who expressed their preferred user-defined gestures for interacting with a radar-based sensor on nineteen referents that represented frequent Internet-of-things tasks. This study clustered the 25 × 19 = 475 initially elicited gestures into four categories of microgestures, namely, micro, motion, combined, and hybrid, and thirty-one classes of distinct gesture types and produced a consensus set of the nineteen most preferred microgestures. In a confirmatory study, twenty new participants selected gestures from this classification for thirty referents that represented tasks of various orders; they reached a high rate of agreement and did not identify any new gestures. This classification of radar-based gestures provides researchers and practitioners with a larger basis for exploring gestural interactions with radar-based sensors, such as for hand gesture recognition.

show abstract

“…Hearst et al showed that faceted navigation is an effective method that can be helpful during a design activity [14]. CHIDeK's facets are based on: task types based on the work of Gonzalles-Caleros et al [15], which are verbs, such as search or navigate; design artifacts, such as screenshots or documents; UI widgets, such as buttons and text fields; and UI patterns extracted from UI pattern libraries, 1,2 such as wizard and breadcrumbs. The task types facets were created to give the designer an option to browse cases adopting a problembased approach or using a more abstract representation than widgets, whereas the UI patterns and widgets facets were created to provide a more concrete representation when following a solution-based approach.…”

Section: The Case Library Shows the Title Of The Cases And A Small Thmentioning

confidence: 99%

Investigating the Case-Based Reasoning Process During HCI Design

Motta

Barbosa²

2015

JIS

View full text Add to dashboard Cite

Given that the design activity makes use of previous design knowledge, we turned to case-based reasoning (CBR) to help identify opportunities to support the design of human-computer interaction (HCI). Using interviews with professional designers and Semiotic Engineering, we developed a CBR tool called CHIDeK (Computer-Human Interaction Design Knowledge), with which we conducted a study to observe how it influenced the HCI design activity. We found that the cases recorded in CHIDeK supported design by motivating the designers’ reflective process, triggering their memories of experiences with similar systems, and helping to generate new ideas. We have also identified limitations in our case representation and case access methods, which offer opportunities for further research.

show abstract

Towards Canonical Task Types for User Interface Design

Cited by 6 publications

References 16 publications

Methodology for Designing an Electricity Demand System in the Context of IoT Household

Methodology for Designing an Electricity Demand System in the Context of IoT Household

Eliciting Contact-Based and Contactless Gestures With Radar-Based Sensors

Investigating the Case-Based Reasoning Process During HCI Design

Contact Info

Product

Resources

About