HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2017T1 Citadel Final Wiki"

From IS480
Jump to navigation Jump to search
 
(34 intermediate revisions by the same user not shown)
Line 44: Line 44:
 
!style="font-weight: bold;background:#191970;color:#fff;" | Google Play Store App Download
 
!style="font-weight: bold;background:#191970;color:#fff;" | Google Play Store App Download
 
|-
 
|-
|[[Image:Citadel Finals Slides.png|130px|link=https://drive.google.com/a/smu.edu.sg/file/d/0B0twVVc1QfAydXQxb2YzYlYzd2c/view?usp=sharing]]
+
|[[Image:Citadel Finals Slides.png|130px|link=https://drive.google.com/a/smu.edu.sg/file/d/1hgZe1j99A_JtYgbLFdPvHtkBmfjDfPgf/view?usp=sharing]]
 
| [[Image:Citadel_GoogleStore.PNG|130px]]
 
| [[Image:Citadel_GoogleStore.PNG|130px]]
 
|-
 
|-
Line 67: Line 67:
 
<br>
 
<br>
  
[[Image:CitadelProjectScope1.png|center|800px]]
+
[[Image:CitadelProjectScope1.png|center|600px]]
[[Image:CitadelProjectScope2.png|center|800px]]
+
[[Image:CitadelProjectScope2.png|center|600px]]
[[Image:CitadelProjectScope3.png|center|800px]]
+
[[Image:CitadelProjectScope3.png|center|600px]]
  
 
<br>
 
<br>
 
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>Project Schedule</font></div>
 
<br>
 
<center>
 
{| class="wikitable"
 
 
! style="font-weight:bold;background: #1f3442;color:#fff; width:65px; border:1px solid #2e2e2e;font-family: Montserrat" |Iteration
 
! style="font-weight:bold;background: #1f3442;color:#fff; width:300px; border:1px solid #2e2e2e;font-family: Montserrat" | Modules
 
! style="font-weight:bold;background: #1f3442;color:#fff; width:135px; border:1px solid #2e2e2e;font-family: Montserrat" | Scope
 
! style="font-weight:bold;background: #1f3442;color:#fff; width:360px; border:1px solid #2e2e2e;font-family: Montserrat" | Status
 
|-
 
| style="text-align:center" | 2                                     
 
| style="text-align:Center" | Account Module 
 
| style="text-align:Center" | Core
 
| style="text-align:left" | Completed     
 
|-
 
| style="text-align:center" | 2         
 
| style="text-align:Center" | Order Matching Module
 
| style="text-align:Center" | Core
 
| style="text-align:left" | Completed
 
|-
 
| style="text-align:center" | 3           
 
| style="text-align:center" | Account Module 
 
| style="text-align:center" | Core
 
| style="text-align:left" | Completed         
 
|-
 
| style="text-align:center" | 3           
 
| style="text-align:center" | Usability Module (AI Help Bot) 
 
| style="text-align:center" | Tertiary
 
| style="text-align:left" | Completed   
 
|-
 
| style="text-align:center" | 3           
 
| style="text-align:center" | Order Matching Module 
 
| style="text-align:center" | Core
 
| style="text-align:left" | Completed   
 
|-
 
| style="text-align:center" | 4           
 
| style="text-align:center" | Trading Module 
 
| style="text-align:center" | Core
 
| style="text-align:left" |  Completed   
 
|-
 
| style="text-align:center" | 4           
 
| style="text-align:center" | Order Matching Module 
 
| style="text-align:center" | Core
 
| style="text-align:left" | Completed     
 
|-
 
| style="text-align:center" | 4           
 
| style="text-align:center" | Portfolio Module 
 
| style="text-align:center" | Core
 
| style="text-align:left" |  Completed     
 
|-
 
| style="text-align:center" | 8           
 
| style="text-align:center" | Portfolio Module 
 
| style="text-align:center" | Core
 
| style="text-align:left" | Completed     
 
|-
 
| style="text-align:center" | 8           
 
| style="text-align:center" | Notification Module 
 
| style="text-align:center" | Secondary
 
| style="text-align:left" |  90% Completion. Will be completed by Iteration 13   
 
|-
 
| style="text-align:center" | 9           
 
| style="text-align:center" | Analytics Module 
 
| style="text-align:center" | Good to have
 
| style="text-align:left" | 90% Completion. Will be completed by Iteration 13       
 
|-
 
| style="text-align:center" | 9           
 
| style="text-align:center" | Order Matching Module 
 
| style="text-align:center" | Add-ons
 
| style="text-align:left" | Completed         
 
|-
 
| style="text-align:center" | 11           
 
| style="text-align:center" | Multi Language Module 
 
| style="text-align:center" | Tertiary
 
| style="text-align:left" |  Completed       
 
|-
 
| style="text-align:center" | 11           
 
| style="text-align:center" | Filter Module 
 
| style="text-align:center" | Tertiary
 
| style="text-align:left" | Completed     
 
|-
 
| style="text-align:center" | 12           
 
| style="text-align:center" | Order Matching Module 
 
| style="text-align:center" | Add-ons
 
| style="text-align:left" | Completed   
 
|-
 
|}
 
 
 
</center>
 
 
 
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>Current Project Schedule</font></div><br>
 
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>Current Project Schedule</font></div><br>
[[Image: Finals current schedule.png|center|900px]]
+
[[Image: Finals current schedule.png|center|1100px]]
 
<br>
 
<br>
 
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>Planned Project Schedule (Mid Term Review)</font></div>
 
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>Planned Project Schedule (Mid Term Review)</font></div>
Line 171: Line 80:
 
<br><br><br>
 
<br><br><br>
 
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>Project Metrics Chart</font></div>
 
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>Project Metrics Chart</font></div>
<br><br><br>
+
<br>
[[Image: Citadel_projmngtcharts.png|center|1100px]]
+
[[Image: Citadel_projmngtcharts.png|center|800px]]
<br><br><br>
+
<br>
 +
[[Image: Citadel_projmngtcharts1.png|center|800px]]
 +
<br>
 
<center><b> Task Score = (Actual Task/ Planned Task)x100% </b></center>
 
<center><b> Task Score = (Actual Task/ Planned Task)x100% </b></center>
[[Image:Midterm Citadel Task Metric.PNG|center|1100px]]
+
[[Image:Midterm Citadel Task Metric.PNG|center|800px]]
<br><br>
 
 
 
 
 
 
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>Project Risks</font></div>
 
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>Project Risks</font></div>
  
<b>Past Risk:</b>
+
<b>Past Risk (At Acceptance):</b>
 
{| class="wikitable" style="margin:1em auto 1em auto;"
 
{| class="wikitable" style="margin:1em auto 1em auto;"
 
|+  
 
|+  
Line 204: Line 112:
 
<br/>
 
<br/>
  
<br>
+
<b> Past Risks (By iteration 9):</b>
<b>Risks (By iteration 9):</b>
 
 
{| class="wikitable" style="margin:1em auto 1em auto;"
 
{| class="wikitable" style="margin:1em auto 1em auto;"
 
|+  
 
|+  
Line 246: Line 153:
 
|}
 
|}
  
<b> New Risks:</b>
+
<b> Past Risks (After Midterms):</b>
 
{| class="wikitable" style="margin:1em auto 1em auto;"
 
{| class="wikitable" style="margin:1em auto 1em auto;"
 
|+  
 
|+  
Line 256: Line 163:
 
! scope="col" style="padding: 5px; text-align: center; margin-left: 10px; background:#434343; color:#ffffff; font-family:Arial; letter-spacing: 0px; font-size: 14px; text-align: center;"| Mitigation Plan
 
! scope="col" style="padding: 5px; text-align: center; margin-left: 10px; background:#434343; color:#ffffff; font-family:Arial; letter-spacing: 0px; font-size: 14px; text-align: center;"| Mitigation Plan
 
|-
 
|-
!scope="row" style="padding: 5px; text-align: center; font-family:Arial; letter-spacing: 0px; font-size: 14px; text-align: Left;"| Lack of Finance Knowledge
+
!scope="row" style="padding: 5px; text-align: center; font-family:Arial; letter-spacing: 0px; font-size: 14px; text-align: Left;"| Lack of Finance Knowledge which is required to develop the main functionalities of the application & essentially predictive analytics chart
 
|style="padding: 5px; text-align: center; font-family:Arial; color:#5f5f5f; letter-spacing: 0px; font-size: 14px; text-align: center;"|  
 
|style="padding: 5px; text-align: center; font-family:Arial; color:#5f5f5f; letter-spacing: 0px; font-size: 14px; text-align: center;"|  
 
High
 
High
Line 264: Line 171:
 
A
 
A
 
|style="padding: 5px; text-align: center; font-family:Arial; color:#5f5f5f; letter-spacing: 0px; font-size: 14px; text-align: left;"|  
 
|style="padding: 5px; text-align: center; font-family:Arial; color:#5f5f5f; letter-spacing: 0px; font-size: 14px; text-align: left;"|  
* Schedule more time to self learn the basics required for predictive analytics chart.
+
* Schedule more time to self learn the basics required for predictive analytics chart. Consult experts on clarity. Conduct more user testings on this function to get more insights to user's understanding and behavior
 
|-
 
|-
 
|}
 
|}
Line 270: Line 177:
 
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>Technical Complexities</font></div>
 
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>Technical Complexities</font></div>
 
<br>
 
<br>
[[File:Citadelcomplexities1.png|center|1300px]]
+
[[File:Citadelcomplexities1.png|center|800px]]
[[File:Citadelcomplexities2.png|center|1300px]]
+
[[File:Citadelcomplexities2.png|center|800px]]
[[File:Citadelcomplexities3.png|center|1300px]]
+
[[File:Citadelcomplexities3.png|center|800px]]
[[File:Citadelcomplexities4.png|center|1300px]]
+
[[File:Citadelcomplexities4.png|center|800px]]
[[File:Citadelcomplexities5.png|center|1300px]]
+
[[File:Citadelcomplexities5.png|center|800px]]
 +
[[File:Citadelcomplexities6.png|center|800px]]
 +
[[File:Citadelcomplexities7.png|center|800px]]
 +
[[File:Citadelcomplexities8.png|center|800px]]
 +
[[File:newCitadelComplexities9.png|center|800px]]
 +
[[File:newCitadelComplexities2.png|center|800px]]
 +
[[File:newCitadelComplexities211111.png|center|800px]]
 +
[[File:newCitadelComplexities211.png|center|800px]]
 +
[[File:newCitadelComplexities2111.png|center|800px]]
 
<br><br>
 
<br><br>
 
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>Architecture Diagram</font></div>
 
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>Architecture Diagram</font></div>
Line 316: Line 231:
  
 
<br>
 
<br>
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>Testing</font></div>
+
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>User Testing 1</font></div>
  
 
<!--Sub Header End-->
 
<!--Sub Header End-->
Line 373: Line 288:
 
<br>
 
<br>
 
[[File:Citadel UAT after.png|center|1100px]]
 
[[File:Citadel UAT after.png|center|1100px]]
 +
 +
<br>
 +
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>User Testing 2</font></div>
  
 
<b><u>User Testing 2</u></b><br><br>
 
<b><u>User Testing 2</u></b><br><br>
Line 378: Line 296:
 
<b>Time:</b> 4pm-7pm <br>
 
<b>Time:</b> 4pm-7pm <br>
 
<b>Number of participants:</b> 20 <br>
 
<b>Number of participants:</b> 20 <br>
[[File:Citadel UAT2.png|center|1100px]]
+
[[File:Citadel UAT2.png|center|800px]]
 
<br><Br>
 
<br><Br>
[[File:Citadel UAT2charts.png|center|1300px]]
+
[[File:Citadel UAT2charts.png|center|800px]]
 
<b>Summary of Key Findings:</b><br>
 
<b>Summary of Key Findings:</b><br>
 
<center>
 
<center>
Line 427: Line 345:
 
</center>
 
</center>
 
<br>
 
<br>
 +
<br>
 +
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>User Testing 3</font></div>
  
 +
<b><u>User Testing 3 </u></b><br><br>
 +
<b>Venue:</b> SIS GSR 2-4 <br>
 +
<b>Date:</b> 10th November 2017 <br>
 +
<b>Time:</b> 4pm-5.30pm <br>
 +
<b>Number of participants:</b> 10 <br>
 +
<b>Scope (Trial preparation for our UAT on 14th November 2017) </b> <br>
 +
* View deals from primary and secondary market
 +
* Add a new Buy/Sell order
 +
* Accept a new Buy/Sell
 +
* View Trade Portfolio
 +
* Cancel an order
 +
* View history
 +
* Able to change password
 +
<br>
 +
 +
{| class="wikitable"
 +
! style="font-weight: text-align: center; bold;background: #232D34;color:#FFFFFF; width:200px; border:1px solid #232D34" | Function
 +
! style="font-weight: text-align: center; bold;background: #232D34;color:#FFFFFF; width:200px; border:1px solid #232D34" | Changes to be made
 +
 +
|-
 +
| style="text-align:center" | iOS
 +
| style="text-align:left" | User feedback that iOS drawer does not support multi-language
 +
|-
 +
|-
 +
| style="text-align:center" | Alert Messages
 +
| style="text-align:left" | When user received alerts, the language did not change according to the selected preferred language
 +
|-
 +
|-
 +
| style="text-align:center" | Operation timeout error message
 +
| style="text-align:left" | Some users experienced extended period of timeout but did not receive error message to notify them
 +
|-
 +
 +
|}
 +
<br>
 +
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>User Acceptance Test</font></div>
 +
 +
<b><u>User Acceptance Test </u></b><br><br>
 +
<b>Venue:</b> SIS GSR 2-1 <br>
 +
<b>Time:</b> 12pm-1pm <br>
 +
<b>Number of participants:</b> 33 <br>
 +
<b>You can download our [[Media:CitadelUserGuide.pdf|User Guide]] and [[Media:CitadelFinalLab.pdf|Lab Questionaire]] </b>
 +
 +
[[File:CitadelUATClassphotos.png|center|600px]]
 +
<br>
 +
<b>Summary of User Behavior:</b><br>
 +
<b><u>User Overview</u></b><br><br>
 +
[[File:UserOverview.png|center|900px]]
 +
[[File:UserOverview1.png|center|900px]]
 +
<br>
 +
<b><u>Screens Overview</u></b><br><br>
 +
[[File:UserOverview3.png|center|900px]]
 +
<br>
 +
<b><u>Session Data Overview</u></b><br><br>
 +
[[File:UserOverview4.png|center|900px]]
 +
<br>
 +
<b><u>User Behavior Overview</u></b><br><br>
 +
[[File:UserOverview5.png|center|1100px]]
 +
[[File:UserOverview6.png|center|1100px]]
 +
[[File:UserOverview7.png|center|1100px]]
 +
 +
<b>Summary of Key Findings (To be updated once TA of Retail Banking class sends us lab documents uploaded to DropBox by students):</b><br>
 +
<center>
 +
{| class="wikitable"
 +
! style="font-weight: text-align: center; bold;background: #232D34;color:#FFFFFF; width:200px; border:1px solid #232D34" | Function
 +
! style="font-weight: text-align: center; bold;background: #232D34;color:#FFFFFF; width:200px; border:1px solid #232D34" | Users' Behavior
 +
! style="font-weight: text-align: center; bold;background: #232D34;color:#FFFFFF; width:200px; border:1px solid #232D34" | Changes to be Made
 +
|-
 +
| style="text-align:center" |
 +
| style="text-align:left" |
 +
| style="text-align:left" |
 +
|-
 +
|-
 +
| style="text-align:center" |
 +
| style="text-align:left" |
 +
| style="text-align:left" |
 +
|-
 +
|-
 +
| style="text-align:center" |
 +
| style="text-align:left" |
 +
| style="text-align:left" |
 +
|-
 +
|-
 +
| style="text-align:center" |
 +
| style="text-align:left" |
 +
| style="text-align:left" |
 +
|-
 +
|-
 +
| style="text-align:center" |
 +
| style="text-align:left" |
 +
| style="text-align:left" |
 +
|-
 +
| style="text-align:center" |
 +
| style="text-align:left" |
 +
| style="text-align:left" |
 +
|-
 +
| style="text-align:center" |
 +
| style="text-align:left" |
 +
| style="text-align:left" |
 +
|-
 +
| style="text-align:center" |
 +
| style="text-align:left" |
 +
| style="text-align:left" |
 +
|-
 +
|}
 +
</center>
 +
<br>
 +
 +
<br>
 +
<br>
 +
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>Handover Meeting</font></div>
 +
<b><u>Handover Meeting with Sponsor at FundPlaces Office </u></b><br><br>
 +
[[File:Handover (Citadel).jpg|center|800px]]
 +
Team Citadel met up with our sponsor at FundPlaces office to discuss about FYP handover. Sponsor expressed great satisfaction to our end product of the application and will endorse their full support in signing off the testings we conducted over the past 3 months to ensure functionalities are all good to be push to production once MAS regulations are cleared.
 +
 +
<br>
  
 
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>Team Reflection</font></div>
 
<div style="background: #384952; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:15px; font-family:helvetica"><font color= #FFFFFF>Team Reflection</font></div>
Line 433: Line 468:
 
<b>Team Reflection:</b><br>Communication with our Sponsors and Supervisor is very important in order for our team to keep align with the requirements and to avoid mismatch of expectations. This is especially so during this time period where we are expecting and anticipating changes from MAS regulations which directly impact the operations of our sponsor company. Our team has set out clear communications and in frequent contact, meetings with sponsors and supervisors.<br><br>
 
<b>Team Reflection:</b><br>Communication with our Sponsors and Supervisor is very important in order for our team to keep align with the requirements and to avoid mismatch of expectations. This is especially so during this time period where we are expecting and anticipating changes from MAS regulations which directly impact the operations of our sponsor company. Our team has set out clear communications and in frequent contact, meetings with sponsors and supervisors.<br><br>
  
<b>Shangguan Yajie: </b><br> Doing a project with new business idea is very challenging, I need identify the risk and have proper plan to deal with the risk. And also the stakeholder management is very important and I learnt a lot from this experience. <br><br>
+
<b>Shangguan Yajie: </b><br> Through this project, I have learnt the following: <br>
 +
* As a project manager, I understand the importance of stakeholder management and planning and also I need to always have backup plans and be flexible when changes occurs.
 +
* As a team, we need to adapt to different working styles and sometimes compromise is necessary
 +
* It is very importance to conduct different testing in different stages and getting users' feedback.
 +
<br>
  
<b>Vivian Quark: </b> <br>Conducting user testings can be challenging sometimes because every individuals may have different interpretations and understanding of our application. This resulted in the need to convey required changes with my team's developers in order to enhance user friendliness. There were some discussions and debating on certain new functionalities within the team but everyone did it for the betterment and improvement of the application. <br><br>
+
<b>Vivian Quark: </b> <br> This FYP have taught me about Murphy's law- If something can go wrong, it can go wrong. There are numerous hiccups along the way and I have learnt how to manage user's expectations,sponsor's expectations and team's expectations. User testings gave great insights on how we can further improve our applications and the team have always been committed of continuous learning and continuous improvement. I have learnt how important it is in putting user empathy first in any functionalities or user interfaces we develop. Secondly, there is a need to constantly gather feedback and do research on consumer behavior, to think in their perspective and to discover what terminologies/functionalities they may find it difficult to understand. It has been a great learning experience to collect these qualitative and quantitative data and correlate them to customer journey, application performance and business outcomes. <br><br>
  
<b> Qi Zhen Yi: </b><br> During this midterm, as I have already picked up the skills before acceptance, there are not much technical challenges actually. The only challenge is meeting expectation of the team. While designing for wiki pages, I often followed my own way and sometimes people’s preferences are different. So I learnt to communicate with the team more to ask for feedback and try to resolve at early stage. <br><br>
+
<b> Qi Zhen Yi: </b><br> Through this whole journey of FYP, I have picked up valuable skills which could only be learnt with such experiences and the team.  There were many mind blowing nights and days which we spent as a group and achieved our milestone. And finally we are here. As an individual, not only I have picked up design, technical and financial knowledge through out the journey. The most  challenging and fulfilling experience for me is always meeting expectation of the team. While I first started my role as app designer, I prefer to follow my own way and not willing to easily give in for others’ preferences. So at the time, it was tough for me. However, I was glad that despite all the differences, we still managed to work as a team and learn to communicate with others. I also learnt to be more proactive and ask more for feedbacks and try to resolve any issues at early stage. Really glad we made it through and did our best as a team. <br><br>
  
<b> Xu Jia Wen: </b><br>I learnt from our user testing and sponsor, supervisor feedback and came up with innovative ideas to improve user experience. I also learnt collaboration is a key to a successful project.<br><br>
+
<b> Xu Jia Wen: </b><br>We could have gone for a safer choice for this FYP but we didn't. We wanted to do something more innovative, more industry-related in a real-world context. So except all the cutting-edge technologies we learnt for this project, I learnt how to deal with challenges and deal with difficult people. We did face many challenges and hit some bumps during the journey. But we managed to get through all of them and bounced back stronger. And I think all the challenges we faced in this project , such as MAS regulation issue and non-compatible technology issue, do happen a lot in real life. And all these invaluable experiences will definitely help me in my future career.<br><br>
  
 
<b> Yongyi: </b> <br>
 
<b> Yongyi: </b> <br>
After the last major milestone, I got my hands on even more amazing technologies and frameworks such as emailers. Working with our sponsor, we also optimized our workflow and I gained valuable insights on how an order-matching process should be properly executed. I also learned that server security is paramout and got an in-depth understanding of the mechanisms and inplementation of various IT security measures such as HTTP signatures. Although we faced challenges, by working closely within ourselves and with our sponsor we managed to overcome them and make ourselves a more resilient team. <br><br>
+
After the last major milestone, I took a deeper dive in to analytics and code performance optimization. We worked as a group and came up with ways to make our code more efficient. I also learned how to modularize Javascript code with closures, for better readability and modularity. Although we faced challenges, by working closely within ourselves and with our sponsor we managed to overcome them. <br><br>
  
 
<b> Jinlong: </b><br>
 
<b> Jinlong: </b><br>
From acceptance to Midterm, our project has moved forward a lot. During this period, I tried to improve the UI and most of the base structure to improve the performance. I realized that making a fully functional app is easy, but making an perfect app is hard, especially when we are new to certain framework. Even though the changes at frontend may not be significant to the user, but much underneath work need to be done to deliver the perfect user experience. <br><br>
+
This Final Year Project has been a great journey, I am fully exposed to the new technologies such as react-native and managed to master it eventually. At the beginning, I feel foreign to React-native because I am a native Android developer. However, my perspective towards React-native changes as I realized it is a powerful framework. Similar to AngularJS, react-native is also written in JS(X) and has the concept of one-way binding.
 +
 
 +
I feel that it is revolutionary as it saves a lot of time dedicated in development phase. During the last hurdle of our project, I encountered what I considered as the biggest issue in FYP which is, React-native has its own limitation in functions like web-socket. After much tries and struggles, I decided to convert and do it as a hybrid app. From this, I learnt we should not just rely on one tech because sometimes hybrid is better!
 +
 
 +
As the main front-end developer, I shoulder a huge responsibility in UI/UX. However, one shortcoming is that I have not take IDP classes yet and UI is proven to be challenging to me at the start. With the help from Jia Wen, we managed to revamp our UI and make it extraordinary! Team work is essentially important especially when we meet with challenges and solidarity makes our group to be outstanding! <br><br>
  
  
 
<!--Content End-->
 
<!--Content End-->

Latest revision as of 17:40, 21 November 2017

Citadel team Logo.jpg

Home FP.png  HOME

About-us FP.png  ABOUT US

PO FP.png  PROJECT OVERVIEW

PM FP.png  PROJECT MANAGEMENT

DOCS FP.png  DOCUMENTATION

MAIN WIKI MID-TERM WIKI FINAL WIKI

Project Progress Summary

Finals slides Google Play Store App Download
Citadel Finals Slides.png Citadel GoogleStore.PNG

Project Highlights

Project Progress Summary
  • Top 4 Achievements:
    • 1. Completed User Guide for Lab Session
    • 2. Completed Prediction Analysis and Search Deals Functions
    • 3. Included Google Analytics into FundPlaces application to monitor application usage
    • 4. iOS Test version released and iPhone users may now download the application with the redeem code


  • Top 2 Challenges:
    • 1. Notification function for iOS is difficult to implement the Team Citadel is focusing the remaining time in the remaining iterations to resolve this hurdle
    • 2. Algorithm implementation is difficult.

Project Management

Project Status


CitadelProjectScope1.png
CitadelProjectScope2.png
CitadelProjectScope3.png


Current Project Schedule


Finals current schedule.png


Planned Project Schedule (Mid Term Review)




Fundplaces Project Timeline ver3.png




Project Metrics Chart


Citadel projmngtcharts.png


Citadel projmngtcharts1.png


Task Score = (Actual Task/ Planned Task)x100%
Midterm Citadel Task Metric.PNG
Project Risks

Past Risk (At Acceptance):

Risk Likelihood Impact Category Mitigation Plan
Project team members are new to Node.js environment, hence they might exceed the time scheduled for development.

High

High

A

  • Allocate more programming session, and code sharing, use pessimistic approach


Past Risks (By iteration 9):

Risk Likelihood Impact Category Mitigation Plan
Regulatory Requirement. Using block chain to perform real estate investment and trading is a relatively new business idea.

High

High

A

  • Team and sponsors are actively observing the situation amidst MAS regulations so that we can respond to new regulatory standards promptly.
Client Management. Sponsors might change their requirements as they are exploring together with us.

Medium

Medium

B

  • Team to stay proactive about the potential changes and communicate frequently with the sponsors.
Project Management. It is a new business model leveraging on latest technology, hence there might be misunderstandings about the business requirements.

Medium

Medium

B

  • Schedule more meetings with our sponsors and do more research to get a deeper understanding of the requirements.

Past Risks (After Midterms):

Risk Likelihood Impact Category Mitigation Plan
Lack of Finance Knowledge which is required to develop the main functionalities of the application & essentially predictive analytics chart

High

High

A

  • Schedule more time to self learn the basics required for predictive analytics chart. Consult experts on clarity. Conduct more user testings on this function to get more insights to user's understanding and behavior
Technical Complexities


Citadelcomplexities1.png
Citadelcomplexities2.png
Citadelcomplexities3.png
Citadelcomplexities4.png
Citadelcomplexities5.png
Citadelcomplexities6.png
Citadelcomplexities7.png
Citadelcomplexities8.png
NewCitadelComplexities9.png
NewCitadelComplexities2.png
NewCitadelComplexities211111.png
NewCitadelComplexities211.png
NewCitadelComplexities2111.png



Architecture Diagram


Citadel Technologies.png
Citadel TechnologiesUsed.png

Quality of product

Immediate Deliverables


Topic of Interest Link
Project Management Minutes
Metrics
Risk Management
Change Management
Project Overview Project Overview
Project Documentation Use Case
Architecture Diagram



User Testing 1


User Testing 1

Scope

  • View deals from primary and secondary market
  • Add a new Buy/Sell order
  • Accept a new Buy/Sell
  • View Trade Portfolio
  • Cancel an order
  • View history
  • Able to change password



Citadel UAT Before.png


Function Changes made
Accept Order Changed "Accept" button to "Sell" and "Buy" to differentiate
Color Scheme Changed to a more elegant, less dazzling color scheme
Login Changed frontend spinner code accordingly
Security Included Touch ID Verification for users before proceeding any confirmation of purchases
Chat bot Developed a chat bot within the app to answer/direct user queries, providing almost instantaneous reply.
Analytics Included a analytics chart showing the past performance of a certain deal or a user's portfolio investment performance to provide better insights. Future pending development include predictive analysis.
UI/UX More intuitive outlook at "Find Deals" in Primary and Secondary Market.
Multi-Language Provided more language option apart from English. Included Simplified Chinese Version in the application.


Citadel UAT after.png


User Testing 2

User Testing 2

Venue: SIS GSR 2-2
Time: 4pm-7pm
Number of participants: 20

Citadel UAT2.png



Citadel UAT2charts.png

Summary of Key Findings:

Function Users' Behavior Changes to be Made
Cancel Order User suggested to add touch ID for cancel order We will include touch ID for cancel order
Place New Order When user placed a new order, there are some overlap in that page We will fix the problem by changing front-end code
Balance Page The chart to display the lock balance and available balance is confusing We will add explanation in the chart
Drawer for IOS When user change to simplified Chinese version, IOS version's drawer is not translated We faced some difficulties on this issue and we will fix it before finals
Login First time login fail will cause the second time login to have the same pop up information even when login is successful We will fix the problem by changing front-end code
Terms and Condition Users try to click the terms and conditions but it cannot work We will add the terms and conditions link
Help Page The keyboard cannot be dismissed after typing We will fix the problem by changing front-end code
Help Bot Some users feel the bot is not very useful We will keep training the bot and make it smarter



User Testing 3

User Testing 3

Venue: SIS GSR 2-4
Date: 10th November 2017
Time: 4pm-5.30pm
Number of participants: 10
Scope (Trial preparation for our UAT on 14th November 2017)

  • View deals from primary and secondary market
  • Add a new Buy/Sell order
  • Accept a new Buy/Sell
  • View Trade Portfolio
  • Cancel an order
  • View history
  • Able to change password


Function Changes to be made
iOS User feedback that iOS drawer does not support multi-language
Alert Messages When user received alerts, the language did not change according to the selected preferred language
Operation timeout error message Some users experienced extended period of timeout but did not receive error message to notify them


User Acceptance Test

User Acceptance Test

Venue: SIS GSR 2-1
Time: 12pm-1pm
Number of participants: 33
You can download our User Guide and Lab Questionaire

CitadelUATClassphotos.png


Summary of User Behavior:
User Overview

UserOverview.png
UserOverview1.png


Screens Overview

UserOverview3.png


Session Data Overview

UserOverview4.png


User Behavior Overview

UserOverview5.png
UserOverview6.png
UserOverview7.png

Summary of Key Findings (To be updated once TA of Retail Banking class sends us lab documents uploaded to DropBox by students):

Function Users' Behavior Changes to be Made




Handover Meeting

Handover Meeting with Sponsor at FundPlaces Office

Handover (Citadel).jpg

Team Citadel met up with our sponsor at FundPlaces office to discuss about FYP handover. Sponsor expressed great satisfaction to our end product of the application and will endorse their full support in signing off the testings we conducted over the past 3 months to ensure functionalities are all good to be push to production once MAS regulations are cleared.


Team Reflection


Team Reflection:
Communication with our Sponsors and Supervisor is very important in order for our team to keep align with the requirements and to avoid mismatch of expectations. This is especially so during this time period where we are expecting and anticipating changes from MAS regulations which directly impact the operations of our sponsor company. Our team has set out clear communications and in frequent contact, meetings with sponsors and supervisors.

Shangguan Yajie:
Through this project, I have learnt the following:

  • As a project manager, I understand the importance of stakeholder management and planning and also I need to always have backup plans and be flexible when changes occurs.
  • As a team, we need to adapt to different working styles and sometimes compromise is necessary
  • It is very importance to conduct different testing in different stages and getting users' feedback.


Vivian Quark:
This FYP have taught me about Murphy's law- If something can go wrong, it can go wrong. There are numerous hiccups along the way and I have learnt how to manage user's expectations,sponsor's expectations and team's expectations. User testings gave great insights on how we can further improve our applications and the team have always been committed of continuous learning and continuous improvement. I have learnt how important it is in putting user empathy first in any functionalities or user interfaces we develop. Secondly, there is a need to constantly gather feedback and do research on consumer behavior, to think in their perspective and to discover what terminologies/functionalities they may find it difficult to understand. It has been a great learning experience to collect these qualitative and quantitative data and correlate them to customer journey, application performance and business outcomes.

Qi Zhen Yi:
Through this whole journey of FYP, I have picked up valuable skills which could only be learnt with such experiences and the team. There were many mind blowing nights and days which we spent as a group and achieved our milestone. And finally we are here. As an individual, not only I have picked up design, technical and financial knowledge through out the journey. The most challenging and fulfilling experience for me is always meeting expectation of the team. While I first started my role as app designer, I prefer to follow my own way and not willing to easily give in for others’ preferences. So at the time, it was tough for me. However, I was glad that despite all the differences, we still managed to work as a team and learn to communicate with others. I also learnt to be more proactive and ask more for feedbacks and try to resolve any issues at early stage. Really glad we made it through and did our best as a team.

Xu Jia Wen:
We could have gone for a safer choice for this FYP but we didn't. We wanted to do something more innovative, more industry-related in a real-world context. So except all the cutting-edge technologies we learnt for this project, I learnt how to deal with challenges and deal with difficult people. We did face many challenges and hit some bumps during the journey. But we managed to get through all of them and bounced back stronger. And I think all the challenges we faced in this project , such as MAS regulation issue and non-compatible technology issue, do happen a lot in real life. And all these invaluable experiences will definitely help me in my future career.

Yongyi:
After the last major milestone, I took a deeper dive in to analytics and code performance optimization. We worked as a group and came up with ways to make our code more efficient. I also learned how to modularize Javascript code with closures, for better readability and modularity. Although we faced challenges, by working closely within ourselves and with our sponsor we managed to overcome them.

Jinlong:
This Final Year Project has been a great journey, I am fully exposed to the new technologies such as react-native and managed to master it eventually. At the beginning, I feel foreign to React-native because I am a native Android developer. However, my perspective towards React-native changes as I realized it is a powerful framework. Similar to AngularJS, react-native is also written in JS(X) and has the concept of one-way binding.

I feel that it is revolutionary as it saves a lot of time dedicated in development phase. During the last hurdle of our project, I encountered what I considered as the biggest issue in FYP which is, React-native has its own limitation in functions like web-socket. After much tries and struggles, I decided to convert and do it as a hybrid app. From this, I learnt we should not just rely on one tech because sometimes hybrid is better!

As the main front-end developer, I shoulder a huge responsibility in UI/UX. However, one shortcoming is that I have not take IDP classes yet and UI is proven to be challenging to me at the start. With the help from Jia Wen, we managed to revamp our UI and make it extraordinary! Team work is essentially important especially when we meet with challenges and solidarity makes our group to be outstanding!