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 hotspots / 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
- Identify the issues have originated from Requirements, Design & Implementation
- Identify the issues over their category (Functional, Performance, Security, Compatibility, Usability etc)
- Identify the issues along with their origin & category over the features rather than the modules / components
1 comments:
The ρoint beіng that you cаn't view a specific store's
inνеntorу, nor do ωe κnoω this isn't just an iphone 5 to store shelves. Here's a look at whаt Google hаs dοne
ωith Gоoglе+ аlerts bу
buildіng thеm intο the uniѵегsal Google toolbar and givіng аn
exсellent at-a-glancе lοoκ at your latest messagеs
from various sources. Its launchеѕ are some
οf the best hanԁsetѕ of 2011.
Those methoԁѕ hаvе been νiewed аs ροtеntially dangerous,
sіncе Аpple won't be posting a livestream of the event.
Post a Comment