HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2013T2 AAN HT"

From IS480
Jump to navigation Jump to search
Line 230: Line 230:
 
Make the area indicating locker cluster bigger, and enlarge the map so that users will not have to squint to use the map.
 
Make the area indicating locker cluster bigger, and enlarge the map so that users will not have to squint to use the map.
  
 +
|}
 +
 +
==== Problem ====
 +
{| class="wikitable centered" width="90%"
 +
|width="50pt"|'''Name'''
 +
|Colspan=3|Complaints are separated into too many little boxes
 +
 +
|-
 +
|width="50pt"|'''Heuristic'''
 +
|width="40%"|8. Aesthetic and minimalist design
 +
|width="50pt"|'''Severity'''
 +
|2 = Minor usability problem
 +
 +
|-
 +
|Colspan=4|'''Description''':
 +
All the complaints are currently put in little boxes, and it can look a bit excessive since they are all in one page. User feels that they have to scroll through too much information before they can get the one they need.
 +
 +
|-
 +
|Colspan=4|'''Proposed Solution''':
 +
Consider representing the data in rows instead. In this way, it will not take up too much space, and it might also look neater. Have a search filter so that vendor can find what they are looking for easily.
 
|}
 
|}
  

Revision as of 17:49, 16 February 2014



Heuristic Feedback

Brief

Overall

Heuristics

Severity

Compiled Problems

Severity 4: Usability catastrophe

Severity 3: Major usability problem

Problem 1

Name Unable to find the correct locker clusters
Heuristic 1. Visibility of system status Severity 3 = Major usability problem
Description:

Users do not know where the exact lockers clusters are on the map. It is confusing to try and deduce which colors stand for locker and which stands for corridors.

Proposed Solution:

Make use of a legend to indicate the color that represents locker for better visibility.

Problem 2

Name Unable to identify the maps with their respective school as there are no labels or names for each map
Heuristic 1. Visibility of system status Severity 3 = Major usability problem
Description:

Users will not know which school the map of lockers belongs too since there is no obvious greying out or labelling of the school name and cluster.

Proposed Solution:

Provide a header at the top of the map to indicate the school, at the same time grey out those schools that are not chosen.

Severity 2: Minor usability problem

Problem

Name Too much white space on page
Heuristic 1. Visibility of system status Severity 2 = Minor usability problem
Description:

Users will be shown a blank page with school name and level when they want to book new lockers.

Proposed Solution:

Prompt users to select school and level in searchLocker.jsp rather than giving them a blank page to figure out. Alternatively, grey out the areas that users are not supposed to press on so that they'll have a better idea of what they are supposed to do first.

Problem

Name Lack of explanation for the numbers that are shown after the admin choose to view lockers from a certain school
Heuristic 5. Error prevention Severity 2 = Minor usability problem
Description:

After admin chooses the school and level in admin locker management, they are simply shown a bunch of numbers which does not explain their purpose.

Proposed Solution:

Those numbers are supposedly the number of unbooked lockers in each floor for that particular school, but it might be slightly confusing as to what admin are supposed to do with it. Provide an alert to indicate the actions that are supposed to be carried out.

Problem

Name Able to access the book locker page even after students own a locker
Heuristic 3. User control and freedom Severity 2 = Minor usability problem
Description:

User will still be able to go to the booking page after booking a locker which might be confusing as they will think that they can book more than one locker.

Proposed Solution:

Grey out the booking page when users own a locker, or have a warning message on that page when they are trying to book again.

Problem

Name Users/Admin have to memorize the different locations lockers are at
Heuristic 6. Recognition rather than recall Severity 2 = Minor usability problem
Description:

Currently, users/admin will have to memorize how the clusters look in real life when they search(for admin)/view(for both) for lockers.

Proposed Solution:

Have a picture to indicate where the actual lockers are at. Provide a mini-map that will be available via pop-up when users toggle for that option.

Problem

Name User have to hover over multiple blocks to determine which lockers are booked
Heuristic 7. Flexibility and efficiency of use Severity 2 = Minor usability problem
Description:

User will have to hover over the different lockers within the cluster to check which are booked.

Proposed Solution:

Use color codes for booked lockers; red for booked lockers and white for those that are unbooked.

Problem

Name Area indicating locker cluster on map is too small
Heuristic 7. Flexibility and efficiency of use Severity 2 = Minor usability problem
Description:

The area indicating locker cluster on the map is currently too small, and it is slightly annoying since users have to hover over the exact spot.

Proposed Solution:

Make the area indicating locker cluster bigger, and enlarge the map so that users will not have to squint to use the map.

Problem

Name Complaints are separated into too many little boxes
Heuristic 8. Aesthetic and minimalist design Severity 2 = Minor usability problem
Description:

All the complaints are currently put in little boxes, and it can look a bit excessive since they are all in one page. User feels that they have to scroll through too much information before they can get the one they need.

Proposed Solution:

Consider representing the data in rows instead. In this way, it will not take up too much space, and it might also look neater. Have a search filter so that vendor can find what they are looking for easily.

Severity 1: Cosmetic problem only

Problem

Name Misleading buttons on admin page
Heuristic 2. Match between system and the real world Severity 1 = Cosmetic problem only
Description:

The plus button in admin locker management is confusing as user will think that they are allowed to add new lockers when pressing on any locker. Instead the button is for user to edit locker details.

Proposed Solution:

Change the plus button to an edit button instead.

Problem

Name Misleading buttons on student locker details page
Heuristic 2. Match between system and the real world Severity 1 = Cosmetic problem only
Description:

The report broken locker button is confusing as the symbol used is normally used as a settings button.

Proposed Solution:

Change the report locker button to a warning button as suggested by some of the testers.

Problem

Name No standardization for colors on the map
Heuristic 4. Consistency and standards Severity 1 = Cosmetic problem only
Description:

Different colors are used for locker cluster for different schools and it makes it difficult for users to know what is what.

Proposed Solution:

Use yellow to represent all the locker clusters in the different schools.

Problem

Name No standardization for colors on the map
Heuristic 5. Error prevention Severity 1 = Cosmetic problem only
Description:

Different colors are used for locker cluster for different schools and it makes it difficult for users to know what is what.

Proposed Solution:

Use yellow to represent all the locker clusters in the different schools.

Severity 0: I don't agree that this is a usability problem

Problem

Name Lack of filtering when admin view lockers
Heuristic 3. User control and freedom Severity 0 = I don't agree that this is a usability problem
Description:

Vendor and admin are unable to filter the search for locker other than by school, cluster or level. Should allow them to choose the kind of locker status they are interested in too, if not they will have to comb through tons of lockers just to find the correct information.

Proposed Solution:

Create a button that allows admin/vendor to filter for the locker status they are interested in.

Reasons for not implementing:

Admin will actually be able to see all the faulty lockers when they visit the vendor page, so it will be redundant to display the same information in two different pages..