Scribd
Upload
5 views

Principles of User Interface Design

Uploaded by

Michael Sinkamba
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
5 views

Principles of User Interface Design

Uploaded by

Michael Sinkamba
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

ICT 382

PRINCIPLES OF INTERFACE DESIGN


INTRODUCTION

 A user interface is the point of human interaction and communication in


devices. It can include display screens, keyboards ,a mouse and the
appearance of a desktop.
 A user interface should be built in such a way that the user must focus on
the task they are performing and not the interface.
 An interface must be invisible this means that, the user will not spend time
on learning the interface, but will utilise the interface to perform the task at
hand.
*As a web /software developer always keep in mind that the system you’re
developing is for users and hence should heavily focus on the user’s needs.
PRINCIPLES

 PRINCIPLE OF SIMPLICITY
This principle highlights the fact that the user interface should be easy to
understand and easy to use from the user’s perspective.
The various categories of users are: novice, intermittent and expert users.
Novice : Refers to someone that just started using computer systems.
Intermittent : Refers to a user that occasionally uses computer systems.
Expert :Refers to users that are well acquainted to computer systems and have
no problems navigating them.
The principle of simplicity ensures that the interface must be easy for a user of
each category to understand.
 PRINCIPLE OF DISCOVERABILITY
This principle entails that the functions should be visible on the interface for the user .
Especially these functions that are very critical to the user.
 PRINCIPLE OF MAPPING
The system should speak the user’s language with words, phrases and concepts that are
familiar to the user rather than system oriented terms .
 PRINCIPLE OF CONSISTENCY
This principle has to do with maintaining uniform formats across the application ,such as the
colour , buttons etc.
Users must not wonder whether words ,situations or actions mean the same .
There are two types of consistency
• External and Internal consistency.
External Consistency refers to uniformity with that which has been accepted as the norm
by humanity.
Internal Consistency refers to consistency in format within the application.
 PRINCIPLE OF PERCEPTIBILITY
This principle entails that the system must always keep the users informed about about its
state that is alert the user on their work progress e.g How Microsoft word uses an asterick
to let you know that your work needs to be saved.
 PRINCIPLE OF FLEXIBILTY
The system must be able to cater for both well experienced users and the inexperienced
users. All of them must be able to navigate the system without great difficulty.
 PRINCIPLE OF EQUITY
The system should be designed in such a way that people with diverse abilities
(disabilities) should be able to use it too. It should cater for both able and differently
abled individuals .
It must avoid stigmatization and segregation at all costs.
 PRINCIPLE OF EASE AND COMFORT
Ensure that the design of the system is such that it can (should) be used efficiently and
comfortably. An Example of this can be the size of buttons across the system.
 PRINCIPLE OF STRUCTURE
The design of your system should be organized purposefully and meaningfully using
consistent models .
And most importantly all related models should be grouped together.
 PRINCIPLE OF TOLERANCE
Implies that the design of your system should reduce mistakes as much as possible as
well as misuse thereby must allow the users allowing users to redo and undo.
This also includes placement of controls on the interface.
 PRINCIPLE OF CONSTRAINTS.
The design as much as possible should constrain users to only perform the correct
actions. It should limit on the number of possibilities that users have as regards to
usage of the system.
There should be constraints to avoid errors.The system must always have messages
that are meaningful when handling the constraints.
 PRINCIPLE OF FEEDBACK
The system should be designed in such a way that it provides meaningful feedback
to the user which should be
• Immediate
• Informative
Feedback which is not informative is the same as having no feedback at all;
The messages must be in plain language so that users know exactly what action to
take.
 PRINCIPLE OF DOCUMENTATION.
It is necessary to provide help and documentation such as in the form of a
help menu.
This documentation should be easy to search and must focus on the users task.

You might also like