HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T2 Team Prime Final Wiki"

From IS480
Jump to navigation Jump to search
 
(32 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
[[Image:PrimeLogo.png|880px|right]]<br>
 
[[Image:PrimeLogo.png|880px|right]]<br>
  
==<font color="#843A36">'''Project Progress Summary'''</font>==
+
==<font color="#794721">'''Project Progress Summary'''</font>==
  
<!--
 
 
===<font color="#FC6B2A">Project Overview</font>===
 
===<font color="#FC6B2A">Project Overview</font>===
 
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
 
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
|scope="row"  width="700" style="text-align: left; background: #FFFFFB"|
+
|scope="row"  width="800" style="text-align: left; background: #FFFFFB"|
<big>[http://www.swimix.com <span style="color:#843A36">'''Swimix'''</span>]</big>&nbsp;&nbsp;&nbsp;&nbsp;
+
<big>[https://wiki.smu.edu.sg/w/is480/images/e/e0/Prime_FYP_Final_Presentation_Final.pdf <span style="color:#794721">'''Final Presentation Slides'''</span>]</big><br><br>
<big>[https://wiki.smu.edu.sg/w/is480/images/0/03/Prime_Midterm_Presentation.pdf <span style="color:#843A36">'''Presentation Slides'''</span>]</big>
+
<big>[http://www.swimix.com <span style="color:#794721">'''Swimix Deployed Site Link'''</span>]</big>
#The team is currently at '''Sprint 5''' (31 Jan 2013 to 26 Feb 2013). View our [https://docs.google.com/spreadsheet/ccc?key=0AmZnvFmI-HxRdElXZk5rekwwRVNYdlN5WEpZanVzOWc#gid=8  <span style="color:#FC6B2A">sprint progress</span>].
+
#The team has completed '''8 sprints''' in total and is now finishing its final milestone.  
#Our first user test was conducted in Sprint 4. View our [[IS480_Team_wiki:_2012T2_Team_Prime_MidTerm_Wiki#Testing| <span style="color:#FC6B2A">user test results</span>]].
+
#We have completed all core, secondary, and tertiary features within our [[IS480_Team_wiki:_2012T2_Team_Prime_Project_Management#Project_Schedule|<span style="color:#F68832">'''<u>SCHEDULE</u>'''</span>]] as listed in the [[IS480_Team_wiki:_2012T2_Team_Prime_Project_Management#Priority_Circle|<span style="color:#F68832">'''<u>PRIORITY CIRCLE</u>'''</span>]].
#Our second user test will be conducted in Sprint 6 (tentatively 17 Mar 2013).
+
:[[Image:Prime_VideoIcon.png|20px]] View the interview with our celebrity endorser and Olympian swimmer Tao Li [http://www.youtube.com/watch?v=ibH7V9AnBbk <font color="#F68832"><u>'''here'''</u></font>]
#View our [http://www.youtube.com/watch?v=HFxRCajHzNA&feature=youtu.be <span style="color:#FC6B2A">Interview with Tao Li</span>], a national swimmer who is endorsing our platform.
+
:[[Image:Prime_VideoIcon.png|20px]] View our pitch [http://www.youtube.com/watch?v=Xkfz5XoCxwk <font color="#F68832">'''<u>here</u>'''</font>]. '''[NEW!]'''
The team is confident of completing the project within the schedule as shown below.
+
:[[Image:Prime_VideoIcon.png|20px]] View our User Test 1 video [http://www.youtube.com/watch?v=3qxlwTbQ0yk <font color="#F68832"><u>'''here'''</u></font>].
 +
:[[Image:Prime_VideoIcon.png|20px]] View our User Test 2 video [http://youtu.be/0_z5cePuaOU <font color="#F68832"><u>'''here'''</u></font>]. '''[NEW!]'''
 
|}
 
|}
-->
+
<br>
 
+
'''This is where we are on the timeline:'''<br>
 
[[Image:Prime_ProjectMilestones_WeAreHere_V0.2.png]]<br>
 
[[Image:Prime_ProjectMilestones_WeAreHere_V0.2.png]]<br>
  
 
===<font color="#FC6B2A">Project Highlights</font>===
 
===<font color="#FC6B2A">Project Highlights</font>===
<br>
+
{|class="wikitable"
'''Highlight 1''': Confirmation of endorsement from Tao Li who has represented Singapore in many international swimming competitions including the Beijing and London Olympics.<br>
+
|+
'''Highlight 2''': Manage Reviews and Manage Users’ Reviews was replaced with Manage Evaluations<br>
+
|-
'''Highlight 3''': In Sprint 3, there was a spike in the number of bugs found, due to the fact that more rigorous testing was conducted on the application to prepare for User Test 1 in the Sprint 4. <br>
+
! scope="col" width="100" style="background-color:#794721"| <font color="#ffffff">Event</font>
 +
! scope="col" width="300" style="background-color:#794721"| <font color="#ffffff">Highlights / Issue Description</font>
 +
 
 +
|-
 +
! scope="row" style="background-color:#FFFFFB"|<font color="#222222">Sprint 6</font>
 +
|
 +
:'''Instructor web mobile feature dropped'''<br>
 +
:Due to the slow progression made, the team decided to drop the instructor web mobile feature in order to bring the project back on schedule.<br><br>
 +
:'''Integration of payment feature pushed to Sprint 7''' <br>
 +
:Towards the end of the sprint, the team encountered difficulties with integrating the payment feature. Hence, the team decided to bring forward the integration to the next sprint.
  
 +
|-
 +
! scope="row" style="background-color:#FFFFFB"|<font color="#222222">Sprint 7</font>
 +
|
 +
:'''Swim school features dropped'''<br>
 +
:The team faced difficulties in implementing the payment feature. To focus our efforts on finishing up the payment feature, the team decided to drop the swim school feature. A secondary reason is that swim schools are not the main target market for Swimix.
 +
|}
 +
<!--
 
===<font color="#FC6B2A">Project Challenges</font>===
 
===<font color="#FC6B2A">Project Challenges</font>===
 +
Type here
 
<br>
 
<br>
 +
-->
  
 
===<font color="#FC6B2A">Project Achievements</font>===
 
===<font color="#FC6B2A">Project Achievements</font>===
 +
# Secured Singapore Olympian swimmer Tao Li as our celebrity sponsor. View our interview with her [http://www.youtube.com/watch?v=ibH7V9AnBbk <font color="#F68832">'''<u>HERE</u>'''</font>].
 +
# Successfully conducted 2 rounds of [[IS480_Team_wiki:_2012T2_Team_Prime_Usability_Tests |<span style="color:#F68832">'''<u>USER TESTS</u>'''</span>]] at Yishun Swimming Complex and Sengkang Swimming Complex, with a total of 38 users and 7 swimming instructors.
 +
# Received confirmation of investment on Swimix from investor Dr Virginia Cha, who is also one of our [[IS480_Team_wiki:_2012T2_Team_Prime_Stakeholders#Project_Advisors|<span style="color:#F68832">'''<u>PROJECT ADVISORS</u>'''</span>]] from SMU Institute of Innovation & Entrepreneurship.
 
<br>
 
<br>
  
==<font color="#843A36">'''Project Management'''</font>==
+
==<font color="#794721">'''Project Management'''</font>==
  
  
 
===<font color="#FC6B2A">Schedule (Planned Vs Actual)</font>===
 
===<font color="#FC6B2A">Schedule (Planned Vs Actual)</font>===
  
[[Image:Prime_Schedule_BeforeAfter.png]]
+
[[Image:Prime_Schedule_BeforeAfterV2.png|550px]]
<br><br>'''Note:'''
 
No significant changes have been made to the schedule with regards to the proposal and acceptance milestones.<br>
 
However, significant changes have been made to the project schedule in the subsequent four milestones as shown below.<br><br>
 
 
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
 
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
 
|scope="row"  width="1100" style="text-align: left; background: #FFFFFB"|
 
|scope="row"  width="1100" style="text-align: left; background: #FFFFFB"|
'''Changes Made'''<br>
+
Since the midterms, the '''following changes''' have been made to the project schedule:
#New user stories were added under the full Manage Search feature in the form of Manage Search (Instructor).
+
# Manage Notifications feature was brought forward to Sprint 6.
#Manage Users' Reviews and Manage Reviews feature was replaced with Manage Evaluations.  
+
# Integration of Payment feature was shifted from Sprint 6 to Sprint 7.
#Manage Class Registration feature was shifted to Midterm.  
+
# Sprint 7 was shifted earlier to the User Test 2 milestone.
#Manage Instructor Schedule and Manage Instructor Account web mobile features were shifted to User Test 2.  
+
# Instructor web mobile and Swim School features were dropped from Sprint 6 and Sprint 7 respectively.
#Manage Notifications, Manage Instructors, Manage Users, Manage Swim Schools, Manage Recruitment, Manage Data Analytics and Manage Enquiry features were shifted to Finals.
+
# Change of date for User Test 2 to 7 April 2013
#Manage Students' Progress and Manage Advertisements features were removed, shifted to Good-to-Have features.
 
 
|}
 
|}
 
<br>
 
<br>
Line 58: Line 75:
 
===<font color="#FC6B2A">Scope (Planned Vs Actual)</font>===
 
===<font color="#FC6B2A">Scope (Planned Vs Actual)</font>===
  
[[Image:Prime_Scope_BeforeAfter.png]]
+
[[Image:Prime_PriorityCircle_BeforeAfter.png]]
 
<br><br>
 
<br><br>
 
 
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
 
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
 
|scope="row"  width="1100" style="text-align: left; background: #FFFFFB"|
 
|scope="row"  width="1100" style="text-align: left; background: #FFFFFB"|
'''Version 1 (Original)'''
+
Since the midterms, the '''following changes''' have been made to the project scope:
:*Features are categorized in priority circles:
+
*The Instructor Web Mobile and Swim School features were re-prioritised as Good-to-Have features so that we can have a more manageable scope.  
::*Core, Secondary and Tertiary Features: Features which will be developed by Prime during IS480
+
|}<br><br>
::*Good-to-have Features: Features which are of lower priority and can be implemented in future beyond this project  
 
 
 
'''Version 2'''
 
:*'''Manage Students’ Progress''' was re-prioritised as a Tertiary feature since it is not the main focus of the IS480 project.
 
:*It was further re-prioritised as a Good-to-Have feature so that we can have a more manageable scope.
 
 
 
'''Version 3 (Latest)'''
 
:*'''Manage Reviews''' and '''Manage Users’ Reviews''' was replaced with '''Manage Evaluations'''
 
|}
 
  
 
===<font color="#FC6B2A">Project Metrics</font>===
 
===<font color="#FC6B2A">Project Metrics</font>===
  
 
====<font color="#222222">Schedule Metric</font>====
 
====<font color="#222222">Schedule Metric</font>====
 +
The diagrams below show the burndown charts and schedule ratio charts of Sprints 6 to 8 since the midterms.<br><br>
 +
<b><font color="#843A36">BURNDOWN CHARTS</font></b><br><br>
 +
[[Image:Prime_BurndownCharts_Sprints678.png]]<br><br>
  
The team has completed 5 sprints thus far, as shown in the burn down charts below.<br><br>
+
<b><font color="#843A36">SCHEDULE RATIO CHARTS</font></b><br><br>
<b><font color="#843A36">BURNDOWN CHARTS</font></b><br>
+
[[Image:Prime_ScheduleRatioCharts_Sprints678.png]]
[[Image:Sprints1to4.png|800px]]<br>
 
[[Image:Sprint5.png]]
 
 
 
<b><font color="#843A36">SCHEDULE RATIO CHARTS</font></b><br>
 
[[Image:ScheduleRatios_Sprints1234.png|800px]]<br>
 
[[Image:ScheduleRatio_Sprint5.png|400px]]
 
  
 
<b><font color="#843A36">KEY ISSUES</font></b><br>
 
<b><font color="#843A36">KEY ISSUES</font></b><br>
Line 93: Line 97:
 
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
 
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
 
|scope="row"  width="1000" style="text-align: left; background: #FFFFFB"|
 
|scope="row"  width="1000" style="text-align: left; background: #FFFFFB"|
'''Sprint 3:'''<br>
+
'''Sprint 6:'''<br>
#During December, the team met up every Monday to Thursday to complete tasks assigned. On 21 Dec, the calculated schedule ratio indicated that the team was behind schedule. We found out that the Manage Search (Instructors) feature needed more time to be completed. To get back on schedule, the team decided to shift the Manage Reviews feature to Sprint 4.
+
# On 12 Mar, the burndown chart indicated that the team was behind schedule. This was due to the slow progression of the team. The team decided to drop the instructor web mobile feature in order to bring the project back on schedule.
#On 27 Dec, the logic for Manage Search (i) feature was working but the feature had many alignment issues. The team also realised that we were behind schedule. To get back on track, we shifted the Update feature for Manage Class Registration to Sprint 4.<br><br>
+
# Towards the end of the sprint, the team encountered difficulties with integrating the payment feature. Hence, the team decided to bring forward the integration to the next sprint (Sprint 7).<br><br>
 
 
'''Sprint 4:'''<br>
 
#On 10 Jan, the team met Dr. Miles Gilman (Entrepreneur-in-Residence, SMU Institute of Innovation and Entrepreneurship) for advice on improving our business plan for the ACE Startup Grant application.
 
#On 11 Jan, we consolidated all the changes to be made and realized that there were many changes to be made. The burndown chart also indicated that we were behind schedule. Hence, for the next 4 days, we dedicated much time and effort to get back on track. We decided to put our focus on the ACE submission which was in two weeks' time, therefore we shifted two features (Manage Recruitment and Manage Swim Schools) to future sprints.
 
#Since then, the team made slow progress on the features and eventually on 17 Jan, the burndown chart indicated that we were running behind schedule. The team decided to shift another two features (Manage Instructors and Manage Users) to future sprints.
 
#On 19 Jan, the burndown chart once again indicated that we were running behind schedule. The team decided to shift the Manage Notifications feature to future sprints.
 
#On 23 Jan, the team met with our supevisor Prof Lin Mei. After taking her feedback into consideration, we decided to replace the Manage Reviews feature and Manage User Reviews feature with Manage Evaluations which will be done at a later sprint.<br><br>
 
  
'''Sprint 5:'''<br>
+
'''Sprint 7:'''<br>
#From User Test 1, the team collected much valuable feedback from the participants and wanted to implement as much feedback as we could. Hence, we put much focus into doing this at the start of the sprint.
+
#1. On 23 Mar, the burndown chart indicated that the team was behind schedule. This was because the team faced difficulties in implementing the payment feature. To focus our efforts on finishing up the payment feature, the team decided to drop the swim school feature. Moreover, swim schools are not the main target market for Swimix.
#On 11 Feb, the team finalized the storyboarding based on the user test feedback, and realized that we needed more time to make changes. Since then, the team started moving away from the ideal progress line.
 
#On 17 Feb, the burndown chart indicated that the team was behind schedule. The team had an urgent meeting on 18 Feb to discuss our possible options. The outcome of the meeting was to prioritize the changes to be made from the user test feedback. We also managed our expectations for the remaining features before midterm.<br><br>
 
 
|}
 
|}
 
<br>
 
<br>
Line 117: Line 112:
 
[https://docs.google.com/spreadsheet/ccc?key=0AmZnvFmI-HxRdElXZk5rekwwRVNYdlN5WEpZanVzOWc#gid=7 <span style="color:#FC6B2A">Sprint 4 </span>]  
 
[https://docs.google.com/spreadsheet/ccc?key=0AmZnvFmI-HxRdElXZk5rekwwRVNYdlN5WEpZanVzOWc#gid=7 <span style="color:#FC6B2A">Sprint 4 </span>]  
 
[https://docs.google.com/spreadsheet/ccc?key=0AmZnvFmI-HxRdElXZk5rekwwRVNYdlN5WEpZanVzOWc#gid=8 <span style="color:#FC6B2A">Sprint 5</span>]
 
[https://docs.google.com/spreadsheet/ccc?key=0AmZnvFmI-HxRdElXZk5rekwwRVNYdlN5WEpZanVzOWc#gid=8 <span style="color:#FC6B2A">Sprint 5</span>]
 +
[https://docs.google.com/spreadsheet/ccc?key=0AmZnvFmI-HxRdElXZk5rekwwRVNYdlN5WEpZanVzOWc#gid=19 <span style="color:#FC6B2A">Sprint 6</span>]
 +
[https://docs.google.com/spreadsheet/ccc?key=0AmZnvFmI-HxRdElXZk5rekwwRVNYdlN5WEpZanVzOWc#gid=20 <span style="color:#FC6B2A">Sprint 7</span>]
 +
[https://docs.google.com/spreadsheet/ccc?key=0AmZnvFmI-HxRdElXZk5rekwwRVNYdlN5WEpZanVzOWc#gid=21 <span style="color:#FC6B2A">Sprint 8</span>]
 
<br><br>
 
<br><br>
  
 
====<font color="#222222">Bug Metric</font>====
 
====<font color="#222222">Bug Metric</font>====
  
[[Image:Prime_NoOfBugsFound_V2.png]]
+
[[Image:Prime_NoOfBugsFound_V3.png]]
 
<br>
 
<br>
 
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
 
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
 
|scope="row"  width="1000" style="text-align: left; background: #FFFFFB"|
 
|scope="row"  width="1000" style="text-align: left; background: #FFFFFB"|
 
'''Number of Bugs Found'''<br>
 
'''Number of Bugs Found'''<br>
#The chart on the left show the number of bugs found in each sprint. <br>
+
#The chart above shows the number of bugs found in each sprint. <br>
#In Sprint 3, there was a spike in the number of bugs found, due to the fact that more rigorous testing was conducted on the application to prepare for User Test 1 in the Sprint 4.  
+
#In Sprint 6, there was a slight spike in the number of bugs found (5), as more rigorous testing was conducted on the application to prepare for User Test 2 (originally scheduled in Sprint 7).  
 
|}
 
|}
 
<br>
 
<br>
[[Image:Prime_BugMetricSeverityChart_V2.png]]
+
[[Image:Prime_BugMetricSeverityChart_V3.png]]
 
<br>
 
<br>
 
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
 
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
Line 136: Line 134:
 
'''Total Bug Score'''<br>
 
'''Total Bug Score'''<br>
 
#The chart above shows the corresponding bug severity score with the number of bugs found in each sprint.<br>
 
#The chart above shows the corresponding bug severity score with the number of bugs found in each sprint.<br>
#The bug severity score in Sprint 3 was the highest out of all sprints due to the testing for User Test 1 as mentioned above.
+
#The bug severity score in Sprint 6 (13 points) was the highest out of Sprints 6 to 8 (after midterms) due to the testing for User Test 2 as mentioned above.
 
|}
 
|}
  
Line 142: Line 140:
 
|+  
 
|+  
 
|-
 
|-
! scope="col" width="150" style="background-color:#843A36"| <font color="#ffffff">Total Bug Score</font>
+
! scope="col" width="150" style="background-color:#794721"| <font color="#ffffff">Total Bug Score</font>
! scope="col" width="300" style="background-color:#843A36"| <font color="#ffffff">Action to be Taken</font>
+
! scope="col" width="300" style="background-color:#794721"| <font color="#ffffff">Action to be Taken</font>
  
 
|-
 
|-
! scope="row" style="background-color:none"|<font color="#222222">< 5</font>
+
! scope="row" style="background-color:#FFFFFB"|<font color="#222222">< 5</font>
 
|Developers resolve issues within the sprint.
 
|Developers resolve issues within the sprint.
  
 
|-
 
|-
! scope="row" style="background-color:none"|<font color="#222222"> 5 - 9</font>
+
! scope="row" style="background-color:#FFFFFB"|<font color="#222222"> 5 - 9</font>
 
|Resolve the bugs during the planned debugging time.
 
|Resolve the bugs during the planned debugging time.
  
 
|-
 
|-
! scope="row" style="background-color:none"|<font color="#222222">≥ 10</font>
+
! scope="row" style="background-color:#FFFFFB"|<font color="#222222">≥ 10</font>
 
|Stop current development and resolve the bugs immediately.  
 
|Stop current development and resolve the bugs immediately.  
 
|}
 
|}
Line 174: Line 172:
  
 
===<font color="#FC6B2A">Project Risks</font>===
 
===<font color="#FC6B2A">Project Risks</font>===
The top 3 risks are prioritised as follows::<br>
+
The top 3 risks are prioritised as follows:<br>
 
{|class="wikitable" style="text-align: center; color:#222222"  
 
{|class="wikitable" style="text-align: center; color:#222222"  
 
|+  
 
|+  
 
|-
 
|-
! scope="col" width="350" style="background-color:#843A36"| <font color="#ffffff">Risk</font>
+
! scope="col" width="200" style="background-color:#794721"| <font color="#ffffff">Risk</font>
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Probability</font>
+
! scope="col" width="100" style="background-color:#794721"| <font color="#ffffff">Probability</font>
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Impact</font>
+
! scope="col" width="100" style="background-color:#794721"| <font color="#ffffff">Impact</font>
! scope="col" width="350" style="background-color:#843A36"| <font color="#ffffff">Mitigation</font>
+
! scope="col" width="400" style="background-color:#794721"| <font color="#ffffff">Mitigation</font>
 
|-
 
|-
  
! scope="row" width="120" style="background-color:#f5f5f5; text-align:center;"|Many issues might be raised during user tests; time is required to rectify these issues
+
! scope="row" width="120" style="background-color:#FFFFFB; text-align:center;"|Low awareness of platform
 
|align="center"|High
 
|align="center"|High
|align="center"|Medium
+
|align="center"|High
|align="center"|Create a response plan document to help us decide whether to implement a change based on priority, complexity and time needed to rectify the issues.  
+
|align="left"|
 +
*We plan to mitigate this through aggressive marketing plans and celebrity endorsements.
  
 
|-
 
|-
! scope="row" width="120" style="background-color:#f5f5f5; text-align:center;"|Project contains numerous documentation and different versions. Inefficent access to a particular document.
+
! scope="row" width="120" style="background-color:#FFFFFB; text-align:center;"|Low usage of platform
 +
|align="center"|High
 
|align="center"|Low
 
|align="center"|Low
|align="center"|Medium
+
|align="left"|
|align="center"|Use a collaborative file management software (e.g. Google Documents, Dropbox) to organise respective folders of the project. Consensus amongst team members to adhere to proper version labelling.
+
*Tap on the power of previous customers’ networks and organize events to encourage signups
 +
*Incentivize users to sign up by giving referral discounts and rebates
  
 
|-
 
|-
! scope="row" width="120" style="background-color:#f5f5f5; text-align:center;"|Putting too much focus on fixing user interface issues compared to ensuring the system logic is working properly
+
! scope="row" width="120" style="background-color:#FFFFFB; text-align:center;"|Idea may be copied by others
 +
|align="center"|Low
 
|align="center"|High
 
|align="center"|High
|align="center"|Medium
+
|align="left"|
|align="center"|Prioritize the task according to the criteria and strike a balance between the two.
+
*Effectively leverage on the first mover advantage to capture the majority of the market share as fast as possible
 +
*More users = Higher value of the portal
 
|}
 
|}
  
View the full list of risks [[IS480_Team_wiki:_2012T2_Team_Prime_Risks#Risk_Management|<span style="color:#FC6B2A">here</span>]].
+
View the full list of risks [[IS480_Team_wiki:_2012T2_Team_Prime_Risks#Risk_Management|<span style="color:#FC6B2A">'''<u>HERE</u>'''</span>]].
  
 
===<font color="#FC6B2A">Technical Complexity</font>===
 
===<font color="#FC6B2A">Technical Complexity</font>===
 +
{|class="wikitable" style="text-align: center; color:#222222"
 +
|+
 +
|-
 +
! scope="col" width="250" style="background-color:#794721"| <font color="#ffffff">Area</font>
 +
! scope="col" width="480" style="background-color:#794721"| <font color="#ffffff">Description</font>
 +
|-
 +
 +
! scope="row" width="120" style="background-color:#FFFFFB; text-align:center;"|1. Improvements in Usability
 +
|align="left"|
 +
*Cross-browser compatibility
 +
 +
|-
 +
! scope="row" width="120" style="background-color:#FFFFFB; text-align:center;"|2. Improvements in Performance
 +
|align="left"|
 +
* Loading of user profile
 +
* Loading of instructor’s calendar
 +
* Search engine optimization
 +
:*Naming convention of class files
 +
:*Mapping on CodeIgniter framework (root folder)
 +
 +
|-
 +
! scope="row" width="120" style="background-color:#FFFFFB; text-align:center;"|3. Future Improvements
 +
|align="left"|
 +
*Internationalization
 +
*Localization
 +
*Payment security
 +
:*Responsiveness
 +
:*User profile
 +
*Instructor’s calendar
 +
:*Usability
 +
::*More data validation needed
 +
|}<br>
 +
 +
The following technical complexities have been listed in order of complexity (highest to lowest):<br><br>
 +
<big>'''Complexity 1: Calendar'''</big><br><br>
 +
 +
'''Load the Calendar:'''<br>
 +
[[Image:Prime_Calendar1.png]]
 +
 +
'''Load the Class:'''<br>
 +
[[Image:Prime_Calendar2.png]]
  
#PHP CodeIgniter 2.1.3
+
<big>'''Complexity 2: Payment'''</big><br><br>
::a. Understand the framework
+
 
::b. Apply the framework
+
'''Generate the Order Form:'''<br>
::c. Customize the code
+
[[Image:Prime_Payment1.png]]
::d. Debug the application
+
 
#Balance between the UI and code reusability
+
'''Confirm Order Form after Payment is Made:'''<br>
#Upload image
+
[[Image:Prime_Payment2.png]]
#Payment
+
 
#Shopping cart
+
<big>'''Complexity 3: Search Engine Optimization'''</big><br><br>
#Calendar
+
'''Search Engine Optimization:'''<br>
#Scope too big for us to handle
+
[[Image:Prime_SEO.png]]
  
 
==<font color="#843A36">'''Quality of Product'''</font>==
 
==<font color="#843A36">'''Quality of Product'''</font>==
Line 224: Line 268:
 
|+  
 
|+  
 
|-
 
|-
! scope="col" width="200" style="background-color:#843A36"| <font color="#ffffff">Stage</font>
+
! scope="col" width="200" style="background-color:#794721"| <font color="#ffffff">Stage</font>
! scope="col" width="200" style="background-color:#843A36"| <font color="#ffffff">Specification</font>
+
! scope="col" width="200" style="background-color:#794721"| <font color="#ffffff">Specification</font>
! scope="col" width="400" style="background-color:#843A36"| <font color="#ffffff">Modules</font>
+
! scope="col" width="400" style="background-color:#794721"| <font color="#ffffff">Modules</font>
 
|-
 
|-
! scope="row" rowspan="2" width="120" style="background-color:#f5f5f5; text-align:center;"|Project Management
+
! scope="row" rowspan="2" width="120" style="background-color:#FFFFFB; text-align:center;"|Project Management
 
|align="center"|Minutes
 
|align="center"|Minutes
 
|style="text-align="left"|
 
|style="text-align="left"|
Line 241: Line 285:
  
 
|-
 
|-
! scope="row" rowspan="2" width="120" style="background-color:#f5f5f5; text-align:center;"|Requirements
+
! scope="row" rowspan="2" width="120" style="background-color:#FFFFFB; text-align:center;"|Requirements
 
|align="center"|Product Backlog
 
|align="center"|Product Backlog
 
|style="text-align="left"|
 
|style="text-align="left"|
Line 247: Line 291:
  
 
|-
 
|-
|align="center"|Metrics
+
|align="center"|UI Mockups
 
|style="text-align="left"|
 
|style="text-align="left"|
 
*[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T2_Team_Prime_User_Interface<span style="color:#FC6B2A"> UI Mockups</span>]<br>
 
*[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T2_Team_Prime_User_Interface<span style="color:#FC6B2A"> UI Mockups</span>]<br>
  
 
|-
 
|-
! scope="row" rowspan="2" width="120" style="background-color:#f5f5f5; text-align:center;"|Analysis
+
! scope="row" rowspan="2" width="120" style="background-color:#FFFFFB; text-align:center;"|Analysis
 
|align="center"|Use Case
 
|align="center"|Use Case
 
|style="text-align="left"|
 
|style="text-align="left"|
Line 263: Line 307:
  
 
|-
 
|-
! scope="row" rowspan="2" width="120" style="background-color:#f5f5f5; text-align:center;"|Design
+
! scope="row" rowspan="3" width="120" style="background-color:#FFFFFB; text-align:center;"|Design
 
|align="center"|ER Diagram
 
|align="center"|ER Diagram
 
|style="text-align="left"|
 
|style="text-align="left"|
Line 274: Line 318:
  
 
|-
 
|-
! scope="row" rowspan="1" width="120" style="background-color:#f5f5f5; text-align:center;"|Testing
+
|align="center"|Software Architecture Diagram
|align="center"|User Test Plan
+
|style="text-align="left"|
 +
*[[IS480_Team_wiki:_2012T2_Team_Prime_Diagrams#Software_Architecture|<span style="color:#FC6B2A">Software Architecture Diagram</span>]]
 +
 
 +
|-
 +
! scope="row" rowspan="2" width="120" style="background-color:#FFFFFB; text-align:center;"|Testing
 +
|align="center"|User Test 1
 +
|style="text-align="left"|
 +
*[https://docs.google.com/document/d/1rDWL0l9kAKOBZLOz8PW1jfouBJ7jY0wwSyrxm3ULiAU/edit <span style="color:#FC6B2A">User Test 1 Execution Plan</span>]<br>
 +
*[[IS480_Team_wiki:_2012T2_Team_Prime_Usability_Tests#UT1_Supporting_Documents |<span style="color:#FC6B2A">Supporting Documents</span>]]<br>
 +
 
 +
|-
 +
|align="center"|User Test 2
 
|style="text-align="left"|
 
|style="text-align="left"|
*[https://docs.google.com/document/d/1rDWL0l9kAKOBZLOz8PW1jfouBJ7jY0wwSyrxm3ULiAU/edit <span style="color:#FC6B2A"> Execution Plan </span>]<br>
+
*[https://docs.google.com/document/d/1xNeLGyzfHjWFYcsQfChWEjVnDxmyRnpeHqg8IL-KcuM/edit <span style="color:#FC6B2A">User Test 2 Execution Plan</span>]<br>
*[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T2_Team_Prime_Usability_Tests#Supporting_Documents <span style="color:#FC6B2A"> Supporting Documents </span>]<br>
+
*[[IS480_Team_wiki:_2012T2_Team_Prime_Usability_Tests#UT2_Supporting_Documents |<span style="color:#FC6B2A">Supporting Documents</span>]]<br>
  
 
|}
 
|}
Line 287: Line 342:
 
|+  
 
|+  
 
|-
 
|-
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Area</font>
+
! scope="col" width="100" style="background-color:#794721"| <font color="#ffffff">Environment</font>
! scope="col" width="500" style="background-color:#843A36"| <font color="#ffffff">Description</font>
+
! scope="col" width="180" style="background-color:#794721"| <font color="#ffffff">URL</font>
 +
! scope="col" width="470" style="background-color:#794721"| <font color="#ffffff">Username / Password</font>
 
|-
 
|-
  
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">Development Environment</font>
+
! scope="row" style="background-color:#FFFFFB"|<font color="#222222">Development</font>
 +
|style="text-align: center"|
 +
[http://www.swimix.com <span style="color:#FC6B2A">'''http://www.swimix.com'''</span>]
 +
 
 
|style="text-align: left"|
 
|style="text-align: left"|
:Web browser and smartphone running on Google Chrome and Safari
+
*'''Registered User: ''' studentpeh@yahoo.com.sg / 123123 [http://www.swimix.com <span style="color:#FC6B2A">(Or Sign Up)</span>]
|-
+
*'''Swimming Instructor: ''' instructortan@yahoo.com / 123123 [http://www.swimix.com <span style="color:#FC6B2A">(Or Sign Up)</span>]
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">Database</font>
 
|style="text-align: left;"|
 
:Database hosted on Vodien
 
 
 
|-
 
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">Web Links</font>
 
|style="text-align: left;"|
 
:[http://www.swimix.com <span style="color:#FC6B2A">View the Swimix application</span>]
 
 
|}
 
|}
  
===<font color="#FC6B2A">Testing</font>===
+
===<font color="#FC6B2A">User Test 2</font>===
  
====<font color="#843A36">Objectives</font>====
+
====<font color="#794721">Objectives</font>====
 
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
 
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
 
|scope="row"  width="1000" style="text-align: left; background: #FFFFFB"|
 
|scope="row"  width="1000" style="text-align: left; background: #FFFFFB"|
 
'''OBJECTIVES:'''<br>
 
'''OBJECTIVES:'''<br>
#To obtain feedback from our users with regards to the features in the application  
+
#To obtain feedback from our users with regards to the features in our application so as to improve its usability
#To improve the usability of the application
+
#To ensure that the features developed matches the expectations of the real users (parents & instructors)
 
|}
 
|}
 
<br>
 
<br>
====<font color="#843A36">Scope</font>====
+
====<font color="#794721">Scope</font>====
 
The table below shows a list of features that were tested for our first user test. The features target parents (representing registered users of Swimix) and swimming instructors.<br>
 
The table below shows a list of features that were tested for our first user test. The features target parents (representing registered users of Swimix) and swimming instructors.<br>
 
{|class="wikitable" style="text-align: center;"  
 
{|class="wikitable" style="text-align: center;"  
 
|+  
 
|+  
 
|-
 
|-
! scope="col" width="50" style="background-color:#843A36"| <font color="#ffffff">No.</font>
+
! scope="col" width="50" style="background-color:#794721"| <font color="#ffffff">No.</font>
! scope="col" width="300" style="background-color:#843A36"| <font color="#ffffff">Features</font>
+
! scope="col" width="300" style="background-color:#794721"| <font color="#ffffff">Features</font>
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Reg. User</font>
+
! scope="col" width="100" style="background-color:#794721"| <font color="#ffffff">Reg. User</font>
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Instructor</font>
+
! scope="col" width="100" style="background-color:#794721"| <font color="#ffffff">Instructor</font>
 
|-
 
|-
  
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">1</font>
+
! scope="row" style="background-color:#f5f5f5"|<font color="#222222">1</font>
 
|style="text-align: center"|Register / Log in / Log out<br>
 
|style="text-align: center"|Register / Log in / Log out<br>
 
|✓
 
|✓
Line 332: Line 383:
  
 
|-
 
|-
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">2</font>
+
! scope="row" style="background-color:#f5f5f5"|<font color="#222222">2</font>
|style="text-align: center"|Change Password<br>
+
|style="text-align: center"| Search for Class / Instructor <br>
|✓
 
 
|✓
 
|✓
 +
|N/A
  
 
|-
 
|-
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">3</font>
+
! scope="row" style="background-color:#f5f5f5"|<font color="#222222">3</font>
|style="text-align: center"|Update User Profile<br>
+
|style="text-align: center"|Pay for Class<br>
 
|✓
 
|✓
|
+
|N/A
  
 
|-
 
|-
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">4</font>
+
! scope="row" style="background-color:#f5f5f5"|<font color="#222222">4</font>
|style="text-align: center"|Update Instructor Profile<br>
+
|style="text-align: center"|Send Mass Notification to Students<br>
|
+
|N/A
 
|✓
 
|✓
  
 
|-
 
|-
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">5</font>
+
! scope="row" style="background-color:#f5f5f5"|<font color="#222222">5</font>
|style="text-align: center"|Search for Class<br>
+
|style="text-align: center"|Send Evaluation Survey to Students<br>
 +
|N/A
 
|✓
 
|✓
|
 
  
 
|-
 
|-
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">6</font>
+
! scope="row" style="background-color:#f5f5f5"|<font color="#222222">6</font>
|style="text-align: center"|Search for Instructor <br>
+
|style="text-align: center"|Evaluate Instructor<br>
 
|✓
 
|✓
|
+
|N/A
  
 
|-
 
|-
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">7</font>
+
! scope="row" style="background-color:#f5f5f5"|<font color="#222222">7</font>
|style="text-align: center"|Create and Remove Lesson Slot<br>
+
|style="text-align: center"|Add New Lesson Slot<br>
|
+
|N/A
 
|✓
 
|✓
  
 
|-
 
|-
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">8</font>
+
! scope="row" style="background-color:#f5f5f5"|<font color="#222222">8</font>
|style="text-align: center"|Create and Remove Student Details<br>
+
|style="text-align: center"|Add Student to Lesson Slot<br>
|
+
|N/A
 
|✓
 
|✓
 
|}
 
|}
 
Insert relevant PICTURE.
 
  
 
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
 
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
 
|scope="row"  width="1000" style="text-align: left; background: #FFFFFB"|
 
|scope="row"  width="1000" style="text-align: left; background: #FFFFFB"|
 
'''THE SESSION'''<br>
 
'''THE SESSION'''<br>
User Test 1 was conducted successfully on '''27 Jan 2013''' at '''Yishun Swimming Complex'''.<br>
+
User Test 1 was conducted successfully on '''7 Apr 2013''' at '''Sengkang Swimming Complex'''.<br>
#A total of '''8 parents''' participated in the user test in the role of a '''Registered User'''.<br>
+
#A total of '''30 parents''' participated in the user test in the role of a '''Registered User'''.<br>
#A total of '''2 swimming instructors''' participated in the user test in the role of an '''Instructor'''.
+
#A total of '''5 swimming instructors''' participated in the user test in the role of an '''Instructor'''.
 
<br>
 
<br>
View the '''Supporting Documents''' for the user test [[IS480_Team_wiki:_2012T2_Team_Prime_Usability_Tests#Supporting_Documents |<span style="color:#FC6B2A">'''HERE'''</span>]].<br>
+
View the '''Supporting Documents''' for the user test [[IS480_Team_wiki:_2012T2_Team_Prime_Usability_Tests#UT2_Supporting_Documents |<span style="color:#FC6B2A">'''<u>HERE</u>'''</span>]].<br>
 +
<!--
 
View our '''Internal Testing Documents (Before User Test 1)''' [https://www.dropbox.com/s/cuewdqge4c0yxip/Prime_Internal_Test_Cases_BeforeUT1.docx <span style="color:#FC6B2A">'''HERE'''</span>]<br>
 
View our '''Internal Testing Documents (Before User Test 1)''' [https://www.dropbox.com/s/cuewdqge4c0yxip/Prime_Internal_Test_Cases_BeforeUT1.docx <span style="color:#FC6B2A">'''HERE'''</span>]<br>
 
View our '''Internal Testing Documents (Before Midterm)''' [https://www.dropbox.com/s/dau9b3jsdz45t2a/Prime_Internal_Test_Cases_V1.docx <span style="color:#FC6B2A">'''HERE'''</span>]
 
View our '''Internal Testing Documents (Before Midterm)''' [https://www.dropbox.com/s/dau9b3jsdz45t2a/Prime_Internal_Test_Cases_V1.docx <span style="color:#FC6B2A">'''HERE'''</span>]
 +
-->
 +
View our '''Internal Testing Documents''' [https://www.dropbox.com/s/3f9wa1c1ttdzqhu/Prime_Internal_Test_Cases_V2.docx <span style="color:#FC6B2A">'''<u>HERE</u>'''</span>]
 
|}
 
|}
  
 
<br>
 
<br>
  
====<font color="#843A36">Testing Methodology</font>====
+
====<font color="#794721">Testing Methodology</font>====
 
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
 
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
 
|scope="row"  width="1000" style="text-align: left; background: #FFFFFB"|
 
|scope="row"  width="1000" style="text-align: left; background: #FFFFFB"|
Line 403: Line 455:
  
 
<br>
 
<br>
====<font color="#843A36">Registered Users</font>====
+
====<font color="#794721">Registered Users</font>====
<font color="#FC6B2A">'''MOST COMMON FEEDBACK:'''</font><br><br>
+
<font color="#FC6B2A">'''FEEDBACK:'''</font><br><br>
[[Image:UserFeedback1.png]]<br>
+
[[Image:Prime_UT2Feedback2.png]]<br>
:'''Solution: '''Place Login and Register in the same area and allow switching by tabs.<br>
+
:'''Solution: '''
 +
:Replace “Please Select” with “No Preference”, and remove the unnecessary “Zone” search option.<br><br>
  
[[Image:UserFeedback2.png]]<br>
+
[[Image:Prime_UT2Feedback3.png]]<br>
:'''Solution: '''Change the View link to a button so users know that they can click on it to view the instructor’s profile<br>
+
:'''Solution:'''
<br><br>
+
:Underline the instructor's name to make it more obvious to the user.<br><br>
  
<font color="#FC6B2A">'''POST-TEST SURVEY RESULTS:'''</font><br>
+
[[Image:Prime_UT2Feedback4.png]]<br>
 
+
:'''Solution: '''
 
+
: Include a popup message to inform unregistered users to login first before making payment.<br><br>
 
 
{|class="wikitable" style="text-align: center;"
 
|+
 
|-
 
! scope="col" width="50" style="background-color:#843A36"| <font color="#ffffff">SN</font>
 
! scope="col" width="300" style="background-color:#843A36"| <font color="#ffffff">Functions</font>
 
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Very Unlikely</font>
 
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Unlikely</font>
 
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Undecided</font>
 
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Likely</font>
 
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Very Likely</font>
 
|-
 
 
 
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">1</font>
 
|style="text-align: center"|Search for Class/Instructor<br>
 
|0
 
|0
 
|0
 
|5
 
|3
 
 
 
|-
 
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">2</font>
 
|style="text-align: center"|Online Class Registration<br>
 
|0
 
|1
 
|2
 
|3
 
|2
 
 
 
|-
 
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">3</font>
 
|style="text-align: center"|Online Payment<br>
 
|0
 
|1
 
|0
 
|4
 
|3
 
 
 
|-
 
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">4</font>
 
|style="text-align: center"|Instructor Review<br>
 
|0
 
|2
 
|1
 
|4
 
|1
 
 
 
|-
 
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">5</font>
 
|style="text-align: center"|Instructor Rating<br>
 
|0
 
|0
 
|2
 
|5
 
|1
 
 
 
|-
 
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">6</font>
 
|style="text-align: center"|Receive Notification <br>
 
|0
 
|0
 
|1
 
|3
 
|4
 
 
 
|}
 
 
<br>
 
<br>
  
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
+
====<font color="#794721">Instructors</font>====
|scope="row"  width="1000" style="text-align: left; background: #FFFFFB"|
+
<font color="#FC6B2A">'''FEEDBACK:'''</font><br>
'''Conclusion'''<br><br>
+
[[Image:Prime_UT2Feedback1.png]]<br>
Based on the user feedback, we found out that users are mostly receptive to the idea of a swim-related search portal. <br><br>
+
:'''Solution: '''
 
+
:Replace the photos with useful information on how the system works. <br><br>
The top 2 favourite functions identified by the users were the Manage Search function and the Manage Notification function. They commented that the search function was easy to use and could be very useful to them. The notification function is also something they felt is lacking in the industry now. This is because they have made wasted trips to the swimming complex on the lesson day only to find out the lesson was cancelled.<br><br>
 
 
 
The function that had the highest amount of users indicating that they are unlikely to use is the Instructor Review feature. They explained that they would not want to go through the trouble to register an account just to write a review for the instructors. However, they would not mind writing if given the option of a simpler and more convenient alternative. <br><br>
 
 
 
A user also commented that he preferred to register classes with the instructor in person instead of registering online because he could infer the instructor’s character and personality through the former. A possible solution is to include a short introduction video clip of each instructor so that users are able to gauge the instructor for themselves through the video.<br><br>
 
In conclusion, many users expressed that they portal is user-friendly and would be very useful to them.
 
|}
 
 
<br>
 
<br>
  
====<font color="#843A36">Instructors</font>====
+
==<font color="#794721">'''Reflections'''</font>==
<font color="#FC6B2A">'''MOST COMMON FEEDBACK:'''</font><br>
 
[[Image:InstructorFeedback1.png]]<br>
 
:'''Solution: '''
 
:Use radio buttons instead of dropdown list.<br><br>
 
  
[[Image:InstructorFeedback2.png]]<br>
+
===<font color="#FC6B2A">Team</font>===
:'''Solution: '''
+
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
:Display only the student name and contact number.
+
|scope="row" width="900" style="text-align: left; background: #FFFFFB"|
:Instructors can choose to click on the student's name to view the rest of their information.<br><br><br>
+
1) '''Good communication can make or break a team'''<br>
 
+
All four of us hail from very different backgrounds and hence have rather diverse perspectives that could become obstacles in our communication. Through the course of this FYP, we learnt the importance of maintaining clear communication so that everyone can be kept on the same page and work together to reach a common goal.
<font color="#FC6B2A">'''POST-TEST SURVEY RESULTS:'''</font><br>
 
 
 
 
 
 
 
{|class="wikitable" style="text-align: center;"
 
|+
 
|-
 
! scope="col" width="50" style="background-color:#843A36"| <font color="#ffffff">SN</font>
 
! scope="col" width="300" style="background-color:#843A36"| <font color="#ffffff">Functions</font>
 
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Very Unlikely</font>
 
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Unlikely</font>
 
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Undecided</font>
 
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Likely</font>
 
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Very Likely</font>
 
|-
 
 
 
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">1</font>
 
|style="text-align: center"|Adding lesson slots to calendar<br>
 
|0
 
|0
 
|1
 
|1
 
|0
 
 
 
|-
 
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">2</font>
 
|style="text-align: center"|Selling available class slots<br>
 
|0
 
|0
 
|0
 
|1
 
|1
 
 
 
|-
 
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">3</font>
 
|style="text-align: center"|Sending mass notification<br>
 
|0
 
|0
 
|0
 
|0
 
|2
 
  
|-
+
2) '''Tapping on each other's strengths'''<br>
! scope="row" style="background-color:#F5f5f5"|<font color="#222222">4</font>
+
Whenever we encountered problems, we learnt to use our diversity to our advantage by bringing together our different opinions to brainstorm for solutions.
|style="text-align: center"|Online payment system<br>
 
|0
 
|0
 
|2
 
|0
 
|0
 
  
 +
3) '''A stronger focus on team building'''<br>
 +
If we could improve on one thing, it would be to place a greater emphasis on team building. This would involve several important aspects: openly and honestly talking about our individual expectations and deciding how we would deal with conflict should it arise (which is often neglected). Most importantly, when problems arise, we would focus on coming up with possible solutions rather than playing the blame game.
 
|}
 
|}
  
<br>
+
===<font color="#FC6B2A">Individual</font>===
 
 
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px"
 
|scope="row"  width="1000" style="text-align: left; background: #FFFFFB"|
 
'''Conclusion'''<br><br>
 
It was hard for us to get instructors to test our system because they are usually busy all the time while they are at the pool. They will either be teaching a class, or be on duty as a security guard. Thus, we only managed to get 2 instructors testers during their lunch break period when the weather is typically too hot to conduct a swim class. <br><br>
 
Both instructors found the portal user friendly and did not face any problem using the portal. They provided mostly aesthetics feedback, such as the student list is too cluttered and the login button is too small. In addition, an important point which they commented was that since they are always on the go, they preferred to use the system on their smartphone rather than in front of the computer.
 
|}
 
<br>
 
 
 
==<font color="#843A36">'''Reflections'''</font>==
 
 
 
Team Reflection:
 
Key lessons learned – indicating where the team improved, or would do things differently next time. You may refer to the learning outcome summary in your proposal. A very short checklist style will suffice. It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.
 
 
 
Individual Reflection:
 
Describe in a paragraph, the key areas of learning or improvement. These should be personal areas of growth or learning. Each individual should list his/her effort, responsibility, actual contributions and personal reflection. Do not repeat team project contributions or member roles. Link if necessary.
 
 
 
Sponsor Comment:
 
Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.
 
 
 
 
{|class="wikitable" style="text-align: center;"  
 
{|class="wikitable" style="text-align: center;"  
 
|+  
 
|+  
 
|-
 
|-
 
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Member</font>
 
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Member</font>
! scope="col" width="400" style="background-color:#843A36"| <font color="#ffffff">Reflections</font>
+
! scope="col" width="300" style="background-color:#843A36"| <font color="#ffffff">Reflections</font>
  
 
|-
 
|-
! scope="row" style="background-color:#ffffff"|[[Image:Prime_XC.png|150px]]<br>Shen Xiaochuan
+
! scope="row" style="background-color:#ffffff"|[[Image:Prime_XC.png|120px]]<br>Xiaochuan
 
|style="text-align: left"|
 
|style="text-align: left"|
*-<br>
+
#'''Learnt''' to be more flexible with and prioritize changes to be made, with the limited time and resources of the team
 +
#'''Learnt''' the importance of having good communication to make sure everyone is on the same page <br>
  
 
|-
 
|-
! scope="row" style="background-color:#ffffff"|[[Image:Prime_HQ.png|150px]]<br>Lim Hui Qing
+
! scope="row" style="background-color:#ffffff"|[[Image:Prime_HQ.png|120px]]<br>Lim Hui Qing
 
|style="text-align: left"|
 
|style="text-align: left"|
*-<br>
+
#'''Learnt''' the importance of engaging real users to test the system to ensure it is designed according to their expectations, and to propose appropriate solutions
 +
#'''Developed''' useful skills in video editing, coming up with a proper investor pitch and writing business plans <br>
  
 
|-
 
|-
! scope="row" style="background-color:#ffffff"|[[Image:Prime_JO.png|150px]]<br>Josephine Heng
+
! scope="row" style="background-color:#ffffff"|[[Image:Prime_JO.png|120px]]<br>Josephine Heng
 
|style="text-align: left"|
 
|style="text-align: left"|
*-<br>
+
#'''Learnt''' the importance of designing clear user interface mockups to make development more efficient
 +
#'''Learnt''' to analyze and validate business requirements, thereby creating a system that would benefit our end users <br>
  
 
|-
 
|-
! scope="row" style="background-color:#ffffff"|[[Image:Prime_LR.png|150px]]<br>Larry Ho
+
! scope="row" style="background-color:#ffffff"|[[Image:Prime_LR.png|120px]]<br>Larry Ho
 
|style="text-align: left"|
 
|style="text-align: left"|
*-<br>
+
#'''Learnt''' to think from the user’s perspective rather than from a developer’s perspective when designing and developing the system <br>
 
+
#'''Learnt''' that no matter how good a system is, without good aesthetics, the system cannot be considered a “success”.
 
|}
 
|}

Latest revision as of 10:56, 22 April 2013

<< MAIN WIKI         << MIDTERM WIKI

PrimeLogo.png


Project Progress Summary

Project Overview

Final Presentation Slides

Swimix Deployed Site Link

  1. The team has completed 8 sprints in total and is now finishing its final milestone.
  2. We have completed all core, secondary, and tertiary features within our SCHEDULE as listed in the PRIORITY CIRCLE.
Prime VideoIcon.png View the interview with our celebrity endorser and Olympian swimmer Tao Li here
Prime VideoIcon.png View our pitch here. [NEW!]
Prime VideoIcon.png View our User Test 1 video here.
Prime VideoIcon.png View our User Test 2 video here. [NEW!]


This is where we are on the timeline:
Prime ProjectMilestones WeAreHere V0.2.png

Project Highlights

Event Highlights / Issue Description
Sprint 6
Instructor web mobile feature dropped
Due to the slow progression made, the team decided to drop the instructor web mobile feature in order to bring the project back on schedule.

Integration of payment feature pushed to Sprint 7
Towards the end of the sprint, the team encountered difficulties with integrating the payment feature. Hence, the team decided to bring forward the integration to the next sprint.
Sprint 7
Swim school features dropped
The team faced difficulties in implementing the payment feature. To focus our efforts on finishing up the payment feature, the team decided to drop the swim school feature. A secondary reason is that swim schools are not the main target market for Swimix.

Project Achievements

  1. Secured Singapore Olympian swimmer Tao Li as our celebrity sponsor. View our interview with her HERE.
  2. Successfully conducted 2 rounds of USER TESTS at Yishun Swimming Complex and Sengkang Swimming Complex, with a total of 38 users and 7 swimming instructors.
  3. Received confirmation of investment on Swimix from investor Dr Virginia Cha, who is also one of our PROJECT ADVISORS from SMU Institute of Innovation & Entrepreneurship.


Project Management

Schedule (Planned Vs Actual)

Prime Schedule BeforeAfterV2.png

Since the midterms, the following changes have been made to the project schedule:

  1. Manage Notifications feature was brought forward to Sprint 6.
  2. Integration of Payment feature was shifted from Sprint 6 to Sprint 7.
  3. Sprint 7 was shifted earlier to the User Test 2 milestone.
  4. Instructor web mobile and Swim School features were dropped from Sprint 6 and Sprint 7 respectively.
  5. Change of date for User Test 2 to 7 April 2013


Refer to the PROJECT TIMELINE for a full view of the current project schedule.


Scope (Planned Vs Actual)

Prime PriorityCircle BeforeAfter.png

Since the midterms, the following changes have been made to the project scope:

  • The Instructor Web Mobile and Swim School features were re-prioritised as Good-to-Have features so that we can have a more manageable scope.



Project Metrics

Schedule Metric

The diagrams below show the burndown charts and schedule ratio charts of Sprints 6 to 8 since the midterms.

BURNDOWN CHARTS

Prime BurndownCharts Sprints678.png

SCHEDULE RATIO CHARTS

Prime ScheduleRatioCharts Sprints678.png

KEY ISSUES

Sprint 6:

  1. On 12 Mar, the burndown chart indicated that the team was behind schedule. This was due to the slow progression of the team. The team decided to drop the instructor web mobile feature in order to bring the project back on schedule.
  2. Towards the end of the sprint, the team encountered difficulties with integrating the payment feature. Hence, the team decided to bring forward the integration to the next sprint (Sprint 7).

Sprint 7:

  1. 1. On 23 Mar, the burndown chart indicated that the team was behind schedule. This was because the team faced difficulties in implementing the payment feature. To focus our efforts on finishing up the payment feature, the team decided to drop the swim school feature. Moreover, swim schools are not the main target market for Swimix.


For more details:
1. Schedule Metric Calculation
2. Schedule Ratio Documentation: Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6 Sprint 7 Sprint 8

Bug Metric

Prime NoOfBugsFound V3.png

Number of Bugs Found

  1. The chart above shows the number of bugs found in each sprint.
  2. In Sprint 6, there was a slight spike in the number of bugs found (5), as more rigorous testing was conducted on the application to prepare for User Test 2 (originally scheduled in Sprint 7).


Prime BugMetricSeverityChart V3.png

Total Bug Score

  1. The chart above shows the corresponding bug severity score with the number of bugs found in each sprint.
  2. The bug severity score in Sprint 6 (13 points) was the highest out of Sprints 6 to 8 (after midterms) due to the testing for User Test 2 as mentioned above.
Total Bug Score Action to be Taken
< 5 Developers resolve issues within the sprint.
5 - 9 Resolve the bugs during the planned debugging time.
≥ 10 Stop current development and resolve the bugs immediately.


For more details:
1. Bug Metric Calculation
2. Bug Log

Change Request Management

ChangeRequest.png

  1. If the priority is a MUST, we will implement the change
  2. If the priority is a SHOULD and the time to implement the change is VERY SHORT, SHORT, or MEDIUM, we will implement the change.
  3. If the priority is a COULD, and the time to implement the change is VERY SHORT, we will implement the change.
  4. If the priority is a WON'T, then we will not implement the request.

View our Change Request Log.

Project Risks

The top 3 risks are prioritised as follows:

Risk Probability Impact Mitigation
Low awareness of platform High High
  • We plan to mitigate this through aggressive marketing plans and celebrity endorsements.
Low usage of platform High Low
  • Tap on the power of previous customers’ networks and organize events to encourage signups
  • Incentivize users to sign up by giving referral discounts and rebates
Idea may be copied by others Low High
  • Effectively leverage on the first mover advantage to capture the majority of the market share as fast as possible
  • More users = Higher value of the portal

View the full list of risks HERE.

Technical Complexity

Area Description
1. Improvements in Usability
  • Cross-browser compatibility
2. Improvements in Performance
  • Loading of user profile
  • Loading of instructor’s calendar
  • Search engine optimization
  • Naming convention of class files
  • Mapping on CodeIgniter framework (root folder)
3. Future Improvements
  • Internationalization
  • Localization
  • Payment security
  • Responsiveness
  • User profile
  • Instructor’s calendar
  • Usability
  • More data validation needed


The following technical complexities have been listed in order of complexity (highest to lowest):

Complexity 1: Calendar

Load the Calendar:
Prime Calendar1.png

Load the Class:
Prime Calendar2.png

Complexity 2: Payment

Generate the Order Form:
Prime Payment1.png

Confirm Order Form after Payment is Made:
Prime Payment2.png

Complexity 3: Search Engine Optimization

Search Engine Optimization:
Prime SEO.png

Quality of Product

Intermediate Deliverables

Stage Specification Modules
Project Management Minutes
Metrics
Requirements Product Backlog
UI Mockups
Analysis Use Case
Process Flow Diagram
Design ER Diagram
System Architecture Diagram
Software Architecture Diagram
Testing User Test 1
User Test 2

Deployment

Environment URL Username / Password
Development

http://www.swimix.com

  • Registered User: studentpeh@yahoo.com.sg / 123123 (Or Sign Up)
  • Swimming Instructor: instructortan@yahoo.com / 123123 (Or Sign Up)

User Test 2

Objectives

OBJECTIVES:

  1. To obtain feedback from our users with regards to the features in our application so as to improve its usability
  2. To ensure that the features developed matches the expectations of the real users (parents & instructors)


Scope

The table below shows a list of features that were tested for our first user test. The features target parents (representing registered users of Swimix) and swimming instructors.

No. Features Reg. User Instructor
1 Register / Log in / Log out
2 Search for Class / Instructor
N/A
3 Pay for Class
N/A
4 Send Mass Notification to Students
N/A
5 Send Evaluation Survey to Students
N/A
6 Evaluate Instructor
N/A
7 Add New Lesson Slot
N/A
8 Add Student to Lesson Slot
N/A

THE SESSION
User Test 1 was conducted successfully on 7 Apr 2013 at Sengkang Swimming Complex.

  1. A total of 30 parents participated in the user test in the role of a Registered User.
  2. A total of 5 swimming instructors participated in the user test in the role of an Instructor.


View the Supporting Documents for the user test HERE.
View our Internal Testing Documents HERE


Testing Methodology

Collecting of Qualitative Metrics

  1. Participants are encouraged to think aloud their thought process as they are performing each task. For example, we would encourage them to say whatever they are looking at, thinking, doing, and feeling as they go about the task. This enables us as the observer to better understand each participant’s thought processs and see first-hand the process of him/her completing the task.
  2. Facilitators will observe for usability issues during the testing procedure by recording down what participants say. The test sessions will also be video-recorded on Screen Flow so that we can go back and refer to what participants did and how they reacted.
  3. In addition, after participants have completed the user test, they will be asked to do a satisfaction level survey that will aid in the collection of qualitative metrics.

Collecting of Quantitative Metrics

  1. The amount of time taken to complete each task
  2. The number of clicks taken for each task


Registered Users

FEEDBACK:

Prime UT2Feedback2.png

Solution:
Replace “Please Select” with “No Preference”, and remove the unnecessary “Zone” search option.

Prime UT2Feedback3.png

Solution:
Underline the instructor's name to make it more obvious to the user.

Prime UT2Feedback4.png

Solution:
Include a popup message to inform unregistered users to login first before making payment.


Instructors

FEEDBACK:
Prime UT2Feedback1.png

Solution:
Replace the photos with useful information on how the system works.


Reflections

Team

1) Good communication can make or break a team
All four of us hail from very different backgrounds and hence have rather diverse perspectives that could become obstacles in our communication. Through the course of this FYP, we learnt the importance of maintaining clear communication so that everyone can be kept on the same page and work together to reach a common goal.

2) Tapping on each other's strengths
Whenever we encountered problems, we learnt to use our diversity to our advantage by bringing together our different opinions to brainstorm for solutions.

3) A stronger focus on team building
If we could improve on one thing, it would be to place a greater emphasis on team building. This would involve several important aspects: openly and honestly talking about our individual expectations and deciding how we would deal with conflict should it arise (which is often neglected). Most importantly, when problems arise, we would focus on coming up with possible solutions rather than playing the blame game.

Individual

Member Reflections
Prime XC.png
Xiaochuan
  1. Learnt to be more flexible with and prioritize changes to be made, with the limited time and resources of the team
  2. Learnt the importance of having good communication to make sure everyone is on the same page
Prime HQ.png
Lim Hui Qing
  1. Learnt the importance of engaging real users to test the system to ensure it is designed according to their expectations, and to propose appropriate solutions
  2. Developed useful skills in video editing, coming up with a proper investor pitch and writing business plans
Prime JO.png
Josephine Heng
  1. Learnt the importance of designing clear user interface mockups to make development more efficient
  2. Learnt to analyze and validate business requirements, thereby creating a system that would benefit our end users
Prime LR.png
Larry Ho
  1. Learnt to think from the user’s perspective rather than from a developer’s perspective when designing and developing the system
  2. Learnt that no matter how good a system is, without good aesthetics, the system cannot be considered a “success”.