Posts Tagged ‘可用性’

可用性维度的5个E

November 11th, 2008

Whitney Quesenbery用5个E开头的单词来描述可用性的5个维度,分别是:

  • Effective
  • Efficient
  • Engaging
  • Error Tolerant
  • Easy to Learn

Effective指的是效力。如果一个系统或者设备无法让用户完成他想要做的工作,无论任务难易或者所花费时间的长短,那么这个系统的效力是很低的。如果我们想测量系统的效力,需要先定义什么是成功的完成一个任务,不管是直接或者曲折的。

Efficient指的是效率,这个很容易理解。完成任务的时间是衡量效率的主要指标。

Egaging指的是满意程度,包含了这个界面在多大程度上吸引用户去使用,以及使用中的愉悦感觉,当然还有使用后的满意程度。

Error Tolerant指的是系统防止错误以及从错误中恢复的能力。

Easy to learn指的是可学性。某些系统的使用的频率很低,用户可能隔很久才会再用一次。怎么保证用户事隔很久之后还能很容易的再次使用这个系统呢?可学性是一个重要的指标。

____________________________________________________________________

Effective

The completeness and accuracy with which users achieve their goals.

Effective is the first E. If a user cannot actually do the thing he or she set out to do, it

probably doesn’t matter whether the experience was short or long, easy or hard. In the end,

they have failed to complete their tasks or meet their goals. If we want to be able to

measure effectiveness, we have to know how people define success or usefulness, whether this is

relatively straight forward or more subtle.

Efficient

The speed (with accuracy) with which this work can be done.

Efficiency may be something that is carefully defined, for example in a call center where

operators are measured on the number of calls they can handle in a day. It may be a

subjective judgement of when a task is taking “too long” or “too many clicks.”

Engaging

How pleasant, satisfying or interesting an interface is to use

“Engaging” replaces “satisfaction,” looking for a word that suggests the ways that the

interface can draw someone into a site or a task. It also looks at the quality of the

interaction, or how well the user can connect with the way the product is presented and

organized.

Error Tolerant

How well the product prevents errors, and helps the user recover from any that do

occur

It would be lovely to say “error free” or “prevents errors” but mistakes and accidents and

misunderstandings will happen. The cat nudges the mouse as you click. You misread a link

and need to find your way back, or enter a number with a typo. The real test is how helpful

the interface is when an error does occur.

Easy to Learn

How well the product supports both initial orientation and deeper learning

A product may be used just once, once in a while, or on a daily basis. It may support a task

that is easy or complex; and the user may be an expert or a novice in this task. But every

time it is used the interface must be remembered or relearned, and new areas of the

product may be explored over time.

利用最新的Morae3做手持设备的Usability Test

October 25th, 2008

手持设备的可用性测试:Morae 3

1.典型的设置,用你的DV作为主摄像头,Webcamera可以作为拍摄脸部的摄像头;这样就可以用最新的Morae 3来进行手持设备或者纸上原型等类型的可用性测试。

Morae setup1

2.看索尼爱立信是怎么做可用性测试的:手机上有一个可调节的摄像头,这样可以保持无论用户以什么方式去拿手机,摄像头传送的画面都是清晰的。桌子上的网络摄像头当然就是方便你看清用户的表情的啦:-)

Morae setup2

3. 如果你要在电脑上做使用flash或者java等程序做的原型测试,当然就是再容易不过了。只需要一个普通的网络摄像头就可以了。

Morae setup3
Technorati 标签: Morae 3,Usability Test

系统可用性量表SUS的使用

October 24th, 2008

SUS(Syestem Usability Scale)用来测量系统的可用性,并给出一个用百分制来计算的分数,超过60分被认为是good usability。我自己常使用SUS来测量某个application,某个网站或者设备,系统的可用性,尤其在竞争对手分析(competitive analysis)的时候,SUS的最终数据的差异和实际使用中用户感受到的差异是很一致的。这也说明SUS具有很高的效度。
那怎么使用SUS呢?先看看下边的英文吧,一个印度人写的他是怎么样用SUS的:(如果你用著名的Techsmith Morae的话,你就会知道,SUS是Morae 3里默认的后测量表)

SUS questionnaire

SUS questionnaire (Brooke, Digital Equipment Corporation, 1996)

SUS questionnaire consists of 10 questions that are evaluated using a Likert scale ranging from 1 for ‘Strongly Disagree’ to 5 for ‘Strongly Agree’.

Q1. I think I would like to use this system frequently.
Q2. I found the system unnecessarily complex.
Q3. I thought the system was easy to use.
Q4. I think that I would need the support of a technical person to be able to use this system.
Q5. I found the various functions in this system were well integrated.
Q6. I thought there was too much inconsistency in this system.
Q7. I would imagine that most people would learn to use this system very quickly.
Q8. I found the system very cumbersome to use.
Q9. I felt very confident using the system.
Q10. I need to learn a lot of things before I could get going with this system.

Scoring the SUS

SUS scores have a range of 0 to 100. To calculate the SUS score, first sum the score contributions from each item. Each item’s score contribution will range from 0 to 4. For items 1, 3, 5, 7 and 9 the score contribution is the scale position minus 1, e.g. position 2 will equal ‘2-1’ a score of 1.

For items 2, 4, 6, 8 and 10, the contribution is 5 minus the scale position, e.g. position 2 will equal ‘5-2’ a score of 3.

Multiply the sum of the scores by 2.5 to obtain the overall value of SUS. A score of around 60 and above is generally considered as an indicator of good usability.

SUS has been made freely available for use in usability assessment, and has been used for a variety of research projects and industrial evaluations; the only prerequisite for its use is that any published report should acknowledge the source of the measure.

Method

The method employed to administer the test was to make available the test online. The users were invited to participate in the survey, where they evaluated the questions and rated them as they found appropriate.  The survey was administered pre-deployment to measure and benchmark as-is version and then post deployment after the user had the opportunity to use the new system for some time. This enabled the comparison between two versions of the same application. It also provided score to compare between different applications and determine the usability score of a particular application in comparison to others.

Initially it was supposed to be just these 10 questions to gather the score, but it as found that the Product Managers were not comfortable with just the scores as they wanted to know the reason for low/ high scores. Before the introduction of SUS there was no such measure against which the applications were compared, though they did go through a final usability testing. But there was no number to compare different applications and determine how usable the applications were on a scale. Hence there was some resistance initially, and to make the product managers more comfortable three open ended questions were added to the questionnaire. The questions were “What I dislike about the application, what I like about the application, and what I would like to have”. These required user comments, and subjective qualitative data were collected through these questions. While they did provide valuable input, these questions did not form part of the final SUS score which was dependent on the original 10 SUS questions. One important function that these added questions performed was to give insight into what may be wrong with applications that had low SUS score. These also made the Product Managers more comfortable with the score as they could identify with the issues instead of merely being provided with a number.


更多:计算机系统的可用性问卷