Ability to identify the hot spots of release from Bug Database


Bug Database for the products might have thousands of issues over a period of time against various builds and releases. Though these issues fixed over a period of time, it might be hard to derive meaningful metrics over the release.

We need to support these releases over the production systems & it might be helpful to capture the hot spots / risk elements with the release. Most of the issues here to deal with the respective features, compatibility with other features / technologies & performance related issues.

The usual metrics of number of issues against a module and their severity levels may not be of help always.

How easy is it to derive the following from the Bug Database for a given release

  1. Identify the issues have originated from Requirements, Design & Implementation
  2. Identify the issues over their category (Functional, Performance, Security, Compatibility, Usability etc)
  3. Identify the issues along with their origin & category over the features rather than the modules / components

A JN0-201 as well as an HP0-053 renders one prepared for HP0-922. However, for 000-253, some extra courses are required.

Share and Enjoy:
  • Print
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Blogplay
  • Blogosphere News
  • DZone
  • FriendFeed
  • LinkedIn
  • Reddit
  • StumbleUpon
  • Technorati
  • Tumblr
  • Twitter
  • Share/Bookmark

Subscribe / Share

Article by Venkat Reddy Chintalapudi

Authors bio is coming up shortly. Venkat Reddy Chintalapudi tagged this post with: , , , , , , , , , , , Read 29 articles by Venkat Reddy Chintalapudi
It's very calm over here, why not leave a comment?

Leave a Reply




Twitter Updates

Recent Trackbacks

Google Search