HeaderSIS.jpg

IS480 Team wiki: 2018T1 Five Stones User Testing UAT2

From IS480
Revision as of 01:15, 18 October 2018 by Hyyeo.2016 (talk | contribs) (Update UAT 2 v3.1)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Logo 1.3.png


ClebsHome.png HOME

ClebsAboutUS.png ABOUT US

ClebsProjectOverview.png PROJECT OVERVIEW

ClebsProjectManagement.png PROJECT MANAGEMENT

ClebsDocumentation.png DOCUMENTATION

Persona & Scenarios Prototypes Meeting Minutes Diagrams User Testing Deliverables


5Stones UAT1.PNG 5Stones UAT2.PNG 5Stones UAT3.PNG


UAT 2 Test Plan

Venue: 8 @ tradehub 21, 09-12, 8 Boon Lay Way, Singapore 609964
Date: 24 September 2018, Monday
Time: 11 am
Number of Participant(s): 3
Target Audience: Sponsor’s client

Objectives

  • To gather potential usability issues such as User Interface (UI) / User Experience (UX) for the developed web application
  • To gather feedback for core developed functions (i.e. Creation of reports & exporting functions such as Powerpoint of PDF format)
  • To identify problems faced by users while using the web application
  • To improve the web application by incorporating the important feedback received

Scope

  • Report Component module
  • Importing module
  • Report customization module
  • Chart Population module
  • Report Storage module
  • Report Descriptive Analytics module
  • Report Developer module
  • Exporting module
  • Slideshow module

Procedures

  1. Participants will be provided with the link to the web application
  2. A document comprising of the step-by-step instructions will be handed to users
  3. Participants will follow the document to complete the UAT
  4. Participants will help the team fill in the post-UAT feedback form.

Results

S/N Goals Achieved? % of participants able to complete the task
1 Participants should be able to login and logout Yes Pass. 100% successful
2 Participants should be able to create a data source and select the data configurations No Fail. 33.33% managed to successfully created the data source
3 Participants should be able to create a report template Yes Pass. 100% successful
4 Participants should be able to see basic summary statistics when they create a chart (i.e. Both bar & line chart inclusive) Yes Pass. 100% successful
5 Participants should be able to export the report template as PPT format Yes Pass. 100% successful
6 Participants should be able to export the report template as PDF format Yes Pass. 100% successful
7 Participants should be able to see report template as slideshow Yes Pass. 100% successful

User Behavior

S/N Module/Function User Behavior Changes to be made
1 Developer / Creating a datasource Unable to make sense of what is needed to be filled in for the blanks, given that it is the first time they are using the developer web page 1. Naming conventions to be improved to make the fields intuitive

2. Placeholders to be added on the blanks to further guide the users

2 Developer / Creating a datasource When trying to select the datasource configurations, user tend to type out the `Path` Disable typing on the “Path” field at the `add` portion to prevent users from typing there
3 Developer / Creating a datasource User is unable to comprehend and understand what does the `Type` field mean Include a tooltip with a basic description for users
4 Developer / Creating a datasource User cannot find the `select` button to finalize the data configuration chose Include in a scrollbar to make the UI intuitive and easy to use
5 Report Customization No indication of “editing” or “not editing” mode for template creation UI indication to show users if they are in “Editing” mode or not with color coding for easier reference
6 Report Customization Users unable to give a title to the charts created, spend a good amount of time to try typing the chart name Add a class to the textbox so that the textbox is not draggable and hence we can click on the textbox
7 Report Customization Users unable to give a title to the charts created, spend a good amount of time to try typing the chart name Add a class to the textbox so that the textbox is not draggable and hence we can click on the textbox
8 Report Customization Unable to export certain components as PDF or PPT (i.e. components not visible after exporting) Include a prompt for the users to know that the components used cannot be exported out as PDF or PPT and give a recommendation otherwise
9 Exporting / Export as PPT No indication that the video component can be played after exporting into PPT To overlay a `play` image to prompt to user to click on video to show that it is working
10 Slideshow No indication of page number is seen Add in the HTML element as the caption and style it

User Comments

S/N Module/Function Comments Changes to be made
1 Developer / Creating a datasource The `add` button does not make it easy for users to understand what they need to do next Naming conventions to be improved to make the button more user friendly and intuitive
2 Developer / Creating a datasource Alignment issues with the `path` and `field name` field after the selecting the path. Very problematic and unpleasing to the eyes `Path` field should be overlayed below the `select` button and make it the same row as the dataset name and type fields
3 Developer / Creating a datasource There is no boundary for every new data configuration. Makes the page very cluttered and messy Create a boundary line to differentiate every dataset to be configured
4 Report Customization The template named “Default template” should be made into the real default template instead of a created template on its own Transfer contents from current report template “ “Default template” and make it the default template available for other users to create
5 Report Customization A lot of buttons on a page to click. Better to consolidate by category and put all related buttons together to simplify the whole page layout Consolidate all the “exporting” function buttons into one dropdown button for users to choose
6 Report Customization System allows duplicating names for different reports (i.e. at least 2 templates with the same name given) 1. To make sure each template created is unique with a different name given to every template created.

2. To also prompt an error message to the user if the same name is used

7 Report Customization Include a `delete` function to conveniently remove a report template page when required Create a `delete` function that links to every single page and allows the user to click and remove the report template page immediately
8 Report Customization Users unable to give a title to the charts created Add a class to the textbox so that the textbox is not draggable and hence we can click on the textbox
9 Report Customization “Show Summary Table” is not intuitive and does not fully represent what we are intending to show Naming conventions to be implemented and changed from “Show Summary Table” to “Show Summary Statistics”
10 Report Customization Components that cannot be exported out to PDF or PPT are not explicitly stated Include a prompt for the users to know that the components used cannot be exported out as PDF or PPT and give a recommendation otherwise
11 Exporting / Export as PDF Better to include in a guidance to show users how to retrieve the embedded URL Include in a tooltip to show users when part of the whole iframe tag is used as the link in addition with the placeholder in place
12 Exporting / Export as PDF The page number is considerably big in size Reduce the size of the page number to make it less outstanding
13 Slideshow No indication of page number is seen Add in the HTML element as the caption and style it

Post-Test Questionnaire

Post test pic1.PNG Post test pic2.PNG Post test pic3.PNG

Overall Comments

  • The web application is generally easy to navigate around, with the functions easily spotted which gave the users an easy time
  • The report template creation user interface is simple to use and intuitive. Users find it easy to focus on the given tasks on hand
  • Developer page can be improved to make it simpler for user