Difference between revisions of "IS480 Team wiki: 2016T1 PolyVision Final"
(Created page with "<!--Logo--> 500px|center|INSIGHT<br /> <!--Navigation Bar--> {|style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadd...") |
|||
(30 intermediate revisions by 2 users not shown) | |||
Line 14: | Line 14: | ||
{| style="background-color:white; color:white padding: 5px 0 0 0;" width="100%" height=50px cellspacing="0" cellpadding="0" valign="top" border="0" | | {| style="background-color:white; color:white padding: 5px 0 0 0;" width="100%" height=50px cellspacing="0" cellpadding="0" valign="top" border="0" | | ||
| style="vertical-align:top;width:15%;" | <div style="padding: 3px; font-weight: bold; text-align:center; line-height: wrap_content; border-bottom:1px solid #c60026"> [[IS480_Team_wiki:_2016T1 PolyVision | <font color="#c60026"><b>Main</b></font>]] | | style="vertical-align:top;width:15%;" | <div style="padding: 3px; font-weight: bold; text-align:center; line-height: wrap_content; border-bottom:1px solid #c60026"> [[IS480_Team_wiki:_2016T1 PolyVision | <font color="#c60026"><b>Main</b></font>]] | ||
− | | style="vertical-align:top;width:15%;" | <div style="padding: 3px; font-weight: bold; text-align:center; line-height: wrap_content; border-bottom:1px solid #c60026"> [[IS480_Team_wiki:_2016T1 PolyVision | + | | style="vertical-align:top;width:15%;" | <div style="padding: 3px; font-weight: bold; text-align:center; line-height: wrap_content; border-bottom:1px solid #c60026"> [[IS480_Team_wiki:_2016T1 PolyVision Midterm | <font color="#c60026"><b>Midterm</b></font>]] |
| style="vertical-align:top;width:15%;" | <div style="padding: 3px; font-weight: bold; text-align:center; line-height: wrap_content; border-bottom:1px solid #c60026"> <b>Final</b> | | style="vertical-align:top;width:15%;" | <div style="padding: 3px; font-weight: bold; text-align:center; line-height: wrap_content; border-bottom:1px solid #c60026"> <b>Final</b> | ||
|}<br/> | |}<br/> | ||
Line 21: | Line 21: | ||
==Project Progress Summary== | ==Project Progress Summary== | ||
Deployed URL: <u>https://vgpinsight.com</u> <br /> | Deployed URL: <u>https://vgpinsight.com</u> <br /> | ||
− | + | Finals Deck: [[Media:FYP Final (print).pdf|View]] | |
===Project Highlights=== | ===Project Highlights=== | ||
<ol> | <ol> | ||
− | <li></li> | + | <li>INSIGHT has been handed over to clients on <b><u>16 November 2016</u></b></li> |
− | <li></ | + | <li>Completed all features on <b><u>13 November 2016</u></b></li> |
− | < | + | <li>Concluded UAT3 with 25 users on <b><u>9 November 2016</u></b></li> |
− | <li></ | ||
− | < | ||
</ol> | </ol> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
==Project Management== | ==Project Management== | ||
Line 130: | Line 123: | ||
| Accepted change request | | Accepted change request | ||
| 100% | | 100% | ||
− | | | + | | Completed |
|- | |- | ||
Line 137: | Line 130: | ||
| Future Development | | Future Development | ||
| 100% | | 100% | ||
− | | | + | | Completed |
|- | |- | ||
Line 144: | Line 137: | ||
| Future Development | | Future Development | ||
| 100% | | 100% | ||
− | | | + | | Completed |
|- | |- | ||
| 15 | | 15 | ||
| Workflow History | | Workflow History | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
| Removed upon negotiation | | Removed upon negotiation | ||
| N.A. | | N.A. | ||
Line 173: | Line 159: | ||
|- | |- | ||
+ | | [[File:FYP Scope v1.png|525px|center|INSIGHT Original Scope]] | ||
| [[File:INSIGHT Midterm.png|525px|center|INSIGHT Latest Scope]] | | [[File:INSIGHT Midterm.png|525px|center|INSIGHT Latest Scope]] | ||
− | |||
|- | |- | ||
+ | | [[File:INSIGHT Timeline.png|525px|center|INSIGHT Original Timeline]] | ||
| [[File:FYP Timeline v7.png|525px|center|INSIGHT Latest Timeline]] | | [[File:FYP Timeline v7.png|525px|center|INSIGHT Latest Timeline]] | ||
− | |||
|- | |- | ||
|} | |} | ||
− | </center> | + | </center> |
+ | |||
===Project Metrics=== | ===Project Metrics=== | ||
====Task Metrics==== | ====Task Metrics==== | ||
[[IS480 Team wiki: 2016T1 PolyVision Metrics | Click here to view more about how we collect our tasks metrics.]]<br> | [[IS480 Team wiki: 2016T1 PolyVision Metrics | Click here to view more about how we collect our tasks metrics.]]<br> | ||
− | <br /> | + | <center>[[File:INSIGHT task metrics final.png|800px]]</center><br /> |
====Bug Metrics==== | ====Bug Metrics==== | ||
[[IS480 Team wiki: 2016T1 PolyVision Metrics | Click here to view more about how we collect our bug metrics.]]<br><br> | [[IS480 Team wiki: 2016T1 PolyVision Metrics | Click here to view more about how we collect our bug metrics.]]<br><br> | ||
− | < | + | <center>[[File:INSIGHT bug metrics final.png|800px]]</center><br /> |
− | |||
− | |||
− | [[ | ||
− | |||
− | <center> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | </ | ||
===Technical Complexity=== | ===Technical Complexity=== | ||
Line 228: | Line 188: | ||
|1 | |1 | ||
− | | | + | | Quartz.Net |
− | | | + | | Complications caused because of no "direct' way to chain triggers with Quartz.NET. Has high impact on the project because 3 of our modules requires the usage this library. |
|- | |- | ||
|2 | |2 | ||
− | | | + | | SVG manipulation & transformation |
− | | | + | | Had no prior experience in working with D3 or SVGs and each chart uses different data structure and there is limited backend guide. Had to learn and customize charts within a limited time frame. |
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
Line 256: | Line 211: | ||
|- | |- | ||
− | |rowspan=" | + | |rowspan="6"| Project Management |
| Schedule Management | | Schedule Management | ||
| A customized spreadsheet is maintained by the PM that is revised at the beginning of each Iteration ensuring that tasks are being completed. | | A customized spreadsheet is maintained by the PM that is revised at the beginning of each Iteration ensuring that tasks are being completed. | ||
Line 262: | Line 217: | ||
| Risk Management | | Risk Management | ||
− | | [[IS480 Team wiki: 2016T1 PolyVision Risk Management | Risk Management]] | + | | [[IS480 Team wiki: 2016T1 PolyVision Risk Management|Risk Management]] |
|- | |- | ||
| Change Management | | Change Management | ||
| Change requests are raised after every meeting with the sponsor at the end of each Iteration. These requests are maintained within a spreadsheet then evaluated as a team on the priority, complexity before being included in the schedule by the PM.<br> | | Change requests are raised after every meeting with the sponsor at the end of each Iteration. These requests are maintained within a spreadsheet then evaluated as a team on the priority, complexity before being included in the schedule by the PM.<br> | ||
− | [[IS480 Team wiki: 2016T1 PolyVision Change Management | Change Management]] | + | [[IS480 Team wiki: 2016T1 PolyVision Change Management|Change Management]] |
|- | |- | ||
| Meeting Minutes | | Meeting Minutes | ||
| All meetings with the sponsor, supervisor, and team are being documented.<br> | | All meetings with the sponsor, supervisor, and team are being documented.<br> | ||
− | [[IS480 Team wiki: 2016T1 PolyVision | + | [[IS480 Team wiki: 2016T1 PolyVision Minutes|Meeting Minutes]] |
|- | |- | ||
| Metrics | | Metrics | ||
− | | [[IS480 Team wiki: 2016T1 PolyVision Metrics | Metrics]] | + | | [[IS480 Team wiki: 2016T1 PolyVision Metrics | Task Metrics<br>Bug Metrics]] |
+ | |- | ||
+ | |||
+ | | Handover | ||
+ | | [[Media:INSIGHT Walkthrough.pdf|Walkthrough Guide]] | ||
|- | |- | ||
− | |rowspan=" | + | |rowspan="3"| Design Diagrams |
| Use Case, Class Diagram, Sequence Diagram, As-Is Process Diagram, To-Be Process Diagram | | Use Case, Class Diagram, Sequence Diagram, As-Is Process Diagram, To-Be Process Diagram | ||
| [[IS480 Team wiki: 2016T1 PolyVision Project Documentation | Use Case<br>Class Diagram<br>Sequence Diagram<br>As-Is Process Diagram<br>To-Be Process Diagram]] | | [[IS480 Team wiki: 2016T1 PolyVision Project Documentation | Use Case<br>Class Diagram<br>Sequence Diagram<br>As-Is Process Diagram<br>To-Be Process Diagram]] | ||
Line 286: | Line 245: | ||
| Prototype | | Prototype | ||
| [[IS480 Team wiki: 2016T1 PolyVision Prototypes | Paper Prototype<br>Hi-fidelity Prototype]] | | [[IS480 Team wiki: 2016T1 PolyVision Prototypes | Paper Prototype<br>Hi-fidelity Prototype]] | ||
+ | |- | ||
+ | |||
+ | | Storyboard | ||
+ | | [[IS480 Team wiki: 2016T1 PolyVision Motivation | Storyboard]] | ||
|- | |- | ||
| Testing | | Testing | ||
| User Test Plan | | User Test Plan | ||
− | | [[IS480 Team wiki: 2016T1 PolyVision UT1 | User Testing 1]]<br> | + | | |
+ | [[IS480 Team wiki: 2016T1 PolyVision UT1 | User Testing 1]]<br> | ||
[[IS480 Team wiki: 2016T1 PolyVision UT2 | User Testing 2]]<br> | [[IS480 Team wiki: 2016T1 PolyVision UT2 | User Testing 2]]<br> | ||
− | User Testing 3 | + | [[IS480 Team wiki: 2016T1 PolyVision UT3 | User Testing 3]] |
|- | |- | ||
|} | |} | ||
Line 302: | Line 266: | ||
===Testing=== | ===Testing=== | ||
− | |||
− | |||
<b>User Testing 3:</b><br> | <b>User Testing 3:</b><br> | ||
[[IS480 Team wiki: 2016T1 PolyVision UT3 | <u>Click here for more details on our UT3</u>]]<br> | [[IS480 Team wiki: 2016T1 PolyVision UT3 | <u>Click here for more details on our UT3</u>]]<br> | ||
<li> | <li> | ||
− | <b>Date: </b> | + | <b>Date: </b>28 Oct - 4 Nov<br> |
− | <br> | ||
</li> | </li> | ||
+ | |||
<li> | <li> | ||
− | + | <b>Users: </b>25 users (15 primary users & 10 secondary users)<br> | |
− | <b>Users: </b> | ||
− | <br> | ||
</li> | </li> | ||
<li> | <li> | ||
− | <b>Scope: </b> | + | <b>Scope: </b>Company management module, deal management module, venture capitalist module, custom notification module, file upload, covenant review<br> |
− | <br> | ||
</li> | </li> | ||
==Reflections== | ==Reflections== | ||
− | === | + | ===Team Reflection=== |
− | <i></i> | + | <i>Collectively, Team PolyVision have a better understanding of their individual capabilities and limitations. The team has managed to pick up ASP .NET Razor markup language as a result of having every member responsible and accountable for a portion of INSIGHT application to foster greater ownership. And when the occasion arise that business needs are not fully aligned with the initial set of requirements, effective communication is paramount to align every stakeholder involved. </i> |
− | ===Fusen Li=== | + | <br> |
− | <i></i> | + | |
− | ===Joleen Lee=== | + | ===Individual Reflection=== |
− | <i></i> | + | ====Fusen Li==== |
− | ===Jonathan Lee=== | + | <i>As the Backend Developer of PolyVision, I learn how to code and deploy c# web application onto Microsoft Azure platform; And learn to ensure product is delivered with good quality through rigorous testing and improvement.</i> |
− | <i></i> | + | ====Joleen Lee==== |
− | ===Kong Song Wei=== | + | <i>As the Frontend Developer of PolyVision, I learnt to optimize our application for different devices with best coding practices. At the same time, understanding how users interact with our application and adapting it based on their feedback.</i> |
− | <i></i> | + | ====Jonathan Lee==== |
− | ===Ong Wee Tiong=== | + | <i>As the Project Manager of PolyVision, I learn that it is important to grasp the optimum working preference and environment for the team to be productive. Most importantly, it is to enforce the above to ensure that the team can work more efficiently together. </i> |
− | <i></i> | + | ====Kong Song Wei==== |
+ | <i>As the Database Architect of PolyVision, I learn the importance of good application and database design, with frequent feedbacks to limit the impact of change requests.</i> | ||
+ | ====Ong Wee Tiong==== | ||
+ | <i>As the Backend Developer of PolyVision, IS480 allowed me to gain exposure and understanding on the use of different technology in the market such as SignalR and Quartz.Net library. Besides overcoming technical challenges to implement real-time push technology and complex threadings spanning across different business requirements. It is also an eye-opening experience for me to be understand how different users usage of information drives the same data to be display differently.</i> | ||
+ | <br> |
Latest revision as of 09:09, 25 November 2016
Home | About Us | Project Overview | Project Management | Project Documentation |
Final
|
Project Progress Summary
Deployed URL: https://vgpinsight.com
Finals Deck: View
Project Highlights
- INSIGHT has been handed over to clients on 16 November 2016
- Completed all features on 13 November 2016
- Concluded UAT3 with 25 users on 9 November 2016
Project Management
Project Status
S/N | Module | Description | Confidence (%) | Status |
---|---|---|---|---|
1 | Administrator | Fully deployed and tested on production server | 100% | Completed |
2 | User Account | Fully deployed and tested on production server | 100% | Completed |
3 | Company Management | Fully deployed and tested on production server | 100% | Completed |
4 | Deal Management | Fully deployed and tested on production server | 100% | Completed |
5 | Dashboard | Fully deployed and tested on production server | 100% | Completed |
6 | VC Management | Fully deployed and tested on production server | 100% | Completed |
7 | Event-Triggered Notification | Fully deployed and tested on production server | 100% | Completed |
8 | Custom Notification | Fully deployed and tested on production server | 100% | Completed |
9 | Reporting | Fully deployed and tested on production server | 100% | Completed |
10 | Newsfeed | Fully deployed and tested on production server | 100% | Completed |
11 | Backup | Fully deployed and tested on production server | 100% | Completed |
12 | Search | Accepted change request | 100% | Completed |
13 | Name Card Recognition | Future Development | 100% | Completed |
14 | Usability | Future Development | 100% | Completed |
15 | Workflow History | Removed upon negotiation | N.A. | Removed upon negotiation |
Project Schedule
Plan | Actual |
---|---|
Project Metrics
Task Metrics
Click here to view more about how we collect our tasks metrics.
Bug Metrics
Click here to view more about how we collect our bug metrics.
Technical Complexity
Rank | Complexity | Reason |
---|---|---|
1 | Quartz.Net | Complications caused because of no "direct' way to chain triggers with Quartz.NET. Has high impact on the project because 3 of our modules requires the usage this library. |
2 | SVG manipulation & transformation | Had no prior experience in working with D3 or SVGs and each chart uses different data structure and there is limited backend guide. Had to learn and customize charts within a limited time frame. |
Quality of Product
Intermediate Deliverables
Stage | Specifications | Work Products |
---|---|---|
Project Management | Schedule Management | A customized spreadsheet is maintained by the PM that is revised at the beginning of each Iteration ensuring that tasks are being completed. |
Risk Management | Risk Management | |
Change Management | Change requests are raised after every meeting with the sponsor at the end of each Iteration. These requests are maintained within a spreadsheet then evaluated as a team on the priority, complexity before being included in the schedule by the PM. | |
Meeting Minutes | All meetings with the sponsor, supervisor, and team are being documented. | |
Metrics | Task Metrics Bug Metrics | |
Handover | Walkthrough Guide | |
Design Diagrams | Use Case, Class Diagram, Sequence Diagram, As-Is Process Diagram, To-Be Process Diagram | Use Case Class Diagram Sequence Diagram As-Is Process Diagram To-Be Process Diagram |
Prototype | Paper Prototype Hi-fidelity Prototype | |
Storyboard | Storyboard | |
Testing | User Test Plan |
Deployment
INSIGHT application can be found at this URL: https://vgpinsight.com
Note: Please ensure that you are using the latest version of Google Chrome browser with Javascript enabled to enjoy the full INSIGHT experience.
Testing
User Testing 3:
Click here for more details on our UT3
Reflections
Team Reflection
Collectively, Team PolyVision have a better understanding of their individual capabilities and limitations. The team has managed to pick up ASP .NET Razor markup language as a result of having every member responsible and accountable for a portion of INSIGHT application to foster greater ownership. And when the occasion arise that business needs are not fully aligned with the initial set of requirements, effective communication is paramount to align every stakeholder involved.
Individual Reflection
Fusen Li
As the Backend Developer of PolyVision, I learn how to code and deploy c# web application onto Microsoft Azure platform; And learn to ensure product is delivered with good quality through rigorous testing and improvement.
Joleen Lee
As the Frontend Developer of PolyVision, I learnt to optimize our application for different devices with best coding practices. At the same time, understanding how users interact with our application and adapting it based on their feedback.
Jonathan Lee
As the Project Manager of PolyVision, I learn that it is important to grasp the optimum working preference and environment for the team to be productive. Most importantly, it is to enforce the above to ensure that the team can work more efficiently together.
Kong Song Wei
As the Database Architect of PolyVision, I learn the importance of good application and database design, with frequent feedbacks to limit the impact of change requests.
Ong Wee Tiong
As the Backend Developer of PolyVision, IS480 allowed me to gain exposure and understanding on the use of different technology in the market such as SignalR and Quartz.Net library. Besides overcoming technical challenges to implement real-time push technology and complex threadings spanning across different business requirements. It is also an eye-opening experience for me to be understand how different users usage of information drives the same data to be display differently.