HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
 
(35 intermediate revisions by 3 users not shown)
Line 1: Line 1:
  
 
<!--------------- Header ---------------------->
 
<!--------------- Header ---------------------->
[[File:Logo.png|200px|center]]
+
[[File:Unition logo.png|500px|center]]
  
  
Line 23: Line 23:
 
|}<br/>
 
|}<br/>
 
<!---------------End of nav bar---------------------->
 
<!---------------End of nav bar---------------------->
 +
{| style="background-color:#ADD8E6; margin: 3px auto 0 auto" width="55%"
 +
|-
 +
 +
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2016T2 Unition midterm | <span style="color:#3d3d3d">Mid-term Wiki</span>]]
 +
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|
 +
 +
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2016T2 Unition final | <span style="color:#3d3d3d">Final Wiki</span>]]
 +
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|
 +
 +
|}
 
=<div style="background: #ADD8E6; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Our Project Process Summary</font></div>=
 
=<div style="background: #ADD8E6; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Our Project Process Summary</font></div>=
  
==Presentation Slides==
+
==<div style="background: #ffffff; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Presentation Slides</font></div>==
 +
[[Media:unition_midterm.pdf|Presentation Slides]]
 +
 
 +
==<div style="background: #ffffff; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Project Progression</font></div>==
 +
There are a total of 13 iterations
 +
*Current iteration : 8
 +
*Google Play Deployment to be done by 18 March 2016
 +
*UAT 3 will be tested with actual users and volunteers in iteration 10, application will be downloaded from Google Play Store
 +
*UAT 4 will be tested with actual users and volunteers in iteration 11, application will be downloaded from Google Play Store
 +
 
 +
==<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Development Process</font></div>==
 +
<div style="background: #ADD8E6; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Completed Functions</font></div>
  
==Project summary==
+
[[File:Complete.png|center|800px]]
 +
<br>
 +
<div style="background: #ADD8E6; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>In-progress Functions</font></div>
 +
[[File:Tobe.png|center|800px]]
 +
<br>
 +
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Completion Level Legend </font></div>
  
==Development Process==
+
[[File:Standard.png|center]]
  
 
=<div style="background: #ADD8E6; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Our Project Management</font></div>=
 
=<div style="background: #ADD8E6; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Our Project Management</font></div>=
==Project Scope==
+
<br>
 +
==<div style="background: #ffffff; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Project Scope</font></div>==
 
[[File:Functions v1.png|center|600px]]
 
[[File:Functions v1.png|center|600px]]
===Change in Project Scope===
+
<br>
 +
===<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Change in Project Scope </font></div>===
 
[[File:unition_scope3.jpg|center|800px]]
 
[[File:unition_scope3.jpg|center|800px]]
 +
<br>
 +
====<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Highlights of Change in Project Scope</font></div>====
 +
*Post acceptance, multiple discussions were done between the team and our Sponsors to realign the project scope with their business requirements
 +
*The aspect of "Booking an Appointment" with Clinical services and Therapists was change to email engagement to provide the communication between the user and the service providers
 +
*The email function will be enforced to the Volunteer sign up option as well
 +
*Logs of email engagements  and as well as shopping cart logs are to be reflected in user account.
 +
 +
==<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Project Timeline</font></div>Project Timeline==
 +
[[Image:Unition_Timeline.png|center|1700px|]]
 +
<br>
 +
===<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Change in Project Schedule </font></div>===
 +
[[File:Unition Schedule (5).png|center|1700px]]
 +
<br>
 +
 +
==<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Project Metrics</font></div>==
 +
===<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Schedule Metrics</font></div>===
 +
[[File:Unition_Breakdown_of_SM_Score.png|800px]]
 +
[[File:unition_SM_Chart.png|1000px]]
 +
<br>
 +
===<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Highlights of Schedule Metric Scores</font></div>===
 +
Iteration 6
 +
*Due to the team unfamiliarity with Wordpress, the initial special account access given to the team was not enough to allow the link between our App and Wordpress's database.
 +
*Upon discussion with Sponsors, the team was granted higher access to tackle the Wordpress database challenge, however, the Wordpress site was down and testing could not be performed.
 +
*Troubleshooting of the Wordpress site took up a lot of time and implementing the techniques from our research on Wordpress database was not smooth sailing.
 +
*The massive delay resulted in the team's decision to re-scope and re-schedule after discussion with both Sponsors and Supervisor.
 +
<br>
  
==Project Timeline==
+
===<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Bug Metric</font></div>===
[[File:Unition Schedule.jpg|center|1700px]]
+
[[File:Bugscore.png|800PX]]
===Change in Project Schedule===
+
<br>
[[File:Unition Schedule_(4).png|center|1700px]]
+
===<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Highlights of Bug Metric Scores</font></div>===
 +
Iteration 7
 +
*Integration of the Events with calendar view UI had contributed to most of the bugs in the iteration.
 +
*Due to the adaptation of external resources on calendar view, developers in the team took some time to understand the codes before implementation, still major bugs occurred which the team took immediate action to rectify them.
 +
<br>
  
==Project Metrics==
+
==<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Project Risks</font></div>==
===Schedule Metric===
 
===Bug Metric===
 
[[File:Unition_bs.JPG|600PX]]
 
===Highlights of Bug Metric Scores===
 
==Project Risks==
 
 
[[File:Riskid.png|center|500px]]
 
[[File:Riskid.png|center|500px]]
  
Line 77: Line 130:
 
|High
 
|High
 
|A
 
|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 bother sponsor and supervisor to obtain the best case scenario
+
|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  
+
|Technical Risk  
|Failed to connect sponsors' WordPress database through Android application  
+
|Failed to connect sponsor's WordPress database with our Android application  
|Sponsors need to manage two separate databases with same content which cause extra work
+
|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
 
|High
 
|Medium
 
|Medium
Line 89: Line 142:
 
|-
 
|-
 
|-
 
|-
|Project Management Risk
+
|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
 
|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
 
|The team may not deliver a product meet sponsors satisfaction
Line 106: Line 168:
 
|Contact sponsors and seek for their help to attract more target users to test our project
 
|Contact sponsors and seek for their help to attract more target users to test our project
 
|-
 
|-
 +
 
|-  
 
|-  
 
|Project Management Risk  
 
|Project Management Risk  
Line 117: Line 180:
 
|-  
 
|-  
 
|}
 
|}
==Technical Complexity==
+
 
===Architecture===
+
==<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Technical Complexity</font></div>==
 +
===<div style="background: #ADD8E6; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Architecture</font></div>===
 
[[File:unition_arch.jpg|1000px]]
 
[[File:unition_arch.jpg|1000px]]
 +
<br>
 +
<br>
 +
===<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Technology Used</font></div>===
 +
[[File:Technologies.png|1000px]]
 +
<br>
 +
====<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Highlights of Technical Complexity</font></div>====
 +
*Due to the nature of Android development, database connection with Wordpress would require HTTP REST requests to query data from its database
 +
*In order for such HTTP requests to be established, plugins are to be in place in the Wordpress site to allow calling of such APIs
 +
*However, off shelf plugins provide limited functions which may not fully suffice the needs of our App development, therefore, customization of the API was required
 +
*With the instability of the Wordpress site and plugins versions, the team experienced a tough testing phase when establishing the database linkage
 +
*Multiple attempts of editing the customization of the APIs was experienced to cater to the right data query and executions
  
 
=<div style="background: #ADD8E6; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Our Quality Assurance</font></div>=
 
=<div style="background: #ADD8E6; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Our Quality Assurance</font></div>=
==Intermediate Deliverables==
+
==<div style="background: #ffffff; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Intermediate Deliverables</font></div>==
  
 
{| class="wikitable" style="margin: auto;width:50%; text-align:center; background: white;"
 
{| class="wikitable" style="margin: auto;width:50%; text-align:center; background: white;"
Line 137: Line 212:
 
|style="text-align:center"| Project Management
 
|style="text-align:center"| Project Management
 
|style="text-align:center" | Metrics  
 
|style="text-align:center" | Metrics  
|style="text-align:center" | [[IS480 Team wiki: 2016T2 Unition documentation|'''Meeting Minutes''']]
+
|style="text-align:center" | [[IS480 Team wiki: 2016T2 Unition Metrics|'''Metrics''']]
 
|-
 
|-
  
 
|style="text-align:center"| Project Management
 
|style="text-align:center"| Project Management
 
|style="text-align:center" | Risk Management  
 
|style="text-align:center" | Risk Management  
|style="text-align:center" | [[IS480 Team wiki: 2016T2 Unition documentation|'''Meeting Minutes''']]
+
|style="text-align:center" | [[IS480 Team wiki: 2016T2 Unition Risk Management|'''Risk Management''']]
 
|-
 
|-
  
 
|style="text-align:center"| Design
 
|style="text-align:center"| Design
 
|style="text-align:center" | Use Case Diagram
 
|style="text-align:center" | Use Case Diagram
|style="text-align:center" | [[IS480 Team wiki: 2016T2 Unition documentation|'''Meeting Minutes''']]
+
|style="text-align:center" | [[IS480 Team wiki: 2016T2 Unition Diagram|'''Use Case Diagram''']]
 
|-
 
|-
  
 
|style="text-align:center"| Design
 
|style="text-align:center"| Design
 
|style="text-align:center" | Architectural Diagram  
 
|style="text-align:center" | Architectural Diagram  
|style="text-align:center" | [[IS480 Team wiki: 2016T2 Unition documentation|'''Meeting Minutes''']]
+
|style="text-align:center" | [[IS480 Team wiki: 2016T2 Unition Technologies|'''Architectural Diagram''']]
 
|-
 
|-
  
 
|style="text-align:center"| Design
 
|style="text-align:center"| Design
 
|style="text-align:center" | Technology and Tools  
 
|style="text-align:center" | Technology and Tools  
|style="text-align:center" | [[IS480 Team wiki: 2016T2 Unition documentation|'''Meeting Minutes''']]
+
|style="text-align:center" | [[IS480 Team wiki: 2016T2 Unition Technologies|'''Technology and Tools''']]
 
|-
 
|-
  
 
|style="text-align:center"| Market Research  
 
|style="text-align:center"| Market Research  
 
|style="text-align:center" | Market Research  
 
|style="text-align:center" | Market Research  
|style="text-align:center" | [[IS480 Team wiki: 2016T2 Unition documentation|'''Meeting Minutes''']]
+
|style="text-align:center" | [[IS480 Team wiki: 2016T2 Unition Research|'''Market Research''']]
 
|-
 
|-
  
 
|style="text-align:center"| Testing   
 
|style="text-align:center"| Testing   
 
|style="text-align:center" | Testing Plan  
 
|style="text-align:center" | Testing Plan  
|style="text-align:center" | [[IS480 Team wiki: 2016T2 Unition documentation|'''Meeting Minutes''']]
+
|style="text-align:center" | [[IS480 Team wiki: 2016T2 Unition Testing|'''Test Plan''']]
 
|-
 
|-
  
 
|style="text-align:center"| Testing   
 
|style="text-align:center"| Testing   
 
|style="text-align:center" | Test Cases  
 
|style="text-align:center" | Test Cases  
|style="text-align:center" | [[IS480 Team wiki: 2016T2 Unition documentation|'''Meeting Minutes''']]
+
|style="text-align:center" | [[IS480 Team wiki: 2016T2 Unition Testing|'''Test Cases''']]
 +
|-
 +
 
 +
|style="text-align:center"| Testing 
 +
|style="text-align:center" | Test Result
 +
|style="text-align:center" | [[IS480 Team wiki: 2016T2 Unition Testing|'''Test Result''']]
 
|-
 
|-
 
|}
 
|}
  
==Testing==
+
==<div style="background: #ffffff; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Testing</font></div>==
 +
 
 +
User Acceptance Testing <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 our User Testing [[IS480 Team wiki: 2016T2 Unition Testing| <font color="#0101DF">User Acceptance Testing</font>]]<br>
  
 
=<div style="background: #ADD8E6; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Our Learning Outcomes</font></div>=
 
=<div style="background: #ADD8E6; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 20px; font-size:22px; font-family:helvetica"><font color= #2d393b>Our Learning Outcomes</font></div>=
 
[[Image:unition_reflection.png|center|800px]]
 
[[Image:unition_reflection.png|center|800px]]

Latest revision as of 11:44, 7 April 2016

Unition logo.png


Home   About Us   Project Overview   Project Management   Documentation


Mid-term Wiki Final Wiki

Our Project Process Summary

Presentation Slides

Presentation Slides

Project Progression

There are a total of 13 iterations

  • Current iteration : 8
  • Google Play Deployment to be done by 18 March 2016
  • UAT 3 will be tested with actual users and volunteers in iteration 10, application will be downloaded from Google Play Store
  • UAT 4 will be tested with actual users and volunteers in iteration 11, application will be downloaded from Google Play Store

Development Process

Completed Functions
Complete.png


In-progress Functions
Tobe.png


Completion Level Legend
Standard.png

Our Project Management


Project Scope

Functions v1.png


Change in Project Scope

Unition scope3.jpg


Highlights of Change in Project Scope

  • Post acceptance, multiple discussions were done between the team and our Sponsors to realign the project scope with their business requirements
  • The aspect of "Booking an Appointment" with Clinical services and Therapists was change to email engagement to provide the communication between the user and the service providers
  • The email function will be enforced to the Volunteer sign up option as well
  • Logs of email engagements and as well as shopping cart logs are to be reflected in user account.

Project Timeline
Project Timeline

Unition Timeline.png


Change in Project Schedule

Unition Schedule (5).png


Project Metrics

Schedule Metrics

Unition Breakdown of SM Score.png Unition SM Chart.png

Highlights of Schedule Metric Scores

Iteration 6

  • Due to the team unfamiliarity with Wordpress, the initial special account access given to the team was not enough to allow the link between our App and Wordpress's database.
  • Upon discussion with Sponsors, the team was granted higher access to tackle the Wordpress database challenge, however, the Wordpress site was down and testing could not be performed.
  • Troubleshooting of the Wordpress site took up a lot of time and implementing the techniques from our research on Wordpress database was not smooth sailing.
  • The massive delay resulted in the team's decision to re-scope and re-schedule after discussion with both Sponsors and Supervisor.


Bug Metric

800PX

Highlights of Bug Metric Scores

Iteration 7

  • Integration of the Events with calendar view UI had contributed to most of the bugs in the iteration.
  • Due to the adaptation of external resources on calendar view, developers in the team took some time to understand the codes before implementation, still major bugs occurred which the team took immediate action to rectify them.


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

Unition arch.jpg

Technology Used

Technologies.png

Highlights of Technical Complexity

  • Due to the nature of Android development, database connection with Wordpress would require HTTP REST requests to query data from its database
  • In order for such HTTP requests to be established, plugins are to be in place in the Wordpress site to allow calling of such APIs
  • However, off shelf plugins provide limited functions which may not fully suffice the needs of our App development, therefore, customization of the API was required
  • With the instability of the Wordpress site and plugins versions, the team experienced a tough testing phase when establishing the database linkage
  • Multiple attempts of editing the customization of the APIs was experienced to cater to the right data query and executions

Our Quality Assurance

Intermediate Deliverables

Type Description Links
Project Management Meeting Minutes Meeting Minutes
Project Management Metrics Metrics
Project Management Risk Management Risk Management
Design Use Case Diagram Use Case Diagram
Design Architectural Diagram Architectural Diagram
Design Technology and Tools Technology and Tools
Market Research Market Research Market Research
Testing Testing Plan Test Plan
Testing Test Cases Test Cases
Testing Test Result Test Result

Testing

User Acceptance Testing
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 our User Testing User Acceptance Testing

Our Learning Outcomes

Unition reflection.png