Difference between revisions of "IS480 Team wiki: 2016T2 Unition final"
Cxchen.2013 (talk | contribs) |
|||
Line 68: | Line 68: | ||
[[File:unition_scope_final.png|center|800px]] | [[File:unition_scope_final.png|center|800px]] | ||
− | < | + | <h3><big>Changes & Highlights of Project Scope</big> </h3> |
− | + | *Due to insufficient data provided in the sponsor's server database, functions such as sending email to book appointment with service providers will not be available as there is no email contact at the moment, and Care Service module to only display care service providers as Occupational Therapists data is not ready | |
+ | *Due to the challenges faced when implementing the shop function's cart and creation of order, tertiary and good-to-have functions were dropped to focus on the completion of core modules | ||
<h2><big>Project Timeline</big></h2> | <h2><big>Project Timeline</big></h2> | ||
<h4><big>Midterm</big></h4> | <h4><big>Midterm</big></h4> | ||
Line 77: | Line 78: | ||
[[File:Final_schedule_V1.png|center|1700px]] | [[File:Final_schedule_V1.png|center|1700px]] | ||
− | < | + | <h3><big>Highlights of Schedule</big></h3> |
+ | *As advised by our midterm reviewers, the team managed to push forward the deployment of the app onto Google Play Store on the 8 of March than the initial planned 18 of March | ||
<h2><big>Project Metrics</big></h2> | <h2><big>Project Metrics</big></h2> |
Revision as of 19:56, 18 April 2016
Home | About Us | Project Overview | Project Management | Documentation |
Mid-term Wiki | Final Wiki |
---|
Contents
Our Project Process Summary
Final Documentation
Project Highlights
Development Process
Our Project Management
Project Scope
Midterm
Final
Changes & Highlights of Project Scope
- Due to insufficient data provided in the sponsor's server database, functions such as sending email to book appointment with service providers will not be available as there is no email contact at the moment, and Care Service module to only display care service providers as Occupational Therapists data is not ready
- Due to the challenges faced when implementing the shop function's cart and creation of order, tertiary and good-to-have functions were dropped to focus on the completion of core modules
Project Timeline
Midterm
Final
Highlights of Schedule
- As advised by our midterm reviewers, the team managed to push forward the deployment of the app onto Google Play Store on the 8 of March than the initial planned 18 of March
Project Metrics
Schedule Metrics
Bug Metric
Iteration | Bug Score | Summary of Issure |
---|---|---|
8 | 1 Low, 5 High | Post midterm debugging based on UAT result |
9 | 2 Low, 3 High | Solve app crashes problem from shopping page |
10 | 4 Low 3 High, | Solved bugs from service and display products functions |
11 | 2 Critical, 4 High, 3 Low | Solved shopping process and app crashes problem. Most of bugs come from cart management and PayPal |
12 | 2 High, 2 Low | Debugging stage, solve problems based on UAT feedback |
Project Risks
Risk Type | Risk Description | Consequence | Likelihood | Impact | Risk level | Mitigation plan |
---|---|---|---|---|---|---|
Technical Risk | Project team has no prior knowledge of Android mobile app and need to learn to use Android Studio | Schedule may potentially be delayed due to time spent on learning and our initial deliverables might be buggy | High | High | A | We will have researching and learning sessions before we begin our actual coding tasks and adopts code we learn strategy. |
Project Management Risk | Requirements may change in the mid or after few iterations | Delay the current process of development and project schedule will be affected | Medium | High | A | Prior agreement with sponsor that major changes will not be addressed after confirmation on the agreement • Team to evaluate changes and to discuss with both sponsor and supervisor to obtain the best case scenario |
Technical Risk | Failed to connect sponsor's WordPress database with our Android application | To further research on other possible solutions or to get advice from supervisor • Discuss with the sponsor on the possibility of the our application using independent database. | High | Medium | A | Find out a stable way to get data from WordPress database. Get sponsors agreement to build a separate database if failed to use their data eventually |
Technical Risk | Sponsor's Wordpress site being down | Team will not be able to utilise required plugins from the wordpress site to perform application functions | Medium | High | A | Contact sponsors to inform them on the possible reasons why the site was down and to see their developer's assistance to bring up the site ASAP |
Technical Risk | Difficulties to map all functions on ShenCARE website to mobile app to fulfil the requirement | The team may not deliver a product meet sponsors satisfaction | Medium | Medium | B | We will clearly state the scope of our project that we agreed with our sponsors. The project manager will also monitor the progress of the project closely to ensure that we stick to the agreed scope. |
Project Management Risk | Unable to find enough users to test the application | Can not get sufficient feedback from users to improve current application | Medium | Medium | B | Contact sponsors and seek for their help to attract more target users to test our project |
Project Management Risk | Team members unavailable during some development periods due to illness or unforeseen urgent issue | Can not get sufficient feedback from users to improve current application | Low | Medium | C | Deputy person in the specific role take the task first, if not able to complete the task split to other members |
Technical Complexity
Architecture Diagram
Technology Used
Our Quality Assurance
Deliverables
Category | Documents | Link |
---|---|---|
Market Research | Market Research | Market Research |
Project Management | Meeting Minutes Risk Management |
Meeting Minutes Risk Management Schedule Metrics & Bug Metrics |
Technology | Technology and Tools Architectural Diagram |
Technology and Tools Architectural Diagram |
Design | Use Case Diagram | Use Case Diagram |
User Testing | Testing Plan Testing Cases Testing Result |
Test Plan Test Cases Test Result |
Testing
User Acceptance Testing
UAT 1
Number of Users: 20
Date and Time: 17 February 2015, 3.00pm - 7.00pm
Venue: Singapore Management University- Li Ka Shing Library, Project Room 4-18
Objectives:
1. To test the application on different Android Devices
2. To Identify any Defects in the design and bugs of the application
3. To Observe the Usability and Accessibility of the application
4. To Better Fine Tune the application in general
Full Documentation of UAT1 here
UAT 2
Number of Users: 15
Date and Time: 21 March 2015, 3.00pm - 7.00pm
Venue: On site
Objectives:
1. To test the application on different Android Devices
2. To allow real ShenCARE targeted users to download and use the application
3. To observe the usability and accessibility of the deployed application
4. To obtain feedback of from the real ShenCARE targeted users
Feedback:
Positive:
1. Clean UI, easy to navigate
Negative:
1. App crashes on some phones during the use of the app
2. App crashes on 2 phones when opening the app
3. Lag during usage
4. Should have better user experience in form input such as Capitalisation of the name
Follow Up:
1. Crashes mainly due to OOM
2. Lag to memory limit
3. Reduce image size within image downloading task
4. Auto caps the name and surname for user profile editing and user registration
UAT 3
Number of Users: 15
Date and Time: 28 March 2015, 3.00pm - 7.00pm
Venue: On site
Objectives:
1. To test the improved and redeployed version of ShenCARE app
2. To allow real ShenCARE targeted users to download and use the application
3. To observe the usability and accessibility of the deployed application
4. To obtain feedback of from the real ShenCARE targeted users
Feedback:
Positive:
1. Big button, good UI display
2. Simple and neat
Negative:
1. App crashes on some phones during the use of the app
2. To include other languages such as Chinese and Malay
3. Could not do real transaction using paypal
4. Should have simple introductions for some professional information such as the voluntary events
Follow Up:
1. Include “ android:largeHeap="true" ” in android manifest to overcome OOM error
Our Learning Outcomes
Reflections
Team Reflections
As a Software Development team we have learnt from this project:
- the importance of project management to guide the team to build a technical product consistently and progressively
- the significance of assigning members tasks which are within their control while urging them to learn more so as to promise the quality of the outcome and also ensure the punctuality
- the need to understand different stakeholders' requirements and work with them to transform the requirements into real working functions in the software application
- Android app design, development and deployment
Member | Takeaways |
---|---|
Liang Bing | "Learning by doing" is the major thing I learnt from this project. With continuous thinking, searching, trying, making mistakes and re-starting again, I pick up knowledge about Android UI, Android activities,
Android add-ons and Integration of Android and cloud database. Moreover, I have experienced a more mature and independent life cycle of software development - from getting user requirement, to iteratively developing and testing the product, and finally to completing the project. |
Jian Xian | One important lesson I learnt from this project is, to always expect the unexpected, especially when dealing with features of the project that has not been explored before. Project planning would need to be precise to anticipate the potential hurdles from the unexpected.
Also, I have learnt that integration between two systems is something that should not be taken lightly. Tenacious attempts and testing are necessary in order make the integration work. |
Chun Xiao | Throughout the whole development of the application, our team has been plagued with all kinds of issues that we have never encountered before. All the hours spend researching and trying out new solutions and greatly increased my knowledge on android development.
I also learnt that android development is significantly different from creating a normal java application as there is strong emphasis on both the appearance and usability of the app. |
Xiao Xia | Through the project I learnt that it is really important to know the needs of users and think from users' perspective. Also it is challenging to deal with conflicting feedbacks from users. We need to do tasks based on the priority.
At the same time always prepared to make changes and have a big picture of the whole project. Passion and interest motivate me work harder. |
Ronny | Through the Final Year Project I learnt to create an android application but the main learning outcome was to realise that changes are inevitable. Plans can be made but changes that arise from the team decision,
SDK changes and also from the user requirements will affect our time allocation for the given task. It is important to properly plan time for the changes and prioritize crucial changes to complete the project. |