IS480 Team wiki: 2016T2 ProgneSIS Heuristic Evaluation

From IS480
Jump to navigation Jump to search
Team Prognesis Icon Home.png


  Team Prognesis Icon AboutUs.png


  Team Prognesis Icon Overview.png


  Team Prognesis Icon ProjectManagement.png


  Team Prognesis Icon Documentation.png


Technical Documents Design Documents Test Documents Meetings Minutes Project Deliverables

Heuristic Evaluation

  • Date: 16-19 September 2015
  • Venue: At the convenience our experts

Heuristic Evaluation Objective

We conducted a Heuristic Evaluation using a paper prototype to learn about the usability of our current design of VersaFleet Analytics. We used a paper prototype as changes can be made easily before we develop the actual application. This HE will help us discover possible improvements in the design of our application to improve its usability.


  • 5 participants

These participants took IDP (IS306) in SMU and are considered UI experts. For confidentiality purposes, we would name them Tester 1, 2, 3, 4 and 5.

Paper Prototype

Below are views for the paper prototype used.

Team ProgneSIS Lo-FiMainPage.jpg
Team ProgneSIS Lo-FiNotification.jpg
Team ProgneSIS Lo-FiBusinessPerformanceDropdownList.jpg
Team ProgneSIS Lo-FiRevenueVSCostGraphPage.jpg
Team ProgneSIS Lo-FiOperationsDDL.jpg
Team ProgneSIS Lo-FiDeliveryFulfilmentRateGraphPage.jpg
Team ProgneSIS Lo-FiNoJHGraphPage.jpg
Team ProgneSIS Lo-FiVCUGraphPage.jpg
Team ProgneSIS Lo-FiFuelCostGraphPage.jpg

Heuristic Evaluation Severity Ratings

Heuristics Severity Ratings
0. Not related to any heuristic

1. Visibility of system status

2. Match between system and the real world

3. User control and freedom

4. Consistency and standards

5. Error prevention

6. Recognition rather than recall

7. Flexibility and efficiency of use

8. Aesthetic and minimalist design

9. Help users recognize, diagnose, and recover from errors

10. Help and documentation

0 = Not a real usability problem

1 = Cosmetic problem only

2 = Minor usability problem

3 = Major usability problem

4 = Usability catastrophe

Heuristics Results

Name Lack of customisability of information
Sources Tester 1, 2, 3, 4 and 5
Heuristic 7. Flexibility and efficiency of use Severity 2. Minor Usability Problem

Choice of time period of the data is not displayed, and users were unable to view older data.

Proposed Solution:

Enable users to select any time period they want from a calendar. Change the single dropdown box to multiple dropdown boxes, such as View By [Start Year] [Start Month] to [End Year] [End Month]. Common presets such as “Current Month”, “Past 3 months”, “Past Year”, etc. can be buttons placed to the right of the graph.

Name Lack of consistency of data displayed
Sources Tester 1 and 2
Heuristic 4. Consistency and standards Severity 2. Minor usability problem

Data used are inconsistent in terms of units. Percentage, whole values etc. Graphs are inconsistent with different axis.

Proposed Solution:

Ensure that graphs use similar units for consistency and comparison - how % of one graph increases % in other graph.

Name Lack of information on the graphs
Sources Tester 1 and 2
Heuristic 1. Visibility of system status, 4. Consistency and efficiency of use Severity 2. Minor usability problem

Experts were not able to learn more information when they would like to as different values of each point on the graph were not visible. The data units were not labelled appropriately or clearly. The table below did not provide sufficient information for the user and some graphs do not have tables.

Proposed Solution:

Give the users ability to magnify/zoom into the graph to see more detailed information. Allow users to select data points on the graph for more information. Include table of details for every graph.

Name Visibility of graph while user scrolls through the list/table of individual unit under the "Operations" functions
Sources Tester 3
Heuristic 6. Recognition rather than recall Severity 3. Major usability problem

As the paper prototype does not show this, I can only assume how the tables will be displayed to the user. i.e. when the user scroll to view the lower entries on the table, the graph will become hidden.

Proposed Solution:

Make the graph smaller so that it takes lesser screen space. Allow the table to be independently scrollable. This is such that the user will have a clear view of the table at all time for comparison with any specific unit’s entry.

Name Overload of information
Sources Tester 2 and 5
Heuristic 8. Aesthetics and minimalistic design Severity 2.Minor usability problem

Experts found there was too much information on certain pages, especially homepage. Cluttered information might overwhelm and confuse the user. Display would also pose a problem for smaller screen sizes.

Proposed Solution:

Adopt minimalist design with lesser information on the home page. The line between Too much information and sufficient details is a fine one. Team need to revise the amount of data to display that is relevant to the real user and remove those redundant ones.