HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T2 Unition final"

From IS480
Jump to navigation Jump to search
 
(48 intermediate revisions by 3 users not shown)
Line 35: Line 35:
 
=<div style="background: #65C7E2; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:24px; font-family:cambria"><font color= #ffffff>Our Project Process Summary</font></div>=
 
=<div style="background: #65C7E2; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:24px; font-family:cambria"><font color= #ffffff>Our Project Process Summary</font></div>=
  
<h3><big>Final Documentation</big></h3>
+
<h2><big>Final Documentation</big></h2>
 
<center><div>
 
<center><div>
 
{| class="wikitable" style="background-color:#FFFFFF; font-family:cambria"  
 
{| class="wikitable" style="background-color:#FFFFFF; font-family:cambria"  
Line 42: Line 42:
 
! style="color:white; background-color:#65C7E2;font-size:20px" | Video
 
! style="color:white; background-color:#65C7E2;font-size:20px" | Video
 
! style="color:white; background-color:#65C7E2;font-size:20px" | Poster
 
! style="color:white; background-color:#65C7E2;font-size:20px" | Poster
 +
! style="color:white; background-color:#65C7E2;font-size:20px" | App
 
|-
 
|-
| [[File:unition_ppticon.png |80px]]
+
| [[File:unition_ppticon.png |80px|link=https://wiki.smu.edu.sg/is480/img_auth.php/7/75/ShenCARE_Final_Presentation_2016.pdf]]
 
| [[File:uniton_videoicon.png |80px|link=https://drive.google.com/a/smu.edu.sg/file/d/0B47YoQQEawCJNUp0NldsTGhCSHM/view]]
 
| [[File:uniton_videoicon.png |80px|link=https://drive.google.com/a/smu.edu.sg/file/d/0B47YoQQEawCJNUp0NldsTGhCSHM/view]]
 
| [[File:unition_Postericon.png |80px|link=https://drive.google.com/a/smu.edu.sg/file/d/0B47YoQQEawCJRjIwc2w0cjhZZ1k/view]]
 
| [[File:unition_Postericon.png |80px|link=https://drive.google.com/a/smu.edu.sg/file/d/0B47YoQQEawCJRjIwc2w0cjhZZ1k/view]]
 +
|[[File:GooglePlay.png|80px|link=https://play.google.com/store/apps/details?id=com.shencare.shencaremobile&hl=en]]
 
|-
 
|-
 
|}
 
|}
Line 51: Line 53:
  
  
<h3><big>Project Highlights</big></h3>
+
<h2><big>Project Highlights</big></h2>
 
+
[[File:Unition_highlight.png|center]]
<h3><big>Development Process</big></h3>
+
<h2><big>Development Process</big></h2>
 +
[[File:Unition_process.png]]
  
 
=<div style="background: #65C7E2; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:24px; font-family:cambria"><font color= #ffffff>Our Project Management</font></div>=
 
=<div style="background: #65C7E2; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:24px; font-family:cambria"><font color= #ffffff>Our Project Management</font></div>=
  
<h3><big>Project Scope</big></h3>
+
<h2><big>Project Scope</big></h2>
 +
<h4><big>Midterm</big></h4>
 +
[[File:unition_scope3.jpg|center|800px]]
  
 +
<br>
 +
<h4><big>Final</big> </h4>
 +
[[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>
 +
<h4><big>Midterm</big></h4>
 +
[[File:Unition Schedule (5).png|center|1700px]]
  
<h3><big>Project Timeline</big></h3>
+
<h4><big>Final</big></h4>
 +
[[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
  
<h3><big>Project Metrics</big></h3>
+
<h2><big>Project Metrics</big></h2>
  
<h4><big>Schedule Metrics</big></h4>
+
<h2><big>Schedule Metrics</big></h2>
 +
[[File:TeanUnitionFinalSM2.JPG|1000px]]
  
 +
[[File:TeanUnitionFinalSM3.JPG|1000px]]
 +
<h2><big>Bug Metric</big></h2>
 +
[[File:unition_bugscore.png|center|500px]]
 +
<br><br>
 +
{| class="wikitable" style="text-align:center; background: white; margin: 1px; font-family:cambria;font-weight: bold; "
 +
|-
 +
! style="color:#FFFFFF; background-color:#65C7E2;" width="500pt" | Iteration
 +
! style="color:#FFFFFF; background-color:#65C7E2;" width="500pt" | Bug Score
 +
! style="color:#FFFFFF; background-color:#65C7E2;" width="500pt" | 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
 +
|-
  
<h4><big>Bug Metric</big></h4>
 
  
 +
|}
  
 +
<h2><big>Project Risks</big></h2>
  
 +
[[File:Riskid.png|center|500px]]
  
 +
{| class="wikitable" style="text-align:center; background: white; margin: 1px; font-family:cambria;font-weight: bold; "
 +
|-
 +
! style="color:#FFFFFF; background-color:#65C7E2;" width="500pt" | Risk Type
 +
! style="color:#FFFFFF; background-color:#65C7E2;" width="500pt" | Risk Description
 +
! style="color:#FFFFFF; background-color:#65C7E2;" width="800pt" | Consequence
 +
! style="color:#FFFFFF; background-color:#65C7E2;" width="400pt" | Likelihood
 +
! style="color:#FFFFFF; background-color:#65C7E2;" width="400pt" | Impact
 +
! style="color:#FFFFFF; background-color:#65C7E2;" width="400pt" | Risk level
 +
! style="color:#FFFFFF; background-color:#65C7E2;" width="800pt" | Mitigation plan
  
<h3><big>Project Risks</big></h3>
+
|-
 +
|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
 +
|-
 +
|-
 +
|Project Management Risk
 +
|Core plugins removed from WordPress site without notice
 +
|Team will not be able to utilise required plugins from the WordPress site to perform application functions
 +
|Medium
 +
|High
 +
|A
 +
|To communicate with sponsors on the handling of the installed plugins to prevent miscommunication which may lead to uninstalling by mistake
 +
|-
 +
|-
 +
|Technical Risk
 +
|App requires too much memory to execute the functions
 +
|App user to experience crashes and inability to use the app or complete any of the available functions
 +
|Medium
 +
|High
 +
|A
 +
|Research in ways to reduce excessive memory usage when performing the app functions
 +
|-
 +
|-
 +
|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
 +
|Insufficient knowledge of the usage of the available API
 +
|Unable to complete the required function
 +
|Medium
 +
|Medium
 +
|B
 +
|To discuss with sponsors on the potential work about solutions to overcome the hurdle
 +
|-
 +
|-
 +
|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
 +
|-
  
 
+
|-
<h3><big>Technical Complexity</big></h3>
+
|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
 +
|-
 +
|-
 +
|}
 +
<br> <br> <br>
 +
<h2><big>Technical Complexity</big></h2>
  
 
<h4><big>Architecture Diagram</big></h4>
 
<h4><big>Architecture Diagram</big></h4>
[[File: Unition_arch.jpg|1000px]]
+
[[File:New archi diagram.png|1000px]]
 
<br>
 
<br>
 
<br>
 
<br>
<h4><big>Technology Used</big></h4>
+
<h2><big>Technology Used</big></h2>
  
 
[[File: Technologies.png|1000px]]
 
[[File: Technologies.png|1000px]]
Line 102: Line 252:
 
|-
 
|-
  
! style="background: #65C7E2; color: white; font-weight: bold; width:50px" | Meeting Minutes
+
! style="background: #65C7E2; color: white; font-weight: bold; width:50px" | Project Management
| '''Internal''' <br>
+
| '''Meeting Minutes''' <br>
'''Supervisor''' <br>
+
'''Risk Management''' <br>
'''Sponsor''' <br>
+
'''Metrics''' <br>
| [[IS480 Team wiki: 2016T2 Unition documentation|'''Meeting Minutes''']]
 
|-
 
  
! style="background: #65C7E2; color: white; font-weight: bold; width:50px" | Metrics
+
| [[IS480 Team wiki: 2016T2 Unition documentation|'''Meeting Minutes''']]  <br>[[IS480 Team wiki: 2016T2 Unition Risk Management|'''Risk Management''']]<br> [[IS480 Team wiki: 2016T2 Unition Metrics|'''Schedule Metrics & Bug Metrics ''']]
| '''Schedu Metric''' <br>
 
'''Bug Metric''' <br>
 
| [[IS480 Team wiki: 2016T2 Unition documentation|'''Meeting Minutes''']]  
 
 
|-
 
|-
  
! style="background: #65C7E2; color: white; font-weight: bold; width:50px" | Risk Management
 
| '''Risk Management''' <br>
 
| [[IS480 Team wiki: 2016T2 Unition documentation|'''Meeting Minutes''']]
 
|-
 
  
! style="background: #65C7E2; color: white; font-weight: bold; width:50px" | Technology Diagram
+
! style="background: #65C7E2; color: white; font-weight: bold; width:50px" | Technology  
|''' Technology and Tools '''
+
|''' Technology and Tools ''' <br> '''Architectural Diagram '''
| [[IS480 Team wiki: 2016T2 Unition Technologies|'''Technology and Tools''']]
+
| [[IS480 Team wiki: 2016T2 Unition Technologies|'''Technology and Tools''']] <br>[[IS480 Team wiki: 2016T2 Unition Technologies|'''Architectural Diagram''']]
 
|-
 
|-
  
! style="background: #65C7E2; color: white; font-weight: bold; width:50px" | Use case Diagram
+
! style="background: #65C7E2; color: white; font-weight: bold; width:50px" | Design
 
|'''Use Case Diagram'''
 
|'''Use Case Diagram'''
|style="text-align:center" | [[IS480 Team wiki: 2016T2 Unition Diagram|'''Use Case Diagram''']]
+
| [[IS480 Team wiki: 2016T2 Unition Diagram|'''Use Case Diagram''']]
 
|-
 
|-
  
! style="background: #65C7E2; color: white; font-weight: bold; width:50px" | Architectural Diagram
+
 
|'''Architectural Diagram '''
+
 
|style="text-align:center" | [[IS480 Team wiki: 2016T2 Unition Technologies|'''Architectural Diagram''']]
+
! style="background: #65C7E2; color: white; font-weight: bold; width:50px" | User Testing
 +
|'''Testing Plan ''' <br> '''Testing Cases ''' <br> '''Testing Result '''  
 +
| [[IS480 Team wiki: 2016T2 Unition Testing|'''Test Plan''']] <br> [[IS480 Team wiki: 2016T2 Unition Testing|'''Test Cases''']] <br> [[IS480 Team wiki: 2016T2 Unition Testing|'''Test Result''']]
 
|-
 
|-
 
|}
 
|}
  
<h3><big>Testing</big></h3>
+
<h3><big>Testing</big></h3><br>
 +
<h3>'''User Acceptance Testing'''</h3> <br>
 +
 
 +
<h2>'''UAT 1'''</h2><br>
 +
Number of Users: 20 <br>
 +
Date and Time: 17 February 2015, 3.00pm - 7.00pm <br>
 +
Venue: Singapore Management University- Li Ka Shing Library, Project Room 4-18 <br>
 +
Objectives:  <br>
 +
1. To test the application on different Android Devices <br>
 +
2. To Identify any Defects in the design and bugs of the application <br>
 +
3. To Observe the Usability and Accessibility of the application <br>
 +
4. To Better Fine Tune the application in general<br>
 +
Full Documentation of UAT1 [[IS480 Team wiki: 2016T2 Unition Testing| <font color="#0101DF">here</font>]]<br>
 +
 
 +
<h2>'''UAT 2'''</h2><br>
 +
Number of Users: 15 <br>
 +
Date and Time: 21 March 2015, 3.00pm - 7.00pm <br>
 +
Venue: On site <br>
 +
Objectives: <br>
 +
1. To test the application on different Android Devices <br>
 +
2. To allow real ShenCARE targeted users to download and use the application <br>
 +
3. To observe the usability and accessibility of the deployed application <br>
 +
4. To obtain feedback of from the real ShenCARE targeted users <br>
 +
Feedback:  <br>
 +
Positive: <br>
 +
1. Clean UI, easy to navigate <br>
 +
 
 +
Negative: <br>
 +
1. App crashes on some phones during the use of the app <br>
 +
2. App crashes on 2 phones when opening the app <br>
 +
3. Lag during usage <br>
 +
4. Should have better user experience in form input such as Capitalisation of the name<br>
 +
 
 +
Follow Up: <br>
 +
1. Crashes mainly due to OOM <br>
 +
2. Lag to memory limit <br>
 +
3. Reduce image size within image downloading task <br>
 +
4. Auto caps the name and surname for user profile editing and user registration <br>
 +
 
 +
<h2>'''UAT 3'''</h2><br>
 +
Number of Users: 15 <br>
 +
Date and Time: 28 March 2015, 3.00pm - 7.00pm <br>
 +
Venue: On site <br>
 +
Objectives: <br>
 +
1. To test the improved and redeployed version of ShenCARE app <br>
 +
2. To allow real ShenCARE targeted users to download and use the application <br>
 +
3. To observe the usability and accessibility of the deployed application <br>
 +
4. To obtain feedback of from the real ShenCARE targeted users <br>
 +
Feedback:  <br>
 +
Positive: <br>
 +
1. Big button, good UI display <br>
 +
2. Simple and neat <br>
 +
 
 +
Negative: <br>
 +
1. App crashes on some phones during the use of the app <br>
 +
2. To include other languages such as Chinese and Malay <br>
 +
3. Could not do real transaction using paypal <br>
 +
4. Should have simple introductions for some professional information such as the voluntary events <br>
 +
 
 +
Follow Up: <br>
 +
1. Include “ android:largeHeap="true" ” in android manifest to overcome OOM error
  
 
=<div style="background: #65C7E2; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:24px; font-family:cambria"><font color= #ffffff>Our Learning Outcomes</font></div>=
 
=<div style="background: #65C7E2; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:24px; font-family:cambria"><font color= #ffffff>Our Learning Outcomes</font></div>=
 +
 +
<h3>Reflections</h3><br>
 +
 +
'''Team Reflections'''<br>
 +
As a Software Development team we have learnt from this project: <br>
 +
 +
- the importance of project management to guide the team to build a technical product consistently and progressively <br>
 +
 +
- 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 <br>
 +
 +
- the need to understand different stakeholders' requirements and work with them to transform the requirements into real working functions in the software application <br>
 +
 +
- Android app design, development and deployment <br>
 +
 +
{| class="wikitable"
 +
|-
 +
! 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.
 +
 +
|-
 +
|}

Latest revision as of 14:31, 19 April 2016

Unition logo.png


Home   About Us   Project Overview   Project Management   Documentation


Mid-term Wiki Final Wiki

Our Project Process Summary

Final Documentation

Slides Video Poster App
Unition ppticon.png Uniton videoicon.png Unition Postericon.png GooglePlay.png


Project Highlights

Unition highlight.png

Development Process

Unition process.png

Our Project Management

Project Scope

Midterm

Unition scope3.jpg


Final

Unition scope final.png

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

Unition Schedule (5).png

Final

Final schedule V1.png

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

TeanUnitionFinalSM2.JPG

TeanUnitionFinalSM3.JPG

Bug Metric

Unition bugscore.png



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

Riskid.png
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
Project Management Risk Core plugins removed from WordPress site without notice Team will not be able to utilise required plugins from the WordPress site to perform application functions Medium High A To communicate with sponsors on the handling of the installed plugins to prevent miscommunication which may lead to uninstalling by mistake
Technical Risk App requires too much memory to execute the functions App user to experience crashes and inability to use the app or complete any of the available functions Medium High A Research in ways to reduce excessive memory usage when performing the app functions
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 Insufficient knowledge of the usage of the available API Unable to complete the required function Medium Medium B To discuss with sponsors on the potential work about solutions to overcome the hurdle
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

New archi diagram.png

Technology Used

Technologies.png

Our Quality Assurance

Deliverables

Category Documents Link
Market Research Market Research Market Research
Project Management Meeting Minutes

Risk Management
Metrics

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.