First Website
Second Website
Nielsen's heuristics
Jakob Nielsen's heuristics are probably
the most-used usability heuristics for user interface design. Nielsen developed
the heuristics based on work together with Rolf Molich in 1990.The final set of heuristics that
are still used today were released by Nielsen in 1994.The heuristics as published in
Nielsen's book Usability Engineering are as follows
Visibility of system status:
The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.
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:
The system should speak the user's 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.
The system should speak the user's 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.
User control and freedom:
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.
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.
Consistency and standards:
Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.
Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.
Error prevention:
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.
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.
Recognition rather than recall:
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.
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.
Flexibility and efficiency of use:
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.
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:
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.
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:
Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
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. 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.
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.
Five differentiation between Rapid Penang website and Sri Maju website
Visibility of system status
The Rapid Penang website provide the latest information about their services at the specific page named Latest News.
The Sri Maju website put all the news update at home page to allow the user alert about the current information and promotion.
Error prevention:
Consistency and standards:
The star icon in the Rapid Penang website is use to mention the user that they to enter their information to further the process of submission the mail.
The selection system is use in Sri Maju website to make the user easier to choose the types of ticket their need and minimize the user error.
Sri Maju website use the consistent button to the entire page to let the viewer can recognize which are the button. They also us the same icon which is hibiscus flower at their company name logo.
The list of menu at Rapid Penang website also same in every pages and the font of the words. They also use standard size and font to all the menu subdivision.
Recognition rather than recall:
The Rapid Penang website provide the flow chart of the menu to ensure the viewer can see the previous page that they visit. they also can click it to go to that page.
The viewer need to memorize which button are provide them the information at previous page because they only have the button as a navigation component.
Match between system and the real world:
Help and documentation:
Both of the website use the standard English language and the writing and answer writing structure that enable the viewer understand which they should read first. the arrangement also help the viewer more easily to find the information they need.
Help and documentation:
The menu button of Rapid Penang website consist of the sub menu that enable user to know the content of every button provided.
Sri Maju website do not provide the sub menu of the button. So, the viewer need to view one by one page to know the content in every pages provided.
No comments:
Post a Comment