SlideShare a Scribd company logo
Chapter 18 
Designing User Interfaces 
Systems Analysis and Design 
Kendall and Kendall 
Fifth Edition
Major Topics 
User interfaces 
Dialogue guidelines 
Feedback 
Help 
Ecommerce dialogue 
Data mining 
Ergonomics 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-2
The User Interface 
The user interface is the system which 
helps users communicate with the 
computer system and/or the application 
system 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-3
User Interface Design 
Objectives 
To design a better user interface, use 
the following objectives: 
Effectiveness as achieved through design 
of interfaces that allow the user to access 
the system in a way that is congruent with 
their individual needs 
Efficiency as demonstrated through 
interfaces that increase speed of data 
entry, and reduce errors 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-4
User Interface Design 
Objectives 
Further interface design objectives 
User consideration as demonstrated in 
designing suitable interfaces, and providing 
appropriate feedback to users from the 
system 
Generating usable queries 
Productivity as shown through following 
sound principles of design for user 
interfaces and work spaces 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-5
Components of the User 
Interface 
The user interface has two main 
components 
Presentation language, which is the 
computer-to-human part of the transaction 
Action language that characterizes the 
human-to-computer portion 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-6
Types of User Interfaces 
There are several types of user 
interfaces: 
Natural-language interfaces 
Question-and-answer interfaces 
A menu interface 
Form-fill interfaces 
Command-language interfaces 
Graphical User Interfaces (GUIs) 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-7
Natural-Language Interfaces 
Natural-language interfaces permit 
users to interact with the computer in 
their everyday or "natural" language 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-8
Question-and-Answer 
Interfaces 
Question-and-answer interfaces 
The computer displays a question for the 
user on the screen 
The user enters an answer via the 
keyboard 
The computer acts on that input 
information in a preprogrammed manner 
New users may find the question-and-answer 
interface most comfortable 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-9
A Menu Interface 
A menu interface, which provides the 
user with an onscreen list of available 
selections 
A nested menu is a menu which can be 
reached through another menu 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-10
Advantages of Nested Menus 
The advantages of nested menus are 
Nested menus give a less cluttered screen 
Nested menus eliminate menu options 
which do not interest a user 
Nested menus allow users to move quickly 
through the program 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-11
Graphical User Interface (GUI) 
Menus 
GUI menus guidelines 
The main menu is always on the screen 
The main menu uses single words 
The main menu should have secondary 
menus grouped into similar features 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-12
Graphical User Interface (GUI) 
Menus 
Further GUI menus guidelines 
The secondary drop-down menus often 
consist of more than one word 
Secondary options perform actions or 
display additional menu options 
Menu items in gray are unavailable for the 
current activity 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-13
Form-Fill Interfaces 
Form-fill interfaces are onscreen forms 
displaying fields containing data items 
or parameters that need to be 
communicated to the user 
Form-fill interfaces may be implemented 
using the Web 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-14
Advantages and Disadvantages 
of Web Forms 
Advantages of using a Web-based form 
User enters the data 
Data may be entered 24 hours a day, 
globally 
Disadvantages of a Web-based form 
The user may not know what to enter if 
the form is not clear 
User might be nervous about using a credit 
card over the Internet 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-15
Command-Language 
Interfaces 
Command-language interfaces are more 
popular than the previous ones 
Allow the user to control the application 
with a series of keystrokes, commands, 
phrases, or some sequence of these 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-16
Graphical User Interfaces 
(GUIs) 
GUIs provide a strong metaphor of the 
application 
Allow direct manipulation of the 
graphical representation on the screen 
Can be accomplished with keyboard input, 
joystick, or mouse 
Requires more system sophistication than 
other interfaces 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-17
Dialog 
Dialog is the communication between a 
person and the computer 
Three key points to be considered 
Meaningful communication 
Minimal user action 
Standard operation and consistency 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-18
Communication 
Communication means that the user 
understands the information that is 
being presented 
Users with less skill require a greater 
amount of communication 
Provide easy to use help screens 
Often these contain hyperlinks to other 
related help topics 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-19
Minimal User Action 
Minimal user action is achieved by 
Entering codes instead of code meanings 
Enter only data that are not stored on files 
Not requiring users to enter editing 
characters 
Supplying default values on entry screens 
Providing inquiry programs with short entry 
fields 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-20
Minimal User Action 
Further key points 
Providing keystrokes for selecting menu 
options that are normally selected using a 
mouse 
Selecting codes from a pull-down menu on 
a GUI screen 
Provide context-sensitive menus, displayed 
when the right mouse button is clicked on 
an object 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-21
Standard Operation 
Standard operation is achieved by 
Keeping header and footer information in 
the same locations for all screens 
Using the same keystrokes to exit a 
program 
Using the same keystrokes to cancel a 
transaction 
Using a standard key for obtaining help 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-22
Standard Operation 
Further key points 
Standardized use of icons when using 
graphical user interface screens 
Consistent use of terminology within a 
screen or Web site 
Providing a consistent way to navigate 
through the dialog 
Consistent font alignment, size, and color 
on a Web page 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-23
Tab Control Dialogue Boxes 
Tab control dialog boxes are a feature 
of GUI design 
They should have logically grouped 
functions on each tab 
Each tab dialog box should have OK, 
Cancel or Apply, and perhaps Help 
buttons 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-24
Voice or Speech Recognition 
Voice or speech recognition systems are 
developing rapidly 
There are two different types of voice 
recognition: 
Continuous speech systems, allowing for 
dictation 
Speaker independence, so people can 
enter commands or words at a given 
workstation 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-25
Evaluating User Interfaces 
The five useful standards in evaluating 
the interfaces are 
The training period for users should be 
acceptably short 
Users early in their training should be able 
to enter commands without thinking about 
them, or referring to a help menu or 
manual 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-26
Evaluating User Interfaces 
Continued evaluation guidelines 
The interface should be "seamless" so that 
errors are few, and those that do occur are 
not occurring because of poor design 
Time necessary for users and the system 
to bounce back from errors should be short 
Infrequent users should be able to relearn 
the system quickly 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-27
Feedback 
All systems require feedback in order to 
monitor and change behavior by 
Comparing current behavior with 
predetermined goals 
Giving back information describing the gap 
between actual and intended performance 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-28
Types of Feedback 
Feedback to the user is necessary in 
seven distinct situations: 
The computer has accepted the input 
The input is in the correct form 
The input is not in the correct form 
There will be a delay in processing 
The request has been completed 
The computer cannot complete the request 
More detailed feedback is available 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-29
Program Help 
Program help comes in a variety of 
ways: 
Pressing a function key, such as F1 
A GUI pull-down menu 
Context-sensitive help, specific for the 
operation being performed 
Iconic help, obtained when a cursor is left 
over an icon for a few seconds 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-30
Program Help 
Program help options, continued 
Wizards, which provide a series of 
questions and answers when trying to 
perform an operation 
Telephone help desks provided by the 
software manufacturer 
Software forums on nation wide bulletin 
boards 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-31
Ecommerce Dialog 
Extra considerations are needed when 
developing ecommerce Web sites 
Feedback needs to be solicited from 
customers, using either of two 
methods: 
Launch the user’s email program 
Create a blank feedback template with a 
submit button labeled “feedback” 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-32
Intuitive Navigation for 
Ecommerce Sites 
Intuitive navigation should be designed 
Creating a rollover menu 
Building a collection of hierarchical links 
Placing a site map on the home page and 
emphasizing the link to it from every page 
on the site 
Placing a navigational bar on every inside 
page that repeats the categories used on 
the entry screen 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-33
Types of Queries 
There are six different types of queries: 
Obtain specified data for a particular entity 
Find a group of entities that have certain 
characteristics 
Find attributes for an entity for certain 
characteristics 
Display all the attributes for a certain entity 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-34
Types of Queries 
Different types of queries (continued): 
Find all entities with a certain characteristic 
List attributes for all entities for certain 
characteristics 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-35
Query Notation 
 V is value, E is entity, A is attributes, 
variables in parentheses are given: 
Query type 1: V <--- (E,A) 
Query type 2: E <--- (V,A) 
Query type 3: A <--- (V,E) 
Query type 4: V <--- (E, all A) 
Query type 5: E <--- (V, all A) 
Query type 6: A <--- (V, all E) 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-36
Methods for Implementing 
Queries 
There are two methods for 
implementing database queries: 
Query By Example (QBE), which allows 
users to select fields and specify conditions 
using a grid 
Structured Query Language (SQL), which 
uses a series of keywords and commands 
to select the rows and columns that should 
be displayed 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-37
Parameter Queries 
A parameter query allows users to enter 
a value to select records without 
changing the query syntax 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-38
Web Searches 
Web searches use search engines to 
answer a query 
Guidelines for searching the Web 
Decide whether to search or surf the Web 
Think of the key terms before searching 
Construct the search questions logically, 
with attention to the use of AND and OR 
search logic 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-39
Web Searches 
Further guidelines for searching the 
Web are: 
Use a search engine that saves your 
searches 
Use a search engine that informs you of 
changes in the Web sites you select 
Look for new search engines periodically 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-40
Data Mining 
Data mining is gathering a large 
amount of information about a person 
and their habits and using that 
information as a predictor of future 
behavior 
It must be carefully and ethically used 
to avoid infringing on an individual’s 
privacy 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-41
Ergonomics 
Systems analysts should consider an 
ergonomically sound working 
environment even though they usually 
don't have much control over the design 
of the workspace 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-42
Ergonomics 
Some of the important working 
environmental variables to be 
considered are 
Room color and lighting 
VDT or LCD screens 
User keyboards 
Computer desks 
User seating 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-43

More Related Content

What's hot

Chap01
Chap01Chap01
Chap01
lolanyunyu
 
Chap08
Chap08Chap08
Chap08
lolanyunyu
 
Chap12
Chap12Chap12
Chap12
lolanyunyu
 
Chap11
Chap11Chap11
Chap11
lolanyunyu
 
Chap14
Chap14Chap14
Chap14
lolanyunyu
 
Chap06
Chap06Chap06
Chap06
lolanyunyu
 
Chap03
Chap03Chap03
Chap03
lolanyunyu
 
Chap22
Chap22Chap22
Chap22
lolanyunyu
 
Chap04
Chap04Chap04
Chap04
lolanyunyu
 
Kendall sad8e ch03
Kendall sad8e ch03Kendall sad8e ch03
Kendall sad8e ch03
N/A
 
Projman
ProjmanProjman
Projman
Fajar Baskoro
 
Ch10-Program Design
Ch10-Program DesignCh10-Program Design
Ch10-Program Design
Fajar Baskoro
 
Improve Predictability & Efficiency with Kanban Metrics using IBM Rational In...
Improve Predictability & Efficiency with Kanban Metrics using IBM Rational In...Improve Predictability & Efficiency with Kanban Metrics using IBM Rational In...
Improve Predictability & Efficiency with Kanban Metrics using IBM Rational In...
Marc Nehme
 
A Comparative Analysis of Project Management Information Systems to Support C...
A Comparative Analysis of Project Management Information Systems to Support C...A Comparative Analysis of Project Management Information Systems to Support C...
A Comparative Analysis of Project Management Information Systems to Support C...
Camila De Araujo
 
Defining and Aligning Requirements using System Architect and DOORS
Defining and Aligning Requirements using System Architect and DOORSDefining and Aligning Requirements using System Architect and DOORS
Defining and Aligning Requirements using System Architect and DOORS
Paul W. Johnson
 

What's hot (15)

Chap01
Chap01Chap01
Chap01
 
Chap08
Chap08Chap08
Chap08
 
Chap12
Chap12Chap12
Chap12
 
Chap11
Chap11Chap11
Chap11
 
Chap14
Chap14Chap14
Chap14
 
Chap06
Chap06Chap06
Chap06
 
Chap03
Chap03Chap03
Chap03
 
Chap22
Chap22Chap22
Chap22
 
Chap04
Chap04Chap04
Chap04
 
Kendall sad8e ch03
Kendall sad8e ch03Kendall sad8e ch03
Kendall sad8e ch03
 
Projman
ProjmanProjman
Projman
 
Ch10-Program Design
Ch10-Program DesignCh10-Program Design
Ch10-Program Design
 
Improve Predictability & Efficiency with Kanban Metrics using IBM Rational In...
Improve Predictability & Efficiency with Kanban Metrics using IBM Rational In...Improve Predictability & Efficiency with Kanban Metrics using IBM Rational In...
Improve Predictability & Efficiency with Kanban Metrics using IBM Rational In...
 
A Comparative Analysis of Project Management Information Systems to Support C...
A Comparative Analysis of Project Management Information Systems to Support C...A Comparative Analysis of Project Management Information Systems to Support C...
A Comparative Analysis of Project Management Information Systems to Support C...
 
Defining and Aligning Requirements using System Architect and DOORS
Defining and Aligning Requirements using System Architect and DOORSDefining and Aligning Requirements using System Architect and DOORS
Defining and Aligning Requirements using System Architect and DOORS
 

Similar to Chap18

Designing user interface week ix part 2
Designing user interface week ix part 2Designing user interface week ix part 2
Designing user interface week ix part 2
Johnecis Madrid
 
Designing effective input week viii
Designing effective input week viiiDesigning effective input week viii
Designing effective input week viii
Johnecis Madrid
 
user-interface-design-131010063550-phpapp01.pdf
user-interface-design-131010063550-phpapp01.pdfuser-interface-design-131010063550-phpapp01.pdf
user-interface-design-131010063550-phpapp01.pdf
LPhiHng3
 
User interface-design
User interface-designUser interface-design
User interface-design
DarkHorse Technologies Pvt Ltd
 
Chapter14 designing interfaces and dialogues
Chapter14 designing interfaces and dialoguesChapter14 designing interfaces and dialogues
Chapter14 designing interfaces and dialogues
Dhani Ahmad
 
Desenho De Interfaces Joao Jose Saraiva Da Fonseca
Desenho De Interfaces Joao Jose Saraiva Da FonsecaDesenho De Interfaces Joao Jose Saraiva Da Fonseca
Desenho De Interfaces Joao Jose Saraiva Da Fonseca
joao jose saraiva da fonseca
 
Chapter5
Chapter5Chapter5
Chapter5
webuploader
 
Bringing Your Wireframe to Life
Bringing Your Wireframe to LifeBringing Your Wireframe to Life
Bringing Your Wireframe to Life
UXPA DC
 
Top No Code and Low Code Platforms | OmnePresent
Top No Code and Low Code Platforms | OmnePresentTop No Code and Low Code Platforms | OmnePresent
Top No Code and Low Code Platforms | OmnePresent
OmnePresentTechnolog1
 
Design Effective Input Chapter 12
Design Effective Input Chapter 12Design Effective Input Chapter 12
Design Effective Input Chapter 12
Novander Ulag
 
User Interface Design
User Interface DesignUser Interface Design
User Interface Design
Yes3000
 
Edge903 Project
Edge903 ProjectEdge903 Project
Edge903 Project
xyz01
 
SECh1516
SECh1516SECh1516
SECh1516
Joe Christensen
 
MR Summary Presentation
MR Summary PresentationMR Summary Presentation
MR Summary Presentation
markrichman
 
Consumer electronics show 2011 - tll
Consumer electronics show   2011 - tllConsumer electronics show   2011 - tll
Consumer electronics show 2011 - tll
jerryhalterman
 
Unit 2
Unit 2Unit 2
Ch09-User Interface Design
Ch09-User Interface DesignCh09-User Interface Design
Ch09-User Interface Design
Fajar Baskoro
 
Ppt 21 ge
Ppt 21 gePpt 21 ge
Build Smarter User Interfaces for Legacy Applications with IBM Rational Host ...
Build Smarter User Interfaces for Legacy Applications with IBM Rational Host ...Build Smarter User Interfaces for Legacy Applications with IBM Rational Host ...
Build Smarter User Interfaces for Legacy Applications with IBM Rational Host ...
Strongback Consulting
 
Application Based Smart Optimized Keyboard for Mobile Apps
Application Based Smart Optimized Keyboard for Mobile AppsApplication Based Smart Optimized Keyboard for Mobile Apps
Application Based Smart Optimized Keyboard for Mobile Apps
cscpconf
 

Similar to Chap18 (20)

Designing user interface week ix part 2
Designing user interface week ix part 2Designing user interface week ix part 2
Designing user interface week ix part 2
 
Designing effective input week viii
Designing effective input week viiiDesigning effective input week viii
Designing effective input week viii
 
user-interface-design-131010063550-phpapp01.pdf
user-interface-design-131010063550-phpapp01.pdfuser-interface-design-131010063550-phpapp01.pdf
user-interface-design-131010063550-phpapp01.pdf
 
User interface-design
User interface-designUser interface-design
User interface-design
 
Chapter14 designing interfaces and dialogues
Chapter14 designing interfaces and dialoguesChapter14 designing interfaces and dialogues
Chapter14 designing interfaces and dialogues
 
Desenho De Interfaces Joao Jose Saraiva Da Fonseca
Desenho De Interfaces Joao Jose Saraiva Da FonsecaDesenho De Interfaces Joao Jose Saraiva Da Fonseca
Desenho De Interfaces Joao Jose Saraiva Da Fonseca
 
Chapter5
Chapter5Chapter5
Chapter5
 
Bringing Your Wireframe to Life
Bringing Your Wireframe to LifeBringing Your Wireframe to Life
Bringing Your Wireframe to Life
 
Top No Code and Low Code Platforms | OmnePresent
Top No Code and Low Code Platforms | OmnePresentTop No Code and Low Code Platforms | OmnePresent
Top No Code and Low Code Platforms | OmnePresent
 
Design Effective Input Chapter 12
Design Effective Input Chapter 12Design Effective Input Chapter 12
Design Effective Input Chapter 12
 
User Interface Design
User Interface DesignUser Interface Design
User Interface Design
 
Edge903 Project
Edge903 ProjectEdge903 Project
Edge903 Project
 
SECh1516
SECh1516SECh1516
SECh1516
 
MR Summary Presentation
MR Summary PresentationMR Summary Presentation
MR Summary Presentation
 
Consumer electronics show 2011 - tll
Consumer electronics show   2011 - tllConsumer electronics show   2011 - tll
Consumer electronics show 2011 - tll
 
Unit 2
Unit 2Unit 2
Unit 2
 
Ch09-User Interface Design
Ch09-User Interface DesignCh09-User Interface Design
Ch09-User Interface Design
 
Ppt 21 ge
Ppt 21 gePpt 21 ge
Ppt 21 ge
 
Build Smarter User Interfaces for Legacy Applications with IBM Rational Host ...
Build Smarter User Interfaces for Legacy Applications with IBM Rational Host ...Build Smarter User Interfaces for Legacy Applications with IBM Rational Host ...
Build Smarter User Interfaces for Legacy Applications with IBM Rational Host ...
 
Application Based Smart Optimized Keyboard for Mobile Apps
Application Based Smart Optimized Keyboard for Mobile AppsApplication Based Smart Optimized Keyboard for Mobile Apps
Application Based Smart Optimized Keyboard for Mobile Apps
 

Chap18

  • 1. Chapter 18 Designing User Interfaces Systems Analysis and Design Kendall and Kendall Fifth Edition
  • 2. Major Topics User interfaces Dialogue guidelines Feedback Help Ecommerce dialogue Data mining Ergonomics Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-2
  • 3. The User Interface The user interface is the system which helps users communicate with the computer system and/or the application system Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-3
  • 4. User Interface Design Objectives To design a better user interface, use the following objectives: Effectiveness as achieved through design of interfaces that allow the user to access the system in a way that is congruent with their individual needs Efficiency as demonstrated through interfaces that increase speed of data entry, and reduce errors Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-4
  • 5. User Interface Design Objectives Further interface design objectives User consideration as demonstrated in designing suitable interfaces, and providing appropriate feedback to users from the system Generating usable queries Productivity as shown through following sound principles of design for user interfaces and work spaces Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-5
  • 6. Components of the User Interface The user interface has two main components Presentation language, which is the computer-to-human part of the transaction Action language that characterizes the human-to-computer portion Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-6
  • 7. Types of User Interfaces There are several types of user interfaces: Natural-language interfaces Question-and-answer interfaces A menu interface Form-fill interfaces Command-language interfaces Graphical User Interfaces (GUIs) Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-7
  • 8. Natural-Language Interfaces Natural-language interfaces permit users to interact with the computer in their everyday or "natural" language Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-8
  • 9. Question-and-Answer Interfaces Question-and-answer interfaces The computer displays a question for the user on the screen The user enters an answer via the keyboard The computer acts on that input information in a preprogrammed manner New users may find the question-and-answer interface most comfortable Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-9
  • 10. A Menu Interface A menu interface, which provides the user with an onscreen list of available selections A nested menu is a menu which can be reached through another menu Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-10
  • 11. Advantages of Nested Menus The advantages of nested menus are Nested menus give a less cluttered screen Nested menus eliminate menu options which do not interest a user Nested menus allow users to move quickly through the program Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-11
  • 12. Graphical User Interface (GUI) Menus GUI menus guidelines The main menu is always on the screen The main menu uses single words The main menu should have secondary menus grouped into similar features Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-12
  • 13. Graphical User Interface (GUI) Menus Further GUI menus guidelines The secondary drop-down menus often consist of more than one word Secondary options perform actions or display additional menu options Menu items in gray are unavailable for the current activity Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-13
  • 14. Form-Fill Interfaces Form-fill interfaces are onscreen forms displaying fields containing data items or parameters that need to be communicated to the user Form-fill interfaces may be implemented using the Web Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-14
  • 15. Advantages and Disadvantages of Web Forms Advantages of using a Web-based form User enters the data Data may be entered 24 hours a day, globally Disadvantages of a Web-based form The user may not know what to enter if the form is not clear User might be nervous about using a credit card over the Internet Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-15
  • 16. Command-Language Interfaces Command-language interfaces are more popular than the previous ones Allow the user to control the application with a series of keystrokes, commands, phrases, or some sequence of these Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-16
  • 17. Graphical User Interfaces (GUIs) GUIs provide a strong metaphor of the application Allow direct manipulation of the graphical representation on the screen Can be accomplished with keyboard input, joystick, or mouse Requires more system sophistication than other interfaces Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-17
  • 18. Dialog Dialog is the communication between a person and the computer Three key points to be considered Meaningful communication Minimal user action Standard operation and consistency Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-18
  • 19. Communication Communication means that the user understands the information that is being presented Users with less skill require a greater amount of communication Provide easy to use help screens Often these contain hyperlinks to other related help topics Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-19
  • 20. Minimal User Action Minimal user action is achieved by Entering codes instead of code meanings Enter only data that are not stored on files Not requiring users to enter editing characters Supplying default values on entry screens Providing inquiry programs with short entry fields Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-20
  • 21. Minimal User Action Further key points Providing keystrokes for selecting menu options that are normally selected using a mouse Selecting codes from a pull-down menu on a GUI screen Provide context-sensitive menus, displayed when the right mouse button is clicked on an object Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-21
  • 22. Standard Operation Standard operation is achieved by Keeping header and footer information in the same locations for all screens Using the same keystrokes to exit a program Using the same keystrokes to cancel a transaction Using a standard key for obtaining help Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-22
  • 23. Standard Operation Further key points Standardized use of icons when using graphical user interface screens Consistent use of terminology within a screen or Web site Providing a consistent way to navigate through the dialog Consistent font alignment, size, and color on a Web page Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-23
  • 24. Tab Control Dialogue Boxes Tab control dialog boxes are a feature of GUI design They should have logically grouped functions on each tab Each tab dialog box should have OK, Cancel or Apply, and perhaps Help buttons Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-24
  • 25. Voice or Speech Recognition Voice or speech recognition systems are developing rapidly There are two different types of voice recognition: Continuous speech systems, allowing for dictation Speaker independence, so people can enter commands or words at a given workstation Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-25
  • 26. Evaluating User Interfaces The five useful standards in evaluating the interfaces are The training period for users should be acceptably short Users early in their training should be able to enter commands without thinking about them, or referring to a help menu or manual Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-26
  • 27. Evaluating User Interfaces Continued evaluation guidelines The interface should be "seamless" so that errors are few, and those that do occur are not occurring because of poor design Time necessary for users and the system to bounce back from errors should be short Infrequent users should be able to relearn the system quickly Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-27
  • 28. Feedback All systems require feedback in order to monitor and change behavior by Comparing current behavior with predetermined goals Giving back information describing the gap between actual and intended performance Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-28
  • 29. Types of Feedback Feedback to the user is necessary in seven distinct situations: The computer has accepted the input The input is in the correct form The input is not in the correct form There will be a delay in processing The request has been completed The computer cannot complete the request More detailed feedback is available Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-29
  • 30. Program Help Program help comes in a variety of ways: Pressing a function key, such as F1 A GUI pull-down menu Context-sensitive help, specific for the operation being performed Iconic help, obtained when a cursor is left over an icon for a few seconds Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-30
  • 31. Program Help Program help options, continued Wizards, which provide a series of questions and answers when trying to perform an operation Telephone help desks provided by the software manufacturer Software forums on nation wide bulletin boards Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-31
  • 32. Ecommerce Dialog Extra considerations are needed when developing ecommerce Web sites Feedback needs to be solicited from customers, using either of two methods: Launch the user’s email program Create a blank feedback template with a submit button labeled “feedback” Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-32
  • 33. Intuitive Navigation for Ecommerce Sites Intuitive navigation should be designed Creating a rollover menu Building a collection of hierarchical links Placing a site map on the home page and emphasizing the link to it from every page on the site Placing a navigational bar on every inside page that repeats the categories used on the entry screen Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-33
  • 34. Types of Queries There are six different types of queries: Obtain specified data for a particular entity Find a group of entities that have certain characteristics Find attributes for an entity for certain characteristics Display all the attributes for a certain entity Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-34
  • 35. Types of Queries Different types of queries (continued): Find all entities with a certain characteristic List attributes for all entities for certain characteristics Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-35
  • 36. Query Notation  V is value, E is entity, A is attributes, variables in parentheses are given: Query type 1: V <--- (E,A) Query type 2: E <--- (V,A) Query type 3: A <--- (V,E) Query type 4: V <--- (E, all A) Query type 5: E <--- (V, all A) Query type 6: A <--- (V, all E) Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-36
  • 37. Methods for Implementing Queries There are two methods for implementing database queries: Query By Example (QBE), which allows users to select fields and specify conditions using a grid Structured Query Language (SQL), which uses a series of keywords and commands to select the rows and columns that should be displayed Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-37
  • 38. Parameter Queries A parameter query allows users to enter a value to select records without changing the query syntax Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-38
  • 39. Web Searches Web searches use search engines to answer a query Guidelines for searching the Web Decide whether to search or surf the Web Think of the key terms before searching Construct the search questions logically, with attention to the use of AND and OR search logic Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-39
  • 40. Web Searches Further guidelines for searching the Web are: Use a search engine that saves your searches Use a search engine that informs you of changes in the Web sites you select Look for new search engines periodically Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-40
  • 41. Data Mining Data mining is gathering a large amount of information about a person and their habits and using that information as a predictor of future behavior It must be carefully and ethically used to avoid infringing on an individual’s privacy Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-41
  • 42. Ergonomics Systems analysts should consider an ergonomically sound working environment even though they usually don't have much control over the design of the workspace Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-42
  • 43. Ergonomics Some of the important working environmental variables to be considered are Room color and lighting VDT or LCD screens User keyboards Computer desks User seating Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 18-43