HeaderSIS.jpg

IS480 Team wiki: 2012T2 5 B 1 G Webapp User Tests

From IS480
Jump to navigation Jump to search
5B1G Logo.png


Home

Our Team/Sponsors

Project Overview

Project Management

Project Documentation

Usability Documentation

Learning Outcomes


Count Me In User Tests

Webapp User Tests

Prototypes & Mockups


Summary of User Tests Documentation
User Test Details Methodology Documents for User Test User Test Results
Webapp UT1 Date: 22 Jan 2013 (Tues)
Participants: 2 retailers
Location: The Basement Cafe
Paper Prototype Web UT1 Execution Plan Web UT1 Results
Webapp UT2 Date: 25 Mar 2013 (Mon)
Participants: 10 users (students)
Location: SIS SR 2-4
(Webapp testing) Goals were given for users to complete Web UT2 Execution Plan

Web UT2 Instructions Sheet

Web UT2 Compiled Results
Webapp UT3 Date: 10 April 2013 (Wednesday)
Participants: 6 retailers
Location: The Cathay
(Webapp testing) Goals were given for retailers to complete Web UT3 Execution Plan

Web UT3 Instructions Sheet

Web UT3 Compiled Results
Webapp UT4 17 April 2013 (Wednesday)
Participants: 6 retailers
Location: The Cathay
(Webapp testing) Goals were given for retailers to complete Web UT4 Execution Plan

Web UT4 Instructions Sheet

Web UT4 Compiled Results
Admin Portal UT 16 April 2013 (Tuesday)
Participants: 6 users
Location: SMU SIS SR 2-3
(Admin Portal testing) Goals were given for users to complete Admin Portal UT Execution Plan

Admin Portal UT Instructions Sheet

Admin Portal System Compiled Results

Webapp User Test 1

How We Conducted the UT

Objectives

The main objectives of this user test are:

  • To obtain feedback from our users with regards to the layout and business logic in our application

Details:

  • Participants: 2 retailers
  • Venue: SMU, The Basement Café
  • Date: 22nd Jan 2013 (Tuesday)
  • Duration: 2 hours
  • Environment: “Sit at a table” setting

Method

We conducted the user test using a low-fidelity paper prototype using the mock up designs of the web application and the participants were given the freedom to explore the application by themselves.

Data collection

Collecting of qualitative metrics

  • We will observe how the participants use the application during the testing procedure.
  • Upon completion of the paper prototype, the participant will be asked to give their feedback on usability and business rules behind the application.

Features Tested

S/N Feature
1 Login with an account
2 Upload e-coupons
3 Edit pending e-coupons
4 View published e-coupons
5 View expired e-coupons
6 View Business Intelligence for published and expired e-coupons
7 Delete E-coupon
8 Logout of application

Gallery

   

5B1G IMG 5073.JPG

5B1G IMG 5074.JPG

5B1G IMG 5075.JPG

IMG 5076.JPG

5B1G IMG 5077.JPG

5B1G IMG 5078.JPG

Results

Results

Download link available here: Web UT Results

Observations

S/N Observation
1 The user did not have any major problems regarding the usability the application
2 They were more concerned about the business logic, they asked about whether they need to upload or select an individual product, because sometimes they offer discounts like “10% off all mains” rather than discount for an individual product
3 Overall, they were quite fascinated by the analytics that the application can produce

Feedback

S/N Feedback
1 “Tagging an e-coupon to a product may not be always applicable, because sometimes we just want to entice people to come and patronize the restaurants, thus we may have a promotion for bulk items”
2 “Maybe you could limit the number of coupons we can give out because sometimes when we conduct an offer, we do not have sufficient stock”

Changes Made

Features Tested

S/N Feedback Change Made
1 “Tagging an e-coupon to a product may not be always applicable, because

sometimes we just want to entice people to come and patronize the restaurants, thus we may have a promotion for bulk items”

The user does not need to tag a product to the coupon. We reduced it to a 1-step upload process instead of a 2-step upload process.
2 ““Maybe you could limit the number of coupons we can give out because

sometimes when we conduct an offer, we do not have sufficient stock”

We included a new field for the retailer to enter the limit on the number of coupons (optional)

Webapp User Test 2

How We Conducted the UT

Objectives

  • To obtain feedback from our users with regards to the usability of the Retailer Admin System
  • To create an application that is user-friendly for retailers

Details:

  • Participants: 10 users
  • Venue: SIS SR 2-4
  • Date: 25th Mar 2013 (Monday)
  • Duration: 4 hours (each individual: 20-30mins)

Method

The actual application was tested this time using a laptop. Each participant was given the Web UT2 Instruction Sheet and asked to circle how easy it was to complete each test case.

Data collection

Collecting of qualitative metrics

  • Facilitators will observe how the participants use the Retailer Admin System during the testing procedure.
  • Upon completion of the web user test, the participant will be asked to give their feedback on the usability of the application.

Collecting of quantitative metrics

  • Upon completion of the UT, the participant will be asked to rate, on a scale of 1 to 5, how easy the task is and to give their feedback on the functionality and the usability of the application.

Features Tested for Retailer Admin System

S/N Feature
1 Create a retail account
2 Login
3 Upload new E-coupon
4 Edit Pending E-coupon
5 Copy E-coupon
6 Delete E-coupon
7 View Published E-coupon statistics
8 Logout

Results

Download the results here:

Compiled Problems & Proposed Solutions

5B1G WebUT2 Prob1.png

5B1G WebUT2 Prob2.png

Gallery

   

5B1G WebUT2 1.JPG

5B1G WebUT2 2.JPG

5B1G WebUT2 3.JPG

5B1G WebUT2 4.JPG

5B1G WebUT2 5.JPG

5B1G WebUT2 6.JPG

5B1G WebUT2 7.JPG

5B1G WebUT2 8.JPG

5B1G WebUT2 9.JPG

Webapp User Test 3 (Cathay retailers)

How We Conducted the UT

Objectives

  • To obtain feedback from our retailers with regards to the usability of the Retailer Admin System
  • To create an application that is user-friendly for retailers

Details:

  • Participants: 6 retailers
  • Venue: The Cathay
  • Date: 10th Apr 2013 (Wedneday)
  • Duration: 6 hours (each individual: 20-30mins)

Method

The Retailer Admin System was tested using a laptop . Each participant was given the Web UT3 Instruction Sheet and asked to circle how easy it was to complete each test case.

Data collection

Collecting of qualitative metrics

  • Facilitators will observe how the participants use the Retailer Admin System during the testing procedure.
  • Upon completion of the web user test, the participant will be asked to give their feedback on the usability of the application.

Collecting of quantitative metrics

  • Upon completion of the UT, the participant will be asked to rate, on a scale of 1 to 5, how easy the task is and to give their feedback on the functionality and the usability of the application.

Features Tested for Retailer Admin System

S/N Feature
1 Create a retail account
2 Login
3 Upload new E-coupon
4 Edit Pending E-coupon
5 Copy E-coupon
6 Delete E-coupon
7 View published E-coupon statistics
8 Delete E-coupon
9 Logout

Results

Download the results here:

Compiled Problems & Proposed Solutions

5B1G UT 3 problem.png

Gallery

   

JShoes 5B1G.jpg

CreaTeaf Waffles.jpg

Marcella 5b1G.JPG

St Games 5B1G.JPG

Popeyes 5B1G.jpg

Gong Cha 5B1G.jpg

Webapp User Test 4(Cathay retailers)

How We Conducted the UT

Objectives

  • To obtain feedback from our retailers with regards to the usability of the Retailer Admin System with the updated changes from the last user test

Details:

  • Participants: 6 retailers
  • Venue: The Cathay
  • Date: 17th Apr 2013 (Wedneday)
  • Duration: 6 hours (each individual: 20-30mins)

Method

The Retailer Admin System was tested using a laptop . Each participant was given the Web UT4 Instruction Sheet and asked to circle how easy it was to complete each test case.

Data collection

Collecting of qualitative metrics

  • Facilitators will observe how the participants use the Retailer Admin System during the testing procedure.
  • Upon completion of the web user test, the participant will be asked to give their feedback on the usability of the application.

Collecting of quantitative metrics

  • Upon completion of the UT, the participant will be asked to rate, on a scale of 1 to 5, how easy the task is and to give their feedback on the functionality and the usability of the application.

Features Tested for Retailer Admin System

S/N Feature
1 Create a retail account
2 Login
3 Upload new E-coupon
4 Crop new E-coupon
5 Edit Pending E-coupon
6 Copy E-coupon
7 Delete E-coupon
8 View Published E-coupon statistics
9 View or export BI report
10 Delete E-coupon
11 Logout

Results

Download the results here:

Admin Portal UT

How We Conducted the UT

Objectives

  • To obtain feedback from our with regards to the usability of the Admin Portal
  • To create an application that is user-friendly for administrators

Details:

  • Participants: 6 users
  • Venue: SMU SIS SR 2-3
  • Date: 16th Apr 2013 (Tuesday)
  • Duration: 2 hours (each individual: 20-30mins)

Method

The Admin Portal was tested using a laptop . Each participant was given the Admin Portal Instruction Sheet and asked to circle how easy it was to complete each test case.

Data collection

Collecting of qualitative metrics

  • Facilitators will observe how the participants use the Admin Portal during the testing procedure.
  • Upon completion of the Admin Portal user test, the participant will be asked to give their feedback on the usability of the application.

Collecting of quantitative metrics

  • Upon completion of the UT, the participant will be asked to rate, on a scale of 1 to 5, how easy the task is and to give their feedback on the functionality and the usability of the application.

Features Tested for Admin Portal

S/N Feature
1 Login
2 View existing retailers
3 Delete existing retailer
4 Approve pending retailer
5 Toggle between self developed IPS and Indoo.rs
6 Logout

Results

Download the results here: