Bài giảng Introduction to Software Engineering - Week 8: UI Design - Nguyễn Thị Minh Tuyền
Week 8:
UI Design
Nguyễn Thị Minh Tuyền
Adapted from slides of Ian Sommerville
Topics covered
1. Design issues
2. User interface design process
3. User analysis
4. User interface prototyping
5. Interface evaluation
2
Topics covered
1. Design issues
2. User interface design process
3. User analysis
4. User interface prototyping
5. Interface evaluation
3
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
p Can cause a user to make catastrophic errors.
p Is the reason why so many software systems are never
used.
4
Human factors in interface design
£ Limited short-term memory
p 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
p When people make mistakes and systems go wrong, inappropriate
alarms and md hence the likelihood
of more mistakes.
£ People are different
p People have a wide range of physical capabilities. Designers should
not just design for their own capabilities.
£ People have different interaction preferences
p Some like pictures, some like text.
5
UI design principles
£ UI design must take account of the needs,
experience and capabilities of the system users.
£ Designers should
p be aware of peoples physical and mental limitations
(e.g. limited short-term memory) and
p should recognise that people make mistakes.
£ UI design principles underlie interface designs
although not all principles are applicable to all
designs.
6
UI design principles
£ User familiarity
p The interface should use terms and concepts which are
drawn from the experience of the people who will make
most use of the system.
£ Consistency
p The interface should be consistent in that, wherever
possible, comparable operations should be activated in
the same way.
£ Minimal surprise
p Users should never be surprised by the behaviour of a
system.
7
UI design principles
£ Recoverability
p The interface should include mechanisms to allow users
to recover from errors.
£ User guidance
p The interfacful feedback when
errors occur and provide context-sensitive user help
facilities.
£ User diversity
p The interface should provide appropriate interaction
facilities for different types of system user.
8
Design issues in UIs
£ Two problems must be addressed in interactive
systems design
p How should the user interact with the computer
system?
p How should information from the computer system be
presented to the user?
9
Interaction styles
£ Direct manipulation
£ Menu selection
£ Form fill-in
£ Command language
£ Natural language
10
Interaction styles
Interaction
style
Main advantages
Main disadvantages
Application
examples
Direct
Fast and intuitive
May be hard to implement.
Only suitable where there is a
visual metaphor for tasks and
objects.
Video games
CAD systems
manipulation interaction
Easy to learn
Menu
selection
Avoids user error
Slow for experienced users.
Little typing required Can become complex if many
Most general-
purpose systems
Form fill-in
Simple data entry
Easy to learn
Checkable
Takes up a lot of screen space.
Causes problems where user
options do not match the form
fields.
Stock control,
Personal loan
processing
Command
language
Powerful and flexible Hard to learn.
Poor error management.
Operating systems,
Command and
control systems
Natural
Accessible to casual Requires more typing.
Information
language
users
Easily extended
Natural language understanding
systems are unreliable.
retrieval systems
11
Multiple user interfaces
12
Web-based interfaces
£ Many web-based systems have interfaces based
on web forms.
£ Form field can be menus, free text input, radio
buttons, etc.
13
Example: LIBSYS system
£ Users make a choice of where to search from a
menu and type the search phrase into a free text
field.
£ LIBSYS interaction
p Document e able to use the
search facilities to find the documents that they need.
p Document request: Users request that a document be
delivered to their machine or to a server for printing.
14
LIBSYS search form
15
Information presentation
£ Is concerned with presenting system
information to system users.
£ The information may be
p presented directly (e.g. text in a word processor)
p or transformed in some way for presentation (e.g. in
some graphical form).
£ The Model-View-Controller approach is a way of
supporting multiple presentations of data.
16
Information presentation
17
MVC model of user interaction
18
Information presentation
£ Static information
p Initialised at the beginning of a session. It does not
change during the session.
p May be either numeric or textual.
£ Dynamic information
p Changes during a session and the changes must be
communicated to the system user.
p May be either numeric or textual.
19
Information display factors
£ Is the user interested in precise information or
data relationships?
£ How quickly do information values change?
Must the change be indicated immediately?
£ Must the user take some action in response to
a change?
£ Is there a direct manipulation interface?
£ Is the information textual or numeric? Are relative
values important?
20
Tải về để xem bản đầy đủ
52 trang
18180
Free
Bạn đang xem 20 trang mẫu của tài liệu "Bài giảng Introduction to Software Engineering - Week 8: UI Design - Nguyễn Thị Minh Tuyền", để tải tài liệu gốc về máy hãy click vào nút Download ở trên
File đính kèm:
- bai_giang_introduction_to_software_engineering_week_8_ui_des.pdf
