Difference between revisions of "IS480 Team wiki: 2016T1 Charlies Angels FinalWiki"
Xwzheng.2014 (talk | contribs) |
Xwzheng.2014 (talk | contribs) |
||
Line 86: | Line 86: | ||
<div style="font-family: Seravek;"> | <div style="font-family: Seravek;"> | ||
− | For more information on how the team tabulates the score for each component, please refer to the following page on our Wiki: [[IS480 Team wiki: 2016T1 Charlies Angels Metrics|Charlies Angels Metrics]] | + | For more information on how the team tabulates the score for each component, please refer to the following page on our Wiki: [[IS480 Team wiki: 2016T1 Charlies Angels Metrics|Charlies Angels Metrics]]<br/> |
+ | Team Charlies Angels is pleased to share that on the whole, there has <b>not been</b> major lapse(s) in our project metrics. And the team has managed to successfully steer in the right direction despite the <b>high technical and business complexity</b> the team faced in the course of this project. | ||
</div> | </div> | ||
<br/> | <br/> |
Revision as of 09:06, 14 November 2016
Main Wiki | Midterm Wiki | Final Wiki |
Project Progress Summary
*Note: Access to Poster and Pitch Video requires SMU-Gmail Login to View
Project Highlights
Project Challenges
Project Achievements
Project Management
Project Status
Project Schedule (Plan vs. Actual)
Planned Project Schedule
Actual Project Schedule
Project Metrics
For more information on how the team tabulates the score for each component, please refer to the following page on our Wiki: Charlies Angels Metrics
Team Charlies Angels is pleased to share that on the whole, there has not been major lapse(s) in our project metrics. And the team has managed to successfully steer in the right direction despite the high technical and business complexity the team faced in the course of this project.
Project Risks
Due to the nature of our application, Team Charlies Angels has been proactively monitoring our efforts to mitigate risk(s). We would like to highlight the top two risks that our project is facing since the mid-terms presentation, the details are found in table below:
Current Risks that may affect the team:
S/N | RISK TYPE | RISK DESCRIPTION | LIKELIHOOD | SEVERITY | CATEGORY | MITIGATION |
---|---|---|---|---|---|---|
9. | Technology Risk | The recent acquisition of Yahoo by Verizon poses an imminent threat to the existence of the Yahoo API where the team utilises to call for its financial information. | Probable | Critical | Unacceptable | The team has identified that Yahoo would close the service only in 2017. However, in the event that the service is closed during the phase of development, the purchase of a paid API is absolutely necessary. In the event of this purchase, the team would propose the drop of all functions happening thereafter, and focus on the fetch of data as it is essentially what makes the application. A list of websites have been provided to the client as alternate sources for varying financial data information:
|
10. | Technology Risk | As the application is utilising web crawling patterns, this aspect is subjected heavily on the patterns that are used on the host(s) which we crawl the data from. | Probable | Critical | Unacceptable | The team has come up with mitigation plans to have two possible steps to take. The first choice would be to proceed to find an alternative website that displays the essential information that we require and proceed to crawl from there. Should the former step fail, we would proceed to consult our client, and proceed to make a purchase for paid API for financial data. In the event of this purchase, the team would propose the drop of all functions happening thereafter, and focus on the fetch of data as it is essentially what makes the application. |