<aside> <img src="/icons/clipping_lightgray.svg" alt="/icons/clipping_lightgray.svg" width="40px" /> Evaluation Details
</aside>
<aside> <img src="/icons/push-pin_red.svg" alt="/icons/push-pin_red.svg" width="40px" /> Severity Rating
<aside> 0️⃣ I don’t agree: this is a problem at all
</aside>
<aside> 1️⃣ Cosmetic problem only: need not be fixed unless extra time is available on the project
</aside>
<aside> 2️⃣ Minor usability problem: fixing this should be given low priority
</aside>
<aside> 3️⃣ Major usability problem: important to fix, should be given high priority
</aside>
<aside> 4️⃣ Usability catastrophe: imperative to fix this before the product can be released
</aside>
</aside>
<aside> <img src="/icons/bookmark_lightgray.svg" alt="/icons/bookmark_lightgray.svg" width="40px" /> Visibility of System Status
• Always keep users informed about what is going on. • Provide appropriate feedback within a reasonable time.
</aside>
<aside> <img src="/icons/bookmark_lightgray.svg" alt="/icons/bookmark_lightgray.svg" width="40px" /> Match Between System and the Real World
• Speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. • Follow real-world conventions, making information appear in a natural and logical order.
</aside>
<aside> <img src="/icons/bookmark_lightgray.svg" alt="/icons/bookmark_lightgray.svg" width="40px" /> User Control and Freedom
• Users often choose system functions by mistake. • Provide a clearly marked "out" to leave an unwanted state without having to go through an extended dialogue. • Support undo and redo.
</aside>
<aside> <img src="/icons/bookmark_lightgray.svg" alt="/icons/bookmark_lightgray.svg" width="40px" /> Consistency and Standards
• Users should not have to wonder whether different words, situations, or actions mean the same thing. • Follow platform conventions.
</aside>
<aside> <img src="/icons/bookmark_lightgray.svg" alt="/icons/bookmark_lightgray.svg" width="40px" /> Error Prevention
• Even better than good error messages is a careful design which prevents a problem from occurring in the first place..
</aside>
<aside> <img src="/icons/bookmark_lightgray.svg" alt="/icons/bookmark_lightgray.svg" width="40px" /> Recognition Rather than Recall
• Make objects, actions, and options visible. • 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.
</aside>
<aside> <img src="/icons/bookmark_lightgray.svg" alt="/icons/bookmark_lightgray.svg" width="40px" /> Flexibility and Efficiency of Use
• Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user so that the system can cater to both inexperienced and experienced users. • Allow users to tailor frequent actions.
</aside>
<aside> <img src="/icons/bookmark_lightgray.svg" alt="/icons/bookmark_lightgray.svg" width="40px" /> Aesthetic and Minimalist 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.
</aside>
<aside> <img src="/icons/bookmark_lightgray.svg" alt="/icons/bookmark_lightgray.svg" width="40px" /> Recognize, Diagnose, and Recover from Errors
• Expressed in plain language (no codes) • Precisely indicate the problem • Constructively suggest a solution
</aside>
<aside> <img src="/icons/bookmark_lightgray.svg" alt="/icons/bookmark_lightgray.svg" width="40px" /> Help and Documentation
• Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. • Help information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.
</aside>
<aside> <img src="/icons/bookmark_lightgray.svg" alt="/icons/bookmark_lightgray.svg" width="40px" /> Skills
• The system should support, extend, supplement, or enhance the user’s skills, background knowledge, and expertise ----not replace them.
</aside>
<aside> <img src="/icons/bookmark_lightgray.svg" alt="/icons/bookmark_lightgray.svg" width="40px" /> Pleasurable and Respectful Interaction with the User
• The user’s interactions with the system should enhance the quality of her or his work-life. The user should be treated with respect. The design should be aesthetically pleasing- with artistic as well as functional value.
</aside>
<aside> <img src="/icons/bookmark_lightgray.svg" alt="/icons/bookmark_lightgray.svg" width="40px" /> Privacy
The system should help the user to protect personal or private information- belonging to the user or the his/her clients.
</aside>