DOCSLIB.ORG

User Interface Design

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
User Interface Design P1: FYX PE040-FM PE040/Lauesen October 13, 2007 10:52 Char Count= 0 User Interface Design A Software Engineering Perspective Soren Lauesen Harlow, England • London • New York • Boston • San Francisco • Toronto Sydney • Tokyo • Singapore • Hong Kong • Seoul • Taipei • New Delhi Cape Town • Madrid • Mexico City • Amsterdam • Munich • Paris • Milan iii P1: FYX PE040-FM PE040/Lauesen October 13, 2007 10:52 Char Count= 0 Contents Preface...................................................................ix 3.6 Text form versus analog form......................94 3.6.1 Automatic and controlled activities.......................94 Part A Best of the classics 3.6.2 Multi-sensory association......................................96 3.7 Overview of complex data............................ 99 1 Usability.........................................3 1.1 User interface..........................................................4 4 Mental models and interface 1.2 Usability factors.....................................................9 design.........................................105 1.3 Usability problems.............................................12 4.1 Hidden data and mental models.............106 1.4 Basics of usability testing..............................15 4.1.1 Example: page format..........................................106 1.5 Heuristic evaluation and 4.1.2 Example: on-line ordering system......................108 user reviews...........................................................19 4.2 Models for data, functions 1.6 Usability measurements and and domain..........................................................111 requirements......................................................... 22 4.3 Dialogue levels and virtual window 1.6.1 Task time (performance measurement)................22 method...................................................................114 1.6.2 Choosing the numbers.......................................... 25 4.4 Data and system functions 1.6.3 Problem counts.......................................................26 1.6.4 Keystroke counts....................................................29 in practice.............................................................117 1.6.5 Opinion poll..............................................................32 4.5 Bad screens – database extreme...........121 1.6.6 Score for understanding........................................34 4.6 Bad screens – step-by-step 1.6.7 Guideline adherence...............................................36 1.6.8 Which usability measure extreme..................................................................124 to choose?...............................................................38 4.7 More on mental models............................... 127 2 Prototyping and iterative Part B Systematic interface design...........................................41 design 2.1 Usability in the development process...................................... 42 5 Analysis, visions and domain 2.2 Case study: a hotel system..........................46 description.................................133 2.3 The first hotel system prototype................50 5.1 Visions for the hotel system.......................135 5.1.1 Business goals......................................................135 2.4 Different kinds of prototypes....................... 58 5.1.2 Large-scale solution.............................................136 2.4.1 Prototypes of user interfaces 58 ................................ 5.1.3 Requirements........................................................136 2.4.2 Contents of a mock-up..........................................61 2.4.3 Lots of screens – accelerator 5.2 Data model and data description...........139 effect.........................................................................62 5.3 Task descriptions............................................. 142 2.5 Does usability pay?...........................................64 5.3.1 Annotated task list................................................142 5.3.2 Task description template................................... 143 5.3.3 Task & Support approach 149 3 Data presentation.......................67 ................................... 5.4 Work area and user profile..........................152 3.1 Gestalt laws...........................................................68 5.5 Good, bad and vague tasks...................... 154 3.2 Screen gestalts....................................................71 3.2.1 Line gestalts?..........................................................71 5.6 Scenarios and use cases............................ 161 3.2.2 Proximity and closure.............................................71 3.3 Text gestalts...........................................................74 6 Virtual windows design............167 3.4 Contrast................................................................... 80 6.1 Plan the virtual windows..............................168 3.5 Presentation formats........................................85 6.2 Virtual windows, graphical version........176 vi Contents P1: FYX PE040-FM PE040/Lauesen October 13, 2007 10:52 Char Count= 0 6.3 Virtual windows in development............. 182 10.4 Virtual windows for course rating...........324 6.4 Checking against task descriptions......187 10.5 Function design................................................ 335 6.5 CREDO check....................................................190 10.6 Prototype and usability test.......................340 6.6 Review and understandability test.........198 6.7 Searching..............................................................202 11 Designing an e-mail system... 343 6.8 Virtual windows and alternative 11.1 Visions for an e-mail system..................... 344 11.1.1 The large-scale solution.......................................345 designs...................................................................208 11.1.2 Requirements........................................................353 11.2 Task descriptions for e-mail.......................355 7 Function design 217 ........................ 11.3 Data model for e-mail....................................360 7.1 Semantic functions and searching........ 218 11.4 Virtual windows for e-mail.......................... 365 7.2 Actions and feedback (use cases).........229 11.5 Function design and prototype................372 7.3 Undo – to do or not to do........................... 231 7.3.1 Undo strategy for the user interface.................. 236 7.3.2 How to implement undo......................................239 12 User documentation and 7.4 From virtual windows to screens............243 support.......................................381 7.5 Single-page dialogue.....................................248 12.1 Support situations...........................................382 7.6 Multi-page dialogue........................................253 12.2 Types of support...............................................385 7.7 More about state diagrams........................257 12.3 Support plan for the hotel system..........392 7.8 Function presentation....................................260 12.4 Support card.......................................................394 7.9 Error messages and inactive 12.5 Reference manual............................................399 12.5.1 System-related lookup.........................................399 functions................................................................268 12.5.2 Task-related lookup..............................................403 12.5.3 Structure of reference manual............................ 405 8 Prototypes and defect 12.5.4 Browsing and language.......................................410 correction...................................273 8.1 The systematic prototype........................... 274 13 More on usability testing.........413 8.2 Programming and testing the system..279 13.1 Common misunderstandings....................414 8.3 Defects and their cure...................................284 13.2 Planning the test...............................................416 8.4 Problems, causes and solutions.............290 13.3 Finding test users............................................ 425 13.4 How many users?............................................427 9 Reflections on user interface 13.5 Which test tasks?............................................ 431 design.........................................293 13.6 Carry out the test............................................. 435 9.1 Overview of the virtual window 13.7 Test report and analysis............................... 438 method...................................................................294 9.2 Data design versus function design......297 14 Heuristic evaluation..................443 9.2.1 A task-oriented design method..........................298 14.1 Variants of heuristic evaluation................444 9.2.2 Object-oriented design........................................300 14.2 Heuristic rules and guidelines...................447 9.2.3 Virtual windows and objects...............................302 14.3 Cost comparison..............................................452 9.3 History of the virtual window method..305 14.4 Effect comparison (CUE-4).........................454 Part C Supplementary design 15 Systems development 465 issues ............. 15.1 The waterfall model........................................ 466 10 Web-based course rating....... 309 15.2 Iterative development....................................470 10.1 Visions for the rating system.....................310
Load more

Recommended publications
  • User Interface Design Issues in HCI
    IJCSNS International Journal of Computer Science and Network Security, VOL.18 No.8, August 2018 153 User Interface Design Issues In HCI Waleed Iftikhar, Muhammad Sheraz Arshad Malik, Shanza Tariq, Maha Anwar, Jawad Ahmad, M. Saad sultan Department of Computing, Riphah International University, Faisalabad, Pakistan Summary Command line is the interface that allows the user to This paper presents an important analysis on a literature review interact with the computer by directly using the commands. which has the findings in design issues from the year 1999 to But there is an issue that the commands cannot be changed, 2018. This study basically discusses about all the issues related they are fixed and computer only understands the exact to design and user interface, and also gives the solutions to make commands. the designs or user interface more attractive and understandable. This study is the guideline to solve the main issues of user Graphical user interface is the interface that allows the interface. user to interact with the system, because this is user There is important to secure the system for modern applications. friendly and easy to use. This includes the graphics, The use of internet is quickly growing from years. Because of pictures and also attractive for all type of users. The this fast travelling lifestyle, where they lets the user to attach with command line is black and white interface. This interface systems from everywhere. When user is ignoring the is also known as WIMPS because it uses windows, icons, functionalities in the system then the system is not secure but, in menus, pointers.
    [Show full text]
  • Software User Guide
    Software User Guide • For the safe use of your camera, be sure to read the “Safety Precautions” thoroughly before use. • Types of software installed on your computer varies depending on the method of installation from the Caplio Software CD-ROM. For details, see the “Camera User Guide”. Using These Manuals How to Use the The two manuals included are for your Caplio Software User Guide 500SE. Display examples: 1. Understanding How to Use Your The LCD Monitor Display examples may be Camera different from actual display screens. “Camera User Guide” (Printed manual) Terms: This guide explains the usage and functions In this guide, still images, movies, and sounds of the camera. You will also see how to install are all referred to as “images” or “files”. the provided software on your computer. Symbols: This guide uses the following symbols and conventions: Caution Caution This indicates important notices and restrictions for using this camera. 2. Downloading Images to Your Computer “Software User Guide” Note *This manual (this file) This indicates supplementary explanations and useful This guide explains how to download images tips about camera operations. from the camera to your computer using the provided software. Refer to This indicates page(s) relevant to a particular function. “P. xx” is used to refer you to pages in this manual. Term 3. Displaying Images on Your This indicates terms that are useful for understanding Computer the explanations. The provided software “ImageMixer” allows you to display and edit images on your computer. For details on how to use ImageMixer, click the [?] button on the ImageMixer window and see the displayed manual.
    [Show full text]
  • Designing for Increased Autonomy & Human Control
    IFIP Workshop on Intelligent Vehicle Dependability and Security (IVDS) January 29, 2021 Designing for Increased Autonomy & Human Control Ben Shneiderman @benbendc Founding Director (1983-2000), Human-Computer Interaction Lab Professor, Department of Computer Science Member, National Academy of Engineering Photo: BK Adams IFIP Workshop on Intelligent Vehicle Dependability and Security (IVDS) January 29, 2021 Designing for Increased Automation & Human Control Ben Shneiderman @benbendc Founding Director (1983-2000), Human-Computer Interaction Lab Professor, Department of Computer Science Member, National Academy of Engineering Photo: BK Adams What is Human-Centered AI? Human-Centered AI Amplify, Augment, Enhance & Empower People Human Responsibility Supertools and Active Appliances Visual Interfaces to Prevent/Reduce Explanations Audit Trails to Analyze Failures & Near Misses Independent Oversight à Reliable, Safe & Trustworthy Supertools Digital Camera Controls Navigation Choices Texting Autocompletion Spelling correction Active Appliances Coffee maker, Rice cooker, Blender Dishwasher, Clothes Washer/Dryer Implanted Cardiac Pacemakers NASA Mars Rovers are Tele-Operated DaVinci Tele-Operated Surgery “Robots don’t perform surgery. Your surgeon performs surgery with da Vinci by using instruments that he or she guides via a console.” https://www.davincisurgery.com/ Bloomberg Terminal A 2-D HCAI Framework Designing the User Interface Balancing automation & human control First Edition: 1986 Designing the User Interface Balancing automation &
    [Show full text]
  • End-User Computing Security Guidelines Previous Screen Ron Hale Payoff Providing Effective Security in an End-User Computing Environment Is a Challenge
    86-10-10 End-User Computing Security Guidelines Previous screen Ron Hale Payoff Providing effective security in an end-user computing environment is a challenge. First, what is meant by security must be defined, and then the services that are required to meet management's expectations concerning security must be established. This article examines security within the context of an architecture based on quality. Problems Addressed This article examines security within the context of an architecture based on quality. To achieve quality, the elements of continuity, confidentiality, and integrity need to be provided. Confidentiality as it relates to quality can be defined as access control. It includes an authorization process, authentication of users, a management capability, and auditability. This last element, auditability, extends beyond a traditional definition of the term to encompass the ability of management to detect unusual or unauthorized circumstances and actions and to trace events in an historical fashion. Integrity, another element of quality, involves the usual components of validity and accuracy but also includes individual accountability. All information system security implementations need to achieve these components of quality in some fashion. In distributed and end-user computing environments, however, they may be difficult to implement. The Current Security Environment As end-user computing systems have advanced, many of the security and management issues have been addressed. A central administration capability and an effective level of access authorization and authentication generally exist for current systems that are connected to networks. In prior architectures, the network was only a transport mechanism. In many of the systems that are being designed and implemented today, however, the network is the system and provides many of the security services that had been available on the mainframe.
    [Show full text]
  • Software Quality Management
    Software Quality Management 2004-2005 Marco Scotto ([email protected]) Software Quality Management Contents ¾Definitions ¾Quality of the software product ¾Special features of software ¾ Early software quality models •Boehm model • McCall model ¾ Standard ISO 9126 Software Quality Management 2 Definitions ¾ Software: intellectual product consisting of information stored on a storage device (ISO/DIS 9000: 2000) • Software may occur as concepts, transactions, procedures. One example of software is a computer program • Software is "intellectual creation comprising the programs, procedures, rules and any associated documentation pertaining to the operation of a data processing system" •A software product is the "complete set of computer programs, procedures and associated documentation and data designated for delivery to a user" [ISO 9000-3] • Software is independent of the medium on which it is recorded Software Quality Management 3 Quality of the software product ¾The product should, on the highest level… • Ensure the satisfaction of the user needs • Ensure its proper use ¾ Earlier: 1 developer, 1 user • The program should run and produce results similar to those expected ¾ Later: more developers, more users • Need to economical use of the storage devices • Understandability, portability • User-friendliness, learnability ¾ Nowadays: • Efficiency, reliability, no errors, able to restart without using data Software Quality Management 4 Special features of software (1/6) ¾ Why is software ”different”? • Does not really have “physical” existence
    [Show full text]
  • Exploring the User Interface Affordances of File Sharing
    CHI 2006 Proceedings • Activity: Design Implications April 22-27, 2006 • Montréal, Québec, Canada Share and Share Alike: Exploring the User Interface Affordances of File Sharing Stephen Voida1, W. Keith Edwards1, Mark W. Newman2, Rebecca E. Grinter1, Nicolas Ducheneaut2 1GVU Center, College of Computing 2Palo Alto Research Center Georgia Institute of Technology 3333 Coyote Hill Road 85 5th Street NW, Atlanta, GA 30332–0760, USA Palo Alto, CA 94304, USA {svoida, keith, beki}@cc.gatech.edu {mnewman, nicolas}@parc.com ABSTRACT and folders shared with other users on a single computer, With the rapid growth of personal computer networks and often as a default system behavior; files shared with other the Internet, sharing files has become a central activity in computers over an intranet or home network; and files computer use. The ways in which users control the what, shared with other users around the world on web sites and how, and with whom of sharing are dictated by the tools FTP servers. Users also commonly exchange copies of they use for sharing; there are a wide range of sharing documents as email attachments, transfer files during practices, and hence a wide range of tools to support these instant messaging sessions, post digital photos to online practices. In practice, users’ requirements for certain photo album services, and swap music files using peer–to– sharing features may dictate their choice of tool, even peer file sharing applications. though the other affordances available through that tool Despite these numerous venues for and implementations of may not be an ideal match to the desired manner of sharing.
    [Show full text]
  • User Interaction Design for Secure Systems
    User Interaction Design for Secure Systems Ka-Ping Yee Report No. UCB/CSD-02-1184 May 2002 Computer Science Division (EECS) University of California Berkeley, California 94720 Supported by NSF award #EIA-0122599 ITR/SI: Societal Scale Information Systems: Technologies, Design and Applications User Interaction Design for Secure Systems Ka-Ping Yee [email protected] Computer Science Department University of California, Berkeley Abstract Perhaps the most spectacular class of recent security problems is the e-mail virus, which is a good real-life The security of any computer system that is configured example of a security violation in the absence of software and operated by human beings critically depends on the errors. At no point in the propagation of the virus does information conveyed by the user interface, the decisions any application or system software do anything other of the computer users, and the interpretation of their than exactly what its programmers would expect: the e- actions. We establish some starting points for reasoning mail client correctly displays the message and correctly about security from a user-centred point of view, by decodes the attached virus program; the system correctly modelling a system in terms of actors and actions and executes the virus program. Rather, the problem has introducing the concept of the subjective actor-ability occurred because the expectations of the programmer state. We identify ten key principles for user interaction became inconsistent with what the user would want. design in secure systems and give case studies to Our purpose here is to present a way of thinking about illustrate and justify each principle, describing real-world this type of issue.
    [Show full text]
  • User Interface for Volume Rendering in Virtual Reality Environments
    User Interface for Volume Rendering in Virtual Reality Environments Jonathan Klein∗ Dennis Reuling† Jan Grimm‡ Andreas Pfau§ Damien Lefloch¶ Martin Lambersk Andreas Kolb∗∗ Computer Graphics Group University of Siegen ABSTRACT the gradient or the curvature at the voxel location into account and Volume Rendering applications require sophisticated user interac- require even more complex user interfaces. tion for the definition and refinement of transfer functions. Tradi- Since Virtual Environments are especially well suited to explore tional 2D desktop user interface elements have been developed to spatial properties of complex 3D data, bringing Volume Render- solve this task, but such concepts do not map well to the interaction ing applications into such environments is a natural step. However, devices available in Virtual Reality environments. defining new user interfaces suitable both for the Virtual Environ- ment and for the Volume Rendering application is difficult. Pre- In this paper, we propose an intuitive user interface for Volume vious approaches mainly focused on porting traditional 2D point- Rendering specifically designed for Virtual Reality environments. and-click concepts to the Virtual Environment [8, 5, 9]. This tends The proposed interface allows transfer function design and refine- to be unintuitive, to complicate the interaction, and to make only ment based on intuitive two-handed operation of Wand-like con- limited use of available interaction devices. trollers. Additional interaction modes such as navigation and clip In this paper, we propose an intuitive 3D user interface for Vol- plane manipulation are supported as well. ume Rendering based on interaction devices that are suitable for The system is implemented using the Sony PlayStation Move Virtual Reality environments.
    [Show full text]
  • Effective User Interface Design for Consumer Trust Two Case Studies
    2005:097 SHU MASTER'S THESIS Effective User Interface Design for Consumer Trust Two Case Studies XILING ZHOU XIANGCHUN LIU Luleå University of Technology MSc Programme in Electronic Commerce Department of Business Administration and Social Sciences Division of Industrial marketing and e-commerce 2005:097 SHU - ISSN: 1404-5508 - ISRN: LTU-SHU-EX--05/097--SE Luleå University of Technology E-Commerce ACKNOWLEDGEMENT This thesis is the result of half a year of work whereby we have been accompanied and supported by many people. It is a pleasant aspect that we could have this opportunity to express our gratitude to all of them. First, we are deeply indebted to our supervisor Prof. Lennart Persson who is from Division of Industrial Marketing at LTU. He helped us with stimulating suggestions and encouragement in all the time of research and writing of this thesis. Without his never-ending support during this process, we could not have done this thesis. Especially, we would like to express our gratitude to all of participants, who have spent their valuable time to response the interview questions and discuss with us. Finally, we would like to thank our family and friends. I, Zhou Xiling am very grateful for everyone who gave me support and encouragement during this process. Especially I felt a deep sense of gratitude to my father and mother who formed part of my vision and taught me the good things that really matter in the life. I also want to thank my friend Tang Yu for his never-ending support and good advices. I, Liu XiangChun am very grateful for my parents, for their endless love and support.
    [Show full text]
  • Student Computer User Agreement
    STUDENT COMPUTER USER AGREEMENT GUIDING PRINCIPLE OF THIS AGREEMENT: Lakeside’s technological resources are dedicated to further the school’s mission and to serve the educational pursuits of its students. Students using Lakeside’s technology services are expected to behave in accordance with the Community Expectations documented in the family handbook. Students are expected to act in ways that show consideration and respect for other people and enhance an open atmosphere of trust, both offline and online. TECHNOLOGY SERVICES The use of Lakeside’s technology services – tech support, network access, email accounts, storage services, software subscriptions and all other school-owned computer resources – is a privilege, not a right. This privilege may be revoked at any time for abusive conduct, or failure to abide by the school’s expectations and/or responsible usage listed below. GENERAL EXPECTATIONS ▪ Lakeside email accounts, software and services, and onsite network access are provided primarily for school-related work. ▪ Any user of Lakeside’s electronic communications resources is expected to respect the person and privacy of others. ▪ The configuration of school-issued computers (operating system, security settings and software applications) may not be altered. ▪ Using the Lakeside computer network to exchange or store pirated software, unlawful information, or other unauthorized copyright-protected material (i.e. music, multimedia) in any file format is strictly prohibited. ▪ Students are expected to maintain the integrity of their computing devices so as not to bring viruses, malware or spyware to school. Unprotected and infected devices are forbidden to connect to the school network and, when detected, will be disconnected from the network until resolved.
    [Show full text]
  • Quality-Based Software Reuse
    Quality-Based Software Reuse Julio Cesar Sampaio do Prado Leite1, Yijun Yu2, Lin Liu3, Eric S. K. Yu2, John Mylopoulos2 1Departmento de Informatica, Pontif´ıcia Universidade Catolica´ do Rio de Janeiro, RJ 22453-900, Brasil 2Department of Computer Science, University of Toronto, M5S 3E4 Canada 3School of Software, Tsinghua University, Beijing, 100084, China Abstract. Work in software reuse focuses on reusing artifacts. In this context, finding a reusable artifact is driven by a desired functionality. This paper proposes a change to this common view. We argue that it is possible and necessary to also look at reuse from a non-functional (quality) perspective. Combining ideas from reuse, from goal-oriented requirements, from aspect-oriented programming and quality management, we obtain a goal-driven process to enable the quality-based reusability. 1 Introduction Software reuse has been a lofty goal for Software Engineering (SE) research and prac- tice, as a means to reduced development costs1 and improved quality. The past decade has seen considerable progress in fulfilling this goal, both with respect to research ideas and industrial practices (e.g., [1–3]). Current reuse techniques focus on the reuse of software artifacts on the basis of de- sired functionality. However, non-functional properties (qualities) of a software system are also crucial. Systems fail because of inadequate performance, security, reliability, usability, or precision, to name a few. Quality concerns, therefore, should also be front and centre in methods for software reuse. For example, in designing for the NASA Mars Spirit spacecraft, one would not adopt a “cosine” function from an arbitrary mathemat- ical library.
    [Show full text]
  • The Management of End User Computing a Research Perspective
    HD2 8 .M414 Oe>NeV THE MANAGEMENT OF END USER COMPUTING A RESEARCH PERSPECTIVE John F. Rockart Lauren S. Flannery February 1983 CISR WP #100 Sloan WP // 1410-83 Centerfor Information Systems Research Massachusetts Institute of Technology Sloan School of Management 77 Massachusetts Avenue Cambridge, Massachusetts, 02139 THE MANAGEMENT OF END USER COMPUTING A RESEARCH PERSPECTIVE John F. Rockart Lauren S . Flannery February 1983 CISR WP #100 Sloan WP // 1410-83 Rockart - Flannery 1983 Center for Information Systems Research Sloan School of Management Massachusetts Institute of Technology MAY 3 1 1983 RECe;v£d 1- ABSTRACT Based on interviews with 200 end users and 50 information systems managers concerned with end user computing, end users can be classified into six distinct types. Each of them needs differentiated education, support and control from the Information Systems function. End users exist primarily in staff functions. They develop and use a wide spectrum of computing applications ranging from "operational systems" of the type usually developed by information systems professionals to complex analytical programs. To support a large number of their applications a new computing environment, "the third environment" (in addition to the traditional COBOL and timesharing environments) must be developed by Information Systems (I/S) management. Close attention must also be paid by I/S management to the need to involve "functional support personnel" (end users in each functional area who spend most of their time programming and aiding other end users) in the I/S end user management process. An end user strategy is needed in each organization. In addition, users cite increasing needs for support from I/S management.
    [Show full text]