Difference between revisions of "IS480 Team wiki: 2011T2 Eureka Heuristic Evaluation"
Va.ng.2009 (talk | contribs) |
Va.ng.2009 (talk | contribs) |
||
Line 35: | Line 35: | ||
{| class="wikitable" valign=top" style="text-align: center; width: 100%" border="1" align="center" | {| class="wikitable" valign=top" style="text-align: center; width: 100%" border="1" align="center" | ||
|- | |- | ||
− | ! align="center" | Heuristic Violated | + | ! align="center" width="40%"| Heuristic Violated |
− | ! align="center" | Comments and Feedback | + | ! align="center" width="50%"| Comments and Feedback |
− | ! align="center" | Severity (1 - 4) | + | ! align="center" width="10%"| Severity (1 - 4) |
|- | |- | ||
| valign="top" align="left"| '''Visibility of system status'''<br> | | valign="top" align="left"| '''Visibility of system status'''<br> | ||
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. | ||
| valign="top" align="left"| A timer should be included to give users and teams a sense of how long each round had been going on for. | | valign="top" align="left"| A timer should be included to give users and teams a sense of how long each round had been going on for. | ||
− | | valign="top" align=" | + | | valign="top" align="center"| 3 |
|- | |- | ||
| valign="top" align="left"| '''Match between system and the real world'''<br> | | valign="top" align="left"| '''Match between system and the real world'''<br> | ||
Line 49: | Line 49: | ||
After sending trade request, all values should be reset back to default instead of remaining as the last setting.<br> | After sending trade request, all values should be reset back to default instead of remaining as the last setting.<br> | ||
The naming of certain functions/buttons need to be rephrased to be made obvious to the users<br> | The naming of certain functions/buttons need to be rephrased to be made obvious to the users<br> | ||
− | | valign="top" align=" | + | | valign="top" align="center"| 3 <br><br><br> |
2<br><br> | 2<br><br> | ||
3 | 3 | ||
Line 56: | Line 56: | ||
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. | ||
| valign="top" align="left"| A reset button on the ‘send request’ page could be added to allow users to undo and reset all their settings back to the default values. | | valign="top" align="left"| A reset button on the ‘send request’ page could be added to allow users to undo and reset all their settings back to the default values. | ||
− | | valign="top" align=" | + | | valign="top" align="center"| 1 |
|- | |- | ||
| valign="top" align="left"| '''Consistency and standards'''<br> | | valign="top" align="left"| '''Consistency and standards'''<br> | ||
Line 63: | Line 63: | ||
Use of conventional icons for certain buttons such as ‘back to main’ could be utilized.<br> | Use of conventional icons for certain buttons such as ‘back to main’ could be utilized.<br> | ||
Login page should include password authentication to disallow other teams from accessing other teams’ accounts.<br> | Login page should include password authentication to disallow other teams from accessing other teams’ accounts.<br> | ||
− | | valign="top" align=" | + | | valign="top" align="center"| 1<br> |
1<br><br> | 1<br><br> | ||
3 | 3 | ||
Line 70: | Line 70: | ||
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. | ||
| valign="top" align="left"| When sending a trade request, the default resources for ‘trade with’ and ‘trade for’ are the same which would not make any sense in a transaction/trade. Application should prevent users from selecting the same resources for both options. | | valign="top" align="left"| When sending a trade request, the default resources for ‘trade with’ and ‘trade for’ are the same which would not make any sense in a transaction/trade. Application should prevent users from selecting the same resources for both options. | ||
− | | valign="top" align=" | + | | valign="top" align="center"| 4 |
|- | |- | ||
| valign="top" align="left"| '''Recognition rather than recall'''<br> | | valign="top" align="left"| '''Recognition rather than recall'''<br> | ||
Line 77: | Line 77: | ||
Create the possibility of a scrollable area on all pages except main page to allow teams/users to view the amount of resources without having to click a separate button to open a popup. This will make it easier for tracking their resources.<br> | Create the possibility of a scrollable area on all pages except main page to allow teams/users to view the amount of resources without having to click a separate button to open a popup. This will make it easier for tracking their resources.<br> | ||
Push notifications to teams whenever sent requests to other teams are accepted or declined. | Push notifications to teams whenever sent requests to other teams are accepted or declined. | ||
− | | valign="top" align=" | + | | valign="top" align="center"| 3<br><br> |
2<br><br><br><br> | 2<br><br><br><br> | ||
3 | 3 | ||
Line 83: | Line 83: | ||
| valign="top" align="left"| '''Flexibility and efficiency of use'''<br> | | valign="top" align="left"| '''Flexibility and efficiency of use'''<br> | ||
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. | ||
− | | valign="top" align="left"| | + | | valign="top" align="left"| - |
− | | valign="top" align=" | + | | valign="top" align="center"| - |
|- | |- | ||
| valign="top" align="left"| '''Aesthetic and minimalist design'''<br> | | valign="top" align="left"| '''Aesthetic and minimalist design'''<br> | ||
Line 90: | Line 90: | ||
| valign="top" align="left"| Some button names are very wordy. Should shorten the naming of particular functions.<br> | | valign="top" align="left"| Some button names are very wordy. Should shorten the naming of particular functions.<br> | ||
More attractive design with some illustrations will be good. Perhaps a better background, include icons and different colour schemes etc. | More attractive design with some illustrations will be good. Perhaps a better background, include icons and different colour schemes etc. | ||
− | | valign="top" align=" | + | | valign="top" align="center"| 2<br><br> |
2 | 2 | ||
|- | |- | ||
| valign="top" align="left"| '''Help users recognize, diagnose, and recover from errors'''<br> | | valign="top" align="left"| '''Help users recognize, diagnose, and recover from errors'''<br> | ||
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. | ||
− | | valign="top" align="left"| | + | | valign="top" align="left"| - |
− | | valign="top" align=" | + | | valign="top" align="center"| - |
|- | |- | ||
| valign="top" align="left"| '''Help and documentation'''<br> | | valign="top" align="left"| '''Help and documentation'''<br> | ||
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. | ||
| valign="top" align="left"| A help button providing descriptions for each function in the main menu will be helpful. | | valign="top" align="left"| A help button providing descriptions for each function in the main menu will be helpful. | ||
− | | valign="top" align=" | + | | valign="top" align="center"| 1 |
|- | |- | ||
|} | |} |
Revision as of 15:01, 25 July 2012
Home | Project Stakeholders | Project Overview | Usability & Storyboard | Project Management | Learning Outcomes | Sitemap |
Game Description | Storyboarding | User Acceptance Test | Heuristic Evaluation |
Heuristic Violated | Comments and Feedback | Severity (1 - 4) |
---|---|---|
Visibility of system status The system should always keep users informed about what is going on, through appropriate feedback within reasonable time. |
A timer should be included to give users and teams a sense of how long each round had been going on for. | 3 |
Match between system and the real world The system should 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. |
Buttons in the navigation bar for shortcuts and flexibility should be distinctively different from other function-specific buttons. This is so users can tell the difference. After sending trade request, all values should be reset back to default instead of remaining as the last setting. |
3 2 |
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. |
A reset button on the ‘send request’ page could be added to allow users to undo and reset all their settings back to the default values. | 1 |
Consistency and standards Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions. |
Button sizes in the navigation bar are not consistent. Use of conventional icons for certain buttons such as ‘back to main’ could be utilized. |
1 1 |
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. |
When sending a trade request, the default resources for ‘trade with’ and ‘trade for’ are the same which would not make any sense in a transaction/trade. Application should prevent users from selecting the same resources for both options. | 4 |
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. |
Team name should be displayed around the top of pages to avoid confusion if tablets got mixed up. Create the possibility of a scrollable area on all pages except main page to allow teams/users to view the amount of resources without having to click a separate button to open a popup. This will make it easier for tracking their resources. |
3 2 |
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. |
- | - |
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. |
Some button names are very wordy. Should shorten the naming of particular functions. More attractive design with some illustrations will be good. Perhaps a better background, include icons and different colour schemes etc. |
2 2 |
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. |
- | - |
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. |
A help button providing descriptions for each function in the main menu will be helpful. | 1 |
Contents
Heuristic Evaluation 1
Work in progress...
Heuristic Evaluation 2
Work in progress...
Heuristic Evaluation 3
Not started...
Heuristic Evaluation 4
Not started...