Object Oriented Software Engineering   View all facts   Glossary   Help
subject > criterion > principle > usability principle
Next principleapproach to identifying generalizations    Upprinciple    Previous principlerule   

usability principle comparison table
Subject follow by state
usability principle 1testing a user interface on usersDo not rely only on usability guidelines - always test with users
usability principle 10
  • accommodating people from different locales and people with disabilities
  • ensuring that the system is usable by both beginners and experts
Consider the needs of different groups of users
usability principle 11
  • organizing help well
  • integrating help with the application
  • ensuring that the help is accurate
Provide all necessary help
usability principle 12
  • using similar layouts and graphic designs throughout your application
  • following look-and-feel standards
  • mimicking other applications
Be consistent within the application and between applications
usability principle 2Base UI designs on users' tasks as expressed in use cases
usability principle 3
  • making sure users can move from step to step easily as they perform their tasks
  • making sure that user has to read the smallest amount of text, to navigate the least, to type the least and not to be lead into making errors
  • making sure the user does not have to repeatedly select menu items to complete a single task
  • avoiding sequences of modal dialogs, since they give users the feeling that the computer is in control of the interaction
Ensure that the sequences of actions to achieve a task are as simple as possible
usability principle 4
  • Ensuring that the user can see what commands are available and are not available
  • making the most important commands stand out
Ensure that the user always knows what he or she can and should do next, and what will happen when he or she does it
usability principle 5
  • informing users of the progress of operations and of their location as they navigate
  • when something goes wrong, explaining the situation in adequate detail and help the user to resolve the problem
Provide good feedback including effective error messages
usability principle 6ensuring that all operations can be done and that it is easy for the user to navigate back to where they came fromEnsure that the user can always get out, go back or undo an action
usability principle 7
  • Recognizing that users are very sensitive to slow response time, and that they compare your system to others in this regard
  • keeping response time less than a second for most operations
  • warning users of longer delays and inform them of progress
Ensure that response time is adequate
usability principle 8
  • making sure that everything that appears on the screen should be easily understandable to users
  • avoiding technical jargon and acronyms
  • employing technical writers to compose text and graphic designers to create graphics
  • labelling items so their meaning is obvious
Ensure that the user always feels in control
usability principle 9
  • trying to avoid displaying too much information
  • organizing the information effectively
Ensure that the UI's appearance is uncluttered

Next principleapproach to identifying generalizations    Upprinciple    Previous principlerule