Thursday, February 27, 2014

Human Computer Interaction

Study about the interaction between human and computer

  • Visibility of system status(Feedback) :The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.
  • Match between system and the real world (METAPHOR):The system should speak the users’ language, with words, phrases and concepts familiar to the user, rather than  system oriented terms.
  • User control and freedom (NAVIGATION): Users often choose system functions by mistake and will need a clearly marked “emergency exit” to leave the unwanted state without having to go through an extended dialogue. Supports undo and redo and a clear way to navigate.
  • Consistency and standards (CONSISTENCY):Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions
  • Error prevention (PREVENTION):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):Minimize the user’s memory load. Make objects, actions, and options visible.
  • Flexibility and efficiency of use (EFFICIENCY):Accelerators — unseen by the novice user — may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.
  • Aesthetic and minimalist design(DESIGN):Dialogues should not contain information, which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
  • Help users recognize, diagnose, and recover from errors (RECOVERY):Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
  • 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. Any such information should be easy to search, focused on the user’s task, list concrete steps to be carried out, and
    not be too large.