HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T1 PolyVision Final"

From IS480
Jump to navigation Jump to search
 
(20 intermediate revisions by 2 users not shown)
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 Midterm.pdf|View]]
+
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>
+
<li>Completed all features on <b><u>13 November 2016</u></b></li>
<li></li>
+
<li>Concluded UAT3 with 25 users on <b><u>9 November 2016</u></b></li>
</ol>
 
 
 
===Project Challenges===
 
<ol>
 
<li></li>
 
<li></li>
 
<li></li>
 
</ol>
 
 
 
===Project Achievements===
 
<ol>
 
<li></li>
 
<li></li>
 
<li></li>
 
 
</ol>
 
</ol>
  
Line 186: Line 172:
 
====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>
<br />
+
<center>[[File:INSIGHT bug metrics final.png|800px]]</center><br />
 
 
===Project Risks===
 
[[IS480 Team wiki: 2016T1 PolyVision Risk Management| Click here to view more about our risk management]]
 
 
 
<center>
 
{| class="wikitable" style="text-align: center; width:1050px"
 
|+
 
|-
 
! scope="col" style="background:#c60026; color:#ffffff"| Risk Event
 
! scope="col" style="background:#c60026; color:#ffffff"| Probability
 
! scope="col" style="background:#c60026; color:#ffffff"| Impact
 
! scope="col" style="background:#c60026; color:#ffffff"| Mitigation Plan
 
|-
 
 
 
| Incomplete deployment onto production server
 
| Medium
 
| High
 
| Immediate debugging session
 
|-
 
 
 
| Further changes to requirements
 
| Medium
 
| High
 
| Regular meetings and feedback from client to ensure timely delivery
 
|-
 
|}
 
</center>
 
  
 
===Technical Complexity===
 
===Technical Complexity===
Line 229: 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.
|-
 
 
 
|3
 
|
 
|
 
 
|-
 
|-
  
Line 257: Line 211:
 
|-
 
|-
  
|rowspan="5"| Project Management
+
|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 263: 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 Minutes| Meeting Minutes]]
+
[[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="2"| Design Diagrams
+
|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 287: 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>
 
[[IS480 Team wiki: 2016T1 PolyVision UT3 | User Testing 3]]
 
[[IS480 Team wiki: 2016T1 PolyVision UT3 | User Testing 3]]
Line 303: Line 266:
  
 
===Testing===
 
===Testing===
We have conducted one user testing.<br>
 
 
 
<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===
 
===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>
 
<br>
 
<br>
  
 
===Individual Reflection===
 
===Individual Reflection===
 
====Fusen Li====
 
====Fusen Li====
<i></i>
+
<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>
 
====Joleen Lee====
 
====Joleen Lee====
<i></i>
+
<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>
 
====Jonathan Lee====
 
====Jonathan Lee====
<i></i>
+
<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>
 
====Kong Song Wei====
 
====Kong Song Wei====
<i></i>
+
<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====
 
====Ong Wee Tiong====
<i></i>
+
<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>
 
 
 
===Sponsor Comment===
 
<i></i>
 
 
<br>
 
<br>

Latest revision as of 09:09, 25 November 2016

INSIGHT


Home About Us Project Overview Project Management Project Documentation


Final


Project Progress Summary

Deployed URL: https://vgpinsight.com
Finals Deck: View

Project Highlights

  1. INSIGHT has been handed over to clients on 16 November 2016
  2. Completed all features on 13 November 2016
  3. 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
INSIGHT Original Scope
INSIGHT Latest Scope
INSIGHT Original Timeline
INSIGHT Latest Timeline

Project Metrics

Task Metrics

Click here to view more about how we collect our tasks metrics.

INSIGHT task metrics final.png


Bug Metrics

Click here to view more about how we collect our bug metrics.

INSIGHT bug metrics final.png


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.

Change Management

Meeting Minutes All meetings with the sponsor, supervisor, and team are being documented.

Meeting Minutes

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

User Testing 1
User Testing 2
User Testing 3

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

  • Date: 28 Oct - 4 Nov
  • Users: 25 users (15 primary users & 10 secondary users)
  • Scope: Company management module, deal management module, venture capitalist module, custom notification module, file upload, covenant review
  • 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.