JP2005326953A - Software quality evaluation system and method, and program for evaluating software quality - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To properly evaluate the quality of software in consideration of condition of a plurality of projects. <P>SOLUTION: This software quality evaluation system is provided with: a quality data storage means 21 for storing inputted quality data for each software development project; a standard reference data storage means 22 for storing evaluation reference data to be used at the time of evaluating the quality of each software development project; an evaluation reference data calculating means 12 for calculating the evaluation reference data according to a predetermined calculation rule based on the quality data of a plurality of software development projects stored in the quality data storage means, and storing the calculated evaluation reference data in an evaluation reference data storage means; and a quality evaluating means 13 for reading the quality data of the predetermined software development project stored in the quality data storage means, and calculating the quality evaluation of the software development project based on the evaluation reference data stored in the evaluation reference data storage means. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a software quality evaluation system, and more particularly to a software quality evaluation system that automatically evaluates each development process of each software development project and the quality of each project.

Software development projects are divided into the following multiple processes.
(1) A basic design process (hereinafter abbreviated as BD) in which requirements to be realized by software are specified from customer's required specifications and documented as a basic design document.
(2) A function design process (abbreviated as FD) in which requirements to be realized by software are defined in function units, external specifications (software input / output specifications) are defined and documented as a function design document.
(3) A detailed design process (abbreviated as DD) for defining a logical structure of internal software based on external specifications and documenting it as a detailed design document.
(4) A manufacturing process (abbreviated as CD) for creating a source code using a programming language.
(5) Unit test process (abbreviated as UT) for testing source code based on unit test specifications.
(6) An integration test process (abbreviated as IT) for combining and testing a plurality of developed software based on the integration test specification.
(7) A comprehensive test process (abbreviated as ST) for testing the function of the developed software based on the comprehensive test specification.
(8) An operational test process (abbreviated as RT) for confirming whether the software conforms to the customer's required specifications.
Then, the system operation starts after the operation test process is completed.

  Here, from the basic design process (BD (1)) to the manufacturing process (CD (4)), multiple developers confirm the design document and source code created in each process and include them in the design document. (Hereinafter referred to as a review). This review improves the quality of the design document and source code. Conventionally, as a method of judging this quality status, project development is based on whether or not the number of defects estimated in advance from past experience and performance has been discovered. The person in charge evaluated each development process.

  In addition, from the unit test process (UT (5)) to the operation test process (RT (8)), conventionally, the number of defects found in the test process is predicted from the past experience and results of the developer. , Predict the number of defects using a software reliability growth model (see, for example, “Introduction to Software Management Model, Shigeru Yamada, Muneo Takahashi, Kyoritsu Publishing”), and the number of defects found in the test The comparison was evaluated and judged by the project developer.

  Furthermore, when multiple projects are evaluated by the organization's quality control department, etc., the standard number of defects in the organization is used, and this value is compared with the actual project value for each development process. Had been implemented.

  Patent Document 1 below discloses a system in which the quality of a project belonging to an organization is evaluated, the evaluation result is digitized, and rearrangement is supported in order from the project with the lowest evaluation result.

JP 2003-345918 A

  However, the conventional example has the following disadvantages. First, when performing quality assessment based on the number of defects for each project, it is a comparison with the past performance of the project, so if the quality of the entire project within the organization has not been improved, the past quality status As a result, there arises a problem that the quality cannot be improved.

  In addition, the quality assessment based on the comparison of multiple projects in the organization is compared with the standard values of the organization, and it is possible to find projects that are out of the standard state. Because of differences, the project may be in good condition even if it is out of the standard state, and it is difficult to distinguish between these cases.

  Furthermore, in the evaluation by the organization, how to determine the numerical values such as the standard number of defects when evaluating the quality status of the project is a problem. Conventionally, the standard values that have been determined need to be regularly reviewed due to improvements in development technology and technical capabilities of project members. However, this review takes time and must be changed manually. Don't be.

  In particular, in the system disclosed in Patent Document 1, since a fixed value is used as a numerical value used when evaluating quality, it is difficult to appropriately capture changes due to quality improvement of the organization. Cannot be evaluated, and there is a problem that quality cannot be improved within the organization.

  Therefore, an object of the present invention is to provide a system that appropriately evaluates the quality of software in consideration of the situation of a plurality of projects.

Therefore, in the present invention, input means for inputting quality data in a predetermined quality item for each software development project,
Quality data storage means for storing the input quality data for each software development project;
Evaluation criteria data storage means for storing evaluation criteria data used when evaluating the quality of each software development project;
Based on the quality data of a plurality of software development projects stored in the quality data storage means, the evaluation reference data is calculated according to a predetermined calculation rule, and the calculated evaluation reference data is stored in the evaluation reference data storage means. Evaluation standard data calculation means;
Quality evaluation means for reading out the quality data of a predetermined software development project stored in the quality data storage means, and calculating the quality evaluation of the software development project based on the evaluation reference data stored in the evaluation reference data storage means;
It has the structure of having.

  Further, in addition to the above configuration, when the quality evaluation calculated by the quality evaluation unit does not satisfy the evaluation standard data, the configuration includes a quality result output unit that outputs the quality evaluation result to the outside. Yes.

  With such a configuration, first, when quality data of a plurality of all software development projects is registered, evaluation reference data serving as a reference for performing quality evaluation is calculated based on these data. Based on this, the quality evaluation of a predetermined software development project is performed and displayed on a display or transmitted to an administrator's terminal. Therefore, the quality evaluation of a specific project can be executed in consideration of the quality of other registered projects. That is, since the evaluation corresponding to the change in quality improvement of other projects in the organization is performed appropriately, the quality of all software can be improved.

Further, in the present invention, in addition to the above configuration, the quality data is quality data in a predetermined quality item for each predetermined development process of each software development project,
The evaluation standard data calculating means calculates evaluation standard data used when evaluating the quality of each development process of each software development project and stores it in the evaluation standard data storage means.
The quality evaluation means is configured to calculate a quality evaluation for each development process of a predetermined software development project.

  At this time, the quality evaluation unit has a function of calculating a quality evaluation for each development process of the predetermined software development project and also calculating a quality evaluation of the entire predetermined software development project. Specifically, the quality data includes the number of defects for each development process in each software development project, and the quality evaluation means determines that each development process based on the number of defects for each development process in a predetermined software development project. The quality of each project is evaluated by evaluating the number of defects remaining in the entire predetermined software development project based on the number of defects for each development process.

  As a result, the evaluation for each development process of the project, for example, the evaluation based on the number of defects is calculated, so the administrator can check for each development process, and can grasp the quality status from the early stage of the project. Yes, measures can be taken early. Also, by calculating the evaluation for each development process and calculating the overall evaluation (for example, the number of defects), even if it is not possible to obtain a better evaluation due to the characteristics of the project in each development process, As a result, it can be a good evaluation, and an appropriate evaluation as a project can be obtained. And even at this time, since evaluation of each development process can be obtained, it is possible to cope with each process and to further improve quality.

The present invention is also a software quality evaluation server,
Input receiving means for receiving external input of quality data in a predetermined quality item for each software development project;
Quality data storage means for storing the input quality data for each software development project;
Evaluation criteria data storage means for storing evaluation criteria data used when evaluating the quality of each software development project;
Based on the quality data of a plurality of software development projects stored in the quality data storage means, the evaluation reference data is calculated according to a predetermined calculation rule, and the calculated evaluation reference data is stored in the evaluation reference data storage means. Evaluation standard data calculation means;
Quality evaluation means for reading out the quality data of a predetermined software development project stored in the quality data storage means, and calculating the quality evaluation of the software development project based on the evaluation reference data stored in the evaluation reference data storage means;
It has the structure of having.

The present invention is also a method for evaluating the quality of software using a computer,
A quality data receiving step in which the computer receives external input of quality data in a predetermined quality item for each software development project, and stores the input quality data for each software development project;
The computer calculates evaluation standard data used when evaluating the quality of each software development project according to a predetermined calculation rule based on the stored quality data of a plurality of software development projects, and the calculated evaluation standard An evaluation standard data calculation step for storing data;
A computer that reads quality data of a predetermined software development project, and calculates a quality evaluation of the software development project based on the stored evaluation standard data; and
It has the structure of having.

Furthermore, the present invention is a software quality evaluation program,
To a computer that performs software quality assessment,
Input receiving means for receiving external input of quality data in a predetermined quality item for each software development project;
Quality data storage means for storing the input quality data for each software development project;
Evaluation criteria data storage means for storing evaluation criteria data used when evaluating the quality of each software development project;
Based on the quality data of a plurality of software development projects stored in the quality data storage means, the evaluation reference data is calculated according to a predetermined calculation rule, and the calculated evaluation reference data is stored in the evaluation reference data storage means. Evaluation standard data calculation means;
Quality evaluation means for reading out the quality data of a predetermined software development project stored in the quality data storage means, and calculating the quality evaluation of the software development project based on the evaluation reference data stored in the evaluation reference data storage means;
The software quality evaluation program is also used to achieve this.

  Even the software quality evaluation server, method, and software quality evaluation program configured as described above can operate in the same manner as the system described above to achieve the above object.

  Since the present invention is configured and functions as described above, according to this, since the quality evaluation of a specific project can be performed in consideration of the quality of other registered projects, other projects in the organization can be executed. Since the evaluation corresponding to the change in quality improvement is performed appropriately, the quality of all software can be improved.

  The software quality evaluation system according to the present invention is mainly configured by a quality evaluation server 1 that performs software quality evaluation processing. Based on the quality data of each software development project input by a developer or the like, It calculates the quality evaluation of software development projects.

  Specifically, quality data such as the number of defects in all development processes from the design process to the test process, which is the development process of the software development project, is collected from multiple software development projects, and the quality evaluation is calculated based on these data The evaluation standard data which becomes the standard at the time is automatically calculated. And based on this evaluation reference data, each process of a specific project and the whole quality evaluation are calculated automatically. After that, for projects that are judged to be of poor quality, the results of quality evaluation are notified to the developer and manager by e-mail. This makes it possible for managers, etc. to grasp the quality status at an early stage at the end of each development process or before the start of software system operation, and to instruct the project to take specific measures. Can be improved. Hereinafter, a specific configuration will be described through examples.

  In the present application, the entire development activities of specific software are collectively referred to as a software development project, and may be simply referred to as a project below. The software development project consists of each development process as described below.

  A first embodiment of the present invention will be described with reference to FIGS. FIG. 1 is a functional block diagram showing the overall configuration of the present invention. 2 to 7 are explanatory diagrams illustrating examples of screens generated by the quality evaluation server and displayed on other terminals. 8 to 10 are explanatory diagrams showing evaluation criteria in the quality evaluation server. 11 to 14 are explanatory diagrams showing the operation of the present invention.

<Configuration>
As shown in FIG. 1, a software quality evaluation system according to the present invention includes a quality evaluation server 1 that performs quality evaluation for each software development project, and a network N for each software development project. Quality data input terminals 31, 32 and the like for inputting quality data, and a quality management terminal 41 to which the quality evaluation result of the software development project calculated by the quality evaluation server 1 is notified from the quality evaluation server 1 via the network N And. Hereinafter, each configuration will be described in detail.

<Quality data input terminal>
The quality data input terminal 31 is a terminal owned by a developer in charge of a software development project (hereinafter simply referred to as a person in charge), and is an information processing apparatus such as a personal computer for inputting quality data in the project.

Here, as described above, development of the software development project is divided into the following plurality of steps.
(1) A basic design process (hereinafter abbreviated as BD) in which requirements to be realized by software are specified from customer's required specifications and documented as a basic design document.
(2) A function design process (abbreviated as FD) in which requirements to be realized by software are defined in function units, external specifications (software input / output specifications) are defined and documented as a function design document.
(3) A detailed design process (abbreviated as DD) for defining a logical structure of internal software based on external specifications and documenting it as a detailed design document.
(4) A manufacturing process (abbreviated as CD) for creating a source code using a programming language.
(5) Unit test process (abbreviated as UT) for testing source code based on unit test specifications.
(6) An integration test process (abbreviated as IT) for combining and testing a plurality of developed software based on the integration test specification.
(7) A comprehensive test process (abbreviated as ST) for testing the function of the developed software based on the comprehensive test specification.
(8) An operational test process (abbreviated as RT) for confirming whether the software conforms to the customer's required specifications.
Then, after the operation test process is completed, the system operation starts (9). In addition, from the basic design process (BD (1)) to the manufacturing process (CD (4)), a plurality of developers confirm the design document and source code created in each process and are included in the design document. The defect is removed (hereinafter referred to as a review).

  Then, when a person in charge of a specific software development project accesses the quality evaluation server 1 via the network N, quality input screen data is transmitted from the quality evaluation server 1, and the screen as shown in FIG. It is displayed on the data input terminal 31. For this quality input screen, the person in charge is responsible for the project name of the software development project, the number of defects found in each development process, the number of pages in the created design document, the number of design review steps, and the number of source code lines. The quality data consisting of the actual value of the number of test items can be input. However, the quality data listed here is an example, and the present invention is not limited to these.

  Then, after inputting the quality data on the quality input screen, the person in charge selects the transmission button shown in FIG. 2 on the quality data input terminal 31 so that the input quality data is transmitted to the quality management server 1. The

  Here, although a plurality of quality data input terminals are illustrated (see reference numerals 31 and 32 in FIG. 1), for example, when there are a plurality of software development projects and each person in charge is different, the terminal of each person in charge This means that 31, 32, etc. exist. Then, quality data for each project is input from the terminals 31 and 32 of each person in charge and transmitted to the quality evaluation server 1. In the present embodiment, the quality data input terminals indicated by reference numerals 31 and 32 are in the same organization (in the same company or in the same department), that is, different projects in the same organization. Quality data is collected in the quality evaluation server 1. However, this is merely an example, and the software development project to be evaluated is not necessarily limited to the same organization.

<Quality control terminal>
The quality management terminal 41 is a terminal owned by a developer in charge of a software development project or a manager in charge of managing software development in the organization. The quality evaluation result in each project is transferred from the quality evaluation server 1 to the network N. An information processing apparatus such as a personal computer that receives the information via the computer. In the following, it is assumed that the person who uses the quality management terminal 41 is the person in charge of management (hereinafter referred to as a manager).

  The quality control terminal 41 has a function that operates as follows when operated by an administrator. First, when the manager accesses the quality evaluation server 1 at the quality management terminal 41 in order to evaluate the quality of each project, the quality management screen data is transmitted from the quality evaluation server 1, as shown in FIG. A quality control screen is displayed on the quality control terminal 41. The quality management screen is for instructing, for example, a “quality evaluation execution button” for instructing the quality management server 1 to execute quality evaluation, and for executing calculation of a parameter serving as a reference for quality evaluation. "Quality evaluation parameter calculation button" is displayed.

  Then, when the administrator selects the “quality evaluation parameter calculation button”, an instruction to calculate the quality evaluation parameter is transmitted to the quality management server 1 and calculated by the quality management server 1 as described later. The screen data for displaying the quality evaluation parameters is transmitted to the quality management terminal 41 and displayed on the terminal 41 as shown in FIG. 4 (however, in FIG. 4, description of parameter values is omitted). The administrator can confirm the displayed parameters, and the parameters can be corrected on the screen as necessary. Then, by pressing the “send button” after the correction, the corrected parameter can be transmitted to the quality evaluation server 1 and registered in the quality evaluation server 1. Note that the quality evaluation parameter may be automatically calculated by the quality evaluation server 1 as described later.

  In addition, when the administrator selects the “quality evaluation execution button”, an instruction to calculate the quality evaluation is transmitted to the quality management server 1, and the quality calculated by the quality management server 1 as will be described later. A quality evaluation result list, which is screen data for displaying the evaluation, is transmitted to the quality management terminal 41 and displayed on the terminal 41 as shown in FIG. The quality management terminal 41 displays a quality evaluation result list, and the administrator can confirm the contents. If the administrator determines that it is necessary to confirm the details of the quality evaluation result of the project, the “detail confirmation button” on the quality evaluation result list screen displayed on the same line as the project to be confirmed is displayed. Press to instruct the quality evaluation server 1 to transmit the details of the quality evaluation result. On the other hand, as will be described later, the quality evaluation server 1 transmits a detailed quality evaluation result of only the project instructed from the quality management terminal 41 to the quality management terminal 41. Thereby, a quality evaluation result detail screen as shown in FIG. 6 is displayed on the quality management terminal 41. In the example shown in FIG. 6, intermediate data calculated when quality evaluation is performed is displayed.

  Then, as described above, if the administrator confirms more detailed contents, and determines that it is necessary to contact the developer in charge of the project with the quality evaluation results and request confirmation and countermeasures, quality control A “mail creation button” on the quality evaluation result list screen shown in FIG. 5 displayed on the terminal 41 is pressed to instruct the quality evaluation server 1 to send a mail creation screen. In response to this instruction, the quality evaluation server 1 transmits a mail creation screen as shown in FIG. 7 and is displayed on the quality management terminal 41. On the other hand, the administrator puts a mark (such as a circle in FIG. 7) on the quality control terminal 41, such as clicking on the mail transmission column for a project that requires mail transmission, and the administrator's column in the comment column. Describe opinions and requests for developers. Then, a mail transmission instruction is issued to the quality evaluation server 1 by pressing a mail transmission button shown in FIG. As a result, as will be described later, an administrator's comment on the evaluation result of the project is transmitted to the quality data input terminal 31 via the quality evaluation server 1 and notified to the person in charge of the project.

<Quality evaluation server>
The quality evaluation server 1 is configured by a general server computer connected on the network N as described above, and is capable of mutual data communication with the quality data input terminals 31 and 32 and the quality management terminal 41. It has become.

  The CPU that is the calculation unit of the quality evaluation server 1 and the hard disk (including ROM, RAM, etc.) that is the storage unit have the following configuration. First, the hard disk stores in advance a quality evaluation program for constructing each processing unit in the CPU so that the quality evaluation server 1 functions as follows. Then, by installing this program in the CPU, a processing unit described mainly below is constructed in the CPU.

  First, the CPU of the quality evaluation server 1 accepts input of quality data in a predetermined quality item for each software development project from the quality data input terminal 31 connected via the network N, and constructs it in the hard disk. The quality data registration processing unit 11 (quality data input accepting means) for registering each software development project in the quality result database 21 (quality data storage means) is constructed. Specifically, the processing unit 11 transmits the quality data input screen shown in FIG. 2 to the quality data input terminal 31, and in the input field input on the screen, the project name for each project, and each development process. The number of found defects, the number of pages in the created design document, the number of design document reviews, the number of source code lines, the actual number of test items, etc. are received and stored in the quality result database. Similarly, when input is received from the quality data input terminal 32 of another project, each data is stored for each project.

  The CPU of the quality evaluation server 1 uses parameters (evaluation standard data) used when evaluating the quality of each software development project in the quality evaluation processing unit 13 described later in a plurality of projects in the quality performance database 21. A quality evaluation parameter calculation processing unit 12 (evaluation reference data calculation means) for calculating using quality data is constructed. The calculated parameters are stored in a parameter file (evaluation reference data storage means) constructed on the hard disk. The quality evaluation parameter calculation processing unit 12 may operate at a preset time interval or, as described above, operate when a request is received from the quality management terminal 41. The parameters used for evaluation are calculated.

  Here, the function of the quality evaluation parameter calculation processing unit 12 will be further described in detail. The parameters calculated by the processing unit 12 include THxR0, THxR1, THxT0, THxT1, THxB0, and THxB1, which are calculated by the following method.

First, B _x is the number of defects found in the x process of the project, D _x is the number of design document pages reviewed in the x process, R _x is the number of man-hours in the review performed in the x process, and B _CD is found in the manufacturing process The number of defects, K is the number of source code lines, and Tx is the number of test items of the test performed in the x process. Here, the x process refers to each development process of each project shown in the above (1) to (8).

Then, R _x / D _x , R _x / K, and T _x / K are calculated to obtain respective average values and standard deviations. Using the average value and the standard deviation, the upper limit (THxR1, THxT1) and the lower limit (THxR0, THxT0) of each value are calculated using the following equations. The same applies to (TH _CD R0, TH _CD T0) and (TH _CD R0, TH _CD T0) in the manufacturing process.

Next, _Bx / _Dx , _Bx / K are calculated, each numerical value is logarithmically converted, and an average value and a standard deviation of the converted numerical values are obtained. Using the average value and the standard deviation, the upper limit (THxB1) and the lower limit (THxB0) of each value are calculated using the following equations.

  Also, the value of the parameter “THSIN” is calculated. First, the ratio of the number of remaining defects at the start of system operation is predicted using the number of defects in each development process of each project in the quality record database 21. This prediction corresponds to obtaining the value of a in the following formula 5 using the number of defects in each development process.

  Here, t corresponds to the numbers (1) to (8) of the respective steps described above. That is, the basic design process is (1), the functional design process is (2), the detailed design process is (3), the manufacturing process is (4), the unit test process is (5), the integration test process is (6), and the comprehensive test The process is (7), the operation test process is (8), and the system operation start time is (9). H (t) represents the cumulative number of defects, H (1) is the number of defects in the basic design process, H (2) is the total number of defects in the basic design process and the functional design process, and H (3) is the basic design. The total number of defects from the process to the detailed design process, and H (8) represents the total number of defects from the basic design process to the operation test process. Using these H (1) to H (8), the parameters a, b, and c in Equation 1 are calculated using the maximum likelihood method. The obtained a, b, and c are set in Expression 5, and residual defect prediction is performed using Expression 6.

  The residual defect prediction for each project obtained as described above is stored as quality data in the quality record database. Then, the residual defect predictions for all projects are read out, the average value and the standard deviation are calculated, the upper limit is calculated using the above equation 1, and this upper limit is set to THSIN. In addition, you may use for the said remaining defect prediction what was calculated | required at the time of calculation of quality evaluation. The parameters thus obtained are stored in the parameter file 22.

  Further, the CPU of the quality evaluation server 1 reads out the quality data of a predetermined software development project stored in the quality performance database 21 and assigns the quality evaluation of the software development project to each parameter stored in the parameter file 22. A quality evaluation processing unit 13 (quality evaluation means) is calculated based on the calculation.

  Specifically, the quality evaluation processing unit 13 performs the evaluation of the number of defects for each development process of the project to be evaluated and the evaluation of the remaining defect prediction after starting the system operation of the project. The evaluation of the number of defects for each development process is performed based on FIG. 8 for the basic design process (BD), the function design process (FD), and the detailed design process (DD). That is, as shown in FIG. 8, the evaluation result predetermined according to the relationship is calculated from the relationship between the Bx / Dx value and the upper limit / lower limit of each parameter described above. More specifically, the table shown in FIG. 8 is a table for determining whether or not the defect removal activity performed in each development process is appropriate, and includes values and parameters based on quality data of a predetermined software development project. Due to the relationship, the description in the corresponding table is the result of the quality evaluation. The manufacturing process (CD) is performed based on FIG. Further, the unit test process (UT), the integration test process (IT), the comprehensive test process (ST), and the operation test process (RT) are performed based on FIG. The description of the tables shown in FIGS. 9 and 10 is the same as in FIG. And the quality evaluation process part 13 registers the quality evaluation result of each development process for every project in the quality evaluation database 23 after calculating the said evaluation result.

  Further, the quality evaluation processing unit 13 calculates the evaluation result of the remaining defect prediction after the system operation is started, and is performed as follows. First, as described above, the residual defect prediction for each project calculated by Equation 5 and Equation 6 is read from the quality record database 21. At the same time, the value of “THSIN” calculated as described above is read from the parameter file 22. At this time, the remaining defect prediction may be calculated by the processing unit based on the above formula. Then, when the numerical value of the equation (6), which is the prediction of the remaining defects of each project, satisfies the following equation (7), it is determined that the number of remaining defects is sufficiently small.

  Thereafter, the quality evaluation processing unit 13 registers the calculated residual defect prediction result for each project in the quality evaluation database 23.

  The quality evaluation server 1 generates a quality evaluation result screen on the CPU of the quality evaluation server 1 based on the results of quality evaluation for each development process and the predicted number of remaining defects using the number of defects in all development processes. The quality evaluation result screen processing unit 14 to be transmitted to is constructed. This processing unit 14 is particularly suitable when it is determined that the quality evaluation by the quality evaluation processing unit 13 does not satisfy a certain standard without falling within a predetermined allowable range, such as a deviation from a parameter value. A quality evaluation result (for example, one shown in FIG. 5) is transmitted to the quality management terminal 41 (quality result output means). However, the quality evaluation result screen processing unit 14 may always transmit the evaluation result to the quality management terminal 41 after performing the evaluation regardless of the content of the evaluation result. Further, the evaluation result may be simply displayed on the display of the quality evaluation server 1.

  The quality evaluation result screen processing unit 14 generates not only the evaluation result but also the screen data as shown in FIGS. 4 to 7 described above, and transmits this to the quality management terminal 41 via the network. It operates to display on the terminal 41. In other words, the screen for displaying the above-described parameters is displayed on the quality management terminal 41, and a correction instruction for this is received. Moreover, as shown in FIG. 7, it has a function which also receives the comment data from the administrator input on the screen which displayed the evaluation result. In such a case, comment data and evaluation result data are notified to the mail transmission processing unit 15 described later.

  The CPU of the quality evaluation server 1 sends the quality evaluation result and the comment from the quality control person in the mail to the project via the network N, that is, the quality data of the development person who is engaged in the project. A mail transmission processing unit 15 that transmits to the input terminal 31 is constructed.

<Operation>
Next, the operation of the system configured as described above will be described with reference to FIGS. FIG. 11 is a flowchart showing the operation of the quality evaluation server 1. 12 to 14 are sequence diagrams showing the operation of the entire system.

  First, the operation when the quality evaluation server 1 stores the quality data of the project will be described with reference to FIGS. 11 and 12 (reference numeral T1 in FIG. 11). When a person in charge of a specific software development project accesses the quality evaluation server 1 at the quality data input terminal 31 (step A1), the quality evaluation server 1 transmits a quality data input screen to the quality data input terminal 31 (step A2). . Then, the quality data input terminal 31 displays a quality data input screen (step A3, see FIG. 2), and the quality data of the project is input to the quality evaluation server by inputting the quality data of the project and pressing the send button. 1 (step A4). The quality evaluation server 1 receives the quality data (step S1 in FIG. 11) and registers it in the quality record database 21 (step A5, step S2 in FIG. 11). In addition, the registration of the quality data is performed from a plurality of software development projects, that is, from persons in charge of different projects. As a result, the quality results database 21 stores the items indicated on the quality data input screens of the plurality of projects. All quality data is registered.

  Next, an operation when the quality evaluation server 1 calculates a parameter will be described with reference to FIGS. 11 and 13 (reference numeral T2 in FIG. 11). Note that FIG. 13 illustrates the operation in the case of performing parameter calculation when a parameter calculation instruction is issued from the quality management terminal 41. However, the operation is periodically performed after a certain period of time has elapsed in the quality evaluation server 1. (See step S3 in FIG. 11).

  First, the administrator connects to the quality evaluation server 1 via the network N at the quality management terminal 41 in order to set parameters used in the quality evaluation (step B1). In contrast, the quality evaluation server 1 transmits a quality management screen (see FIG. 3) to the quality management terminal 41 (step B2). The quality management terminal 41 displays a quality management screen (step B3), and the administrator issues a parameter calculation instruction to the quality evaluation server 1 by pressing the quality evaluation parameter calculation button shown in FIG. 3 (step B4). , Affirmative determination in step S3 of FIG. 11). In the quality evaluation server 1, the quality evaluation parameter calculation processing unit 12 reads out quality data of all projects from the quality record database 21, and calculates quality evaluation parameters (step B5, step S4 in FIG. 11). Here, as described above, the parameters include THxR0, THxR1, THxT0, THxT1, THxB0, THxB1, and THSIN. The calculation method is also as described above.

  Subsequently, each parameter is automatically calculated by the above-described calculation method, and the result is set in the quality evaluation parameter screen shown in FIG. 4 and transmitted to the quality management terminal 41 (step B6). In the quality management terminal 41, the received quality evaluation parameter screen is displayed (step B7), the administrator confirms it, corrects the parameter as necessary, and presses the transmission button. Thereby, the parameter correction can be notified to the quality evaluation server 1 (step B8). Further, the quality evaluation server 1 registers the parameter received from the quality management terminal 41 in the parameter file 22 (step B9). If there is no parameter correction, the parameter calculated in step B5 is directly registered in the parameter file 22 (step S5 in FIG. 11).

  Next, the operation when the quality evaluation server 1 calculates the quality evaluation result of each project will be described with reference to FIGS. 11 and 14 (reference numeral T3 in FIG. 11). First, an administrator such as a quality management department of the organization connects to the quality evaluation server 1 at the quality management terminal 41 in order to evaluate the quality of each project (step C1). Then, the quality evaluation server 1 transmits a quality management screen (see FIG. 3) to the quality management terminal 41 (step C2), and the quality management terminal 41 displays the received quality management screen (step C3). In order to execute the quality evaluation, the administrator presses the quality evaluation execution button on the screen (FIG. 3) displayed on the quality management terminal 41, and instructs the quality evaluation server 1 to execute the quality evaluation (step C4, Step S6 in FIG.

  Then, the quality evaluation server 1 reads the quality data of each project from the quality record database 21 and the parameters necessary for quality evaluation from the parameter file 22 (step C5), and evaluates the quality for each development process of the project (step C5). C6). At this time, the evaluation result is performed based on the tables shown in FIGS. 8 to 10 as described above. Then, the quality evaluation server 1 registers the quality evaluation result of each development process for each project in the quality evaluation database 23. In addition, the residual defect prediction result for each project is calculated and registered in the quality evaluation database 23. In this way, the quality evaluation is calculated (steps S7 and S8 in FIG. 11). In addition, the quality evaluation process by the quality evaluation server 1 may be automatically executed at regular time intervals.

  Subsequently, the quality evaluation server 1 reads the quality evaluation result from the quality evaluation database 23 by the quality evaluation result screen processing unit 14 in order to transmit the quality evaluation result to the quality management terminal 41. Then, a quality evaluation result list screen (see FIG. 4) is generated and transmitted to the quality management terminal 41 (step C7, step S9 in FIG. 11). Receiving this, the quality management terminal 41 displays the quality evaluation result list screen (FIG. 4) (step C8), and the manager confirms the contents. Here, the transmission of the evaluation result may be performed only when the calculated evaluation result does not satisfy a predetermined criterion, that is, when the evaluation result is not desirable.

  After that, if the administrator determines that it is necessary to confirm the detailed quality evaluation result of the project in more detail, press the detail confirmation button on the quality evaluation result list screen (Fig. 4) of the project to be confirmed, and quality evaluation The server 1 is instructed to transmit the quality evaluation result (step C9). Then, the quality evaluation server 1 reads the quality evaluation result of only the project instructed from the quality management terminal 41 by the quality evaluation result screen processing unit 14 from the quality evaluation database 23, and generates a quality evaluation result screen (see FIG. 5). Is transmitted to the quality management terminal 41 (step C10). In response to this, the quality management terminal 41 displays the quality evaluation result screen (FIG. 5) (step C11), and the administrator confirms the contents.

  At this time, if the administrator determines that it is necessary to contact the project (developer, etc.) with the quality evaluation result and ask the project for confirmation and countermeasure, the quality evaluation result list screen (FIG. 4) The mail creation button is pressed to instruct the quality evaluation server 1 to send a mail creation screen (step C12). In response to this instruction, the quality evaluation server 1 transmits a mail creation screen (FIG. 7) to the quality management terminal 41 (step C13). The quality management terminal 41 displays an email creation screen (FIG. 7) (step C14), marks the email transmission column of the email creation screen for projects that require email transmission, and the quality control person in charge in the comment column. An opinion or a request item is described, and an e-mail transmission instruction is issued to the quality evaluation server 1 by pressing the e-mail transmission button (step C15). Receiving this, the quality evaluation server 1 creates a mail for the project using the quality evaluation result and the comment of the manager in the mail transmission processing unit 15, and assigns it to the corresponding project, that is, the terminal of the person in charge of the project (For example, the quality data input terminal 31) (step C16).

  In this way, in the present invention, the administrator can confirm the result of the quality evaluation of the project for each development process, and therefore grasps the quality status for each development process from the early stage of the project. Can do. In addition, since it is possible to predict the remaining defects at the start of system operation from the number of defects in the project and determine whether the operation can be started, if the number of remaining defects is large, take measures such as adding tests. This can be done before the operation starts.

  In addition, the project has various characteristics, and the appearance of defects in each development process varies depending on the characteristics. For example, in a project that can find many defects in the upstream process of development (from basic design process to manufacturing process), the number of defects in the upstream process is larger than the upper limit, and in the downstream process (unit test process to operational test process) ) May be smaller than the lower limit. In the conventional methods, the quality is evaluated for each development process, and therefore the result is out of the upper limit or lower limit, and the quality evaluation result may be deteriorated. However, according to the present invention, in this case, since the residual defect prediction is a good result, it cannot be judged that the quality is bad. In this way, quality evaluation for each development process and overall quality evaluation through all development processes can be performed at the same time, so that errors in judgment can be reduced. In addition, when the residual defect prediction result is bad (when the upper limit is exceeded), it is indicated how bad the development process is evaluated, so it becomes easy to examine the countermeasures of the project for quality improvement.

  In addition, the quality evaluation results are sent to the project development staff by e-mail with comments from the quality control staff, so immediately when the quality management staff discovers a problem, the project immediately investigates and takes countermeasures. It becomes possible to request implementation.

  In addition, the quality evaluation parameters are automatically calculated based on the quality data of the organization's project, and the quality control personnel can modify the parameters by looking at the results, so that the quality of the entire organization can be improved. It is possible to modify the parameters.

  The present invention can be incorporated into a system such as a company as a system for evaluating the quality of a software development project and improving the quality, and has industrial applicability.

It is a functional block diagram which shows the structure of this invention. It is a figure which shows an example of a quality data input screen. It is a figure which shows an example of the operation screen of a quality management terminal. It is a figure which shows the example of a display of a parameter. It is a figure which shows the example of a display of an evaluation result. It is a figure which shows the detailed example of a display of an evaluation result. It is a figure which shows the state by which the comment was input into the evaluation result. It is a figure which shows an example of quality evaluation. It is a figure which shows an example of quality evaluation. It is a figure which shows an example of quality evaluation. It is a flowchart which shows operation | movement of a quality evaluation server. It is a sequence diagram which shows operation | movement of the whole system. It is a sequence diagram which shows operation | movement of the whole system. It is a sequence diagram which shows operation | movement of the whole system.

Explanation of symbols

1 Quality Evaluation Server 11 Quality Data Registration Processing Unit (Input Accepting Unit)
12 Quality evaluation parameter calculation processing unit (evaluation standard data calculation means)
13 Quality evaluation processing section (quality evaluation means)
14 Quality evaluation result screen processing unit (quality result output means)
15 Mail transmission processing unit 21 Quality record database (quality data storage means)
22 Parameter file (Evaluation criteria data storage means)
23 Quality evaluation databases 31 and 32 Quality data input terminal (input means)
41 Quality control terminal (quality result output means)
N network

Claims (8)

Input means for inputting quality data in a predetermined quality item for each software development project;
Quality data storage means for storing the input quality data for each software development project;
Evaluation criteria data storage means for storing evaluation criteria data used when evaluating the quality of each software development project;
The evaluation reference data is calculated according to a predetermined calculation rule based on quality data of a plurality of software development projects stored in the quality data storage means, and the calculated evaluation reference data is used as the evaluation reference data storage means. Evaluation criteria data calculation means stored in
Quality evaluation means for reading quality data of a predetermined software development project stored in the quality data storage means and calculating a quality evaluation of the software development project based on the evaluation reference data stored in the evaluation reference data storage means When,
A software quality evaluation system characterized by comprising   The quality result output means which outputs the said quality evaluation result outside when the quality evaluation calculated by the said quality evaluation means does not satisfy | fill the said evaluation reference data, The output of the said quality evaluation means is characterized by the above-mentioned. Software quality evaluation system. The quality data is quality data in a predetermined quality item for each predetermined development process of each software development project,
The evaluation standard data calculating means calculates evaluation standard data used when evaluating the quality of each development process of each software development project and stores the evaluation standard data in the evaluation standard data storage means,
The quality evaluation means calculates a quality evaluation for each development process of the predetermined software development project;
The software quality evaluation system according to claim 1 or 2, characterized in that   4. The quality evaluation unit according to claim 3, wherein the quality evaluation unit calculates a quality evaluation for each development process of the predetermined software development project and also calculates a quality evaluation of the entire predetermined software development project. Software quality evaluation system. The quality data includes the number of defects for each development process in each software development project,
The quality evaluation unit performs quality evaluation for each development process based on the number of defects for each development process in the predetermined software development project, and the predetermined software based on the number of defects for each development process. 5. The software quality evaluation system according to claim 4, wherein the quality evaluation of the entire project is performed by evaluating the number of defects remaining in the entire development project. Input receiving means for receiving external input of quality data in a predetermined quality item for each software development project;
Quality data storage means for storing the input quality data for each software development project;
Evaluation criteria data storage means for storing evaluation criteria data used when evaluating the quality of each software development project;
The evaluation reference data is calculated according to a predetermined calculation rule based on quality data of a plurality of software development projects stored in the quality data storage means, and the calculated evaluation reference data is used as the evaluation reference data storage means. Evaluation criteria data calculation means stored in
Quality evaluation means for reading quality data of a predetermined software development project stored in the quality data storage means and calculating a quality evaluation of the software development project based on the evaluation reference data stored in the evaluation reference data storage means When,
A software quality evaluation server characterized by comprising: A method for evaluating the quality of software using a computer,
A quality data receiving step in which the computer receives input from outside of quality data in a predetermined quality item for each software development project, and stores the input quality data for each software development project;
The computer calculates evaluation reference data used when evaluating the quality of each software development project according to a predetermined calculation rule based on the stored quality data of the plurality of software development projects. An evaluation standard data calculation step for storing evaluation standard data;
The computer reads quality data of the predetermined software development project, and calculates a quality evaluation of the software development project based on the stored evaluation standard data; and
A software quality evaluation method characterized by comprising: To a computer that performs software quality assessment,
Input receiving means for receiving external input of quality data in a predetermined quality item for each software development project;
Quality data storage means for storing the input quality data for each software development project;
Evaluation criteria data storage means for storing evaluation criteria data used when evaluating the quality of each software development project;
The evaluation reference data is calculated according to a predetermined calculation rule based on quality data of a plurality of software development projects stored in the quality data storage means, and the calculated evaluation reference data is used as the evaluation reference data storage means. Evaluation criteria data calculation means stored in
Quality evaluation means for reading quality data of a predetermined software development project stored in the quality data storage means and calculating a quality evaluation of the software development project based on the evaluation reference data stored in the evaluation reference data storage means When,
Software quality evaluation program to achieve

Images