IS480 Team wiki: 2012T2 Succinq Midterm Wiki
- 1 Project Progress Summary
- 2 Project Management
- 3 Quality of Product
- 4 Reflections and Learning Outcomes
Project Progress Summary
- Download the iOS Version through your mobile device: m.diawi.com
- Download the Android Version from Google Play through your mobile device: bit.ly/humaneity_play
- Download the Android Preview Version (PayPal donations in sandbox environment) through your mobile device: bit.ly/humaneity_android
- View our Administrative Portal here: http://www.humaneity.com/mobileapp/
- Download our Mid Term presentation slides here!
We have 3 more iterations worth of development till we reach our poster submission day. We are currently on schedule and we are confident that the project will progress as planned.
|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 this iteration (10) to the Voice for a Cause functionality in the schedule.|
|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 schedule.|
|Feature||Status||Confidence Level (0 - 1)||Comments|
|Articles||100% developed and deployed||1|
|Videos||100% developed and deployed||1|
|Gives||100% developed and deployed||1|
|Quotes||90% developed and deployed||1||There are still improvements to be made towards userbility and navigation after collecting feedback from User Test 2.|
|Voice for a Cause||Not Started||0.8||This additional function replaces the earlier planned gamification function(Rewards Scheme) as requested by the client in the latest meeting.|
|Magazine Subscription||Not Started||1|
Project Schedule (Planned VS. Actual)
For a more comprehensive understanding of our project schedule, please download Project Schedule.
|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|
The rest of the tasks progressed smoothly as per planned.
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.
|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.|
|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. To date, there is 1 outstanding bug in iOS, which involves updating the number of comments in the icon after commenting on a quote, that is yet to be resolved|
Top 3 Project Risks
|S/N||Type of Risk||Risk Description||Likelihood||Impact||Mitigation Strategy|
|1||Technology and Learning||The steep learning curve of new development modules may result in slower deliverable to the project and the team may not meet the expected scheduled deadline.||Maybe||Medium||The team will manage this issue by doing extensive research from the internet/books or get help from our expert advisors (Erwan & Vincent). The PM will also manage the schedule and plan for a longer duration for newer functions.|
|2||Technology and Deployment||Not being able to officially deliver/publish the application on time due to requirement mismatch or other missing elements on the app store||Likely||High||Attempt to deploy the application before mid terms to understand the requirements that the team needs to adhere from the app store. This will help the team understand the publishing process for subsequent launch versions.|
|3||Post Development Support||Low or no post project maintenance may result in low product quality of the application in the long run.||Likely||High||Application developed in a layered and modular manner. Use of more familiar technologies wherever possible. Meet client regularly to assess relevance and functionalities. Provide an administration portal to manage the frontend application as seamless and flexible as possible.|
|PayPal Integration|| 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|| 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|| 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|| 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.
Quality of Product
|Requirements||User Interface Mockups|
|User Interface Storyboard|
|Analysis||Use Case Diagram|
- 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 RESTFUL webservices
- Web Links: View our Deployment Diagram Here!
|Heuristics||Software Testing and Results (Mobile and Administration Portal)||User Test|