HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
Line 51: Line 51:
  
  
<h3><big>Project Highlights</big></h3>
+
<h2><big>Project Highlights</big></h2>
  
 
<h3><big>Development Process</big></h3>
 
<h3><big>Development Process</big></h3>

Revision as of 12:38, 18 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
Unition ppticon.png Uniton videoicon.png Unition Postericon.png


Project Highlights

Development Process

Unition process.png

Our Project Management

Project Scope

Midterm

Unition scope3.jpg


Final

Unition scope final.png

Changes & Highlights

Project Timeline

Midterm

Unition Schedule (5).png

Final

Final schedule V1.png

Highlights

Project Metrics

Schedule Metrics


Bug Metric



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
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

Unition arch.jpg

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
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
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