Graphical User Interfaces CS 5389 Lecture 7. The Basic Goals of Language Design Precision Precision Compactness Compactness Ease in writing and reading.

Slides:



Advertisements
Similar presentations
Chapter 12 cognitive models.
Advertisements

Chapter 5: Introduction to Information Retrieval
COMP 3715 Spring 05. Computer Interface Interaction between human and computer Has to deal with two things  User’s mental model Different user has different.
Representation at the Interface Gabriel Spitz 1 Lecture #13.
MET CS 405/605 Human Computer Interface Design. Week 5 – Design  Interaction Style ~  Command Line  Menu Selection  Form Fill  Direct Manipulation.
Command and Natural Languages
User Interface Design Notes p7 T120B pavasario sem.
Interaction Styles Course 6, CMC, 07/10/03 Direct Manipulation
Dialog Styles. The Five Primary Styles of Interaction 4 Menu selection 4 Form fill-in 4 Command language 4 Natural language 4 Direct manipulation.
Copyright © 2005, Pearson Education, Inc. Chapter 8 Command and Natural Languages.
Dialog Styles. The Six Primary Styles of Interaction n Q & A n Menu selection n Form fill-in n Command language n Natural language n Direct manipulation.
Part 4: Evaluation Days 25, 27, 29, 31 Chapter 20: Why evaluate? Chapter 21: Deciding on what to evaluate: the strategy Chapter 22: Planning who, what,
Lecture 7 Date: 23rd February
1 / 31 CS 425/625 Software Engineering User Interface Design Based on Chapter 15 of the textbook [SE-6] Ian Sommerville, Software Engineering, 6 th Ed.,
Copyright © 2005, Pearson Education, Inc. An Instructor’s Outline of Designing the User Interface 4th Edition by Ben Shneiderman & Catherine Plaisant Slides.
User Interface Design: Methods of Interaction. Accepted design principles Interface design needs to consider the following issues: 1. Visual clarity 2.
Today’s class Group Presentation More about principles, guidelines, style guides and standards In-class exercises More about usability Norman’s model of.
Help and Documentation CSCI324, IACT403, IACT 931, MCS9324 Human Computer Interfaces.
User interface design Designing effective interfaces for software systems Objectives To suggest some general design principles for user interface design.
About the Presentations The presentations cover the objectives found in the opening of each chapter. All chapter objectives are listed in the beginning.
1 User Interface Design CIS 375 Bruce R. Maxim UM-Dearborn.
Chapter 4 Product Design. Objectives of Design  As all other aspects of object-oriented system development, design can be deployed in an iterative or.
Performing User Interface Design
Design, goal of design, design process in SE context, Process of design – Quality guidelines and attributes Evolution of software design process – Procedural,
Chapter 15 Designing Effective Output
Chapter 11: Interaction Styles. Interaction Styles Introduction: Interaction styles are primarily different ways in which a user and computer system can.
Copyright © 2005, Pearson Education, Inc. Chapter 8 Command and Natural Languages.
Ch 6 - Menu-Based and Form Fill-In Interactions Yonglei Tao School of Computing & Info Systems GVSU.
1 Command and Natural Languages Lecture 9. CS774 – Spring The Basic Goals of Language Design Precision Compactness Ease in writing and reading Speed.
1 Human-Computer Interaction  Design process  Task and User Characteristics  Guidelines  Evaluation.
11.10 Human Computer Interface www. ICT-Teacher.com.
Nielsen’s Ten Usability Heuristics
Usability Evaluation/LP Usability: how to judge it.
Multimedia Specification Design and Production 2012 / Semester 1 / week 5 Lecturer: Dr. Nikos Gazepidis
1 Chapter 15 User Interface Design. 2 Interface Design Easy to use? Easy to understand? Easy to learn?
© 2010 Pearson Addison-Wesley. All rights reserved. Addison Wesley is an imprint of Designing the User Interface: Strategies for Effective Human-Computer.
Software Architecture
Fall 2002CS/PSY Dialog Design 1 Command languages and WIMP Command languages  Advantages, disadvantages  Design guidelines WIMP  Advantages, disadvantages.
Evaluating a UI Design Expert inspection methods Cognitive Walkthrough
1 COSC 4406 Software Engineering COSC 4406 Software Engineering Haibin Zhu, Ph.D. Dept. of Computer Science and mathematics, Nipissing University, 100.
Developed by Tim Bell Department of Computer Science and Software Engineering University of Canterbury Human Computer Interaction.
Heuristic Evaluation Short tutorial to heuristic evaluation
Yonglei Tao School of Computing & Info Systems GVSU Ch 7 Design Guidelines.
Conceptual Model Design Informing the user what to do Lecture # 10 (a) Gabriel Spitz.
Importance of user interface design – Useful, useable, used Three golden rules – Place the user in control – Reduce the user’s memory load – Make the.
User Interface Design Lecture #4 Part-A. 30 January, 2008Human Computer Interaction Spring 2008, Lecture #4A 2 Agenda Principles on User Interface Design.
Human-Computer Interaction Design process Task and User Characteristics Guidelines Evaluation ISE
Basic Elements.  Design is the process of collecting ideas, and aesthetically arranging and implementing them, guided by certain principles for a specific.
© 2010 Pearson Addison-Wesley. All rights reserved. Addison Wesley is an imprint of 1-1 HCI Human Computer Interaction Week 7.
IT323 - Software Engineering 2 1 Tutorial 3.  Suggest ways in which the user interface to an e-commerce system such as an online stores might be adapted.
© 2016 Cognizant. © 2016 Cognizant Introduction PREREQUISITES SCOPE Heuristic evaluation is a discount usability engineering method for quick, cheap,
System is a set of interacting or interdependent components forming an integrated whole.
Ten Usability Heuristics These are ten general principles for user interface design. They are called "heuristics" because they are more in the nature of.
Human Computer Interaction Lecture 21 User Support
Mechanism Level Design - continued
1. Command and Natural Languages
Chapter 2 Hix & Hartson Guidelines.
11.10 Human Computer Interface
User Interface Design PPT By :Dr. R. Mall.
Copyright Catherine M. Burns
Dialog Design 1 Command languages and WIMP
Kuliah #7: Command and Natural Languages
Heuristic Evaluation Jon Kolko Professor, Austin Center for Design.
10 Design Principles.
Systems Analysis and Design in a Changing World, 6th Edition
Proper functionality Good human computer interface Easy to maintain
Nilesen 10 hueristics.
CIS 375 Bruce R. Maxim UM-Dearborn
CHAPTER 7: Command and Natural Languages
Presentation transcript:

Graphical User Interfaces CS 5389 Lecture 7

The Basic Goals of Language Design Precision Precision Compactness Compactness Ease in writing and reading Ease in writing and reading Speed in learning Speed in learning Simplicity to reduce errors Simplicity to reduce errors Ease of retention over time Ease of retention over time

Higher-Level Goals of Language Design Close correspondence between reality and the notation Close correspondence between reality and the notation Convenience in carrying out manipulations relevant to user's tasks Convenience in carrying out manipulations relevant to user's tasks Compatibility with existing notations Compatibility with existing notations Flexibility to accommodate novice and expert users Flexibility to accommodate novice and expert users Expressiveness to encourage creativity Expressiveness to encourage creativity Visual appeal Visual appeal

Functionality to Support User ’ s Tasks Users do wide range of work: text editing text editing electronic mail electronic mail financial management financial management airline or hotel reservations airline or hotel reservations inventory inventory manufacturing process control manufacturing process control gaming gaming

Functionality to Support User ’ s Tasks (cont.) Designers should determine functionality of the system by studying users' task domain determine functionality of the system by studying users' task domain create a list of task actions and objects create a list of task actions and objects abstract this list into a set of interface actions and objects abstract this list into a set of interface actions and objects represent low-level interface syntax represent low-level interface syntax create a table of user communities and tasks, with expected use frequency create a table of user communities and tasks, with expected use frequency determine hierarchy of importance of user communities (i.e. prime users) determine hierarchy of importance of user communities (i.e. prime users) evaluate destructive actions (e.g. deleting objects) to ensure reversibility evaluate destructive actions (e.g. deleting objects) to ensure reversibility identify error conditions and prepare error messages identify error conditions and prepare error messages allow shortcuts for expert users, such as macros and customizing system parameters allow shortcuts for expert users, such as macros and customizing system parameters

Command-Organization Strategies A unifying interface concept or metaphor aids –learning –problem solving –retention Designers often err by choosing a metaphor closer to machine domain than to the user's task domain. Simple command set –Each command is chosen to carry out a single task. The number of commands match the number of tasks. –For small number of tasks, this can produce a system easy to learn and use. –E.g. the vi editor of Unix (Figure 8.2).

Command plus arguments/options Command plus arguments Follow each command by one or more arguments that indicate objects to be manipulated, e.g. Follow each command by one or more arguments that indicate objects to be manipulated, e.g. –COPY FILEA, FILEB –DELETE FILEA –PRINT FILEA, FILEB, FILEC Keyword labels for arguments are helpful for some users, e.g. COPY FROM=FILEA TO=FILEB. Keyword labels for arguments are helpful for some users, e.g. COPY FROM=FILEA TO=FILEB. Commands may also have options to indicate special cases, e.g.: Commands may also have options to indicate special cases, e.g.: –PRINT/3,HQ FILEA –PRINT (3, HQ) FILEA –PRINT FILEA -3, HQ to produce 3 copies of FILEA on the printer in the headquarters building. to produce 3 copies of FILEA on the printer in the headquarters building. Error rates and the need for extensive training increase with the number of possible options. Error rates and the need for extensive training increase with the number of possible options.

The Benefits of Structure Human learning, problem solving, and memory are greatly facilitated by meaningful structure. Beneficial for Beneficial for –task concepts –computer concepts –syntactic details of command languages Consistent Argument Ordering Inconsistent order of argumentsConsistent order of arguments SEARCHfile no, message idSEARCHmessage id, file no TRIMmessage id, segment sizeTRIMmessage id, segment size REPLACEmessage id, code noREPLACEmessage id, code no INVERTgroup size, message idINVERTmessage id, group size

Hierarchical command structure –The full set of commands is organized into a tree structure –5x3x4 = 60 tasks with 5 command names and 1 rule of formation ActionObject Destinatio n CREATEFileFile DISPLAYProcess Local printer REMOVEDirectoryScreen COPY Remote printer MOVE

Symbols versus Keywords Command structure affects performance Symbol Editor Keyword Editor FIND:/TOOTH/;-1 BACKWARD TO "TOOTH" LIST;10 LIST 10 LINES RS:/KO/,/OK/;* CHANGE ALL "KO" TO "OK"

Hierarchical Structure and Congruence Sources of structure that have proved advantageous include: Positional consistency Positional consistency Grammatical consistency Grammatical consistency Congruent pairing Congruent pairing Hierarchical form Hierarchical form

Naming and Abbreviations There is often a lack of consistency or obvious strategy for construction of command abbreviations. Specificity Versus Generality Infrequent, discriminating words insertdelete Frequent, discriminating words addremove Infrequent, nondiscriminating words ambleperceive Frequent, nondiscriminating words walkview General words (frequent, nondiscriminating) altercorrect Nondiscriminating nonwords (nonsense) GACMIK Discriminating nonwords (icons) abc-adbcabc-ab

Six Potential Abbreviation Strategies 1. Simple truncation: The first, second, third, etc. letters of each command. 2. Vowel drop with simple truncation: Eliminate vowels and use some of what remains. 3. First and last letter: Since the first and last letters are highly visible, use them. 4. First letter of each word in a phrase: Use with a hierarchical design plan. 5. Standard abbreviations from other contexts: Use familiar abbreviations. 6. Phonics: Focus attention on the sound.

Guidelines for using abbreviations Ehrenreich and Porcu (1982) offer this set of guidelines: A simple primary rule should be used to generate abbreviations for most items; a simple secondary rule should be used for those items where there is a conflict. A simple primary rule should be used to generate abbreviations for most items; a simple secondary rule should be used for those items where there is a conflict. Abbreviations generated by the secondary rule should have a marker (for example, an asterisk) incorporated in them. Abbreviations generated by the secondary rule should have a marker (for example, an asterisk) incorporated in them. The number of words abbreviated by the secondary rule should be kept to a minimum. The number of words abbreviated by the secondary rule should be kept to a minimum. Users should be familiar with the rules used to generate abbreviations. Users should be familiar with the rules used to generate abbreviations. Truncation should be used because it is an easy rule for users to comprehend and remember. However, when it produces a large number of identical abbreviations for different words, adjustments must be found. Truncation should be used because it is an easy rule for users to comprehend and remember. However, when it produces a large number of identical abbreviations for different words, adjustments must be found. Fixed-length abbreviations should be used in preference to variable-length ones. Fixed-length abbreviations should be used in preference to variable-length ones. Abbreviations should not be designed to incorporate endings (ING, ED, S). Abbreviations should not be designed to incorporate endings (ING, ED, S). Unless there is a critical space problem, abbreviations should not be used in messages generated by the computer and read by the user. Unless there is a critical space problem, abbreviations should not be used in messages generated by the computer and read by the user.

Command-language guidelines

Natural Language in Computing Natural-language interaction Natural-language interaction Natural-language queries and question answering Natural-language queries and question answering Text-database searching Text-database searching Natural-language text generation Natural-language text generation Adventure games and instructional systems Adventure games and instructional systems