IS480 Team wiki: 2011T2 Eureka Heuristic Evaluation
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 |
Contents
Heuristic Evaluation 1
Work in progress...
Heuristic Evaluation 2
Work in progress...
Heuristic Evaluation 3
Not started...
Heuristic Evaluation 4
Not started...