HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
 
(25 intermediate revisions by the same user not shown)
Line 50: Line 50:
 
{|
 
{|
 
|-
 
|-
| [[File:Screen Shot 2018-04-03 at 2.10.13 PM.png|300px|link=]]||  [[File:Screen Shot 2018-04-03 at 2.10.13 PM 2.png|300px|center|link=]]         
+
| [[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>
 
</center>
  
Line 67: Line 71:
 
[[File:Screen Shot 2018-04-03 at 10.19.53 PM.png|700px|center|link=]]<br>
 
[[File:Screen Shot 2018-04-03 at 10.19.53 PM.png|700px|center|link=]]<br>
  
[[File:Mv-4.png|800px|center|link=]]
+
[[File:Mv-4.png|800px|center|link=]]<br>
[[Image:MV-scope-4.png|center|700px|link=]]
+
[[Image:MV-scope-4.png|center|600px|link=]]<br>
<div style="text-align: center; font-size:85%; ">
+
<center>
{| class="wikitable" style="text-align: center; font-size:; border-spacing:4px; border:1px solid #7EB2B9; background:white; "
+
{| class="wikitable" style="text-align: center; font-size:85%; border-spacing:4px; border:1px solid #7EB2B9; background:white; width: 750px;" align="center""
 +
|- style="background:#D3D3D3; color:black"  
 
! style="font-weight:bold;background: #7EB2B9;color:#000; width:65px; border:0px solid #2e2e2e" | Iteration
 
! style="font-weight:bold;background: #7EB2B9;color:#000; width:65px; border:0px solid #2e2e2e" | Iteration
 
! style="font-weight:bold;background: #7EB2B9;color:#000; width:65px; border:0px solid #2e2e2e" | Scope
 
! style="font-weight:bold;background: #7EB2B9;color:#000; width:65px; border:0px solid #2e2e2e" | Scope
Line 271: Line 276:
 
| style="text-align:center" | 1
 
| style="text-align:center" | 1
 
| style="text-align:center" | Reviewed and accepted by sponsor
 
| style="text-align:center" | Reviewed and accepted by sponsor
|}
+
|}</center><br>
</div>
+
 
[[File:Mv-5.png|800px|center|link=]]
+
[[File:Mv-5.png|800px|center|link=]]<br>
  
 
<div style="text-align: center; font-size:85%; ">
 
<div style="text-align: center; font-size:85%; ">
Line 284: Line 289:
 
[[File:Mv-6.png|800px|center|link=]]<br><br>
 
[[File:Mv-6.png|800px|center|link=]]<br><br>
  
<center>[[File:MV-TaskMetrics.PNG|470px]][[File:Mv-bugs.png|500px]]<br>
+
<center>[[File:MV-TaskMetrics.PNG|450px]][[File:Bug Metric.PNG|480px]]<br>
  
 
For more information on metrics collected, please refer [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Metrics here].</center><br>
 
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>
 
</div>
  
[[File:Mv-7.png|800px|center|link=]]
+
[[File:Mv-quality-banner.png|1000px|center|link=]]<br>
 
 
<div style="text-align: center; font-size:85%; ">
 
To be inserted<br>
 
</div>
 
 
 
[[File:Mv-quality-banner.png|1000px|center|link=]]
 
  
[[File:Mv-a.png|800px|center|link=]]<br>
+
[[File:Mv-a.png|800px|center|link=]]
  
 
<center>
 
<center>
Line 309: Line 308:
 
|rowspan="4"| Project Management
 
|rowspan="4"| Project Management
 
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Meeting_Minutes Minutes]
 
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Meeting_Minutes Minutes]
 +
|| Minutes with Sponsor, Internal Team & Supervisor
 
|-
 
|-
  
 
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Project_Schedule Schedule]
 
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Project_Schedule Schedule]
 +
|| Project Schedule
 
|-
 
|-
  
Line 319: Line 320:
  
 
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Risk_Mitigation Risk Mitigation]
 
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Risk_Mitigation Risk Mitigation]
 +
|| Risks & Mitigation
 
|-
 
|-
  
 
|rowspan="3"| Requirements
 
|rowspan="3"| Requirements
 
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Description_and_Motivation Overview]
 
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Description_and_Motivation Overview]
 +
|| Project Description
 
|-
 
|-
  
 
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Project_Scope Scope]
 
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Project_Scope Scope]
 +
|| Project Scope
 
|-
 
|-
  
 
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Documentation Scenarios]
 
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Documentation Scenarios]
 +
|| Personas & Scenario
 
|-
 
|-
  
Line 334: Line 339:
 
|rowspan="2"| Analysis
 
|rowspan="2"| Analysis
 
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Diagrams System Architecture Diagram]
 
|| [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]
 
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Diagrams Technologies Used]
 +
|| Technologies Used
 
|-  
 
|-  
  
 
|rowspan="2"| Design
 
|rowspan="2"| Design
 
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Diagrams ER Diagram]
 
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_Diagrams ER Diagram]
 +
|| ER Diagram
 
|-
 
|-
  
 
|| Prototype
 
|| Prototype
|| Video of tBuddy Prototype
+
|| [https://youtu.be/BEHdTrV4AZQ Video of tBuddy Prototype
 
|-
 
|-
  
Line 361: Line 369:
  
 
|| User Testing 4
 
|| User Testing 4
||  
+
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2017T2_Mavericks_User_Testing_4 UT4 - 21 Mar 2018]
|-
 
 
 
|rowspan="3"| Handover
 
|| Manuals
 
|| User tutorial, Developer manual, Setup manual
 
 
|-
 
|-
  
|| Code
+
|rowspan="1"| Proof of Deployment
|| client server
+
|| [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
 
|-
 
|-
  
|| [http://en.wikipedia.org/wiki/Deployment_diagram Deployment Diagram]
+
|}<br>
|| [[IS480_Midterm_Wiki#Deployment: | instructions]]
 
 
 
|}
 
 
</center>
 
</center>
  
[[File:Mv-B.png|800px|center|link=]]<br>
+
[[File:Mv-Z.png|800px|center|link=]]<br>
  
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: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=]]
  
 
[[File:Mv-D.png|800px|center|link=]]<br>
 
[[File:Mv-D.png|800px|center|link=]]<br>
  
* Internal Testing is performed for every new function developed
+
<div style="text-align: center; font-family:avenir; font-size:97%; ">
* Team Mavericks has scheduled for 5 User Testings in total  
+
Internal Testing is performed for every new function developed.<br>
** We have accomplished 3 User Testings as of Iteration 11
+
Team Mavericks has scheduled for 4 User Testings in total.<br>
 +
We have accomplished all User Testings as of Iteration 14.<br>
  
 
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].
 
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>
  
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.
+
[[File:mv-reflections-banner.png|1000px|center|link=]]<br>
 
 
[[File:mv-reflections-banner.png|1000px|center|link=]]
 
 
 
===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 | 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.
 
  
 +
<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>
 
'''Jamie's Reflection'''<br>
I have learnt the importance of my role in team and stakeholder management, as well as maintaining overall responsibility of the project. As much as communication is essential within a team, it is also important for me to recognise every member's strengths and weaknesses, so that everyone can achieve their fullest potential to accomplish a common goal.  
+
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>
 
 
  
 
'''Yi Xiang's Reflection'''<br>
 
'''Yi Xiang's Reflection'''<br>
  
We should be open to change in order for us to improve. Even if we have a good idea, which we believe to be the best, we should be open to feedback and make necessary changes. The ones who decide whether if the idea is good or not are the target users. Thus, it is important to have proof of deploment and user testing to get users' feedback for improvements.
+
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>
 
 
  
 
'''Gerald's Reflection'''<br>
 
'''Gerald's Reflection'''<br>
As the Tech Architect, there is always something new to learn, best practices that we ought to adopt. It’s important that I’m up to speed with the right implementation to ensure that the application performs according to expectation. I’ve learnt that other than implementing a feature, we ought to implement it well so that it is usable for the users.
+
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'''<br>
 
'''Bertran's Reflection'''<br>
What I have learnt is that in a software project, non-functional requirements are extremely important. In fact, it might even be more difficult to fulfil a non-functional requirement, and these are often overlooked or underestimated in project plans.
+
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'''<br>
 
'''Yi An's Reflection'''<br>
As the Quality Assurance Lead, I learnt that having attention to details is crucial in making a excellent product. Additionally, adapting to changes is the key to creating a holistic product.
+
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>
===Sponsor Comment:===
+
<br>
Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.
+
<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!