Changes between Version 16 and Version 17 of PLATFORM_NFR_USABILITY_R0
- Timestamp:
- 10/31/08 13:15:35 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PLATFORM_NFR_USABILITY_R0
v16 v17 59 59 * Learnability: How easy is it for users to accomplish basic tasks the first time they encounter the design? 60 60 * Efficiency: Once users have learned the design, how quickly can they perform tasks? 61 * Statement of how easy it will be. 61 62 62 * Memorability: When users return to the design after a period of not using it, how easily can they re establish proficiency? 63 63 * Another benefit of the tooltips and simple concept, also overlapping features (halos and right clicks), common used keyboard shortcuts, intuitive solutions as base bound controls. 64 64 * Errors: How many errors do users make, how severe are these errors, and how easily can they recover from the errors? 65 * Maybe a little confused in the start. Program errors are automatically sent to the developers.66 65 * Satisfaction: How pleasant is it to use the design? 67 66 Part 2 … … 99 98 * Are there provisions for meeting the special needs of users with disabilities? 100 99 * Efficiency: Once users have learned the design, how quickly can they perform tasks? 100 * Statement of how easy it will be. 101 101 * Recall: How much does the person remember afterwards or after periods of non-use? 102 * Memorability: When users return to the design after a period of not using it, how easily can they re establish proficiency? 103 * 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? 104 * 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.) 102 * Errors and mistakes: 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? 103 * Program errors are automatically sent to the developers. 104 * Reporting issues 105 * Help and support (community support) 106 * Performance: How much time, and how many steps, are required for people to complete basic tasks? 107 * Creating a book 108 * Loading a book 109 * Sharing a book 110 * Collaborative editing 105 111 * 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? 112 * User interface, extensibility and options. Benefits of open source (community ideas for improvement, skinning). 113 * Rendering solutions 114 * Templates. 106 115 107 116 = Implementation =
