Designing User Interfaces: A Classroom Experience in Iterative Software Design

1986 ◽  
Vol 30 (14) ◽  
pp. 1366-1370
Author(s):  
Susan C. Hoffman

A program was developed to expose undergraduate Computer Technology students to methods for designing and evaluating user dialogue in interactive software. The class was given an assignment to develop an Interactive program for use by the general public. This was given prior to any experience using concepts in Human Factors, a Standard Development Process, or general guidelines for evaluating the user interface. Task analysis was performed extracting data from video tapes. Formal lecture material on designing user interfaces incorporating good Human Factors was then introduced. Students then were given the opportunity to modify their programs and assess the value of these changes through retesting. Substantial improvements in both transaction performance times and accuracy occurred during the evaluation of the revised applications. This program was an effective method for demonstrating the complexities involved in designing and implementing interactive software.

Author(s):  
Merissa Walkenstein ◽  
Ronda Eisenberg

This paper describes an experimental study that compares a graphical user interface for a computer-telephony product designed without the involvement of a human factors engineer to a redesign of that interface designed with a human factors engineer late in the development cycle. Both interfaces were usability tested with target customers. Results from a number of measures, both subjective and objective, indicate that the interface designed with the human factors engineer was easier to use than the interface designed without the human factors engineer. The results of this study show the benefits of involving human factors engineers in the design of graphical user interfaces even towards the end of a development cycle. However, this involvement is most effective when human factors engineers are included as an integral part of the design and development process even at this late stage in the process.


Author(s):  
Dalene M. Shin

The focus of this paper is the utility and application of a Human System Interface (HSI) Style Guide. There are a number of reasons for the routine adaptation of a tool such as a style guide. First, consistent application of human factors guidelines, methods and principles is ensured in the design of Graphical User Interfaces (GUIs). Secondly, a style guide is a mechanism for integrating human factors early into the development of any system or process. A HSI style guide is also an explicit resource for designers responsible for user interface, standards and principles. Moreover, serving as a reference manual, a style guide positively impacts user interface design as well as implementation decisions and accompanying rationale. Finally, through the descriptive content and structure, the style guide communicates human factors processes thus allowing for full integration with all associated disciplines in design processes. Consequently, all those involved (designers, implementers, managers and reviewers or evaluators) in the GUI design and development process benefit from style guide application.


Author(s):  
Qian Li

Human factors has provided many applicable theories and techniques to analyze user requirements, design user interfaces, and conduct evaluation of usability in software development. However, it is common that contributions made by human factors practitioners are not incorporated in this development process, which impairs the ability of human factors practitioners to have significant impact in cross-functional teams. This paper reviews the possible reasons that human factors efforts are frequently ignored in software design and development and proposes a conceptual framework for the integration of the methods and tools from both the user-centered design approach and the use case driven process to take advantages of the merit and recent progress in both human factors and object-oriented technology.


2019 ◽  
Author(s):  
Yvonne J G Korpershoek ◽  
Sander Hermsen ◽  
Lisette Schoonhoven ◽  
Marieke J Schuurmans ◽  
Jaap C A Trappenburg

BACKGROUND Adequate self-management skills are of great importance for patients with chronic obstructive pulmonary disease (COPD) to reduce the impact of COPD exacerbations. Using mobile health (mHealth) to support exacerbation-related self-management could be promising in engaging patients in their own health and changing health behaviors. However, there is limited knowledge on how to design mHealth interventions that are effective, meet the needs of end users, and are perceived as useful. By following an iterative user-centered design (UCD) process, an evidence-driven and usable mHealth intervention was developed to enhance exacerbation-related self-management in patients with COPD. OBJECTIVE This study aimed to describe in detail the full UCD and development process of an evidence-driven and usable mHealth intervention to enhance exacerbation-related self-management in patients with COPD. METHODS The UCD process consisted of four iterative phases: (1) background analysis and design conceptualization, (2) alpha usability testing, (3) iterative software development, and (4) field usability testing. Patients with COPD, health care providers, COPD experts, designers, software developers, and a behavioral scientist were involved throughout the design and development process. The intervention was developed using the behavior change wheel (BCW), a theoretically based approach for designing behavior change interventions, and logic modeling was used to map out the potential working mechanism of the intervention. Furthermore, the principles of design thinking were used for the creative design of the intervention. Qualitative and quantitative research methods were used throughout the design and development process. RESULTS The background analysis and design conceptualization phase resulted in final guiding principles for the intervention, a logic model to underpin the working mechanism of the intervention, and design requirements. Usability requirements were obtained from the usability testing phases. The iterative software development resulted in an evidence-driven and usable mHealth intervention—Copilot, a mobile app consisting of a symptom-monitoring module, and a personalized COPD action plan. CONCLUSIONS By following a UCD process, an mHealth intervention was developed that meets the needs and preferences of patients with COPD, is likely to be used by patients with COPD, and has a high potential to be effective in reducing exacerbation impact. This extensive report of the intervention development process contributes to more transparency in the development of complex interventions in health care and can be used by researchers and designers as guidance for the development of future mHealth interventions.


Author(s):  
Geerten van de Kaa

This chapter discusses the notion of “responsible innovation” and “value sensitive design”. It applies these notions to standardization and more specifically to standard selection. Based on earlier research (Van de Kaa, 2013; Van den Ende, Van de Kaa, Den Uyl, & De Vries, 2012), it is proposed that standards should be flexible to facilitate changes related to ethical and societal values. An acceptable standard can be achieved by involving users in the standard development process. The understanding of standardization and standard selection in particular can be improved by incorporating concepts and theories from the discipline of philosophy. This chapter discusses three conceptualizations of standard selection: market dominance, socio-political acceptance, and acceptability.


Author(s):  
Marco Kuhrmann ◽  
Georg Kalus ◽  
Gerhard Chroust

Software development projects are complex. The more complex a project is, the higher are the requirements related to the software development process. The implementation of a process is a great challenge. This, in part, has to do with human factors (acceptance, etc.) as the benefits of a formal development process might not be obvious immediately and it may take a while until the process becomes the lifeblood of a team. A crucial step towards implementing, enacting and enforcing a process is to provide tool support for the many activities the process asks for. Tool support is necessary to guarantee efficiency in the project, to do the housekeeping and to minimize the “overhead” of the process. This chapter describes challenges and options for supporting process models by tools. Furthermore it describes concrete samples and shows how tool chains can be created with commercial tools as well as with open source tools.


Author(s):  
Maria Lund Jensen ◽  
Jayme Coates

Development of implantable medical devices is becoming increasingly interesting for manufacturers, but identifying the right Human Factors Engineering (HFE) approach to ensure safe use and effectiveness is challenging. Most active implantable devices are highly complex; they are built on extremely advanced, compact technology, often comprise systems of several device elements and accessories, and they span various types of user interfaces which must facilitate diverse interaction performed by several different user groups throughout the lifetime of the device. Furthermore, since treatment with implantable devices is often vital and by definition involves surgical procedures, potential risks related to use error can be severe. A systematic mapping of Product System Elements and Life Cycle Stages can help early identification of Use Cases, and for example user groups and high-level use risks, to be accounted for via HFE throughout development to optimize Human Factors processes and patient outcomes. This paper presents a concrete matrix tool which can facilitate an early systematic approach to planning and frontloading of Human Factors Engineering activities in complex medical device development.


1981 ◽  
Vol 25 (1) ◽  
pp. 119-121
Author(s):  
Jon G. Rogers

A display systems development logic is described which has proved useful as a communication aid in assuring human factors input in the development process. The logic in the form of a flow chart begins with an examination of the system mission objective and works the display problem to the final configuration. The procedure is thorough, systematic and assures attention to basic human factors data and standards.


Sign in / Sign up

Export Citation Format

Share Document