Method and device for analyzing software error

• US 20050204241A1
• Filed: 02/03/2005
• Published: 09/15/2005
• Est. Priority Date: 02/03/2004
• Status: Abandoned Application

• Current Assignee: Panasonic Corporation (Panasonic Holdings Corporation)
• Original Assignee: Matsushita Electric Industrial Company Limited (Panasonic Holdings Corporation)
• Inventors: Tamakoshi, Yasushi
• Application Number:
  US11/048,721
• Publication Number:
  US 20050204241A1
• Time in Patent Office: Days
• US Class Current: 714/741
• CPC Class Codes: G06F 11/3604 Software analysis for verifying properties of programs byte-code verification G06F9/44589

Abstract

In a cause categorization step, bugs are categorized according to technical causes. In a damage evaluation step, how many steps the process has turned back due to a bug is measured. In a damage calculation step, damages are calculated for each bug technical cause. In a problem extraction step, a technical cause of which the damage is large is chosen as a problem. Then, in the bug database search step, a search for a measure for the bug technical cause extracted as a problem is performed with reference with a bug database so as to indicate an appropriate measure for a project.

Claims

1. A method for analyzing software error, the method comprising of:

a cause categorization step of categorizing bugs recorded in an electric bug form according to technical causes;

a damage evaluation step of evaluating damages of the bugs on progress of a project;

a damage calculation step of calculating damage amounts of the bugs for each bug technical cause; and

a problem extraction step of choosing as a problem a bug technical cause of which the damage amount is large.

2. The method of claim 1, wherein the damage evaluation step includes the steps of:

obtaining a bug discovery date and a bug correction verified date from the bug form; and

calculating the number of days from the bug discovery date to the bug correction verified date.

3. The method of claim 1, further comprising the steps of:

an analysis result storage step of storing the damage amount of the bug technical cause in a bug database;

a measure storage step of storing a measure for the bug technical cause in the bug database; and

an effect storage step of storing an effect of the measure for the bug technical cause in the bug database.

4. The method of claim 3, further comprising:

a bug database search step of performing, for the bug technical cause chosen as a problem, a search for the damage amount, measure and effect stored in the bug database and outputting a result of the search.

5. The method of claim 4, wherein the bug database search step further includes the step of arranging records of the search in decreasing order of the damage amount.

6. The method of claim 4, wherein the bug database search step further includes the step of arranging records of the search in decreasing order of the number of same measures.

7. The method of claim 4, wherein the bug database search step further includes the step of arranging records of the search in decreasing order of effect.

8. A device for analyzing software errors, the device comprising:

a cause categorizer for categorizing bugs recorded in an electric bug form according to technical causes;

a damage evaluator for evaluating damages of the bugs on progress of a project;

a damage calculator for calculating damage amounts of the bugs for each technical cause; and

a problem extractor for choosing as a problem a bug technical cause of which the damage amount is large.

9. The device of claim 8, wherein the damage evaluator includes:

an extractor for obtaining a bug discovery date and a bug correction verified date from the bug form; and

a calculator for calculating the number of days from the bug discovery date to the bug correction verified date.

10. The device of claim 8, further comprising:

an analysis result storage for storing the damage amount of the bug technical cause in a bug database;

a measure storage for storing a measure for the bug technical cause in the bug database; and

an effect storage for storing an effect of the measure for the bug technical cause in the bug database.

11. The device of claim 8, further comprising:

a bug database searcher for performing, for the bug technical cause chosen as a problem, a search for the damage amount, measure and effect stored in the bug database and outputting a result of the search.

12. The device of claim 11, wherein the bug database searcher further includes a sorter for arranging records of the search in decreasing order of the damage amount.

13. The device of claim 11, wherein the bug database searcher further includes a sorter for arranging records of the search in decreasing order of the number of same measures.

14. The method of claim 11, wherein the bug database searcher further includes a sorter for arranging records of the search in decreasing order of effect.