Project evaluation device and project evaluation method

Abstract

The purpose of the present invention is to provide a technology for making it possible to assess a project appropriately. This project assessment apparatus comprises: a document analysis unit that calculates a first similarity rate on the basis of documents; a source code analysis unit that calculates a first appropriation rate on the basis of source codes; and an assessment unit. The assessment unit assesses an assessment target project on the basis of a result of associating a second similarity rate and a second appropriation rate with at least one of the first similarity rate and the first appropriation rate.

Description

[Technical field]

[0001] The present disclosure relates to a project evaluation device and a project evaluation method. [Background technology]

[0002] In a software development project, documents, source codes, etc. are generated as deliverables of the project. For example, Patent Document 1 proposes a technique for verifying the traceability of deliverables. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2019-95961 A Summary of the Invention [Problem to be solved by the invention]

[0004] In the conventional technology, traceability is verified by evaluating the same type of deliverables, such as evaluating documents or source codes. However, since the evaluation is not performed by associating different types of deliverables, there is a problem that it is not possible to appropriately evaluate a project, for example, by evaluating whether documents and source codes are mutually excessive or insufficient.

[0005] Therefore, the present disclosure has been made in consideration of the above-mentioned problems, and aims to provide a technique that enables appropriate evaluation of projects. [Means for solving the problem]

[0006] The project evaluation device of the present disclosure includes a document analysis unit that calculates a first similarity rate based on the documents of the project to be evaluated and the documents of the project to be compared, among projects in which corresponding documents and source code are generated as deliverables; a source code analysis unit that calculates a first diversion rate based on the source code of the project to be evaluated and the source code of the project to be compared; and an evaluation unit that evaluates the project to be evaluated based on a result of associating at least one of the first similarity rate and the first diversion rate, a second similarity rate for the documents of the project to be compared, and a second diversion rate for the source code of the project to be compared. Effect of the Invention

[0007] According to the present disclosure, a project to be evaluated is evaluated based on a result of correlating at least one of the first similarity rate and the first diversion rate with the second similarity rate and the second diversion rate. With this configuration, it is possible to appropriately evaluate the project.

[0008] The objects, features, aspects and advantages of the present disclosure will become more apparent from the following detailed description and the accompanying drawings. [Brief description of the drawings]

[0009] [Figure 1] 1 is a block diagram showing an example of the configuration of a project evaluation device according to a first embodiment. [Diagram 2] FIG. 13 is a diagram showing an example of a transition of a diversion rate with respect to a development phase. [Diagram 3] 4 is a flowchart showing an example of operation of the source code analyzing device according to the first embodiment. [Figure 4] FIG. 13 is a diagram showing an example of a transition of a similarity rate with respect to a development phase. [Diagram 5] 4 is a flowchart showing an example of the operation of the document analysis device according to the first embodiment. [Figure 6] 4 is a flowchart showing an operation example of the project evaluation device according to the first embodiment. [Figure 7] 4 is a flowchart showing an operation example of the project evaluation device according to the first embodiment. [Figure 8] FIG. 2 is a diagram for explaining an example of the operation of the project evaluation device according to the first embodiment. [Figure 9] FIG. 2 is a diagram for explaining an example of the operation of the project evaluation device according to the first embodiment. [Figure 10] FIG. 13 is a block diagram showing a hardware configuration of a project evaluation device according to another modified example. [Figure 11] FIG. 13 is a block diagram showing a hardware configuration of a project evaluation device according to another modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] <Embodiment 1> Fig. 1 is a block diagram showing an example of the configuration of a project evaluation device 1 according to the first embodiment. In a software development project, documents and source codes are generated as deliverables, and the project evaluation device 1 in Fig. 1 is a project evaluation device that evaluates the project. The documents are, for example, specifications or design documents for the source codes, and the documents and the source codes correspond to each other.

[0011] The project evaluation device 1 in FIG. 1 includes a source code analysis device 2, a document analysis device 6, an evaluation unit 10, and a notification unit 11.

[0012] <Source code analysis device> The source code analysis device 2 includes a source code registration device 3, a source code analysis unit 4, and a source code database 5.

[0013] The source code registration device 3 registers source code, which is a deliverable of a project, in the source code database 5. The source code to be registered includes source code of the project under development, source code of the reuse source project, and source code of the reuse destination project.

[0014] The project under development is a project to be evaluated by the project evaluation device 1.

[0015] The reuse source project is a past project, which is a comparative project with which the project under development is compared.

[0016] The destination project is a past project, which is a project obtained by reusing the source project. On the other hand, the above-mentioned project under development may be a project obtained by reusing the source project, or may be a project other than the source project.

[0017] In the following explanation, the source code of the project under development, the source code of the reuse project, and the source code of the reuse destination project may be abbreviated as the source code under development, the source code to be reused, and the destination source code, respectively.

[0018] The reuse source code and the reuse destination source code are registered in the source code database 5 at the end of each development phase. In the first embodiment, information indicating the development phase of the source code is added to the registered source code. Also in the first embodiment, functional information defined by the project or organization is added to the registered source code in units defined by the project or organization (for example, source file units or function units). By adding the above information to the registered source code, the source code analysis unit 4 can perform a detailed analysis of the source code, as described below.

[0019] The source code analysis unit 4 calculates the second diversion ratio by analyzing the source code based on the diversion source code and the diversion destination source code that are in the same development phase. For example, the source code analysis unit 4 extracts the difference between the diversion source code and the diversion destination source code, and divides the difference by the total amount of source code to calculate the second diversion ratio, which increases as the value obtained decreases.

[0020] For example, the source code analysis unit 4 may measure and tally the amount of newly created code, the amount of modified code, and the amount of deleted code separately to extract the above-mentioned difference. For example, the source code analysis unit 4 may take into account the development scale of the source code in calculating the second diversion rate. For example, when functional information is added to the source code, the source code analysis unit 4 may measure and tally the amount of newly created code, the amount of modified code, and the amount of deleted code by function. According to the above, a more detailed second diversion rate can be calculated. For example, the source code analysis unit 4 may calculate the second diversion rate by using machine learning such as AI (artificial intelligence) on the diversion source code and the diversion destination source code.

[0021] 2 is a diagram showing an example of the transition of reuse rates such as the second reuse rate with respect to the development phase. In general, the reuse rate gradually decreases from the early development stage, and decreases more significantly in the software production phase than in other phases. In general, software changes start after system design. It is preferable that software changes start after the start of software production, but depending on the state of the project or the state of the source code, application to new hardware, porting of functions from other projects, etc. may be added before the start of software production.

[0022] The source code analysis unit 4 registers the second diversion rate in the source code database 5. The calculation and registration of the second diversion rate is performed for each development phase. This enables the evaluation unit 10, which will be described later, to refer to the second diversion rate in each development phase of the past project when evaluating the source code and documents of the project under development.

[0023] FIG. 3 is a flowchart showing an example of the operation of the source code analyzing device 2 according to the first embodiment for a past project.

[0024] In step S1, the source code registration device 3 adds development phase information of the source code to be reused, to the source code. In step S2, the source code registration device 3 adds function information of the source code to be reused, to the source code. In step S3, the source code registration device 3 registers the source code to be reused in the source code database 5. The processing of steps S1 to S3 is performed each time each development phase of the source code to be reused is completed.

[0025] In step S4, the source code registration device 3 adds development phase information of the destination source code to the destination source code. In step S5, the source code registration device 3 adds function information of the destination source code to the destination source code. In step S6, the source code registration device 3 registers the destination source code in the source code database 5.

[0026] In step S7, the source code analysis unit 4 calculates a second diversion rate based on the diversion source code and the diversion destination source code. In step S8, the source code analysis unit 4 registers the second diversion rate in the source code database 5 in association with the diversion source code. The processes in steps S4 to S8 are performed each time a development phase of the diversion destination source code ends. After that, the operation in FIG. 3 ends.

[0027] 3 may be performed for a plurality of diversion source codes and a plurality of diversion destination source codes. In addition, when a plurality of diversion destination source codes exist for one diversion source code, a single second diversion ratio may be calculated by performing statistical processing such as averaging on a plurality of second diversion ratios respectively calculated from the plurality of diversion destination source codes.

[0028] As will be described later, the source code analysis unit 4 calculates the first diversion rate based on the source code under development and the source code to be diverted, in the same way that the source code analysis unit 4 calculates the second diversion rate based on the source code to be diverted and the destination source code.

[0029] The source code analysis device 2 consisting of the above components is capable of registering not only source code of past projects, but also the reuse rate, which is the analysis result.

[0030] <Document Analysis Device> The document analysis device 6 includes a document registration device 7 , a document analysis unit 8 , and a document database 9 .

[0031] The document registration device 7 registers documents that are deliverables of a project in the document database 9. The documents to be registered include documents of the project under development, documents of the source project, and documents of the destination project.

[0032] In the following description, the document of the project under development, the document of the source project, and the document of the destination project may be abbreviated as the document under development, the source document, and the destination document, respectively.

[0033] The source document and the destination document are registered in the document database 9 at the end of each development phase. In this embodiment 1, information indicating the development phase of the document is added to the registered document. Also in this embodiment 1, functional information defined by the project or organization is added to the registered document in units defined by the project or organization (for example, source file units or function units). By adding the above information to the registered document, the document analysis unit 8 can perform a detailed analysis of the document, as described below.

[0034] The document analysis unit 8 calculates the second similarity rate by analyzing the source document and the destination document based on the source document and the destination document that are in the same development phase. For example, the document analysis unit 8 calculates the second similarity rate by using machine learning such as AI on the source document and the destination document. Note that the document analysis unit 8 may calculate the second similarity rate by performing a calculation similar to the second diversion rate of the source code analysis unit 4.

[0035] 4 is a diagram showing an example of the transition of similarity rates such as the second similarity rate with respect to the development phase. In general, the similarity rate drops significantly in the early stages of development because many changes are made in the design stage, and the degree of the drop becomes smaller in the software production phase.

[0036] The document analysis unit 8 registers the second similarity rate in the document database 9. The second similarity rate is calculated and registered for each development phase. This enables the evaluation unit 10, which will be described later, to refer to the second similarity rates in each development phase of past projects when evaluating documents and documents of the project under development.

[0037] FIG. 5 is a flowchart showing an example of the operation of the document analysis apparatus 6 according to the first embodiment for a past project.

[0038] In step S11, the document registration device 7 adds development phase information of the source document to the source document. In step S12, the document registration device 7 adds function information of the source document to the source document. In step S13, the document registration device 7 registers the source document in the document database 9. The processing of steps S11 to S13 is performed each time each development phase of the source document ends.

[0039] In step S14, the document registration device 7 adds development phase information of the destination document to the destination document. In step S15, the document registration device 7 adds function information of the destination document to the destination document. In step S16, the document registration device 7 registers the destination document in the document database 9.

[0040] In step S17, the document analysis unit 8 calculates a second similarity rate based on the source document and the destination document. In step S18, the document analysis unit 8 registers the second similarity rate in the document database 9 in association with the source document. The processes in steps S14 to S18 are performed each time a development phase of the destination document ends. After that, the operation in FIG. 5 ends.

[0041] 5 may be performed for a plurality of source documents and a plurality of destination documents. In addition, when a plurality of destination documents exist for one source document, a single second similarity rate may be calculated by performing a statistical process such as averaging on a plurality of second similarity rates respectively calculated from the plurality of destination documents.

[0042] As will be described later, the document analysis unit 8 calculates the first similarity rate based on the document under development and the source document, in the same way that it calculates the second similarity rate based on the source document and the destination document.

[0043] The document analysis device 6 consisting of the above components is capable of registering not only documents from past projects, but also the similarity rate that is the analysis result.

[0044] The information on past projects is stored in a database and analyzed by the above-described source code analysis device 2 and document analysis device 6. This creates evaluation data such as differences in development phases or development processes for each organization, and differences in the degree of change in the reuse rate and similarity rate for each development phase.

[0045] <Evaluation Department> The evaluation unit 10 evaluates the project under development based on the result of associating the first similarity rate or the first diversion rate with the second similarity rate regarding the diversion source document and the second diversion rate regarding the diversion source source code. An example of the evaluation by the evaluation unit 10 will be described later.

[0046] <Notification Department> The notification unit 11 notifies the evaluation result of the evaluation unit 10. An example of the notification by the notification unit 11 will be described later.

[0047] <Project evaluation device operation> 6 and 7 are flowcharts showing an example of the operation of the project evaluation device 1 according to the first embodiment for a project under development. In the following explanation, it is assumed that source codes and documents of a plurality of reuse source projects are registered in the project evaluation device 1. The operations in Fig. 6 and Fig. 7 are performed, for example, at the end of each development phase of the project under development.

[0048] In step S21, the source code registration device 3 adds development phase information of the source code under development to the source code under development. In step S22, the source code registration device 3 adds function information of the source code under development to the source code under development. In step S23, the source code registration device 3 registers the source code under development in the source code database 5.

[0049] In steps S24 to S28, the project evaluation device 1 selects an appropriated project to be compared with the project under development from among the multiple appropriated projects. First, in step S24, the project evaluation device 1 determines whether or not there is an appropriated project that has been appropriated to generate the project under development among the multiple appropriated projects. If it is determined that there is an appropriated project that has been appropriated to generate the project under development, the process proceeds to step S25, and if it is not determined that there is such an appropriated project, the process proceeds to step S26.

[0050] In step S25, the project evaluation device 1 selects the original project that has been diverted to generate the project under development as a project to be used in evaluating the project under development. After that, the process proceeds to step S29.

[0051] In step S26, the project evaluation device 1 calculates the development scale of the source code and the number of development functions of the project under development. The development scale here is, for example, the total amount of source code, and the number of development functions is, for example, the amount of code for each function.

[0052] Then, the project evaluation device 1 judges whether or not there is a diversion source project among the multiple diversion source projects that is similar to the project under development in terms of the development scale and number of development functions of the source code. For example, the project evaluation device 1 judges that the diversion source project is similar to the project under development when the differences between the development scale and number of development functions of the source code of the project under development and the development scale and number of development functions of the source code of the diversion source project are within a predetermined range. If it is judged that a diversion source project similar to the project under development exists, the process proceeds to step S27, and if it is not judged that such a diversion source project exists, the process proceeds to step S28.

[0053] In step S27, the project evaluation device 1 selects the source project similar to the project under development as a project to be used in evaluating the project under development. After that, the process proceeds to step S29.

[0054] In step S28, the project evaluation device 1 selects, from among the multiple source projects, the source project having the source code development scale closest to that of the project under development as the project to be used for evaluating the project under development. Then, the process proceeds to step S29.

[0055] In the following description, the reuse source project selected by the processing in steps S24 to S28 may be abbreviated to a selected project.

[0056] In step S29, the source code analysis unit 4 calculates a first reuse rate based on the source code of the project under development and the source code of the selected project.

[0057] In step S30, the source code analysis unit 4 registers the first reuse rate in the source code database 5 in association with the source code under development.

[0058] After step S30, in step S31 of Fig. 7, the document registration device 7 adds development phase information of the document under development to the document under development. In step S32, the document registration device 7 adds function information of the document under development to the document under development. In step S33, the document registration device 7 registers the document under development in the document database 9.

[0059] In step S34, the document analysis unit 8 calculates a first similarity rate based on the documents of the project under development and the documents of the selected project.

[0060] In step S35, the document analysis unit 8 registers the first similarity rate in the document database 9 in association with the document under development.

[0061] In step S36, the evaluation unit 10 evaluates the project under development based on the result of associating the first similarity rate or the first diversion rate with the second similarity rate and the second diversion rate. Note that the second similarity rate and the second diversion rate used in this evaluation are the second similarity rate and the second diversion rate calculated for the selected project. An example of evaluation by the evaluation unit 10 will be described below.

[0062] First, the evaluation unit 10 compares the document similarity rates (i.e., the first and second similarity rates) between the project under development and the selected project. The reason for comparing the document similarity rates before comparing the source code reuse rates is that changes to the document generally precede changes to the source code.

[0063] In order to perform the comparison, the evaluation unit 10 identifies a second similarity rate corresponding to the development phase of the project under development from the transition of the second similarity rates of the multiple development phases of the selected project. In the example of Fig. 8, the development phase of the project under development is Phase A, and Xa is identified as the second similarity rate.

[0064] If the selected project is not an original project that has been diverted to generate the project under development, that is, if step S27 or step S28 has been performed, the evaluation unit 10 corrects the second similarity rate Xa by the following formula (1). Similarly, if the development scale of the project under development and the development scale of the selected project differ, the evaluation unit 10 corrects the second similarity rate Xa by the following formula (1). Note that if the selected project is an original project that has been diverted to generate the project under development, that is, if step S25 has been performed, the evaluation unit 10 does not need to correct the second similarity rate Xa by the following formula (1).

[0065] Xa × (development scale of the project to be reused ÷ development scale of the project under development) (1)

[0066] Next, the evaluation unit 10 calculates the application ratio Rp in the development phase using the following formula (2). Note that as shown in the following formula (2), the application ratio Rp represents a comparison between the first similarity ratio Xp of the project under development and the appropriately corrected second similarity ratio Xa.

[0067] Rp = Xp ÷ Xa (2)

[0068] The evaluation unit 10 identifies a second diversion rate corresponding to the development phase of the project under development from the transition of the second diversion rates of the multiple development phases of the selected project. In the example of Fig. 9, the development phase of the project under development is Phase A, and Ya is identified as the second diversion rate.

[0069] The evaluation unit 10 applies the second diversion rate Ya and the application rate Rp to the following formula (3) to calculate an expected value Z1p of the diversion rate.

[0070] Z1p = Ya × Rp (3)

[0071] The evaluation unit 10 judges whether the expected value Z1p is within a range that is greater than a project lower limit value that has been previously determined for the project under development and less than a project upper limit value that has been previously determined for the project under development. For example, if the expected value Z1p is within the range, the evaluation unit 10 judges that the source code of the project under development is normal. For example, if the expected value Z1p is smaller than the lower limit value of the range, the evaluation unit 10 judges that the source code of the project under development is excessive. For example, if the expected value Z1p is greater than the upper limit value of the range, the evaluation unit 10 judges that the source code of the project under development is insufficient.

[0072] As described above, the evaluation unit 10 determines whether the source code of the project under development is insufficient or excessive by using the expected value Z1p that associates the first similarity rate Xp, the second similarity rate Xa, and the second diversion rate Ya, all of which are in the same development phase.

[0073] Next, the evaluation unit 10 uses the expected value Z2p, which associates the first diversion rate Yp, the second similarity rate Xa, and the second diversion rate Ya, all of which are in the same development phase, to determine whether the documents in the project under development are excessive or insufficient. For example, the expected value Z2p may be calculated by replacing the first similarity rate Xp, the second similarity rate Xa, and the second diversion rate Ya in the calculation of the expected value Z1p with the first diversion rate Yp, the second diversion rate Ya, and the second similarity rate Xa. Then, for example, when the expected value Z2p is within a range that is predetermined for the project under development, the evaluation unit 10 determines that the documents in the project under development are normal. For example, when the expected value Z2p is smaller than the lower limit of the range, the evaluation unit 10 determines that the documents in the project under development are excessive. For example, when the expected value Z2p is larger than the upper limit of the range, the evaluation unit 10 determines that the documents in the project under development are insufficient.

[0074] As described above, the evaluation unit 10 can determine whether there is a surplus or deficiency in the source code or the document of the project under development, and can therefore evaluate the project under development. The evaluation unit 10 may also evaluate whether there is a difference in the changes and modifications in the source code or the document of the project under development.

[0075] In step S37 of Fig. 7, the project evaluation device 1 judges whether or not to issue a report from the notification unit 11 based on the evaluation result of the evaluation unit 10. For example, when the evaluation result of the evaluation unit 10 indicates that there is an excess or deficiency in either the source code or the document of the project under development, or when there is a difference in the parts of the changes and corrections, it judges to issue a report from the notification unit 11. When it is judged that the notification unit 11 issues a report, the process proceeds to step S38, and when it is not judged that the notification unit 11 issues a report, the operation of Fig. 7 ends.

[0076] In step S38, the notification unit 11 notifies the manager of the project evaluation device 1 of the evaluation result of the evaluation unit 10. For example, if there is a surplus or deficiency in either the source code or the document of the project under development, or if there is a difference in the parts of the changes and corrections, the notification unit 11 notifies that fact. After that, the operation of FIG. 7 ends.

[0077] <Summary of the first embodiment> According to the first embodiment as described above, the project under development is evaluated based on Z1p, which is a result of associating the first similarity rate Xp, the second similarity rate Xa, and the second diversion rate Ya, and Z2p, which is a result of associating the first diversion rate Yp, the second similarity rate Xa, and the second diversion rate Ya. According to such a configuration, since the project under development is evaluated by associating different types of deliverables, it is possible to appropriately evaluate the project under development, for example, by evaluating the relative excess or deficiency of documents and source code.

[0078] In the first embodiment, the document analysis unit 8 calculates the second similarity rate based on the source document and the destination document. With this configuration, the second similarity rate can be appropriately updated to make it more appropriate.

[0079] In the first embodiment, the source code analysis unit 4 calculates the second diversion ratio based on the diversion source code and the diversion destination source code. With this configuration, the second diversion ratio can be appropriately updated to be appropriate.

[0080] Furthermore, in the first embodiment, the notification unit 11 notifies the evaluation result of the evaluation unit 10, so that the manager can find errors in the documents and source codes of the project under development.

[0081] In the first embodiment, the first similarity rate, the second similarity rate, and the second diversion rate used in the evaluation unit 10 are all in the same development phase, and the first diversion rate, the second similarity rate, and the second diversion rate used in the evaluation unit 10 are all in the same development phase. With this configuration, it is possible to improve the accuracy of, for example, evaluation of the relative excess or deficiency of the document and the source code.

[0082] <Variation 1> In the first embodiment, the evaluation unit 10 evaluates the project under development based on Z1p, which is a result of associating the first similarity rate Xp, the second similarity rate Xa, and the second diversion rate Ya, and Z2p, which is a result of associating the first diversion rate Yp, the second similarity rate Xa, and the second diversion rate Ya. However, the evaluation unit 10 may evaluate the project under development based on Z3p, which is a result of associating the first similarity rate Xp, the first diversion rate Yp, the second similarity rate Xa, and the second diversion rate Ya. For example, as Z3p, a value such as Xp×Yp÷(Xa×Ya) or a difference between the first diversion rate Yp and the expected value Z1p may be used.

[0083] <Variation 2> In the first embodiment, the second similarity rate is calculated by the document analysis unit 8, and the second diversion rate is calculated by the source code analysis unit 4, but this is not limiting. For example, at least one of the second similarity rate and the second diversion rate may be set and stored in advance in the project evaluation device 1.

[0084] <Other Modifications> The source code analysis unit 4, the document analysis unit 8, and the evaluation unit 10 in FIG. 1 described above are hereinafter referred to as the "source code analysis unit 4, etc." The source code analysis unit 4, etc. are realized by a processing circuit 81 shown in FIG. 10. That is, the processing circuit 81 includes a document analysis unit 8 that calculates a first similarity rate based on a document of a project to be evaluated and a document of a project to be compared among projects in which corresponding documents and source codes are generated as deliverables, a source code analysis unit 4 that calculates a first diversion rate based on a source code of the project to be evaluated and a source code of the project to be compared, and an evaluation unit 10 that evaluates the project to be evaluated based on at least one of the first similarity rate and the first diversion rate, a result of associating a second similarity rate related to the document of the project to be compared and a second diversion rate related to the source code of the project to be compared. The processing circuit 81 may be implemented with dedicated hardware, or may be implemented with a processor that executes a program stored in a memory. The processor may be, for example, a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, a DSP (Digital Signal Processor), or the like.

[0085] When the processing circuit 81 is a dedicated hardware, the processing circuit 81 corresponds to, for example, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a combination of these. Each function of the source code analysis unit 4 and the like may be realized by a circuit in which the processing circuits are distributed, or the functions of each unit may be realized by a single processing circuit.

[0086] When the processing circuit 81 is a processor, the functions of the source code analysis unit 4 and the like are realized by a combination with software and the like. The software and the like includes, for example, software, firmware, or software and firmware. The software and the like is written as a program and stored in a memory. As shown in FIG. 11, the processor 82 applied to the processing circuit 81 realizes the functions of each unit by reading and executing a program stored in the memory 83. That is, the project evaluation device 1 includes a memory 83 for storing a program that, when executed by the processing circuit 81, results in the following steps: calculating a first similarity rate based on a document of a project to be evaluated and a document of a project to be compared among projects in which corresponding documents and source codes are generated as deliverables; calculating a first diversion rate based on a source code of the project to be evaluated and a source code of the project to be compared; and evaluating the project to be evaluated based on a result of associating at least one of the first similarity rate and the first diversion rate with a second similarity rate related to the document of the project to be compared and the second diversion rate related to the source code of the project to be compared. In other words, this program can be said to cause a computer to execute the procedures and methods of the source code analysis unit 4, etc. Here, the memory 83 may be, for example, a non-volatile or volatile semiconductor memory such as a random access memory (RAM), a read only memory (ROM), a flash memory, an erasable programmable read only memory (EPROM), or an electrically erasable programmable read only memory (EEPROM), a hard disk drive (HDD), a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, a digital versatile disk (DVD), a drive device for any of these, or any storage medium to be used in the future.

[0087] The above describes a configuration in which each function of the source code analysis unit 4 and the like is realized either in hardware or software, etc. However, the present invention is not limited to this, and a configuration in which a part of the source code analysis unit 4 and the like is realized in dedicated hardware and another part is realized in software, etc. For example, the function of the source code analysis unit 4 can be realized by a processing circuit 81 and an interface as dedicated hardware, and the other functions can be realized by the processing circuit 81 as a processor 82 reading and executing a program stored in a memory 83.

[0088] As described above, the processing circuitry 81 can realize each of the above-mentioned functions by hardware, software, or a combination of these.

[0089] The project evaluation device described above can also be applied to a project evaluation system constructed as a system by appropriately combining a program creation device such as a personal computer, a communication terminal including a mobile terminal such as a mobile phone, a smartphone, and a tablet, the functions of an application installed in at least one of the program creation device and the communication terminal, and a server. In this case, each function or each component of the project evaluation device described above may be distributed among the devices that construct the system, or may be concentrated in one of the devices.

[0090] In addition, the embodiments can be modified or omitted as appropriate.

[0091] The above description is illustrative in all respects and is not restrictive. It is understood that countless variations not illustrated can be envisioned. [Explanation of symbols]

[0092] 1 Project evaluation device, 4 Source code analysis unit, 8 Document analysis unit, 10 Evaluation unit, 11 Notification unit.

Claims

1. a document analysis unit that calculates a first similarity rate based on the document of a project to be evaluated and the document of a project to be compared, among projects in which corresponding documents and source code are generated as deliverables; a source code analysis unit that calculates a first reuse rate based on the source code of the project to be evaluated and the source code of the project to be compared; an evaluation unit that evaluates the project to be evaluated based on a result of associating at least one of the first similarity rate and the first diversion rate with a second similarity rate regarding the document of the project to be compared and a second diversion rate regarding the source code of the project to be compared; A project evaluation device comprising:

2. The project evaluation device according to claim 1, The document analysis unit a project evaluation device that calculates the second similarity rate based on the documents of a diversion source project, which is the project to be compared, and the documents of a diversion destination project, which is the project obtained by diversion of the diversion source project.

3. The project evaluation device according to claim 1, The source code analysis unit a project evaluation device that calculates the second diversion rate based on the source code of a diversion source project, which is the project to be compared, and the source code of a diversion destination project, which is the project obtained by diversion of the diversion source project.

4. The project evaluation device according to any one of claims 1 to 3, The project evaluation device further comprises a notification unit that notifies the evaluation result of the evaluation unit.

5. The project evaluation device according to any one of claims 1 to 4, a project evaluation device, wherein at least one of the first similarity rate and the first diversion rate, the second similarity rate, and the second diversion rate used in the evaluation unit are all in the same development phase.

6. a document analysis unit calculates a first similarity rate based on the document of the project to be evaluated and the document of the project to be compared, among projects in which corresponding documents and source codes are generated as deliverables; a source code analysis unit calculates a first diversion rate based on the source code of the project to be evaluated and the source code of the project to be compared; a project evaluation method, in which an evaluation unit evaluates the project to be evaluated based on a result of associating at least one of the first similarity rate and the first reuse rate with a second similarity rate for the document of the project to be compared and a second reuse rate for the source code of the project to be compared.

Images