HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T1 ByteMe User Testing"

From IS480
Jump to navigation Jump to search
Line 56: Line 56:
 
* Bugs were recorded and the team would fix the bugs accordingly.
 
* Bugs were recorded and the team would fix the bugs accordingly.
 
* The term function would have to be re-done.
 
* The term function would have to be re-done.
 
 
  
 
==Test Plan 1 (Student)==
 
==Test Plan 1 (Student)==
Line 81: Line 79:
 
<b>Action Plan</b><br>
 
<b>Action Plan</b><br>
 
* Bugs were recorded and the team would fix the bugs accordingly.
 
* Bugs were recorded and the team would fix the bugs accordingly.
 +
* Added HTML Function to make the project much easier to read
 +
 +
==Test Plan 2 (Admin)==
 +
<b>Number of Users: </b>4<br>
 +
<b>Date: </b>19th August 2016<br>
 +
<b>Venue: </b>SMU SR 2-3<br>
 +
<b>Duration: </b>30 mins per user<br>
 +
<b>Objectives: </b><br>
 +
* Analysing the usability of the Application (User Interface, Navigation Ease, etc.)
 +
* Improving the Overall Feel of new functions
 +
<b>Scope: </b><br>
 +
* Faculty Management
 +
* Export Functions
 +
* Notification Module
 +
<b>Procedure: </b>Users are given a document which contains information on how to go about with the user testing.<br>
 +
 +
<b>Results & Comments</b><br>
 +
* thoughts on the new functions was given, overall average results.
 +
* Ideas were given to improve usability and improve the navigation of coordinator function.
 +
 +
<b>Action Plan</b>
 +
* Front-end development fixes were given to Michael.
 +
* We intend to make the faculty management from 3 different navigation tabs into 1.
 +
 +
==Test Plan 2 (Student)==
 +
<b>Number of Users: </b>7<br>
 +
<b>Date: </b>15th August 2016<br>
 +
<b>Venue: </b>SMU Labs<br>
 +
<b>Duration: </b>Around 30 mins per user<br>
 +
<b>Objectives: </b><br>
 +
* Observation of user behavior when using our application
 +
* Identify usability issues that exist in the application
 +
* Improve our application based on user testing result
 +
<b>Scope: </b><br>
 +
* SSO Login using your SMU Account details
 +
* Edit their Student Details
 +
* Create/Join Team
 +
* Request to take up a Project
 +
<b>Procedure: </b>Users are given a document which contains information on how to go about with the user testing.<br>
 +
 +
<b>Results & Comments</b><br>
 +
* Many did not know how to accept a team invitation.
 +
* User Interface has improved, but still not acceptable to our team.
 +
 +
<b>Action Plan</b><br>
 +
* Intend to do a A/B Testing in our next user test.
 +
* Added a notification module to notify users of pending invitations.
 
<!--Body End-->
 
<!--Body End-->

Revision as of 12:07, 28 September 2016

ByteMe Logo.jpeg
ByteMe Home icon 2.png
ByteMe About me icon 2.png
ByteMe overview icon 2.png
Management icon.png
ByteMe Documentation icon 2.png
ByteMe Project Documentation.png
Technical Documents Design & UI/UX Process Flows Meeting Minutes User Testings


User Test 1

Main Page Test

Test Plan 1 (Admin)

Number of Users: 4
Date: 4th August 2016 & 5th August 2016
Venue: Benjamin Gan Office (SMU SIS 5034) & Fiona Lee's Office (SMU SIS 4056)
Duration: 30 mins per user
Objectives:

  • Analysing the usability of the Application (User Interface, Navigation Ease, etc.)
  • Identify any bugs or issues that users may face during the user testing.
  • Improving the IS480 application based on the user testing result.
  • Identify any other functions that the course coordinators of IS480 may find useful.

Scope:

  • Create Term
  • Create/Edit Milestones in Terms
  • Export Student-Team.csv

Procedure: Users are given a document which contains information on how to go about with the user testing.

Results & Comments

  • The System still contains bugs that our team did not successfully fix.
  • User Interface is good, but some parts be improved on. Ideas and suggestions were given.

Action Plan

  • Front-end development fixes were given to Michael.
  • Bugs were recorded and the team would fix the bugs accordingly.
  • The term function would have to be re-done.

Test Plan 1 (Student)

Number of Users: 7
Date: 6th August 2016 & 7th August 2016
Venue: SMU School of Information Systems
Duration: Around 30 mins per user
Objectives:

  • Observation of user behavior when using our application
  • Identify usability issues that exist in the application
  • Improve our application based on user testing result

Scope:

  • SSO Login using your SMU Account details
  • Edit their Student Details
  • Create/Join Team
  • Request to take up a Project

Procedure: Users are given a document which contains information on how to go about with the user testing.

Results & Comments

  • There were some bugs in the system, but none serious.
  • User Interface is good, but some parts be improved on. Ideas and suggestions were given.

Action Plan

  • Bugs were recorded and the team would fix the bugs accordingly.
  • Added HTML Function to make the project much easier to read

Test Plan 2 (Admin)

Number of Users: 4
Date: 19th August 2016
Venue: SMU SR 2-3
Duration: 30 mins per user
Objectives:

  • Analysing the usability of the Application (User Interface, Navigation Ease, etc.)
  • Improving the Overall Feel of new functions

Scope:

  • Faculty Management
  • Export Functions
  • Notification Module

Procedure: Users are given a document which contains information on how to go about with the user testing.

Results & Comments

  • thoughts on the new functions was given, overall average results.
  • Ideas were given to improve usability and improve the navigation of coordinator function.

Action Plan

  • Front-end development fixes were given to Michael.
  • We intend to make the faculty management from 3 different navigation tabs into 1.

Test Plan 2 (Student)

Number of Users: 7
Date: 15th August 2016
Venue: SMU Labs
Duration: Around 30 mins per user
Objectives:

  • Observation of user behavior when using our application
  • Identify usability issues that exist in the application
  • Improve our application based on user testing result

Scope:

  • SSO Login using your SMU Account details
  • Edit their Student Details
  • Create/Join Team
  • Request to take up a Project

Procedure: Users are given a document which contains information on how to go about with the user testing.

Results & Comments

  • Many did not know how to accept a team invitation.
  • User Interface has improved, but still not acceptable to our team.

Action Plan

  • Intend to do a A/B Testing in our next user test.
  • Added a notification module to notify users of pending invitations.