HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2015T1 Chipmunks Final Wiki"

From IS480
Jump to navigation Jump to search
(Added project highlights)
m (Update Finals slide)
 
(6 intermediate revisions by 2 users not shown)
Line 49: Line 49:
 
[[Image: Chipmunks FinalsWiki Title.png|center|800px]]
 
[[Image: Chipmunks FinalsWiki Title.png|center|800px]]
 
=Project Progress Summary=
 
=Project Progress Summary=
[[Image: Chipmunks Finals Dashboard.png|center|1000px]]
+
[[Image: Chipmunks Finals Dashboard_v2.png|center|1000px]]
  
  
Line 58: Line 58:
 
! style="font-weight: bold;background: #0077B5;color:#fff;" | Deployed Site
 
! style="font-weight: bold;background: #0077B5;color:#fff;" | Deployed Site
 
|-
 
|-
| [[Image:Chipmunks Mid-term-slides.png|130px|link=https://drive.google.com/open?id=0BzxXlDDPiCKfYUlTVE9Rem45SUk ]]
+
| [[Image:Chipmunks Mid-term-slides.png|130px|link=https://drive.google.com/open?id=0BzxXlDDPiCKfVkl3cHdjUkk0ODQ ]]
| [[Image:Chipmunks Deployed-site.png|130px|link=https://drive.google.com/open?id=0BzxXlDDPiCKfS2ZZRE5nS0NjVjg]]
+
| [[Image:Chipmunks Deployed-site.png|130px|link=https://www.dropbox.com/s/7eykxkgyv8kztrk/Finals%20Presentation%20Deployment%20Details.docx?dl=0]]
 
|}
 
|}
 
</div></center>
 
</div></center>
Line 66: Line 66:
 
===<div style="background: #0077B5; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:18px; font-family:helvetica"><font color= #FFFFFF>Project Highlights  </font></div>===
 
===<div style="background: #0077B5; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:18px; font-family:helvetica"><font color= #FFFFFF>Project Highlights  </font></div>===
 
<br>
 
<br>
[[Image: Chipmunks Project Highlights.png|center|800px]]
+
[[Image: Chipmunks Project Highlights.png|center|1000px]]
 
<br/>
 
<br/>
  
Line 85: Line 85:
 
Team Chipmunks makes use of the following 3 metrics to enable us to be more effective in project planning. Of the 3 metrics, the team introduced the Workload Metric to monitor individual focus segments on a per iteration basis.
 
Team Chipmunks makes use of the following 3 metrics to enable us to be more effective in project planning. Of the 3 metrics, the team introduced the Workload Metric to monitor individual focus segments on a per iteration basis.
 
<br>  
 
<br>  
*Workload Metrics – The objective of this metric is to ensure that no single segment gets overwhelmed. You might have noticed that we labelled ‘Graphing’ as one of our segments! This is because our application has a pretty strong focus on frontend technologies and visualization. Hence, we made the split to segregate responsibilities for greater trackability. <br>
+
*Workload Metrics – The objective of this metric is to view quantity of hours spent on particular segments, and then preempt if more people need to work on a particular segment (given that they have the appropriate skill set required). You might have noticed that we labelled ‘Graphing’ as one of our segments! This is because our application has a pretty strong focus on frontend technologies and visualization. Hence, we made the split to segregate responsibilities for greater trackability. <br>
  
  
Line 111: Line 111:
 
Usability – StockParser focuses on visualization of information. Hence it is necessary for the visualizations to be mobile responsive on various resolutions. While our chosen library D3.js allowed us to have great degree of customization, there were no ready-made codes to handle mobile responsiveness. Furthermore, our visualizations go beyond the standard set of a single graph. Hence, multiple tweaks were required to handle multiple visualizations [graphs on graphs] along a single row, responsiveness across multiple <div> tags and upon screen resizing.
 
Usability – StockParser focuses on visualization of information. Hence it is necessary for the visualizations to be mobile responsive on various resolutions. While our chosen library D3.js allowed us to have great degree of customization, there were no ready-made codes to handle mobile responsiveness. Furthermore, our visualizations go beyond the standard set of a single graph. Hence, multiple tweaks were required to handle multiple visualizations [graphs on graphs] along a single row, responsiveness across multiple <div> tags and upon screen resizing.
 
<br/>
 
<br/>
[[Image:Chipmunks Midterm Scaling.png|center|900px]]
+
[[Image:Chipmunks Finals Scaling.png|center|900px]]
 
<br/>
 
<br/>
  
Line 149: Line 149:
 
|| [[IS480 Team wiki: 2015T1 Chipmunks Documentation#Use Case | Use Case]]
 
|| [[IS480 Team wiki: 2015T1 Chipmunks Documentation#Use Case | Use Case]]
 
|-
 
|-
|| [[IS480 Team wiki: 2015T1 Chipmunks Documentation#Technology Interactions | Tech & System Architecture]]
+
|| [[IS480 Team wiki: 2015T1 Chipmunks Documentation#Technology Interactions | Tech, Infra & System Architecture]]
 
|-
 
|-
 
|| [https://drive.google.com/open?id=0B5TLE_R6Vwj3Q29PUTNPYTRFd2M Logical Diagram]
 
|| [https://drive.google.com/open?id=0B5TLE_R6Vwj3Q29PUTNPYTRFd2M Logical Diagram]

Latest revision as of 13:58, 2 December 2015

Team Chipmunks Logo.png


Team Chipmunks Icon Home.png   HOME

 

Team Chipmunks Icon AboutUs.png   ABOUT US

 

Team Chipmunks Icon Overview.png   PROJECT OVERVIEW

 

Team Chipmunks Icon ProjectManagement.png   PROJECT MANAGEMENT

 

Team Chipmunks Icon Documentation.png   DOCUMENTATION

 

Chipmunks FinalsWiki Title.png

Project Progress Summary

Chipmunks Finals Dashboard v2.png


Finals Slides Deployed Site
Chipmunks Mid-term-slides.png Chipmunks Deployed-site.png


Project Highlights


Chipmunks Project Highlights.png


Project Management

Project Status


Chipmunks Finals Project Status.png

Planned Project Schedule

Chipmunks Midterms Planned Schedule.png

Actual Project Schedule

Chipmunks Finals Actual Schedule.png


Project Metrics

Team Chipmunks makes use of the following 3 metrics to enable us to be more effective in project planning. Of the 3 metrics, the team introduced the Workload Metric to monitor individual focus segments on a per iteration basis.

  • Workload Metrics – The objective of this metric is to view quantity of hours spent on particular segments, and then preempt if more people need to work on a particular segment (given that they have the appropriate skill set required). You might have noticed that we labelled ‘Graphing’ as one of our segments! This is because our application has a pretty strong focus on frontend technologies and visualization. Hence, we made the split to segregate responsibilities for greater trackability.


Chipmunks Workload Metrics Finals.pngChipmunks Schedule Metrics Finals.png


Chipmunks Midterm Bug Metrics2.png

Project Risks

From Acceptance, Team Chipmunks’ top 2 concerns were 1) unfamiliarity with the technologies and 2) inefficient allocation of resources. These concerns were allayed as the team became proficient in their own roles and technical competencies. The other 2 risks identified which took the center stage till Mid-Terms were the need for deeper domain knowledge and scope creep. Domain knowledge came in form of 1) understanding the project domain and requirements and 2) translating these requirements into codes. It was later discovered that several functionalities require us to have deep knowledge in the finance and statistics area. The team also experienced requirements churn, which was identified as one of our medium risks.

Chipmunks Midterm Risks.png

Quality of product

Quality Attributes of the System
Performance – Team Chipmunks had testers which reported slowness when navigating through our website. Hence, the team did File Minification using Grunt to compress JavaScript and CSS files to reduce file size and HTTP requests. This reduces the fetch times of these resources. Additionally, Team Chipmunks enabled browser caching to optimize load times upon repeated visits.

Chipmunks Midterms Minification.png


Chipmunks Midterms Caching.png


Chipmunks Midterms Performance Results.png


Usability – StockParser focuses on visualization of information. Hence it is necessary for the visualizations to be mobile responsive on various resolutions. While our chosen library D3.js allowed us to have great degree of customization, there were no ready-made codes to handle mobile responsiveness. Furthermore, our visualizations go beyond the standard set of a single graph. Hence, multiple tweaks were required to handle multiple visualizations [graphs on graphs] along a single row, responsiveness across multiple

tags and upon screen resizing.


Chipmunks Finals Scaling.png


Technical Complexity


Upon the Sponsor's request, the documentation, screenshots and visualizations for our Technical Complexity is hosted on our private Google Drive here

Intermediate Deliverables

Topic of Interest Link
Project Management Minutes
Metrics
Risk Management
Change Management
Project Overview Project Overview
Team's Motivation
Pitch Video
Poster
Project Documentation Use Case
Tech, Infra & System Architecture
Logical Diagram
Choice of Technologies
Testing Testing Documentation

Testing


Internal Testing.png
Team Chipmunks - User Test Final.png


For testing results, assess here:

Chipmunks UT1 Icon.png     Chipmunks UT2 Icon.png     Chipmunks LT1 Icon.png     Chipmunks ut3 icon.png


Reflections


Team Reflections

This journey has been a tough but fulfilling one for Team Chipmunks. Collectively, the Chipmunks have gelled together, learning each other’s strengths and weaknesses and are proficient in complementing each other’s working style. We focused on constant communication, knowledge sharing and quantitative objectives in goal setting to help us move quickly and effectively as a team.


Individual Reflections


Chipmunks Midterm Reflections.png

Sponsor's Comment


Team Chipmunks - Sponsor Comment.png