EVALUAT IONI N T E R A K S I M A N U S I A - K O M P U T E R 2 0 1 5

namun sebelumnya ….

Quiz: Visualisasi Jadwal Penerbangan Jakarta - Sorong

Perhitungkan perbedaan waktu antar kota, lama penerbangan, transit, stop over. Jam Berangkat dan Datang sesuai dengan wilayah waktu kota tersebut (WIB/WITA/WIT) GA : Garuda IndonesiaQZ : AirAsia

Jakarta7 8 9 10 11 14

QZ121

GA083QZ151

Denpasar

Makassar

Sorong

13 12 16

8 9 10 11 14 13 12 15

8 9 10 11 14 13 12 15

9 10 11 14 13 12 15 16 17

1716

GA080

15

16 17

18

jangan lupa THT 1405

E VA L U AT I O N V S

[ U S E R ] T E S T I N G

E VA L U AT I O N PA R A D I G M

Any kind of evaluation is guided explicitly or implicitly by a set of beliefs, which are often under-pined by theory. These beliefs and the methods associated with them are known as an ‘evaluation paradigm’

Preece  2005

U S E R S T U D I E S / T E S T I N G

involve looking at how people behave in their natural environments, or in the laboratory, both with old technologies and with new ones. Preece  2005

R E F E R E N S IGalitz (2005). The Essential Guide

to User Interface DesignStep 14: test, test, and retest

E VA L U AT I O N M E T H O D S

• Expert Review

• Guidelines & Standards Review

• Heuristic Evaluation

G U I D E L I N E S & S TA N D A R D S R E V I E Worganization’s standards, design guidelines, style guide, government standard

[+]

can be performed by developers, low cost, can identify general & recurring problems, perticularly useful for identifying screen design and layout problems

[-]

may miss severe conceptual, navigation, & operational problems

H E U R I S T I C E VA L U AT I O N

TA K E H O M E T E S T 2

• melakukan Heuristic Evaluation terhadap sebuah software/mobile apps/situs web.

• s/d tgl 14/05/2015 pukul 23:55 usulkan 3 software/mobile apps/situs web via link di LMS

• pilihan akan diumumkan pada 18/05/2015

• deadline 31/05/2015 -09:45

H E U R I S T I C E VA L U AT I O N

Heuristic evaluation involves having a small set of evaluators examine the interface and judge its compliance with recognized usability principles

(the "heuristics")

H E U R I S T I C E VA L U AT I O N

[+]

easy to do,

relatively low cost,

does not waste user’s time,

can identify many problems

H E U R I S T I C E VA L U AT I O N

[-]

evaluators must possess interface design expertise

evaluators may not possess an adequate understanding of the

task and user communities

diifficult to identify systemwide structural problems

difficult to uncover missing exits and interface elements

difficult to identify the most important problems among all problems uncovered

does not provide any systematic way to generate solutions to the problems uncovered

H E U R I S T I C E VA L U AT I O N

[GUIDELINES]

use 3-5 expert evaluators

choose knowledgeable people:

familiar with project situation

possessing a long-term relationship with the organization

Saul Greenberg

Problems found by a single inspector

Evaluators miss both easy and hard problems

– ‘best’ evaluators can miss easy problems

– ‘worse’ evaluators can discover hard problems

19

Saul Greenberg

Problems found by multiple evaluators

3-5 evaluators find 66-75% of usability problems

– different people find different usability problems – only modest overlap between the sets of problems found

20

Saul Greenberg

Problems found by multiple evaluators

Where is the best cost/benefit?

21

H E U R I S T I C E VA L U AT I O N

• Nielsen (10)

• Norman (4)

• Tognazzini (16)

• Shneiderman (8)

• Gerhardt-Powals (10)

• Levi-Conrad (9)

H E U R I S T I C E VA L U AT I O NN I E L S E N 1 9 9 4

V I S I B I L I T Y O F S Y S T E M S TAT U S

The system should always keep users informed about what is going on, through appropriate feedback within reasonable

time.

M AT C H B E T W E E N S Y S T E M A N D T H E R E A L W O R L D

The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-

oriented terms. Follow real-world conventions, making information appear in a natural and logical order.

U S E R C O N T R O L A N D F R E E D O M

Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support

undo and redo.

C O N S I S T E N C Y A N D S TA N D A R D S

Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform

conventions

E R R O R P R E V E N T I O N

Even better than good error messages is a careful designwhich prevents a problem from occurring in the first place.

Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit

to the action.

R E C O G N I T I O N R AT H E R T H A N R E C A L L

Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to

another. Instructions for use of the system should be visible or easily retrievable whenever appropriate

F L E X I B I L I T Y A N D E F F I C I E N C Y O F U S E

Accelerators -- unseen by the novice user may often speed up the interaction for the expert user such

that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.

A E S T H E T I C A N D M I N I M A L I S T D E S I G N

Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue

competes with the relevant units of information and diminishes their relative visibility.

H E L P U S E R S R E C O G N I Z E , D I A G N O S E , A N D R E C O V E R F R O M E R R O R S

Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively

suggest a solution.

H E L P A N D D O C U M E N TAT I O N

Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to

search, focused on the user's task, list concrete steps to be carried out, and not be too large.

S E V E R I T Y R AT I N G