The User Interface Design Process: The Good, the Bad, & we did What we Could in Two Weeks

1994 ◽  
Vol 38 (4) ◽  
pp. 305-309 ◽  
Author(s):  
Marta A. Miller ◽  
Reynold P. Stimart
Keyword(s):  
User Interface ◽  
Software Development ◽  
Human Factors ◽  
Interface Design ◽  
User Interface Design ◽  
Design Processes ◽  
Software Products ◽  
Usability Tests ◽  
Development Cycle ◽  
Speed Accuracy

Conventional wisdom inside human factors circles says that the integration of user interface design processes into the software development cycle is the best way to improve the usability of software products. While there is no problem convincing human factors practitioners of this, frequently there is still a need to demonstrate the effectiveness of user interface processes to product development teams and management. Mayhew (1992) suggests that it is not enough to be able to apply human factors knowledge. Successful user interface design must include buy-in from outside of the user interface organization. To demonstrate the effectiveness of a user interface design program, data from usability tests on three versions of a product were analyzed. The oldest version of the product was developed without the inclusion of any user interface design processes. The second version of the product had minimal involvement of user interface practitioners late in the development cycle. The newest version of the product was developed with the user interface design processes fully integrated into the software development cycle. The data indicate that user interface design processes do impact usability, as measured by speed, accuracy, and subjective measures. Furthermore, user interface processes which are part of the software development cycle, as opposed to just a side effort by user interface practitioners, seem to have a much greater impact on usability.

Human Factors Problems in Interactive Voice Response (IVR) Applications: Do we Need a Guideline/Standard?

1992 ◽  
Vol 36 (3) ◽  
pp. 222-226 ◽  
Author(s):  
Daryle Jean Gardner-Bonneau
Keyword(s):  
User Interface ◽  
Human Factors ◽  
Interface Design ◽  
Interactive Voice Response ◽  
User Interface Design ◽  
Application Development ◽  
Design Guideline ◽  
Dialogue Design ◽  
Specification Document ◽  
Voice Response

The purpose of this paper is to present a case for the development of a user interface design guideline or standard for interactive voice response applications, to be widely disseminated throughout business and industry. A number of sample problems are cited, based on the author's consulting experience in this area, which serve to demonstrate that many of the problems encountered in IVR application development, particularly in scripting/dialogue design and use of automated speech recognition as a front-end, are not only solvable, but easily avoidable, given the current human factors knowledge base. The paper also discusses the Specification Document developed by the Voice Messaging User Interface Forum (1990, April), and the reasons why it cannot be applied, as written, to the user interface design of more complex IVR applications. Finally, the author proposes an approach to developing the proposed guideline/standard.

Localized User Interface for Improving Cell Phone Users' Device Competency

2010 ◽  
pp. 129-143 ◽  
Author(s):  
D. Krisnawati Lucia ◽  
Restyandito
Keyword(s):  
User Interface ◽  
Interface Design ◽  
Cell Phone ◽  
Procedural Knowledge ◽  
User Interface Design ◽  
Rote Learning ◽  
Usability Tests ◽  
Factors Influencing ◽  
Design Culture ◽  
A Cell

This study tried to examine how cell phone users who undergo a technology leap acquire their procedural knowledge of operating a cell phone and to find out which factors can improve their device competency. Using interviews, usability tests, and a questionnaire, this study found out that many respondents use unstructured means such as asking other cell phone users or rote learning in gaining their procedural knowledge. Some factors influencing users’ device competencies that were found in this study are classified into three categories: user interface design, culture, and the users themselves. In order to improve users’ device competency, elements in those three categories must be integrated. One realization of such integration is the attempt of localizing user interface through the user’s culture, not the culture where the cell phone is designed and manufactured.

Contracting for User Interface Design in Military Systems

1989 ◽  
Vol 33 (10) ◽  
pp. 593-593
Author(s):  
Jane N. Mosier ◽  
Mildred D. Jarvis ◽  
Donald L. Monk ◽  
Larry H. O'Brien ◽  
Robert Simon
Keyword(s):  
User Interface ◽  
Human Factors ◽  
Interface Design ◽  
User Interface Design ◽  
Computer Hardware ◽  
Design Issues ◽  
Acquisition Process ◽  
Military Systems ◽  
The Government

Many of the systems the Government acquires contain a large amount of software. Some are limited almost exclusively to off-the-shelf computer hardware, and software that is developed by a contractor. But human factors in military systems is regulated by documented standards and procedures that were developed before software gained an important role in military systems, and so do not deal with issues specific to user interface design. The purpose of this panel is to discuss user interface design issues and to propose changes to the acquisition process to improve user interface design for military systems.

Guidelines for the Use of a Prototype in User Interface Design

1988 ◽  
Vol 32 (5) ◽  
pp. 370-374 ◽  
Author(s):  
Lovie A. Melkus ◽  
Robert J. Torres
Keyword(s):  
User Interface ◽  
Interface Design ◽  
Design Methodology ◽  
Development Process ◽  
User Interface Design ◽  
Software Application ◽  
Development Cycle

Although the use of a prototype of the user interface of a software application early in the development cycle is a valuable tool in the design of a usable user interface, prototyping can be difficult to introduce into the development process. Furthermore, designers without experience in using a prototype can run into problems which counteract the value of this user interface design methodology. Designers with experience in a substantial prototyping effort have formulated guidelines for the use of prototyping which can help to minimize these problems.

Computers and Telecommunications in the Year 2000-Multi-Modal Interfaces, Miniaturisation, and Portability

1996 ◽  
Vol 40 (6) ◽  
pp. 353-356 ◽  
Author(s):  
Leah S. Kaufman ◽  
Jim Stewart ◽  
Bruce Thomas ◽  
Gerhard Deffner
Keyword(s):  
User Interface ◽  
Human Factors ◽  
Interface Design ◽  
User Interface Design ◽  
Position Paper ◽  
Advantages And Disadvantages ◽  
Multimodal Communications ◽  
Year 2000

In this, the second of three sets of position papers for the CTG-CSTG co-sponsored symposium on Computers and Telecommunications in the Year 2000, we begin with a paper by Leah Kaufman and Jim Stewart on the human factors challenges involved in creating an effective multimodal communications environment. Bruce Thomas continues with a position paper outlining the advantages and disadvantages of technology miniaturisation, and how these advantages and disadvantages impact our approaches to user interface design. In the final paper in this set, Gerhard Deffner describes the portability-functionality dilemma, in which designers are confronted with two distinct user goals that are difficult to meet simultaneously.

Evaluasi Usability Website library.umn.ac.id Universitas Multimedia Nusantara

2018 ◽  
Vol 8 (2) ◽  
pp. 87-94
Author(s):  
Melanesia N.W. Rumbiak ◽  
Johan Setiawan
Keyword(s):  
User Interface ◽  
User Interfaces ◽  
Interface Design ◽  
User Interface Design ◽  
Usability Evaluation ◽  
Testing System ◽  
Usability Tests ◽  
System Usability Scale ◽  
System Usability ◽  
Interface Usability

Abstract – The library.umn.ac.id is the library website which is owned by the Universitas Multimedia Nusantara. The website has never been examined with usability especially its user interfaces. In conducting the evaluation, the methods of usability tests are applied that is users’ observations of the website user interface design continued by collecting and analyzing data. In addition, data is collecting by creating a questionnaire which is based on System Usability Scale (SUS) to measure users’ satisfaction when using the system. The data is analyzed by applying usability test that refers to the theory of Jacob Nielsen (2003) which is composed of five components that are learnability, efficiency, memorability, errors, and satisfaction. The results of this research, some new user interfaces are recommended for enhancing the library website that has been fully the old version. As a result, the user interfaces prototype is easy to use and easy to understand based on the students’ responses compared to the old version. Keywords-Usability Evaluation, User Interface, Usability Testing, System Usability Scale

Growing a Styleguide: Macroergonomic Strategies for Achieving Consistent User Interface Design

1993 ◽  
Vol 37 (12) ◽  
pp. 882-885 ◽  
Author(s):  
Robert W. Root
Keyword(s):  
User Interface ◽  
Software Development ◽  
Interface Design ◽  
Organizational Structures ◽  
User Interface Design ◽  
Design Guidelines ◽  
Design Criteria ◽  
Organizational Strategies ◽  
Development Organization ◽  
Large Software

Consistency in user interface design is generally recognized as a desirable goal. The main problem facing most practitioners is how to achieve it. In many cases the solution begins with a user interface styleguide that defines the design criteria for user interface developers. A styleguide is a necessary, but not sufficient, part of the solution. In practice, achieving consistency requires a multi-faceted approach ranging from design guidelines to organizational structures and processes. This paper discusses macroergonomic aspects of styleguide development in a large software development organization, focusing on the processes and organizational strategies used to develop content and achieve initial buyin by user interface designers and developers.

Sign in / Sign up

Export Citation Format

Share Document