HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki 2017T2 Oops Metric"

From IS480
Jump to navigation Jump to search
Line 27: Line 27:
  
 
<br/>
 
<br/>
 +
 +
<!--Logo-->
 +
[[File:sirpotato.png|center|300px|]]<br>
 +
 +
<!--Header Start-->
 +
{|style="background-color:#1ebca3; border: 1px solid black; padding: 0 0 0 0" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |
 +
 +
| style=" text-align:center; border-right: 1px solid black" width="10%" |
 +
[[IS480 Team wiki: 2016T1 Potato |<font color="#F5F5F5" size=2><b>HOME</b></font>]] &nbsp; [[Image: potato.png|20px|link=]]
 +
 +
| style=" text-align:center;  border-right: 1px solid black" width="10%" |
 +
[[IS480 Team wiki: 2016T1 Potato Our Team|<font color="#F5F5F5" size=2><b>THE TEAM</b></font>]] &nbsp; [[Image: sweetpotato.png|20px|link=]]
 +
 +
| style=" text-align:center;  border-right: 1px solid black" width="12%" | 
 +
[[IS480 Team wiki: 2016T1 Potato Project Overview |<font color="#F5F5F5" size=2><b>PROJECT OVERVIEW</b></font>]] &nbsp; [[Image: potato2.png|25px|link=]]
 +
 +
| style=" text-align:center;  border-right: 1px solid black" width="12%" |
 +
[[IS480 Team wiki: 2016T1 Potato Project Management |<font color="#F5F5F5" size=2><b>PROJECT MANAGEMENT</b></font>]] &nbsp; [[Image: fries.png|25px|link=]]
 +
 +
| style=" text-align:center; background-color:#000000" width="10%" |
 +
[[IS480 Team wiki: 2016T1 Potato Documentation | <font color="#F5F5F5" size=2><b>DOCUMENTATION</b></font>]] &nbsp; [[Image: chipsss.png|25px|link=]]
 +
|}
 +
<!--Header End-->
 +
<!--SUB HEADER-->
 +
{|style=" width="100%; font-size:85%;" cellspacing="0" border="0" |
 +
| style="border-bottom: 1px solid black; border-left: 1px solid black; border-right: 1px solid #354458; text-align:center; background-color: #e9f0f6;" width="25%"  | [[IS480 Team wiki: 2016T1 Potato Documentation | Meeting Minutes]]
 +
 +
| style="border-bottom: 1px solid black; border-right: 1px solid black; text-align:center; background-color: #e9f0f6;" width="25%" | [[IS480 Team wiki: 2016T1 Potato User Testing| User Testing]]
 +
 +
| style="border-bottom: 1px solid black; border-right: 1px solid black; text-align:center; background-color: #e9f0f6;" width="25%" | [[IS480 Team wiki: 2016T1 Potato Diagrams| Diagrams]]
 +
 +
|}
 +
<!--SUB HEADER END-->
 
<br>
 
<br>
  
{| class="wikitable" align = "center"
+
==UT 1==
 +
===Test Plan===
 +
<b>Objectives</b><br>
 +
*To gather feedback regarding the current UI design and find ways to improve it<br>
 +
*To find out insights on problems they have when they are doing overseas business transactions
 +
<b>Users:</b> 3 business users<br/>
 +
<b>Venue:</b> SMU SIS GSR 3.1<br/>
 +
<b>Date:</b> 27 August 2016<br/>
 +
<b>Duration:</b> 15:00 - 17:00<br/>
 +
<b>Scope of UT1</b><br>
 +
# Create an account
 +
# Verify the account
 +
# Make a transfer request
 +
# View transfer details/statuses
 +
# Cancel matched transfers
 +
# Confirm a matched transfer
 +
# Transfer money to TranSwap
 +
<b>Procedure</b><br>
 +
*Users are given business goals and they are to use the system to achieve the goals. The team are there to observe.
 +
*At the end of UT, the team asks for feedback regarding users' behavior and suggestions for improvement.
 +
 
 +
===Results/Comments===
 +
*Since the service involves real money transaction, there need to be visibility and clarity on market rate even before signing up.
 +
*During making a transfer request, the clarity of market rate and exchanging amount is not good enough.
 +
*Some colors like neon green are hard to see.
 +
*Making a transfer request is quite confusing.
 +
*Having a choice to confirm booking once matched and having to re-request the booking once unmatched can be quite troublesome.
 +
 
 +
===Changes To Be Made===
 +
*Re-organize the process flow and sitemap
 +
<!-- {| class="wikitable" width="100%"
 
|-
 
|-
! Risk Description
+
! Changes made
! Consequences
+
! Before
! Likelihood
+
! After
! Impact
 
! Mitigation Plan
 
 
|-
 
|-
| The sponsor may have a different change of plans
+
|
| This results in a scope creep and as a result the team mission and schedule might have to different thus jeopardising the delivery of other applications
+
|
| Medium
+
|
| High
 
| The client will understand the feasibility based on the change management logs. If the change is highly critical, negotiate for the changes and revise the schedule accordingly. The change will be rejected if the team is unable to handle the workload
 
 
|-
 
|-
 +
|} -->
 +
 +
===GPS Module===
 +
{| class="wikitable" width="100%"
 
|-
 
|-
| Roles and responsibilities not clearly defined
+
! width=20% style="padding: 8px; text-align: center; background:#1d4c5d; color:#ffffff; font-size: 14px;"| Changes made
|
+
! width=40% style="padding: 8px; text-align: center; background:#1d4c5d; color:#ffffff; font-size: 14px;"| Before
| Low
+
! width=40% style="padding: 8px; text-align: center; background:#1d4c5d; color:#ffffff; font-size: 14px;"| After
| Low
 
| The documentation has to detail all the changes and roles clearly. Handover of the task is important and proper time allocation is necessary
 
 
|-
 
|-
 +
|1)Redesign the entire GPS Lookup page to demonstrate the right location
 +
|[[Image: |center|400px]]
 +
|rowspan="2"|[[Image: |center|400px]]
 
|-
 
|-
| Timeline estimates are unrealistic
+
|2)Unable to find users, end result is that you stalk the user on the map.
| The tasks that are completed in one iteration will thus spill over, resulting in unnecessary delay and compromising the time schedule
+
|[[Image: |center|400px]]
| High
 
| High
 
| The team will discuss the timeline and progress together
 
 
|-
 
|-
 +
|}
 +
 +
==UAT 1==
 +
===Test Plan===
 +
<b>Objectives</b><br>
 +
*To ensure that our system can handle required tasks and support business process after integrating and modifying the Ruby on Rails MVP
 +
<b>Tester:</b> 2 TranSwap Sponsors<br/>
 +
<b>Venue:</b> SMU IIE<br/>
 +
<b>Date:</b> 25 September 2016<br/>
 +
<b>Duration:</b> 15:00 - 17:00<br/>
 +
<b>Scope of UAT 1</b><br>
 +
# Transfer Module
 +
# Admin Module
 +
# Matching Module
 +
# Liquidity Module
 +
# Client MVP integration (exiting functions)
 +
 +
===Results/Comments===
 +
[[File:Is480-potato-UAT1.jpg|500px|frameless]]<br>
 +
[[File:User Acceptance Test Checklist.docx]]
 +
 +
Sponsors are satisfied with the application thus far. However, there are a few functional bugs. Majority of the bugs is related to cosmetics and sponsor's preference in information organization. We have fixed these bugs Iteration 9.
 +
 +
==UT 2==
 +
===Test Plan===
 +
<b>Objectives</b><br>
 +
*To assess usability of new changes for transfer user interface<br>
 +
*To gain insights regarding the transfer process
 +
<b>Users:</b> 3 business users<br/>
 +
<b>Venue:</b> SMU IIE<br/>
 +
<b>Date:</b> 3 October 2016<br/>
 +
<b>Duration:</b> 10:00 - 11:00<br/>
 +
<b>Scope of UT 2</b><br>
 +
# Make a transfer request
 +
# View transfer details/statuses
 +
# Cancel matched transfers
 +
# Confirm a matched transfer
 +
<b>Procedure</b><br>
 +
*Users are given business goals and they are to use the system to achieve the goals. The team are there to observe.
 +
*At the end of UT, the team asks for feedback regarding users' behavior and suggestions for improvement.
 +
 +
===Results/Comments===
 +
# Requesting for a transfer is straighforwards and clear.
 +
# Users take sometime to find a way to go back to main page after confirming the transfer.
 +
# Good to have estimated waiting time to match.
 +
# Making payment to TranSwap is troublesome because the payment can't be done via the website.
 +
 +
===Changes To Be Made===
 +
*Add a "back to main page" button in confirm page
 +
<!-- {| class="wikitable" width="100%"
 
|-
 
|-
| Team is not familiar with features of Android/R programming
+
! Changes made
| Project delays due to incorrect estimates and lower quality as there will be more bugs
+
! Before
| High
+
! After
| High
 
| Team to be trained before iteration 2 for Android programming and before iteration 4 R programming
 
 
|-
 
|-
 +
|
 +
|
 +
|
 
|-
 
|-
| GPS Function – Parsing the location data into the system
+
|} -->
| Team members don’t know which function belongs to which member
+
 
| High
+
===Transfer Module===
| High
+
{| class="wikitable" width="100%"
| Team to be trained in the aspects of Geo-location tagging before iteration 4
 
 
|-
 
|-
 +
! width=20% style="padding: 8px; text-align: center; background:#1d4c5d; color:#ffffff; font-size: 14px;"| Changes made
 +
! width=40% style="padding: 8px; text-align: center; background:#1d4c5d; color:#ffffff; font-size: 14px;"| Before
 +
! width=40% style="padding: 8px; text-align: center; background:#1d4c5d; color:#ffffff; font-size: 14px;"| After
 
|-
 
|-
 +
|Confirm transfer - Add "back" button to ease navigation to main page.
 +
|[[Image: Potato_confirm_transfer.jpg|center|400px]]
 +
|rowspan="2"|[[Image: Potato_new_confirm_transfer.jpg|center|400px]]
 +
|}
 +
 +
==UT 3==
 +
===Test Plan===
 +
<b>Objectives</b><br>
 +
*To assess usability of new changes for transfer user interface<br>
 +
*To find out how we can better provide information to help users decide whether request transfer
 +
<b>Users:</b> <br/>
 +
<b>Venue:</b> SMU IIE<br/>
 +
<b>Date:</b> 26 October 2016<br/>
 +
<b>Duration:</b> 10:30 - 11:30<br/>
 +
<b>Scope of UT 3</b><br>
 +
# Make a transfer request
 +
# View transfer details/statuses
 +
# Cancel matched transfers
 +
# Confirm a matched transfer
 +
# Exchange rate graph
 +
<b>Procedure</b><br>
 +
*Users are given 2 different version to test.
 +
*Users are given business goals and they are to use the system to achieve the goals. The team are there to observe.
 +
*While users are at "request transfer" page, users are to answer questions regarding information on exchange rate at the left panel.
 +
*At the end of part UT, the team asks for feedback regarding ease of finding information, users' behavior and suggestions for improvement.
 +
 +
===Results/Comments===
 +
 +
 +
===Changes To Be Made===

Revision as of 17:28, 6 November 2016

Oopslogo.png
HomeButton.png Home ShakeHands.png About Us Glyphicons 042 pie chart.png Project Overview Calendaricon.png Project Management Tableicon.png Project Documentation


Schedule Risk Management Change Management Task Metrics Bug Metrics


Sirpotato.png


HOME   Potato.png

THE TEAM   Sweetpotato.png

PROJECT OVERVIEW   Potato2.png

PROJECT MANAGEMENT   Fries.png

DOCUMENTATION   Chipsss.png

Meeting Minutes User Testing Diagrams


UT 1

Test Plan

Objectives

  • To gather feedback regarding the current UI design and find ways to improve it
  • To find out insights on problems they have when they are doing overseas business transactions

Users: 3 business users
Venue: SMU SIS GSR 3.1
Date: 27 August 2016
Duration: 15:00 - 17:00
Scope of UT1

  1. Create an account
  2. Verify the account
  3. Make a transfer request
  4. View transfer details/statuses
  5. Cancel matched transfers
  6. Confirm a matched transfer
  7. Transfer money to TranSwap

Procedure

  • Users are given business goals and they are to use the system to achieve the goals. The team are there to observe.
  • At the end of UT, the team asks for feedback regarding users' behavior and suggestions for improvement.

Results/Comments

  • Since the service involves real money transaction, there need to be visibility and clarity on market rate even before signing up.
  • During making a transfer request, the clarity of market rate and exchanging amount is not good enough.
  • Some colors like neon green are hard to see.
  • Making a transfer request is quite confusing.
  • Having a choice to confirm booking once matched and having to re-request the booking once unmatched can be quite troublesome.

Changes To Be Made

  • Re-organize the process flow and sitemap

GPS Module

Changes made Before After
1)Redesign the entire GPS Lookup page to demonstrate the right location [[Image: |center|400px]] [[Image: |center|400px]]
2)Unable to find users, end result is that you stalk the user on the map. [[Image: |center|400px]]

UAT 1

Test Plan

Objectives

  • To ensure that our system can handle required tasks and support business process after integrating and modifying the Ruby on Rails MVP

Tester: 2 TranSwap Sponsors
Venue: SMU IIE
Date: 25 September 2016
Duration: 15:00 - 17:00
Scope of UAT 1

  1. Transfer Module
  2. Admin Module
  3. Matching Module
  4. Liquidity Module
  5. Client MVP integration (exiting functions)

Results/Comments

Is480-potato-UAT1.jpg
File:User Acceptance Test Checklist.docx

Sponsors are satisfied with the application thus far. However, there are a few functional bugs. Majority of the bugs is related to cosmetics and sponsor's preference in information organization. We have fixed these bugs Iteration 9.

UT 2

Test Plan

Objectives

  • To assess usability of new changes for transfer user interface
  • To gain insights regarding the transfer process

Users: 3 business users
Venue: SMU IIE
Date: 3 October 2016
Duration: 10:00 - 11:00
Scope of UT 2

  1. Make a transfer request
  2. View transfer details/statuses
  3. Cancel matched transfers
  4. Confirm a matched transfer

Procedure

  • Users are given business goals and they are to use the system to achieve the goals. The team are there to observe.
  • At the end of UT, the team asks for feedback regarding users' behavior and suggestions for improvement.

Results/Comments

  1. Requesting for a transfer is straighforwards and clear.
  2. Users take sometime to find a way to go back to main page after confirming the transfer.
  3. Good to have estimated waiting time to match.
  4. Making payment to TranSwap is troublesome because the payment can't be done via the website.

Changes To Be Made

  • Add a "back to main page" button in confirm page

Transfer Module

Changes made Before After
Confirm transfer - Add "back" button to ease navigation to main page.
Potato confirm transfer.jpg
Potato new confirm transfer.jpg

UT 3

Test Plan

Objectives

  • To assess usability of new changes for transfer user interface
  • To find out how we can better provide information to help users decide whether request transfer

Users:
Venue: SMU IIE
Date: 26 October 2016
Duration: 10:30 - 11:30
Scope of UT 3

  1. Make a transfer request
  2. View transfer details/statuses
  3. Cancel matched transfers
  4. Confirm a matched transfer
  5. Exchange rate graph

Procedure

  • Users are given 2 different version to test.
  • Users are given business goals and they are to use the system to achieve the goals. The team are there to observe.
  • While users are at "request transfer" page, users are to answer questions regarding information on exchange rate at the left panel.
  • At the end of part UT, the team asks for feedback regarding ease of finding information, users' behavior and suggestions for improvement.

Results/Comments

Changes To Be Made