IS480 Team wiki: 2016T2 LOCK FinalWiki
HOME | ABOUT US | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
Contents
OUR PROJECT PROGRESS
Team LOCK FINALS Documentation
Summary of Project
Our Development Progress
OUR PROJECT MANAGEMENT
Project Scope
Acceptance | Midterms |
---|---|
Final Project Scope!
Highlights of Changes Made in Scope
- Dropped Secondary Functions I
- Dropped Good-To-Have Functions
Project Schedule
Highlights of Changes Made in Schedule
Metrics
Schedule Metric
Highlights of Schedule Metrics
Iteration | Planned (Days) | Actual (Days) | SM Score | Action | Status |
---|---|---|---|---|---|
- | - | - | - | - | - |
Bug Metric
iOS | Android |
---|---|
Highlight of Changes in Collection of Bugs
There was a huge spikes of bugs found in iteration 7 & 8 (both iOS & Android). This was largely due to the fact this was the period where our team was solely focusing on cleaning up our application(Fixing of bugs/UI) in preparation for Soft-Launch.
Iteration | Bug Score | Summary of Bugs and Issues | Action Taken |
---|---|---|---|
7 | 65 (iOS) , 34 (Android) | In this iteration, our client proposed an entire UI overhaul for our application. We responded to this with proper discussions, and agreed to the new UI based on our consensus to improve the overall usability and design of our application. This resulted in a full-scale change as we shifted away from the old UI, with the addition of new functions. And because of the immense changes, the conversion of the old UI to new UI required changes to the logic behind the UI as well. This led to the discovery and birth of many bugs during this iteration. | Stop current development and resolve bugs immediately. Seek to solve all the minor bugs and issues during the allocated debugging period of the iteration. (Next iteration - 8) |
8 | 48 (iOS) | In this iteration, our team was preparing for the soft-launch of our application, making sure that our application was bug free and user friendly. As there were new several critical bugs found in our application, following our schedule all work was put on hold to ensure that these bugs was resolved before moving foward | Stop current development and resolve bugs immediately. All bugs and issues were resolved during allocated debugging period of the iteration. |
12 | 35 (iOS) | In this iteration, our team was building up new functions relating to Career Buddy. Therefore, there were a very critical bugs found whilst going our iteration | Stop current development and resolve bugs immediately. All bugs and issues were resolved during allocated debugging period of the iteration. |
Full documentation of our issue tracker is available on our Test Documents which can be found here!(Android) & here!(iOS)
Project Risks
Technical Complexity
How we design our Architecture?
Project Complexity
OUR QUALITY ASSURANCE
Deliverables
Type | Decription | Documentation |
---|---|---|
Requirement Gathering | Market Research | Market Research |
Project Management | Minutes, Metrics, Risks, Change | |
Analysis and Design | Use Case, Architectural Diagram, ER Diagram, Technology and Tools Used | Use Case, Architectural Diagram, ER Diagram, Technology and Tools Used |
Testing | User Test Plan |
Testing
As at 20th February 2016, we have completed 2 User Testing. These activities are primarily conducted to ensure that the StaffOnDemand Mobile satisfies the needs of our target group as agreed upon with our Sponsors and provides confidence of its use.
User Testing 1
- Number of Users: 30
- Venue: SOE-SR3.1
- Date: 3rd – 5th November 2015
- Duration: 15 minutes per user
- Test Platform: Android Mobile Device , iOS
Objective:User Testing is conducted to ensure that StaffOnDemands satisfies our target consumer group and meets the expectations of sponsors and users. In this User Testing, we are primarily focusing on :
- Usability and intuitiveness of functions
- Find bugs / defects in the application
User Testing 2
- Number of Users: 42
- Venue: SOE-SR-3.1 | SOE SR-2.7
- Date: 15th January 2015
- Duration: 15 minutes per user
- Test Platform: Android Mobile Device , iOS
Objective:User Testing is conducted to ensure that StaffOnDemands satisfies our target consumer group and meets the expectations of sponsors and users. In this User Testing, we are primarily focusing on :
- Gathering feedback from potential stakeholders with regards to the heuristics and design of the existing functions of the current application
- Identify any usability issues that persist in the application
- Improvement of our application based on the results
User Testing 3
- Number of Users: 10
- Venue: At user's convenience
- Date: 11th April 2016
- Duration: 20 minutes per user
- Test Platform: Android Mobile Device , iOS
Objective:User Testing is conducted to ensure that StaffOnDemands satisfies our target consumer group and meets the expectations of sponsors and users. In this User Testing, we are primarily focusing on :
- Gathering feedback from potential stakeholders with regards to the heuristics and design to the newly implemented functions