HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
Line 291: Line 291:
  
 
[[File:Mv-7.png|800px|center|link=]]<br>
 
[[File:Mv-7.png|800px|center|link=]]<br>
 
<div style="text-align: center; font-size:85%; ">
 
To be inserted<br>
 
</div>
 
 
<br>
 
<br>
 
[[File:Mv-quality-banner.png|1000px|center|link=]]<br>
 
[[File:Mv-quality-banner.png|1000px|center|link=]]<br>
Line 364: Line 360:
 
||  
 
||  
 
|-
 
|-
 
|rowspan="3"| Handover
 
|| Manuals
 
|| User tutorial, Developer manual, Setup manual
 
|-
 
 
|| Code
 
|| client server
 
|-
 
 
|| [http://en.wikipedia.org/wiki/Deployment_diagram Deployment Diagram]
 
|| [[IS480_Midterm_Wiki#Deployment: | instructions]]
 
  
 
|}<br>
 
|}<br>
 
</center>
 
</center>
  
[[File:Mv-B.png|800px|center|link=]]<br>
+
[[File:Mv-Z.png|800px|center|link=]]<br>
  
<div style="text-align: center; font-size:85%; ">
+
[[File:FYP Midterms Presentation.062.jpeg|700px|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.019.jpeg|800px|center|link=]]<br>
</div><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>

Revision as of 23:28, 3 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
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.PNGMv-bugs.png
For more information on metrics collected, please refer here.


Mv-7.png



Mv-quality-banner.png


Mv-a.png
Stage Specification Modules
Project Management Minutes
Schedule
Metrics Bug Metrics, Task Metrics
Risk Mitigation
Requirements Overview
Scope
Scenarios
Analysis System Architecture Diagram
Technologies Used
Design 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

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:

Key lessons learned – indicating where the team improved, or would do things differently next time. You may refer to the learning outcome summary in your proposal. A very short checklist style will suffice. It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.

Individual Reflection:

Describe in a paragraph, the key areas of learning or improvement. These should be personal areas of growth or learning. Each individual should list his/her effort, responsibility, actual contributions and personal reflection. Do not repeat team project contributions or member roles. Link if necessary.

Jamie's Reflection
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.


Yi Xiang's Reflection

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.


Gerald's Reflection
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.


Bertran's Reflection
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.


Yi An's Reflection
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.

Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.