JP2007241347A - Program quality management device, and method for creating quality management report of program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a technique for quality management of a program for managing processes from design to manufacture and testing of the program in a consistent way. <P>SOLUTION: A program quality management device includes: a minute input screen 100 for inputting minutes when specifications described in program units are reviewed during a design process; a quality input screen 200 for accepting the input of test results when a program code manufactured according to the specifications is tested during a test process; a minute data storage part 10; a quality data storage part 20; and a quality management report creating part 80 for creating a quality management report 500 about the design process and the test process and outputting the quality management report 500 created. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a technique for quality control of a computer program.

In software development, Patent Document 1 discloses a system for managing a project based on a predetermined development plan and quality standards.
JP 2005-55993 A

  In order to manage the quality of software, it is more preferable not only to manage the test results of the manufactured program code, but also to perform quality control at the design document stage of the program and to combine them.

  Further, in order to realize a function related to a certain business requirement, it is often realized by combining a plurality of programs. For this reason, in addition to quality control of a single program, it is also necessary to perform quality control by grouping a plurality of programs.

  Accordingly, an object of the present invention is to provide a technique for quality control of a program for consistently managing from a program design process to a manufacturing and test process.

  A quality control apparatus for a program according to an embodiment of the present invention includes a means for receiving an input of a review result when a design document described in a program unit is reviewed in a design process; Means for accepting input of a test result obtained by executing a test of a program code manufactured based thereon, storage means for storing the review result and the test result in association with each other, design process and test with reference to the storage means Reporting means for generating a quality control report of the process and outputting the generated quality control report.

  In a preferred embodiment, the management identification information further includes means for storing program identification information for identifying a program and management identification information for grouping and managing a plurality of programs in association with each other. A plurality of program identification information may be associated with each other, and the report unit may generate and output the quality management report for each management identification information unit.

  In a preferred embodiment, means for storing quality control index reference values for a design process and a test process, means for calculating a quality control index based on the review result and the test result, and the calculated quality And a means for comparing the management index with the reference value of the quality index. In this case, the report unit may generate the quality control report based on the comparison result of the comparison unit.

  Hereinafter, a quality management system for a program according to an embodiment of the present invention will be described with reference to the drawings. This system performs quality control in each process from program design (external design, internal design, detailed design) to manufacturing and testing.

  The program quality management system according to the present embodiment is configured by, for example, a general-purpose computer system, and individual components or functions in the system described below are realized by executing, for example, a computer program. .

  FIG. 1 is a diagram showing a functional configuration of a quality management system for a program according to the present embodiment.

  The system stores a minutes input screen 100, a minutes data storage unit 10 for storing information input to the minutes input screen 100, a quality input screen 200, and information input to the quality input screen 200. Quality data storage unit 20, item registration screen 300, item table 30 generated based on information input to item registration screen 300, minutes data stored in minutes data storage unit 10, and quality A data editing unit 60 that integrates quality data stored in the data storage unit 20, an integrated data storage unit 40 that stores data integrated by the data editing unit 60, and a management index that stores a management index for quality control A storage unit 50 and a generation unit 80 that generates a quality control report are provided.

  In the quality management system according to the present embodiment, a plurality of programs can be managed with one program as a minimum management unit. At this time, each program is identified by the program ID. In the program, a design document is created in the design process, and a program code is manufactured in the manufacturing process based on the design document. Therefore, a common program ID is assigned to a program for realizing a certain function throughout the entire process.

  The system according to the present embodiment can further manage a plurality of programs as one group. This group to be managed is called a case, and each case is identified by a case ID. This is because, by grouping, a plurality of programs for realizing a function related to a certain business requirement are collectively managed.

  The case registration screen 300 is a screen for registering a case which is one management unit in this system. That is, the user can use the case registration screen 300 to define the correspondence between one case ID and a plurality of program IDs. Then, the defined correspondence is registered in the case table 30. Thereby, if the case ID is specified, a plurality of program IDs included in the case can be specified.

  FIG. 2 shows an example of the minutes input screen 100.

  The minutes input screen 100 is a screen for inputting the minutes of the review when the design document created in the program design process is reviewed.

  The minutes input screen 100 includes a basic information input screen 110 and a detailed information input screen 130 as shown in FIG.

  The basic information input screen 110 receives input of basic information related to reviews. That is, the basic information input screen 110 includes a case ID 111, a program ID 112, a review attendee 113, a review execution date 114, a circulator of this minutes 115, a person in charge of this program 116, a review category 117, a review theme 118, Each of the input areas for receiving the number of pages 119 of the design document that has been reviewed has a minutes update button 120 for registering the input contents.

  The design document to be reviewed is uniquely identified by the program ID. When inputting the program ID 112, the program ID associated with the case ID 111 may be acquired from the case table 30 and selectable from the program ID.

  As the number of pages 119 of the design document, the number of pages is input according to the difficulty of creating the design document.

  When the minutes update button 120 is pressed, information input on the basic information input screen 110 is stored in the minutes data storage unit 10 as basic information 15 (see FIG. 3) described later.

  The detailed information input screen 130 accepts input of specific agenda contents and the like in the review. That is, the detailed information input screen 130 includes input areas for agenda content 131, countermeasure 132, agenda category 133, scheduled countermeasure date 134, countermeasure completion date 135, and countermeasure person 136.

  In the agenda content 131, specific agenda content in the review (for example, problems, future issues, comments, etc.) is described in text.

  The countermeasure 132 is related to the agenda described in the agenda content 131 and specifically describes the countermeasure when necessary. When no countermeasure is particularly required, the description of the countermeasure 132 can be omitted.

  The agenda classification 133 is for classifying the contents of the agenda. For example, “points to be pointed out” and “comments” are set in advance in the agenda category 133, and the user can select from among them.

  In general, the minutes of a meeting are often itemized by item. Therefore, in this system, when describing the contents of agenda items for a plurality of items, it is possible to describe by item by depressing the detail addition button 137 after describing the one item on the detail information input screen 130. Become. In other words, when the detail addition button 137 is pressed, the contents already described on the detail information input screen 130 are stored in the minutes data storage unit 10 as detail information 17 (see FIG. 3) to be described later. The screen 130 is cleared, and the next agenda content can be described. In this way, on the minutes input screen 100, the contents of a plurality of items can be registered for the basic information input on the basic information input screen 110.

  FIG. 3 shows the data structure of the minutes data storage unit 10.

  As shown in FIG. 3A, the minutes data stored in the minutes data storage unit 10 is registered in association with a plurality of detailed information 17 for one basic information 15. The basic information 15 is information input on the basic information input screen 110. The detail information 17 is information input on the detail information input screen 130.

  As shown in FIG. 3B, the basic information 15 includes a case ID 151, a program ID 152, a review execution date 153, a review category 154, a review theme 155, an attendee 156, a circulator 157, and a person in charge 158. And are included. These are all information input on the basic information input screen 110.

  As shown in FIG. 3C, the detailed information 17 includes agenda content 171, countermeasure 172, agenda classification 173, scheduled countermeasure date 174, countermeasure completion date 175, and countermeasure staff 176. These are all information input on the detailed information input screen 130.

  FIG. 4 shows an example of the quality input screen 200. The quality input screen 200 is a screen for inputting the contents and results of tests performed in the test process (unit test process) of the program.

  The quality input screen 200 includes input areas for a case ID 211, a program ID 212, a difficulty 213, a review indication number 214, a page number 215, a step number 216, a test case number 217, a bug occurrence number 218, and a coverage rate 219.

  The quality input screen 200 receives input in units of programs. When inputting the program ID 212, the program ID associated with the case ID 111 may be acquired from the case table 30 and selectable from the program ID.

  The page number 215 is the number of design document pages.

  In the number of steps 216, the number of parameters, the final scale, the number of steps of addition, correction, deletion, and automatic generation are input.

  FIG. 5 shows the data structure of the quality data storage unit 20. The quality data storage unit 20 stores information input on the quality input screen 200.

  As shown in the figure, the quality data stored in the quality data storage unit 20 includes a case ID 21, a program ID 22, a difficulty level 23, a review indication number 24, a page number 25, a step number 26, and a test. A case number 27, a bug occurrence number 28, and a coverage rate 29 are included.

  The data editing unit 60 reads and edits the minutes data stored in the minutes data storage unit 10 and the quality data stored in the quality data storage unit 20. For example, the data editing unit 60 calculates a quality management index described below. Then, the data editing unit 60 merges the minutes data, the quality data, and the calculated management index using the program ID as a key, and stores the merged data in the integrated data storage unit 40.

  The management index storage unit 50 stores process-specific reference values for various management indexes. This management index is a predetermined index in order to ensure the quality of the design document and program code. For example, the management index is the number of items pointed out per page during the design document review (designated item rate). ), The number of test cases per unit step (test density) in the test process, or the bug detection rate (bug density) per unit step in the test process. For these indexes, the reference value to be achieved is registered in the management index storage unit 50.

  The data editing unit 60 calculates the quality index as described above for each program ID based on the data read from the minutes data storage unit 10 and the quality data storage unit 20. The data editing unit 60 stores the calculated management index values in the integrated data storage unit 40 using the program ID as a key.

  The quality management report generation unit 80 refers to the integrated data storage unit 40 and generates a quality management report 500 for each program. For example, the quality management report generation unit 80 acquires data stored in the integrated data storage unit 40 using the program ID as a key, and generates a report indicating the quality of each program for each program. Further, the quality management report generation unit 80 acquires data stored in the integrated data storage unit 40 using the case ID as a key, and outputs a quality management report 500 regarding a plurality of programs associated with the case ID. It can also be generated. Furthermore, the quality management report generating unit 80 compares the reference value of the management index stored in the management index storage unit 50 with the calculated management index value of each program, and performs quality management based on the comparison result. A report 500 can also be generated.

  FIG. 6 shows an example of the quality management report output screen 700. On this screen 700, it is possible to set search conditions when creating a quality control report.

  The quality management report output screen 700 has search condition input areas 710, 720, and 730 for basic information, design process quality, and test process quality, respectively. When a search condition is input to these search condition input areas 710, 720, and 730 by the user, the quality management report generation unit 80 acquires data according to the condition from the integrated data storage unit 40, and A predetermined quality management report 500 is generated.

  For example, search by agenda category in the review of design documents (for example, extract only “pointed items”), generate a quality control report, or extract only program IDs that do not meet the standard value for a given management index It is possible to do.

  The above-described embodiments of the present invention are examples for explaining the present invention, and are not intended to limit the scope of the present invention only to those embodiments. Those skilled in the art can implement the present invention in various other modes without departing from the gist of the present invention.

It is a functional block diagram of the quality management system of the program which concerns on one Embodiment of this invention. An example of the minutes input screen 100 is shown. The data structure of the minutes data storage part 10 is shown. An example of the quality input screen 200 is shown. The data structure of the quality data storage part 20 is shown. An example of the quality management report output screen 700 is shown.

Explanation of symbols

10 Minutes data storage unit 20 Quality data storage unit 30 Case table 40 Integrated data storage unit 50 Management index storage unit 60 Data editing unit 80 Quality management report generation unit 100 Minutes input screen 110 Basic information input screen 130 Detailed information input screen 200 Quality input screen 300 Item registration screen 500 Quality management report 700 Quality management report output screen

Claims (5)

A program quality control device,
Means for accepting input of review results when a design document described in a program unit is reviewed in the design process;
Means for receiving an input of a test result obtained by executing a test of the program code manufactured based on the design document in the test process;
Storage means for associating and storing the review results and the test results;
A quality control apparatus for a program comprising: report means for generating a quality control report for a design process and a test process with reference to the storage means and outputting the generated quality control report. Means for storing program identification information for identifying a program and management identification information for grouping and managing a plurality of programs in association with each other;
The management identification information is associated with a plurality of program identification information,
2. The quality management apparatus for a program according to claim 1, wherein the report means generates and outputs the quality management report in the management identification information unit. Means for storing quality control index reference values for the design process and test process;
Means for calculating a quality control index based on the review result and the test result;
Means for comparing the calculated quality control index with a reference value of the quality index,
2. The program quality management apparatus according to claim 1, wherein the report unit generates the quality management report based on a comparison result of the comparison unit. In the design process, receiving a review result input when a design document described in a program unit is reviewed;
In the test process, receiving an input of a test result obtained by executing a test of the program code manufactured based on the design document;
Storing the review result and the test result in a storage means in association with each other;
Generating a quality control report for a design process and a test process with reference to the storage means, and outputting the generated quality control report. When executed on a computer,
In the design process, receiving a review result input when a design document described in a program unit is reviewed;
In the test process, receiving an input of a test result obtained by executing a test of the program code manufactured based on the design document;
Storing the review result and the test result in a storage means in association with each other;
A computer program for generating a quality management report of a program in which a quality control report for a design process and a test process is generated with reference to the storage means, and the generated quality control report is output.

Images