Difference between revisions of "IS480 Team wiki: 2016T2 Unition midterm"
Jump to navigation
Jump to search
Xx.xu.2012 (talk | contribs) |
Xx.xu.2012 (talk | contribs) |
||
Line 64: | Line 64: | ||
<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>Change in Project Schedule </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>Change in Project Schedule </font></div>=== | ||
− | [[File:Unition | + | [[File:Unition Schedule (5).png|center|1700px]] |
<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>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>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>=== | ===<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>=== |
Revision as of 22:13, 18 February 2016
Home | About Us | Project Overview | Project Management | Documentation |
Contents
Our Project Process Summary
Presentation Slides
Project Progression
There are a total of 13 iterations
- Current iteration : 8
- UAT 3 will be tested with actual users and volunteers in iteration 11
- Google Play Deployment to be done by 18 March 2016
Development Process
Completed Functions
In-progress Functions
Completion Level Legend
Our Project Management
Project Scope
Change in Project Scope
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 TimelineProject Timeline
Change in Project Schedule
Project Metrics
Schedule Metrics
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
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
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 | 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 |
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 | Medium | B | 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 |
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
Technology Used
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