| Visibility of system status (visibility) |
The system should always keep user informed about what is going on, through appropriate feedback within reasonable time. |
| Match between system and the real world (match) |
The system should speak the user’s language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. |
| User control and freedom (control) |
Users should be free to select and sequence tasks, rather than having the system do this for them. |
| Consistency and standards (consistency) |
Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions. |
| Help users recognize, diagnose, and recover from errors (undo) |
Error messages should be expressed in plain language. |
| Error prevention (error) |
Even better than good error messages is a careful design which prevents a problem from occurring in the first place. |
| Recognition rather than recall (memory) |
The user should not have to remember information from one part of the dialogue to another. |
| Flexibility and efficiency of use (flexibility) |
Allow users to tailor frequent actions. Provide alternative means of access and operation for users who differ from the “average” user. |
| Aesthetic and minimalist design (minimalist) |
Dialogues should not contain information which is irrelevant or rarely needed. |
| Help and documentation (help) |
Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. |
| Skills |
The system should support, extend, supplement, or enhance the user’s skills, background knowledge, and expertise. |
| Pleasurable and respectful interaction with the user |
The user’s interactions with the system should enhance the quality of her or his work-life. |
| Privacy |
The system should help the user to protect personal or private information. |
