HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
Line 472: Line 472:
 
<b>Time:</b> 12pm-1pm <br>
 
<b>Time:</b> 12pm-1pm <br>
 
<b>Number of participants:</b> 33 <br>
 
<b>Number of participants:</b> 33 <br>
<b>You can download our <u>User Guide</u> and <u>Lab Questionaire</u></b>
+
<b>You can download our [[Media:CitadelUserGuide.pdf|User Guide]] and [[Media:CitadelFinalLab.pdf|Lab Questionaire]] </b>
[[Media:CitadelUserGuide.pdf|User Guide]] <br>
+
 
[[Media:CitadelFinalLab.pdf|Lab Questionaire]] <br>
 
 
[[File:CitadelUATClassphotos.png|center|1100px]]
 
[[File:CitadelUATClassphotos.png|center|1100px]]
 
<br><Br>
 
<br><Br>

Revision as of 14:26, 14 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


Project Schedule


Iteration Modules Scope Status
2 Account Module Core Completed
2 Order Matching Module Core Completed
3 Account Module Core Completed
3 Usability Module (AI Help Bot) Tertiary Completed
3 Order Matching Module Core Completed
4 Trading Module Core Completed
4 Order Matching Module Core Completed
4 Portfolio Module Core Completed
8 Portfolio Module Core Completed
8 Notification Module Secondary Completed
9 Analytics Module Good to have Completed
9 Order Matching Module Add-ons Completed
11 Multi Language Module Tertiary Completed
11 Filter Module Tertiary Completed
12 Order Matching Module Add-ons Completed


Current Project Schedule


Finals current schedule.png


Planned Project Schedule (Mid Term Review)




Fundplaces Project Timeline ver3.png




Project Metrics Chart




Citadel projmngtcharts.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


NewCitadelComplexities1.png
NewCitadelComplexities2.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: 6th November 2017
Time: 4pm-5.30pm
Number of participants: 10
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



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 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




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.

Qi Zhen Yi:
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.

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:
In the last phase of fyp, we still encountered quite a lot issues in terms of techknowlege. I realized that, even if we use some new techknowledge, it is not perfect, we should not limit ourselves to the languages that we use. The limitation of the techknowledge should not become the limitation of our imagination.