JP2011215927A - Productivity evaluation device, productivity evaluation method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a productivity evaluation device that uniformly evaluates productivity of projects, based on a plurality of inputs or outputs.SOLUTION: A project information storage part 121 of the productivity evaluation device 1 stores project data. An efficiency value table generating part 13 calculates an efficiency value of each project, using a data envelope analytical method, based on a data including the plurality of inputs or outputs stored in the project information storage part 121. The efficiency value that is a unified index indicating a production efficiency of the project is presented for each project.

Description

  The present invention relates to a productivity evaluation device, a productivity evaluation method, and a program.

Estimating project man-hours is an important task directly linked to the profit and loss of the project. In general, the estimation of the man-hour of the project is performed based on the experience and know-how of an expert. Therefore, estimation results are likely to vary depending on the estimate person, and it is generally not easy to evaluate and correct whether or not the estimation results are appropriate.
Therefore, several techniques have been proposed in order to increase the estimation accuracy of the project man-hours. For example, the technique described in Patent Document 1 shows a technique for pointing out items that are inferior to a project that has been completed by comparing a new project with a project that has been completed. Specifically, projects that have been developed are classified in advance based on a group discrimination criterion such as a project type, and first, a group of comparison target projects is selected based on the project type of the new project. Next, based on in-group evaluation criteria such as asset diversion, determine whether the characteristics of the new project match the characteristics of the selected group. To do. Furthermore, based on productivity characteristic items such as customer participation rate, a project similar to the new project is selected from the group, and an item in which the selected project is inferior to the new project is pointed out.

JP 2003-280901 A

However, although the technique described in Patent Document 1 can evaluate individual items of man-hour estimation of a new project, it does not sufficiently provide objective evaluation for man-hour estimation of the entire project.
In an actual project, the productivity, which is the result obtained by the man-hours input, varies greatly depending on the field of the target system, the characteristics of the customer, and the development environment used. Without considering this productivity, for example, if the evaluation of the man-hour estimate is performed using only the index indicating the sense of scale of the project, such as the number of program steps, there is a possibility that fluctuation will occur between the man-hour performance and the estimate. . Due to the demand for cost reduction, there is a need to plan an efficient project with few man-hours in order to have a highly productive environment as much as possible, and the accuracy of man-hour estimation is very important.

In general, productivity evaluation is a balance between input and output, and various combinations of input and output can be considered depending on the situation of each project. For example, a combination of various deliverables such as the number of functions of a system and the number of display screens generated in a project can be considered as output for simple man-hours. Although it can be expected that the evaluation accuracy is improved by evaluating productivity based on a plurality of inputs or a plurality of outputs, in the prior art including Patent Document 1, each of the plurality of inputs or a plurality of outputs is used for each evaluation. There is no indication of a technique for uniformly evaluating project productivity.
Project productivity also varies greatly depending on the characteristics of the development tools used. When searching for existing project cases similar to the new project in the hope that the same productivity can be obtained by using the same development tools as the existing project in the new project, a considerable number of existing project cases Need to be accumulated.

The present invention has been made in consideration of such circumstances, and its purpose is to provide a productivity evaluation apparatus and a production system that can integrally evaluate the productivity of each project based on a plurality of inputs or a plurality of outputs. It is to provide a sex evaluation method and program.
Another object of the present invention is to provide a productivity evaluation apparatus, a productivity evaluation method, and a program capable of evaluating a production environment such as a development tool based on accumulation of relatively few existing project examples. .

  [1] The present invention has been made to solve the above-described problem, and the productivity evaluation apparatus according to one aspect of the present invention includes a value of a product item indicating a scale of a product generated in a project, Based on the value of the resource item indicating the size of the resource input to the project, a productivity evaluation value calculation unit that calculates the efficiency value by the data envelope analysis method for each project as the value indicating the production efficiency of the project It is characterized by doing.

  [2] A productivity evaluation apparatus according to an aspect of the present invention is the productivity evaluation apparatus described above, wherein the value of the deliverable item and the resource item of the project for which the efficiency value is calculated A project information storage unit for storing values, wherein the productivity evaluation value calculation unit is a non-negative first weighting factor determined for each deliverable item in common to all projects stored in the project information storage unit And the first condition for all projects stored in the project information storage unit as a constraint condition with a non-negative second weighting factor determined for each resource item in common for all projects stored in the project information storage unit. The sum of the product of the weighting factor and the value of the deliverable item of the project is the value of the second weighting factor and the resource item of the project. For each project, the sum of the product of the first weighting factor and the value of the deliverable item of the project is set as the second weighting factor under the condition that the value divided by the sum of the products of A linear programming problem for obtaining a maximum value of a value divided by the sum of products of the resource items of the project is solved, and the obtained maximum value is used as the efficiency value of the project.

  [3] A productivity evaluation apparatus according to an aspect of the present invention is the productivity evaluation apparatus described above, and is added to a storage unit that stores the constraint condition generated by the productivity evaluation value calculation unit. An additional project processing unit that processes project data, wherein the productivity evaluation value calculation unit writes the constraint condition in the storage unit, and the additional project processing unit includes the productivity evaluation value calculation unit When the value of the deliverable item and the value of the resource item of the project for which the efficiency value is not calculated are input, the constraint condition generated by the productivity evaluation value calculation unit before the input is input from the storage unit Read, under the constraints that have been read, the sum of products of the first weighting factor and the value of the input product item, the second weighting factor and the value of the input resource item Productive And solving the linear programming problem for obtaining the maximum value divided by, and using the obtained maximum value as the efficiency value of the project to which the value of the deliverable item and the value of the resource item are input. To do.

  [4] A productivity evaluation apparatus according to an aspect of the present invention is the productivity evaluation apparatus described above, wherein the productivity evaluation value calculation unit performs the efficiency of a project to be evaluated under the constraint condition. A value is calculated.

  [5] A productivity evaluation apparatus according to an aspect of the present invention is the above-described productivity evaluation apparatus, wherein the efficiency value calculated by the productivity evaluation value calculation unit corresponds to characteristic data indicating characteristics of a project. A productivity evaluation storage unit that stores the attached data; and a project search unit that reads the efficiency value associated with the characteristic data that matches the input search condition from the productivity evaluation storage unit. And

  [6] A productivity evaluation apparatus according to an aspect of the present invention is the productivity evaluation apparatus described above, wherein the project search unit is configured to associate the efficiency value with the characteristic data that matches the search condition. Of these, the maximum efficiency value is selected.

  [7] A productivity evaluation apparatus according to an aspect of the present invention is the productivity evaluation apparatus described above, wherein the project search unit reads the characteristic data that meets the search condition.

  [8] Moreover, the productivity evaluation device according to one aspect of the present invention is the above-described productivity evaluation device, wherein the productivity evaluation value calculation unit includes the project among the all projects stored in the project information storage unit. For a project excluding the project with the highest efficiency value, the sum of the product of the first weighting factor and the value of the deliverable item of the project is the sum of the second weighting factor and the value of the resource item of the project. Under the condition that the value divided by the sum of products is 1 or less, for the project with the maximum efficiency value, the first weighting factor, the value of the deliverable item of the project with the maximum efficiency value, Obtained by solving a linear programming problem that finds the maximum value of the sum of products divided by the sum of the products of the second weighting factor and the resource item value of the project with the maximum efficiency value. It said maximum value and judging whether greater than a predetermined threshold value.

  [9] A productivity evaluation method according to an aspect of the present invention is a project productivity evaluation method used in a project productivity evaluation apparatus that calculates an efficiency value indicating the production efficiency of a project, and calculates a productivity evaluation value. As a value indicating the production efficiency of the project based on the value of the product item indicating the size of the product generated in the project and the value of the resource item indicating the size of the resource input to the project. A productivity evaluation value calculation step of calculating an efficiency value by a data envelope analysis method for each project is performed.

  [10] A program according to an aspect of the present invention is a program for evaluating productivity of a product item indicating a scale of a product generated in a project and a resource input to the project. It is a program for executing a productivity evaluation value calculation step of calculating, for each project, an efficiency value according to a data envelope analysis method as a value indicating the production efficiency of the project based on a value of a resource item indicating a scale.

According to this invention, the productivity of each project can be uniformly evaluated based on a plurality of inputs or a plurality of outputs.
Further, according to the present invention, it is possible to evaluate a production environment such as a development tool based on the accumulation of relatively few existing project examples.
Objectively evaluate the production efficiency of the entire project.

It is a block diagram which shows schematic structure of the productivity evaluation system in one Embodiment of this invention. In the same embodiment, it is a figure which shows the example of the profile table which the project information storage part 121 memorize | stores. In the same embodiment, it is a figure which shows the example of the input / output table which the project information storage part 121 memorize | stores. In the same embodiment, it is a figure which shows the example of the efficiency value table which the productivity evaluation memory | storage part 122 memorize | stores. In the same embodiment, it is a figure which shows the example of the search result table which the search result memory | storage part 123 memorize | stores. 5 is a flowchart showing a processing procedure of the productivity evaluation device 1 when project data is transmitted from the evaluator terminal device 2 in the embodiment. In the same embodiment, it is a flowchart which shows the process sequence in which the efficiency value calculation part 131 produces | generates an efficiency value table. In the embodiment, the outlier removal unit 132 is a flowchart showing a processing procedure for removing outliers. In the embodiment, the productivity evaluation apparatus 1 is a flowchart showing a procedure for processing a newly added project. In the embodiment, the productivity evaluation device 1 is a flowchart showing a processing procedure for searching for a project that matches a search condition. It is a figure which shows the example of the efficiency value of the project in the case of 1 input 2 output in the same embodiment. In the same embodiment, it is a figure which shows the example of the project which the project search part 15 selects.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a configuration diagram showing a schematic configuration of a productivity evaluation system according to an embodiment of the present invention.
In the figure, a productivity evaluation system 500 includes a productivity evaluation device 1, an evaluator terminal device 2, and a searcher terminal device 3. The productivity evaluation device 1 includes a transmission / reception unit 11, a storage unit 12, an efficiency value table generation unit (productivity evaluation value calculation unit) 13, an additional project processing unit 14, and a project search unit 15. The storage unit 12 includes a project information storage unit 121, a productivity evaluation storage unit 122, and a search result storage unit 123. The efficiency value table generation unit 13 includes an efficiency value calculation unit 131 and an outlier value removal unit 132.

The productivity evaluation apparatus 1 uses a value of a product item indicating the scale of a product generated in a project and a value of a resource item indicating the scale of a resource input to the project in the evaluator terminal device 2. When input, an efficiency value by data envelope analysis (DEA) based on the input value is calculated for each project.
Here, the product generated in the project includes, for example, a system produced in the project, and the value of the product item indicating the scale of the product includes, for example, the number of functions and screens of the system. The number or the number of forms can be used.

The resources input to the project include, for example, human resources, physical resources, time resources, or financial resources such as personnel and time input to the project or expenses (money) required for the project. The resource item value indicating the scale of the resource is, for example, quantifying some resource required for the project, such as the number of man-hours required for the project or the total cost required for the project. The indicated values can be used.
Further, the efficiency value calculated by the productivity evaluation device 1 is a value obtained by dividing the value of the weighted product item by the value of the weighted resource item, that is, the output of the project, as will be described later. This value is divided by the input to the project, and can be used as a value indicating the production efficiency of the project.

In addition, when the search condition of the project is input in the searcher terminal device 3, the productivity evaluation apparatus 1 evaluates the project that matches the input search condition from the projects whose efficiency values are calculated. The device 1 is selected, and the selected project is displayed on the searcher terminal device 3.
The evaluator terminal device 2 accepts input of data indicating the characteristics of the project including the value of the deliverable item and the value of the resource item, and transmits the accepted data to the productivity evaluation device 1. The searcher terminal device 3 receives project search conditions, and transmits the received search conditions to the productivity evaluation device 1.

In the productivity evaluation device 1, the storage unit 12 stores various information related to the project. The project information storage unit 121 stores an input / output table and a profile table. The productivity evaluation storage unit 122 stores an efficiency value table. The search result storage unit 123 stores a search result table.
Here, the input / output table is a table including the value of the resource item and the value of the deliverable item in the data indicating the characteristics of the project (hereinafter referred to as “characteristic data”). As will be described later, the data included in the input / output table is used when the efficiency value table generation unit 13 or the additional project processing unit 14 calculates the efficiency value of the project. In the following, the value of the resource item is referred to as “input” of the project, the value of the deliverable item is referred to as “output” of the project, and the input and output of the project are collectively referred to as “input / output” of the project.

The profile table is a table including data other than the input / output of the project among the characteristic data indicating the characteristics of the project. As will be described later, the data included in the profile table is used when the project search unit 15 selects a project that matches the search condition input by the searcher terminal device 3.
The efficiency value table is a table including the efficiency value of each project. The search result table is a table including characteristic data including the efficiency value of the project selected by the project search unit 15 based on the search condition input by the searcher terminal device 3.

  The transmission / reception unit 11 transmits / receives data to / from the evaluator terminal device 2 and the searcher terminal device 3. The transmission / reception unit 11 generates / updates the profile table and the input / output table based on the data output from the evaluator terminal device 2, and sends the efficiency value table generation unit 13 and the additional project processing unit to each project. A signal for instructing generation / update of the efficiency value table including the efficiency value is output.

The efficiency value table generation unit 13 generates an efficiency value table indicating the characteristic data of each project including the efficiency value of the project. The efficiency value calculation unit 131 reads the input / output of the project from the input / output table, calculates the efficiency value of each project, and generates an efficiency value table. The outlier removal unit 132 removes exceptional project data from the efficiency value table generated by the efficiency value calculation unit 131.
The additional project processing unit 14 reads the input / output of the added project from the input / output table, calculates the efficiency value, and updates the efficiency value table.
The project search unit 15 searches the efficiency value table, reads project data that meets the search conditions, and generates a search result table.

Next, the data configuration of each data stored in the storage unit 12 will be described with reference to FIGS.
FIG. 2 is a diagram illustrating an example of a profile table stored in the project information storage unit 121. The profile table includes characteristic data of each project that is used as an index when the project search unit 15 selects a project that matches the search condition. In the example of the figure, the profile table contains the project ID (Identifier), scale, development period, development type, industry type, security level, operation rate, data volume, communication volume, software configuration, usage tool, usage method, usage development. Includes procedures and software information.
In addition to the data of the profile table or instead of the data of the profile table, the data of the input / output table may be used as an index when the project search unit 15 selects a project that matches the search condition. . As the number of types of data used as a search index increases, the project search unit 15 can perform a search corresponding to various search conditions.

“Project ID” is identification information of a project. The data in the “Scale” column is data indicating the scale of the project. In the example of FIG. 5, the number of program steps of the system generated in the project is used. The data in the “development period” column is data indicating the number of days spent in the project. The data in the “development type” column takes a value of “new” indicating a project for newly developing a system, or “function addition” indicating a project for adding a function to an existing system. The data in the “industry” column is data indicating an industry targeted by the system generated by the project, and indicates an industry such as a manufacturing industry, a retail industry, or a financial industry.
The data in the “security level” column is data indicating the security level of the system generated in the project, and takes one of high, medium, and low values. The data in the “operation rate”, “data amount”, and “communication amount” columns indicate the operation rate required for the system generated by the project, the amount of data stored in the system, and the communication amount of the system, respectively. It is data.

  The data in the “software configuration” column is data indicating the software configuration of the system generated in the project, and indicates an OS (Operating System) name, application software name, and the like. The data in the “Use Tool” column is data indicating the tool used at each stage of the project. For example, the name of the automatic source code generation tool used in the manufacturing process and the source code automatic diagnosis tool used in the test process. Indicates the name. The data in the “utilization method” column is data indicating a method that is not used as a tool and is used at each stage of the project, and indicates, for example, the name of a manual that defines how to write a design document. The data in the “Usage Development Procedure” column is an overview of the work performed in each process. For example, a software development process model that conforms to a waterfall model or a spiral model. Indicates the name of The data in the “used software” column is data indicating software used in the system development environment, and indicates, for example, the name of the software used when generating the system screen.

  Note that the data items of the profile table stored in the project information storage unit 121 are not limited to those shown in FIG. For example, an item indicating the processing form of the system, such as “centralized processing type”, “distributed processing type”, “mobile information processing (Mobile Computing) type”, may be included. Further, some of the items shown in FIG. 2 may not be included. As the number of data items in the profile table increases, the project search unit 15 can cope with various search conditions. On the other hand, the smaller the number of data items in the profile table, the smaller the storage capacity required for the project information storage unit 121.

FIG. 3 is a diagram illustrating an example of an input / output table stored in the project information storage unit 121. The input / output table includes the input / output of each project, which is the basis on which the efficiency value table generation unit 13 calculates the efficiency value.
In the example in the figure, the input / output table contains the input / output of each project for each process of design, manufacturing, and testing, and each project's input includes information on man-hours, cost, period, and number of people. The output of each project includes information on the number of steps, the number of screens, the number of forms, the number of batch jobs, the number of tables, and the number of functions. The evaluator terminal device 2 accepts non-negative numbers as these inputs and outputs, and the input / output table stores non-negative numbers as inputs and outputs.

  The data in the “Man-hours” column is data indicating the man-hours of the project, and in the example of FIG. The data in the “cost” column is data indicating the total cost required for the project. The data in the “period” column is data indicating a period during which the project has been operated. The data in the “number of people” column is data indicating the number of project personnel.

The data in the “number of steps” column is data indicating the number of program steps of the system generated in the project. The data in the “number of screens” column is data indicating the number of types of screens (hereinafter referred to as “number of screens”) displayed by the system generated in the project. The data in the “number of forms” column is data indicating the number of types of forms output by the system generated in the project (hereinafter referred to as “number of forms”). The data in the “number of batch jobs” column is data indicating the number of batch jobs processed by the system generated in the project. The data in the “number of tables” column is data indicating the number of tables in the database stored in the system generated by the project. The data in the “number of functions” column is data indicating the number of functions executed by the system generated in the project.
In the example of the figure, each output item is an item indicating the attribute of the system generated in the project, and is a value common to each process of design, manufacturing, and testing. Thus, for items common to each process, for example, the transmission / reception unit 11 writes the data transmitted from the evaluator terminal device 2 in the corresponding column of each process in the input / output table, thereby providing an input / output table. Is generated.

The input / output table stored in the project information storage unit 121 is not limited to that shown in FIG. For example, it may be a table indicating input / output for each project that is not divided into design, manufacturing, and testing processes. Thereby, the storage capacity in which the project information storage unit 121 stores the input / output table can be reduced. On the other hand, by storing data for each process as shown in FIG. 3, data analysis for each process can be performed.
The items in the input / output table are not limited to those shown in FIG. For example, when there is a large variation between the scale of the system generated by the project and the number of steps due to the diversion of existing software, it is possible to use items other than the number of steps as the output. The number of screens, number of forms, number of batch jobs, number of tables, and number of functions are objectively determined data based on customer specifications. By using these data, the scale of the system can be grasped more appropriately. I can expect to do it. Alternatively, items other than those shown in the figure may be included as input items, such as data items indicating the skill level of personnel input to the project in a five-step evaluation.

FIG. 4 is a diagram illustrating an example of the efficiency value table stored in the productivity evaluation storage unit 122. The efficiency value table includes an efficiency value indicating the production efficiency of each project.
In the example shown in the figure, the efficiency value table includes each data of the profile table, each data of the input / output table, and an efficiency value calculated by the efficiency value table generation unit 13 based on each data of the input / output table. It is.

FIG. 5 is a diagram illustrating an example of a search result table stored in the search result storage unit 123. The search result table shows the result of the search performed by the project search unit 15. In the example shown in the figure, the search result table includes the project ID of the project selected by the search, the name of the tool used, the efficiency value, the process, and the man-hour.
For example, when the evaluator terminal device 2 receives a user input of “process = design” as a search condition and receives a user input of “use tool, process, man-hour” as a display item and transmits it to the productivity evaluation device 1, The project search unit 15 searches the efficiency value table in the productivity evaluation storage unit 122, selects a project that matches the search condition, reads the data of the selected project, and stores it in the search result storage unit 123 as a search result table. Write.
At this time, the project search unit 15 reads out data of “use tool, process, man-hour” as a display item and “project ID, efficiency value” as a predetermined item, and writes it into the search result storage unit 123. .

  Note that the project search unit 15 may write all data of the selected project. By writing all the data, a lot of data can be presented to the user, and the user can study from various angles. On the other hand, as shown in FIG. 5, by writing only some items, it is possible to reduce the amount of communication when the search result is transmitted from the productivity evaluation device 1 to the searcher terminal device 3. In addition, since the amount of data to be displayed on the searcher terminal device 3 is reduced, the user can easily see the search result and can easily read the necessary data (for example, the name of the tool used).

Next, the operation of the productivity evaluation device 1 will be described with reference to FIGS.
FIG. 6 is a flowchart illustrating a processing procedure of the productivity evaluation device 1 when project data is transmitted from the evaluator terminal device 2.
When project data is transmitted from the evaluator terminal device 2, the transmission / reception unit 11 of the productivity evaluation device 1 generates a profile table and an input / output table in which the transmitted data is collected in a table format, and project information Write to the storage unit 121. Thereafter, the transmission / reception unit 11 outputs a signal instructing generation of the efficiency value table to the efficiency value calculation unit 131 (step S101).
When a signal instructing generation of the efficiency value table is output from the transmission / reception unit 11, the efficiency value calculation unit 131 generates an efficiency value table and writes it in the productivity evaluation storage unit 122. Thereafter, the efficiency value calculation unit 131 outputs a signal instructing the outlier removal unit 132 to remove outliers (step S102).

When a signal instructing the removal of outliers is output from the efficiency value calculation unit 131, the outlier removal unit 132 deletes the outlier project data from the efficiency value table stored in the productivity evaluation storage unit 122, Based on the remaining project data, the efficiency value of each project is calculated, and the efficiency value table is updated (step S103). The “outlier value project” here is a project whose efficiency value stored in the efficiency value table of the productivity evaluation storage unit 122 is larger than a predetermined threshold value. Outlier projects are considered projects with exceptionally high production efficiency.
Thereafter, the productivity evaluation device 1 ends the process of FIG.

FIG. 7 is a flowchart illustrating a processing procedure in which the efficiency value calculation unit 131 generates an efficiency value table. When the efficiency value calculation unit 131 outputs a signal instructing generation of the efficiency value table from the transmission / reception unit 11, the efficiency value calculation unit 131 starts the process of FIG.
First, the efficiency value calculation unit 131 generates an efficiency value table (framework) in the storage area of the productivity evaluation storage unit 122. Then, the efficiency value calculation unit 131 reads each data of the profile table from the project information storage unit 121 and writes it in the efficiency value table generated in the productivity evaluation storage unit 122 (step S121). Next, the efficiency value calculation unit 131 reads each data of the input / output table from the project information storage unit 121 and writes it in the efficiency value table of the productivity evaluation storage unit 122 (step S122).

The efficiency value calculation unit 131 generates a constraint condition in the data envelope analysis method for calculating the efficiency value of the project based on each data of the input / output table read from the project information storage unit 121.
More specifically, a non-negative weight coefficient (second weight coefficient) v _i for each resource item (i is a positive integer of 1 ≦ i ≦ m. M is the number of resource items) and a non-negative value for each product item A weighting factor (first weighting factor) u _r (r is a positive integer satisfying 1 ≦ r ≦ s, where s is the number of product items) is generated. At this point in time, the values of these weighting factors are unconfirmed, and the efficiency value calculation unit 131 treats these weighting factors as variables. Then, the efficiency value calculation unit 131 reads the input x _{ij of the} project P _j (j is a positive integer of 1 ≦ j ≦ q. Q is the number of projects stored in the input / output table) read from the input / output table. (I is a positive integer of 1 ≦ i ≦ m, m is the number of resource items), output y _rj (r is a positive integer of 1 ≦ r ≦ s, s is the number of product items), and weight Using the coefficients, a constraint condition consisting of q inequalities shown in Expression (1) for each of j = 1, 2,..., Q is generated.
(V ₁ x _1j + v ₂ x _2j +... + V _m x _mj ) / (u ₁ y _1j + u ₂ y _2j +... + U _s y _sj ) ≦ 1 (1)
The efficiency value calculation unit 131 writes the generated constraint condition in the working memory area of the storage unit 12 (step S123).

Here, as shown in the input / output table of FIG. 3, when project input is indicated for each of a plurality of processes, the efficiency value calculation unit 131 is set in advance so that the data of each process is handled as input. Keep it. For example, the efficiency value calculation unit 131 outputs three pieces of data, that is, the man-hours for the design process, the man-hours for the manufacturing process, and the man-hours for the test process, for one project among the inputs and outputs read from the input-output table in FIG. Are handled as manhour data, three weighting factors corresponding to each are generated, and a constraint condition including each data and each weighting factor is generated.
On the other hand, in the input / output table of FIG. 3, the output column is also shown for each of the plurality of processes. However, when only the same data is copied to each process, the efficiency value calculation unit 131 selects any one process. It is set in advance so that only the data is handled as output. For example, the efficiency value calculation unit 131 treats only the output of the design process among the outputs read from the input / output table of FIG. 3 as the output, and sets each item (the number of steps, the number of screens,. Six corresponding weighting factors are generated, and constraint conditions including each data and each weighting factor are generated. However, weighting factors are not generated for the output of the manufacturing process and the test process, and are not included in the constraint conditions.

  Note that the efficiency value calculation unit 131 may handle only data of any one process as input / output. For example, the efficiency value calculation unit 131 treats only the input / output of the manufacturing process as the input / output among the data read from the input / output table of FIG. 3, generates the weighting coefficient corresponding to each of the data, and the weighting coefficient However, for the input and output of the design process and the test process, the weighting coefficient is not generated and is not included in the constraint condition. Thus, by using only data for one process, the efficiency value in the process can be calculated, and the production efficiency in the process can be evaluated.

Thereafter, the efficiency value calculation unit 131 executes a loop for performing processing for each project (step S124). In this loop, the efficiency value calculation unit 131 first generates a function of the efficiency value of the project to be processed as an objective function in the data envelope analysis method. More specifically, a function (formula (2)) of the efficiency value θ _j of the project P _{j to be} processed is generated (step S125).
_{θ j = (v 1 x 1j} + v 2 x 2j + ··· + v m x mj) / (u 1 y 1j + u 2 y 2j + ··· + u s y sj) ··· Equation (2)
Next, the efficiency value calculation unit 131 solves the linear programming problem that maximizes the value of the objective function generated in step S125 under the constraint conditions generated in step S123, and calculates the efficiency value of the project to be processed. . That is, the value of the weighting coefficient that maximizes the objective function under the constraint condition is calculated, and the efficiency value θ _j at the value of the weighting coefficient is calculated. The efficiency value calculation unit 131 solves the linear programming problem using, for example, a simplex method (step S126).
Then, the efficiency value calculation unit 131 writes the calculated efficiency value in the efficiency value table of the productivity evaluation storage unit 122 (step S127).

  After that, the efficiency value calculation unit 131 determines whether there is a project that has not been subjected to the loop processing from step S124. If it is determined that there is a project, the efficiency value calculation unit 131 returns to step S124 and performs the loop processing for the remaining projects. continue. On the other hand, if it is determined that all the projects have been processed, the outlier removal unit 132 outputs a signal instructing the removal of the outliers, and the process in the figure ends (step S128).

FIG. 8 is a flowchart illustrating a processing procedure in which the outlier removal unit 132 removes outliers. The outlier removal unit 132 starts the processing in FIG. 5 when a signal instructing removal of outliers is output from the efficiency value calculator 131.
In the process of FIG. 8, the outlier removal unit 132 first sets all projects included in the efficiency value table of the productivity evaluation storage unit 122 to be unselected. For example, the outlier removal unit 132 reads out the project IDs of all projects from the efficiency value table of the productivity evaluation storage unit 122, and associates each of the read project IDs with a selection status flag indicating selected or unselected. The selection status table is generated, the selection status flags of all the projects are set to unselected, and are written in the working memory area of the storage unit 12 (step S141).

Next, the outlier removal unit 132 refers to the efficiency value table and the selection status table to determine whether there is a project having an efficiency value of 1 and an unselected selection status flag (step S142). If it is determined that there is a corresponding project (step S142: YES), one of the corresponding projects (hereinafter referred to as project “P _i ”) is selected (step S143).
The outlier removal unit 132, the efficiency value table productivity evaluation storage unit 122, reads the input and output of each project except the project P _i, on the basis of the read output, for calculating the efficiency value of the project Generate constraints in the data envelopment analysis method.
More specifically, the number of projects stored in the efficiency value table is t, and j = 1, 2,..., I−1, i + 1,. Generate a constraint consisting of t-1 inequalities shown.
(V ₁ x _1j + v ₂ x _2j +... + V _m x _mj ) / (u ₁ y _1j + u ₂ y _2j +... + U _s y _sj ) ≦ 1 (3)
Here, as described above, the input of the project P _j is x _ij , the output is y _rj , the non-negative weighting factor for each resource item is v _i, and the non-negative weighting factor for each product item is u _r (Step S144).

Further, the outlier removal unit 132 reads the input / output of the project P _i from the efficiency value table of the productivity evaluation storage unit 122 and, based on the read / output, the project P _i as an objective function in the data envelope analysis method. A function (Equation (4)) of the efficiency value θ _i of is generated (step S145).
_{θ i = (v 1 x 1i} + v 2 x 2i + ··· + v m x mi) / (u 1 y 1i + u 2 y 2i + ··· + u s y si) ··· (4)
The outlier removal unit 132, under the generated constraint condition at the step S144, the value of the objective function generated at step S145 to solve the linear programming problem to maximize calculates the efficiency value of the project P _i (step S146).

The outlier removal unit 132 determines whether or not the calculated efficiency value is greater than a predetermined threshold (for example, “3”) (step S147). If it is determined that the calculated efficiency value is greater (step S147: YES) from the efficiency value table sex evaluation storage unit 122, a selection state table of the storage unit 12, removes the data of the project P _i. As a result, the number t of projects stored in the efficiency value table decreases by one. Further, the outlier removal unit 132 rewrites the constraint condition stored in the working memory area by the storage unit 12 with the constraint condition generated in step S144 (step S148 above).
Then, the outlier removal unit 132 calculates the efficiency value of each remaining project and writes it in the efficiency value table of the productivity evaluation storage unit 122. More specifically, the outlier removal unit 132 performs the function of the efficiency value of the project to be processed as an objective function in the data envelope analysis method for each of the remaining projects as in the loop of steps S124 to S128 in FIG. And the efficiency value of the project to be processed is calculated by solving the linear programming problem that maximizes the value of the objective function under the constraints generated in step S144, and the calculated efficiency value is used as the productivity evaluation storage unit. The result is written in the efficiency value table 122 (step S149). Thereafter, the process returns to step S141.
On the other hand, if it is determined in step S147 that the calculated efficiency value is equal to or less than a predetermined threshold value (step S147: NO), the project selection status flag of project P _{i in} the project selection status table of the storage unit 12 is determined. Is written as the value of (step S161), and then the process returns to step S142.
If it is determined in step S142 that there is no project having an efficiency value of 1 and the selection status flag is not selected (step S147: NO), the processing in FIG.

In step S147, when the calculated efficiency value is determined to be greater than the predetermined threshold, outlier removal section 132, even if the efficiency value table in step S147 so as not to remove the project data P _i Good. In this case, outlier removal unit 132, as the efficiency value of the project P _i, writes the efficiency value calculated in step S146 to the efficiency value table. Since this efficiency value is larger than the threshold value, a user who refers to the data in the efficiency value table recognizes that the efficiency value of the project P _i is an extremely large value (so-called outlier value), and the project P _i The data can be used as a reference.

  When the productivity evaluation apparatus 1 includes a multiprocessor and has parallel processing capability, the outlier removal unit 132 determines the outlier value performed in steps S144 to S147 and the efficiency value of each project performed in step S149. Recalculation may be performed in parallel. In this case, when it is determined in step S147 that the efficiency value is larger than the threshold value (step S147: YES), the outlier removal unit 132 rewrites the efficiency value of each project in the efficiency value table with the recalculated efficiency value. On the other hand, when it is determined in step S147 that the efficiency value is equal to or less than the threshold (step S147: NO), the outlier removal unit 132 discards the recalculated efficiency value and does not rewrite the efficiency value table. As described above, the outlier removal unit 132 can reduce the processing time by executing the processing in steps S144 to S147 and the processing in step S149 in parallel. On the other hand, by performing the processing according to the procedure shown in FIG. 8, the outlier removal unit 132 does not perform unnecessary work, so that the processing amount can be reduced.

FIG. 9 is a flowchart illustrating a procedure in which the productivity evaluation apparatus 1 performs processing for a newly added project (hereinafter referred to as project “P _k ”).
When the data of the project P _k is transmitted from the evaluator terminal device 2, the transmission / reception unit 11 of the productivity evaluation device 1 outputs the transmitted data to the additional project processing unit 14.
The additional project processing unit 14 writes the data of the project _Pk output from the transmission / reception unit 11 into the profile table and the input / output table of the project information storage unit 121 (step S201). Further, the additional project processing unit 14 adds the data of the project P _{k to} the efficiency value table (step S202).

Note that the additional project processing unit 14 may write the data of the project P _k only in the efficiency value table, not in the profile table and the input / output table of the project information storage unit 121. By not writing to the project information storage unit 121, the load of the additional project processing unit 14 and the storage capacity required for the project information storage unit 121 can be reduced. On the other hand, since the additional project processing unit 14 writes the data of the project P _k into the profile table and the input / output table of the project information storage unit 121, the profile table and the input / output table data are updated. In addition, in the input / output table, it is possible to centrally manage the data of the additional project and the data of the project that has been processed by the efficiency value table generation unit.

The transmission / reception unit 11 may write the data of the project P _k into the profile table and the input / output table of the project information storage unit 121 and output the project ID of the project P _k to the additional project processing unit 14. . In this case, additional projects processing unit 14, based on the project ID project P _k, reads the data of the project P _k from the profile table of the project information storage unit 121 and the input-output table. Thereby, the data amount which the transmission / reception part 11 outputs to the additional project process part 14 can be reduced.

Next, the additional project processing unit 14 reads the constraint condition generated in step S123 of FIG. 7 or step S144 of FIG. 8 stored in the working memory area of the storage unit 12 (step S203). This constraint condition is a constraint condition that includes only the inequality related to the project processed by the efficiency value table generation unit 13 and does not include the inequality related to the additional project.
Furthermore, additional projects processing unit 14 based on the input and output of the project _{P k,} as an objective function in data envelopment analysis, to generate a function of the efficiency value theta _k project _{P k} (Equation (5)) (step S204 ).
_{θ k = (v 1 x 1k} + v 2 x 2k + ··· + v m x mk) / (u 1 y 1k + u 2 y 2k + ··· + u s y sk) ··· (5)
Then, the additional project processing unit 14 solves the linear programming problem that maximizes the value of the objective function generated in step S204 under the constraints read in step S203, and calculates the efficiency value of the project P _k (step S205).
The additional project processing unit 14 writes the calculated efficiency value in the efficiency value table of the productivity evaluation storage unit 122 (step S206), and thereafter ends the process of FIG.

FIG. 10 is a flowchart showing a processing procedure in which the productivity evaluation device 1 searches for a project that matches the search condition.
When the search condition is transmitted from the searcher terminal device 3, the transmission / reception unit 11 outputs the transmitted search condition to the project search unit 15. As will be described later, as the search condition, a condition based on the characteristic data of the new project to be evaluated or the name of the tool to be compared is used (step S301).
The project search unit 15 reads the project data that matches the search condition output from the transmission / reception unit 11 from the efficiency value table of the productivity evaluation storage unit 122 (step S302), and reads the read data from the project with the large efficiency value. A search result table is generated in order and written in the search result storage unit 123. When the writing is completed, the project search unit 15 outputs a signal indicating the end of the search to the transmission / reception unit 11, and the transmission / reception unit 11 reads the data of the search result table from the search result storage unit 123 to the searcher terminal device 3. Transmit (step S303). Thereafter, the process of FIG.
The searcher terminal device 3 displays the data of the search result table, whereby the search result is presented to the user.

Next, the efficiency value generated by the efficiency value table generation unit 13 will be described with reference to FIG.
FIG. 11 is a diagram showing an example of the efficiency value of a project in the case of 1 input 2 output. In the figure, represents the input of the project _{P j} in _{x j,} the output 1 and output 2, respectively represented by _{y 1j} and _{y 2j.}
Each point in the figure is obtained by taking the value y _1j / x _j obtained by dividing the output 1 by the input on the horizontal axis and the value y _2j / x _j obtained by dividing the output 2 by the input on the vertical axis for each project. Show.
Here, each project corresponds to a decision making unit (DMU) in data envelope analysis. Also, points a, b, and c located outside of the points in FIG. 4 correspond to efficient frontiers, and a broken line ENV that has these points a, b, and c as vertices and that is orthogonal to the vertical and horizontal axes Corresponds to the envelope.

The projects corresponding to the points a, b, and c of the efficient frontier are all projects that are efficient. The efficiency value of the project corresponding to another point is a value obtained by dividing the distance from the origin to the point on the straight line passing through the origin o and the point by dividing the distance from the origin to the envelope. For example, if the distance from the origin o to the point d on the straight line passing through the origin o and the point d is l ₁ and the distance from the point d to the envelope is l ₂ , the efficiency of the project corresponding to the point d The value is l ₁ / (l ₁ + l ₂ ).

  A project with a higher efficiency value has a higher output to input ratio and can be evaluated as having higher production efficiency. When the productivity evaluation apparatus 1 calculates the efficiency value of the project to be evaluated, the user can use the calculated efficiency value as a standard for the production efficiency of the project to be evaluated. When the evaluation value is close to 1, it can be evaluated that the project has high production efficiency. On the other hand, when the evaluation value is small, it can be evaluated that the project has low production efficiency.

Next, project selection performed by the project search unit 15 will be described with reference to FIG.
FIG. 12 is a diagram illustrating an example of a project selected by the project search unit 15. Each point in the figure is the same as each point in FIG.
The set G1 is a set of points corresponding to projects similar to the project to be evaluated. For example, the searcher terminal device 3 receives a search condition based on the characteristics of the new project to be evaluated, such as “development type = new, industry = manufacturing, security level = medium,. When transmitted to the performance evaluation device 1, the project search unit 15 that has received the search condition via the transmission / reception unit 11 searches the efficiency value table in the productivity evaluation storage unit 122 and projects that match the search condition (for example, evaluation) Each project corresponding to the set G1 is selected as a project having the same characteristic data as the target project.

  By displaying the data of each project selected by the project search unit 15 on the searcher terminal device 3 including the efficiency value, the user can know whether or not the production efficiency of each selected project is high. it can. This allows the user to review a new project based on a project with a large efficiency value, such as using a tool used in a project with a large efficiency value in a new project to be evaluated, and to produce a new project. It can be expected to increase efficiency. In addition, for a project with a low efficiency value, the user may analyze the cause of the low efficiency value and reflect the analysis result in the new project.

Note that the project search unit 15 may select only the project having the highest efficiency value (in the example of FIG. 12, the project corresponding to the point a) from among the projects that match the search condition. In this case, the project search unit 15 searches each project in the efficiency value table in descending order of efficiency value, and the search can be terminated when one project matching the search condition is detected. Moreover, the communication amount at the time of transmitting a search result from the productivity evaluation apparatus 1 to the terminal device 3 for searchers can be reduced.
Alternatively, the project search unit 15 may select only projects whose efficiency value is a predetermined value (for example, “0.7”) or more. Also in this case, as in the case where only the project having the largest efficiency value is selected, the search load can be reduced and the communication amount can be reduced.

The set G2 is a set of points corresponding to the project using the tool A, and the set G3 is a set of points corresponding to the project using the tool B.
For example, when the searcher terminal device 3 receives a search condition “use tool = tool A” and transmits it to the productivity evaluation device 1, the project search unit that has received the search condition via the transmission / reception unit 11. 15 searches the efficiency value table in the productivity evaluation storage unit 122 and selects each project corresponding to the set G2 as a project that matches the search condition. Similarly, when the searcher terminal device 3 receives the input of the search condition “used tool = tool B”, the project search unit 15 selects each project corresponding to the set G3.

  By displaying the data of each project selected by the project search unit 15 including the efficiency value, the searcher terminal device 3 displays the general production efficiency when the tool A is used, and the tool B. It can be compared with the general production efficiency when used. Then, the user can consider whether the tool A or the tool B should be used based on the comparison result. In the example of the figure, the project using the tool A has a larger efficiency value than the project using the tool B. For this reason, it can be expected that the production efficiency is increased by using the tool A even in a new project.

The project search unit 15 may perform a search combining the search described in FIG. 11 and the search described in FIG.
For example, when the searcher terminal device 3 has a search condition such as “development type = new, business type = manufacturing industry, security level = medium,...” And “use tool = tool A” A search condition for comparing projects having specific characteristics such as “used tool = tool B” is received. The project search unit 15 searches the productivity evaluation storage unit 122 and selects a project that matches the “development type = new, business type = manufacturing industry, security level = medium,...” And uses the tool A. To do. In the example of FIG. 12, the project search unit 15 selects projects corresponding to the points a and b included in both the set G1 and the set G2.
Further, the project search unit 15 selects a project that matches the “development type = new, business type = manufacturing industry, security level = medium,...” And uses the tool B. In the example of FIG. 12, the project search unit 15 selects projects corresponding to the points f, g, and h that are included in both the set G1 and the set G3.

  By displaying the data of each selected project on the searcher terminal device 3 including the efficiency value, the user can use the tool A as the evaluation target project, and the tool in the evaluation target project. The production efficiency when using B can be compared, and based on the comparison result, it can be determined whether tool A or tool B should be used. In the example of the figure, the project using the tool A has a larger efficiency value than the project using the tool B. For this reason, it can be expected that the production efficiency is increased by using the tool A even in a new project.

As described above, the productivity evaluation apparatus 1 uses the data including the project inputs and outputs stored in the project information storage unit 121, in particular, the data including a plurality of inputs or the plurality of outputs. Since the value is calculated, this efficiency value can be shown as an objective assessment of the overall project estimate. In particular, the number of system screens, forms, batch jobs, tables, functions, etc. generated by the project is small compared to the number of program steps compared to the number of program steps, and easy from the system specifications. By using multiple item values that can be measured, it is possible to show the evaluation of project production efficiency based on the efficiency value that is a single indicator for the entire project, rather than for each item, while suppressing evaluation blurring. .
In this way, it is possible to evaluate the production efficiency of a project based on the efficiency value that is a single index, so the effects of the system development environment and parts, etc. on the production efficiency, such as the study of improving production efficiency by using a certain tool, can be considered. Can be considered. At this time, the projects used for evaluation do not necessarily have to be similar to each other. As a result, even when the number of projects used for evaluation is relatively small, the development environment and parts can be evaluated and examined.

  In addition, in the planning stage of a new project, the productivity evaluation device 1 outputs past project data similar to the new project including the efficiency value, so that the user can make the project characteristics similar to the new project. In addition, a past project having a large efficiency value can be used as a model, and an overall picture of the project to be used as a model can be obtained. Further, by referring to the data of the past project, the user can know an appropriate tool, method, number of personnel, etc. according to the characteristics of the new project. This can be expected to reduce the cost and duration of new projects.

Moreover, since the outlier removal unit 132 detects a project that shows an exceptionally large efficiency value and deletes the data of the project from the efficiency value table, it is more appropriate for projects that do not include an exceptional project. Efficiency value can be calculated.
Thereby, for example, the efficiency value of each project is concentrated on a small value (for example, 0.3 or less), and the projects obtained as the search results of the productivity evaluation device 1 are all misunderstood as projects with low production efficiency. Or giving confusion to the user.

  Further, when the new project is added, the additional project processing unit 14 calculates the efficiency value of the added project using the constraint condition generated by the efficiency value table generating unit 13, and thus calculates the efficiency value. It is not necessary to update the efficiency value for a completed project, and the calculation load can be reduced.

Note that the productivity evaluation device 1 may calculate the efficiency value of the project to be evaluated. Even if the project to be evaluated is a new project, output specifications such as the number of screens, number of forms, number of batch jobs, number of tables, number of functions, etc. are determined based on the customer specifications, and the customer specifications and output specifications are determined. After estimating the resources to be input to the project, such as man-hours and costs, the efficiency value can be calculated.
In this case, when the searcher terminal device 3 receives input / output user input and transmits it to the productivity evaluation device 1, the productivity evaluation device 1 processes the newly added project described in FIG. Similarly to the above, the efficiency value is calculated. More specifically, the efficiency value calculation unit 131 first reads the constraint condition stored in the working memory area of the storage unit 12. This constraint condition is a constraint condition that includes only the inequality related to the project processed by the efficiency value table generation unit 13 and does not include the inequality related to the project to be evaluated.
The efficiency value calculation unit 131 generates a function of the efficiency value of the project to be evaluated based on the input / output transmitted from the searcher terminal device 3. Then, the efficiency value calculation unit 131 solves the linear programming problem that maximizes the value of the generated objective function under the read constraint condition, and calculates the efficiency value of the project to be evaluated.

When the searcher terminal device 3 displays the efficiency value calculated by the efficiency value calculation unit 131, the user can use the displayed efficiency value as a measure of the production efficiency of the project to be evaluated. When the evaluation value is close to 1, it can be evaluated that the project has high production efficiency, and the project is promoted according to the plan.
On the other hand, when the evaluation value is small, it can be evaluated that the project is low in production efficiency, and it is considered that there is room for improving the production efficiency by reviewing the project and process estimation, such as reviewing the tools used for the project.

A program for realizing all or part of the functions of the productivity evaluation apparatus 1 is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into a computer system and executed. You may process each part by. Here, the “computer system” includes an OS and hardware such as peripheral devices.
Further, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used.
The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Furthermore, the “computer-readable recording medium” dynamically holds a program for a short time like a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. In this case, a volatile memory in a computer system serving as a server or a client in that case, and a program that holds a program for a certain period of time are also included. The program may be a program for realizing a part of the functions described above, and may be a program capable of realizing the functions described above in combination with a program already recorded in a computer system.

  The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes design changes and the like within a scope not departing from the gist of the present invention.

DESCRIPTION OF SYMBOLS 1 Productivity evaluation apparatus 2 Terminal apparatus for evaluators 3 Terminal apparatus for searchers 11 Transmission / reception part 12 Storage part 13 Efficiency value table production | generation part 14 Additional project process part 15 Project search part 121 Project information storage part 122 Productivity evaluation storage part 123 Search result storage unit 131 Efficiency value calculation unit 132 Outlier removal unit 500 Productivity evaluation system

Claims (10)

  Based on the value of the product item indicating the size of the product generated in the project and the value of the resource item indicating the size of the resource input to the project, a data envelope is obtained as a value indicating the production efficiency of the project. A project productivity evaluation apparatus comprising a productivity evaluation value calculation unit that calculates an efficiency value by an analysis method for each project. A project information storage unit for storing the value of the deliverable item and the value of the resource item of the project for which the efficiency value is calculated;
The productivity evaluation value calculation unit includes a non-negative first weighting factor determined for each deliverable item common to all projects stored in the project information storage unit, and all projects stored in the project information storage unit. For all projects stored in the project information storage unit as a constraint condition with a non-negative second weight coefficient that is commonly determined for each resource item, the first weight coefficient and the value of the deliverable item of the project For each project under the condition that the value obtained by dividing the sum of the products by the sum of the products of the second weighting factor and the value of the resource item of the project is 1 or less. The maximum value of the product sum of the product item value of the project divided by the sum of the product of the second weighting factor and the resource item value of the project. Solve the mel linear programming problem, the maximum values obtained, characterized in that said efficiency value of the project,
The project productivity evaluation device according to claim 1. A storage unit for storing the constraint condition generated by the productivity evaluation value calculation unit;
An additional project processing unit for processing the data of the added project;
Further comprising
The productivity evaluation value calculation unit writes the constraint condition in the storage unit,
When the value of the deliverable item and the value of the resource item of the project for which the productivity evaluation value calculation unit does not calculate the efficiency value is input to the additional project processing unit,
Read the constraint condition generated by the productivity evaluation value calculation unit before the input from the storage unit,
Under the read constraints, the sum of the product of the first weighting factor and the input value of the product item is the sum of the product of the second weighting factor and the input value of the resource item. Solving a linear programming problem for obtaining a maximum value obtained by dividing by a sum, the obtained maximum value is set as an efficiency value of the project in which the value of the deliverable item and the value of the resource item are input. And
The project productivity evaluation apparatus according to claim 2.   The project productivity evaluation apparatus according to claim 2 or 3, wherein the productivity evaluation value calculation unit calculates the efficiency value of a project to be evaluated under the constraint condition. A productivity evaluation storage unit that stores the efficiency value calculated by the productivity evaluation value calculation unit in association with characteristic data indicating characteristics of the project;
A project search unit that reads the efficiency value associated with the characteristic data that matches the input search condition from the productivity evaluation storage unit;
The project productivity evaluation apparatus according to any one of claims 1 to 4, further comprising:   6. The project productivity evaluation apparatus according to claim 5, wherein the project search unit selects a maximum efficiency value from the efficiency values associated with the characteristic data that matches the search condition. .   The project productivity evaluation apparatus according to claim 5, wherein the project search unit reads out the characteristic data that matches the search condition.   The productivity evaluation value calculation unit, for all projects stored in the project information storage unit, for a project excluding the project having the maximum efficiency value, the first weighting factor and the value of the deliverable item of the project For the project with the maximum efficiency value under the condition that the value obtained by dividing the sum of the product by the sum of the products of the second weighting factor and the value of the resource item of the project is 1 or less, The sum of the product of the first weighting factor and the value of the deliverable item of the project with the maximum efficiency value, and the value of the resource item of the project with the maximum weighting factor and the efficiency value. 3. A linear programming problem for obtaining a maximum value obtained by dividing the product by the sum of products with the product is solved, and it is determined whether or not the obtained maximum value is larger than a predetermined threshold value. Project evaluation device according to any one of the paragraphs 4. A project productivity evaluation method used in a project productivity evaluation device that calculates an efficiency value indicating the production efficiency of a project,
The productivity evaluation value calculation unit produces the project based on the value of the deliverable item indicating the size of the deliverable generated in the project and the value of the resource item indicating the size of the resource input to the project. A project productivity evaluation method, comprising: executing a productivity evaluation value calculation step of calculating an efficiency value by a data envelope analysis method for each project as a value indicating efficiency. Based on the value of the deliverable item indicating the scale of the deliverable generated in the project and the value of the resource item indicating the scale of the resource input to the project on the computer as the project productivity evaluation device A program for executing a productivity evaluation value calculating step for calculating, for each project, an efficiency value by a data envelope analysis method as a value indicating the production efficiency.

Images