Heuristic Evaluation

To identify usability problems in the user interface design before completion of the application, we performed an heuristic evaluation. The following program flow chart shows the structure of “Moove” and formed the basis of our heuristic evaluation.

Overall game state

Performing the evaluation we examined the following heuristics:

  • user control and freedom
  • error prevention
  • flexibility and efficiency of use
  • aesthetic and minimalist design
  • help and documentation
  • missing elements
  • errors in the program sctructure

The last two heuristics had been phrased especially for our apllication, thus they are project specific heuristics. After having done the heuristic we evaluated and compared our results, rated the severity of each problem and discussed the most important issues that needed to be adressed:

1. User control and freedom

problem: The user can touch the particular area anytime without error report releasing an error report or using score points.
severity: major problem
relevance: principle of the game is missed
status: FIXED

problem: The buttons in the menu are too small, therefore its challenging to use them.
severity: cosmetic problem
relevance: only concerning comfort
status: FIXED

problem: control too imprecise and kind of bumpy
severity: minor problem
relevance: limiting the joy of use
status: not yet fixed

2. Error prevention:
problem: identification of multiple players in single-player
severity: minor problem
relevance: maybe confusing. If it is fixed, there probably will be no more possibility to change from single- to multi-player-mode during a session of the game
status: not yet fixed

3. Flexibility and efficiency of use
problem: sheet music appearing too fastly and in a too large amount
severity: usability catastrophe
relevance: game is just not playable
status: not yet fixed

problem: appearance of sheet music and song are not synchronized perfectly
severity: minor problem
relevance: nevertheless well playable and not too annoying
status: not yet fixed

problem: placing of the symbols around the player still needs adjustment for being more efficient but without underchallenging the player
severity: minor problem
status: not yet fixed

4. Aesthetic and minimalist design
problem: The look of “moove” is a little bit confusing. The background is supposed to be just black, therefore player can more easily focuse on the game
severity: minor problem
status: not yet fixed

problem: letters are too small and difficult to read
severity: cosmetic problem
status: FIXED

problem: sheet music could look more lovely
severity: cosmetic problem
status: not yet fixed

5. Help and documentation
problem: especially in the menu there is no guidance or instructions, telling users what to do. But we suppose the game to be usable intuitionally
severity:cosmetoc problem
status: status: not yet fixed

6. Missing elements
problem: 2-player-mode is missing
severity: major problem
relevance: 2-player-mode is supposed to be a feature of major importance, because this is how we promoted the idea for our application and moreover it just will be more fun in  multi-player-mode
status: not yet fixed

problem: there are only 2 song to choose from
severity: cosmetic problem
relevance: more songs will increase long-term-amusement, but implementing more songs later will be easy if main functions of the application are developped completely. So currently it is just not important
status: not yet fixed

problem: no highscore availablle
severity: minor problem
relevance: Without highscore, there is no possibility to determine the winner in 2-player mode. There are more important problems to solve in advance, but realisation is easy.
status: FIXED

7. Errors in the program structure
problem: there is no valid stop-signal indicating the end of a session. For this reason the game starts another session or continues incorrect.
severity: usability catastrophe
relevance: Game not playable for more than one session
status: not yet fixed

problem: sometimes the game starts without sound output, a reset is needed
severity: minor problem
status: not yet fixed

The following pictures show some of the imrovements we made to the software after having done this evaluation. Because of the short time provided for this evaluation and it’s implementation, we could not solve all problems so far.

Before evaluation:

Game

After evaluation:
Game_2

Before evaluation:

Menu

After evaluation:

Menu_2

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s