HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2015T2 Insightiers Midterm Wiki"

From IS480
Jump to navigation Jump to search
 
(37 intermediate revisions by the same user not shown)
Line 34: Line 34:
 
| style="padding:0.4em;  font-size:90%; border-bottom:4px solid #000000;  text-align:center; background-color:#ffffff; " width="10%" |[[IS480_Team_wiki:_2015T2_Insightiers |<font color="#3d3d3d"><b>Home</b></font>]]  
 
| style="padding:0.4em;  font-size:90%; border-bottom:4px solid #000000;  text-align:center; background-color:#ffffff; " width="10%" |[[IS480_Team_wiki:_2015T2_Insightiers |<font color="#3d3d3d"><b>Home</b></font>]]  
  
| style="border-bottom:4px solid #2f2929; background:none;" width="1%" | &nbsp;  
+
| style="border-bottom:4px solid #000000; background:none;" width="1%" | &nbsp;  
 
| style="padding:0.4em; font-size:90%; background-color:#40CDFF;  border-bottom:4px solid #000000; text-align:center; color:#2f2929" width="10%" |[[IS480_Team_wiki:_2015T2_Insightiers_Midterm_Wiki |<font color="#3d3d3d" size=2><b>Midterm Wiki</b></font>]]
 
| style="padding:0.4em; font-size:90%; background-color:#40CDFF;  border-bottom:4px solid #000000; text-align:center; color:#2f2929" width="10%" |[[IS480_Team_wiki:_2015T2_Insightiers_Midterm_Wiki |<font color="#3d3d3d" size=2><b>Midterm Wiki</b></font>]]
  
| style="border-bottom:4px solid #2f2929; background:none;" width="1%" | &nbsp;  
+
| style="border-bottom:4px solid #000000; background:none;" width="1%" | &nbsp;  
 
| style="padding:0.4em; font-size:90%; background-color:#ffffff;  border-bottom:4px solid #000000; text-align:center; color:#2f2929" width="10%" |[[IS480_Team_wiki:_2015T2_Insightiers_Final_Wiki |<font color="#3d3d3d" size=2><b>Final Wiki</b></font>]]
 
| style="padding:0.4em; font-size:90%; background-color:#ffffff;  border-bottom:4px solid #000000; text-align:center; color:#2f2929" width="10%" |[[IS480_Team_wiki:_2015T2_Insightiers_Final_Wiki |<font color="#3d3d3d" size=2><b>Final Wiki</b></font>]]
 
|} <br>
 
|} <br>
Line 45: Line 45:
 
<div align=left>
 
<div align=left>
  
==Project Progress Summary==
+
==Slides and Links==
 +
[[Media: Insightiers_Midterm_Presentation.pptx | View our midterm presentation slides here]]
 +
<!--[INSERT OUR STAGING SERVER LINK View our SYMPLProj web application here]<br>-->
  
You may view our midterm presentation slides here:
+
<br>
<!--GIVE MIDTERM PRESENTATION LINK HERE-->
+
As you are viewing our midterm wiki, you may realize that we've included several links in their relevant sections. <br>
link!!!
+
For your convenience sake, we've consolidated the list of links used in this midterm wiki in the following: <br>
 +
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Insightiers_Project_Scope Project Scope]<br>
 +
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Insightiers_Project_Management Current and Past Schedule Timeline]<br>
 +
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Insightiers_UAT1 UAT1 Results]<br>
 +
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Insightiers_UAT2 UAT2 Results]<br>
 +
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Insightiers_Metrics Schedule and Bug Metrics]<br>
 +
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Insightiers_Risk_Management Risk Management]<br>
  
<!--For proposal, please see Requrements at the Project Deliverables. This will help us understand your scope. Note wiki policy [[Help:Contents|here]].
+
==Project Progress Summary==
 
 
This page should NOT be too long. It should link to other pages in the IS480 team wiki. Do not repeat the proposal or other wiki information here. However, keep a snapshot of the midterm state. Highlight changes since project acceptance.
 
 
 
Describe the project progress briefly here. Have the project continued as planned? If not, is the team confident to complete? This is a crossroad for the team to make a decision. Proceed with confident or file an incomplete.-->
 
  
 
===Project Highlights===
 
===Project Highlights===
  
 
Unexpected events that have occurred:
 
Unexpected events that have occurred:
 +
*Two members' laptops broke down, which resulted in loss of time for system development
 
*Could not access SVN in China
 
*Could not access SVN in China
 
*List of major changes to be made from December holidays and UATs:  
 
*List of major changes to be made from December holidays and UATs:  
Line 67: Line 72:
 
** Added email task rejection
 
** Added email task rejection
 
** Added sign/pay functions for documents
 
** Added sign/pay functions for documents
 +
** Added seal invoice function
 
** Deploying on DigitalOcean instead of AWS
 
** Deploying on DigitalOcean instead of AWS
 
** Implemented security features for secured data transmission
 
** Implemented security features for secured data transmission
Line 72: Line 78:
 
*Integration with Trello was a lot tougher than expected
 
*Integration with Trello was a lot tougher than expected
 
*Actual learning curve for email function was a lot higher
 
*Actual learning curve for email function was a lot higher
 +
*Delay in product list submission by client
 +
*UAT3 pushed to after midterm
  
 +
<br>
 
===In a Nutshell===
 
===In a Nutshell===
 +
[[Image:Insightiers_Midterm_Progress_Nutshell.png | 700px]]
 +
<br>
 +
<br>
 +
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Insightiers_Project_Scope View our project scope here]<br>
 +
<br>
 +
==Project Management==
 +
<!--------------------------------PROJECT STATUS: TASK COMPLETION AND CONFIDENCE LEVEL------>
 +
===Project Status===
 +
 +
{| border="1" cellpadding="5" cellspacing="0" width="80%"
 +
|- style="background:#C40000; color:white"
 +
|align="center" width="20px"|Module
 +
|align="center" width="50px"|Task/Features
 +
|align="center" width="50px"|Status
 +
|align="center" width="10px"|Confidence Level (0-1)
 +
|align="center" width="100px"|Remark
 +
|-
 +
 +
| rowspan="7" align="center"| User Account Management
 +
|| Login
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Yixi & Li Dan
 +
|-
 +
 +
|| Logout
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Yixi & Li Dan
 +
|-
 +
 +
|| Forget/Reset Password
 +
|| 100% implemented and user testing done
 +
|align="center"| 0.5
 +
|| Email function new to team. Yixi & Annan in charge.
 +
|-
 +
 +
|| Create Account
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Yixi & Li Dan
 +
|-
 +
 +
|| Edit Account
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Yixi & Li Dan
 +
|-
  
<!--
+
|| Delete Account
==Project Management==
+
|| 100% implemented
 +
|align="center"| 1
 +
|| Yixi & Li Dan
 +
|-
 +
 
 +
|| Filter Account
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan
 +
|-
 +
 
 +
| rowspan="3" align="center"| Staff Management
 +
|| Create Staff
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Yixi & Li Dan
 +
|-
 +
 
 +
|| Edit Staff
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Yixi & Li Dan
 +
|-
 +
 
 +
|| Delete/Deactivate Staff
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
| rowspan="5" align="center"| Staff Portfolio
 +
|| Display Staff Portfolio
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan
 +
|-
 +
 
 +
|| Filter Portfolio Summary Page
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan & Annan
 +
|-
 +
 
 +
|| View Projects
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan
 +
|-
 +
 
 +
|| Filter Projects of Staff
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Annan
 +
|-
 +
 
 +
|| View Tasks in Calendar
 +
|| 100% implemented
 +
|align="center"| 0.75
 +
|| Li Dan
 +
|-
 +
 
 +
| rowspan="14" align="center"| Project
 +
|| Create Project
 +
|| 100% implemented and user testing done
 +
|align="center"| 0.25
 +
|| Replicating project to Trello was technically challenging. Li Dan, Yixi & Annan in charge.
 +
|-
 +
 
 +
|| Edit Project
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan, Yixi & Annan in charge.
 +
|-
 +
 
 +
|| View Project Summary Page
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan
 +
|-
 +
 
 +
|| View Individual Project
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan & Annan
 +
|-
 +
 
 +
|| Start Project
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yixi
 +
|-
 +
 
 +
|| End Project
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Yixi & Annan
 +
|-
 +
 
 +
|| Close Project
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Yixi & Annan
 +
|-
 +
 
 +
|| Cancel Project
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Yixi & Annan
 +
|-
 +
 
 +
|| Delete Project
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Yixi & Annan
 +
|-
 +
 
 +
|| View Project Tasks
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan
 +
|-
 +
 
 +
|| Project News Feed
 +
|| To be implemented in iteration 13
 +
|align="center"| 1
 +
|| Li Dan and Yixi
 +
|-
 +
 
 +
|| Approve Tasks from Trello
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Newly added task, client approved. Yixi & Annan in charge.
 +
|-
 +
 
 +
|| Email Task Rejection
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Newly added task based on supervisor's suggestion, client approved. Yixi & Annan in charge.
 +
|-
 +
 
 +
|| Export Projects to CSV
 +
|| To be implemented in iteration 13
 +
|align="center"| 1
 +
|| Yixi & Annan
 +
|-
 +
 
 +
| rowspan="5" align="center"| Project Task
 +
|| Create Task
 +
|| 100% implemented and user testing done
 +
|align="center"| 0.25
 +
|| Replicating task to Trello was technically challenging. Li Dan & Annan in charge.
 +
|-
 +
 
 +
|| Edit Task
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan & Annan
 +
|-
 +
 
 +
|| End Task
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Annan
 +
|-
 +
 
 +
|| Delete Task
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Annan
 +
|-
 +
 
 +
|| View Task
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan & Annan
 +
|-
 +
 
 +
| rowspan="1" align="center"| Dashboard
 +
|| View Dashboard
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Annan
 +
|-
 +
 
 +
| rowspan="6" align="center"| Simulation
 +
|| Create Simulation
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan & Annan
 +
|-
 +
 
 +
|| View Simulation
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan & Annan
 +
|-
 +
 
 +
|| Clear Simulation
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Annan
 +
|-
 +
 
 +
|| View Simulated Details
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan
 +
|-
 +
 
 +
|| Create Project from Simulation
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan
 +
|-
 +
 
 +
|| View Projects in Each Month
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan
 +
|-
 +
 
 +
| rowspan="11" align="center"| Quotation
 +
|| Create Quotation
 +
|| 100% implemented and user testing done
 +
|align="center"|  0.5
 +
|| Challenged by technical difficulty in pulling data from master setup template. Li Dan & Yining in charge.
 +
|-
 +
 
 +
|| Create Quotation with Preset Modules
 +
|| 100% implemented
 +
|align="center"| 0.75
 +
|| Displaying data on quotation from preset modules challenging. Li Dan & Yining in charge.
 +
|-
 +
 
 +
|| Edit Quotation
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| View Quotation Summary Page
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| View Individual Quotation
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| Save Quotation
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| Delete Quotation
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| Generate Quotation to PDF
 +
|| 100% implemented and user testing done
 +
|align="center"| 0.25
 +
|| Unfamiliar with technology. Huge technical challenge team has faced. Li Dan & Yining in charge.
 +
|-
 +
 
 +
|| Send Quotation via Email
 +
|| 100% implemented
 +
|align="center"| 0.5
 +
|| Send attachment via email technology new to team. Li Dan & Yining in charge.
 +
|-
 +
 
 +
|| Sign Quotation
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| Export Quotations to CSV
 +
|| To be implemented in iteration 13
 +
|align="center"| 1
 +
|| Yixi & Annan
 +
|-
 +
 
 +
| rowspan="11" align="center"| Invoice
 +
|| Create Invoice
 +
|| 100% implemented
 +
|align="center"| 0.5
 +
|| Challenged by technical difficulty in pulling data from master setup template.
 +
|-
 +
 
 +
|| Edit Invoice
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| View Invoice Summary Page
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| View Individual Invoice
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| Save Invoice
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| Delete Invoice
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| Generate Invoice to PDF
 +
|| 100% implemented and user testing done
 +
|align="center"| 0.25
 +
|| Unfamiliar with technology. Huge technical challenge team has faced. Li Dan & Yining in charge.
 +
|-
 +
 
 +
|| Send Invoice via Email
 +
|| 100% implemented
 +
|align="center"| 0.5
 +
|| Send attachment via email technology new to team. Li Dan & Yining in charge.
 +
|-
 +
 
 +
|| Pay Invoice
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| Seal Invoice
 +
|| 100% implemented
 +
|align="center"| 0.5
 +
|| A technical hurdle as team has never tried inserting picture into a document. Li Dan & Yining in charge.
 +
|-
 +
 
 +
|| Export Invoice to CSV
 +
|| To be implemented in iteration 13
 +
|align="center"| 1
 +
|| Yixi & Annan
 +
|-
 +
 
 +
| rowspan="9" align="center"| Contract
 +
|| Create Contract
 +
|| 100% implemented and user testing done
 +
|align="center"| 0.5
 +
|| Challenged by technical difficulty in pulling data from master setup template. Li Dan & Yining in charge.
 +
|-
 +
 
 +
|| Edit Contract
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| View Contract Summary Page
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| View Individual Contract
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan
 +
|-
 +
 
 +
|| Save Contract
 +
|| 100% implemented and user testing done
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| Delete Contract
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| Generate Contract to PDF
 +
|| 100% implemented and user testing done
 +
|align="center"| 0.25
 +
|| Unfamiliar with technology. Huge technical challenge team has faced. Yining in charge.
 +
|-
 +
 
 +
|| Send Contract via Email
 +
|| 100% implemented
 +
|align="center"| 0.5
 +
|| Send attachment via email technology new to team. Li Dan & Yining in charge.
 +
|-
 +
 
 +
|| Sign Contract
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
| rowspan="9" align="center"| Sign-Off
 +
|| Create Sign-Off
 +
|| 100% implemented
 +
|align="center"| 0.5
 +
|| Relatively easier to implement due to its similarity with contract template. Li Dan & Yining in charge.
 +
|-
 +
 
 +
|| Edit Sign-Off
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| View Sign-Off Summary Page
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| View Individual Sign-Off
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan
 +
|-
 +
 
 +
|| Save Sign-Off
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| Delete Sign-Off
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| Generate Sign-Off to PDF
 +
|| 100% implemented
 +
|align="center"| 0.25
 +
|| Unfamiliar with technology. Huge technical challenge team has faced. Yining in charge.
 +
|-
 +
 
 +
|| Send Sign-Off via Email
 +
|| 100% implemented
 +
|align="center"| 0.5
 +
|| Send attachment via email technology new to team. Li Dan & Yining in charge.
 +
|-
 +
 
 +
|| Sign Sign-Off
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
| rowspan="6" align="center"| Bug Logbook
 +
|| Create Bug Logbook
 +
|| 100% implemented
 +
|align="center"| 0.5
 +
|| A different layout from other document templates. New UI hurdle to overcome. Li Dan in charge.
 +
|-
 +
 
 +
|| Edit Bug Logbook
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| View Bug Logbook Summary Page
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| View Individual Bug Logbook
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan
 +
|-
 +
 
 +
|| Save Bug Logbook
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| Delete Bug Logbook
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
| rowspan="9" align="center"| NDA
 +
|| Create NDA
 +
|| 100% implemented
 +
|align="center"| 0.75
 +
|| A relatively easier module to do with reference from contract module. Li Dan & Yining in charge.
 +
|-
 +
 
 +
|| Edit NDA
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| View NDA Summary Page
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| View Individual NDA
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan
 +
|-
 +
 
 +
|| Save NDA
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| Delete NDA
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
|| Generate NDA to PDF
 +
|| 100% implemented
 +
|align="center"| 0.25
 +
|| Unfamiliar with technology. Huge technical challenge team has faced. Yining in charge.
 +
|-
 +
 
 +
|| Send NDA via Email
 +
|| 100% implemented
 +
|align="center"| 0.5
 +
|| Send attachment via email technology new to team. Li Dan & Yining in charge.
 +
|-
 +
 
 +
|| Sign NDA
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan & Yining
 +
|-
 +
 
 +
| rowspan="5" align="center"| Product
 +
|| Create Product
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan and Yining
 +
|-
 +
 
 +
|| Edit Product
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan and Yining
 +
|-
 +
 
 +
|| View Product Summary Page
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan and Yining
 +
|-
 +
 
 +
|| View Individual Product Details
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan and Yining
 +
|-
 +
 
 +
|| Delete Product
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Li Dan and Yining
 +
|-
 +
 
 +
| rowspan="5" align="center"| Hardware
 +
|| Create Hardware
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Yixi and Annan
 +
|-
 +
 
 +
|| Edit Hardware
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Yixi and Annan
 +
|-
 +
 
 +
|| View Hardware Summary Page
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Yixi and Annan
 +
|-
 +
 
 +
|| Assign Hardware to Staff
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Yixi and Li Dan
 +
|-
 +
 
 +
|| Delete Hardware
 +
|| 100% implemented
 +
|align="center"| 1
 +
|| Yixi and Li Dan
 +
|-
 +
 
 +
| rowspan="7" align="center"| Master Setup
 +
|| Edit Quotation
 +
|| 100% implemented
 +
|align="center"| 0.25
 +
|| A huge technical obstacle for team due to unfamiliar technology. Li Dan and Yining in charge.
 +
|-
  
Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.
+
|| Edit Quotation Preset Modules
 +
|| 100% implemented
 +
|align="center"| 0.5
 +
|| Tough to implement due to technical difficulty. Li Dan and Yining in charge.
 +
|-
  
===Project Status===
+
|| Edit Invoice
 +
|| 100% implemented
 +
|align="center"| 0.25
 +
|| A huge technical obstacle for team due to unfamiliar technology. Requires different layout from quotation. Li Dan and Yining in charge.
 +
|-
  
Highlight changes to modules, the completion status (implemented, user testing done, client approved, deployed, etc), the confidence level (0-1 where 0 is no confident of getting it done, 1 is 100% confident in getting it done) and comments (who has been assigned to do it, new scope, removed scoped, etc). Please use a table format to summarize with links to function details.
+
|| Edit Contract
 +
|| 100% implemented
 +
|align="center"| 0.25
 +
|| A huge technical obstacle for team due to unfamiliar technology. Requires a different layout from quotation and invoice. Li Dan and Yining in charge.
 +
|-
  
{| border="1"
+
|| Edit Sign-Off
|- style="background:blue; color:white"
+
|| 100% implemented
||Task/function/features, etc
+
|align="center"| 1
|align="center"|Status
+
|| Relatively easier to implement due to its similarity with contract template. Li Dan and Yining in charge.
|align="center"|Confident Level (0-1)
 
|align="center"|Comment
 
 
|-
 
|-
  
|| Customer CRUD
+
|| Edit Bug Logbook
|| Fully deployed and tested 100%
+
|| 100% implemented
|| 1
+
|align="center"| 0.75
|| Fiona
+
|| Requires a different layout from other documentation modules. Li Dan and Yining in charge.
 
|-
 
|-
  
|| Trend Analytic
+
|| Edit NDA
|| 25%
+
|| 100% implemented
|| 0.9
+
|align="center"| 1
|| Ben is researching analytic algoritms
+
|| Relatively easier to implement due to its similarity with contract template. Li Dan and Yining in charge.
 +
|-
 
|}
 
|}
 +
<br>
  
 +
<!----------------PROJECT SCHEDULE PLANNED VS ACTUAL ---->
 
===Project Schedule (Plan Vs Actual)===
 
===Project Schedule (Plan Vs Actual)===
  
Compare the project plan during acceptance 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.
+
Along the way, from acceptance till now, team has made some significant changes to schedule due to various reasons such as schedule delays, differences in system requirements between client and team and UAT feedback. The main bulk of changes comes in iteration 11 where we drilled deeper into the documentation module and Trello integration. Overall, the scope has expanded slightly with more specific requirements on documentation modules such as the need to implement the 'Sign Document' functionality. At the same time, unimportant tasks such as 'Upload Profile Picture' and 'News Feed' are either removed from the scope or pushed back to later dates to first focus our attention on completing primary and secondary features.
 +
 
 +
The table below displays the list of changes made to the schedule since acceptance.
 +
 
 +
{| border="1" cellpadding="5" cellspacing="0" width="80%"
 +
|- style="background:#C40000; color:white"
 +
| width="10px" align="center"| Iteration
 +
| colspan="2" align="center"| Planned
 +
| colspan="2" align="center"| Actual
 +
| width="100px" align="center"| Comments
 +
|-
 +
 
 +
| rowspan="2" align="center"| 8
 +
| width="130px"| Generate PDF Document
 +
| width="90px"| 5 Dec 2014
 +
| width="130px"|
 +
| width="90px"| 23 Dec 2014
 +
|| High learning curve for master setup, PDF generation and email attached document. Team focused on implementing master setup task first, and do more research on PDF generation and email attached document to be more prepared for the two tasks in next iteration.
 +
|-
 +
 
 +
|| Email PDF Document
 +
|| 5 Dec 2014
 +
||
 +
|| 23 Dec 2014
 +
|| High learning curve. Yining researched on this in current iteration and began implementing next iteration.
 +
|-
  
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.
+
| rowspan="4" align="center"| 9
 +
|| Hardware Resource
 +
|| 23 Dec 2014
 +
||
 +
|| 10 Feb 2015
 +
|| Not a core functionality, pushed back to later iteration to focus on completing core functionalities.
 +
|-
 +
 
 +
|| UAT 1
 +
|| 2 Jan 2015
 +
||
 +
|| 17 & 19 Jan 2015
 +
|| Team wasn't ready for UAT then.
 +
|-
 +
 
 +
|| UAT 2
 +
|| 17 Jan 2015
 +
||
 +
|| 9 Feb 2015
 +
|| UAT2 date affected by UAT1.
 +
|-
 +
 
 +
|| UAT 3
 +
|| 7 Feb 2015
 +
||
 +
|| 19 Feb 2015
 +
|| UAT3 date affected by UAT1 and UAT2.
 +
|-
 +
 
 +
| rowspan="5" align="center"| 10
 +
|| Upload Profile Picture
 +
|| 4 Jan 2014
 +
|| Task removed
 +
||
 +
|| Not an essential functionality to spend time on. Team concentrated on completing core functionalities first.
 +
|-
  
{| border="1"
+
| colspan="2"|
|- style="background:blue; color:white"
+
|| Revamp Trello Card to Board
|| Iterations
+
|| 4 Jan 2015
|colspan="2" align="center"| Planned
+
|| New task based on client's request to use Trello board instead of card.
|colspan="2" align="center"| Actual
 
|| Comments
 
 
|-
 
|-
  
|rowspan="2"| 1
+
| colspan="2"|
|| Customer CRUD  
+
|| CRUD of all Documentation Modules
|| 1 Sept 2010
+
|| 4 Jan 2015
||
+
|| Adjusted tasks in iteration to close misalignment gaps between client requirements and system built.  
|| 25 Aug 2010
 
|| Fiona took the Sales CRUD as well.
 
 
|-
 
|-
  
|| Trend Analytic
+
|| Project News Feed
|| 1 Sept 2010
+
|| 10 Feb 2015
 
||  
 
||  
|| 15 Sept 2010
+
|| 25 Feb 2015
|| Ben is too busy and pushed iteration 1 back
+
|| Team focused on completing core functionalities by midterm. News feed shifted to after midterm as it's not a core functionality.
 +
|-
 +
 
 +
| colspan="2"|
 +
|| User Feedback Session
 +
|| 9 Mar 2015
 +
|| Newly added milestone.
 +
|-
 +
 
 +
| rowspan="6" align="center"| 11
 +
| colspan="2"| 
 +
|| Product
 +
|| 23 Jan 2015
 +
|| Added product module in iteration 11 based on client's requirement.
 +
|-
 +
 
 +
| colspan="2"| 
 +
|| Task Approval
 +
|| 23 Jan 2015
 +
|| Client's request to allow project managers to approve tasks from Trello.
 +
|-
 +
 
 +
| colspan="2"| 
 +
|| Send Email for Rejected Tasks
 +
|| 23 Jan 2015
 +
|| Adopted based on supervisor's suggestion and after seeking client's approval.
 
|-
 
|-
  
|rowspan="2"| 2
+
| colspan="2"|
|| User tutorial
+
|| Sign/Pay Document
|| 1 Oct 2010
+
|| 23 Jan 2015
|colspan="2"|  
+
|| Client's request for ability to indicate the status of a document.
|| Removed proposed by Ben
 
 
|-
 
|-
  
|colspan="2"|  
+
| colspan="2"|
|| Psycho analysis
+
|| Seal Invoice
|| 1 Oct 2010
+
|| 23 Jan 2015
|| New module proposed by sponsor
+
|| A technical hurdle for the team due to unfamiliar technology. Li Dan and Yining took charge of this.
 +
|-
 +
 
 +
|| Product
 +
|| 23 Jan 2014
 +
||
 +
|| 10 Feb 2015
 +
|| Shifted product module to next iteration due to late product list submission from Viatick. 
 +
|-
 +
 
 +
| rowspan="1" align="center"| 12
 +
|| UAT 3
 +
|| 19 Feb 2015
 +
||
 +
|| 4 Mar 2015
 +
|| Pushed UAT3 to after midterm. Team focused on debugging from UAT2 and internal testing for live deployment.
 
|}
 
|}
 +
<br>
 +
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Insightiers_Project_Management View our current and past schedule timeline here]<br>
  
 
===Project Metrics===
 
===Project Metrics===
 +
<br>
 +
[[Image:Insightiers_Schedule_Metrics_Midterm.png | 700px]]
 +
<br>
 +
 +
{| border="1" cellpadding="5" cellspacing="0" width="80%"
 +
|- style="background:#C40000; color:white"
 +
| width="20px" align="center"| Iteration
 +
| width="75px" align="center"| Planned No. of Days
 +
| width="75px" align="center"| Actual No. of Days
 +
| width="70px" align="center"| SM Score (%)
 +
| width="100px" align="center"| Actions Taken
 +
|-
 +
 +
| align="center"| 1
 +
| align="center"| 8
 +
| align="center"| 8
 +
| align="center"| 100
 +
|| On track. Stuck to plan.
 +
|-
 +
 +
| align="center"| 2
 +
| align="center"| 15
 +
| align="center"| 15
 +
| align="center"| 100
 +
|| On track. Stuck to plan.
 +
|-
 +
 +
| align="center"| 3
 +
| align="center"| 10
 +
| align="center"| 12
 +
| align="center"| 83
 +
|| Stuck to plan for upcoming iteration as schedule was not affected by the delay because of sufficient buffer days. No need for adjustment of scope.
 +
|-
 +
 +
| align="center"| 4
 +
| align="center"| 14
 +
| align="center"| 22
 +
| align="center"| 64
 +
|| Dragged the iteration till completion of tasks. Adjusted the tasks required for the next two iterations due to shortage of time. Changed iterations 5 and 6 start and end dates in view of this iteration's delay.
 +
|-
 +
 +
| align="center"| 5
 +
| align="center"| 9
 +
| align="center"| 10
 +
| align="center"| 90
 +
|| Stuck to plan for upcoming iteration as schedule was not affected by the delay because of sufficient buffer days. No need for adjustment of scope.
 +
|-
 +
 +
| align="center"| 6
 +
| align="center"| 6
 +
| align="center"| 6
 +
| align="center"| 100
 +
|| On track. Stuck to plan.
 +
|-
  
Summary of analysis for the metrics collected. You may refer to another page for the details about the metrics and how it is collected.
+
| align="center"| 7
 +
| align="center"| 11
 +
| align="center"| 11
 +
| align="center"| 100
 +
|| On track. Stuck to plan.
 +
|-
  
===Project Risks===
 
  
Update the proposal assumptions and risks. Describe what you learn from the risk update and mitigation steps taken.  
+
| align="center"| 8
 +
| align="center"| 15
 +
| align="center"| 16
 +
| align="center"| 94
 +
|| On track. Stuck to plan.
 +
|-
 +
 
  
{| border="1"
+
| align="center"| 9
|- style="background:blue; color:white"
+
| align="center"| 10
|align="center" width="150px"| Risk
+
| align="center"| 11
|align="center"| Probability
+
| align="center"| 91
|align="center"| Impact
+
|| On track. Stuck to plan.
|align="center"| Mitigation
 
 
|-
 
|-
  
|width="150px"| Sponsor want to use Joomla instead of Drupal
+
| align="center"| 10
|| High
+
| align="center"| 16
|| High
+
| align="center"| 19
|| Team evaluating Joomla to write an impact analysis report
+
| align="center"| 84
 +
|| Re-adjusted tasks by focusing on core functionalities. Removed supplementary task 'upload profile picture'. Shifted news feed task to after midterm.
 
|-
 
|-
  
|width="150px"| Sponsor deployment machine approval and support
+
| align="center"| 11
|| High
+
| align="center"| 15
|| Medium (now it is low)
+
| align="center"| 18
|| Use UPL machine
+
| align="center"| 83
 +
|| Stuck to plan for upcoming iteration as schedule was not affected by the delay because of sufficient buffer days. No need for adjustment of scope. However, shifted product module to the next iteration as client delayed the product list submission.
 +
|-
 
|}
 
|}
 +
<br>
 +
[[Image:Insightiers_Bug_Metrics_Midterm.png | 1000px]]
 +
<br>
 +
{| border="1" cellpadding="5" cellspacing="0" width="80%"
 +
|- style="background:#C40000; color:white"
 +
| width="20px" align="center"| Iteration
 +
| width="75px" align="center"| Total Bug Score
 +
| width="100px" align="center"| Brief Explanation
 +
| width="100px" align="center"| Action Taken
 +
|-
 +
 +
| align="center"| 1
 +
| align="center"| -
 +
|| No coding task in this iteration
 +
||
 +
|-
 +
 +
| align="center"| 2
 +
| align="center"| -
 +
|| No coding task in this iteration
 +
||
 +
|-
 +
 +
| align="center"| 3
 +
| align="center"| 29
 +
|| The first coding iteration. Team was challenged by the new framework Play and the integration with Outlook.
 +
|| Stopped current development and resolve the bug immediately. Used up buffer days to debug.
 +
|-
  
Be sure to prioritize the risks.
+
| align="center"| 4
 +
| align="center"| 64
 +
|| Misalignment between system and the business requirements. Test cases designed differ from what was built in system. Several required error messages missing. Project module had couple of critical bugs.
 +
|| Stopped current development and resolve the bug immediately. Used up buffer days to debug.
 +
|-
  
===Technical Complexity===
+
| align="center"| 5
 +
| align="center"| 27
 +
|| Critical bug occurred where edit task button could not work.
 +
|| Stopped current development and resolve the bug immediately. Used up buffer day to debug.
 +
|-
  
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.
+
| align="center"| 6
 +
| align="center"| 11
 +
||
 +
|| Used planned debugging time in iteration.
 +
|-
  
==Quality of product==
+
| align="center"| 7
 +
| align="center"| 33
 +
|| Bugs mainly came from Project module.
 +
|| Stopped current development and resolve the bug immediately. Bugs found were relatively easy to solve thus buffer days were not used. Schedule not affected.
 +
|-
  
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.
+
| align="center"| 8
 +
| align="center"| -
 +
|| All developers went back to China where SVN could not work. Integration of codes was not possible thus testing was halt.  
 +
||
 +
|-
  
===Intermediate Deliverables===
+
| align="center"| 9
 +
| align="center"| -
 +
|| All developers went back to China where SVN could not work. Integration of codes was not possible thus testing was halt.
 +
||
 +
|-
  
There should be some evidence of work in progress.  
+
| align="center"| 10
 +
| align="center"| 32
 +
|| Technical difficulty in PDF generation and emailing of document attachment.
 +
|| Stopped current development and resolve the bug immediately. Bugs found were relatively easy to solve thus buffer days were not used. Schedule not affected.
 +
|-
  
{| border="1"
+
| align="center"| 11
|- style="background:blue; color:white"
+
| align="center"| 40
|align="center"| Stage
+
||  
|align="center"| Specification
+
|| Stopped current development and resolve the bug immediately. Bugs found were rather tricky and thus dragged into to buffer days. Schedule not affected though.
|align="center"| Modules
 
 
|-
 
|-
  
|rowspan="2"| Project Management
+
|}
|| Minutes
+
<br>
|| Sponsor weeks -10 -5 3 7 Supervisor weeks -2 3 5 7
+
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Insightiers_Metrics View our schedule and bug metrics detailed explanations and actions taken here]<br>
 +
 
 +
===Project Risks===
 +
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Insightiers_Risk_Management View all our risks and mitigation plans here]<br>
 +
<br>
 +
Instead of regurgitating the risks mentioned in the above link, we've picked out the top 3 risks that have been activated and dealt with and they are as follows:
 +
<br>
 +
{| border="1" cellpadding="5" cellspacing="0" width="80%"
 +
|- style="background:#C40000; color:white"
 +
| width="70px" align="center"| Risk Description
 +
| width="70px" align="center"| How It Has Impacted Team
 +
| width="20px" align="center"| Likelihood
 +
| width="20px" align="center"| Impact
 +
| width="40px" align="center"| Action Taken
 
|-
 
|-
  
|| Metrics
+
|| Steep learning curve in exploring new technologies and integrating with 3rd party software, such as Trello integration and master setup template.
|| Bug metrics
+
|| Load factor per member increased to research intensively and also to debug. Buffer days were used for debugging. Schedule was not greatly affected as sufficient buffer days were allocated in most of the iterations.
 +
|align="center"| Medium
 +
|align="center"| High
 +
|| Members researched intensively and sought for help from IT experts in Viatick if necessary.
 
|-
 
|-
  
|| Requirements
+
|| Differing opinions between client and team on the requirements and functionalities.
|| Story cards
+
|| Tasks assigned in iteration 10 and 11 were greatly affected. Some tasks were removed or pushed back to future iterations. Schedule was delayed as a result.
|| [http://www.agilemodeling.com/artifacts/userStory.htm CRUD Customer], [http://www.agilemodeling.com/artifacts/userStory.htm Trend Analytic]
+
|align="center"| High
 +
|align="center"| Medium
 +
|| Re-added tasks that were thought to have completed in past iterations, such as CRUD of Quotation module, to iteration 10 to work on the misalignment in requirements between client and system.
 
|-
 
|-
  
|rowspan="4"| Analysis
+
|| Client asks for changes to project requirements, such as the 'Sign Document' functionality.
|| Use case
+
|| Tasks assigned in iteration 10 and 11 were greatly affected. Some tasks were removed or pushed back to future iterations. Schedule was delayed as a result but team managed to overcome the delay by increasing load factor.
|| [http://en.wikipedia.org/wiki/Use_case_diagram overall]
+
|align="center"| Low
 +
|align="center"| High
 +
|| New tasks were added to include the new requests from client. Supplementary task 'Upload Profile Picture' was agreed to be dropped. Less important tasks such as 'News Feed' were pushed to later dates to focus on completing core functionalities.
 
|-
 
|-
  
|| System Sequence Diagram
+
 
|| [http://en.wikipedia.org/wiki/System_Sequence_Diagram client], [http://en.wikipedia.org/wiki/System_Sequence_Diagram server]
+
|}
 +
<br>
 +
Besides the above activated risks, we have also come up with more potential risks that may occur in the future and they are as follows:
 +
<br>
 +
{| border="1" cellpadding="5" cellspacing="0" width="80%"
 +
|- style="background:#C40000; color:white"
 +
| width="90px" align="center"| Risk Description
 +
| width="90px" align="center"| How It May Impact Team
 +
| width="20px" align="center"| Likelihood
 +
| width="20px" align="center"| Impact
 +
| width="40px" align="center"| Mitigation Plan
 
|-
 
|-
  
|| [http://en.wikipedia.org/wiki/Business_Process_Modeling_Notation Business Process Diagram]
+
|| Trello closes down its application for good.  
|| Here
+
|| Integration with Trello will no longer work and features such as 'Trello Update' will not be applicable anymore.
 +
|align="center"| Low
 +
|align="center"| Medium
 +
|| Reduce our application's dependency on Trello to ensure that minimal casualty is achieved should risk be activated.
 
|-
 
|-
  
|| Screen Shots
+
|| New users, such as new Viatick staff or client, find it difficult to understand and use the application.
|| CRUD Customer, Trend Analysis
+
|| Users may end up going backwards and use Microsoft tools such as Word and Excel, thereby giving up the use of the application.
 +
|align="center"| Medium
 +
|align="center"| Low
 +
|| Conduct multiple user testings with various personas and hold user feedback session to gather opinions on the ease of using the application. From the feedback gathered, team shall then fine-tune the application to enhance usability of the application.
 +
|}
 +
<br>
 +
 
 +
===Technical Complexity===
 +
{| border="1" cellpadding="5" cellspacing="0" width="80%"
 +
|- style="background:#C40000; color:white"
 +
| width="40px" align="center"| S/N (highest complexity to lowest)
 +
| width="40px" align="center"| Complexity Rating
 +
| width="100px" align="center"| Technical Description
 +
| width="70px" align="center"| Remarks
 
|-
 
|-
  
|rowspan="2"| Design
+
| align="center"| 1
|| [http://en.wikipedia.org/wiki/Entity-relationship_model ER Diagram]
+
| align="center"| [[Image:Insightiers_Complexity3star.png | 70px]]
|| 1, 2, 3
+
|| Integrating the projects between application and Trello was extremely challenging.  
 +
|| Affected our planned schedule and caused a huge delay in iteration 4.
 
|-
 
|-
  
|| [http://en.wikipedia.org/wiki/Class_diagram Class Diagram]
+
| align="center"| 2
|| [http://en.wikipedia.org/wiki/Class_diagram 1], [http://en.wikipedia.org/wiki/Class_diagram 2], [http://en.wikipedia.org/wiki/Class_diagram 3]
+
| align="center"| [[Image:Insightiers_Complexity2star.png | 47px]]
 +
|| Adoption of Play framework took a lot of effort to research and understand the framework.
 +
||
 
|-
 
|-
  
 +
| align="center"| 3
 +
| align="center"| [[Image:Insightiers_Complexity1star.png | 22px]]
 +
|| Introduction of predecessor and successor of project tasks required a lot of logical thinking.
 +
||
  
|| Testing
 
|| User test plan
 
|| [[IS480_Midterm_Wiki#Testing: | instructions]]
 
 
|}
 
|}
  
Not all parts of the deliverables are necessary but the evidence should be convincing of the progress. Try to include design deliverables that shows the quality of your project.
+
==Quality of product==
 +
===Intermediate Deliverables===
 +
 
 +
{| border="1" cellpadding="5" cellspacing="0" width="50%"
 +
|- style="background:#C40000; color:white"
 +
| width="20px" align="center"| Stage
 +
| width="40px" align="center"| Specification
 +
| width="40px" align="center"| Relevant Links
 +
|-
 +
 
 +
|rowspan="2"| Project Management
 +
|| Meeting Minutes
 +
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Insightiers_Meeting_Minutes Meeting Minutes]
 +
|-
 +
 
 +
|| Schedule and Bug Metrics
 +
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Insightiers_Metrics Metrics]
 +
|-
 +
 
 +
|| Analysis
 +
|| Use Case and Architecture Diagrams
 +
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Insightiers_Project_Documentation Diagrams],
 +
|-
 +
 
 +
|rowspan="2"| Design
 +
|| ER Diagram
 +
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Insightiers_Project_Documentation ER Diagram]
 +
|-
 +
 
 +
|| Prototypes
 +
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Insightiers_Prototypes Prototypes]
 +
|-
 +
|-
  
 +
|| Testing
 +
|| User Test Plan
 +
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Insightiers_UAT1 UAT1],  [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Insightiers_UAT2 UAT2]
 +
|}
 +
<br>
 
===Deployment===
 
===Deployment===
  
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]].
+
[http://128.199.171.117:9000 View our staging SYMPLProj application here]<br>
 +
[http://www.symplproj.com View our live SYMPLProj application here]<br>
 +
<br>
 +
[[Media:Insightiers_Deployment_Plan.pdf | View our deployment plan here]]<br>
 +
[[Media:Insightiers_Contingency_Plan.pdf | View our contingency plan here]]<br>
 +
[[Media:Insightiers_Contingency_Plan_V2.pdf | View our updated contingency plan here]]<br>
 +
[[Media:Insightiers_Agreement_Form.pdf | View our agreement form here]]<br>
 +
<br>
 +
Please take note that there is user access control to various pages and functions. The one thing that you should know is that an admin user is not allowed to create/edit projects. Only the project manager in charge of the project is allowed to edit. You may wish to find out more about the user access control table by downloading it here:<br>
 +
[[Media:Insightiers_User_Access_Control_Table.xlsx | User Access Control Table for Our SYMPLProj Application]]
  
 
===Testing===
 
===Testing===
  
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.
+
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Insightiers_UAT1 View our UAT1 for more details]<br>
 +
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Insightiers_UAT2 View our UAT2 for more details]<br>
 +
 
  
 
==Reflection==
 
==Reflection==
 
In this section, describe what have the team learn? Be brief. Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.
 
  
 
===Team Reflection===
 
===Team Reflection===
  
Any training and lesson learn? What are the take-away so far? It would be very convincing if the knowledge is share at the wiki [[Knowledge_base | knowledge base]] and linked here.
+
*Learnt new technologies
 +
*Learnt about liaising with real world client
 +
*Learnt to manage time well between FYP and other commitments
 +
*Learnt to be more flexible and open to changes and ideas
 +
*Learnt to joke around and stay positive even during tough times
  
 
===Individual Reflection===
 
===Individual Reflection===
  
You may include individual reflection if that make sense at this point. The team is uncooperative and did not follow my instructions.
+
<u>Project Manager: Elaine</u>
-->
+
*Learnt to adapt to members’ culture to communicate more effectively
 +
*Learnt that understanding and planning of technical tasks is not easy
 +
*Learnt to professionally manage and balance stakeholders’ interests without compromising team’s interest and schedule
 +
*It’s all about patience, understanding and being accommodating
 +
 
 +
<br>
 +
<u>Lead Designer: Li Dan</u>
 +
*Learnt front end technologies
 +
*Learnt to define and implement innovative solutions for product visuals and user experience
 +
*Learnt to translate those solutions into intuitive and functional user interface
 +
*It’s about being adventurous,  being creative and being bold
 +
 
 +
<br>
 +
<u>Lead Developer: Zheng Yixi</u>
 +
*Learnt about Play framework and its usefulness to development
 +
*Learnt about considering all corner cases when integrating systems
 +
*Learnt about writing scalable codes  leave room for future changes
 +
*It’s all about being logical, being logical and being logical
 +
 
 +
<br>
 +
<u>Business Analyst: Zhang Annan</u>
 +
*Learnt to skillfully gather requirements from a real world client
 +
*Learnt to accurately translate business to technical requirements
 +
*It’s all about building relationship, communication and being comprehensive
 +
 
 +
<br>
 +
<u>System Analyst: Liu Yining</u>
 +
*Learnt to be meticulous in formulating detailed test cases to ensure quality application
 +
*Learnt to conduct user tests and gather feedback to enhance usability of application
 +
*It’s all about being meticulous, hardworking and a fortune teller
 +
 
 
</div>
 
</div>

Latest revision as of 13:40, 16 March 2015

Insightiers Official Logo.png

  Home Navi V2.png   Project Overview Navi.png   Team Navi.png   Project Management Navi.png   Project Documentation Navi.png  
Home   Midterm Wiki   Final Wiki


Slides and Links

View our midterm presentation slides here


As you are viewing our midterm wiki, you may realize that we've included several links in their relevant sections.
For your convenience sake, we've consolidated the list of links used in this midterm wiki in the following:
Project Scope
Current and Past Schedule Timeline
UAT1 Results
UAT2 Results
Schedule and Bug Metrics
Risk Management

Project Progress Summary

Project Highlights

Unexpected events that have occurred:

  • Two members' laptops broke down, which resulted in loss of time for system development
  • Could not access SVN in China
  • List of major changes to be made from December holidays and UATs:
    • Revamped simulation calendar feature
    • Changed cards to boards in Trello
    • Added task approval from Trello
    • Added email task rejection
    • Added sign/pay functions for documents
    • Added seal invoice function
    • Deploying on DigitalOcean instead of AWS
    • Implemented security features for secured data transmission
  • Took longer than expected to complete document master setup
  • Integration with Trello was a lot tougher than expected
  • Actual learning curve for email function was a lot higher
  • Delay in product list submission by client
  • UAT3 pushed to after midterm


In a Nutshell

Insightiers Midterm Progress Nutshell.png

View our project scope here

Project Management

Project Status

Module Task/Features Status Confidence Level (0-1) Remark
User Account Management Login 100% implemented and user testing done 1 Yixi & Li Dan
Logout 100% implemented and user testing done 1 Yixi & Li Dan
Forget/Reset Password 100% implemented and user testing done 0.5 Email function new to team. Yixi & Annan in charge.
Create Account 100% implemented and user testing done 1 Yixi & Li Dan
Edit Account 100% implemented and user testing done 1 Yixi & Li Dan
Delete Account 100% implemented 1 Yixi & Li Dan
Filter Account 100% implemented and user testing done 1 Li Dan
Staff Management Create Staff 100% implemented and user testing done 1 Yixi & Li Dan
Edit Staff 100% implemented and user testing done 1 Yixi & Li Dan
Delete/Deactivate Staff 100% implemented 1 Li Dan & Yining
Staff Portfolio Display Staff Portfolio 100% implemented and user testing done 1 Li Dan
Filter Portfolio Summary Page 100% implemented and user testing done 1 Li Dan & Annan
View Projects 100% implemented 1 Li Dan
Filter Projects of Staff 100% implemented 1 Li Dan & Annan
View Tasks in Calendar 100% implemented 0.75 Li Dan
Project Create Project 100% implemented and user testing done 0.25 Replicating project to Trello was technically challenging. Li Dan, Yixi & Annan in charge.
Edit Project 100% implemented and user testing done 1 Li Dan, Yixi & Annan in charge.
View Project Summary Page 100% implemented and user testing done 1 Li Dan
View Individual Project 100% implemented and user testing done 1 Li Dan & Annan
Start Project 100% implemented 1 Li Dan & Yixi
End Project 100% implemented 1 Yixi & Annan
Close Project 100% implemented 1 Yixi & Annan
Cancel Project 100% implemented 1 Yixi & Annan
Delete Project 100% implemented 1 Yixi & Annan
View Project Tasks 100% implemented and user testing done 1 Li Dan
Project News Feed To be implemented in iteration 13 1 Li Dan and Yixi
Approve Tasks from Trello 100% implemented and user testing done 1 Newly added task, client approved. Yixi & Annan in charge.
Email Task Rejection 100% implemented 1 Newly added task based on supervisor's suggestion, client approved. Yixi & Annan in charge.
Export Projects to CSV To be implemented in iteration 13 1 Yixi & Annan
Project Task Create Task 100% implemented and user testing done 0.25 Replicating task to Trello was technically challenging. Li Dan & Annan in charge.
Edit Task 100% implemented and user testing done 1 Li Dan & Annan
End Task 100% implemented 1 Li Dan & Annan
Delete Task 100% implemented 1 Li Dan & Annan
View Task 100% implemented and user testing done 1 Li Dan & Annan
Dashboard View Dashboard 100% implemented 1 Li Dan & Annan
Simulation Create Simulation 100% implemented and user testing done 1 Li Dan & Annan
View Simulation 100% implemented and user testing done 1 Li Dan & Annan
Clear Simulation 100% implemented 1 Li Dan & Annan
View Simulated Details 100% implemented and user testing done 1 Li Dan
Create Project from Simulation 100% implemented and user testing done 1 Li Dan
View Projects in Each Month 100% implemented 1 Li Dan
Quotation Create Quotation 100% implemented and user testing done 0.5 Challenged by technical difficulty in pulling data from master setup template. Li Dan & Yining in charge.
Create Quotation with Preset Modules 100% implemented 0.75 Displaying data on quotation from preset modules challenging. Li Dan & Yining in charge.
Edit Quotation 100% implemented 1 Li Dan & Yining
View Quotation Summary Page 100% implemented 1 Li Dan & Yining
View Individual Quotation 100% implemented and user testing done 1 Li Dan & Yining
Save Quotation 100% implemented and user testing done 1 Li Dan & Yining
Delete Quotation 100% implemented 1 Li Dan & Yining
Generate Quotation to PDF 100% implemented and user testing done 0.25 Unfamiliar with technology. Huge technical challenge team has faced. Li Dan & Yining in charge.
Send Quotation via Email 100% implemented 0.5 Send attachment via email technology new to team. Li Dan & Yining in charge.
Sign Quotation 100% implemented 1 Li Dan & Yining
Export Quotations to CSV To be implemented in iteration 13 1 Yixi & Annan
Invoice Create Invoice 100% implemented 0.5 Challenged by technical difficulty in pulling data from master setup template.
Edit Invoice 100% implemented 1 Li Dan & Yining
View Invoice Summary Page 100% implemented 1 Li Dan & Yining
View Individual Invoice 100% implemented and user testing done 1 Li Dan & Yining
Save Invoice 100% implemented and user testing done 1 Li Dan & Yining
Delete Invoice 100% implemented 1 Li Dan & Yining
Generate Invoice to PDF 100% implemented and user testing done 0.25 Unfamiliar with technology. Huge technical challenge team has faced. Li Dan & Yining in charge.
Send Invoice via Email 100% implemented 0.5 Send attachment via email technology new to team. Li Dan & Yining in charge.
Pay Invoice 100% implemented 1 Li Dan & Yining
Seal Invoice 100% implemented 0.5 A technical hurdle as team has never tried inserting picture into a document. Li Dan & Yining in charge.
Export Invoice to CSV To be implemented in iteration 13 1 Yixi & Annan
Contract Create Contract 100% implemented and user testing done 0.5 Challenged by technical difficulty in pulling data from master setup template. Li Dan & Yining in charge.
Edit Contract 100% implemented 1 Li Dan & Yining
View Contract Summary Page 100% implemented and user testing done 1 Li Dan & Yining
View Individual Contract 100% implemented and user testing done 1 Li Dan
Save Contract 100% implemented and user testing done 1 Li Dan & Yining
Delete Contract 100% implemented 1 Li Dan & Yining
Generate Contract to PDF 100% implemented and user testing done 0.25 Unfamiliar with technology. Huge technical challenge team has faced. Yining in charge.
Send Contract via Email 100% implemented 0.5 Send attachment via email technology new to team. Li Dan & Yining in charge.
Sign Contract 100% implemented 1 Li Dan & Yining
Sign-Off Create Sign-Off 100% implemented 0.5 Relatively easier to implement due to its similarity with contract template. Li Dan & Yining in charge.
Edit Sign-Off 100% implemented 1 Li Dan & Yining
View Sign-Off Summary Page 100% implemented 1 Li Dan & Yining
View Individual Sign-Off 100% implemented 1 Li Dan
Save Sign-Off 100% implemented 1 Li Dan & Yining
Delete Sign-Off 100% implemented 1 Li Dan & Yining
Generate Sign-Off to PDF 100% implemented 0.25 Unfamiliar with technology. Huge technical challenge team has faced. Yining in charge.
Send Sign-Off via Email 100% implemented 0.5 Send attachment via email technology new to team. Li Dan & Yining in charge.
Sign Sign-Off 100% implemented 1 Li Dan & Yining
Bug Logbook Create Bug Logbook 100% implemented 0.5 A different layout from other document templates. New UI hurdle to overcome. Li Dan in charge.
Edit Bug Logbook 100% implemented 1 Li Dan & Yining
View Bug Logbook Summary Page 100% implemented 1 Li Dan & Yining
View Individual Bug Logbook 100% implemented 1 Li Dan
Save Bug Logbook 100% implemented 1 Li Dan & Yining
Delete Bug Logbook 100% implemented 1 Li Dan & Yining
NDA Create NDA 100% implemented 0.75 A relatively easier module to do with reference from contract module. Li Dan & Yining in charge.
Edit NDA 100% implemented 1 Li Dan & Yining
View NDA Summary Page 100% implemented 1 Li Dan & Yining
View Individual NDA 100% implemented 1 Li Dan
Save NDA 100% implemented 1 Li Dan & Yining
Delete NDA 100% implemented 1 Li Dan & Yining
Generate NDA to PDF 100% implemented 0.25 Unfamiliar with technology. Huge technical challenge team has faced. Yining in charge.
Send NDA via Email 100% implemented 0.5 Send attachment via email technology new to team. Li Dan & Yining in charge.
Sign NDA 100% implemented 1 Li Dan & Yining
Product Create Product 100% implemented 1 Li Dan and Yining
Edit Product 100% implemented 1 Li Dan and Yining
View Product Summary Page 100% implemented 1 Li Dan and Yining
View Individual Product Details 100% implemented 1 Li Dan and Yining
Delete Product 100% implemented 1 Li Dan and Yining
Hardware Create Hardware 100% implemented 1 Yixi and Annan
Edit Hardware 100% implemented 1 Yixi and Annan
View Hardware Summary Page 100% implemented 1 Yixi and Annan
Assign Hardware to Staff 100% implemented 1 Yixi and Li Dan
Delete Hardware 100% implemented 1 Yixi and Li Dan
Master Setup Edit Quotation 100% implemented 0.25 A huge technical obstacle for team due to unfamiliar technology. Li Dan and Yining in charge.
Edit Quotation Preset Modules 100% implemented 0.5 Tough to implement due to technical difficulty. Li Dan and Yining in charge.
Edit Invoice 100% implemented 0.25 A huge technical obstacle for team due to unfamiliar technology. Requires different layout from quotation. Li Dan and Yining in charge.
Edit Contract 100% implemented 0.25 A huge technical obstacle for team due to unfamiliar technology. Requires a different layout from quotation and invoice. Li Dan and Yining in charge.
Edit Sign-Off 100% implemented 1 Relatively easier to implement due to its similarity with contract template. Li Dan and Yining in charge.
Edit Bug Logbook 100% implemented 0.75 Requires a different layout from other documentation modules. Li Dan and Yining in charge.
Edit NDA 100% implemented 1 Relatively easier to implement due to its similarity with contract template. Li Dan and Yining in charge.


Project Schedule (Plan Vs Actual)

Along the way, from acceptance till now, team has made some significant changes to schedule due to various reasons such as schedule delays, differences in system requirements between client and team and UAT feedback. The main bulk of changes comes in iteration 11 where we drilled deeper into the documentation module and Trello integration. Overall, the scope has expanded slightly with more specific requirements on documentation modules such as the need to implement the 'Sign Document' functionality. At the same time, unimportant tasks such as 'Upload Profile Picture' and 'News Feed' are either removed from the scope or pushed back to later dates to first focus our attention on completing primary and secondary features.

The table below displays the list of changes made to the schedule since acceptance.

Iteration Planned Actual Comments
8 Generate PDF Document 5 Dec 2014 23 Dec 2014 High learning curve for master setup, PDF generation and email attached document. Team focused on implementing master setup task first, and do more research on PDF generation and email attached document to be more prepared for the two tasks in next iteration.
Email PDF Document 5 Dec 2014 23 Dec 2014 High learning curve. Yining researched on this in current iteration and began implementing next iteration.
9 Hardware Resource 23 Dec 2014 10 Feb 2015 Not a core functionality, pushed back to later iteration to focus on completing core functionalities.
UAT 1 2 Jan 2015 17 & 19 Jan 2015 Team wasn't ready for UAT then.
UAT 2 17 Jan 2015 9 Feb 2015 UAT2 date affected by UAT1.
UAT 3 7 Feb 2015 19 Feb 2015 UAT3 date affected by UAT1 and UAT2.
10 Upload Profile Picture 4 Jan 2014 Task removed Not an essential functionality to spend time on. Team concentrated on completing core functionalities first.
Revamp Trello Card to Board 4 Jan 2015 New task based on client's request to use Trello board instead of card.
CRUD of all Documentation Modules 4 Jan 2015 Adjusted tasks in iteration to close misalignment gaps between client requirements and system built.
Project News Feed 10 Feb 2015 25 Feb 2015 Team focused on completing core functionalities by midterm. News feed shifted to after midterm as it's not a core functionality.
User Feedback Session 9 Mar 2015 Newly added milestone.
11 Product 23 Jan 2015 Added product module in iteration 11 based on client's requirement.
Task Approval 23 Jan 2015 Client's request to allow project managers to approve tasks from Trello.
Send Email for Rejected Tasks 23 Jan 2015 Adopted based on supervisor's suggestion and after seeking client's approval.
Sign/Pay Document 23 Jan 2015 Client's request for ability to indicate the status of a document.
Seal Invoice 23 Jan 2015 A technical hurdle for the team due to unfamiliar technology. Li Dan and Yining took charge of this.
Product 23 Jan 2014 10 Feb 2015 Shifted product module to next iteration due to late product list submission from Viatick.
12 UAT 3 19 Feb 2015 4 Mar 2015 Pushed UAT3 to after midterm. Team focused on debugging from UAT2 and internal testing for live deployment.


View our current and past schedule timeline here

Project Metrics


Insightiers Schedule Metrics Midterm.png

Iteration Planned No. of Days Actual No. of Days SM Score (%) Actions Taken
1 8 8 100 On track. Stuck to plan.
2 15 15 100 On track. Stuck to plan.
3 10 12 83 Stuck to plan for upcoming iteration as schedule was not affected by the delay because of sufficient buffer days. No need for adjustment of scope.
4 14 22 64 Dragged the iteration till completion of tasks. Adjusted the tasks required for the next two iterations due to shortage of time. Changed iterations 5 and 6 start and end dates in view of this iteration's delay.
5 9 10 90 Stuck to plan for upcoming iteration as schedule was not affected by the delay because of sufficient buffer days. No need for adjustment of scope.
6 6 6 100 On track. Stuck to plan.
7 11 11 100 On track. Stuck to plan.
8 15 16 94 On track. Stuck to plan.
9 10 11 91 On track. Stuck to plan.
10 16 19 84 Re-adjusted tasks by focusing on core functionalities. Removed supplementary task 'upload profile picture'. Shifted news feed task to after midterm.
11 15 18 83 Stuck to plan for upcoming iteration as schedule was not affected by the delay because of sufficient buffer days. No need for adjustment of scope. However, shifted product module to the next iteration as client delayed the product list submission.


Insightiers Bug Metrics Midterm.png

Iteration Total Bug Score Brief Explanation Action Taken
1 - No coding task in this iteration
2 - No coding task in this iteration
3 29 The first coding iteration. Team was challenged by the new framework Play and the integration with Outlook. Stopped current development and resolve the bug immediately. Used up buffer days to debug.
4 64 Misalignment between system and the business requirements. Test cases designed differ from what was built in system. Several required error messages missing. Project module had couple of critical bugs. Stopped current development and resolve the bug immediately. Used up buffer days to debug.
5 27 Critical bug occurred where edit task button could not work. Stopped current development and resolve the bug immediately. Used up buffer day to debug.
6 11 Used planned debugging time in iteration.
7 33 Bugs mainly came from Project module. Stopped current development and resolve the bug immediately. Bugs found were relatively easy to solve thus buffer days were not used. Schedule not affected.
8 - All developers went back to China where SVN could not work. Integration of codes was not possible thus testing was halt.
9 - All developers went back to China where SVN could not work. Integration of codes was not possible thus testing was halt.
10 32 Technical difficulty in PDF generation and emailing of document attachment. Stopped current development and resolve the bug immediately. Bugs found were relatively easy to solve thus buffer days were not used. Schedule not affected.
11 40 Stopped current development and resolve the bug immediately. Bugs found were rather tricky and thus dragged into to buffer days. Schedule not affected though.


View our schedule and bug metrics detailed explanations and actions taken here

Project Risks

View all our risks and mitigation plans here

Instead of regurgitating the risks mentioned in the above link, we've picked out the top 3 risks that have been activated and dealt with and they are as follows:

Risk Description How It Has Impacted Team Likelihood Impact Action Taken
Steep learning curve in exploring new technologies and integrating with 3rd party software, such as Trello integration and master setup template. Load factor per member increased to research intensively and also to debug. Buffer days were used for debugging. Schedule was not greatly affected as sufficient buffer days were allocated in most of the iterations. Medium High Members researched intensively and sought for help from IT experts in Viatick if necessary.
Differing opinions between client and team on the requirements and functionalities. Tasks assigned in iteration 10 and 11 were greatly affected. Some tasks were removed or pushed back to future iterations. Schedule was delayed as a result. High Medium Re-added tasks that were thought to have completed in past iterations, such as CRUD of Quotation module, to iteration 10 to work on the misalignment in requirements between client and system.
Client asks for changes to project requirements, such as the 'Sign Document' functionality. Tasks assigned in iteration 10 and 11 were greatly affected. Some tasks were removed or pushed back to future iterations. Schedule was delayed as a result but team managed to overcome the delay by increasing load factor. Low High New tasks were added to include the new requests from client. Supplementary task 'Upload Profile Picture' was agreed to be dropped. Less important tasks such as 'News Feed' were pushed to later dates to focus on completing core functionalities.


Besides the above activated risks, we have also come up with more potential risks that may occur in the future and they are as follows:

Risk Description How It May Impact Team Likelihood Impact Mitigation Plan
Trello closes down its application for good. Integration with Trello will no longer work and features such as 'Trello Update' will not be applicable anymore. Low Medium Reduce our application's dependency on Trello to ensure that minimal casualty is achieved should risk be activated.
New users, such as new Viatick staff or client, find it difficult to understand and use the application. Users may end up going backwards and use Microsoft tools such as Word and Excel, thereby giving up the use of the application. Medium Low Conduct multiple user testings with various personas and hold user feedback session to gather opinions on the ease of using the application. From the feedback gathered, team shall then fine-tune the application to enhance usability of the application.


Technical Complexity

S/N (highest complexity to lowest) Complexity Rating Technical Description Remarks
1 Insightiers Complexity3star.png Integrating the projects between application and Trello was extremely challenging. Affected our planned schedule and caused a huge delay in iteration 4.
2 Insightiers Complexity2star.png Adoption of Play framework took a lot of effort to research and understand the framework.
3 Insightiers Complexity1star.png Introduction of predecessor and successor of project tasks required a lot of logical thinking.

Quality of product

Intermediate Deliverables

Stage Specification Relevant Links
Project Management Meeting Minutes Meeting Minutes
Schedule and Bug Metrics Metrics
Analysis Use Case and Architecture Diagrams Diagrams,
Design ER Diagram ER Diagram
Prototypes Prototypes
Testing User Test Plan UAT1, UAT2


Deployment

View our staging SYMPLProj application here
View our live SYMPLProj application here

View our deployment plan here
View our contingency plan here
View our updated contingency plan here
View our agreement form here

Please take note that there is user access control to various pages and functions. The one thing that you should know is that an admin user is not allowed to create/edit projects. Only the project manager in charge of the project is allowed to edit. You may wish to find out more about the user access control table by downloading it here:
User Access Control Table for Our SYMPLProj Application

Testing

View our UAT1 for more details
View our UAT2 for more details


Reflection

Team Reflection

  • Learnt new technologies
  • Learnt about liaising with real world client
  • Learnt to manage time well between FYP and other commitments
  • Learnt to be more flexible and open to changes and ideas
  • Learnt to joke around and stay positive even during tough times

Individual Reflection

Project Manager: Elaine

  • Learnt to adapt to members’ culture to communicate more effectively
  • Learnt that understanding and planning of technical tasks is not easy
  • Learnt to professionally manage and balance stakeholders’ interests without compromising team’s interest and schedule
  • It’s all about patience, understanding and being accommodating


Lead Designer: Li Dan

  • Learnt front end technologies
  • Learnt to define and implement innovative solutions for product visuals and user experience
  • Learnt to translate those solutions into intuitive and functional user interface
  • It’s about being adventurous, being creative and being bold


Lead Developer: Zheng Yixi

  • Learnt about Play framework and its usefulness to development
  • Learnt about considering all corner cases when integrating systems
  • Learnt about writing scalable codes leave room for future changes
  • It’s all about being logical, being logical and being logical


Business Analyst: Zhang Annan

  • Learnt to skillfully gather requirements from a real world client
  • Learnt to accurately translate business to technical requirements
  • It’s all about building relationship, communication and being comprehensive


System Analyst: Liu Yining

  • Learnt to be meticulous in formulating detailed test cases to ensure quality application
  • Learnt to conduct user tests and gather feedback to enhance usability of application
  • It’s all about being meticulous, hardworking and a fortune teller