HeaderSIS.jpg

IS480 Team wiki: 2011T2 Eureka Heuristic Evaluation

From IS480
Revision as of 14:51, 25 July 2012 by Va.ng.2009 (talk | contribs)
Jump to navigation Jump to search
Team Eureka logo.jpg







Heuristic Evaluation

Good design begins with honesty, tough questions, and trusting your intuition...


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.
The naming of certain functions/buttons need to be rephrased to be made obvious to the users

3


2

3

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.
Login page should include password authentication to disallow other teams from accessing other teams’ accounts.

1

1

3

Back to Top






Work in progress...

Work in progress...

Not started...

Not started...

Back to Top