Chapter 8 (Updated) User Interface Design

CHAPTER 8: USER
INTERFACE DESIGN
KP24103 SYSTEM
ANALYSIS AND DESIGN
OBJECTIVE
Explain the concept of user interface
design and human-computer
interaction.
Explain how experienced interface
designers perform their tasks.
Describe rules for successful
interface design.
Discuss input and output technology
issues.
INTRODUCTION
The goal of system design is to build a
system that is:
Effective:
supports
business
requirement and meets user needs.
Reliable:
handles
input
errors,
processing errors, hardware failures
or human mistakes.
Maintainable: flexible, scalable, and
easily modified.
USER INTERFACE DESIGN

User interface describes how user
interact with a computer system and
consists of all hardware, software,
screens, menus, functions, output,
and features that affect two-way
communications between the user
and the computer
HUMAN-COMPUTER INTERACTION
A user interface is based on basic

principles
of
human-computer
interaction.
Human-computer
interaction
describes the relationship between
computers and people who use them
to perform their jobs.
SEVEN HABITS OF SUCCESSFUL

INTERFACE DESIGNERS
1.
2.
3.
4.
5.
6.
7.
Understand the business

Maximize graphical effectiveness
Think like a user
Use models and prototypes
Focus on usability
Invite feedback
Document everything
Understand the business

Understand the underlying business
functions and how the system
supports.
Understand how the system supports
individual,
departmental,
and
enterprise goals.
So that they can design an interface
that helps users to perform their
jobs.
2. MAXIMIZE GRAPHICAL
EFFECTIVENESS
A well-designed interface can help
users learn a new system rapidly and
be more productive.
In graphical environment, a user can
display and work with multiple
windows on a single screen and
transfer data between programs.
3. THINK LIKE A USER

A system analysts should understand
user experience, knowledge and skill
levels.
The interface should be flexible
enough to accommodate novices as
well a experienced users.
4. USE MODELS AND

PROTOTYPES
Construct models and prototypes for
users approval.
To gain as much feedbacks as
possible, as early as possible.
5. FOCUS ON USABILITY
The user interface should include all
tasks,
commands,
and
communications between users and
the information system.
Offer a reasonable number of choices
that a user easily can comprehend.
6. INVITE FEEDBACK
To determine if system features are
being used as intended by observing
and surveying users.
DOCUMENT EVERYTHING
For later use by programmers.
User-approved
sketches
and
storyboards also can be used to
document the user interface.
RULES FOR USER INTERFACE

DESIGN
1. Create an interface that is easy to learn
and use
2. Enhance user productivity
3. Provide users with help and feedback
4. Create an attractive layout and design
5. Enhance the interface
6. Focus on data entry screens
7. Use validation rules
8. Reduce input volume
SOURCE DOCUMENT AND FORM

DESIGN
A source document collects input
data, triggers or authorizes an input
action, and provides a record of the
original transaction.
Form layout
1. Heading zone: contains company name or
logo.
2. Instruction zone: contains instruction for
completing the form.
3. Body zone: takes up at least half of the
space on the form and contain captions and
areas for entering variable data.
4. Totals zone: if totals are included on the form
5. Authorization zone: contains any required
signatures
REPORT DESIGN (PRINTED OUTPUT)

Types of report:
a) Detail reports
Produces one or more lines of output for
each record processed.
b) Exception reports
Displays only those records that meet a
specific condition or conditions
c) Summary reports
Suitable for upper-level managers , eg:
total figures without supporting details
TECHNOLOGY ISSUES
Most technology advances today
affect both output and input.
Eg:
New
touch
screen
input
technology generates output that
must be properly deigned and sized
for a particular device which might
be smart phone etc.
Output Technology
Internet-based information delivery: Online
catalog on a website
Email
Blogs
Instant messaging
Wireless devices: tablet computers,
smartphones.
Digital audio, images, videos
Podcasts: a specially formatted digital audio
file that can be downloaded by Internet users
Input Technology
Batch input: data entry usually is
performed on a specified time
schedule, such as daily, weekly,
monthly.
Online
input:
Source
data
automation, which combines online
data entry and automated data
capture using input devices such as
RFID tags or magnetic data strips.
SECURITY AND CONTROL

ISSUES
Output security and control
Every report should include report
number or code.
Printing date and time period.
Limit the number of printed copies.
Sensitive reports should be stored in
secure areas
SECURITY AND CONTROL

ISSUES
Input security and control
Provide audit trail that records the source of
each data item and when it entered the system.
Must have procedures for handling source
documents to ensure that data is not lost before
it enters the system
Once data is entered, company should store
source documents in a safe location.
System sign-on procedures should prevent
unauthorized individuals from entering the
system.
MODULAR DESIGN
Modules (individual components) are
created which connect to a higher-level
program or process.
Each module represent a specific process.
Try to design modules that perform a
single function.
Independent modules provide greater
flexibility because they can be developed
and tested individually.
PROTOTYPING
System prototyping
Produces a full-featured, working model of the
information system.
It is especially important to obtain user feedback,
and to be sure that the prototype meets all
requirements of users and managers.
Design prototyping
A user-approved model that documents and
benchmarks the features of the finished system.
To capture user input and approval while continuing
to develop the system within the framework of SDLC
BENEFITS OF PROTOTYPING
Avoid misunderstandings between users and
systems
Developers can create accurate specifications
for finished system
Managers can evaluate a working model
System analysts can use a prototype to develop
testing and training procedures before finished
system available
Reduces the risk and potential financial exposure
when finished system fails to support business
needs.
POTENTIAL PROBLEM OF A
PROTOTYPING
May create quality problem (rapid
pace)
System requirement like reliability
and maintainability cannot be tested
adequately.
In a complex system, prototype can
become difficult to manage.
THE END

Chapter 8 (Updated) User Interface Design

Uploaded by

Copyright:

Available Formats

Chapter 8 (Updated) User Interface Design

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter 8 (Updated) User Interface Design

Uploaded by

Copyright:

Available Formats

CHAPTER 8: USER

USER INTERFACE DESIGN

A user interface is based on basic

SEVEN HABITS OF SUCCESSFUL

Understand the business

Understand the business

3. THINK LIKE A USER

4. USE MODELS AND

RULES FOR USER INTERFACE

SOURCE DOCUMENT AND FORM

REPORT DESIGN (PRINTED OUTPUT)

SECURITY AND CONTROL

SECURITY AND CONTROL

You might also like