Difference between revisions of "IS480 Team wiki: 2012T2 Succinq Final Wiki"
Blleong.2010 (talk | contribs) |
Blleong.2010 (talk | contribs) |
||
(4 intermediate revisions by the same user not shown) | |||
Line 15: | Line 15: | ||
*<b> View our Administrative Portal here: http://www.humaneity.com/mobileapp/</b> | *<b> View our Administrative Portal here: http://www.humaneity.com/mobileapp/</b> | ||
<br> | <br> | ||
− | *<b>Download our Final presentation slides [[Media:.pdf|here!]] </b> | + | *<b>Download our Final presentation slides [[Media:Succinq Final Presentation.pdf|here!]] </b> |
<br> | <br> | ||
Line 848: | Line 848: | ||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
<br> | <br> | ||
− | [[Image: | + | <center> '''Overall Team Reflection''' </center> |
+ | <br> | ||
+ | [[Image:team_succinq.jpg|center|800px]] | ||
+ | <br> | ||
+ | [[Image:reflection.png|center|600px]] |
Latest revision as of 13:24, 19 April 2013
Project Progress Summary
Immediate Deliverables
- Download the iOS Version through your mobile device: http://tinyurl.com/bvcfjnx, or search for "Humaneity" in the iTunes App Store on your iPhone.
- Download the Android Version from Google Play through your mobile device: http://tinyurl.com/bquc2jb, or search for "Humaneity" in the Google Play Store on your Android device.
- View our Administrative Portal here: http://www.humaneity.com/mobileapp/
- Download our Final presentation slides here!
Overview
Project Highlights
S/N | Issue Description | Mitigation Plan |
---|---|---|
1 | The rewards scheme functionality has been changed to Voice for a Cause functionality, where the user is able to sign in a petition for a cause put up by Humaneity. The user can choose to support or oppose the cause through a message or video. | The team feels that the difficulty level for both functions are similar, and thus has replaced the rewards scheme functionality which was to be completed in iteration 10 to the Voice for a Cause functionality in the schedule. Voices function was developed in iteration 12 as appose to iteration 10 as the team was still gathering requirements about the functionality. |
2 | The volunteer and the donate function has been combined into one feature called Gives Back. | The volunteer function and the donate function was split between 2 iterations, the volunteer function in Iteration 7 and the donate function in Iteration 8 respectively, and the Gives Back function was completed on time. |
3 | Flagging of Comments, Qutoes & Quotes Comments | IOS app store requires user contents to have flagging capabilities. Scheduled task in iteration 11 which had significantly less task as previously scheduled. |
4 | Implementation of a second donation platform - Ammado | Research and seek technological support from the people at ammado. Find workarounds so that integration would be seemless and less time consuming. Scheduled task in iteration 11 which had significantly less task as previously scheduled |
5 | Changed of focus from User Testing to Google Analytics | Focused on google analytics instead of user testing because after 3 user tests, the team received similar results which were not significant enough for changes to take place. Replaced tasks from user testing to google analytics implementation/integration. |
Project Management
Project Status
Feature | Status | Comments |
---|---|---|
Articles | 100% developed and deployed | Mobile and Admin Portal features completed |
Videos | 100% developed and deployed | High Quality YouTube videos available for Android |
Gives | 100% developed and deployed | Now supporting both PayPal and Ammado, donation records synced with Admin Portal |
Quotes | 100% developed and deployed | Flagging of Quotes and Comments to comply with App Store requirements |
Voice for a Cause | 100% developed and deployed | Video upload from device to Admin Portal, upload from Admin Portal to YouTube & playback of video responses |
Travel | 100% developed and deployed | Manage travel applicants from Admin Portal |
Magazine Subscription | 100% developed and deployed | Function can be switched on or off from the Admin Portal |
Google Analytics | 100% developed and deployed | Tracking content and events on device, analyse traffic demographics and app content viewership from Admin Portal |
Submit Feedback | 100% developed and deployed | Give device specific feedback, view feedback in Admin Portal |
Project Schedule (Planned VS. Actual)
For a more comprehensive understanding of our project schedule, please download Project Schedule.
Iteration | Tasks | Planned | Actual | Comments |
---|---|---|---|---|
7 | Develop Gives back function | 7 Jan 2013 | 14 Jan 2013 | Rescheduled Gives back function in place of heuristic evaluation modifications |
8 | Integrate PayPal module | 14 Jan 2013 | 31 Jan 2013 | Moved integration of PayPal module from Iteration 7 to Iteration 8 because preparations for User Test 1 took longer than expected |
8 | Backend Improvements to articles function and data analytics | NA | 28 Jan 2013 | Since the Paypal module function needed more testing and cannot integrate with the backend yet, the team inserted improvement tasks that was recommended by the client (refer to additional feature metric). |
9 | IPN Listener integration with backend function | 28 Jan 2013 | 7 Feb 2013 | This task had to be rescheduled because software testing for the PayPal module did not meet the expected result |
10 | Voices for a cause | 26 Feb 2013 | NA | There is a change in user requirements and Voices for a cause has replaced the Rewards Scheme functionality. The function has been moved (reason for move is due to the client's current business situation) from Iteration 9 to Iteration 10 |
11 | Flagging of Content | NA | 4 Mar 2013 | IOS app store requires user contents to have flagging capabilities. Inserted task in remaining iterations that had the least task |
12 | Travel Function | 18 Mar 2013 | Iteration 10 - 26 Feb 2013 | Still collecting user requirements about voices function. Push forward development of travel function |
The rest of the tasks progressed smoothly as per planned.
Project Metrics
Schedule Metric Score
The overall team’s schedule metric score over the past 9 iterations has been quite consistent maintaining within the healthy range of between 0.9 and 1.1. We have so far managed to meet most of individual tasks deadlines as well as allocating tasks for testing and functional improvements.
Schedule Highlights
Iteration | Description/Mitigation |
---|---|
5 | We had a few tasks that were delayed such as system integration of articles comments in iteration 5. However, the delay of tasks did not affect the schedule substantially as each iteration, there is a 2 days of buffer time in the event where a delay of tasks are present. With the help of the buffer days we were still able to complete the scheduled tasks within that iteration. |
7 & 9 | The giving back project feature was delayed in Iteration 7 due to the preparation of our first User test 1 also conducted in Iteration 7. Similarly, it did not affect the schedule much as we had 2 days of buffer time which still enabled us to complete our tasks on schedule. As such, the team learnt from this experience and so in Iteration 9, and began preparing for User test 2 in advance as well as allocating one specific resource to handle all User test 2 administrative work. As compared to Iteration 7 where all of the resources were activated, it was a much more efficient method. With the use of this mitigation strategy, we were able to improve the process of managing the user test as well as assigning the right amount of resources to avoid overloading on each member. As a result, the iterative score in Iteration 9 improved significantly as compared to Iteration 7. |
11 | Iteration 11 was task intensive as new features of flagging comments (Quotes & Comments) and ammado integration was being developed. These tasks were new in nature and had not be done before which explains the slight spike/delay in the iteration score. |
Links:
Bug Metric Score
Bug Highlights
Iteration | Description/Mitigation |
---|---|
6 | There is a substantial increase in the number of bugs in iteration 6 as we conducted our first Heuristics evaluation. Bug fixing tasks were scheduled in Iteration 7 to resolve all bugs. All 6 bugs found in this iteration were resolved in Iteration 7. |
7 | The number of bugs caught remained the same in Iteration 7 as we conducted our first user test 1. Bug fixing tasks were scheduled in Iteration 8 to resolve all bugs. All bugs found in this iteration were resolved in Iteration 8. |
8 | In Iteration 8, 8 bugs were caught as we conducted more rigorous software testing with more functionalities completed. Bug fixing tasks were scheduled in Iteration 9 to resolve all bugs. All bugs found in this iteration were resolved in Iteration 9. |
9 | In Iteration 9, the number of bugs caught dropped significantly. This could be due to the extensive testing that we carried out for the past 3 iterations. We conducted a second user test 2 as well as another software test in preparation for deployment to the app store. Bug fixing tasks were scheduled in Iteration 10 (this iteration) to resolve all bugs. All Bugs found in this iteration were resolved in iteration 10 |
10, 11 & 12 | In iteration 10,11 & 12, we caught a steady amount of bugs. Most of these bugs were of class A and not critical in nature. We also conducted software testing for each iteration |
Links:
Quality of Product
Final Deliverables
Stage | Specification | Modules |
---|---|---|
Project Management | Methodology | |
Schedule | ||
Scope | ||
Risks | ||
Metrics | ||
Meeting Minutes | ||
Requirements | User Interface Mockups | |
User Interface Storyboard | ||
Analysis | Use Case Diagram | |
Design | ER Diagram | |
Architecture Diagram | ||
Deployment Diagram | ||
Testing | Software Testing | |
Heuristics | ||
User Testing |
Deployment
- Staging & Development Environment: The application is compatible for Android Versions from 2.2 to 4.2.1. iOS minimum version compatibility is 4.3 to 6.1.2
- Database: It is currently in MySQL which is hosted on Humaneity's Server.
- Web Services: Facebook, YouTube, PayPal, Ammado RESTFUL webservices
- Web Links: View our Deployment Diagram Here!
Technical Complexity and Challenges
Task | Description |
---|---|
YouTube API Integration | What is this feature about?
The Global Forum feature allows users to upload videos of their views on a certain raging topic of concern. Users will upload their videos via the mobile application and then it would be stored at the Administrative Portal to await vetting by the Humaneity Administrator. Once approved, the video would be automatically uploaded to the YouTube channel, which ensures that the Humaneity database would not need to store the videos. In addition, the team is able to stream high quality MP4 videos for the Android section for the videos section, which is mentioned during the Mid-Term presentation.
|
Google Analytics Integration | What is this feature about?
Google Analytics allows the Humaneity team to track page views of the mobile application and as well as track user behaviour in terms of scrolling or navigation. The team can also analyse interesting information such as user demographics, the differences in usage between the iOS and the Android applications etc. With the help of Google Analytics, they could integrate all these information with the Administrative Portal as a dashboard for better viewing and analysis.
|
Full server backup for Admin Portal | What is this feature about?
In the event of a server crash and prevent losing all critical information, the team created a function for the Humaneity Administrator to be able to constantly save information of the entire Administrative portal. Be it the SQL database, source code, and all images, stories, videos etc zipped and downloaded locally as backup. It would be an easy migration to the new server with instructions provided on how to deploy the portal on a word document. Minimal configuration is required on the Humaneity Administrator's end to re-deploy the portal.
|
Multiple Donation Options | What is this feature about?
Due to a change in business requirements, the client hoped that our application would be able support Ammado (Another type of payment gateway) on top of PayPal for our donation functions.
|
PayPal Integration (from Mid Term) | What is this feature about?
This feature is for users to donate their desired amount to fund the projects they chose. The team needed to manage the donation process across the backend, administrative portal, iOS and Android systems. In this case, Paypal's IPN(Instant Payment Notification) is required for server-to-server communication of PayPal donation transactions.
|
High Quality YouTube Video Playback on Android (from Mid Term) | What is this feature about?
Previously due to the inability to embed YouTube HTML5 player in Titanium for Android, we could only use RTSP(Real Time Streaming protocol) to stream 3gp (video file format) from YouTube API. As such, the quality of the video could only be 240p 3gp format, which was very pixelated. On top of that, there is a blocking of RTSP on some networks, for eg. WLAN-SMU.
|
Google Charts API Integration (from Mid Term) | What is this feature about?
By integrating the Google Charts API with our administrative portal, we are able to generate user statistics in graphical representation for viewing.
|
Quotes Submission (from Mid Term) | What is this feature about?
Submission of quotes onto the mobile application either by using an existing picture from the phone's gallery or taking a new picture with the phone's camera. On top of that, user will also be able to put some text over the image before uploading on to the mobile application's server. As with all pictures, they come in portrait or landscape orientation, the complexity here is to retrieve the orientation of the picture so that we can correctly display the picture in its aspect ratio.
|
Testing
Heuristics | Software Testing and Results (Mobile and Administration Portal) | User Test |
Heuristics Evaluation
Area | Details |
---|---|
Method |
|
Measures |
|
Participants |
|
Environment |
|
Results |
|
Observations |
|
User Test 1
Area | Details |
---|---|
Method |
|
Measures |
|
Participants |
|
Environment |
|
Results | |
Observations |
|
User Test 2
Area | Details |
---|---|
Method |
|
Measures |
|
Participants |
|
Environment |
|
Results | |
Observations |
|
User Test 3
Area | Details |
---|---|
Method |
|
Measures |
|
Participants |
|
Environment |
|
Results | |
Observations |
|
UI Change Validation with Google Analytics
Area | Details |
---|---|
Method |
|
Measures |
|
Participants |
|
Environment |
|
Results | |
Observations |
|
Learning Outcomes
Team Member | Reflections |
---|---|
Chevy | This experience has taught me patience, perseverance and more importantly the camaraderie that my group mates and I share. I thoroughly enjoyed myself throughout the process and my group mates have certainly made my life a whole lot easier as project manager. I’m really proud to be part of this team/experience and am thankful to God who has placed me here. |
Boon Liang | Even though our client was not around to guide us most of the times, the team still must step up ourselves and ensure that we deliver a quality product and satisfy the business requirements. I was mainly in charge of testing for our application, and getting users to come and test our application without any incentive is a real pain. We needed a minimum number of testers in order to make our results significant enough to make any changes, and it was really difficult to co-ordinate everyone’s schedules. On a side note, it had been a long 14 weeks of development and many many weeks before of planning and prototyping etc. Finally, Team Succinq can finally heave a sigh of relief that WE ARE DONE! |
Willis | I identify each and every one of us as an integral role in making this project a success and that we fortify one another's role in the team. Roles changes over time from insignificant to crucial, but even the insignificant role cannot be missing. I recognise the efforts that each of us makes throughout my fyp journey as not one of them is redundant in making this an eventful journey. |
Vijay | From this FYP, I leave with 3 important lessons. Firstly, things don’t go always to plan. Many a time during our project we would plan for something and it would be pushed back due to unforeseen circumstances. Secondly, the project manager plays a essential role. Without our PM’s guidance and constant push, we would not have got as far as we have today. Finally, team dynamics can decide whether you succeed or fail in whatever you set out to do. |
Andrew | I have learned that communication and mutual respect is essential in any team project. Without these, the project would have been a much heavier burden for all of us. Also, resourcefulness and creativity are required when faced with set-backs. Finally, it has been extremely satisfying to see the fruits of our labour, from conceptualisation to countless iterations and the successful deployment of the admin portal and mobile apps. |