Cognitive Walk Through

7/23/2019 Cognitive Walk Through

1/33

Evaluating Designs & Interfaces:Cognitive Walkthrough


2/33

Based on

The Cognitive Walkthrough: A Practitioners Guide

by C. Wharton, J. Rieman, C. Lewis, and P. Polson, U. ofColorado, Boulder

Lecture Overview: Cognitive Walkthrough


3/33

Traditional requirements analysis looks at abstrat

and !artial task elements.

Task"entered desi#n fouses on real, om!lete,

and re!resentati$e tasks.

Cognitive walkthrough is a task"entered

e$aluation

Task-centered Design


4/33

%uestion assum!tions about what the users will be

thinkin#

&dentify ontrols that may be missin# or hard to find

'ote inadequate feedbak

(u##est diffiulties with labels and !rom!ts

Whats it good for!


5/33

)ous most learly on !roblems that users will ha$e

when they first use an interfae, without trainin#

'ot a tehnique for e$aluatin# the system o$er time

*e.#., how quikly a user mo$es from be#inner to

intermediate+

ost effeti$e if desi#ners an really reate a mental

!iture of the atual en$ironment of use

Cognitive Walkthrough "ur#ose


6/33

Prior to doin# a walkthrou#h, you need four thin#s-

. / desri!tion or a !rototy!e of the interfae

0. / task desri!tion for a re!resentati$e task

1. / om!lete, written list of the ations needed to

om!lete the task

2. /n idea of who the users will be and what kind of

e3!eriene they4ll brin# to the 5ob

"re#aration


7/33

. 6efine in!uts

0. 7et analysts

1. (te! throu#h ation sequenes for eah task

2. Reord im!ortant information8. Re$ise U&

$te#s in a Cognitive Walkthrough


8/33

Who are the users9

What are the tasks9

What are the ation sequenes for the tasks9

6esri!tion:!rototy!e:im!lementation of the U&

%irst ste#: define in#uts


9/33

;ou don


10/33

Will users know what to do9

Will users see how to do it9

Will users understand from the feedbak whether their

ations are orret or not9

Third ste#: ste# through actions


11/33

User knowled#e *!rior to and after ation+

/ssum!tions about users

(ide issues = desi#n han#es

Credible suess or failure story "" why user would or

would not select correct action

%ourth ste#: 'ecord i(#ortant infor(ation


12/33

)ailure to try to #et the ri#ht effet

eliminate that ation

!rom!t user for ation

han#e other !art so user knows that s*he+ an try the ation

User does not know orret ation is a$ailable

make ation more ob$ious

%ifth ste#: revise the )I


13/33

User does not know orret ation is the orret one label ontrols based on knowled#e of users

User ant tell thin#s are #oin# ok#i$e feedbak, any feedbak>

if !ossible, say what ha!!ened

%ifth ste#: revise the )I *cont+,


14/33

Want to reate a sim!le UL dia#ram-

Representative Task

E./"LE

0oal: Create )/L diagra( in DI.


15/33

. Put in UL mode

0. /dd !arent lass *(tudent+

/. (elet lass tool

B. 6raw lass onto an$as by likin#

C. Chan#e lass name

1. /dd name as !ri$ate (trin#

/. Brin# u! dialo#, lik on /ttribute tab

B. Clik 'ew

C. ?nter name

6. Chan#e $isibility to Pri$ate

?. Clik @A

$te#s


16/33

2. /dd !ubli method addCourse *(trin# !arameter+

/. Clik on @!erations tab

B. Press 'ew

C. ?nter method name

6. Clik 'ew !arameter

?. ?nter !arameter name *ourse+

). ?nter !arameter ty!e *(trin#+

$te#s1 continued


17/33

8. /dd C(a5or and atha5or as hildren

/. Create C(a5or and atha5or lasses, as abo$e

B. Line them u! on the an$as

C. (elet 7eneraliation tool

6. 6ra# mouse from !arent lass to one hild

?. Use i#a#line to onnet to seond hild

$te#s1 continued


18/33

(reen omes u! in database mode

&


19/33

'ow the UL menu is a$ailable.

&


20/33

'ow &


21/33

'ow &


22/33

'ow &


23/33

'ow &


24/33

'ow my attribute is listed, but it has a H

&


25/33

'ow my attribute is listed, but it has a H

& want to add a method. & know now tolook at the tabs. ethods is not there,

but @!erations is. (reen o!eration is

similar to /ttributes, so & immediately

!ress 'ew. & then enter the method

'ame. & !ress 'ew under !arameters. &enter the 'ame and Ty!e.

Reommend-

& would mo$e buttons to left *as with

su##estion for /ttributes+. Rest

seems !retty intuiti$e.

$te# 7: .dd #u4lic (ethod addCourse

$te#s 7. 8 7E


26/33

'ow & ha$e a fully defined !arent lass

&


27/33

'ow & ha$e 1 lasses&


28/33

'ow & ha$e 1 lasses lined u!

&


29/33

'ow & ha$e 1 lasses and ha$e seleted inheritane

tool &


30/33

'ow & ha$e 1 lasses and one inheritane relationshi!

&


31/33

/ssesses learna4ilit *ease of learnin#+ of a user

interfae

&dentifies s#ecific #ro4le(s with desi#n

'o need for users to #et in$ol$ed

Cognitive Walkthrough $u((ar


32/33

(e$ere !roblems- om!arable with other tehniques

Content"related !roblems

Consisteny- om!arable with other tehniques

Reurrene- worse than Deuritis or Usability Testin#

(o!e- finds (ore s#ecific #ro4le(s rather than#eneral ones

What #ro4le(s cognitive walkthrough finds


33/33

;ou will e$aluate

. ;our #rou!

Cognitive Walk Through

Documents

Transcript of Cognitive Walk Through