JP2001222422A - Process control device - Google Patents

Abstract

(57) [Summary] [Problem] To easily determine the possibility of delay in a process by graphically displaying the status of a defect measure in the development of software or hardware. [MEANS FOR SOLVING PROBLEMS] A test item count management table storing a planned value of test item digestion count and an actual value of test item digestion count, a planned value of defect extraction count, an actual value of defect extraction count, and a countermeasure status of defect extraction count. A defect count management table storing the number of test items and a display device are provided, and the display device has a scheduled value 304 of the number of test item digests, an actual value 305 of the test item digest count, and a scheduled value 30 of the defect extraction count.
6. The actual value 307 of the number of defective cases and the number of cases 308 of the number of defective cases according to the countermeasure status are displayed in a graph for each first predetermined period.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a process control device, and more particularly to a quality control device which is visually displayed so that a defect countermeasure status can be instantaneously grasped in the development of software or hardware.

[0002]

2. Description of the Related Art Japanese Unexamined Patent Publication No. 8-212107 discloses a graph of a test situation in software development.
It is shown to be displayed as a quality control chart. The graph is a line graph with the number of remaining test items and the total number of failures on the vertical axis and the number of test days on the horizontal axis. By displaying this graph, the status of digestion of test items and the status of occurrence of defects are grasped, and the quality of software is determined. Further, by displaying a breakdown by function using a table below the graph, more detailed information is displayed.

[0003]

SUMMARY OF THE INVENTION The above-mentioned Japanese Patent Application Laid-Open No. 8-212 is disclosed.
In the method disclosed in Japanese Patent Publication No. 107-107, it is possible to grasp the digestion status and the failure extraction status of the test items up to the present.
However, it does not indicate the degree of countermeasures taken for the extracted defect. Therefore, there is a possibility that a large amount of unmeasured defects may occur due to delay in finding unmeasured defects. When such a large number of unmeasured failures occur, which delays the process, it has been difficult to predict them. Also, it was difficult to determine whether the tests in the design department were sufficiently performed.

SUMMARY OF THE INVENTION The present invention has been made in view of the above-mentioned problems, and a visual display is provided so that a defect countermeasure situation can be instantaneously grasped in the development of software or hardware, thereby facilitating the possibility of occurrence of a process delay. It is possible to make a judgment. It also provides material for determining whether the tests in the design department have been sufficiently performed.

[0005]

The present invention employs the following means in order to solve the above-mentioned problems.

[0006] A test item count management table storing the planned value of the number of test items and the actual value of the number of test items, and the planned value of the number of defective items, the actual value of the number of defective items, and the number of defective items by countermeasures. And a display device for calculating and displaying the contents of these tables. The display device includes a scheduled value of the number of test items consumed, an actual value of the test item consumed number, and a defect extraction number. The daily scheduled value, the actual value of the number of defective extractions, and the number of defective extractions by countermeasure status are displayed daily in a graph. In addition, the display device displays a graph of the number of defective cases by countermeasure status, for example, every three days. Further, predicted values such as the final number of defective cases and the defect extraction rate are displayed.

[0007]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to FIGS. FIG. 1 is a diagram showing a system configuration of a quality management device according to an embodiment of the present invention. In the figure, 101 is a server, 102 is a database installed in the server, 103 is a communication network such as a LAN, and 104 is a plurality of client PCs (personal computers) connected to the server 101 via the communication network 103.

First, the user operates the client PC 104 at the time of setting a test item, and sets the test schedule item information 1
05 and expected defect count information 106, and various test information such as test digest count information 107 and defect extraction count information 108 during the test. The input information is transmitted to the server 101 via a communication network 103 such as a LAN, and stored in a database 102 installed in the server 101.
Further, the client PC 104 can acquire the stored data via the communication network 103 and display the quality management information as a quality management chart as described later.

FIG. 2 is a diagram showing a main body of the quality control device formed by the client PC. In the figure, reference numeral 200 denotes a quality management device formed by a client PC, and reference numeral 201 denotes a processing unit, which includes a quality management program and performs display, update, printing, and the like of quality management information by user operation. An input unit 202 inputs the various test information. Further, the quality control chart displayed on the output unit 203 is edited. An output unit 203 displays the quality control chart, quality control information prediction result, check result, and the like. A storage unit 204 stores the quality management program or the quality management information and the like, and a line connection unit 205 connects to the server 101 via the communication network 103.

FIG. 3 is a diagram showing an example of a quality control chart displayed on the display device of the client PC 104. The quality control chart includes a test item digestion status graph 300 and a test item digestion status table 310 including data for generating the test item digestion status graph 300.
A test item digestion status graph 300 is displayed on the display device 104.
And one or both of the test item digestion status table 310 can be displayed.

In the test item status graph 300, the left scale 301 on the vertical axis indicates the number of remaining test items, the right scale 302 indicates the number of defective items extracted, and the horizontal axis 30
3 indicates a test date. Line graphs 304 and 305
Indicates the planned number of actual test items and the actual number of test items. Also, the line graphs 306 and 307 show the planned number and the actual number of defective cases. In addition, bar graph 3
08 indicates the number of defective cases extracted by the countermeasure status. For example, the black-filled portion of the bar graph indicates the number of corrected defects, the gray-colored portion indicates the number of corrected countermeasures due to specification changes, and the white portion indicates the number of causes under investigation. The line graphs 304, 305, 306, and 307 display graphs based on daily data. The bar graph 308 may be displayed every day like the line graph, but is displayed every predetermined period, for example, every three days. This makes it easier to see the graph display. By displaying the countermeasure status in this way, the countermeasure status can be visually and instantaneously grasped.

Further, in the test item digestion status table 310, the planned number of test item digests and the actual number of test items 31 are shown.
1 is arranged in a row and the test date 312 is arranged in a column to form a table, and the test status data 313 for each day is entered in this table. Defects by countermeasure status can be categorized as countermeasures completed, countermeasures taken by changing specifications, under investigation of causes, and the like.

Next, a display process of the quality control device will be described with reference to FIGS. 4 to 7 are diagrams for explaining the display processing of the quality control device. FIG. 5 is a diagram for explaining the details of step 403 in FIG. 4, and FIGS. 6 and 7 are examples of steps 407 and 408 in FIG. FIG.

First, in step 401, the quality management device 200 obtains test item digestion count data and defect extraction count data for each countermeasure status from the database 102. In step 402, from the acquired test item digestion count data and defect extraction count data, the planned and actual counts of the remaining test item counts and the planned and actual counts of the defect extraction counts are calculated, and the line graph 3 is obtained.
04, 305, 306 and 307 are displayed. In step 403, the data of the number of defective picked-up cases according to the countermeasure status is calculated, and a bar graph 308 is displayed every three days. In step 404, the process waits for a user operation. When the user operates the quality control device, the process proceeds to step 405. In step 405, the type of the operation is determined.
Then, if the type of operation is the end operation, the process ends. If the type of operation is a quality check or a quality prediction, the process proceeds to step 407. In step 406, the data in the database 102 is updated, and in step 4
Go to 02. Steps 407 and 40
8, a display for quality check or quality prediction, that is, a predicted value of the number of defective items to be extracted as described later,
After displaying the number of unmeasured defects, the predicted value of the defect extraction rate, and the reference value of the defect extraction rate, the process proceeds to step 404.

Next, the details of step 403 will be described with reference to FIG. First, in step 501, a display interval for displaying the bar graph 308 is acquired from the storage unit 204. In step 502, 1 is substituted for a variable N.
In step 503, it is determined whether or not N is less than or equal to the number of test days.
Proceed to 04, otherwise terminate the process. In step 504, it is determined whether or not it is a multiple of the display interval (for example, 3 days) of the bar graph 308. If it is a multiple, the process proceeds to step 505; otherwise, the process proceeds to step 506. In step 505, the bar graph 308 is displayed, and the process proceeds to step 506. In step 506,
Substitute N + 1 for N and go to step 503.

Next, an example of steps 407 and 408, that is, an example of displaying the predicted value of the number of detected defects and the current value of the number of unmeasured defects will be described with reference to FIG. First, in step 601, the total number of test items and the number of digested test items are stored in the database 102.
To get from. In step 602, the digest rate of the test item is calculated by (current test item digest number / total number of test items). In step 603, the current number of defective cases is acquired from the database 102. In step 604, a predicted value of the final number of defective items to be extracted is calculated from (number of defective items to be extracted / digestibility of test items). In step 605, the number of unmeasured defective cases is obtained from the database 102. In step 606,
The current number of defective cases obtained in step 603 (actual value), the predicted value of the final number of defective cases calculated in step 604, and the number of unmeasured defective cases obtained in step 605 are displayed.

Next, another example of steps 407 and 408, that is, an example of displaying the predicted value of the defect extraction rate and the reference value of the defect extraction rate after the design completion date of the design department with reference to FIG. explain. First, in step 701, the design completion date of the design department is acquired from the database 102. In step 702, the total number of test items obtained after the design completion date of the design department and the number of digested test items up to now are acquired from the database 102. In step 703, the digest rate of the test items after the design completion date is calculated from (the digest count of test items up to the present / the total number of test items). Step 704
In the database 10
Obtain from 2. In step 705, a predicted value of the final number of defective items to be extracted is calculated from (the number of defective items to be extracted to date / digestibility of test items). In step 706, the size of the development target (for example, the number of program lines in the development target software) is acquired from the database 102. In step 707, using the predicted value of the number of final defective items calculated in step 705 and the scale of the development object obtained in step 706, the predicted value of the final defective item extraction rate Value / scale of development target). In step 708, a reference value of the defect extraction rate is obtained from the database 102. In step 709, the predicted value of the final defect extraction rate calculated in step 707 and step 7
The reference value of the defective extraction rate acquired in step 08 is displayed.

FIG. 8 is a diagram showing an example of display contents displayed on the display device of the client PC 104 when the operator selects the quality check or the quality prediction in step 405 shown in FIG. 8 is an example of a display screen displayed in step 606 of FIG. 6, and FIG. 8B is an example of a display screen displayed in step 709 of FIG.

FIG. 9 is a diagram showing an example of tables stored in the database 102. In each table, a shaded portion indicates a primary key of the table. In the figure, 901
Is a test item count management table.
The process and the number of test item digests for each test date are stored, and in step 401 shown in FIG. 4, the planned value and the actual value of the remaining test item number shown in FIG. 3 are provided. Also, step 601 in FIG. 6 and step 702 in FIG.
Provides the total number of test items.

Reference numeral 902 denotes a defect count management table which stores the defect extraction count for each project, process, and countermeasure status for each test date.
Step 505 is used to display the line graphs 306 and 307 of the planned value and the actual number of defective extractions in FIG. 3 and the bar graph 308 of the number of defective extractions by countermeasure status. Also, in step 601 of FIG. 6 and step 704 of FIG. 7, the number of defective extractions is provided.

Reference numeral 903 denotes a development schedule management table, which stores process start dates and end dates for each project and each process. Further, the end date (actual result) of the last process of the design department in the above process is used as the design completion date of the design department in step 701 of FIG.

A scale management table 904 stores the development scale of each program as a value indicating the development scale of the project. This development scale is used as the scale of the development target in step 706 of FIG.

As described above, according to this embodiment, in the quality control of software or hardware, the quality status can be automatically tabulated and displayed, and the quality status can be easily grasped. Has the effect of

(1) By visually and digitally displaying the number of test items and the number of failures by countermeasure status in the quality control chart, the countermeasure status of the failure can be grasped visually and in detail.

(2) By predicting the number of defective cases and displaying the number of unprocessed defective cases, the quality can be grasped and the test process delay can be found at an early stage, so that measures can be taken at an early stage.

(3) It is possible to know whether the test has been sufficiently performed by the design department by totalizing and displaying the number of defects generated after the date when the design department completed the design. It is possible to take countermeasures such as reviewing in the department.

[0027]

As described above, according to the present invention, the status of the measure against failure is graphically displayed in the development of software or hardware, so that it is possible to easily judge the possibility of a delay in the process. Further, it is possible to easily determine whether or not the test in the design department has been sufficiently performed.

[Brief description of the drawings]

FIG. 1 is a diagram showing a system configuration of a quality management device according to an embodiment of the present invention.

FIG. 2 is a diagram showing a main body of a quality management device formed by a client PC.

FIG. 3 is a diagram showing an example of a quality control chart.

FIG. 4 is a diagram illustrating a display process of the quality management device.

FIG. 5 is a diagram illustrating details of a display process of the quality management device.

FIG. 6 is a diagram illustrating details of display processing of the quality management device.

FIG. 7 is a diagram illustrating details of display processing of the quality management device.

FIG. 8 is a diagram illustrating an example of display content displayed on a display device.

FIG. 9 is a diagram illustrating an example of a table stored in a database.

[Explanation of symbols]

 Reference Signs List 101 server 102 database 103 communication network 104 client PC 200 quality management control device 201 processing unit 202 input unit 203 output unit 204 storage unit 205 line connection unit

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Noboru Yamashita No. 1 Ikegami, Haruoka-cho, Owariasahi-shi, Aichi Prefecture F-term in the Information Equipment Division, Hitachi, Ltd. 5B076 EC09 5E501 AC10 AC13 AC17 AC35 BA03 DA11 FA14 FA23

Claims (5)

[Claims] 1. A test item count management table storing a planned value of the number of test items and an actual value of the number of test items, a planned value of the number of defective items, an actual value of the number of defective items, and a countermeasure status of the number of defective items. A defect count management table storing different counts, and a display device, the display device has a planned value of the number of test items consumed, an actual value of the test item consumed number, a planned value of the number of defective items extracted, and an actual result of the number of defective items extracted A process management apparatus characterized in that a value and the number of defective cases according to countermeasure status are displayed in a graph for each first predetermined period. 2. A process management method according to claim 1, wherein the number of defective cases according to the countermeasure status is displayed in a graph for each second predetermined period that is longer than the first predetermined period. apparatus. 3. The display device according to claim 1, wherein the display device calculates a predicted value of a final defect extraction number calculated from the current defect extraction number and a test item digestion rate, and a current defect extraction number. A process management apparatus, wherein the number of defective picked-up items is switched and displayed on the graph display. 4. The process management device according to claim 1, wherein the display device displays a predicted value of a final value of the defect extraction rate after the completion of the design. 5. The predicted value of the final value of the defect extraction rate according to claim 4, wherein the predicted value of the final value of the defect extraction rate is a predicted value of the final defect number calculated from the current defect extraction number after the design completion date and the test item digestibility. And a process control device for calculating from the scale of the program to be developed.