HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T1 Fixxlar User Tests"

From IS480
Jump to navigation Jump to search
m
(updated user test findings)
Line 77: Line 77:
  
 
<h3>Goals and Results: </h3>
 
<h3>Goals and Results: </h3>
{| class="wikitable"
+
 
 +
{| class="wikitable" style="background-color:#FFFFFF; width: 900px;" align="center"
 +
|-
 +
|-
 +
! style="color:#ffffff; background-color:#E5A400;" width="30pt" align="center" | S/N
 +
! style="color:#ffffff; background-color:#E5A400;" width="400pt" align="center" | Goals
 +
! style="color:#ffffff; background-color:#E5A400;" width="400pt" align="center" | Results
 
|-
 
|-
! S/N !! Goals !! Results
+
|style="text-align: center;"| 1 || Participants should be able to login and logout successfully as a Workshop/Fixir Administrator, and also change password (note that more accounts may be required)
 +
|style="background-color:#A3E4D7"| Successful. Participants tried changing the passwords and logging in with the new accounts created.
 
|-
 
|-
| 1 || Participants should be able to login and logout successfully as a Workshop/Fixir Administrator, and also change password (note that more accounts may be required)
+
|style="text-align: center;"| 2 || Participants should be able to add, edit, and delete a workshop from the system.
  || -
+
  || N.A. as Fixir Administrator testing has been postponed
 
|-
 
|-
| 2 || Participants should be able to add, edit, and delete a workshop from the system.
+
|style="text-align: center;"| 3 || Participants should be able to receive a quotation request sent by the “customer” from his/her mobile application, and reply accordingly.  
  || -
+
  |style="background-color:#A3E4D7"| Successful. All participants were able to reply a quotation without guidance.
 
|-
 
|-
| 3 || Participants should be able to receive a quotation request sent by the “customer” from his/her mobile application, and reply accordingly. || -
+
|style="text-align: center;"| 4 || Participants should be able to manage all services requests.  
 +
|style="background-color:#F9E79F"| Partially reached. Some participants required guidance to navigate to "Manage Services" page.
 
|-
 
|-
| 4 || Participants should be able to trigger valet services when “customer” requests for one.
+
|style="text-align: center;"| 5 || Participants should be able to trigger valet services when “customer” requests for one.
  || -
+
  || N.A as Valet Module's process workflow is still TBC.
 
|}
 
|}
  
<h3>Key Findings:</h3>
+
<h3>User Test Findings:</h3>
* <To Be Updated>
+
{| class="wikitable" style="background-color:#FFFFFF; width: 900px;" align="center"
<h3>Detailed Findings:</h3>
+
|-
* <To Be Updated>
+
|-
 +
! style="color:#ffffff; background-color:#E5A400;" width="200pt" align="center" | Function / Task
 +
! style="color:#ffffff; background-color:#E5A400;" width="600pt" align="center" | Observation / Comments
 +
|-
 +
|style="text-align: center;"| Login/Logout & Change of Password
 +
||
 +
* Generally easy and self-explanatory. Participants had no trouble accomplishing this task.
 +
|-
 +
|style="text-align: center;"| Dashboard View
 +
||
 +
* Request page may be able to replace the current dashboard
 +
* General dashboard may have too much information which may not be the most relevant
 +
* "Final Quote Accepted" may have higher precedence over "New Requests" as workshops have to prepare for the repair which will be coming in
 +
|-
 +
|style="text-align: center;"| Viewing of Specific request
 +
||
 +
* Colour of vehicle may not be required
 +
* Quotation amount should be clearer (with or without GST)
 +
* Information is messy, with car info, service info, and customer details all mixed up
 +
* One Motoring link can be placed under the license plate number, for users to extract relevant vehicle information like chassis number, year of registration etc.
 +
* Chat button can be more prominent
 +
|-
 +
|style="text-align: center;"| Replying Estimated Quotation
 +
|| 
 +
* Easy to use
 +
* Estimated quotation vs diagnostic price is clear
 +
|-
 +
|style="text-align: center;"| Replying Final Quotation
 +
||
 +
* Final quotation and estimated time of completion should be keyed in at the same time
 +
* Estimated time should be dynamic (able to update), as accident claims may take more than 2 weeks' time, which is difficult to estimate
 +
* Difficult to navigate to Manage Services page after final quotation is accepted by user - does not seem like the same process flow
 +
|-
 +
|style="text-align: center;"| Miscellaneous
 +
||
 +
* On Request page, search bar should be named "search" instead of "filter"
 +
* Scheduling and rescheduling would be useful, with chat function as another layer of communication
 +
* In the long run, it may be good to have a report for each request logged in case any mishaps/conflicts arise
 +
* Auto-refresh is disruptive to user, as pop-up requests may be dismissed
 +
|}
 
<h3>Follow-ups to be made:</h3>
 
<h3>Follow-ups to be made:</h3>
 
* <To Be Updated>
 
* <To Be Updated>

Revision as of 16:40, 7 August 2016

Fixxlar-logo.png


Fixxir-Home.png   HOME

Fixir-about-icon.png   ABOUT US

Fixir-Overview-icon.png   PROJECT OVERVIEW

Project management-icon.png   PROJECT MANAGEMENT

Fixir-documentation-icon.png   DOCUMENTATION

 

User Testing 1 (6 August 2016)

User Testing 1

Venue: FIXIR’s office (BASH, #03-01, 79 Ayer Rajah Crescent, Singapore 139955) & Respective Workshops
Date: 6 August 2016, Saturday
Time: 10.00am - 2.00pm
Duration: ~30 minutes
Number of Participant(s): 6 (TBC)

Objectives:

  • To gather feedback on the user interface of Workshop Administrator’s and Fixir Administrator's web application
  • Identify possible usability issues with functions of Account Module, Quotation Request Module, Dashboard Module, Valet Module

Scope for User Testing 1:

  • Logging in and out as Workshop/Fixir Administrator
  • Changing of password
  • CRUD Workshops as as Fixir Administrator
  • Viewing and replying of quotation requests
  • Requesting of valet services
  • Chat messaging with the mobile application (KIV)

Target Participants & Rationale:

  • Participants of this first user testing would be our sponsor (from Fixir team), and also workshop administrators (from Dynamic Mechanics etc) whom we had spoken to during our market research.

Method of Conduct:

Goals and Results:

S/N Goals Results
1 Participants should be able to login and logout successfully as a Workshop/Fixir Administrator, and also change password (note that more accounts may be required) Successful. Participants tried changing the passwords and logging in with the new accounts created.
2 Participants should be able to add, edit, and delete a workshop from the system. N.A. as Fixir Administrator testing has been postponed
3 Participants should be able to receive a quotation request sent by the “customer” from his/her mobile application, and reply accordingly. Successful. All participants were able to reply a quotation without guidance.
4 Participants should be able to manage all services requests. Partially reached. Some participants required guidance to navigate to "Manage Services" page.
5 Participants should be able to trigger valet services when “customer” requests for one. N.A as Valet Module's process workflow is still TBC.

User Test Findings:

Function / Task Observation / Comments
Login/Logout & Change of Password
  • Generally easy and self-explanatory. Participants had no trouble accomplishing this task.
Dashboard View
  • Request page may be able to replace the current dashboard
  • General dashboard may have too much information which may not be the most relevant
  • "Final Quote Accepted" may have higher precedence over "New Requests" as workshops have to prepare for the repair which will be coming in
Viewing of Specific request
  • Colour of vehicle may not be required
  • Quotation amount should be clearer (with or without GST)
  • Information is messy, with car info, service info, and customer details all mixed up
  • One Motoring link can be placed under the license plate number, for users to extract relevant vehicle information like chassis number, year of registration etc.
  • Chat button can be more prominent
Replying Estimated Quotation
  • Easy to use
  • Estimated quotation vs diagnostic price is clear
Replying Final Quotation
  • Final quotation and estimated time of completion should be keyed in at the same time
  • Estimated time should be dynamic (able to update), as accident claims may take more than 2 weeks' time, which is difficult to estimate
  • Difficult to navigate to Manage Services page after final quotation is accepted by user - does not seem like the same process flow
Miscellaneous
  • On Request page, search bar should be named "search" instead of "filter"
  • Scheduling and rescheduling would be useful, with chat function as another layer of communication
  • In the long run, it may be good to have a report for each request logged in case any mishaps/conflicts arise
  • Auto-refresh is disruptive to user, as pop-up requests may be dismissed

Follow-ups to be made:

  • <To Be Updated>