/  27
 
 
Evaluation
ElectronicAttendanceSystem
JosephNgChowjoseph.ngchow@utoronto.caVictoriaMuivictoria.mui@utoronto.caBrianShimbrian.shim@utoronto.caVeronicaWongveve.wong@utoronto.ca
DAVEDEARMANCSC318–THEDESIGNOFINTERACTIVECOMPUTATIONALMEDIANOVEMBER26,2008
 
Page 2
Table of Contents
EVALUATION TECHNIQUES
3
C
OGNITIVE
W
ALKTHROUGH
3
U
SABILITY
T
ESTS
4
H
EURISTIC
E
VALUATION
6
P
ARTICIPANTS
7
RATIONALE
7
C
HOICE OF
P
ARTICIPANTS
7
C
HOICE OF
T
ECHNIQUES
 /T
ASKS
7
C
HOICE OF
M
ATERIALS
9
EVALUATION DATA AND RESULTS
9
C
OGNITIVE
W
ALKTHROUGH
R
ESULTS
9
Q
UALITATIVE
D
ATA
9
U
SABILITY
T
EST
R
ESULTS
10
Q
UALITATIVE
D
ATA
10Q
UANTITATIVE
D
ATA
11
H
EURISTIC
E
VALUATIONS
R
ESULTS
11
Q
UALITATIVE
D
ATA
11Q
UANTITATIVE
D
ATA
12
E
RROR
-S
TEP
T
EST
12
DATA ANALYSIS AND DISCUSSION
15
C
OGNITIVE
W
ALKTHROUGH
15
U
SABILITY
T
EST
16
H
EURISTIC
E
VALUATION
19
E
RROR
-S
TEP
T
EST
 
22
 
DESIGN IMPLICATIONS AND IMPROVEMENTS
23
CRITIQUE OF EVALUATION PLAN
25
K
NOWING WHAT WE KNOW NOW
,
WHAT WOULD WE HAVE DONE DIFFERENTLY
?
25
W
HAT WOULD WE HAVE DONE IF WE HAD MORE RESOURCES
?
26
 
Page 3
Evaluation Techniques
The objectives of our evaluation are to learn:
 
Whether or not the design requirements were met, and
 
How well the prototype met the expectations of the design requirements.To answer these questions, we used usability tests, cognitive walkthroughs, and heuristicevaluation techniques.We performed 2 separate sets of tests on our participants; usability tests for the end users, andcognitive walkthroughs
 
and heuristic evaluations for the HCI
 
experts. To ensure that the resultsof one test would not influence the results of the other, our second group of participants eitherdid a cognitive walkthrough
 
or a heuristic evaluation. Although tests were divided, we felt thatobserving the number of errors and testing the result was both important and generic enoughthat it needed to be applied to both user groups. This will be discussed later in the Evaluationof Results section.
Cognitive Walkthrough
Input
Interaction Task:
The high-level interaction task was “taking the attendance”. Since this waswhat the system was designed to do, it was the primary task that potential users performed.
 
Action Sequence:
0. Take the attendance1. Log in with employee number and PIN1.1. Use the stylus to activate the employee number input field1.2. Input given employee number1.2.1 Tap the numbers on the number pad with the stylus1.3. Tap the numbers on the number pad with the style for PIN1.4. Hit enter with the stylus2. Mark each student in the class, present, absent, or late2.1. Call out the student’s name2.2. Tap the bubble next to each student’s name that corresponds to theirattendance status2.3. Repeat 2.1-2.2. for each student on the class list

Share & Embed

More from this user

Add a Comment

Characters: ...