PROOF User/System Interface Design

Total Page:16

File Type:pdf, Size:1020Kb

PROOF User/System Interface Design 9902.ch256 1/8/02 2:10 PM Page 1 PROOF User/System Interface Design Theo Mandel Interface Design and Development I. DEFINITIONS V. USER-CENTERED DESIGN PRINCIPLES II. HISTORY OF HUMAN–COMPUTER INTERFACE VI. THE WEB USER EXPERIENCE III. THE INTERFACE DESIGN AND USABILITY PROCESS VII. NEW DIRECTIONS IN HUMAN–COMPUTER INTERACTION IV. FUNDAMENTALS OF INTERFACE DESIGN VIII. INTERFACE DESIGN AND USABILITY RESOURCES GLOSSARY usability evaluation A test of either an actual program or device or a representation (prototype) of the computer–human interface (CHI) See Interface. system. Data obtained usually includes user perfor- graphical user interface (GUI) A user interface which mance (time, success, errors, and accuracy) and presents information graphically, typically with win- subjective responses of test participants. dows, buttons, and icons that are sizable and mov- user interface (UI) See Interface. able, as opposed to a textual user interface, where user experience The environment encompassing all information is presented on a text-based screen aspects of the end-user’s interaction with a com- and commands are typed by the user. A GUI rep- puter system, program, or Web site. In order to resents and displays a visual metaphor (such as a achieve a high-quality user experience, there must desktop) for a computer operating system or be a seamless merging of multiple disciplines, in- application. cluding engineering, marketing, graphical design, human–computer interface (HCI) See Interface. and interface design. human factors The discipline devoted to under- world wide web consortium (W3C) The industry standing and improving how humans interact with group responsible for establishing guidelines and the world around them. Research in human cog- standards for Web accessibility. nitive and social psychology, perception, and phys- world wide web (WWW) A vast network of computer ical and biological characteristics is used to apply systems. Also called the Web and the Internet. that information to the design, operation, and use WYSIWYG An acronym meaning “what you see is of products or systems for optimizing human per- what you get.” WYSIWYG refers to the technology formance, health, and safety. (syn. ergonomics.) that enables users to see images on-screen exactly interface The place where two independent systems as they will appear when printed out. As screen and meet and communicate. The presentation, naviga- printer fonts have become more sophisticated, and tion, and interaction of information between a as GUIs have improved their display, people have computer system and a user. come to expect everything to be WYSIWYG. Un- intranet A controlled, private network of computer fortunately, this is not always the case. systems for use by employees within a corporation. object-oriented user interface (OOUI) A graphical user interface that also represents objects the user THE GROWTH of the personal computer and work- works with and the behaviors and interactions users station computer markets has meant that sales of com- have with those objects. puters and software, as well as sales of services and usability The ability of a product to be used in an ef- products over the World Wide Web, are more directly fective and meaningful way by the intended user. tied to the quality of their interfaces than ever in the Encyclopedia of Information Systems, Volume Four Copyright © 2002 by Academic Press. All rights of reproduction in any form reserved. 256-1 9902.ch256 1/8/02 2:10 PM Page 2 PROOF 256-2 User/System Interface Design past. The result has been the gradual evolution of a tools, machines, systems, tasks, jobs, and an environ- standardized interface architecture, from hardware ment for productive, safe, comfortable, and effective support of mice to shared window systems to “appli- human use. cation management layers.” Along with these changes, The field of ergonomics arose from studies of how researchers, designers and developers have begun to humans interact with their environment, especially in develop specification, design, and testing techniques the workplace. The concerns of ergonomics tend to for the production of usable interfaces. be at the sensory-motor level, but with an additional User/system interface design is a complex disci- physiological flavor and an emphasis on stress. Er- pline that draws from a number of fields. In simple gonomic studies of computers and the workplace in- terms, the basic goals are to design and build systems vestigate the relationship between humans and the that are effective, are intuitive, and meet the goals of work setting, including the effects of stress, routine a set of users. By definition, a user, system, interface, work tasks, sitting posture, keyboard use, mouse us- and designer are involved. age, height and distance of computer monitors, and any other factors involved in the work environment. • User: He or she uses the system to accomplish Human–computer interaction (HCI; also com- tasks and achieve goals. puter–human interaction, CHI) is the discipline con- • System: A set of connected things or parts that cerned with the design, evaluation, and implementa- form a whole or work together. Specifically, a tion of interactive computing systems for human use (computer) program designed to provide (both hardware and software) and with the study of information and functionality to the user. human interaction with computers. HCI is a subset of • Interface: The presentation, communication, and the HF discipline, focusing on computer hardware interaction between the user and the system. and software as the “system” as defined above. • Designer: The person responsible for building the The term interface is used commonly in the HF field system based on his or her understanding of users and should be more clearly defined. An interface is and their tasks, goals, abilities, and motivations. the place at which independent systems meet and act on or communicate with each other. Narrowly de- Because user/system interface design studies a human fined, the user interface (UI) is composed of input and a machine in communication, it draws from dis- and output devices, as well as the information that ciplines on both the human and the machine side. On users see and interact with on the computer screen. the human side, relevant disciplines include cognitive More broadly defined, the UI includes everything that psychology, information architecture, communication shapes users’ involvement with the systems, informa- theory, graphic design, industrial design, linguistics, tion, and humans as they perform tasks using com- social sciences, and human performance. On the ma- puters. This includes on-line and hardcopy product chine side, the fields of computer science, computer documentation, additional documentation, training, graphics, operating systems, programming languages, personal and remote technical support, and other and development environments are relevant. tools needed to perform the task. A more encom- passing description of the computer–user interface is I. DEFINITIONS the term “user experience.” Usability guru Jakob Nielsen defines user experience on his Web site (www.nngroup.com/about/userexperience.html) as, The human race spends a great deal of time sitting down, whether working in an office, studying in a li- User experience encompasses all aspects of the end- brary, commuting by bus, car, or airplane, or eating user’s interaction with the company, its services, and in a restaurant. Some seats are far more comfortable its products. The first requirement for an exemplary than others. user experience is to meet the exact needs of the cus- tomer, without fuss or bother. Next comes simplicity Barry H. Kantowitz and Robert D. Sorkin (1983) and elegance that produce products that are a joy to own, a joy to use. True user experience goes far be- User/system interface design addresses a wide range yond giving customers what they say they want, or of both users and systems. Human factors (HF) is the providing checklist features. In order to achieve high- discipline that tries to optimize the relationship be- quality user experience in a company’s offerings there tween technology and humans. HF discovers and ap- must be a seamless merging of the services of multi- plies information about human behaviors, abilities, ple disciplines, including engineering, marketing, limitations, and other characteristics to the design of graphical and industrial design, and interface design. 9902.ch256 1/8/02 2:10 PM Page 3 PROOF User/System Interface Design 256-3 Perhaps the most common interface term used today for the ball mouse in 1974 by Xerox. The idea came is the acronym GUI. A graphical user interface (GUI) suddenly to Ron Rider, “I suggested that they turn a utilizes intuitive or familiar symbols (pictures and trackball upside down, make it small, and use it as a icons) to display system programs and files that users mouse instead. Easiest patent I ever got. It took me directly manipulate to perform user tasks and system five minutes to think of, half an hour to describe to functions. Today’s computer operating systems (Mi- the attorney, and I was done.” Apple Computer re- crosoft Windows and Apple Macintosh) are the most designed the mouse in 1979, using a rubber ball rather familiar examples of GUIs. than a metal one. Variations on the ball mouse are what GUI users mostly mouse with today. The first operating system designed around the II. HISTORY OF HUMAN–COMPUTER GUI was a Xerox in-house computer system called the INTERFACE AND GRAPHICAL USER INTERFACES Alto in the early 1970s. It had multiple, overlapping windows; used pop-up menus; and, of course, came HCI arose as a field from intertwined roots in com- with a mouse. Around 1976, icons were added to the puter graphics, operating systems, HF, ergonomics, on-screen desktop. The research and design of the industrial engineering, cognitive psychology, and com- Alto system led to the first commercial GUI product, puter science. The cognitive aspects of users will be the Xerox Star, in 1981.
Recommended publications
  • IBM Tivoli Decision Support for Z/OS: Guide to Reporting Figures
    IBM Tivoli Decision Support for z/OS Version 1.8.2 Guide to Reporting IBM SH19-6842-12 IBM Tivoli Decision Support for z/OS Version 1.8.2 Guide to Reporting IBM SH19-6842-12 Note Before using this information and the product it supports, read the information in “Notices” on page 113. Thirteenth Edition (May 2019) This edition applies to version 1, release 8, modification level 2 of IBM Tivoli Decision Support for z/OS (program number 5698-B06) and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces SH19-6842-11. © Copyright 21st Century Software Inc. and IBM Corp. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. 1994, 2019 Contents Figures ............... v Opening a report definition ......... 33 Opening a report definition when QMF is used 33 Preface .............. vii Opening a report definition when the built-in report generator is used ......... 35 Who should read this book ......... vii Opening the definition of saved report data ... 37 What this book contains .......... vii Publications .............. viii Accessing publications online ....... viii Chapter 4. Working with report groups 39 Using LookAt to look up message explanations viii Listing report groups ........... 39 Accessibility .............. ix Displaying the contents of a report group .... 40 Tivoli technical training .......... ix Viewing and modifying a report group definition . 40 Support information ........... ix Changing the report group definition..... 41 Conventions used in this book ........ x Adding a report to the group ....... 42 Typeface conventions .......... x Deleting a report from the group ...... 42 Creating a report group .........
    [Show full text]
  • Visualage for Smalltalk Handbook Volume 2: Features
    SG24-2219-00 VisualAge for Smalltalk Handbook Volume 2: Features September 1997 SG24-2219-00 International Technical Support Organization VisualAge for Smalltalk Handbook Volume 2: Features September 1997 IBM Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix A, “Special Notices.” First Edition (September 1997) This edition applies to VisualAge for Smalltalk, Versions 2, 3, and 4, for use with OS/2, AIX, and Microsoft Windows 95/NT. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. QXXE Building 80-E2 650 Harry Road San Jose, California 95120-6099 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 1997. All rights reserved. Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Contents Preface . xiii How This Redbook Is Organized ....................... xiv ITSO on the Internet ................................ xv VisualAge Support on CompuServe ..................... xvii About the Authors ................................ xvii Acknowledgments . xviii Comments Welcome . xix Chapter 1. AS/400 Connection . 1 Multiple Programs with a Single Remote Procedure Call ......... 1 RPC Part Sets Commit Boundary ........................ 1 Connection Problem with V3R1 ......................... 2 AS/400 Communication Error .......................... 2 Strange Characters on Log-on Window .................... 3 Quick Form from AS/400 Record Classes ................... 3 Communication . 4 Read Next/Previous . 4 SQL Statements . 5 Data Queues and Records ............................ 6 ODBC Requirements .
    [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]
  • Blueprint for the Decade
    Blueprint for the Decade In the 1990s, Apple will expand its role in both personal computing and enterprise computing. This will be driven by a focused product strategy that provides: • Rapid advances in our System 7 software architecture • Breakthroughs in how people interact with computers, fostered by the power of RISC • Enterprisewide client/server integration and A/UX-based open Macintosh computers and servers • An object-oriented operating system that will revolutionize the economics of software development for enterprise computing, code-named “Pink.” Our goal is to help people, individually and in organizations, transform the way they work, learn, and communicate by offering exceptional computing products and customer services. Apple will continue to be known as the company that leads the industry by providing powerful, innovative technologies that are easy to use. Our product strategy begins, as always, with Macintosh. The new products will complement and coexist with our current products, sharing data, networks, printers, file servers, and application software. A smooth migration path is a fundamental part of each new product development effort. We think that these new products will be important to the entire industry. Apple believes that its role is to develop rich platforms upon which powerful and easy-to-use applications software can be created by other companies. As the computer industry increasingly requires complex interdependencies for the development of new industry standards, Apple will no longer go the distance alone. Whenever technologies can best be developed and marketed through partnerships, alliances, and licensing arrangements, we will do so. We expect to work closely with other major industry players.
    [Show full text]
  • Reinventing User Applications for Mission Control
    Reinventing User Applications for Mission Control Jay Trimble NASA Ames Research Center, Mountain View CA, 94035, USA Alan Crocker NASA Johnson Space Center, Houston TX, 77062, USA I. Introduction Scenario, Present Day – In a simulation de-brief, flight controllers discover the need to build a multi-discipline composite display. They submit a software change request to platform services. Constrained by a traditional software change process, the changes roll out and are available for use months later. Scenario 2011 – In a simulation, flight controllers discover the need to build a multi-discipline composite display. After the de-brief is over, one flight controller stays an extra hour. Using Mission Control Technologies (MCT) certified composable user objects, the controller builds the new displays. Within the hour, the display is ready for use. Exploration Scenario – A future mission control center has continued what the International Space Station Flight Controllers have begun—the combining of what were previously multiple flight control positions into one. A slimmed down mission control center is guiding a descent to the lunar surface. Using an MCT multi-disciplinary display composition, a flight controller executes a procedure. Within each procedure step, commands and telemetry are composed, so no context switching between software packages is required. On a nearby console, another operator is viewing some of the same information. She has composed only the telemetry points she needs, and she’s viewing them as plots, not alphanumerics, as in the procedure steps. These scenarios illustrate the capability of technology now being installed and tested in NASA Johnson Space Centers (JSC) Mission Control Center (MCC).
    [Show full text]
  • Visibility Aspects Importance of User Interface Reception in Cloud Computing Applications with Increased Automation
    School of Computing Blekinge Institute of Technology Visibility Aspects Importance of User Interface Reception in Cloud Computing Applications with Increased Automation Denis Haxhixhemajli Thesis submitted for completion of Master of Science (120 credits) Main field of study: Computer Science Specialization: Informatics School of Computing Blekinge Institute of Technology SE-371 79 Karlskrona Sweden This thesis is submitted to the School of Computing at Blekinge Institute of Technology in partial fulfillment of the requirements for the degree of Master of Science (120 credits) in Computer Science with specialization in Informatics. The thesis is equivalent to 20 weeks of full time studies (30 credits). Contact Information: Author: Denis Haxhixhemajli Address: Rruga “UÇK” BII Nr:12, Pristina 10000, Republic of Kosovo E-mail: [email protected] University advisor: Hans Kyhlbäck School of Computing Blekinge Institute of Technology School of Computing Internet : www.bth.se/com Blekinge Institute of Technology Phone : + 46 455 38 50 00 SE-371 41 Karlskrona Fax : + 46 455 38 50 57 Sweden ii ACKNOWLEDGEMENTS I would like to thank my parents for their continuous support. Special thanks to my Supervisor: Hans Kyhlbäck, as I could not have done this without his detailed, precise and motivating feedback, especially for his ideas to make things better. I would also like to thank the people who participated in the scenario of this thesis. Finally, a big thanks goes to the whole academic staff of this Master’s program for their extra effort to make it awesome: Sara Eriksén, Per Flensburg, Stig Holmberg, Lars-Olof Johansson, Christian Östlund, Lars Svensson, Sten Carlsson, Viveca Asproth, Christina Amcoff Nyström, Anita Håkansson, Ulrica Skagert and Sofia Swartz.
    [Show full text]
  • A Review of User Interface Design for Interactive Machine Learning
    1 A Review of User Interface Design for Interactive Machine Learning JOHN J. DUDLEY, University of Cambridge, United Kingdom PER OLA KRISTENSSON, University of Cambridge, United Kingdom Interactive Machine Learning (IML) seeks to complement human perception and intelligence by tightly integrating these strengths with the computational power and speed of computers. The interactive process is designed to involve input from the user but does not require the background knowledge or experience that might be necessary to work with more traditional machine learning techniques. Under the IML process, non-experts can apply their domain knowledge and insight over otherwise unwieldy datasets to find patterns of interest or develop complex data driven applications. This process is co-adaptive in nature and relies on careful management of the interaction between human and machine. User interface design is fundamental to the success of this approach, yet there is a lack of consolidated principles on how such an interface should be implemented. This article presents a detailed review and characterisation of Interactive Machine Learning from an interactive systems perspective. We propose and describe a structural and behavioural model of a generalised IML system and identify solution principles for building effective interfaces for IML. Where possible, these emergent solution principles are contextualised by reference to the broader human-computer interaction literature. Finally, we identify strands of user interface research key to unlocking more efficient and productive non-expert interactive machine learning applications. CCS Concepts: • Human-centered computing → HCI theory, concepts and models; Additional Key Words and Phrases: Interactive machine learning, interface design ACM Reference Format: John J.
    [Show full text]
  • Multimedia User Interface Design Alistair US Tcliffe
    17 Multimedia User Interface Design Alistlir sS tAliife CONTENTS 17.1 Introduction ..................................................................................................................................................................... 387 17.2 Definitions and Terminology ........................................................................................................................................... 388 17.3 Cognitive Background ..................................................................................................................................................... 389 17.3.1 Perception and Comprehension ........................................................................................................................... 389 17.3.2 Selective Attention ............................................................................................................................................... 389 17.3.3 Emotion and Arousal ........................................................................................................................................... 389 17.3.4 Learning and Memorization ................................................................................................................................ 390 17.4 Design Process ................................................................................................................................................................. 391 17.4.1 Users, Requirements, and Domains ...................................................................................................................
    [Show full text]
  • User Interface Design
    User interface design ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 16 Slide 1 Objectives ● To suggest some general design principles for user interface design ● To explain different interaction styles and their use ● To explain when to use graphical and textual information presentation ● To explain the principal activities in the user interface design process ● To introduce usability attributes and approaches to system evaluation ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 16 Slide 2 Topics covered ● Design issues ● The user interface design process ● User analysis ● User interface prototyping ● Interface evaluation ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 16 Slide 3 The user interface ● User interfaces should be designed to match the skills, experience and expectations of its anticipated users. ● System users often judge a system by its interface rather than its functionality. ● A poorly designed interface can cause a user to make catastrophic errors. ● Poor user interface design is the reason why so many software systems are never used. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 16 Slide 4 Human factors in interface design ● Limited short-term memory • People can instantaneously remember about 7 items of information. If you present more than this, they are more liable to make mistakes. ● People make mistakes • When people make mistakes and systems go wrong, inappropriate alarms and messages can increase stress and hence the likelihood of more mistakes. ● People are different • People have a wide range of physical capabilities. Designers should not just design for their own capabilities. ● People have different interaction preferences • Some like pictures, some like text. ©Ian Sommerville 2004 Software Engineering, 7th edition.
    [Show full text]
  • Methods and Qualities of a Good User Interface Design
    2008:PR002 User Interface Design – Methods and Qualities of a Good User Interface Design Ravi Chandra Chaitanya Guntupalli MASTER’S THESIS Software Engineering, 2008 Department of Technology, Mathematics and Computer Science MASTER’S THESIS User Interface Design – Methods and Qualities of a Good User Interface Design Summary User interface (UI) plays a vital role in software. In terms of visibility, its design and precision holds the primary importance for depicting the exact amount of information for the intended user. Every minor decision taken for the designing of UI can contribute to the software both positively and negatively. Therefore, our study is intended to highlight the strategies that are currently being used for successfully designing UIs, and make appropriate suggestions for betterment of UI designs based on case studies and research findings. Author: Ravi Chandra Chaitanya. Guntupalli Examiner: Dr. Samantha Jenkins Advisor: Dr. Samantha Jenkins Programme: Software Engineering, 2008 Subject: Software Engineering Level: Master Date: June, 2008 Report Number: 2008:PR002 Keywords User interface design, Software Quality, Reliability, Efficiency, Conciseness, Portability, Consistency, Maintainability, Understandability, System status visibility, System consistency, Error handling, Feedback systems, Memory loading, Efficiency, Appropriate outlook, UI design principles, Usability design, Interface design, Information design, Stake holder, End user. Publisher: University West, Department of Technology, Mathematics and Computer Science,
    [Show full text]
  • User Interface Design 3 0 0 3
    COURSE CODE COURSE TITLE L T P C 1152CS108 USER INTERFACE DESIGN 3 0 0 3 A. Preamble : The design of user interfaces for machines and software, such as computers, home appliances, mobile devices, and other electronic devices, with the focus on maximizing the user experience. The goal of user interface design is to make the user’s interaction as simple and efficient as possible, in terms of accomplishing user goals (user-centered design). B. Prerequisite Courses: Sl. No Course Code Course Name 1 1150MA202 Engineering Mathematics I C. Related Courses: Sl. No Course Code Course Name 1 1151CS102 Data Structures 2 1151CS113 Computer Graphics and Image Processing D. Course Educational Objectives : Learners are exposed to Describe the web user Interface Describe the structure of user Interface and design process Organize the web systems and control E. Course Outcomes : Upon the successful completion of the course, students will be able to Knowledge Level CO Course Outcomes (Based on revised No’s Bloom’s Taxonomy) Describe the Characteristics of Graphics Interface and its K2 CO1 Principles Design the standards and structures for Human computer K2 CO2 interaction CO3 Understand the components of web systems and text boxes K2 Demonstrate the Guidance of multimedia systems and its K3 CO4 accessibility CO5 Summarize the concepts of windows layout and visualization K2 F. Correlation of Cos with Pos : Cos PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO10 PO11 PO12 PSO1 PSO2 PSO3 CO1 M M L CO2 M L M L M CO3 M L M L L CO4 M M L L L M CO5 H L M L L L L H- High; M-Medium; L-Low G.
    [Show full text]
  • Adaptation of User Interface Based on Contextual Feedback
    Adaptation of User Interface Based on Contextual Feedback Robertas Damaševičius, Paulius Paškevičius Department of Software Engineering Kaunas University of Technology Kaunas, Lithuania [email protected] Abstract—The spread of social networks and other online The users are no longer the consumers of media content, but collaboration-related practices changes the target of software also want to act as producers of content or even co-designers of products from a single user to virtual communities. Such content delivery platforms [4] to have impact on the face of the communities view user interfaces of social websites as virtual community. communication partners (facilitators) rather than mere communication medium. Effective communication requires The strength of relationships that bind a member to a proper feedback from community-driven systems that create the community can be influenced by the impact a member can illusion of active participation and control. Furthermore, make as well as a feedback that a member can receive from a feedback combined with community effort and evaluation community. The success of a virtual community relies on the mechanisms such as crowdvoting can be used as a vehicle for voluntary contribution of valuable intellectual property of adaptation of interfaces to the requests of community. The individuals to a community without explicit compensation [5]. implementation of community-driven interfaces requires the Even if an individual does not receive any explicit reward for extension of existing user interface development architectures his/her contribution, he/she often wants his/her contribution to and design patterns. In this paper we analyse known user make impact or at least be seen.
    [Show full text]