Difference between revisions of "IS480 Team wiki: 2016T2 Unition final"
Jump to navigation
Jump to search
Xx.xu.2012 (talk | contribs) |
Xx.xu.2012 (talk | contribs) |
||
Line 228: | Line 228: | ||
<h3><big>Testing</big></h3> | <h3><big>Testing</big></h3> | ||
+ | <br> | ||
+ | <big>'''User Acceptance Testing'''</big> <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]] | ||
=<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>= |
Revision as of 10:29, 8 April 2016
Home | About Us | Project Overview | Project Management | Documentation |
Mid-term Wiki | Final Wiki |
---|
Contents
Our Project Process Summary
Final Documentation
Project Highlights
Development Process
Our Project Management
Project Scope
Project Timeline
Midterm
Final
Highlights
Project Metrics
Schedule Metrics
Bug Metric
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 | 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
Technology Used
Our Quality Assurance
Deliverables
Category | Documents | Link |
---|---|---|
Market Research | Market Research | Market Research |
Meeting Minutes | Internal Supervisor |
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 |
User Testing | Testing Plan Testing Cases Testing Result |
Test Plan Test Cases 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