HeaderSIS.jpg

IS480 Team wiki: 2015T1 A3XY BugMetrics

From IS480
Jump to navigation Jump to search


A3xy team logo1.png



A3xy HomeIcon.png

HOME

  A3xy UserIcon.png

ABOUT US

  A3xy Project.png

PROJECT OVERVIEW

  A3xy StatsIcon.png

PROJECT MANAGEMENT

  A3xy PapersIcon.png

DOCUMENTATION

 
Project Schedule Schedule Metrics Bug Metrics WP SubPlane.png Risk Management Change Management


Bug Metrics


A3xy finalbug1.png
A3xy finalbug3.png


Iteration Bug Score Summary of Bugs Action Taken
2 15 Most of the bugs were in calling of the web services from BPM. Stop current development and resolve the bug immediately. Project Manager reschedules the project.
3 14 The bugs were mostly due to mapping error in web services which is a minor task. Other bugs were validation errors which were also manageable. Stop current development and resolve the bug immediately. Project Manager reschedules the project.
4 2 Developers did thorough unit and integration testing. Hence, lesser bugs were found in this iteration. The system does not need immediate fixing, could be fixed during buffer time or during coding sessions.
5 13 Most of the bugs were in exposing BPM as a web service and UI improvements. Stop current development and resolve the bug immediately. Project Manager reschedules the project.
7 4 Bugs were related to parsing of XML element. The system does not need immediate fixing, could be fixed during buffer time or during coding sessions.
8 7 Errors involved UI improvements and calling of web services. Use planned debugging time in the iteration to solve the bug.
10 7 Internal error showing in the web services for SWIFT – ISO comparison. Use planned debugging time in the iteration to solve the bug.

Formula


1 x Low Impact Bugs + 5 x High Impact Bugs + 10 x Critical Impact Bugs

Documentation


Severity Description
Low Impact (1 point) Unimportant. Typo error or small user interface alignment issues.
High Impact (5 points) The system runs. However, some non-critical functionalities are not working.
Critical Impact(10 points) The system is down or is un-usable after a short period of time. We have to fix the bugs to continue.


Point(s) Action
BM < = 5 The system does not need immediate fixing, could be fixed during buffer time or during coding sessions
5 < BM < 10 Coders 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