HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2015T2 Elements Heuristic Evaluation"

From IS480
Jump to navigation Jump to search
Line 7: Line 7:
 
{|style="background-color:#5C005C; color:#DF8DDF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0"  |
 
{|style="background-color:#5C005C; color:#DF8DDF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0"  |
 
| style="padding:0.3em; font-size:100%; background-color:#5C005C;  border-bottom:0px solid #3D9DD7; text-align:center; color:#F5F5F5" width="10%" |  
 
| style="padding:0.3em; font-size:100%; background-color:#5C005C;  border-bottom:0px solid #3D9DD7; text-align:center; color:#F5F5F5" width="10%" |  
[[Image:Team_Elements_Home.png|30px|link=IS480 Team wiki: 2015T2 Team Elements]]  
+
[[Image:Team_Elements_Home.png|30px|link=IS480 Team wiki: 2016T2 Team Elements]]  
[[IS480 Team wiki: 2015T2 Elements |<font color="#F5F5F5" size=2><b>HOME</b></font>]]
+
[[IS480 Team wiki: 2016T2 Elements |<font color="#F5F5F5" size=2><b>HOME</b></font>]]
  
 
| style="border-bottom:0px solid #5C005C; background:none;" width="1%" | &nbsp;  
 
| style="border-bottom:0px solid #5C005C; background:none;" width="1%" | &nbsp;  

Revision as of 01:32, 19 February 2016

Team Elements Logo.jpg



Team Elements Home.png   HOME

 

Team Elements AboutUs.png   ABOUT US

 

Team Elements PrjOverview.png   PROJECT OVERVIEW

 

Team Elements PrjMgmt.png   PROJECT MANAGEMENT

 

Team Elements Documentation.png   DOCUMENTATION

Technical Documents Design Documents NavigationElements.png Testing Documents Meeting Minutes Project Documents


Heuristic evaluation

  • Venue: Singapore Management University

heuristic evaluation Objective

We conducted a Heuristic Evaluation to test out the design of our application. This is to learn more about the usability of our application and improve it further in our future designs. This was conducted with a paper prototype. A paper prototype was used because we want to be able to discover UI issues early, so that the cost of changing will not be so high.

Heuristic Evaluation Participants

  • 5 participants

These participants took IDP (IS306) in SMU and were UI experts. To keep the confidentialiy of the participants, we named them Tester A, Tester B, Tester C, Tester D, Tester E.

Paper Prototype

Here are some of the screen for the paper prototype. To view the full paper prototype, please click here.

Admin Portal - User Management
Admin Portal - Case Management
Admin Portal - Create Case

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 guidance for whole process and medicine tab
Sources Tester A, Tester B, Tester C, Tester E
Heuristic 10. Help and documentation Severity 2. Minor Usability Problem
Description:

There is no steps to guide the students on what they should do first.

Even as users are required to scan in patient’s bar code before medicine’s, the system still

allows user to scan medicine’s bar code before patient’s which will be followed by an

error message. This process can be more efficient.

Proposed Solution:

Implement a tour around the website to tour the students around if they are using the

web for the first time. E.g: Step 1: View previous team’s Multidisciplinary notes. Step

2: Administer care for your patients by navigating to various tabs.

Step 3: Submit notes.

Provide some form of guidance such as disabling the medicine input field before

scanning the patient’s bar code. This way, users will be reminded that they have to

scan the patient’s bar code first.

Name Missing case information which results in user having to navigate back to obtain case information where the “back” button is not available.
Sources Tester A, Tester C, Tester E
Heuristic 3. User control and freedom Severity 2. Minor usability problem
Description:

After selecting the case, students will be able to view case’s information where the

ward and the bed is stated. Users will need memorize the ward and bed’s

information so that they can navigate to the patient’s information. In any case when

the users click wrong ward or bed, the users will need to look at the case’s

information again where there is no “back” button to navigate to it.

Proposed Solution:

A “back” button so that users can navigate back to look at the case information. Or a

dropdown information from the top bar where they can view basic case information

quickly by hovering over it.

Name Unnecessary information on case selection page
Sources Tester C, Tester E
Heuristic 1. Visibility of system status, 8. Aesthetic and minimalist design Severity 2. Minor usability problem
Description:

The existing case selection page shows both locked and unlocked cases. It is not

necessary to show the students the cases that are locked as they are unable to

access it anyway.

Proposed Solution:

The application should only show unlocked cases or show the case information that

is available for the current week.

The team can consider omitting the locked cases and only populate the page with

the cases that can be accessed, i.e. past cases and current week case. In order to

minimize the number of clicks, the team can include the case synopsis when user

hovers over the thumbnail of the respective cases. In addition, they could add labels

or more information to distinguish between the past cases and the current case. For

instance, a tick could be shown for the completed case(s).

Name Misleading titles and button names
Sources Tester E
Heuristic MisMatch between system and the real world Severity 3. Major usability problem
Description:

On the report tab, the title says generate new report which sounds like creating a

new report from scratch instead of the intended function of retrieving reports that was

previously generated. The button name, “Generate” contributes to this issue as well.

Proposed Solution:

Consider changing the title to “Retrieval of reports” and button name to “Retrieve”.

Name Unable to tell report generation progress
Sources Tester C, Tester E
Heuristic 1. Visibility of system status Severity 1. Cosmetic problem only
Description:

While generating new report(s), there is no indication that the reports are generating

in progress. Users may not know that it is loading and may click on “Generate” again.

This may result in repeated reports.

Proposed Solution:

The team could add words like “Processing” or “Generating” once the user clicks on

“Generate”. Have a notification which informs the user of the status of the generation

(whether it is successful or not)

Name Lack of details on chart in vital signs tab
Sources Tester A, Tester E
Heuristic 7. Flexibility and efficiency of use Severity 2. Minor usability problem
Description:

As user hovers the mouse on the chart, there is no additional details provided. It may

be hard to read off the screen. When the user view the temperature chart of the

patient, he has to manually match the readings to the axis values of the chart. This

will take unnecessary time and will make the user more prone to making inaccurate

readings.

Proposed Solution:

Team can include data labels for each point to facilitate reading the chart easier. This

will provide the user the information he needs at a glance and reduce chances of

inaccurate readings.