HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
Line 198: Line 198:
 
| '''Schedu Metric''' <br>
 
| '''Schedu Metric''' <br>
 
'''Bug Metric''' <br>
 
'''Bug Metric''' <br>
| [[IS480 Team wiki: 2016T2 Unition documentation|'''Meeting Minutes''']]  
+
| [[IS480 Team wiki: 2016T2 Unition Metrics|'''Metrics''']]
 
|-
 
|-
  
 
! style="background: #65C7E2; color: white; font-weight: bold; width:50px" | Risk Management
 
! style="background: #65C7E2; color: white; font-weight: bold; width:50px" | Risk Management
 
| '''Risk Management''' <br>
 
| '''Risk Management''' <br>
| [[IS480 Team wiki: 2016T2 Unition documentation|'''Meeting Minutes''']]  
+
| [[IS480 Team wiki: 2016T2 Unition Risk Management|'''Risk Management''']]
 
|-
 
|-
  
Line 213: Line 213:
 
! style="background: #65C7E2; color: white; font-weight: bold; width:50px" | Use case Diagram
 
! style="background: #65C7E2; color: white; font-weight: bold; width:50px" | Use case Diagram
 
|'''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''']]
 
|-
 
|-
  

Revision as of 10:21, 8 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


Project Timeline

Midterm

Unition Schedule (5).png

Final

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
Meeting Minutes Internal

Supervisor
Sponsor

Meeting Minutes
Metrics Schedu Metric

Bug Metric

Metrics
Risk Management Risk Management
Risk Management
Technology Diagram Technology and Tools Technology and Tools
Use case Diagram Use Case Diagram Use Case Diagram
Architectural Diagram Architectural Diagram Architectural Diagram

Testing

Our Learning Outcomes