4 RESULTS
In this section we analyze the collected data in terms
of individual tasks. All participants completed
successfully (even if they faced some problems) the
Camera and Contacts scenarios, while only 36% of
users came across difficulties and didn’t manage to
complete the Clock scenario. Some users (14% and
18% respectively) also failed to complete the
Calendar and Safari scenarios but their number is
not as high as the number of those who failed the
Clock scenario.
Figure 2 shows the average time per scenario.
Although the Clock scenario had the smallest
success rate, its average completion time was low
due to the fact that many candidates quit the scenario
when they had difficulties. Unlike difficulties of
type b, the difficulties of type a did not affect the
success rates but both types of difficulties imposed a
penalty to the completion time in Figure 2. Type c
problems did not affect the success rates but in this
case also a penalty has been imposed to the
completion time. From a usability perspective, type
c problems may not have the severity of type b but
reside to a tricky ‘grey area’ of usability problems
that usually remain undiscovered and thus
unresolved.
A thorough examination of the videos led to the
identification of the most frequent mistakes made by
users in each scenario with the results summarized
in Table 2. In an effort to categorize the severity of
difficulties recorded, one ends up with three such
types: (a) the difficulties users managed to
overcome, (b) the difficulties users failed to
overcome, and (c) the errors they made but did not
realize making.
Figure 2: Average time per scenario.
Specifically, even though 13.6% of users didn’t
edit correctly a contact at their first attempt and
22.7% didn’t delete the contact correctly, all users
finally completed the Contacts scenario. On the
contrary, the difficulties users came across in the
Clock scenario resulted in 36% failure. This is due
to the fact that many users (22.7%) couldn’t edit the
alarm, as they were clicking on the alarm they
wanted to edit and finally gave up. In this failure rate
also contributed the 18.1% of the users who didn’t
delete the alarm but deactivated it without realizing
the difference. The same happened in the Camera
scenario where 22.7%
of the users took more than
one picture without realizing it.
The difficulties users had in the Calendar
scenario didn’t significantly affect its successful
completion but users considered this scenario to be
difficult (Figure 3). In the Safari scenario, 31.8%
was very confused with the bookmarks button
resulting in an 18% failure percentage.
Table 2: Frequency of errors observed.
Contacts Freq.
To edit a contact they tapped on the contact 13.6%
To delete a contact they deleted the contact
name using the keyboard
22.7%
Alarm setting (Clock) Freq.
To edit an alarm they tapped on the alarm 22.7%
They didn’t delete the alarm, they deactivated
it
18.1%
Photo taking (Camera) Freq.
They took more than one picture without
realizing it
22.7%
Task setting (Calendar) Freq.
They didn’t use the month view 18.1%
To set the hour they clicked on the hour
option instead of using the spinning dials
13.6%
They didn’t add a second appointment but
edited the existing one
13.6%
Web browsing (Safari) Freq.
They didn’t open an additional webpage but
edited the address field of the existing one
18.1%
They had difficulties with the bookmarks
button (did not find it easily)
31.8%
Returning to the numbered list of potential
usability issues recorded prior to this study (in
section 2), it is important to notice that they were all
confirmed. More specifically, issue no. 1 has been
confirmed by the 6.7% of users (even though all
managed to locate the non-physical button), issue
no. 2 by 10% of users, issue no. 3 by the 22.7% of
users, issue no. 4 by 8.3%, issue no. 5 by 18.3%,
issue no. 6 by 20%, issue no. 7 by 31.8% and issue
no. 8 by 22.7% for the Contacts application and by
0.00
50.00
100.00
150.00
200.00
250.00
300.00
averagetime(sec)
ICEIS2012-14thInternationalConferenceonEnterpriseInformationSystems
114