HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2018T1 analyteaka usertesting"

From IS480
Jump to navigation Jump to search
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<center>
 
  
 
<!--HEADER-->
 
<!--HEADER-->
Line 30: Line 29:
 
<!--SUB MENU-->
 
<!--SUB MENU-->
 
{| class="wikitable;style="background-color:white; color:white padding: 5px 0 0 0;" width="100%" height=50px cellspacing="0" cellpadding="0" valign="top" border="0"  
 
{| class="wikitable;style="background-color:white; color:white padding: 5px 0 0 0;" width="100%" height=50px cellspacing="0" cellpadding="0" valign="top" border="0"  
| style="vertical-align:top;width:16.67%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:1px">[[IS480 Team wiki: 2018T1 analyteaka Documentation | <font color="#35332E"><b>MEETING MINUTES</b></font>]]  
+
| style="vertical-align:top;width:14%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:1px">[[IS480 Team wiki: 2018T1 analyteaka Documentation | <font color="#35332E"><b>MEETING MINUTES</b></font>]]  
| style="vertical-align:top;width:16.67%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:1px"> [[IS480_Team_wiki:_2018T1_ analyteaka_diagrams | <font color="#35332E"><b>DIAGRAMS</b></font>]]  
+
| style="vertical-align:top;width:14%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:1px"> [[IS480_Team_wiki:_2018T1_ analyteaka_diagrams | <font color="#35332E"><b>DIAGRAMS</b></font>]]  
| style="vertical-align:top;width:16.67%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:1px"> [[IS480_Team_wiki:_2018T1_ analyteaka_personaandscenario | <font color="#35332E"><b>PERSONA AND SCENARIO</b></font>]]  
+
| style="vertical-align:top;width:14%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:1px"> [[IS480_Team_wiki:_2018T1_ analyteaka_personaandscenario | <font color="#35332E"><b>PERSONA AND SCENARIO</b></font>]]  
| style="vertical-align:top;width:16.67%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:1px"> [[IS480_Team_wiki:_2018T1_ analyteaka_prototype | <font color="#35332E"><b>PROTOTYPE</b></font>]]  
+
| style="vertical-align:top;width:14%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:1px"> [[IS480_Team_wiki:_2018T1_ analyteaka_prototype | <font color="#35332E"><b>PROTOTYPE</b></font>]]  
| style="vertical-align:top;width:16.67%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:3px solid #7D5B53; "> [[IS480_Team_wiki:_2018T1_ analyteaka_usertesting | <font color="#35332E"><b>USER TESTING</b></font>]]  
+
| style="vertical-align:top;width:14%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:3px solid #7D5B53; "> [[IS480_Team_wiki:_2018T1_ analyteaka_usertesting | <font color="#35332E"><b>USER TESTING</b></font>]]  
| style="vertical-align:top;width:16.67%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:1px"> [[IS480_Team_wiki:_2018T1_ analyteaka_deliverables | <font color="#35332E"><b>DELIVERABLES</b></font>]]
+
| style="vertical-align:top;width:14%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:1px"> [[IS480_Team_wiki:_2018T1_ analyteaka_deliverables | <font color="#35332E"><b>DELIVERABLES</b></font>]]
 
|}
 
|}
 
<!--SUB MENU-->
 
<!--SUB MENU-->
Line 42: Line 41:
  
 
<!--CONTENT-->
 
<!--CONTENT-->
 +
<center>
 +
{|
 +
|[[Image: Analyteaka_UserTestingRound1.png|center|200px|link=https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2018T1_analyteaka_UT1]]
 +
|[[Image: Analyteaka_UserTestingRound2.png|center|200px|link=https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2018T1_analyteaka_UT2]]
 +
|[[Image: Analyteaka_UserTestingRound3.png|center|200px|link=https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2018T1_analyteaka_UT3]]
 +
|}
 +
</center>
 +
 
[[File:Analyteaka Testplan.png|1000px|center]]
 
[[File:Analyteaka Testplan.png|1000px|center]]
  
 
<b>Objective and Scope </b>
 
<b>Objective and Scope </b>
  
User testing is conducted on every functionality that has been implemented and completed till date. The objective of testing in every iteration is to  1) identify the presence of bugs, 2) any irregularities in the application that were not previously discovered by the developers in the development phase, 3) user’s behaviour and expectation and 4) Accuracy of the data . To ensure performance consistency over different platforms, we conduct application testing on the following operating systems and browsers:
+
User testing is conducted on every functionality that has been implemented and completed till date. The objective of testing in every iteration is to   
 +
 
 +
1) identify the presence of bugs
 +
 
 +
2) any irregularities in the application that were not previously discovered by the developers in the development phase
 +
 
 +
3) user’s behaviour and expectation and  
 +
 
 +
4) Accuracy of the data .  
 +
 
 +
 
 +
To ensure performance consistency over different platforms, we conduct application testing on the following operating systems and browsers:
  
 
     <b>Operating Systems </b>
 
     <b>Operating Systems </b>
Line 55: Line 73:
  
 
<b>Testing Procedure </b>
 
<b>Testing Procedure </b>
 
  
 
The team ensure that functionalities implemented in the application are of the highest quality, by pushing codes that are tested to be working properly with the other modules. Hence, reducing the potential occurrence of bugs.
 
The team ensure that functionalities implemented in the application are of the highest quality, by pushing codes that are tested to be working properly with the other modules. Hence, reducing the potential occurrence of bugs.
Line 62: Line 79:
  
 
<b>Testing Schedule</b>
 
<b>Testing Schedule</b>
 
  
 
Integration and testing of the application occur simultaneously, allowing a more efficient, time-effective way of testing and ensuring the system isn’t broken.  
 
Integration and testing of the application occur simultaneously, allowing a more efficient, time-effective way of testing and ensuring the system isn’t broken.  
  
 
+
[[File:Analyteaka_Footer_Transparent.png|1000px|center]]
[[File:Analyteaka UserTesting1.png|1000px|center]]
 
<b>Venue: </b> SUNGEI KADUT HQ, 60 Sungei Kadut Drive Singapore 729569
 
 
 
<b>Date: </b>13 Aug 2018
 
 
 
<b>Time:</b> 1pm – 2pm
 
 
 
<b>Duration:</b> 60 minutes
 
 
 
<b>Number of Participants:</b> 3
 
 
 
<b>Objectives </b>
 
 
 
- Deduct usability issues based on users’ behaviour. 
 
 
 
- To gather feedback regarding user interface and the developed functions from existing user
 
 
 
- To improve web application based on the feedback
 
 
 
 
 
<b>Procedures </b>
 
 
 
Participants are to think aloud as they follow through the instructions given for the user testing. The team will be there to record down the participants. Participants are to leave their feedback at the end of their user testing. The team will conclude the user testing by asking the participants question with regards to their behaviours and thought process.
 
 
 
{| class="wikitable"
 
|-
 
! S/N !! Goal !! Reached?
 
|-
 
| 1 || Participants should be able to tell what’s the sales amount the top 3 outlets || Reached
 
|-
 
| 2 || Participants should be able to tell what’s the best selling item category in Suntec outlet || Reached
 
|-
 
| 3 || Participants should be able to see what category of customer visit which outlets || Reached
 
|-
 
| 4 || Participants should agree with the result of the customer segment that visits a specific store outlet (Suntec)  || Reached
 
|-
 
| 5 || Participants should agree that the result that the store’s best-selling item/date is as shown.|| Reached
 
|-
 
| 6 || Participants should be able to find and view the revenue for week 52 for 2017 || Reached
 
|-
 
| 7 || Rate the overall UI design? Scale of 1-5, 1 being bad, 5 being perfect .Goal is 3  || Reached (3,3,4)
 
|-
 
| 8 || Rate the overall ease of use? Scale of 1-5, 1 being very difficult, 5 being very easy. Goal is 3. || Reached (3,4,4)
 
|-
 
| 9 || How useful is the dashboard ? On a scale of 1-5, 1 being bad, 5 being perfect. Goal is 3.  || Reached (4,4,5)
 
|}
 
 
 
 
 
<b> Key Finding </b>
 
 
 
{| class="wikitable"
 
|-
 
! Functions  !! Users' Comments !! Changes to be made
 
|-
 
| User Interface – store || User was able to identify top store quickly just by glancing at the data.  || NA
 
|-
 
| User Interface - bootstrap || User was able to upload the files successfully without being provided any instruction || NA
 
|-
 
| User Interface - bootstrap || User wasn’t sure how many records were upload as only error was shown || To add in a summary page containing the number of records being upload successfully.
 
|-
 
| User interface - store || User mention they may have additional item category in the future, wondering how would they be able to add new category or category?  || Add a setting page to manage the category and sub category
 
|-
 
| User interface - store || User was wondering how to reset the view || Add a reset button to reset the view
 
|-
 
| User interface - store || User was wondering what’s the start date of week 50  || Change week number to start date of the week
 
|}
 
 
 
<b> Others </b>
 
 
 
{| class="wikitable"
 
|-
 
! Subject  !! Users' Comments  !! Changes to be made
 
|-
 
| Function Refinement || Sales data - Would like to know the time the item is being sold to adjust manpower || Will change charts to stack barchart to sort by day and hours
 
|-
 
| Function Refinement || Not sure what profile A,B,C,D for customer means || To specify what specific profile means / add settings page for user to define profile name
 
|-
 
| Additional Request || Marketing campaign project recommendation tools  with Inputs (store, item category, target segmentation, payment methods and specific days) || Adding of marketing campaign project recommendation page to the system 
 
|-
 
| Feedback || User feel that 1) the tools can help to reduce planning time, marketing time and cost. 2) Improve the way/accuracy they plan their marketing campaigns with limited marketing budget. 3) Provide better training for new sales staff based on the data  || NA
 
|}
 
<b>Overall Results/comments </b>
 
 
 
 
 
To conclude, the users like what was being shown and feel the things we have shown would have a major impact on the company’s operation and improve business process effectiveness. However,  such an application would require a continuous iterative cycle for feedback and improvement. As such, we will be providing them access to the live server by iteration 8 (early September) for constant feedback prior to midterms.
 
 
 
 
 
To meet the above user’s request and function refinement. We would require an update to our schedule planning.
 
 
 
  
 
<!--CONTENT-->
 
<!--CONTENT-->

Latest revision as of 14:43, 9 October 2018

Analyteaka Header.png


HOME

ABOUT US

PROJECT OVERVIEW

PROJECT MANAGEMENT

DOCUMENTATION



Analyteaka UserTestingRound1.png
Analyteaka UserTestingRound2.png
Analyteaka UserTestingRound3.png
Analyteaka Testplan.png

Objective and Scope

User testing is conducted on every functionality that has been implemented and completed till date. The objective of testing in every iteration is to

1) identify the presence of bugs

2) any irregularities in the application that were not previously discovered by the developers in the development phase

3) user’s behaviour and expectation and

4) Accuracy of the data .


To ensure performance consistency over different platforms, we conduct application testing on the following operating systems and browsers:

    	Operating Systems 
    •	Windows 10.1 
    •	Mac OS High Sierra (10.13.5) / Windows 10.1  
    	Browsers 
    •	Google Chrome 

Testing Procedure

The team ensure that functionalities implemented in the application are of the highest quality, by pushing codes that are tested to be working properly with the other modules. Hence, reducing the potential occurrence of bugs.

We also dedicated 1-2 days at the end of each iteration for manual final testing, locally and on Google Cloud. The team’s quality assurance will test out each module to ensure the integration was completed successfully. If bugs/errors has been identified, the quality assurance will alert the PM and update the bug-tracking excel sheet.

Testing Schedule

Integration and testing of the application occur simultaneously, allowing a more efficient, time-effective way of testing and ensuring the system isn’t broken.

Analyteaka Footer Transparent.png