HeaderSIS.jpg

IS480 Team wiki: 2016T1 Fixxlar User Tests

From IS480
Revision as of 12:01, 30 July 2016 by Desmond.neo.2014 (talk | contribs) (First draft of User Testing 1)
Jump to navigation Jump to search
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

User Testing 1

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

Objectives:

  • To gather feedback on the user interface of Workshop 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 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 one of the workshop administrator (from Dynamic Mechanics) whom we had spoken to during our market research.

Method of Conduct:

  • <insert link for testing.doc here>

Goals and Results:

S/N Goals Results
1 Participants should be able to login and logout successfully as a Workshop Administrator, and also change password (note that more accounts may be required) null
2 Participants should be able to add, edit, and delete a workshop from the system. null
3 Participants should be able to receive a quotation request sent by the “customer” from his/her mobile application, and reply accordingly. null
4 Participants should be able to trigger valet services when “customer” requests for one. null

Key Findings:

  • <To Be Updated>

Detailed Findings:

  • <To Be Updated>

Follow-ups to be made:

  • <To Be Updated>