# US 2005/0240903 A1 · Estimating software project requirements for resolving defect backlogs

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2005/0240903 A1
- Document ID: US20050240903A1
- Status: Published application
- Kind: A1
- Application number: 10/828,720
- Filed: 2004-04-21
- Published: 2005-10-27
- Earliest claimed: 2004-04-21
- Assignees: International Business Machines Corporation
- Inventors: John Lake
- Web page: https://patentgrep.com/patent/US20050240903A1

## CPC

- G06Q 10/04: Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem" (market predictions or forecasting for commercial activities G06Q30/0202)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

Methods, apparatus, and computer program products for analyzing defect backlogs that arise in the software development process. Analysis is based on a validity ratio that projects the number of open defects that are likely to actually require fixes, a fix rate that describes the performance of the development team charged with fixing the defects, defect census data, and team performance census data. One outcome of the analysis may be an estimate of the date by which the defect backlog should be resolved. Another outcome of the analysis may be an estimate of the capacity of a team to resolve defects between a given start date and a given target date.

## Claims

### Claim 1

A method for estimating software project requirements, comprising the steps of:
computing a validity ratio for defects in an open state;
computing a fix rate for a team;
analyzing a software defect backlog that includes the defects in the open state, using the computed validity ratio and the computed fix rate.

### Claim 2 (depends on 1)

The method of claim 1, wherein the validity ratio is computed using defect census data read from a defect census data repository.

### Claim 3 (depends on 1)

The method of claim 1, wherein the fix rate is computed using team performance census data read from a team performance census data repository.

### Claim 4 (depends on 1)

The method of claim 1, wherein the step of computing a validity ratio includes steps of adding numbers of defects in working, verify, and closed states, to provide a first sum; adding numbers of defects in the working, verify, and closed states and a number of defects in a canceled state, to provide a second sum; and dividing the first sum by the second sum, to provide the validity ratio.

### Claim 5 (depends on 4)

The method of claim 4, wherein the step of computing a fix rate includes steps of adding the number of defects in the close state and the number of defects in the verify state, to provide a third sum; and dividing the third sum by a number of working days, to provide the fix rate.

### Claim 6 (depends on 5)

The method of claim 5, wherein the step of analyzing a software defect backlog includes a step of computing a drain date for the backlog, using the validity ratio and the fix rate.

### Claim 7 (depends on 6)

The method of claim 6, wherein the step of computing a drain date includes steps of multiplying the number of defects in the open state by the validity ratio to provide a product; adding the product to the number of defects in the working state, to provide work left; dividing the work left by the fix rate, to provide days left; and adjusting the days left for non-working days, to provide the drain date.

### Claim 8 (depends on 5)

The method of claim 5, wherein the step of analyzing a software defect backlog includes a step of computing a capacity of a team to fix defects, using the validity ratio and the fix rate.

### Claim 9 (depends on 8)

The method of claim 8, wherein the step of computing a capacity includes steps of multiplying a number of working days by the fix rate, to provide a product; and dividing the product by the validity ratio, to provide the capacity.

### Claim 10

A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform method steps for estimating software project requirements, said method steps comprising:
computing a validity ratio for defects in an open state;
computing a fix rate for a team;
analyzing a software defect backlog that includes the defects in the open state, using the computed validity ratio and the computed fix rate.

### Claim 11 (depends on 10)

The program storage device of claim 10, wherein the validity ratio is computed using defect census data read from a defect census data repository.

### Claim 12 (depends on 10)

The program storage device of claim 10, wherein the fix rate is computed using team performance census data read from a team performance census data repository.

### Claim 13 (depends on 10)

The program storage device of claim 10, wherein the step of computing a validity ratio includes steps of adding numbers of defects in working, verify, and closed states, to provide a first sum; adding the numbers of defects in the working, verify, and closed states and a number of defects in a canceled state, to provide a second sum; and dividing the first sum by the second sum, to provide the validity ratio.

### Claim 14 (depends on 13)

The program storage device of claim 13, wherein the step of computing a fix rate includes steps of adding the number of defects in the closed state and the number of defects in the verify state, to provide a third sum; and dividing the third sum by a number of working days, to provide the fix rate.

### Claim 15 (depends on 14)

The program storage device of claim 14, wherein the step of analyzing a software defect backlog includes a step of computing a drain date for the backlog, using the validity ratio and the fix rate.

### Claim 16 (depends on 15)

The program storage device of claim 15, wherein the step of computing a drain date includes steps of multiplying the number of defects in the open state by the validity ratio, to provide a product; adding the product to the number of defects in the working state, to provide work left; dividing the work left by the fix rate, to provide days left; and adjusting the days left for non-working days, to provide the drain date.

### Claim 17 (depends on 14)

The program storage device of claim 14, wherein the step of analyzing a software defect backlog includes a step of computing a capacity of a team to fix defects, using the validity ratio and the fix rate.

### Claim 18 (depends on 17)

The program storage device of claim 17, wherein the step of computing a capacity includes steps of multiplying a number of working days by the fix rate, to provide a product; and dividing the product by the validity ratio, to provide the capacity.

### Claim 19

Apparatus for estimating software project requirements, comprising:
a defect census data repository;
a team performance census data repository; and
an estimation engine for computing a validity ratio for defects in an open state, using information from the defect census data repository; computing a fix rate for a team, using information from the team performance census data repository; and analyzing a software defect backlog that includes the open defects, using the computed validity ratio and the computed fix rate.

### Claim 20 (depends on 19)

The method of claim 19, wherein analyzing a software defect backlog includes computing a drain date for the backlog, using the validity ratio and the fix rate.

### Claim 21 (depends on 19)

The method of claim 19, wherein analyzing a software defect backlog includes computing a capacity of a team to fix defects, using the validity ratio and the fix rate.
