defect tracking

Articles

Problem Resolution Optimization

No matter how well we plan and execute software development, defects are generated and can escape to the customers. Failure to quickly resolve software problems leads to negative consequences for our customers and increases internal business costs. A quick deterministic
method to prioritize problems and implement their solution helps to reduce cycle time and costs. Achieving this goal requires several steps. The first is to determine a model that links problem resolution performance to institutional variables and problem characteristics. Statistical Design of
Experiments (DOE) is a tool that provides data requirements for estimating the impacts of these variables on problem resolution. Once data has been gathered, the results of statistical analysis can be input into a mathematical optimization model to guide the organization.
This paper describes such an analysis.

Don Porter
Bug Movie

Lights. Camera. Action! This article suggests using multimedia tools that combine a visual display, voice recording, and screen annotations to illuminate the steps required to isolate a bug. The result is an effective means of simplifying the process for both testers and developers. Yogita explains the benefits and risks associated with producing your own bug movie.

Yogita Sahoo's picture Yogita Sahoo
Software Bug Report Sample (template)

This is a sample bug reporting template for accounting and financial software software that includes description, severity, priority levels, and bug solution categories.

Khaja Ahmed's picture Khaja Ahmed
Categorizing Defects by Eliminating "Severity" and "Priority"

With all of the advancements in defect tracking systems within the past few years, companies are still using the same ambiguous, canned fields known as Severity and Priority to categorize their defects. Let's examine a better way to assign importance to a defect.

Brian Beaver
Software Test Incident Report IEEE 829-1998 Format (template)

This Software Test Incident Report template is based on the IEEE 829-1998 test standard and additional information added from various sources—actual test plans, instructor experience, student comments, etc.

Wayne Middleton's picture Wayne Middleton
Counting Defects

Defect counts are often considered as measurements of product quality. However, the most important defect count in that respect is by definition unknown; the number of undiscovered errors. Defect counts can be used as indicators of process quality. In doing so, one should avoid assuming simple causal relations. Defect counts can provide useful information but have to be presented with care.

Bert Wijgers's picture Bert Wijgers
Software Development Lifecycle: Defect and Test Case Measurement

This article focuses on how to manage the defect and test case measurement during the software development lifecycle. This should be a practical resource for software developers and project managers.

Steve Miller
Defect Depletion and Cost Analysis (template)

You can use this spreadsheet to demonstrate the value of early defect removal. It includes defect depletion curves or phase containment effectiveness calculations.

Ed Weller's picture Ed Weller

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.