Beyond Levels of Automation: Developing More Detailed Guidance for Human Automation Interaction Design

2018 ◽  
Vol 62 (1) ◽  
pp. 150-154 ◽  
Author(s):  
Emilie Roth ◽  
Beth Depass ◽  
Jonathan Harter ◽  
Ronald Scott ◽  
Jeffrey Wampler
Keyword(s):  
Software Architecture ◽  
User Interfaces ◽  
Interaction Design ◽  
Design Decisions ◽  
Planning And Scheduling ◽  
Automation Systems ◽  
Levels Of Automation ◽  
Airlift Planning ◽  
High Level ◽  
Design Challenges

There is growing recognition of a need to go beyond levels of automation frameworks to provide more detailed guidance for design of effective human automation interaction (HAI). Here we present some design questions that are important for designers of HAI to address as they develop the requirements for the software architecture and user interfaces for automated aids. This set of guiding questions has grown out of our experience in developing a series of successful collaborative automation systems for airlift planning and scheduling. We illustrate through examples how answers to these high-level questions helped inform the HAI design decisions we confronted. The set of questions are offered in an attempt to broaden the discussion of how best to provide guidance to system developers confronted with HAI design challenges.

Model-Based Approaches to Human-Automation Systems Design

2012 ◽  
Author(s):  
Greg A. Jamieson ◽  
Jonas Andersson ◽  
Ann Bisantz ◽  
Asaf Degani ◽  
Morten Lind
Keyword(s):  
Complex Systems ◽  
Interaction Design ◽  
Systems Design ◽  
Limited Range ◽  
Design Activity ◽  
Panel Session ◽  
Automation Systems ◽  
Explicit Consideration ◽  
Design Challenges

Human-automation interaction in complex systems is common, yet design for this interaction is often conducted without explicit consideration of the role of the human operator. Fortunately, there are a number of modeling frameworks proposed for supporting this design activity. However, the frameworks are often adapted from other purposes, usually applied to a limited range of problems, sometimes not fully described in the open literature, and rarely critically reviewed in a manner acceptable to proponents and critics alike. The present paper introduces a panel session wherein these proponents (and reportedly one or two critics) can engage one another on several agreed questions about such frameworks. The goal is to aid non-aligned practitioners in choosing between alternative frameworks for their human-automation interaction design challenges.

scholarly journals User Interface Stereotypes: A Model-Based Approach for Information Systems User Interfaces

2014 ◽  
Author(s):  
Sofia Larissa Da Costa ◽  
Valdemar Vicente Graciano Neto ◽  
Juliano Lopes De Oliveira ◽  
Bruno dos Reis Calçado
Keyword(s):  
Information Systems ◽  
User Interface ◽  
Software Development ◽  
Software Architecture ◽  
User Interfaces ◽  
Model Based ◽  
Behavioral Aspects ◽  
Definition Of ◽  
High Level ◽  
And Behavior

This paper presents a model-based approach to build Information Systems User Interfaces (ISUI). In this approach, UI presentation and behavioral aspects are modeled as UI Stereotypes, which are high level abstractions of UI appearance and interaction features. A taxonomy of ISUI elements is proposed as the basis for definition of UI stereotypes. These elements are orchestrated on a software architecture which manages model-based UI building and integration with the IS applications. The proposed approach reduces software development efforts and costs, facilitating maintenance and evolution of ISUI. Moreover, UI stereotypes improve usability, consistency, reuse and standardization of both presentation and behavior of ISUI.

What can you Learn from a Low-Fidelity Prototype?

1989 ◽  
Vol 33 (4) ◽  
pp. 224-228 ◽  
Author(s):  
Robert A. Virzi
Keyword(s):  
User Interface ◽  
Design Process ◽  
User Interfaces ◽  
Design Principles ◽  
Design Phase ◽  
Central Tendency ◽  
Design Decisions ◽  
Design Information ◽  
High Level ◽  
Interface Designs

A case is made for using low-fidelity prototypes early in the design phase of new services. The rationale for this is based upon (1) a model of how user interface designs progress and (2) a call to expediency. The design process is viewed as the successive application of constraints that serve to prune the space of all user interfaces. Some constraints are external (i.e., placed on the service by limits of technology or cost). Other constraints are derived by application of heuristic design principles. Even after these constraints have been applied, the design is still not fully constrained and the designer must make high-level design decisions. At these choice points, I propose that low-fidelity prototyping is an appropriate means of gathering design information as it is an expedient solution and may serve as a method of testing the central tendency of entire classes of user interfaces.

scholarly journals Levels of What?Investigating Drivers’ Understanding of Different Levels of Automation in Vehicles

2021 ◽  
pp. 155534342110090
Author(s):  
Fjollë Novakazi ◽  
Mikael Johansson ◽  
Helena Strömberg ◽  
MariAnne Karlsson
Keyword(s):  
Interaction Design ◽  
Design Guidelines ◽  
Automation System ◽  
Automated Systems ◽  
Attentional Demand ◽  
Design Decisions ◽  
Wizard Of Oz ◽  
Traffic Conditions ◽  
Levels Of Automation ◽  
Different Levels

Extant levels of automation (LoAs) taxonomies describe variations in function allocations between the driver and the driving automation system (DAS) from a technical perspective. However, these taxonomies miss important human factors issues and when design decisions are based on them, the resulting interaction design leaves users confused. Therefore, the aim of this paper is to describe how users perceive different DASs by eliciting insights from an empirical driving study facilitating a Wizard-of-Oz approach, where 20 participants were interviewed after experiencing systems on two different LoAs under real driving conditions. The findings show that participants talked about the DAS by describing different relationships and dependencies between three different elements: the context (traffic conditions, road types), the vehicle (abilities, limitations, vehicle operations), and the driver (control, attentional demand, interaction with displays and controls, operation of vehicle), each with associated aspects that indicate what users identify as relevant when describing a vehicle with automated systems. Based on these findings, a conceptual model is proposed by which designers can differentiate LoAs from a human-centric perspective and that can aid in the development of design guidelines for driving automation.

Introduction

2018 ◽  
Author(s):  
Xiaojun Bi ◽  
Andrew Howes ◽  
Per Ola Kristensson ◽  
Antti Oulasvirta ◽  
John Williamson
Keyword(s):  
Information Visualization ◽  
User Interfaces ◽  
Graphic Design ◽  
Interaction Design ◽  
Human Interaction ◽  
Learning Design ◽  
Human Factors Engineering ◽  
Interaction Techniques ◽  
Iterative Design ◽  
And Control

This chapter introduces the field of computational interaction, and explains its long tradition of research on human interaction with technology that applies to human factors engineering, cognitive modelling, artificial intelligence and machine learning, design optimization, formal methods, and control theory. It discusses how the book as a whole is part of an argument that, embedded in an iterative design process, computational interaction design has the potential to complement human strengths and provide a means to generate inspiring and elegant designs without refuting the part played by the complicated, and uncertain behaviour of humans. The chapters in this book manifest intellectual progress in the study of computational principles of interaction, demonstrated in diverse and challenging applications areas such as input methods, interaction techniques, graphical user interfaces, information retrieval, information visualization, and graphic design.

scholarly journals E-learning-Oriented Software Architecture Design and Case Study

2015 ◽  
Vol 10 (4) ◽  
pp. 59
Author(s):  
Peng Lu ◽  
Xiao Cong ◽  
Dongdai Zhou
Keyword(s):  
Software Architecture ◽  
Building Blocks ◽  
Domain Model ◽  
Learning System ◽  
Application Framework ◽  
Component Library ◽  
E Learning ◽  
The Difference ◽  
High Level

Nowadays, E-learning system has been widely applied to practical teaching. It was favored by people for its characterized course arrangement and flexible learning schedule. However, the system does have some problems in the process of application such as the functions of single software are not diversified enough to satisfy the requirements in teaching completely. In order to cater more applications in the teaching process, it is necessary to integrate functions from different systems. But the difference in developing techniques and the inflexibility in design makes it difficult to implement. The major reason of these problems is the lack of fine software architecture. In this article, we build domain model and component model of E-learning system and components integration method on the basis of WebService. And we proposed an abstract framework of E-learning which could express the semantic relationship among components and realize high level reusable on the basis of informationized teaching mode. On this foundation, we form an E-learning oriented layering software architecture contain component library layer, application framework layer and application layer. Moreover, the system contains layer division multiplexing and was not built upon developing language and tools. Under the help of the software architecture, we could build characterized E-learning system flexibly like building blocks through framework selection, component assembling and replacement. In addition, we exemplify how to build concrete E-learning system on the basis of this software architecture.

Design decisions and design rationale in software architecture

2009 ◽  
Vol 82 (8) ◽  
pp. 1195-1197 ◽  
Author(s):  
Muhammad Ali Babar ◽  
Patricia Lago
Keyword(s):  
Software Architecture ◽  
Design Rationale ◽  
Design Decisions

scholarly journals Generating Collaborative Systems for Digital Libraries: a Model-Driven Approach

2010 ◽  
Vol 29 (4) ◽  
pp. 171 ◽  
Author(s):  
Alessio Malizia ◽  
Paolo Bottoni ◽  
S. Levialdi
Keyword(s):  
Digital Library ◽  
User Interfaces ◽  
Digital Libraries ◽  
Automatic Generation ◽  
Visual Language ◽  
Domain Experts ◽  
Model Driven ◽  
Neutral Models ◽  
Definition Of ◽  
High Level

The design and development of a digital library involves different stakeholders, such as: information architects, librarians, and domain experts, who need to agree on a common language to describe, discuss, and negotiate the services the library has to offer. To this end, high-level, language-neutral models have to be devised. Metamodeling techniques favor the definition of domainspecific visual languages through which stakeholders can share their views and directly manipulate representations of the domain entities. This paper describes CRADLE (Cooperative-Relational Approach to Digital Library Environments), a metamodel-based framework and visual language for the definition of notions and services related to the development of digital libraries. A collection of tools allows the automatic generation of several services, defined with the CRADLE visual language, and of the graphical user interfaces providing access to them for the final user. The effectiveness of the approach is illustrated by presenting digital libraries generated with CRADLE, while the CRADLE environment has been evaluated by using the cognitive dimensions framework.

High-Level User Interfaces for the DOE ACTS Collection

2007 ◽  
pp. 251-259 ◽  
Author(s):  
L. Anthony Drummond ◽  
Vicente Galiano ◽  
Violeta Migallón ◽  
José Penadés
Keyword(s):  
User Interfaces ◽  
High Level

On Software Architecture Processes and their Use in Practice

2014 ◽  
pp. 198-218
Author(s):  
Perla Velasco-Elizondo ◽  
Humberto Cervantes
Keyword(s):  
Software Architecture ◽  
Level Structure ◽  
Practical Experience ◽  
High Quality ◽  
Software Artifact ◽  
High Level ◽  
Architecture Development

Software architecture is a very important software artifact, as it describes a system’s high-level structure and provides the basis for its development. Software architecture development is not a trivial task; to this end, a number of methods have been proposed to try to systematize their related processes to ensure predictability, repeatability, and high quality. In this chapter, the authors review some of these methods, discuss some specific problems that they believe complicate their adoption, and present one practical experience where the problems are addressed successfully.

Sign in / Sign up

Export Citation Format

Share Document