HeaderSIS.jpg

IS480 Team wiki: 2017T2 All Stack Documentation UAT

From IS480
Revision as of 23:44, 22 March 2018 by Joleen.mok.2014 (talk | contribs)
Jump to navigation Jump to search
AllStackTeamlogo2.png

AllStack Home.png

AllStack About Us.png

AllStack Project Overview.png

AllStack ProjectManagement.png

AllStack Project Documentation Selected.png

User Testing

UAT

UT 1


Test Plan

Venue: Gushcloud HQ @ 60 Anson Road
Date: 12 December 2017
Time: 1.30PM - 4:30PM
Duration: 15 minutes per participant
Number of Participants: 4
User Test: Click here for test instructions


Objectives

  • Allow users to verify the core functionalities (Uploading contracts and classifying them) of this web application are correct
  • To gather feedback on the charts used for visualization
  • To observe users' behaviour when using CtMS to extract key information from the contracts
  • To improve CtMS based on user feedback


Scope of UT 1

  • Upload Single Contract
  • Identification of Contract Type
  • Identification of Key Clauses
  • Identification of Entities and Contract Details
  • Auto/Manual-tagging of Contracts
  • Search for Contract
  • View Widgets on Dashboard


Procedures

Participants will be given a study consent to sign before commencing the testing. Once signed, they will be given a pre-test questionnaire and the instructions for user testing, where they will fill up the questionnaire and start the user testing. Team All Stack will be there to help with technical issues as well as to observe the users. Upon completion of testing, users will complete a post-test questionnaire, providing their feedbacks.

S/N Goals Reached?
1 Users should be able to upload contract Goal reached. Users were able to complete the task
2 Users should be able to view contract details Goal reached. Users were able to complete the task.
3 Users should be able to search for contracts Goal reached. Users were able to complete the task
4 Users should be able to view insights from dashboard (widgets only) Goal reached. Users were able to complete the task


Key Findings

Functions User's Comments Changes to Be Made
Function Refinement Users requested to add an “Others” contract type for other miscellaneous contract types All Stack will add in an “Others” contract type for those contracts uploaded that is not NDA, Employee or Talent contract
Function Refinement Users requested for an email notification providing them with weekly summary of the contracts they have All Stack will be implementing a notification module in future iterations
Function Refinement Users requested for a way to cancel the upload when it’s taking too long to upload All Stack will add a cancel button or timeout the page when the upload takes too long
Function Refinement Users requested for a way to view the number of exclusive and non-exclusive contracts All Stack will add a widget in the dashboard showing the values respectively
Function Refinement Users requested for a dynamic chart where they can select certain tags and the chart’s data changes accordingly All Stack will add in a chart with a dropdown list of tags for users to select and the chart will change accordingly


Overall Results/Comments

  • Sponsor is satisfied with the team’s progress and achievements


UT 2


Test Plan

Venue: Gushcloud HQ @ 10 Central Exchange Green
Date: 6 February 2018
Time: 4.30PM – 6.15PM
Duration: 15 minutes per participant
Number of Participants: 4
User Test: Click here for test instructions


Objectives

  • Allow users to verify the core functionalities
  • Gather feedback on accuracy of contract type detection
  • To gather feedback on functionalities developed
  • Detect usability issues when using application


Scope of UT 2

  • Upload Zipped File of Contracts
  • Verify Key Contract Details from Batch Upload
  • Search for Contracts
  • Edit Contracts’ Details
  • Reupload New Version of Existing Contracts
  • View Version Control Log for Contracts
  • Change Access Rights of Users
  • View Expiring Contracts from Dashboard


Procedures

Participants will be given a study consent to sign before commencing the testing. Once signed, they will be given a pre-test questionnaire and the instructions for user testing, where they will fill up the questionnaire and start the user testing. Team All Stack will be there to help with technical issues as well as to observe the users. Upon completion of testing, users will complete a post-test questionnaire, providing their feedbacks.

S/N Goals Reached?
1 Users (as admin) should be able to edit access rights of other employees Goal reached. Users were able to complete the task
2 Users should be able to upload a zipped file of contracts Goal reached. Users were able to complete the task.
3 Users should be able to edit existing contracts and view the version log Goal reached. Users were able to complete the task
4 Users should be able to easily navigate between pages to perform tasks Goal reached. Users were able to complete the task without need for clarifications
5 Contract type detected should be at least 75% accurate Goal reached. 21 out of 24 contracts (87.5%) uploaded were accurate


Key Findings

Functions User's Comments Changes to Be Made
Function Refinement Users requested to add more names for parties involved upon uploading of contract All Stack will modify the system to facilitate displaying multiple names for users to add as parties involved in the verifying contract details page
Function Refinement Users requested for more tags to be identified by the system upon uploading of contract All Stack will add in the list of tags (will be provided by users) to facilitate the identification of tags
Functions User's Behaviour Changes to Be Made
User Interface Users were confused about editing contracts because upon clicking the edit icon from search results page, they didn’t know that they were required to click “Edit” again to enter edit mode (All Stack did this to ensure users would not accidentally make unwanted edits) All Stack will edit the font colours for all the text fields (to make it lighter when in disabled mode) and additionally add in a notification to alert users when they are in edit/view mode


Overall Results/Comments

  • Sponsor is satisfied with changes made based on UT 1’s feedbacks
  • Sponsor is happy with the team’s progress and achievements
UT 3


Test Plan

Venue: SMU SIS
Date: 18 March 2018
Time: Various Timings
Duration: 15 minutes per participant
Number of Participants: 20
User Test: Click here for test instructions


Objectives

  • Allow non-gushcloud employees to give feedback on the usability when using CtMS
  • To observe the user's behaviour when using CtMS
  • To improve CtMS based on user's feedbacks


Scope of UT 3

  • Upload Single Contract
  • Upload Zipped File of Contracts
  • Verify Key Contract Details from Batch Upload
  • Search for Contracts
  • Edit Contracts’ Details
  • View Version Control Log for Contracts


Procedures

Participants will be given the instructions for user testing, where they will read the scenarios provided and start the user testing. Team All Stack will be there to help with technical issues as well as to observe the users. Throughout the testing, users will provide their feedbacks either on the study tasks instructions or verbally and Team All Stack will document it.

S/N Goals Reached?
1 Uploading a single contract Goal reached. Users were able to complete the task
2 Uploading a batch of contracts Goal reached. Users were able to complete the task.
3 Searching for a contract Goal reached. Users were able to complete the task
4 Edit contract (with version control) Goal reached. Users were able to complete the task without need for clarifications


Key Findings

Functions User's Feedback/Suggestions Changes to Be Made
Function Refinement Should have a delete function to delete the entire batch upload All Stack will be implementing this in iteration 10
Function Refinement Should have a forget password function All Stack will be implementing this in iteration 10
Function Refinement Should include filter in search for users to only see contracts they have uploaded All Stack will be implementing this in iteration 10
Functions User's Behaviour Changes to Be Made
User Interface Users were confused about editing contracts because upon clicking the edit icon from search results page, they didn’t know that they were required to click “Edit” again to enter edit mode (All Stack did this to ensure users would not accidentally make unwanted edits) All Stack will edit the font colours for all the text fields (to make it lighter when in disabled mode) and additionally add in a notification to alert users when they are in edit/view mode


Overall Results/Comments

  • Sponsor is satisfied with changes made based on UT 1’s feedbacks
  • Sponsor is happy with the team’s progress and achievements