Systems Analysis and Design

Chapter 8. User Interface Design

 Chapter 8 Outline

Principles of user interface

design.
User interface design process.
Navigation design.
Input design.
Output design.
 INTRODUCTION
Interface design is the process of
defining how the system will interact
with external entities.
Inthis chapter, we focus on the design of
user interfaces – how the system will
interact with the users.
The design of system interfaces defines
how the systems exchange information
with other systems.
(cont’d)
The user interface includes three fundamental parts:
- The Navigation mechanism - the way in which the
user tells the system what to do.
- The input mechanism – the way in which the
system captures information.
- The output mechanism - the way in which the system
provides information to the user or to other systems.
Graphical user interfaces (GUI) use windows, menus,
icons, etc., and are the most common type of user
interfaces.
 PRINCIPLES FOR USER INTERFACE
DESIGN
User interface design is an art.
Thegoal is to make the interface
pleasing to the eye and simple to
use, while minimizing the user’s
effort.
(cont’d)
 Layout
Layout refers to organizing areas of the screen and
document for different purposes and using these
The screen is often divided into three areas:
areas consistently throughout the user interface.

– The top area provides the user with ways to

navigate through the system;
– The middle and the largest area is for display of
user’s work; and
– The bottom area contains status information
about that the user is doing.
(cont’d)
The areas and information within areas should
have a natural intuitive flow to minimize
user’s movement from one area to the next.
Ideally, the areas will remain consistent in
– size,
– shape,
– placement for the forms, and
– reports used to present it.
(cont’d)
Webpage layout with multiple
navigation areas
(cont’d)
The flow between sections should also be consistent.
 Content Awareness
Content awareness refers to the ability of an
interface to make the user aware of the
information it contains.
All interfaces should have titles.
Menus should show where the user are and
where the user came from to get there.
All area should be clear and well defined.
Content awareness also applies to the fields and
field labels within each area, and the information
that a form or report contains.
 Aesthetics
Aesthetics refers to designing interfaces that
pleasing to the eye.
Interfaces need to be functional and inviting
to use.
In general, all forms and reports need a
certain amount of white space.
The design of text is also important.
– Fonts and font sizes
– Colors and patterns
(cont’d)
An example of form with high density
 User Experience
User experience refers to designing the user
interface with the users’ level of computer
experience in mind.
Novice users are concerned with easy of
learning.
Expert users are concerned with easy of use.
Often, the two objectives are complementary
and lead to similar design decisions, but
sometimes there are trade-offs.
 Consistency
Consistency usually refers to the interface within one
computer system, so that all parts of the same system
work in the same way. Ideally, however, the system
also should be consistent with other computer systems
in the organization.
Consistency enables users to predict what will happen,
Consistency occurs at many different levels.
and to reduce the amount of learning.
– Navigation controls;
– Terminology;
– Report and form design.
 Minimize User Effort
Minimizing user effort means using the
fewest possible mouse clicks or keystrokes
to move from one part of the system to
another.
Three-clicks rule
– Users should be able to go from the start or main
menu of a system to the information or action
they want in no more than three mouse clicks or
three keystrokes.
USER INTERFACE DESIGN PROCESS

User interface design is a five-step process

that is iterative.
 Use Scenario Development

Ause scenario is an outline of steps

that user s perform to accomplish
some part of their work.
Usescenarios are presented in a
simple narrative description that is
tied to the DFD.
(cont’d)
Examples of use scenarios
 Interface Structure Design
The interface structure design defines the basic
components of the interface and how they work
together to provide functionality to users.
An interface structure diagram (ISD) is used to show
how all screens, forms, and reports are related and
how the user moves from one to another.
An ISD is similar to a DFD in that it uses boxes and lines
to show the structure. However, unlike DFDs, there
are no commonly used rules or standards for ISDs.
The basic structure of the interface follows the basic
structure of the business process itself as defined in
the process mode©lC.opyright 2011 John Wiley & Sons, Inc. 9-20
(cont’d)
Interface Structure Diagram Example
 Interface Standards Design
The interface standards are the basic design
elements that are common across the individual
screens, forms, and reports within the system.
An interface metaphor is a concept from the real
world that is used as a model for the computer
system.
– E.g., Quicken uses a checkbook metaphor.
The interface template defines the general
appearance of all screens and the paper-based forms
and reports.
(cont’d)
The template specifies the names that the
interface will use for the major interface
objects, the fundamental building blocks of
the system.
The template gives names to the most
commonly used interface actions.
The interface objects and actions, and also
their status, may be represented by interface
icons.
 Interface Design Prototyping
Aninterface design prototype is a mock-
up or a simulation of a computer screen,
form, or report.
Common approaches to interface design
prototyping:
– Storyboards
– HTML prototypes
– Language prototypes.
 Storyboard
The storyboard shows hand-drawn pictures of
screens.
 HTML Prototype

AnHTML prototype is built with the

use of Web pages created in HTML
(hypertext mark-up language).
The designer uses HTML to create a
series of Web pages that show the
fundamental parts of the system.
 Language Prototype
A language prototype is an interface design
prototype built in the actual language or by the
actual that will be used to build the system.
An example of language prototype.
 Interface Evaluation
The objective of interface evaluation is to
understand how to improve the interface design.
There are four common approaches to interface
evaluation.
1. Heuristic evaluation - Compare the interface to a
checklist of design principles.
2. Walk-through evaluation - It is a meeting conducted
with the users to walk through the interface.
3. Interactive evaluation - Users try out the interface.
4. Formal usability testing - It is a formal testing
process to understand how usable the interface is.
 NAVIGATION DESIGN
Basic Principles
- Analysts usually must assume that users
have not read the manual, have not
attended training, and do not have
external help readily at hand.
- All controls should be clear and
understandable and placed in an
intuitive location on the screen.
(cont’d)
Prevent Mistakes - The first of principle of designing
navigation control is to prevent users from making
mistakes.
– Labeling commands appropriately and limiting
choices.
– Confirming with the user that the actions are difficult
Simplify
or impossible to undo.
Recovery from Mistakes – making “undo”

buttons whenever possible.

Use Consistent Grammar Order – Windows
application uses an object-action grammar order.
 Types of Navigation Control
There are three basic software approaches for
defining user commands:
- Languages: command language and natural
language.
- Menus: A menu presents the user with a list of
choices.
- Direct Manipulation: With direct manipulation,
the user enters commands by working directly
with interface objects.
Types of Menus
 Messages
Messages are the way in which the system
responds to a user and informs the user of
the status of the interaction.
Messages should be clear, concise, and
complete.
Allmessages should be grammatically
correct and free of jargon and
abbreviations (unless they are the users’
ones).
Avoid negatives and humor.
© Copyright 2011 John Wiley & Sons, Inc. 9-33
(cont’d)

Types of messages
 INPUT DESIGN

Input mechanisms facilitate the

entry of data into the computer
system.
Input design means designing the
screen used to enter information
and forms on which the users write
and type information.
 Basic Principles

Thegoal of input design is to capture

accurate information for the system
simply and easily.
 Use Online and Batch Processing
Appropriately
There are two general formats for entering inputs
into a computer system: online processing and
batch processing.
Online processing: each input item is entered
into the system immediately.
Batch processing: all the inputs collected over
some period are gathered together and entered
into the system at one time in a batch.
Batch processing simplifies data communications
and cuts communications costs.
 Capture Data at the Source

Themost important principle of

input design is to capture the data in
an electronic format at the original
source.
Itreduces duplication work, reduces,
processing time, decreases the cost,
decreases the probability of error.
(cont’d)
Source data automation refers to using special
hardware devices to automatically capture data
without requiring anyone to type it.
Source data automation technologies:
– bar code readers
– optical character recognition
– magnetic stripe readers
– smart cards
– RFID (radio frequency identification) tags
– the Web.
 Minimize Keystrokes
Keystrokes cost time and money.
The system should never ask for information
that can be obtained in another way (e.g., by
retrieving it from a database).
The system should not require a user to type
information that can be selected from a list.
The frequent values should be used as the
default value for the data.
 Types of Inputs
There are many different types of inputs, in the same way
that there are many different types of fields .
(cont’d)
There are many types of selection boxes
 Input Validation

Alldata entered into the system

must be validated in order to ensure
accuracy.
Input validation (also called edit
checks) can take many forms
(cont’d)

There are six different types of

validation checks:
 OUTPUT DESIGN

Outputs are the reports that the

system produces, whether on the
screen, on paper, or in other media,
such as the Web.
Outputs are the most visible part of
any system.
 Basic Principles
The goal of the output mechanism is to present
information to users so that they can accurately
Understand report usage – the first principle in
understand it with the least effort.
designing reports is to understand how they are
used.
Manage information load – the goal of a
well- designed report is to provide all needed
information without information overload.
Minimize bias – no analyst sets out to design a
biased report. © Copyright 2011 John Wiley & Sons, Inc. 9-46
(cont’d)
Example of bias: Bias in graphs.
Types of Outputs
 Media
Thetwo dominant media of reports are
paper and electronic.
Paper is the more traditional medium and
is relatively permanent, easy to use, highly
portable, and accessible in most situations.
However, paper reports are expensive.
Many organizations are moving to
electronic production of reports.
 SUMMARY
User interface design principles
- Layout, content awareness, aesthetics, user
experience, consistency, minimize user effort.
Theuser interface design process
- Use scenario development, interface structure
design, interface standards design, interface
design prototyping, and interface evaluation.
(cont’d)
Navigation design
- The fundamental goal of navigation design is to
make the system as simple to use as possible.
Input design
- The goal of input design is to simply and easily
capture accurate information for the system.
Output design
- The goal of the output design is to present
information to users so that they can accurately
understand it with the least effort.