| | 83 | Contents of the documents, explanations and links: |
| | 84 | * User related: |
| | 85 | * What do users want or need to do? |
| | 86 | * What is the general background of the users? |
| | 87 | * What is the context in which the user is working? |
| | 88 | * What has to be left to the machine? |
| | 89 | * Software related: |
| | 90 | * Learnability: How easy is it for users to accomplish basic tasks the first time they encounter the design? How much training do users need? What documentation or other supporting materials are available to help the user? Can users find the solutions they seek in these materials? |
| | 91 | * Are there provisions for meeting the special needs of users with disabilities? |
| | 92 | * Efficiency: Once users have learned the design, how quickly can they perform tasks? |
| | 93 | * Recall: How much does the person remember afterwards or after periods of non-use? |
| | 94 | * Memorability: When users return to the design after a period of not using it, how easily can they re establish proficiency? |
| | 95 | * Errors: How many errors do users make, how severe are these errors, and how easily can they recover from the errors? What do users have to do to recover from errors? Does the product help users recover from errors? For example, does software present comprehensible, informative, non-threatening error messages? |
| | 96 | * Performance: How much time, and how many steps, are required for people to complete basic tasks? (For example, find something to buy, create a new account, and order the item.) |
| | 97 | * Emotional response -- How does the person feel about the tasks completed? Is the person confident, stressed? How pleasant is it to use the design? Would the user recommend this system to a friend? |
