This is the most up to date version of this scale.

Construct Summary

The author define usability as:

“the usability of any tool or system has to be viewed in terms of the context in which it is used, and its appropriateness to that context.” (p. 2)

and claim that it should cover:

“effectiveness ( the ability of users to complete tasks using the system, and the quality of the output of those tasks), efficiency ( the level of resource consumed in performing tasks, and satisfaction (users’ subjective reactions to using the system)” (p. 3)

Rating = 23%

Check? Guideline Item
Is the construct defined?
Does the final version of the items capture the construct as it has been defined by the authors?
Is the item generation process discussed (e.g., literature review, Delphi method, crowd-sourcing)?
Person to items 10:1 for the initial set of items?
Did they perform an EFA, PCA, Rasch, or similar test to determine the item to factor relationship?
Did they describe how they determined number of factors?
Did they report the full initial set of items?
Did they provide loadings (EFA) or item fits (Rasch) of all items?
Is there a description of the item removal process (e.g., using infit/outfit, factor loading minimum value, or cross-loading values)?
Did they list the final items included in the scale?
Did they include a factor structure test (e.g., second EFA, CFA, DIF, test for unidimensionality when using Rasch, or similar)?
Was a measure of reliability (e.g., Cronbach’s alpha, McDonalds Omega_h or Omega_t, Tarkkonen’s Rho) reported?
Was a test of validity (e.g., predictive, concurrent, convergent, discriminant) reported?

Comments None.

Reviewed by Experts ✓

Downloads

PAPER
Brooke, J. (1996). SUS-A quick and dirty usability scale. Usability evaluation in industry, 189(194), 4-7.


PDF of scale as well as instructions for administration and scoring are located in the PDF version of the paper at the link above.

Final Scale Items (10 total):

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