Team Motiva Mid Term
Project Progress Summary
This section only covers the progress of the project. For more detailed information, refer to our main wiki page here.
The following functions are completed.
- Registration of a new account
- Login and Logout
- Creating of new lifestyle and tagging a project to it.
- Uploading of picture from camera and library
- Randomizing of projects for users
- Filtering of projects by category
- Contribution via PayPal
Project Highlights
- Total of 2 changes raised while development. For more information, click here.
- A total of 58 testers attended our first UAT. Our targeted size was 50.
- PayPal API did not function correctly days before UAT.
Project Management
Project Schedule (Plan VS Actual)
Project Metrics
To know how we manage our schedule, click here
Schedule Metric:
To know how we manage the quality of the product, click here
Bug Metric:
Project Risks
Risk Description | Type | Impact (Low/Medium/High) | Probability (Low/Medium/High) | Rating | Mitigation Strategy | Impact of Strategy |
---|---|---|---|---|---|---|
Client requirements may change during the course of project resulting in change of scope | External | High | High | A | Enforce the scope change process. Ensure that all documentations are up to date and that all members of the team are aware of the scope changes. | More time required on ensuring proper documentation for each change. |
Conflicting clauses in placing charitable transaction based services in the application for Apple AppStore billing system | Business | High | Medium | A | Use an external link which brings user out from the application to a web browser for further payment process | Reduces user experience. |
Submission of application to Paypal for review | Business | Medium | Medium | B | Submit to Paypal as early as possible. Research on the internet for more information on Paypal application submission. | Tighter schedule in developing the application. |
Quality issues like application bugs and synchronization with B1G1 database may surface. | Technical | Medium | Medium | B | Design more test cases and increase testing frequencies each iteration. Engage a higher number of users during User Acceptance Test (UAT) | More time incurred for carrying out more tests and design more test cases |
Minimal professional training on Cocoa (API) and Objective-C programming language used in Mac application development | Technical | Low | Low | C | Source for Apple training program and reading up eBooks from library and internet | More time spent on research, peer sharing sessions and self-learning for the team. |
Technical Complexity
Quality of Product
Intermediate Deliverables
Stage | Specification | Module |
---|---|---|
Project Management | Scope Management | Motiva Scope Management |
Time Management | Motiva Time Management | |
Quality Management - Bug Metric | Motiva Bug Metric | |
Quality Management - UAT | Motiva UAT | |
Communication Management | Client & Supervisor Meeting Minute | |
Requirements | Navigation Flow | Navigation Diagram |
Story Boarding | Story Boarding PDF | |
Analysis | User Interface Prototype | User Interface PDF |
Use Case Diagram | Motiva Use Case | |
Schema Diagram | Motiva Schema Diagram PDF | |
Sequence Diagram | Motiva Sequence PDF | |
Design | ERD | Motiva ERD PDF |
Archiecture Diagram | Motiva Arch. Diagram | |
Testing | Test cases | All test cases used through iteration |
UAT Guide | UAT 1 guide |
Deployment
As our project is iPhone application, provision IDs need to be assigned to devices before it can be used for deployments.
The deployment is done at every end of the iteration and will be connected only to our client's B1G1 staging database.
UAT
The plan for our 1st UAT
While we aimed for 50 testers, a total of 58 testers attended our UAT.
The UAT was carried out over 2 days, 21st and 22nd Sept and 6 devices were deployed.
5 bugs were found during UAT and we had logged it here.
At the end of the testing, testers rated the ease of using our application and the overall user experience.
The results are shown as below:
- 0% for Very Difficult, hence not shown in pie chart.
- 0% for Very Bad, hence not shown in pie chart.