HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
Line 28: Line 28:
  
 
<!--Body-->
 
<!--Body-->
 +
<div style="background: #ffc113; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size: 32px"><font color=#FFFFFF>User Test 1</font></div>
  
 +
==Test Plan (Admin)==
 +
<b>Number of Users: </b>4<br>
 +
<b>Date: </b>4th August 2016 & 5th August 2016<br>
 +
<b>Venue: </b>Benjamin Gan Office (SMU SIS 5034) & Fiona Lee's Office (SMU SIS 4056)<br>
 +
<b>Duration: </b>30 mins per user<br>
 +
<b>Objectives: </b><br>
 +
* 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.
 +
<b>Scope: </b><br>
 +
* Create Term
 +
* Create/Edit Milestones in Terms
 +
* Export Student-Team.csv
 +
<b>Procedure: </b>Users are given a <b>[[Media: ByteMe_UAT_1.docx|document]]</b> which contains information on how to go about with the user testing.<br>
 +
 +
<b>Results & Comments</b><br>
 +
* 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.
 +
 +
<b>Action Plan</b></br>
 +
* 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 (Student)==
 +
<b>Number of Users: </b>7<br>
 +
<b>Date: </b>6th August 2016 & 7th August 2016<br>
 +
<b>Venue: </b>SMU School of Information Systems<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 <b>[[Media: ByteMe_UAT_Student_1.docx|document]]</b> which contains information on how to go about with the user testing.<br>
 +
 +
<b>Results & Comments</b><br>
 +
* 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.
 +
 +
<b>Action Plan</b><br>
 +
* Bugs were recorded and the team would fix the bugs accordingly.
 
<!--Body End-->
 
<!--Body End-->

Revision as of 15:00, 7 August 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

Test Plan (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 (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.