Heuristic Evaluation, usability of heuristic

This presentation is on the topic of heuristic. Evaluation of Heuristic , usability of Heuristic

1. By~ Jehanzeb Buledi Heuristic Evaluation 1

2. When we measure the user interface that how much mistakes and flaws are there in user interface. Example I opened any software so any software must have user interface it means I am dealing with a user interface the measurement and the judgement of that user interface by me is known as evaluation. Evaluation

3. Heuristic evaluation is a process where experts uses rules of thumb to measure the usability of user interfaces in independent walkthroughs and report issues. Example I have 3 experts to evaluate the software and every one evaluate by their own point of view means they will see mistakes and flaws by their on expertise. Heuristic Evaluation

4. Jakob Nielsen Usability Heuristic So when the evaluation occurs for any software that how much software is competitive and qualitative for that reason Jakob Nielsen introduced 10 usability heuristic. He said, having these ten things in your software can increase the usability of your software . Must effective Must efficient Must qualitative

5. Visibility of system status 5 Match between system and the real world User control and freedom Consistency and standards Error prevention 10 Usability Heuristic 1 2 3 4 5 Reference : The basics you can find anywhere 5 Steps To Successful Storytelling Published on April 5, 2014 Featured in: Marketing & Advertising

6. Recognition rather than recall 6 Flexibility and efficiency of use Aesthetic and minimalist design Help users recognize, diagnose, and recover from errors Help and documentation 6 7 8 9 10 Reference : The basics you can find anywhere 5 Steps To Successful Storytelling Published on April 5, 2014 Featured in: Marketing & Advertising

7. The system should always keep users informed about current state and actions through appropriate visual cues and feedback within reasonable time.  Careem Bykea Visibility of system status Example

8. Our system or software connects the real world with it. Means it must familiar with user so user must feel the real world connection with software. It can be any type like icons, products, e.t.c ibooks ipad application using the metaphor of wooden book shelf. Match between system and the real world Example

9. 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. Support undo and redo. User control and freedom

10. Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions. Consistency and standards

11. Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action. Error prevention

12. Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate. Recognition rather than recall

13. 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. Flexibility and efficiency of use

14. 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. Aesthetic and minimalist design

15. Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution. Help users recognize , diagnose , and recover from errors

16. How to use the application Full detail will be provided Help and documentation

17. END PRESENTATION! THANK YOU Jehanzeb Buledi | CS-E20-026