Difference between revisions of "IS480 Team wiki: 2012T1 Twee-ta-doo Tweetadoo Midterm"
(42 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | <div style="min-width: 980px; max-width: | + | <div style="min-width: 980px; max-width: 1280px"> |
− | + | <div id="header_image" style="width:980px; height:360px; margin: 0 auto; overflow:hidden; float:center"><div style="display:block; margin-top:-15%">[[Image:Tweetadoo_Header_Image.png|980px]]</div></div> | |
− | <div id="header_image" style="width:980px; height:360px; margin: 0 auto; overflow:hidden;"><div style="display:block; margin-top:-15%">[[Image:Tweetadoo_Header_Image.png|980px]]</div></div> | + | |
− | < | + | <div id="nav-bar" style="width: 1150px; height: 40px; margin: 0 auto 30px auto; float:center; left:60px; border:10px dashed #71B3F5"> |
+ | <ul style="list-style:none; font-size: 120%; letter-spacing:3px"> | ||
+ | <li style="float: left">[[IS480 Team wiki: 2012T1 Twee-ta-doo|Home]]</li> | ||
+ | <li style="float: left; padding: 0 5px 0 5px; " > | </li> | ||
+ | <li style="float: left;">[[IS480 Team wiki: 2012T1 Twee-ta-doo The Team|Team]]</li> | ||
+ | <li style="float: left; padding: 0 5px 0 5px; " > | </li> | ||
+ | <li style="float: left;">[[IS480 Team wiki: 2012T1 Twee-ta-doo The Stakeholders|Stakeholders]]</li> | ||
+ | <li style="float: left; padding: 0 5px 0 5px; " > | </li> | ||
+ | <li style="float: left;">[[IS480 Team wiki: 2012T1 Twee-ta-doo The Project|Project Management]]</li> | ||
+ | <li style="float: left; padding: 0 5px 0 5px; " > | </li> | ||
+ | <li style="float: left;">[[IS480 Team wiki: 2012T1 Twee-ta-doo The Scope|Scope]]</li> | ||
+ | <li style="float: left; padding: 0 5px 0 5px; " > | </li> | ||
+ | <li style="float: left;">[[IS480 Team wiki: 2012T1 Twee-ta-doo The Application|UI Mockup]]</li> | ||
+ | <li style="float: left; padding: 0 5px 0 5px; " > | </li> | ||
+ | <li style="float: left;">[[IS480 Team wiki: 2012T1 Twee-ta-doo The Technology|Technology]]</li> | ||
+ | <li style="float: left; padding: 0 5px 0 5px; " > | </li> | ||
+ | <li style="float: left;">[[IS480 Team wiki: 2012T1 Twee-ta-doo User Testing|User Testing]]</li> | ||
+ | <li style="float: left; padding: 0 5px 0 5px; " > | </li> | ||
+ | <li style="float: left;">[[IS480 Team wiki: 2012T1 Twee-ta-doo Presentation Slides|Presentation Slides]]</li> | ||
+ | </ul> | ||
+ | </div> | ||
− | <div id="nav-bar" style="width: 700px; height: 60px; margin: 0 auto 30px auto; | + | <div id="nav-bar" style="width: 700px; height: 60px; margin: 0 auto 30px auto; left:60px; border:10px dashed #71B3F5"> |
− | < | + | <p style="font-size:2.5em; font-weight:bold; color:black; text-align:center; margin: -4px 0px;">Tweetadoo's Midterm Progress</p> |
− | |||
</div> | </div> | ||
− | < | + | <p style="font-size:1.3em; font-weight:bold; color:#4861A0">[[IS480 Team wiki: 2012T1 Twee-ta-doo |Back to Tweetadoo Page]]</p> |
<p> </p> | <p> </p> | ||
+ | Midterm Slides: [[Media:Tweetadoo_FinalMidterm.pdf|Midterm]] | ||
+ | |||
+ | <p style="font-size: 2.0em; color:#4863A0; font-weight: bold">OVERVIEW:</p> | ||
− | |||
− | |||
<p>Tweetadoo is currently in our 6th iteration.</p> | <p>Tweetadoo is currently in our 6th iteration.</p> | ||
− | <p | + | <p>Listed are some of the the key accomplishment that we have achieved due 1 October 2012:</p> |
<p>• We managed to develop an Ipad application which is based on Objective C - a language we were not taught before </p> | <p>• We managed to develop an Ipad application which is based on Objective C - a language we were not taught before </p> | ||
<p>• We have gathered favourable and userful results from our user testing which comprises of 40 testers conducted on 24, 26 September 2012. </p> | <p>• We have gathered favourable and userful results from our user testing which comprises of 40 testers conducted on 24, 26 September 2012. </p> | ||
− | <p>• We were on schedule despite having faced with some difficulties while coding the | + | <p>• We were on schedule despite having faced with some difficulties while coding the web service and integrating the web service with the iPad application. </p> |
− | <p>< | + | <p><strong>We are confident of completing the project to upload the application to the App Store successfully. </strong></p> |
<p> </p> | <p> </p> | ||
− | < | + | |
− | < | + | <p style="font-size: 2.0em; color:#4863A0; font-weight: bold">1 PROJECT HIGHLIGHTS:</p> |
− | + | <p style="font-size: 1.1em"> Unexpected Happenings:</p> | |
− | <p>• < | + | <p>• <strong> Scope Changes: </strong> </p> |
<p>Added - Webservice (coding ourselves), Retweet/ Mention/ Follow, Database functionality. </p> | <p>Added - Webservice (coding ourselves), Retweet/ Mention/ Follow, Database functionality. </p> | ||
<p>Remove - Badges Award System, Trending Topics, Settings Page functionality </p> | <p>Remove - Badges Award System, Trending Topics, Settings Page functionality </p> | ||
− | <p>• < | + | <p>• <strong> Time Constraint: </strong> </p> |
<p>Learning of objective C language took longer than the designated 3 months</p> | <p>Learning of objective C language took longer than the designated 3 months</p> | ||
− | <p> | + | <p>More time is placed in the development of the webservices and the understanding of backend data, thus we have to shift our focus from the front-end to the back-end too.</p> |
− | <p>• < | + | <p>• <strong> Technical Difficulties: </strong> </p> |
− | <p>Data scrapping to extract and display images, and titles on the newsfeed</p | + | <p>Data scrapping to extract and display images, and titles on the newsfeed</p> |
<p> </p> | <p> </p> | ||
− | < | + | <p style="font-size: 2.0em; color:#4863A0; font-weight: bold">2 PROJECT MANAGEMENT:</p> |
− | <p> | + | <p style="font-size: 1.4em; color:#98B0D2; font-weight: bold">Project Timeline:</p> |
+ | [[Image:Klique_Schedule_Diagram.jpg|700px|center]] | ||
− | < | + | <p style="font-size: 1.4em; color:#98B0D2; font-weight: bold">2.1 Project Status:</p> |
− | + | <p><strong> Overall Completion Status: 70% </strong></p> | |
− | + | <p><strong> Overall Confidence Level of app deploying to App Store: 100%</strong></p> | |
<p> </p> | <p> </p> | ||
− | <table | + | <table style="border: 3px solid black; border-collapse: collapse; background-color: white; text-align: center; font-family: 'Arial'; min-width: 700px; max-width: 1000px"> |
− | <tr | + | <tr style="border: 1px solid black"> |
− | < | + | <th style="border: 1px solid black; font-weight: bold">Task/ Function/ Features, etc</th> |
− | < | + | <th style="border: 1px solid black; font-weight: bold">Status</th> |
− | <td | + | <th style="border: 1px solid black; font-weight: bold">Confident Level (0-1)</th> |
− | <td | + | <th style="border: 1px solid black; font-weight: bold">Comments</th> |
− | </ | + | </tr> |
− | + | <tr style="border: 1px solid black"> | |
− | <td | + | <td style="border: 1px solid black; width: 31%; background-color: #18C4AD; font-weight: bold; text-align: left">Twitter Single Sign on</td> |
− | < | + | <td style="border: 1px solid black; width: 15%;">Fully deployed and tested <br />100% Function Completed</td> |
− | </td> | + | <td style="border: 1px solid black; width: 8%;">1</td> |
− | <td | + | <td style="border: 1px solid black; width: 46%;text-align: left">Completed before acceptance</td> |
− | + | </tr> | |
− | </td> | + | <tr style="border: 1px solid black"> |
− | <td | + | <td style="border: 1px solid black; width: 31%; background-color: #18C4AD; font-weight: bold; text-align: left">Registration</td> |
− | + | <td style="border: 1px solid black; width: 15%;">Fully deployed and tested <br />100% Function Completed</td> | |
− | </td> | + | <td style="border: 1px solid black; width: 8%;">1</td> |
− | <td | + | <td style="border: 1px solid black; width: 46%;text-align: left">Completed before acceptance</td> |
− | + | </tr> | |
− | </td> | + | <tr style="border: 1px solid black"> |
− | </tr> | + | <td style="border: 1px solid black; width: 31%; background-color: #18C4AD; font-weight: bold; text-align: left">Display of Friend List</td> |
− | <tr> | + | <td style="border: 1px solid black; width: 15%;">Fully deployed and tested <br />100% Function Completed</td> |
− | <td | + | <td style="border: 1px solid black; width: 8%;">1</td> |
− | < | + | <td style="border: 1px solid black; width: 46%;text-align: left">Completed before acceptance</td> |
− | </td> | + | </tr> |
− | <td | + | <tr style="border: 1px solid black"> |
− | < | + | <td style="border: 1px solid black; width: 31%; background-color: #18C4AD; font-weight: bold; text-align: left">Terms and Conditions</td> |
− | + | <td style="border: 1px solid black; width: 15%;">Fully deployed and tested <br />90% Function Completed</td> | |
− | <td | + | <td style="border: 1px solid black; width: 8%;">1</td> |
− | + | <td style="border: 1px solid black; width: 46%;text-align: left">Awaiting LARC to input the legalized terms and condition</td> | |
− | </td> | + | </tr> |
− | <td | + | <tr style="border: 1px solid black"> |
− | < | + | <td style="border: 1px solid black; width: 31%; background-color: #18C4AD; font-weight: bold; text-align: left">View Profile page</td> |
− | < | + | <td style="border: 1px solid black; width: 15%;">Fully deployed and tested <br />90% Function Completed</td> |
− | </ | + | <td style="border: 1px solid black; width: 8%;">1</td> |
− | + | <td style="border: 1px solid black; width: 46%;text-align: left">Removed Badges functionality</td> | |
− | <td | + | </tr> |
− | < | + | <tr style="border: 1px solid black"> |
− | </td> | + | <td style="border: 1px solid black; width: 31%; background-color: #18C4AD; font-weight: bold; text-align: left">Favourite/ Unfavourite Artiste</td> |
− | <td | + | <td style="border: 1px solid black; width: 15%;">Did Internal testing bit have not been deployed 90% <br />Awaiting deployment and approval from client</td> |
− | + | <td style="border: 1px solid black; width: 8%;">1</td> | |
− | </td> | + | <td style="border: 1px solid black; width: 46%;text-align: left">Need to deploy and do user testing</td> |
− | <td | + | </tr> |
− | < | + | <tr style="border: 1px solid black"> |
− | </ | + | <td style="border: 1px solid black; width: 31%; background-color: #18C4AD; font-weight: bold; text-align: left">Manage Newsfeed</td> |
− | < | + | <td style="border: 1px solid black; width: 15%;">Deployed and tested first version UI 50% <br /> |
− | < | + | Web service 50%</td> |
− | + | <td style="border: 1px solid black; width: 8%;">0.9</td> | |
− | < | + | <td style="border: 1px solid black; width: 46%;text-align: left"><p>Tweaking the application to accommodate changes from UT and client</p> |
− | < | + | <p>1. Handle slow loading (memory allocation for iPad) |
− | <td | + | <p>2. Content to display not only words but pictures and site headers related to the content (requires data extraction)</p> |
− | < | + | <p>3. Push 2. to display on iPad </p> |
− | </td> | + | <p>4. Implement Youtube extracted video thumbnail on iPad (backend extraction has been completed for Youtube)</p> |
− | <td | + | <p>5. Implement personalized tweets based on thumbs up and favourited artistes. (Displaying of Fav. Artistes feeds has been completed </p> |
− | + | <p>6. Need to implement algorithm to include even more personalization (4 functions -> thumbs up, view detailed view, mention and retweet</p></td> | |
− | + | </tr> | |
− | <td | + | <tr style="border: 1px solid black"> |
− | < | + | <td style="border: 1px solid black; width: 31%; background-color: #18C4AD; font-weight: bold; text-align: left">Thumbs Up</td> |
− | </ | + | <td style="border: 1px solid black; width: 15%;">Completed internal testings but have not been deployed<br/> |
− | < | + | Web Service 90% completed</td> |
− | < | + | <td style="border: 1px solid black; width: 8%;">1</td> |
− | < | + | <td style="border: 1px solid black; width: 46%;text-align: left"><p>Needs to be implemented on the iPad </p> |
− | + | <p>We have completed backend implementation and have done internal testing </p> | |
− | < | + | <p>Need to discuss with LARC to include the additional tables we have created for LARC</p> |
− | < | + | <p>Need to integrate both front and back end </p></td> |
− | + | </tr> | |
− | < | + | <tr style="border: 1px solid black"> |
− | <td | + | <td style="border: 1px solid black; width: 31%; background-color: #18C4AD; font-weight: bold; text-align: left">Manage Group</td> |
− | < | + | <td style="border: 1px solid black; width: 15%;">Not deployed and not tested<br/> |
− | </td> | + | Web Service 0% completed</td> |
− | <td | + | <td style="border: 1px solid black; width: 8%;">0.8</td> |
− | + | <td style="border: 1px solid black; width: 46%;text-align: left"><p>Only the UI part has been partially completed. </p> | |
− | </td> | + | <p>View (100%)</p> |
− | <td | + | <p>Create (100%)</p> |
− | < | + | <p>Delete (0%)</p> |
− | < | + | <p>Edit (0%)</p> |
− | </ | + | <p>Web service has not been implemented</p></td> |
− | < | + | </tr> |
− | + | <tr style="border: 1px solid black"> | |
− | < | + | <td style="border: 1px solid black; width: 31%; background-color: #18C4AD; font-weight: bold; text-align: left">Badges Award System</td> |
− | </ | + | <td style="border: 1px solid black; width: 15%;">Not deployed and not tested<br/> |
− | < | + | Web Service 0% completed</td> |
− | < | + | <td style="border: 1px solid black; width: 8%;">0.5</td> |
− | </td> | + | <td style="border: 1px solid black; width: 46%;text-align: left"><p>Functionality removed</p></td> |
− | <td | + | </tr> |
− | + | <tr style="border: 1px solid black"> | |
− | </td> | + | <td style="border: 1px solid black; width: 31%; background-color: #18C4AD; font-weight: bold; text-align: left">App Design</td> |
− | <td | + | <td style="border: 1px solid black; width: 15%;">100%</td> |
− | < | + | <td style="border: 1px solid black; width: 8%;">1</td> |
− | < | + | <td style="border: 1px solid black; width: 46%;text-align: left"><p>Keeping the current UI based on positive user feedbacks</p></td> |
− | + | </tr> | |
− | < | + | <tr style="border: 1px solid black"> |
− | < | + | <td style="border: 1px solid black; width: 31%; background-color: #18C4AD; font-weight: bold; text-align: left">Working on the user testing feedback</td> |
− | < | + | <td style="border: 1px solid black; width: 15%;">50%</td> |
− | < | + | <td style="border: 1px solid black; width: 8%;">0.8</td> |
− | < | + | <td style="border: 1px solid black; width: 46%;text-align: left"><p>We are consolidating the user feedbacks and resolving the critical issues on hand</p></td> |
− | < | + | </tr> |
− | |||
− | </td> | ||
− | <td | ||
− | < | ||
− | </ | ||
− | < | ||
− | < | ||
− | </td> | ||
− | < | ||
− | < | ||
− | <td | ||
− | < | ||
− | </ | ||
− | < | ||
− | < | ||
− | |||
− | </td> | ||
− | <td | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | < | ||
− | </td> | ||
− | </tr> | ||
</table> | </table> | ||
<p> </p> | <p> </p> | ||
− | < | + | <p style="font-size: 1.4em; color:#98B0D2; font-weight: bold">2.2 Project Schedule (Planned Vs Actual):</p> |
− | <p | + | <p style="font-weight: bold;"><u>Updates since Acceptance: </u></p> |
− | < | + | <p style="font-weight: bold;">Significant changes to scope:</p> |
− | |||
<p>• Change 1 : Added Webservice (coding ourselves) - Initial LARC was helping us with the coding webservice, however, we decided to code ourselves as we needed the webservices quickly so as to carry on with the development of our application.</p> | <p>• Change 1 : Added Webservice (coding ourselves) - Initial LARC was helping us with the coding webservice, however, we decided to code ourselves as we needed the webservices quickly so as to carry on with the development of our application.</p> | ||
<p>• Change 2 : Added Retweet/ Mention/ Follow Functionalities - As our application was closely linked with Twitter, our client suggested that he would like the users to be able to do some twitter functions on our app</p> | <p>• Change 2 : Added Retweet/ Mention/ Follow Functionalities - As our application was closely linked with Twitter, our client suggested that he would like the users to be able to do some twitter functions on our app</p> | ||
Line 264: | Line 170: | ||
<p>• Change 5 : Removed Trending Topics - We removed it as the application crawls only twitter and youtube feeds</p> | <p>• Change 5 : Removed Trending Topics - We removed it as the application crawls only twitter and youtube feeds</p> | ||
<p>• Change 6 : Removed Settings - We removed it as the the application would be relying on the user's app interaction to display the relevant tweets</p> | <p>• Change 6 : Removed Settings - We removed it as the the application would be relying on the user's app interaction to display the relevant tweets</p> | ||
+ | <p> </p> | ||
Refer to : [[Media:Tweetadoo_ActualVsPlannedSchedule2.pdf|Schedule Actual Vs Planned]] | Refer to : [[Media:Tweetadoo_ActualVsPlannedSchedule2.pdf|Schedule Actual Vs Planned]] | ||
− | + | ||
− | <table | + | <table style="border: 3px solid black; border-collapse: collapse; background-color: white; text-align: center; font-family: 'Arial'; min-width: 700px; max-width: 1000px"> |
− | <tr | + | <tr> |
− | <td>[[Image:Tweetadoo_Scope_Acceptance.jpg|center]]</td> | + | <td style="border: 1px solid black; width: 50%;">[[Image:Tweetadoo_Scope_Acceptance.jpg|500px|center]]</td> |
− | <td>[[Image:Tweetadoo_Scope_Midterm.JPG|center]]</td> | + | <td style="border: 1px solid black; width: 50%">[[Image:Tweetadoo_Scope_Midterm.JPG|500px|center]]</td> |
+ | </tr> | ||
</table> | </table> | ||
<p> </p> | <p> </p> | ||
− | < | + | <p style="font-size: 1.4em; color:#98B0D2; font-weight: bold">2.3 Project Metric:</p> |
− | <p | + | <p style="font-weight: bold"> Schedule Metric: </p> |
− | |||
<p> </p> | <p> </p> | ||
− | <p>< | + | [[Image:Klique_ScheduleCalculation.jpg|700px|center]] |
+ | <p>Please refer to: [[IS480 Team wiki: 2012T1 Twee-ta-doo The Project#milestones|Schedule Metric]] for the project metrics</p> | ||
+ | <p> </p> | ||
+ | <p style="font-weight: bold"> Bug Metric:</p> | ||
[[Image:Tweetadoo_Bug_Diagram.png|800px|center]] | [[Image:Tweetadoo_Bug_Diagram.png|800px|center]] | ||
+ | [[Image:Klique_BugList2.JPG|1000px|center]] | ||
<p> </p> | <p> </p> | ||
− | < | + | <p style="font-size: 1.4em; color:#98B0D2; font-weight: bold">2.4 Project Risks:</p> |
− | <table | + | <table style="border: 3px solid black; border-collapse: collapse; background-color: white; text-align: center; font-family: 'Arial'; min-width: 700px; max-width: 1000px"> |
− | <tr | + | <tr style="border: 1px solid black;"> |
− | < | + | <th style="border: 1px solid black;font-weight: bold"> Risk</th> |
− | < | + | <th style="border: 1px solid black;font-weight: bold"> Probability</th> |
− | < | + | <th style="border: 1px solid black;font-weight: bold"> Impact</th> |
− | < | + | <th style="border: 1px solid black;font-weight: bold"> Mitigation</th> |
− | </tr> | + | <th style="border: 1px solid black;font-weight: bold"> Status</th> |
− | <tr> | + | </tr> |
− | <td | + | <tr style="border: 1px solid black;"> |
− | + | <td style="width: 20%; background-color:#18C4AD; font-weight: bold; border: 1px solid black; text-align: left">LARC server down</td> | |
− | </td> | + | <td style="width: 10%; border: 1px solid black;">Low</td> |
− | <td | + | <td style="width: 10%; border: 1px solid black;">High</td> |
− | + | <td style="width: 30%; border: 1px solid black;text-align: left">Setting up of alternate server with a set up similar to that of LARC's server which includes a snapshot of their database</td> | |
− | </td> | + | <td style="width: 30%; border: 1px solid black;text-align: left">Occured, followed Mitigation plan</td> |
− | <td | + | </tr> |
− | + | <tr style="border: 1px solid black;"> | |
− | </td> | + | <td style="width: 20%; background-color:#18C4AD; font-weight: bold; border: 1px solid black; text-align: left">Application not accepted by app store in time for final presentation</td> |
− | <td | + | <td style="width: 10%; border: 1px solid black;">High</td> |
− | + | <td style="width: 10%; border: 1px solid black;">High</td> | |
− | </td> | + | <td style="width: 30%; border: 1px solid black;text-align: left">Deploy a working but incomplete application early for review by App Store and continue development of the final application with inputs return from App Store</td> |
− | </tr> | + | <td style="width: 30%; border: 1px solid black;text-align: left">Did not occur</td> |
− | <tr> | + | </tr> |
− | <td | + | <tr style="border: 1px solid black;"> |
− | + | <td style="width: 20%; background-color:#18C4AD; font-weight: bold; border: 1px solid black; text-align: left">Increase of scope due to unforeseen technical difficulties</td> | |
− | </td> | + | <td style="width: 10%; border: 1px solid black;">Medium</td> |
− | <td | + | <td style="width: 10%; border: 1px solid black;">Medium</td> |
− | + | <td style="width: 30%; border: 1px solid black;text-align: left">Evaluation of current functionalities and schedules to see if the additional scope is workable with the current functionalities and thus, evaluate if we need to drop a function or 2.</td> | |
− | </td> | + | <td style="width: 30%; border: 1px solid black;text-align: left">Followed Mitigation plan</td> |
− | <td | + | </tr> |
− | + | <tr style="border: 1px solid black;"> | |
− | </td> | + | <td style="width: 20%; background-color:#18C4AD; font-weight: bold; border: 1px solid black; text-align: left">Random crashes of ipad due to inefficient handling of memory</td> |
− | <td | + | <td style="width: 10%; border: 1px solid black;">High</td> |
− | + | <td style="width: 10%; border: 1px solid black;">High</td> | |
− | </td> | + | <td style="width: 30%; border: 1px solid black;text-align: left">Release the memory as soon as the function is closed (km)</td> |
− | </tr> | + | <td style="width: 30%; border: 1px solid black;text-align: left">Followed Mitigation plan</td> |
− | <tr> | + | </tr> |
− | <td | + | <tr style="border: 1px solid black;"> |
− | + | <td style="width: 20%; background-color:#18C4AD; font-weight: bold; border: 1px solid black; text-align: left">IOS 6 compatability issues</td> | |
− | </td> | + | <td style="width: 10%; border: 1px solid black;">High</td> |
− | <td | + | <td style="width: 10%; border: 1px solid black;">High</td> |
− | + | <td style="width: 30%; border: 1px solid black;text-align: left">Ensure that XCode 4.5 is installed and used the framework provided by IOS.</td> | |
− | </td> | + | <td style="width: 30%; border: 1px solid black;text-align: left">Occured. Installed XCode 4.5 and ensured compatability by replacing keywords used in IOS.</td> |
− | <td | + | </tr> |
− | |||
− | </td> | ||
− | <td | ||
− | |||
− | </td> | ||
− | </tr> | ||
− | <tr> | ||
− | <td | ||
− | |||
− | </td> | ||
− | <td | ||
− | < | ||
− | </ | ||
− | < | ||
− | < | ||
− | </td> | ||
− | <td | ||
− | < | ||
− | </td> | ||
− | </tr> | ||
</table> | </table> | ||
<p> </p> | <p> </p> | ||
− | < | + | <p style="font-size: 1.4em; color:#98B0D2; font-weight: bold">2.5 Technical Complexities:</p> |
− | <table | + | <table style="border: 3px solid black; border-collapse: collapse; background-color: white; text-align: left; font-family: 'Arial'; min-width: 700px; max-width: 1000px"> |
− | <tr | + | <tr style="border: 1px solid black; text-align: center;"> |
− | < | + | <th style="border: 1px solid black; font-weight: bold"> Technical Complexities</th> |
− | < | + | <th style="border: 1px solid black; font-weight: bold"> Description</th> |
− | </tr> | + | </tr> |
− | <tr> | + | <tr style="border: 1px solid black;"> |
− | <td | + | <td style="border: 1px solid black; width: 50%; background-color: #18C4AD; font-weight: bold">Deploying app to ipad using objective C</td> |
− | + | <td style="border: 1px solid black; width: 50%; background-color: #18C4AD; font-weight: bold">Deploying app to ipad using objective C</td> | |
− | </td> | + | </tr> |
− | <td | + | <tr style="border: 1px solid black;"> |
− | + | <td style="border: 1px solid black; width: 50%; background-color: #2886c4; font-weight: bold">Creating of webservices</td> | |
− | </td> | + | <td style="border: 1px solid black; width: 50%; background-color: #2886c4; font-weight: bold">Using Memcache as a workaround to slow connection for mysql server</td> |
− | </tr> | + | </tr> |
− | <tr> | + | <tr style="border: 1px solid black;"> |
− | <td | + | <td style="border: 1px solid black; width: 50%; background-color: #18C4AD; font-weight: bold">Content scrapping</td> |
− | + | <td style="border: 1px solid black; width: 50%; background-color: #18C4AD; font-weight: bold">Scrapping has to be tune to individual websites</td> | |
− | </td> | + | </tr> |
− | <td | + | <tr style="border: 1px solid black;"> |
− | + | <td style="border: 1px solid black; width: 50%; background-color: #2886c4; font-weight: bold">Adapting our current system (webservice and IOS application) to fit the client's system (database and memcache)</td> | |
− | </td> | + | <td style="border: 1px solid black; width: 50%; background-color: #2886c4; font-weight: bold">We have to understand how to store the data in our mysql and to adapt our webservices to compliment our webservices with the client's database. Client's database is not in 3rd normal form that we learnt in our dm module, hence we need to explore how the data is being stored.</td> |
− | </tr> | + | </tr> |
− | <tr> | + | <tr style="border: 1px solid black;"> |
− | <td | + | <td style="border: 1px solid black; width: 50%; background-color: #18C4AD; font-weight: bold">Heavy use of MVC model to push specific views for display to the ipad</td> |
− | + | <td style="border: 1px solid black; width: 50%; background-color: #18C4AD; font-weight: bold">NIL</td> | |
− | </td> | + | </tr> |
− | <td | + | </table> |
− | |||
− | </td> | ||
− | </tr> | ||
− | <tr> | ||
− | <td | ||
− | |||
− | </td> | ||
− | <td | ||
− | |||
− | </td> | ||
− | </tr> | ||
− | <tr> | ||
− | <td | ||
− | |||
− | </td> | ||
− | <td | ||
− | |||
− | </td> | ||
− | </tr> | ||
− | </table> | ||
<p> </p> | <p> </p> | ||
− | < | + | <p style="font-size: 2.0em; color:#4863A0; font-weight: bold">3 QUALITY OF PRODUCT</p> |
− | < | + | [[Image:Tweetadoo_QualityProduct.jpg|800px|center]] |
− | < | + | <p style="font-size: 1.4em; color:#98B0D2; font-weight: bold">3.1 Immediate Deliverables</p> |
− | < | + | <table style="border: 3px solid black; border-collapse: collapse; background-color: white; text-align: left; font-family: 'Arial'; min-width: 400px; max-width: 600px; margin: 0 auto"> |
+ | <tr style="border: 1px solid black; text-align: center; background-color: #18C4AD; font-weight: bold"> | ||
+ | <td style="width: 33%; border: 1px solid black">Stage</td> | ||
+ | <td style="width: 33%; border: 1px solid black">Specification</td> | ||
+ | <td style="width: 34%; border: 1px solid black">Modules</td> | ||
+ | </tr> | ||
+ | <tr style="border: 1px solid black;"> | ||
+ | <td style="width: 33%; border: 1px solid black" rowspan=2>Project Management</td> | ||
+ | <td style="width: 33%; border: 1px solid black">Minutes</td> | ||
+ | <td style="width: 34%; border: 1px solid black">[[IS480 Team wiki: 2012T1 Twee-ta-doo The Project#documentation|Minutes]]</td> | ||
+ | </tr> | ||
+ | <tr style="border: 1px solid black"> | ||
+ | <td style="width: 33%; border: 1px solid black">Metrics</td> | ||
+ | <td style="width: 34%; border: 1px solid black">Schedule and Bug Metrics</td> | ||
+ | </tr> | ||
+ | <tr style="border: 1px solid black"> | ||
+ | <td style="width: 33%; border: 1px solid black">Requirements</td> | ||
+ | <td style="width: 33%; border: 1px solid black">Storycards</td> | ||
+ | <td style="width: 34%; border: 1px solid black">[[IS480 Team wiki: 2012T1 Twee-ta-doo The Project|Project]]</td> | ||
+ | </tr> | ||
+ | <tr style="border: 1px solid black"> | ||
+ | <td style="width: 33%; border: 1px solid black" rowspan=2>Analysis</td> | ||
+ | <td style="width: 33%; border: 1px solid black">Usecase</td> | ||
+ | <td style="width: 34%; border: 1px solid black">[[IS480 Team wiki: 2012T1 Twee-ta-doo The Scope|Usecase]]</td> | ||
+ | </tr> | ||
+ | <tr style="border: 1px solid black"> | ||
+ | <td style="width: 33%; border: 1px solid black">App Screenshots</td> | ||
+ | <td style="width: 33%; border: 1px solid black">[[IS480 Team wiki: 2012T1 Twee-ta-doo The Application|App Screenshot]]</td> | ||
+ | </tr> | ||
+ | <tr style="border: 1px solid black"> | ||
+ | <td style="width: 33%; border: 1px solid black">Design</td> | ||
+ | <td style="width: 33%; border: 1px solid black">ER Diagram</td> | ||
+ | <td style="width: 33%; border: 1px solid black">[[Media:Klique_ER.png|ER Diagram]]</td> | ||
+ | </tr> | ||
+ | <tr style="border: 1px solid black"> | ||
+ | <td style="width: 33%; border: 1px solid black" rowspan=2>User Testing</td> | ||
+ | <td style="width: 33%; border: 1px solid black">User Guided Document</td> | ||
+ | <td style="width: 34%; border: 1px solid black">https://docs.google.com/file/d/0Bx-a0moKfQPXLUFUaXl0Zms4VkU/edit</td> | ||
+ | </tr> | ||
+ | <tr style="border: 1px solid black"> | ||
+ | <td style="width: 33%; border: 1px solid black">User Feedback form</td> | ||
+ | <td style="width: 34%; border: 1px solid black">https://docs.google.com/spreadsheet/viewform?formkey=dE1yamNaZWpKR1c0YTBLQW5KYjhibGc6MQ#gid=0</td> | ||
+ | </tr> | ||
+ | </table> | ||
− | <p | + | <p style="font-size: 1.4em; color:#98B0D2; font-weight: bold">3.2 Deployment</p> |
− | + | [[Image:Klique_Deployment Diagram.jpg|700px|center]] | |
− | [[Image:Klique_Deployment Diagram.jpg| | ||
− | <p | + | <p style="font-size: 1.4em; color:#98B0D2; font-weight: bold">3.3 Testing</p> |
− | + | <table style="border: 3px solid black; border-collapse: collapse; background-color: white; text-align: left; font-family: 'Arial'; min-width: 700px; max-width: 1000px; margin: 0 auto"> | |
− | <table | + | <tr style="border: 1px solid black; text-align: center; font-weight: bold"> |
− | <tr | + | <th> User Test Details</th> |
− | < | + | <th> Description</th> |
− | < | + | </tr> |
− | </tr> | + | <tr style="border: 1px solid black"> |
− | <tr> | + | <td style="border: 1px solid black; width: 30%; background-color: #18C4AD; font-weight: bold;">No. of user testing</td> |
− | <td | + | <td style="border: 1px solid black; width: 70%;">40</td> |
− | + | </tr> | |
− | </td> | + | <tr style="border: 1px solid black"> |
− | <td | + | <td style="border: 1px solid black; width: 30%; background-color: #18C4AD; font-weight: bold;">User Testing Dates</td> |
− | + | <td style="border: 1px solid black; width: 70%;">24 - 26 Sept (10 - 6pm), each session: 20 mins</td> | |
− | </td> | + | </tr> |
− | </tr> | + | <tr style="border: 1px solid black"> |
− | <tr> | + | <td style="border: 1px solid black; width: 30%; background-color: #18C4AD; font-weight: bold;">Tester Profile</td> |
− | <td | + | <td style="border: 1px solid black; width: 70%;">Testers are belonged to 3 categories: (i) kpop lovers & own twitter account, (ii) kpop lovers who do not own a twitter account, (iii) Non-kpop lovers & own twitter account |
− | + | <p><strong>Rationale: Guided Test - Act as Control Group</strong></p> | |
− | </td> | + | <p><b>Unguided Test - Act as Test Group</b></p> |
− | <td | + | <p> We wanted to find out if the user can use the app without guidance</p></td> |
− | + | </tr> | |
− | </td> | + | <tr style="border: 1px solid black"> |
− | </tr> | + | <td style="border: 1px solid black; width: 30%; background-color: #18C4AD; font-weight: bold;">Survey Questions</td> |
− | <tr> | + | <td style="border: 1px solid black; width: 70%;">https://docs.google.com/spreadsheet/viewform?formkey=dE1yamNaZWpKR1c0YTBLQW5KYjhibGc6MQ#gid=0</td> |
− | <td | + | </tr> |
− | + | <tr style="border: 1px solid black"> | |
− | </td> | + | <td style="border: 1px solid black; width: 30%; background-color: #18C4AD; font-weight: bold;">Guided Testing Document</td> |
− | <td | + | <td style="border: 1px solid black; width: 70%;">https://docs.google.com/file/d/0Bx-a0moKfQPXLUFUaXl0Zms4VkU/edit</td> |
− | + | </tr> | |
− | <p>< | + | <tr style="border: 1px solid black"> |
− | <p> Unguided Test - | + | <td style="border: 1px solid black; width: 30%; background-color: #18C4AD; font-weight: bold;">Survey Results</td> |
− | </td> | + | <td style="border: 1px solid black; width: 70%;"> |
− | </tr> | + | <p><strong> Feedback on app functionality: </strong> </p> |
− | <tr> | + | <p>• Navigation bar is too small</p> |
− | <td | + | <p>• too many empty spaces in newsfeed</p> |
− | + | <p>• can't find the back button </p> | |
− | </td> | + | <p>• cannot click on the artiste picture, had to click at the areas around the picture</p> |
− | <td | + | <p>• The retweet, mention buttons are not prominent position</p> |
− | + | <p>• didn't know what to do on the select favourite artiste page</p> | |
− | </td> | + | <p>• should have a select all artiste if he wants to choose all artistes</p> |
− | </tr> | + | <p><strong> Other features that the user might want to see: </strong> </p> |
− | <tr> | + | <p>• More information about favourite kpop groups and other artistes that you haven't heard of </p> |
− | <td | + | <p>• Translation </p> |
− | + | <p>• Customization of own profile background</p> | |
− | </td> | + | <p><strong> Are you satisfied with the app? </strong> </p> |
− | <td | + | <p>• More information about favourite kpop groups and other artistes that you haven't heard of </p> |
− | + | <p>•Personalised tweets </p> | |
− | </td> | + | <p>•Easy to use </p> |
− | </tr> | + | <p>•Comprehensive </p> |
− | <tr> | + | <p>•Intuitive UI </p> |
− | <td | + | <p><strong> Will you introduce the app to your friends? </strong> </p> |
− | + | <p>•find kpop artiste easily : easier to find the news</p> | |
− | </td> | + | <p>•nice design and intuitive layout that is easy to follow</p> |
− | <td | + | <p>•keep one updated to latest news</p> |
− | + | <p>•useful for catching up trends</p> | |
− | <p>< | + | <p>•interesting interacting with kpop fans</p> |
− | <p>• Navigation bar is too small</p> | + | <p>•makes sharing kpop stuff easier</p> |
− | <p>• too many empty spaces in newsfeed</p> | + | <p>•have not seen an app that combines with youtube</p> |
− | <p>• can't find the back button </p> | + | <p>•easy access to your favourite artistes</p> |
− | <p>• cannot click on the artiste picture, had to click at the areas around the picture</p> | + | <p>•make life easier as kpop fans</p> |
− | <p>• The retweet, mention buttons are not prominent position</p> | + | <p>•convenient</p> |
− | <p>• didn't know what to do on the select favourite artiste page</p> | + | <p>•frequent updates</p> |
− | <p>• should have a select all artiste if he wants to choose all artistes</p> | + | </td> |
− | <p>< | + | </tr> |
− | <p>• More information about favourite kpop groups and other artistes that you haven't heard of </p> | ||
− | <p>• Translation </p> | ||
− | <p>• Customization of own profile background</p> | ||
− | <p>< | ||
− | <p>• More information about favourite kpop groups and other artistes that you haven't heard of </p> | ||
− | <p>•Personalised tweets </p> | ||
− | <p>•Easy to use </p> | ||
− | <p>•Comprehensive </p> | ||
− | <p>•Intuitive UI </p> | ||
− | <p>< | ||
− | <p>•find kpop artiste easily : easier to find the news</p> | ||
− | <p>•nice design and intuitive layout that is easy to follow</p> | ||
− | <p>•keep one updated to latest news</p> | ||
− | <p>•useful for catching up trends</p> | ||
− | <p>•interesting interacting with kpop fans</p> | ||
− | <p>•makes sharing kpop stuff easier</p> | ||
− | <p>•have not seen an app that combines with youtube</p> | ||
− | <p>•easy access to your favourite artistes</p> | ||
− | <p>•make life easier as kpop fans</p> | ||
− | <p>•convenient</p> | ||
− | <p>•frequent updates</p> | ||
− | |||
− | |||
− | </td> | ||
− | </tr> | ||
</table> | </table> | ||
<p> </p> | <p> </p> | ||
− | + | <p style="font-size: 2.0em; color:#4863A0; font-weight: bold">4 REFLECTIONS</p> | |
− | < | + | <p style="font-size: 1.4em; color:#98B0D2; font-weight: bold">4.1 Team Reflection</p> |
− | <p | ||
− | |||
− | |||
<p>• We learn how to handle scope changes by breaking it down to manageable portions</p> | <p>• We learn how to handle scope changes by breaking it down to manageable portions</p> | ||
<p>• We learnt the importance of user testing because we realised that we were carried away by our application that we cannot see what the users see. </p> | <p>• We learnt the importance of user testing because we realised that we were carried away by our application that we cannot see what the users see. </p> | ||
Line 510: | Line 395: | ||
<p>• It is important for a team member to stand up and take charge if he feels that the team's discussion is going no where or if we are progressing in the wrong direction </p> | <p>• It is important for a team member to stand up and take charge if he feels that the team's discussion is going no where or if we are progressing in the wrong direction </p> | ||
<p>• It is important for the team to meet up with their client and supervisor regularly to keep them in the loop </p> | <p>• It is important for the team to meet up with their client and supervisor regularly to keep them in the loop </p> | ||
+ | </div> |
Latest revision as of 16:32, 28 November 2012
Midterm Slides: Midterm
OVERVIEW:
Tweetadoo is currently in our 6th iteration.
Listed are some of the the key accomplishment that we have achieved due 1 October 2012:
• We managed to develop an Ipad application which is based on Objective C - a language we were not taught before
• We have gathered favourable and userful results from our user testing which comprises of 40 testers conducted on 24, 26 September 2012.
• We were on schedule despite having faced with some difficulties while coding the web service and integrating the web service with the iPad application.
We are confident of completing the project to upload the application to the App Store successfully.
1 PROJECT HIGHLIGHTS:
Unexpected Happenings:
• Scope Changes:
Added - Webservice (coding ourselves), Retweet/ Mention/ Follow, Database functionality.
Remove - Badges Award System, Trending Topics, Settings Page functionality
• Time Constraint:
Learning of objective C language took longer than the designated 3 months
More time is placed in the development of the webservices and the understanding of backend data, thus we have to shift our focus from the front-end to the back-end too.
• Technical Difficulties:
Data scrapping to extract and display images, and titles on the newsfeed
2 PROJECT MANAGEMENT:
Project Timeline:
2.1 Project Status:
Overall Completion Status: 70%
Overall Confidence Level of app deploying to App Store: 100%
Task/ Function/ Features, etc | Status | Confident Level (0-1) | Comments |
---|---|---|---|
Twitter Single Sign on | Fully deployed and tested 100% Function Completed |
1 | Completed before acceptance |
Registration | Fully deployed and tested 100% Function Completed |
1 | Completed before acceptance |
Display of Friend List | Fully deployed and tested 100% Function Completed |
1 | Completed before acceptance |
Terms and Conditions | Fully deployed and tested 90% Function Completed |
1 | Awaiting LARC to input the legalized terms and condition |
View Profile page | Fully deployed and tested 90% Function Completed |
1 | Removed Badges functionality |
Favourite/ Unfavourite Artiste | Did Internal testing bit have not been deployed 90% Awaiting deployment and approval from client |
1 | Need to deploy and do user testing |
Manage Newsfeed | Deployed and tested first version UI 50% Web service 50% |
0.9 | Tweaking the application to accommodate changes from UT and client 1. Handle slow loading (memory allocation for iPad) 2. Content to display not only words but pictures and site headers related to the content (requires data extraction) 3. Push 2. to display on iPad 4. Implement Youtube extracted video thumbnail on iPad (backend extraction has been completed for Youtube) 5. Implement personalized tweets based on thumbs up and favourited artistes. (Displaying of Fav. Artistes feeds has been completed 6. Need to implement algorithm to include even more personalization (4 functions -> thumbs up, view detailed view, mention and retweet |
Thumbs Up | Completed internal testings but have not been deployed Web Service 90% completed |
1 | Needs to be implemented on the iPad We have completed backend implementation and have done internal testing Need to discuss with LARC to include the additional tables we have created for LARC Need to integrate both front and back end |
Manage Group | Not deployed and not tested Web Service 0% completed |
0.8 | Only the UI part has been partially completed. View (100%) Create (100%) Delete (0%) Edit (0%) Web service has not been implemented |
Badges Award System | Not deployed and not tested Web Service 0% completed |
0.5 | Functionality removed |
App Design | 100% | 1 | Keeping the current UI based on positive user feedbacks |
Working on the user testing feedback | 50% | 0.8 | We are consolidating the user feedbacks and resolving the critical issues on hand |
2.2 Project Schedule (Planned Vs Actual):
Updates since Acceptance:
Significant changes to scope:
• Change 1 : Added Webservice (coding ourselves) - Initial LARC was helping us with the coding webservice, however, we decided to code ourselves as we needed the webservices quickly so as to carry on with the development of our application.
• Change 2 : Added Retweet/ Mention/ Follow Functionalities - As our application was closely linked with Twitter, our client suggested that he would like the users to be able to do some twitter functions on our app
• Change 3 : Added database - We needed to implement a database to save data from LARC's server
• Change 4 : Removed Badges Award System - Our client wanted us to focus on the app's newsfeed functions and he felt that the badges functions would not be necessary and would consume some time implementing it
• Change 5 : Removed Trending Topics - We removed it as the application crawls only twitter and youtube feeds
• Change 6 : Removed Settings - We removed it as the the application would be relying on the user's app interaction to display the relevant tweets
Refer to : Schedule Actual Vs Planned
2.3 Project Metric:
Schedule Metric:
Please refer to: Schedule Metric for the project metrics
Bug Metric:
2.4 Project Risks:
Risk | Probability | Impact | Mitigation | Status |
---|---|---|---|---|
LARC server down | Low | High | Setting up of alternate server with a set up similar to that of LARC's server which includes a snapshot of their database | Occured, followed Mitigation plan |
Application not accepted by app store in time for final presentation | High | High | Deploy a working but incomplete application early for review by App Store and continue development of the final application with inputs return from App Store | Did not occur |
Increase of scope due to unforeseen technical difficulties | Medium | Medium | Evaluation of current functionalities and schedules to see if the additional scope is workable with the current functionalities and thus, evaluate if we need to drop a function or 2. | Followed Mitigation plan |
Random crashes of ipad due to inefficient handling of memory | High | High | Release the memory as soon as the function is closed (km) | Followed Mitigation plan |
IOS 6 compatability issues | High | High | Ensure that XCode 4.5 is installed and used the framework provided by IOS. | Occured. Installed XCode 4.5 and ensured compatability by replacing keywords used in IOS. |
2.5 Technical Complexities:
Technical Complexities | Description |
---|---|
Deploying app to ipad using objective C | Deploying app to ipad using objective C |
Creating of webservices | Using Memcache as a workaround to slow connection for mysql server |
Content scrapping | Scrapping has to be tune to individual websites |
Adapting our current system (webservice and IOS application) to fit the client's system (database and memcache) | We have to understand how to store the data in our mysql and to adapt our webservices to compliment our webservices with the client's database. Client's database is not in 3rd normal form that we learnt in our dm module, hence we need to explore how the data is being stored. |
Heavy use of MVC model to push specific views for display to the ipad | NIL |
3 QUALITY OF PRODUCT
3.1 Immediate Deliverables
Stage | Specification | Modules |
Project Management | Minutes | Minutes |
Metrics | Schedule and Bug Metrics | |
Requirements | Storycards | Project |
Analysis | Usecase | Usecase |
App Screenshots | App Screenshot | |
Design | ER Diagram | ER Diagram |
User Testing | User Guided Document | https://docs.google.com/file/d/0Bx-a0moKfQPXLUFUaXl0Zms4VkU/edit |
User Feedback form | https://docs.google.com/spreadsheet/viewform?formkey=dE1yamNaZWpKR1c0YTBLQW5KYjhibGc6MQ#gid=0 |
3.2 Deployment
3.3 Testing
User Test Details | Description |
---|---|
No. of user testing | 40 |
User Testing Dates | 24 - 26 Sept (10 - 6pm), each session: 20 mins |
Tester Profile | Testers are belonged to 3 categories: (i) kpop lovers & own twitter account, (ii) kpop lovers who do not own a twitter account, (iii) Non-kpop lovers & own twitter account
Rationale: Guided Test - Act as Control Group Unguided Test - Act as Test Group We wanted to find out if the user can use the app without guidance |
Survey Questions | https://docs.google.com/spreadsheet/viewform?formkey=dE1yamNaZWpKR1c0YTBLQW5KYjhibGc6MQ#gid=0 |
Guided Testing Document | https://docs.google.com/file/d/0Bx-a0moKfQPXLUFUaXl0Zms4VkU/edit |
Survey Results |
Feedback on app functionality: • Navigation bar is too small • too many empty spaces in newsfeed • can't find the back button • cannot click on the artiste picture, had to click at the areas around the picture • The retweet, mention buttons are not prominent position • didn't know what to do on the select favourite artiste page • should have a select all artiste if he wants to choose all artistes Other features that the user might want to see: • More information about favourite kpop groups and other artistes that you haven't heard of • Translation • Customization of own profile background Are you satisfied with the app? • More information about favourite kpop groups and other artistes that you haven't heard of •Personalised tweets •Easy to use •Comprehensive •Intuitive UI Will you introduce the app to your friends? •find kpop artiste easily : easier to find the news •nice design and intuitive layout that is easy to follow •keep one updated to latest news •useful for catching up trends •interesting interacting with kpop fans •makes sharing kpop stuff easier •have not seen an app that combines with youtube •easy access to your favourite artistes •make life easier as kpop fans •convenient •frequent updates |
4 REFLECTIONS
4.1 Team Reflection
• We learn how to handle scope changes by breaking it down to manageable portions
• We learnt the importance of user testing because we realised that we were carried away by our application that we cannot see what the users see.
• Team Planning and keeping one another updated is very crucial for the team's progress
• We have to strategise and ride on one another's strength to do a task efficiently
• It is important for a team member to stand up and take charge if he feels that the team's discussion is going no where or if we are progressing in the wrong direction
• It is important for the team to meet up with their client and supervisor regularly to keep them in the loop