Interface Design

the University of Amsterdam, May 20-31, 1974.This Tract collects the lecture notes of five of the courses given.The sixth course, given by Dr. R. Kowalski on Predicate Logic as a Programming Language in Artificial Intelligence, is scheduled to appear elsewhere.We are very grateful to the Netherlands Organization for the Advancement of Pure Research (Z.W.O.)

In software development, the user interface(UI) design process involves the part from an imagination that begins on a piece of paper where designers share thoughts to the final prototype that is ready to implement. UI designers use a technique of paper prototyping in low-fidelity sketches to implement the conceptual design. Once a design is drawn, it is usually captured within a photograph, then converted to a high-level mockup, and manually translated into a working client-side code by developers. The process consumes considerable effort and also delays the design process. Recently, researchers attempted to recreate UI from their sketches using code generation techniques. In this paper, we present a system for automatic code generation that combines recent advances in computer vision and deep learning for translating a sketched wireframe into a UI skeleton code. The proposed system has two main components: component recognition and code generation. The component recognition learns to extract visual features and their spatial layouts from sketched UI images. The code generator creates the equivalent UI skeleton codes based on the information from the detection model. A layout algorithm has been developed to resolve the overlapping of components and structure the layout. The evaluation result of the component recognition model indicates that the Faster R-CNN with Inception ResNet v2 backbone model achieved a mean average precision (mAP) of 95.5 %, among the other trained models. To evaluate the generator, we conducted a user study based on visual similarities between input image and the rendered UI.

Interface design and interaction testing is not a completely robust or scientific process. Rather, it is an artful, iterative, social process regulated by inter- or multi-disciplinary design teams. Lamentably, the design trajectory and iterations are often left out or partially communicated in the description of a published design. We offer display design considerations considering AI and propose a modular structure for the interface design and interaction testing process of teams. The key feature of the structure is that it considers display design and display interaction testing and general experimental design and enables teams to transparently communicate how they start, traverse, and end their design cycles. The system can be accessed via an established Industrial Engineering Society on the world wide web. Such a structure would enable studying where innovation and failure happen through iterations of steps taken by different design teams. Subsequently, the information can be used to enrich future research.

In this panel, we propose to figure out how requirements engineering and interaction design can be usefully combined. In particular, some people argue that scenarios/ use cases should be concrete, as in story-telling. Others argue for use of essential use cases as a methodological approach to interaction and user-interface design. Somewhat in the middle, it is argued that use cases should help acquiring the requirements in the first place. What should the practitioner believe and, in particular, do, in order to develop useful and usable software and systems? Software development and interaction design require different skills and different methods and are typically done by different people. Still, scenario-based design is proposed for several activities relevant for both tasks, such as requirements elicitation, software design, and interaction design. Symbolic modeling in this spirit is actually common to various fields. However, scenario-based approaches vary, especially with regard to their use, e.g., employing abstract use cases or integrating scenarios with functions and goals in a systematic design process. So, the key issue to be raised at the panel is how to combine different approaches, e.g., in scenario-based development, so that the interaction design as well as the development of the user interface and of the software internally result in an overall useful and useable system.

Interface design, as a medium of communication between human and computer, transmits information through design semantics and makes the user generate corresponding emotional changes, which affects the user experience. This paper explores the shape semantic and color semantics of the interface design by referring to the product semantics, and by using the theory of Kansei engineering, analyzes the influence of design semantics on the users’ emotional images. Experimental results show that the design semantics affect the user’s emotional image, and the influence of color semantics on the user’s emotional image in the interface design is greater than that of the shape semantics. Therefore, in the interface design process, according to different product positioning, select the appropriate graphic elements and color collocation, can accurately convey the information expressed by the designer, and match the emotions generated by the user.

Applying the technology acceptance model in a study of the factors affecting usage of the Taiwan digital archives system

A REVIEW OF STUDIES ON OPERATOR'S INFORMATION SEARCHING BEHAVIOR FOR HUMAN FACTORS STUDIES IN NPP MCRS

A user interface is a point in the system where a human being interacts with a computer. This chapter discusses several different types of direct interfaces and the interface design process. It introduces some important principles of user interface design. The chapter focuses on certain general principles associated with direct user interface design. The interface can incorporate hardware, software, procedures, and data. Some user interfaces rely on abbreviated commands or acronyms. Command-based interfaces require considerable user training, however, and it is unreasonable to expect users to memorize all the commands without referencing a command template. Object-oriented interfaces, also called icon-based interfaces or graphic user interfaces, have become increasingly common since the introduction of the Apple Macintosh and Microsoft’s Windows operating systems. Expert system interfaces utilize natural language processing. The chapter also discusses strengths, weaknesses, and limitations associated with specific interfaces or interface design techniques.

The present manuscript-based doctoral thesis addresses the question of how approaches to interaction design can be made more structured. This is an attempt to make it more transparent how one can come to a final design of a user interface starting from the results of foundational user research. The results of this analysis can help designers to work very systematic at times, to better reflect on their own idiosyncratic design process “on the job”, or to learn interaction design in the first place. In user-centered design (UCD) there are lifecycles and methods that already provide a certain degree of structuring with the discrimination of different phases etc. But they leave open some gaps here and there. This work is an attempt to close some of the gaps and bring closer together these individual methods. Interaction design patterns are a way to describe solutions to problems in designing user in-terfaces in a very systematic way. However, pattern libraries usually are far from complete. They mostly lack patterns to support the early phases of interaction design and therefore they do usually not link to the abstract models of conceptual design. The third manuscript describes an organizational scheme for interaction design patterns to support the process of implementing a complete pattern language covering all the different levels of the solution domain. The scheme has been found by analyzing several established UCD lifecycles and it has been evaluated by organizing all the individual patterns of several public pattern libraries into it. The first manuscript describes a process of systematically building up a pattern language alongside of a redesign project of a complex application in a corporate environment. The second manuscript describes how patterns have been evaluated in the aforementioned project, when there were several different solutions for one problem. This is shown with two interaction design patterns for the problem of making required input fields visible to users. The fourth manuscript is an attempt to bring together the idea of a complete pattern language, as a description of the solution domain of interaction design, with the different parts of the problem domain. Therefore, the same UCD lifecycles (as in the third manuscript) have been analyzed to find a universal structure of the problem domain. Then all the mappings between the individual parts of the two domains have been described in order to link the two domains in this direct way. Another way of looking at the gap between the problem domain and the solution domain is by seeing it as a distance of levels of abstraction between results of foundational user research and the final user interface. From this point of view a bridging of the gap can be seen in different intermediate representations (abstract models, sketches, and prototypes) and linking them together in a coherent way. These different ways of bridging the gap between foundational user research and the final design of a user interface can be seen as cognitive artifacts to foster problem solving and learning of interaction designers.

Interface and interaction design: How mobile touch devices foster cognitive offloading

A case study in interface design The CHI'89 Information Kiosk

Chapter 8 - Interface Design

The current paper presents the results of the evaluation of a novel human machine interface for supervision and guidance of multiple highly automated unmanned aircraft. Accidents of unmanned aircraft are often related to deficiencies in the design of the human machine interface. Many of these deficiencies are a consequence of insufficient consideration of human factors engineering principles in the early stages of system development. Therefore, in the design of the current human machine interface, empirically validated human factors methods were applied in order to optimally support a remote pilot in supervising and guiding multiple highly automated unmanned aircraft. An information management concept was developed that allows for an increase in the number of UAS that are being supervised without considerably increasing display complexity. In order to evaluate the human machine interface, two within-subj ect simulation studies were conducted. In both studies, pilots were asked to supervise and guide a varying number of UAS in several experimental scenarios using the new human machine interface. Following the experimental scenarios, a structured interview regarding the design of the human machine interface was conducted. The objective of the first study was to gather initial data on the general usability of the interface. The aim of the second simulation study was to investigate how increasing the number of UAS from one up to five affects the time that a pilot needs to acquire and change specific system parameters of any UAS under supervision. Further, the impact of increasing the number of UAS on pilot workload and situation awareness was assessed. The results of the interviews suggest that the design concept of the human machine interface is feasible and easy to understand. The information management concept was described as reasonable and logical. Important information was accessible quickly and (critical) system states could easily be identified. No significant effects of increasing the number of UASs to be supervised on reaction, workload or situation awareness were observed. The findings suggest that the information management concept is reasonable and usable.

At present, the website construction has become one of the necessary works of any industry. However, among hundreds of millions of websites, interface design is very convenient for people to use, and a small number of fast. The reason, including web interface design, web technology adoption, etc. will influence people to visit a website. Among these reasons, the interactive design of website interfaces and become the primary problem of experience that people visit the website. To address this problem, the current website interface and interactive design were discussed in this article, and try to propose improved method of most common small and medium-sized websites.

Event-related potential and oscillatory cortical activities of artistic methodology in information visualization design in human–computer interface