HeaderSIS.jpg

IS480 Team wiki: 2016T2 ProgneSIS Bug Metrics

From IS480
Jump to navigation Jump to search
Progensis.png
Team Prognesis Icon Home.png

HOME

  Team Prognesis Icon AboutUs.png

ABOUT US

  Team Prognesis Icon Overview.png

PROJECT OVERVIEW

  Team Prognesis Icon ProjectManagement.png

PROJECT MANAGEMENT

  Team Prognesis Icon Documentation.png

DOCUMENTATION

 
Project Schedule Schedule Metrics Task Metrics Bug Metrics Risk Management Change Management

Bug metrics - keep track of the bugs that discovered during the application development.
Bugs will be recorded in the bug metrics document during the testing of each function.

Severity Point(s)
Low Impact User interface display errors, such as out of alignment, colour used is not according to theme.

It does not affect the functionality of the system.

High Impact The system is functional with some non-critical functionalities are not working.
Critical Impact The system is not functional.

Bugs have to be fixed before proceeding.

Formula: 1 x No.(Low) + 5 x No.(High) + 10 x No.(Critical)
Point(s) Description
BM <= 5 The system does not need immediate fixing, could be fixed during buffer time or during coding sessions.
5 < BM < 10 Developers to use planned debugging time in the iteration to solve the bug.
BM >= 10 The team has to stop all current development and resolve the bug immediately.

Bug Metrics Score

View our bug log here.

Team ProgneSIS Bug Metrics Score Graph.png

Bugs by Category

Team ProgneSIS Bugs by Category Graph.png

Bugs Summary(by Iteration)


Iteration Bug Score Summary of bugs Action Taken
1 26
1 Critical
3 High
1 Low
1 critical bug was due to undefined session. 3 high bugs were due to incorrect logic to get accurate figures. The team has to stop all current development and resolve the bug immediately.
2 6
1 High
1 Low
1 high bug was due to the missing plots although the JSON format is returned correctly. 1 low bug was due to the datepicker not showing what the user has selected. Developers to use planned debugging time in the iteration to solve the bug.
3 0
0 High
0 Low
No bugs as this iteration is used for change management. The team did major changes in scope.
4 0
0 High
0 Low
No bugs as the UI is not up for testing. Only the backend development is done.
5 6
1 High
1 Low
1 high bug was due to inaccuracy in date conversion. 1 low bug was due to no indication when there's no data for time period. Developers to use planned debugging time in the iteration to solve the bug.
6 6
1 High
1 Low
1 high bug was due to users unable to change password. 1 low bug was due to calculation error in performance growth. Developers to use planned debugging time in the iteration to solve the bug.
7 6
1 High
1 Low
1 high bug was was due to customers unable to change password. 1 low bug was due to the display of information although selected time period does not have data. Developers to use planned debugging time in the iteration to solve the bug.
8 10
2 High
2 high bugs were due to 1) Customer unable to login at times, 2) Data was displayed for customers even during time period without data. The team has to stop all current development and resolve the bug immediately.
9 5
5 Low
5 low bugs were cosmetics - the way the lowest level graphs from the 5 dimensions are displayed. Developers to use planned debugging time in the iteration to solve the bug.
10 10
1 Critical
1 critical bug was due to screen scrape being unable to function on server due to overconsumption of memory. Although it was a critical bug, there were no other development to be done, thus, developers used planned debugging time in the iteration to resolve the bug.
11 & 12 0
0 High
0 Low
User testings were conducted to collate information that sponsor could use to enhance the application as team would not have sufficient time to implement major changes at this stage. -