HeaderSIS.jpg

IS480 Team wiki: 2015T6 6nificance Bug Metrics

From IS480
Jump to navigation Jump to search

6nificance Logo.png

6nificance-home.png
HOME

6nificance-about-us.png
ABOUT US

6nificance-proj-overview.png
PROJECT OVERVIEW

6nificance-proj-mgmt.png
PROJECT MANAGEMENT

6nificance-docs.png
DOCUMENTATION

Project Schedule Metrics Risks Change Management


SCHEDULE METRICS TASK METRICS BUG METRICS


What: Bug metrics are used to keep track of bugs found during development.
When: Bugs are recorded in the bug metrics document during testing at the end of each iteration.
How: 1 x num (Low Impact) + 5 x num (High Impact) + 10 x num (Critical Impact)

Severity Action
Low Impact Typo error or small user interface alignment issues. Functionality of the application is still stable.
High Impact Though application is functional, some non-critical functions are not working
Critical Impact Application is not functional. Bugs must be fixed before proceeding.
Score Description
BM <= 5 Application does not need immediate fixing, can be fixed during buffer days or coding tasks.
5 < BM < 10 Ultilize planned debugging time in the iteration to rectify the bug.
BM >= 10 Stop all current development and rectify the bug immediately.


Bug Metrics Results


Bug Metric (Score).PNG


Summary of Bug Metrics

Iteration Bug Score Bug Summary Action Taken
1 11
1 Low
2 High
2 high bugs were due to new generated password sometimes not being able to be sent to the user when a new password is requested due to forgotten password as well as user being able to signup with an invalid email. Resolve bugs immediately. End date of iteration 1 is delayed. PM to reschedule end dates and tasks of iterations 2, 3 and 4.
2 12
2 Low
2 High
2 high bugs were due to photo not being scaled to the intended size and RGB value not being equal to the selected color. Used the planned debugging time in iteration 2. Team was able to fix the identified bugs within the planned debugging time.
3 12
2 Low
2 High
2 high bugs were due to concierge module (Back-End Website) not being able to add remarks and having duplicates of name in cloud SQL. Used the planned debugging time in iteration 3. Team was able to fix the identified bugs within the planned debugging time.
4 10
1 Critical
1 critical bug due to application crashing when user presses back upon choosing color in photo. Used the planned debugging time in iteration 4. Team was able to fix the identified bugs within the planned debugging time.
5 17
2 Low
3 High
3 high bugs were due to profile picture not being shown due to problems with uploading images to Cloud Database. Resolve bugs immediately. End date of iteration 5 is delayed. PM to reschedule end dates and tasks of iteration 6.
6 21
1 Low
2 High
1 Critical
1 critical bug was due to app cash when newsfeed refresh is attempted without internet connection. 2 high bugs were due to number of likes and color hashtags not being accurately recorded in database. Resolve bugs immediately. End date of iteration 6 is delayed. PM to reschedule end dates and tasks of iteration 7.
7 29
4 Low
5 High
5 high bugs were due to wrong user profile picture being displayed in the newsfeed, incorrect number of posts sometimes being displayed on user profile and incorrect color tags shown in each post. Resolve bugs immediately. End date of iteration 7 is delayed. PM to reschedule end dates and tasks of iteration 8.
8 10
1 Critical
1 critical bug due to application crash due to out of memory error if application is used for a long period of time. Used the planned debugging time in iteration 8. Team was able to fix the identified bugs within the planned debugging time.
9 15
3 High
3 high bugs due to posts not being sorted properly, profile picture not being shown and blank page being shown when users' profile are shown. Used the planned debugging time in iteration 9. Team was able to fix the identified bugs within the planned debugging time.
10 17
2 Low
3 High
3 high bugs were due to trends not showing the correct number of posts and saved colors Used the planned debugging time in iteration 10. Team was able to fix the identified bugs within the planned debugging time.
11 15
1 High
1 Critical
Loading of incorrect images in newsfeed of social module Used the planned debugging time in iteration 11. Team was able to fix the identified bugs within the planned debugging time.

Test Cases

Download 6nificance Test Cases