HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2017T2 Mavericks Finals Wiki"

From IS480
Jump to navigation Jump to search
 
(66 intermediate revisions by the same user not shown)
Line 44: Line 44:
 
|}
 
|}
 
<!--Sub Header End-->
 
<!--Sub Header End-->
 +
<br>
 +
[[File:Mv-progress-banner.png|1000px|center|link=]]
  
==Project Progress Summary==
+
<center>
 +
{|
 +
|-
 +
| [[File:Screen Shot 2018-04-03 at 2.10.13 PM.png|300px|link=https://wiki.smu.edu.sg/is480/File%3AFYP_Finals_v6.pdf]]||  [[File:Screen Shot 2018-04-03 at 2.10.13 PM 2.png|300px|center|link=https://tbankonline.com/SMUtBank_tBuddy/]]       
 +
|}
 +
<div style="text-align:; font-family:avenir; font-size:85%; ">
 +
This website is restricted to tBuddy account holders. <br>
 +
To gain access to the test account, <br>please contact Project Manager.
 +
</div>
 +
</center>
  
Place your Final slides link and deployed site link here
+
[[File:Mv-1.png|800px|center|link=]]<br>
 +
[[File:Screen Shot 2018-04-03 at 9.29.24 PM.png|550px|center|link=]]<br>
  
For proposal, please see Requrements at the Project Deliverables. This will help us understand your scope. Note wiki policy [[Help:Contents|here]].
+
[[File:Mv-2.png|800px|center|link=]]<br>
 +
[[File:Screen Shot 2018-04-03 at 9.12.52 PM.png|800px|center|link=]]<br>
  
This page should NOT be too long. It should link to other pages in the IS480 team wiki. Do not repeat the proposal, midterm or other wiki information here. Highlight changes since [[IS480_Midterm_Wiki | midterm]].
+
[[File:Mv-3.png|800px|center|link=]]<br>
 +
[[File:Screen Shot 2018-04-03 at 10.08.45 PM.png|600px|center|link=]]<br>
  
Describe the project progress briefly here. Is the project completed? Link to the final presentation slides and videos.
+
[[File:Mv-mgmt-banner.png|1000px|center|link=]]<br>
  
===Project Highlights:===
+
[[File:Screen Shot 2018-04-03 at 10.19.53 PM.png|700px|center|link=]]<br>
  
What unexpected events occurred and how were they handled?
+
[[File:Mv-4.png|800px|center|link=]]<br>
*A team member left the project and dropped the course
+
[[Image:MV-scope-4.png|center|600px|link=]]<br>
*List of requirement changes
+
<center>
** CRUD items replaced with CU/Sync/Archive items
+
{| class="wikitable" style="text-align: center; font-size:85%; border-spacing:4px; border:1px solid #7EB2B9; background:white; width: 750px;" align="center""
** Business analytics replaced with iPad client
+
|- style="background:#D3D3D3; color:black"
*Took 8 weeks to learn Ruby on Rails
+
! style="font-weight:bold;background: #7EB2B9;color:#000; width:65px; border:0px solid #2e2e2e" | Iteration
*etc.
+
! style="font-weight:bold;background: #7EB2B9;color:#000; width:65px; border:0px solid #2e2e2e" | Scope
Be brief. A couple of sentences on the event and another couple on what was done is sufficient. Do not repeat the next sub sections. If there are no highlights, remove this section
+
! style="font-weight:bold;background: #7EB2B9;color:#000; width:300px; border:0px solid #2e2e2e" | Module
 
+
! style="font-weight:bold;background: #7EB2B9;color:#000; width:135px; border:0px solid #2e2e2e" | Task
===Project Challenges:===
+
! style="font-weight:bold;background: #7EB2B9;color:#000; width:360px; border:0px solid #2e2e2e" | Planned/New Feature
 
+
! style="font-weight:bold;background: #7EB2B9;color:#000; width:360px; border:0px solid #2e2e2e" | Status
Describe areas of the project that were particularly difficult and how they were dealt with, whether successfully or not. Again, a few sentences are enough. If there are no challenges, remove this section.
+
! style="font-weight:bold;background: #7EB2B9;color:#000; width:360px; border:0px solid #2e2e2e" | Confidence Level
 
+
! style="font-weight:bold;background: #7EB2B9;color:#000; width:360px; border:0px solid #2e2e2e" | Comments
===Project Achievements:===
+
|-
 
+
| style="text-align:center" | 2                                     
Methods, technologies, processes, teamwork, etc. which were particularly successful – highlight things which worked very well towards completing the project. A bulleted list of one to two sentences each will do. If there are no achievement, remove this section.
+
| style="text-align:Center" | Core 
 
+
| style="text-align:Center" | Account Module
==Project Management==
+
| style="text-align:left" | Login/Logout
 
+
| style="text-align:center" | Planned   
Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.
+
| style="text-align:center" | Fully deployed and tested 100%
 
+
| style="text-align:center" | 1
===Project Schedule (Plan Vs Actual):===
+
| style="text-align:center" | Reviewed and accepted by sponsor
 
+
|-
Compare the project plan during midterm with the actual work done at this point. Briefly describe a summary here. Everything went as plan, everything has changed and the team is working on a new project with new sponsors or the supervisor is missing. A good source for this section comes from the project weekly report.
+
| style="text-align:center" | 2                                     
 
+
| style="text-align:Center" | Core 
Provide a comparison of the plan and actual schedule. Has the project scope expanded or reduced? You can use the table below or your own gantt charts.
+
| style="text-align:Center" | Customer Request Module
 
+
| style="text-align:left" | - View Account Balance<br>- View Account Details<br>- Funds Transfer<br>- Add Payee<br>- View Payee
{| border="1"
+
| style="text-align:center" | Planned   
|- style="background:blue; color:white"  
+
| style="text-align:center" | Fully deployed and tested 100%
|| Iterations
+
| style="text-align:center" | 1
|colspan="2" align="center"| Planned
+
| style="text-align:center" | Reviewed and accepted by sponsor
|colspan="2" align="center"| Actual
+
|-
|| Comments
+
| style="text-align:center" | 2                                     
 +
| style="text-align:Center" | Core 
 +
| style="text-align:Center" | Chat Module
 +
| style="text-align:left" | View Chat History
 +
| style="text-align:center" | Planned   
 +
| style="text-align:center" | Fully deployed and tested 100%
 +
| style="text-align:center" | 1
 +
| style="text-align:center" | Reviewed and accepted by sponsor
 +
|-
 +
| style="text-align:center" | 2                               
 +
| style="text-align:Center" | Core 
 +
| style="text-align:Center" | Dialog Flow Module
 +
| style="text-align:left" | Manage Entities & Intents
 +
| style="text-align:center" | Planned   
 +
| style="text-align:center" | Fully deployed and tested 100%
 +
| style="text-align:center" | 1
 +
| style="text-align:center" | Reviewed and accepted by sponsor
 +
|-
 +
| style="text-align:center" | 3                                     
 +
| style="text-align:Center" | Core 
 +
| style="text-align:Center" | Security Module
 +
| style="text-align:left" | OTP Management
 +
| style="text-align:center" | Planned   
 +
| style="text-align:center" | Fully deployed and tested 100%
 +
| style="text-align:center" | 1
 +
| style="text-align:center" | Reviewed and accepted by sponsor
 +
|-
 +
|-
 +
| style="text-align:center" | 3                                     
 +
| style="text-align:Center" | Core 
 +
| style="text-align:Center" | Dialog Flow Module
 +
| style="text-align:left" | Process User Requests <br> - AI Events & Exception Handling
 +
| style="text-align:center" | Planned   
 +
| style="text-align:center" | Fully deployed and tested 100%
 +
| style="text-align:center" | 1
 +
| style="text-align:center" | Reviewed and accepted by sponsor
 +
|-
 +
|-
 +
| style="text-align:center" | 3                                     
 +
| style="text-align:Center" | Core 
 +
| style="text-align:Center" | Chat Module
 +
| style="text-align:left" | Speech-to-text Processing
 +
| style="text-align:center" | Planned   
 +
| style="text-align:center" | Fully deployed and tested 100%
 +
| style="text-align:center" | 1
 +
| style="text-align:center" | Reviewed and accepted by sponsor
 +
|-
 +
|-
 +
| style="text-align:center" | 3                                     
 +
| style="text-align:Center" | Core 
 +
| style="text-align:Center" | Admin Module I
 +
| style="text-align:left" | - Live Chat Takeover<br> - Receive Notifications<br>
 +
| style="text-align:center" | Planned   
 +
| style="text-align:center" | Fully deployed and tested 100%
 +
| style="text-align:center" | 1
 +
| style="text-align:center" | Reviewed and accepted by sponsor
 +
|-
 +
| style="text-align:center" | 4                                     
 +
| style="text-align:Center" | Core 
 +
| style="text-align:Center" | Admin Module I
 +
| style="text-align:left" | View All Chats
 +
| style="text-align:center" | Planned   
 +
| style="text-align:center" | Fully deployed and tested 100%
 +
| style="text-align:center" | 1
 +
| style="text-align:center" | Reviewed and accepted by sponsor
 +
|-
 +
| style="text-align:center" | 5                                     
 +
| style="text-align:Center" | Core 
 +
| style="text-align:Center" | Admin Module I
 +
| style="text-align:left" | Receive Notifications
 +
| style="text-align:center" | Planned   
 +
| style="text-align:center" | Fully deployed and tested 100%
 +
| style="text-align:center" | 1
 +
| style="text-align:center" | Reviewed and accepted by sponsor
 +
|-
 +
| style="text-align:center" | 5                                     
 +
| style="text-align:Center" | Core 
 +
| style="text-align:Center" | Customer Request Module
 +
| style="text-align:left" | View Transaction History
 +
| style="text-align:center" | Planned   
 +
| style="text-align:center" | Fully deployed and tested 100%
 +
| style="text-align:center" | 1
 +
| style="text-align:center" | Reviewed and accepted by sponsor
 +
|-
 +
| style="text-align:center" | 6                                     
 +
| style="text-align:Center" | Core 
 +
| style="text-align:Center" | Customer Request Module
 +
| style="text-align:left" | - Request Loan<br> - Agg. Expense View<br> - Loan Calculator<br> - Bill Payment<br>
 +
| style="text-align:center" | Planned   
 +
| style="text-align:center" | Fully deployed and tested 100%
 +
| style="text-align:center" | 1
 +
| style="text-align:center" | Reviewed and accepted by sponsor
 +
|-
 +
| style="text-align:center" | 7                                     
 +
| style="text-align:Center" | Core 
 +
| style="text-align:Center" | Educational Module
 +
| style="text-align:left" | Assessment Quiz (Backend Logic)
 +
| style="text-align:center" | Planned   
 +
| style="text-align:center" | Fully deployed and tested 100%
 +
| style="text-align:center" | 1
 +
| style="text-align:center" | Reviewed and accepted by sponsor
 +
|-
 +
| style="text-align:center" | 8                                   
 +
| style="text-align:Center" | Core 
 +
| style="text-align:Center" | Educational Module
 +
| style="text-align:left" | Glossary of Terms
 +
| style="text-align:center" | Planned   
 +
| style="text-align:center" | Fully deployed and tested 100%
 +
| style="text-align:center" | 1
 +
| style="text-align:center" | Reviewed and accepted by sponsor
 +
|-
 +
| style="text-align:center" | 8                                     
 +
| style="text-align:Center" | Core 
 +
| style="text-align:Center" | Customer Request Module
 +
| style="text-align:left" | - View Standing Instructions<br> - Create Standing Instructions<br>
 +
| style="text-align:center" | Planned   
 +
| style="text-align:center" | Fully deployed and tested 100%
 +
| style="text-align:center" | 1
 +
| style="text-align:center" | Reviewed and accepted by sponsor
 +
|-
 +
| style="text-align:center" | 9                                     
 +
| style="text-align:Center" | Core 
 +
| style="text-align:Center" | Educational Module
 +
| style="text-align:left" | - Assessment Quiz (Creation)<br> - Architecture View<br>
 +
| style="text-align:center" | Planned   
 +
| style="text-align:center" | Fully deployed and tested 100%
 +
| style="text-align:center" | 1
 +
| style="text-align:center" | Reviewed and accepted by sponsor
 +
|-
 +
| style="text-align:center" | 9                                     
 +
| style="text-align:Center" | Core 
 +
| style="text-align:Center" | Admin Module II
 +
| style="text-align:left" | Live Scoreboard
 +
| style="text-align:center" | Planned    
 +
| style="text-align:center" | Fully deployed and tested 100%
 +
| style="text-align:center" | 1
 +
| style="text-align:center" | Reviewed and accepted by sponsor
 
|-
 
|-
 
+
| style="text-align:center" | 11                                     
|rowspan="2"| 1
+
| style="text-align:Center" | Core 
|| Customer CRUD
+
| style="text-align:Center" | Educational Module
|| 1 Sept 2010
+
| style="text-align:left" | Request-Reply Details of API
||
+
| style="text-align:center" | Planned   
|| 25 Aug 2010
+
| style="text-align:center" | Fully deployed and tested 100%
|| Fiona took the Sales CRUD as well.
+
| style="text-align:center" | 1
 +
| style="text-align:center" | Reviewed and accepted by sponsor
 
|-
 
|-
 
+
| style="text-align:center" | 11                                     
|| Trend Analytic
+
| style="text-align:Center" | Core 
|| 1 Sept 2010
+
| style="text-align:Center" | Admin Module II
||  
+
| style="text-align:left" | Descriptive Analysis
|| 15 Sept 2010
+
| style="text-align:center" | Planned   
|| Ben is too busy and pushed iteration 1 back
+
| style="text-align:center" | Fully deployed and tested 100%
 +
| style="text-align:center" | 1
 +
| style="text-align:center" | Reviewed and accepted by sponsor
 
|-
 
|-
 
+
| style="text-align:center" | 12                                     
|rowspan="2"| 2
+
| style="text-align:Center" | Core 
|| User tutorial
+
| style="text-align:Center" | Educational Module
|| 1 Oct 2010
+
| style="text-align:left" | Assessment Quiz (New Changes)
|colspan="2"|  
+
| style="text-align:center" | New
|| Removed proposed by Ben
+
| style="text-align:center" | Fully deployed and tested 100%
 +
| style="text-align:center" | 1
 +
| style="text-align:center" | Reviewed and accepted by sponsor
 
|-
 
|-
 +
| style="text-align:center" | 12                                     
 +
| style="text-align:Center" | Core 
 +
| style="text-align:Center" | Admin Module II
 +
| style="text-align:left" | Live Support Analysis
 +
| style="text-align:center" | New
 +
| style="text-align:center" | Fully deployed and tested 100%
 +
| style="text-align:center" | 1
 +
| style="text-align:center" | Reviewed and accepted by sponsor
 +
|}</center><br>
  
|colspan="2"|
+
[[File:Mv-5.png|800px|center|link=]]<br>
|| Psycho analysis
 
|| 1 Oct 2010
 
|| New module proposed by sponsor
 
|}
 
 
 
===Project Metrics:===
 
  
Summary of analysis for the metrics collected. You may refer to another page for the details about the metrics and how it is collected.
+
<div style="text-align: center; font-size:85%; ">
 +
<b>Planned Schedule</b>
 +
[[Image:Screen Shot 2018-04-03 at 2.25.58 PM.png|center|900px|link=]]
  
===Technical Complexity:===
+
<b>Actual Schedule</b>
 +
[[Image:Project Timeline.005.jpeg|center|900px|link=]]
  
Describe and list the technical complexity of your project in order of highest complexity first. For example, deploying on iPhone using Objective-C, customizing Drupal with own database, quick search for shortest flight path, database structure, etc.
+
[[File:Mv-6.png|800px|center|link=]]<br><br>
  
==Quality of product==
+
<center>[[File:MV-TaskMetrics.PNG|450px]][[File:Bug Metric.PNG|480px]]<br>
  
Provide more details about the quality of your work. For example, you designed a flexible configurable system using XML.config files, uses Strategy Design Pattern to allow plugging in different strategy, implement a regular expression parser to map a flexible formula editor, etc.  
+
For more information on metrics collected, please refer [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Metrics here].</center><br>
 +
</div>
  
===Project Deliverables:===
+
[[File:Mv-quality-banner.png|1000px|center|link=]]<br>
  
List the artifacts produced for this project. The entire deliverable can be submitted in a separate thumb drive, web repository or place in the IS480 team wiki.
+
[[File:Mv-a.png|800px|center|link=]]
  
{| border="1"
+
<center>
|- style="background:blue; color:white"  
+
{| class="wikitable" style="font-family:helvetica; font-size:85%; background-color:#FFFFFF; width: 750px;" align="center"; border="1"
 +
|- style="background:#D3D3D3; color:black"  
 
|align="center"| Stage  
 
|align="center"| Stage  
 
|align="center"| Specification
 
|align="center"| Specification
Line 143: Line 306:
 
|-
 
|-
  
|rowspan="2"| Project Management
+
|rowspan="4"| Project Management
|| Minutes
+
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Meeting_Minutes Minutes]
|| Sponsor weeks -10 -5 3 7 Supervisor weeks -2 3 5 7
+
|| Minutes with Sponsor, Internal Team & Supervisor
 
|-
 
|-
  
|| Metrics
+
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Project_Schedule Schedule]
|| Bug metrics
+
|| Project Schedule
 
|-
 
|-
  
|| Requirements
+
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Metrics Metrics]
|| Story cards
+
|| Bug Metrics, Task Metrics
|| [http://www.agilemodeling.com/artifacts/userStory.htm CRUD Customer], [http://www.agilemodeling.com/artifacts/userStory.htm Trend Analytic]
 
 
|-
 
|-
  
|rowspan="4"| Analysis
+
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Risk_Mitigation Risk Mitigation]
|| Use case
+
|| Risks & Mitigation
|| [http://en.wikipedia.org/wiki/Use_case_diagram overall]
 
 
|-
 
|-
  
|| System Sequence Diagram
+
|rowspan="3"| Requirements
|| [http://en.wikipedia.org/wiki/System_Sequence_Diagram client], [http://en.wikipedia.org/wiki/System_Sequence_Diagram server]
+
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Description_and_Motivation Overview]
 +
|| Project Description
 
|-
 
|-
  
|| [http://en.wikipedia.org/wiki/Business_Process_Modeling_Notation Business Process Diagram]
+
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Project_Scope Scope]
||  
+
|| Project Scope
 
|-
 
|-
  
|| Screen Shots
+
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Documentation Scenarios]
|| CRUD Customer, Trend Analysis
+
|| Personas & Scenario
 
|-
 
|-
 +
 +
 +
|rowspan="2"| Analysis
 +
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Diagrams System Architecture Diagram]
 +
|| System Architecture Diagram
 +
|-
 +
 +
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Diagrams Technologies Used]
 +
|| Technologies Used
 +
|-
  
 
|rowspan="2"| Design
 
|rowspan="2"| Design
|| [http://en.wikipedia.org/wiki/Entity-relationship_model ER Diagram]
+
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Diagrams ER Diagram]
|| 1, 2, 3
+
|| ER Diagram
 
|-
 
|-
  
|| [http://en.wikipedia.org/wiki/Class_diagram Class Diagram]
+
|| Prototype
|| [http://en.wikipedia.org/wiki/Class_diagram 1], [http://en.wikipedia.org/wiki/Class_diagram 2], [http://en.wikipedia.org/wiki/Class_diagram 3]
+
|| [https://youtu.be/BEHdTrV4AZQ Video of tBuddy Prototype]
 
|-
 
|-
  
 +
|rowspan="4"| Testing
 +
|| User Testing 1
 +
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_User_Testing_1 UT1 - 6 Nov 2017]
 +
|-
  
|| Testing
+
|| User Testing 2
|| Test plan
+
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_User_Testing_2 UT2 - 26 Jan 2018 ]
|| [[IS480_Midterm_Wiki#Testing: | instructions]]
 
 
|-
 
|-
  
|rowspan="3"| Handover
+
|| User Testing 3
|| Manuals
+
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_User_Testing_3 UT3 - 13 Feb 2018]
|| User tutorial, Developer manual, Setup manual
 
 
|-
 
|-
  
|| Code
+
|| User Testing 4
|| client server
+
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_User_Testing_4 UT4 - 21 Mar 2018]
 
|-
 
|-
  
|| [http://en.wikipedia.org/wiki/Deployment_diagram Deployment Diagram]
+
|rowspan="1"| Proof of Deployment
|| [[IS480_Midterm_Wiki#Deployment: | instructions]]
+
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Proof_of_Deployment Proof of Deployment]
|}
+
|| Lab sessions conducted with NP Diploma Students, SMU Undergraduates & SMU Postgraduates
 +
|-
 +
 
 +
|}<br>
 +
</center>
  
Not all parts of the deliverables are necessary but the evidence should be convincing of the scope.
+
[[File:Mv-Z.png|800px|center|link=]]<br>
  
=== Quality:===
+
[[File:FYP Midterms Presentation.062.jpeg|800px|center|link=]]<br>
 +
[[File:FYP Midterms Presentation.019.jpeg|500px|center|link=]]<br>
 +
[[File:FYP Midterms Presentation.063.jpeg|800px|center|link=]]<br>
 +
[[File:FYP Midterms Presentation.065.jpeg|800px|center|link=]]
  
Explain the quality attributes (non functional) of your project deliverables. Have you designed the architecture, use a design pattern, etc? Does your architecture address scalability, performance, reliability, availability, fault tolerance, usability, etc. Does your design address maintainability, flexibility, configurability, etc. Be brief here but you can link to diagrams or code detail pages. Do not repeat the technical complexity part, link to it if necessary.
+
[[File:Mv-D.png|800px|center|link=]]<br>
  
===Deployment:===
+
<div style="text-align: center; font-family:avenir; font-size:97%; ">
 +
Internal Testing is performed for every new function developed.<br>
 +
Team Mavericks has scheduled for 4 User Testings in total.<br>
 +
We have accomplished all User Testings as of Iteration 14.<br>
  
In an iterative approach, ready to use system should be available (deployed) for client and instructions to access the system described here (user name). If necessary, provide a [[IS480_Final_Wiki#Project_Deliverables: | deployment diagram link]].
+
For more information regarding User Testing and view results, please click [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_User_Testing here].
 +
</div><br>
  
===Testing:===
+
[[File:mv-reflections-banner.png|1000px|center|link=]]<br>
  
Describe the testing done on your system. For example, the number of user testing, tester profile, test cases, survey results, issue tracker, bug reports, etc.
+
<div style="text-align:; font-family:avenir; font-size:97%; ">
 +
<b>Team Reflection</b><br>
 +
This project has made us realise that positive synergy is the holy grail of team work. Despite our differences in backgrounds, capabilities and perspectives, we have built common goals - to excel and to enjoy the most from this learning process. Through open communication and respect for others, we were able to find common consensus when solving problems. Since mid-terms, our team has improved on our application in terms of ease of use, UI design and its effectiveness as a learning tool. We are proud that our overall ratings after mid-terms have increased to an average of 4.0/5.0 in all aspects. As a team, we are proud to progress together to achieve our individual and group outcomes, while building a successful implementation of tBuddy for our sponsor.<br>
 +
<br>
 +
'''Jamie's Reflection'''<br>
 +
After 14 long iterations of working on this project, I've learnt that the Murphy's law ("whatever can go wrong, will go wrong"), is nonetheless true. Although the progress of our project was relatively smooth, there were some hiccups that occurred along the way. Fortunately, it was indeed through sweat, blood and tears that allowed us to accomplish what we have today. We have tested this application with users of different educational backgrounds and received invaluable feedback on our project. And I'm pleased to say that today, all of us can shed happy tears to witness how tBuddy can make meaningful impact in one's learning through fun and interaction. <br><br>
  
==Reflection==
+
'''Yi Xiang's Reflection'''<br>
  
Compile common lessons and reflection for the team and for each team member. Be brief.
+
As a backend developer, I've learnt that modern backend development is not just about coding anymore, it also about the architecture. Hence, the ability to be able integrate all the different components of the application together seamlessly. This project has allowed me to leverage on several third-party tools out there alongside with our own development.<br><br>
  
===Team Reflection:===
+
'''Gerald's Reflection'''<br>
 +
As a full stack developer of tBuddy, I have learnt the importance of performance and test driven development. Our application consumes a few services, such as the tBank api, dialogflow and goglespeech. I have picked up techniques to retain recyclable information and optimise performance. Also, a test driven development ensures that the application will continue to function and provide the right feedback even when users action are anomalous. In this project, I have mainly contributed to the architectural design of the application, the designing and development of the admin module, the live support system and the aggregated expense function. The aggregated expense was coincidentally rolled out on DBS iBanking at the time of writing. I have also contributed to the configurations of the Dialogflow service and is in charge of infrastructure and deployments configuration.
  
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 | knowledge base]] and linked here.
 
  
===Individual Reflection:===
+
'''Bertran's Reflection'''<br>
 +
As the front-end developer of tBuddy, not only did I learn a new front-end framework, Framework 7, I had the opportunity to work on web audio recording as well as web socket streaming.
  
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:===
+
'''Yi An's Reflection'''<br>
Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.
+
As Quality Assurance Lead, it was great working with the team in producing a high quality product to our sponsor. I learnt that attention to details is very important in any project and the opportunity to create a product with real users has been an exciting and fruitful experience.
 +
<br>
 +
<br>
 +
<b>Sponsor's Comment</b><br>
 +
This was quite a complex project, done well by only a 5 member team.  Very strong technical skills.  The AI chatbot idea was theirs, and they came up with the architecture and implemented it.  They made good use of the SMU tBank API to perform the banking transactions.  Of the 8 FYP projects I have sponsored so far, this is the only team that has done a proof of deployment (in a classroom lab session) for 3 different tiers of education; polytechnic, undergrad, and postgrad. Overall, great job!
 +
<br>
 +
</div>

Latest revision as of 15:18, 10 April 2018

MV-background.png


MV-home.png   HOME

 

MV-logo.png   ABOUT US

 

MV-overview.png   PROJECT OVERVIEW

 

MV-schedule.png   PROJECT MANAGEMENT

 

MV-documentation.png   DOCUMENTATION

Main Wiki

Midterms Wiki

Finals Wiki


Mv-progress-banner.png
Screen Shot 2018-04-03 at 2.10.13 PM.png
Screen Shot 2018-04-03 at 2.10.13 PM 2.png

This website is restricted to tBuddy account holders.
To gain access to the test account,
please contact Project Manager.

Mv-1.png


Screen Shot 2018-04-03 at 9.29.24 PM.png


Mv-2.png


Screen Shot 2018-04-03 at 9.12.52 PM.png


Mv-3.png


Screen Shot 2018-04-03 at 10.08.45 PM.png


Mv-mgmt-banner.png


Screen Shot 2018-04-03 at 10.19.53 PM.png


Mv-4.png


MV-scope-4.png


Iteration Scope Module Task Planned/New Feature Status Confidence Level Comments
2 Core Account Module Login/Logout Planned Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
2 Core Customer Request Module - View Account Balance
- View Account Details
- Funds Transfer
- Add Payee
- View Payee
Planned Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
2 Core Chat Module View Chat History Planned Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
2 Core Dialog Flow Module Manage Entities & Intents Planned Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
3 Core Security Module OTP Management Planned Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
3 Core Dialog Flow Module Process User Requests
- AI Events & Exception Handling
Planned Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
3 Core Chat Module Speech-to-text Processing Planned Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
3 Core Admin Module I - Live Chat Takeover
- Receive Notifications
Planned Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
4 Core Admin Module I View All Chats Planned Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
5 Core Admin Module I Receive Notifications Planned Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
5 Core Customer Request Module View Transaction History Planned Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
6 Core Customer Request Module - Request Loan
- Agg. Expense View
- Loan Calculator
- Bill Payment
Planned Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
7 Core Educational Module Assessment Quiz (Backend Logic) Planned Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
8 Core Educational Module Glossary of Terms Planned Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
8 Core Customer Request Module - View Standing Instructions
- Create Standing Instructions
Planned Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
9 Core Educational Module - Assessment Quiz (Creation)
- Architecture View
Planned Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
9 Core Admin Module II Live Scoreboard Planned Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
11 Core Educational Module Request-Reply Details of API Planned Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
11 Core Admin Module II Descriptive Analysis Planned Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
12 Core Educational Module Assessment Quiz (New Changes) New Fully deployed and tested 100% 1 Reviewed and accepted by sponsor
12 Core Admin Module II Live Support Analysis New Fully deployed and tested 100% 1 Reviewed and accepted by sponsor


Mv-5.png


Planned Schedule

Screen Shot 2018-04-03 at 2.25.58 PM.png

Actual Schedule

Project Timeline.005.jpeg
Mv-6.png


MV-TaskMetrics.PNGBug Metric.PNG
For more information on metrics collected, please refer here.

Mv-quality-banner.png


Mv-a.png
Stage Specification Modules
Project Management Minutes Minutes with Sponsor, Internal Team & Supervisor
Schedule Project Schedule
Metrics Bug Metrics, Task Metrics
Risk Mitigation Risks & Mitigation
Requirements Overview Project Description
Scope Project Scope
Scenarios Personas & Scenario
Analysis System Architecture Diagram System Architecture Diagram
Technologies Used Technologies Used
Design ER Diagram ER Diagram
Prototype Video of tBuddy Prototype
Testing User Testing 1 UT1 - 6 Nov 2017
User Testing 2 UT2 - 26 Jan 2018
User Testing 3 UT3 - 13 Feb 2018
User Testing 4 UT4 - 21 Mar 2018
Proof of Deployment Proof of Deployment Lab sessions conducted with NP Diploma Students, SMU Undergraduates & SMU Postgraduates

Mv-Z.png


FYP Midterms Presentation.062.jpeg


FYP Midterms Presentation.019.jpeg


FYP Midterms Presentation.063.jpeg


FYP Midterms Presentation.065.jpeg
Mv-D.png


Internal Testing is performed for every new function developed.
Team Mavericks has scheduled for 4 User Testings in total.
We have accomplished all User Testings as of Iteration 14.

For more information regarding User Testing and view results, please click here.


Mv-reflections-banner.png


Team Reflection
This project has made us realise that positive synergy is the holy grail of team work. Despite our differences in backgrounds, capabilities and perspectives, we have built common goals - to excel and to enjoy the most from this learning process. Through open communication and respect for others, we were able to find common consensus when solving problems. Since mid-terms, our team has improved on our application in terms of ease of use, UI design and its effectiveness as a learning tool. We are proud that our overall ratings after mid-terms have increased to an average of 4.0/5.0 in all aspects. As a team, we are proud to progress together to achieve our individual and group outcomes, while building a successful implementation of tBuddy for our sponsor.

Jamie's Reflection
After 14 long iterations of working on this project, I've learnt that the Murphy's law ("whatever can go wrong, will go wrong"), is nonetheless true. Although the progress of our project was relatively smooth, there were some hiccups that occurred along the way. Fortunately, it was indeed through sweat, blood and tears that allowed us to accomplish what we have today. We have tested this application with users of different educational backgrounds and received invaluable feedback on our project. And I'm pleased to say that today, all of us can shed happy tears to witness how tBuddy can make meaningful impact in one's learning through fun and interaction.

Yi Xiang's Reflection

As a backend developer, I've learnt that modern backend development is not just about coding anymore, it also about the architecture. Hence, the ability to be able integrate all the different components of the application together seamlessly. This project has allowed me to leverage on several third-party tools out there alongside with our own development.

Gerald's Reflection
As a full stack developer of tBuddy, I have learnt the importance of performance and test driven development. Our application consumes a few services, such as the tBank api, dialogflow and goglespeech. I have picked up techniques to retain recyclable information and optimise performance. Also, a test driven development ensures that the application will continue to function and provide the right feedback even when users action are anomalous. In this project, I have mainly contributed to the architectural design of the application, the designing and development of the admin module, the live support system and the aggregated expense function. The aggregated expense was coincidentally rolled out on DBS iBanking at the time of writing. I have also contributed to the configurations of the Dialogflow service and is in charge of infrastructure and deployments configuration.


Bertran's Reflection
As the front-end developer of tBuddy, not only did I learn a new front-end framework, Framework 7, I had the opportunity to work on web audio recording as well as web socket streaming.


Yi An's Reflection
As Quality Assurance Lead, it was great working with the team in producing a high quality product to our sponsor. I learnt that attention to details is very important in any project and the opportunity to create a product with real users has been an exciting and fruitful experience.

Sponsor's Comment
This was quite a complex project, done well by only a 5 member team. Very strong technical skills. The AI chatbot idea was theirs, and they came up with the architecture and implemented it. They made good use of the SMU tBank API to perform the banking transactions. Of the 8 FYP projects I have sponsored so far, this is the only team that has done a proof of deployment (in a classroom lab session) for 3 different tiers of education; polytechnic, undergrad, and postgrad. Overall, great job!