Specification learning level calculation device and specification learning level calculation method

Abstract

To provide a technique capable of managing an accurate specification learning level.SOLUTION: A specification learning level calculation device includes: a specification learning database generation part configured to generate a specification learning database; an oblivion determination part configured to determine whether or not a developer has forgotten a specification, according to time lapsed after the developer has learned the specification; a learning update part configured to update a presence / absence of learning in a specification learning database according to a determination result of the oblivion determination part; and a specification learning level calculation part configured to calculate a specification learning level of the developer according to the updated specification learning database.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present disclosure relates to a specification proficiency calculation device and a specification proficiency calculation method.

Background Art

[0002] In order to develop software by diversion, the development team needs to understand without omission the specifications regarding the added / changed parts and their influence ranges (for example, requirement specifications, design specifications, implementation specifications, technologies used, etc.). On the other hand, as the scale of the software developed by diversion increases, it becomes difficult for each member of the development team to grasp the specifications without omission. As a result, various specifications may become personalized to different members.

[0003] When the specifications become personalized to different members of the development team, during the development by diversion, only all members can conduct a proper review of the specifications regarding the influence range, and thus it becomes impossible to grasp the omission in presentation. Also, if other members cannot understand the specifications personalized to a member who has suddenly become absent, there is a concern that the progress of development may be hindered. In contrast, for example, in Patent Document 1, in a state where technologies, progress management, and schedule management, etc. are personalized in software development, a technique for analyzing the level of personalization for coding processes, specification design processes, external design processes, internal design processes, etc. has been proposed.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, in the prior art, only invariant metrics that can be obtained from the work product at a certain development time or immediately after the completion of development are used as inputs for analyzing the level of personalization, that is, the proficiency of the development team in the specifications. That is, in the prior art, for example, in consideration of the fact that humans forget the familiar specifications over time, it is not configured to change the specification proficiency. For this reason, the specification proficiency obtained by the prior art may be different from the actual specification proficiency, and there is a problem that the accurate specification proficiency cannot be grasped and managed.

[0006] Therefore, the present disclosure has been made in view of the above problems, and an object thereof is to provide a technique capable of managing accurate specification proficiency.

Means for Solving the Problems

[0007] The specification proficiency calculation device according to the present disclosure includes: an artifact analysis unit that analyzes the work product of software development and generates the specifications in the software development and developer information indicating the person related to the specifications as a developer; a specification proficiency database generation unit that generates a specification proficiency database indicating the presence or absence of the developer's proficiency for each of the plurality of specifications based on the specifications and the developer information; a forgetting determination unit that determines whether the developer has forgotten the specifications based on the time elapsed since the developer became proficient in the specifications; a proficiency update unit that updates the presence or absence of proficiency in the specification proficiency database based on the determination result of the forgetting determination unit; and a specification proficiency calculation unit that calculates the specification proficiency of the developer based on the updated specification proficiency database.

Effects of the Invention

[0008] According to the present disclosure, it is determined whether the developer has forgotten the specifications based on the time elapsed since the developer became proficient in the specifications, the presence or absence of proficiency in the specification proficiency database is updated based on the determination result, and the specification proficiency of the developer is calculated based on the updated specification proficiency database. With such a configuration, for example, accurate specification proficiency can be managed.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Mode for Carrying Out the Invention

[0010] <Embodiment 1> FIG. 1 is a block diagram showing the configuration of a specification proficiency calculation device 101 according to Embodiment 1 of the present invention. In the following description, the database may be abbreviated as DB. The specification proficiency calculation device 101 in FIG. 1 includes an artifact analysis unit 102, a specification proficiency DB generation unit 105, a specification proficiency calculation unit 107, a forgetting determination unit 108, and a proficiency update unit 109.

[0011] The artifact analysis unit 102 analyzes the artifact 103 of software development and generates a specification DB 104, which is a database of specifications in software development. The artifact 103 represents all artifacts in software development, such as design documents, source codes, test documents, and review documents for each of these. Also, the artifact 103 is not limited to these and may include intermediate artifacts such as project management information and work memos.

[0012] FIG. 2 is a diagram showing an example of the specification DB 104. The specification DB 104 in FIG. 2 includes a plurality of specifications, and a unique ID is assigned to each specification. For each specification, a development process for classifying the specification broadly, an artifact for classifying the specification moderately, an item for classifying the specification finely, the specification content, and the registration date are set.

[0013] In the specification where the development process is "requirement" or "specification", the content within <> which has the role of classification by USDM (Universal Specification Describing Manner), a specification technique for defining accurate requirement specifications, is set for the sub-classification items. For the specification content, the content extracted by USDM in one-line units is set.

[0014] In the specification where the development process is "design", the headings of the design documents are set for the sub-classification items. For the specification content, the content of those headings (for example, the content for each sentence or each paragraph) is set.

[0015] In the specification where the development process is "implementation", various granularity contents such as folder names, file names, variable names, function names, and cyclomatic complexity are set for the sub-classification items. When a folder name is set for an item, for the specification content, the group of files stored in the folder with that folder name is set. When a file name is set for an item, for the specification content, the variables or functions defined or declared within the file with that file name are set. When a variable name or function name is set for an item, for the specification content, the explanatory text described in their comments or various metrics such as reference relationships are set.

[0016] In the specification where the development process is "test (document)", function headers, test cases, etc. are set for the sub-classification items. For the specification content, the content in accordance with the design specification and implementation specification is set, and when the item is test code, the input values and expected values are set.

[0017] For the registration date of the specification, for example, the creation date described in the work product may be set, or the commit date and time used in version control tools such as Git may be set.

[0018] The deliverable analysis unit 102 in FIG. 1 analyzes the deliverable 103 and generates not only the specification DB 104 but also developer information. The developer information is information indicating persons related to the specification as developers, and the persons related to the specification are, for example, those who may be familiar with the specification, such as the creator of the specification, the reviewer of the specification, and the commit user.

[0019] The developer may be each member of the development team or the entire group of a plurality of members of the development team. The plurality of members may be, for example, all of the plurality of members of the development team, or a plurality of members belonging to a group defined by the user, or a plurality of members with similar specification proficiency values defined by the specification proficiency calculation device 101. Note that the specification proficiency will be described later.

[0020] For example, the deliverable analysis unit 102 may obtain, as a developer, the specification creator or reviewer described in the person-in-charge information included in the deliverable 103, and generate, as developer information, information indicating that the developer is familiar with the specification that the developer is in charge of. Also, for example, the deliverable analysis unit 102 may obtain, as a developer, the commit user of the deliverable used in a version control tool such as Git, and generate, as developer information, information indicating that the developer is familiar with the specification that the developer is in charge of.

[0021] Based on the specification DB 104 and the developer information generated by the deliverable analysis unit 102, the specification proficiency DB generation unit 105 generates a specification proficiency DB 106 indicating the presence or absence of developer proficiency for each of the plurality of specifications. For example, when the developer information indicates that the developer is familiar with any one of the specifications in the specification DB 104, the specification proficiency DB generation unit 105 sets the developer's proficiency with respect to the specification to "proficient". On the other hand, when the developer information does not indicate that the developer is familiar with any one of the specifications in the specification DB 104, the specification proficiency DB generation unit 105 sets the developer's proficiency with respect to the specification to "not proficient". Note that the specification proficiency DB generation unit 105 generates the specification proficiency DB 106 for each developer.

[0022] FIG. 3 is a diagram showing an example of a specification proficiency DB 106 of a certain developer. The IDs included in the specification proficiency DB 106 are associated with the IDs in FIG. 2 included in the specification DB 104. Proficiency indicates whether the developer is proficient in the specification. When the developer is proficient in the specification, TRUE indicating "proficient" is set for proficiency, and when the developer is not proficient in the specification, FALSE indicating "not proficient" is set for proficiency. For the proficiency date, similar to the registration date of the specification, for example, the creation date described in the work product may be set, or the commit date and time used in a version control tool such as Git may be set.

[0023] Based on the specification proficiency DB 106, the specification proficiency calculation unit 107 in FIG. 1 calculates the specification proficiency of the developer for the software. For example, the specification proficiency calculation unit 107 calculates 87% (= 13 / 15 × 100) as the specification proficiency of the developer by applying the data in the specification proficiency DB 106 in FIG. 3 to the following formula (1).

[0024]

Equation

[0025] The specification proficiency is calculated on a per-developer basis (for example, per member of the development team or per multiple members of the development team). The specification proficiency calculation unit 107 outputs at least one of the data in the specification proficiency DB 106 and the specification proficiency by at least one of display and transmission. Note that instead of the specification proficiency calculation unit 107 performing the output, other components of the specification proficiency calculation apparatus 101 (such as an output unit not shown in the figure) may perform the output. Also, in this specification, for example, at least one of A, B, C,..., and Z means any one of all combinations extracted from the group of A, B, C,..., and Z, with one or more types.

[0026] The forgetting determination unit 108 determines whether the developer has forgotten the specifications based on the elapsed time of proficiency. The elapsed time of proficiency is the time elapsed since the developer became proficient in the specifications. For example, it is the time from the point when the developer became proficient in the specifications to the current time. The point when the developer became proficient in the specifications is, for example, the point indicated by a numerical value input by the developer or the point when the work product was generated, and the current time is, for example, the point when the forgetting determination unit 108 makes a determination.

[0027] For example, when the elapsed time of proficiency exceeds a threshold value, the forgetting determination unit 108 determines that the developer has forgotten the specifications. The forgetting determination unit 108 according to the first embodiment sets the threshold value based on, for example, the forgetting curve of Ebbinghaus. The approximate formula of the forgetting curve of Ebbinghaus is expressed as the following formula (2).

[0028]

Number

[0029] Here, b is the savings rate [%], and t is the elapsed time [minutes]. The savings rate is a ratio representing how much time (or number of times) required to completely re - remember the content once memorized can be saved. For example, when it is assumed that a state where the savings rate is less than 20% is a state where the developer has forgotten the specifications, substituting 20 into b in formula (2) gives approximately 2 months as the elapsed time t. In this case, the forgetting determination unit 108 sets 2 months as the above - mentioned threshold value, and determines that the developer has forgotten the specifications when the elapsed time of proficiency exceeds 2 months.

[0030] The proficiency update unit 109 updates the presence or absence of proficiency in the proficiency DB 106 based on the determination result of the forgetting determination unit 108. For example, when the forgetting determination unit 108 determines that the developer has forgotten the specification with ID3 in the proficiency DB 106 of FIG. 3, the proficiency update unit 109 updates the proficiency of ID3 from TRUE to FALSE.

[0031] When the specification proficiency DB 106 is updated, the specification proficiency calculation unit 107 calculates the specification proficiency for each developer in the same manner as described above based on the updated specification proficiency DB 106. The specification proficiency calculation unit 107 outputs at least one of the data in the updated specification proficiency DB 106 and the specification proficiency.

[0032] <Operation> FIG. 4 is a flowchart showing the operation of the specification proficiency calculation device 101 according to the first embodiment for calculating the specification proficiency before the update of the specification proficiency DB 106.

[0033] In step S1, the work product analysis unit 102 analyzes the work product 103 to generate the specification DB 104 and developer information. In step S2, the specification proficiency DB generation unit 105 generates the developer's specification proficiency DB 106 based on the specification DB 104 and the developer information. In step S3, the specification proficiency calculation unit 107 calculates the specification proficiency for each developer based on the specification proficiency DB 106, and outputs at least one of the data in the specification proficiency DB 106 and the specification proficiency. Then, the operation in FIG. 4 ends.

[0034] FIG. 5 is a flowchart showing the operation of the specification proficiency calculation device 101 according to the first embodiment for calculating the specification proficiency after the update of the specification proficiency DB 106.

[0035] In step S6, the forgetting determination unit 108 determines whether a developer has forgotten the specification based on the proficiency elapsed time. In step S7, the proficiency update unit 109 updates the presence or absence of proficiency in the specification proficiency DB 106 based on the determination result of the forgetting determination unit 108. In step S8, the specification proficiency calculation unit 107 calculates the specification proficiency for each developer based on the updated specification proficiency DB 106, and outputs at least one of the data in the updated specification proficiency DB 106 and the specification proficiency. Then, the operation in FIG. 5 ends.

[0036] <Summary of the First Embodiment> According to the first embodiment as described above, the specification proficiency that varies due to forgetting over time is calculated. As a result, for example, the user can grasp and manage the accurate specification proficiency by visualizing the specification proficiency, etc., so that a software development plan can be accurately formulated. Further, the specification proficiency is calculated for each developer. As a result, for example, the user can easily grasp and manage which specifications are assigned to which members of the development team by visualizing the specification proficiency, etc., so that it is possible to easily grasp the specifications for which personalization should be preferentially eliminated.

[0037] <Second Embodiment> FIG. 6 is a block diagram showing the configuration of the specification proficiency calculation device 101 according to the second embodiment. Hereinafter, among the components according to the second embodiment, the same or similar components as the above-described components are given the same or similar reference numerals, and different components will be mainly described.

[0038] The configuration of FIG. 6 is the same as the configuration of FIG. 1 with the addition of a traceability analysis unit 301, a partial specification proficiency DB generation unit 401, and a highlighted part extraction unit 403.

[0039] Similar to the first embodiment, the work product analysis unit 102 analyzes the work product 103 to generate the specification DB 104 and the developer information, and the specification proficiency DB generation unit 105 generates the developer's specification proficiency DB 106 based on the specification DB 104 and the developer information. Thereafter, when the work product 103 is updated, the work product analysis unit 102 analyzes and compares the work product 103 before and after the update to generate an updated specification DB 201 corresponding to the update content of the specification DB 104 and the update content of the developer information. Note that the update includes at least one of addition, deletion, and change. The content of the updated specification DB 201 may conform to the content of the specification DB 104.

[0040] In Embodiment 2, the deliverable analysis unit 102 integrates the contents of the updated specification DB 201 into the specification DB 104. FIG. 7 is a diagram showing an example of the specification DB 104 into which the contents of the updated specification DB 201 are integrated. In the example of FIG. 7, specifications with IDs 16, 17, and 18 were added on April 1, 2023, and the registration dates of IDs 16, 17, and 18 are set respectively on the deletion dates of the specifications with IDs 1, 2, and 11, which are the specifications before the change. The setting of the deletion date means that the specification before the change has been deleted.

[0041] The traceability analysis unit 301 in FIG. 6 analyzes the deliverable 103 and generates a traceability DB 302, which is traceability for associating specifications with each other. For example, the traceability analysis unit 301 generates the traceability DB 302 based on the traceability relationships among the deliverables 103.

[0042] In Embodiment 2, the traceability analysis unit 301 integrates the contents of the traceability DB 302 into the specification DB 104. In the example of FIG. 7, the REQ-ID of USDM is used as the traceability of the traceability DB 302. By REQ-01, the specifications with IDs 1, 2, 5, 7, 8, 9, 10, 11, 12, 13, 16, 17, and 18 are associated, and by REQ-02, the specifications with IDs 3, 4, 6, 7, 14, and 15 are associated.

[0043] The forgetting determination unit 108 in FIG. 6 determines that when a developer updates a specification, the developer has not forgotten the specification updated by the developer and the specification associated by the traceability DB 302. The reason is that when the developer updates and defines a specification, it is considered that the developer also grasps the existing specifications associated by the traceability DB 302.

[0044] As a specific process of the above determination, for example, the forgetting determination unit 108 identifies, from the specifications included in the specification DB 104 but not included in the update specification DB 201, the specifications associated with the specifications included in the update specification DB 201 by the traceability DB 302. Then, the forgetting determination unit 108 determines that the identified specifications have not been forgotten by the developer. As a result of this determination, the proficiency update unit 109 sets the proficiency of the identified specifications in the specification proficiency DB 106 to TRUE.

[0045] Next, with reference to FIG. 8, the proficiency update unit 109 according to the second embodiment will be described. FIG. 8 is a diagram showing an example of the specification proficiency DB 106 updated by the proficiency update unit 109 according to the second embodiment. Here, it will be described on the premise that the specification DB 104 in FIG. 2 and the specification proficiency DB 106 in FIG. 3 are generated by analyzing the work product 103 on January 1, 2023, and the specification DB 104 in FIG. 7 is generated by analyzing the work product 103 on April 1, 2023.

[0046] Similar to the first embodiment, the proficiency update unit 109 updates the presence or absence of proficiency in the specification proficiency DB 106 based on the determination by the forgetting determination unit 108 based on the proficiency elapsed time. The specifications of ID3, 4, and 6 were proficient as of January 1, 2023 as shown in FIG. 3. However, since the proficiency elapsed time of the specifications of ID3, 4, and 6 (that is, three months) exceeds the threshold value (for example, two months) and it is determined that forgetting has occurred, the proficiency update unit 109 updates the proficiency of these specifications to FALSE as shown in FIG. 8.

[0047] The proficiency update unit 109 updates the specifications and the presence or absence of proficiency in the specification proficiency DB 106 based on the specification DB 104 in FIG. 7 including the updated content of the specifications and the updated content of the developer information. Since the specifications of IDs 16, 17, and 18 are the specifications updated on April 1, 2023, as shown in FIG. 8, the proficiency update unit 109 sets the proficiency of these specifications to TRUE and sets the proficiency date to 2023 / 4 / 1. Also, although the specifications of IDs 1, 2, and 11 that are the basis of the specifications of IDs 16, 17, and 18 were registered on January 1, 2023 as shown in FIG. 2, they are the specifications deleted on April 1, 2023. Therefore, as shown in FIG. 8, the proficiency update unit 109 sets the proficiency of these specifications to blank and maintains the proficiency date as it is.

[0048] For the specifications in the specification proficiency DB 106 that the forgetting determination unit 108 determines that the developer has not forgotten due to the association of the traceability DB 302, the proficiency update unit 109 sets the proficiency to TRUE. The specifications of IDs 5, 7, 8, 9, 10, 12, and 13 were not updated on April 1, 2023, but are associated with the specifications of IDs 16, 17, and 18 updated on that day by the traceability of REQ-01 as shown in FIG. 7. Therefore, as shown in FIG. 8, the proficiency update unit 109 maintains the proficiency of the specifications of IDs 5, 7, 8, 9, 10, 12, and 13 as TRUE and sets the proficiency date to 2023 / 4 / 1.

[0049] The specifications of IDs 14 and 15 are valid specifications on April 1, 2023, but since the developer of this example is not proficient in them, as shown in FIG. 8, the proficiency update unit 109 maintains the proficiency of these specifications as FALSE and maintains the proficiency date as blank.

[0050] When the specification proficiency DB 106 is updated as described above, the specification proficiency calculation unit 107 in FIG. 6 calculates the specification proficiency for each developer based on the updated specification proficiency DB 106. For example, the specification proficiency calculation unit 107 calculates 67% (= 10 / 15 × 100) as the specification proficiency of the developer by applying the data in the specification proficiency DB 106 in FIG. 8 to the following formula (3).

[0051]

Number

[0052] Here, for the specifications deleted by the update of the update specification DB 201, it is necessary to exclude them from the calculation of the specification proficiency. Therefore, in the denominator of formula (3), the total number of valid specifications, that is, the total number of specifications in which the proficiency value of the specification proficiency DB 106 is not blank and TRUE or FALSE is set, is used. The specification proficiency calculation unit 107 outputs at least one of the data of the updated specification proficiency DB 106 and the specification proficiency.

[0053] The partial specification proficiency DB generation unit 401 in FIG. 6 generates a partial specification proficiency DB 402 by classifying the specification proficiency DB 106 for each specification group, which is a group of specifications based on the user's designation. The user's designation may be, for example, that at least one of the development process, work product, item, and traceability included in the specification DB 104 in FIG. 7 exactly matches, or is similar, or is a group of IDs classified by the user.

[0054] FIG. 9 is a diagram showing an example of the partial specification proficiency DB 402 obtained by classifying the specification proficiency DB 106 in the specification group of traceability "REQ-01". FIG. 10 is a diagram showing an example of the partial specification proficiency DB 402 obtained by classifying the specification proficiency DB 106 in the specification group of traceability "REQ-02".

[0055] Based on the partial specification proficiency DB 402, the specification proficiency calculation unit 107 calculates the developer's partial specification proficiency in the same way as the developer's specification proficiency. For example, based on the partial specification proficiency DB 402 in FIG. 9, the specification proficiency calculation unit 107 calculates 100% (= 10 / 10 × 100) as the developer's partial specification proficiency for the specifications within the specification group of "REQ-01" in terms of traceability. Also, for example, based on the partial specification proficiency DB 402 in FIG. 10, the specification proficiency calculation unit 107 calculates 17% (= 1 / 6 × 100) as the developer's partial specification proficiency for the specifications within the specification group of "REQ-02" in terms of traceability.

[0056] Similar to the specification proficiency, the partial specification proficiency is calculated on a per-developer basis (for example, per member of the development team or per multiple members of the development team). The partial specification proficiency calculated based on the partial specification proficiency DB 402 is associated with the partial specification proficiency DB 402. The specification proficiency calculation unit 107 outputs at least one of the data of the partial specification proficiency DB 402 and the partial specification proficiency.

[0057] The highlighted part extraction unit 403 extracts the partial specification proficiency DB 402 for which the partial specification proficiency corresponds to the representative value as the highlighted part DB 404, which is the database of the highlighted part. For example, when the partial specification proficiency DB 402 in FIGS. 9 and 10 is obtained and the representative value is the highest value, the highlighted part extraction unit 403 extracts the partial specification proficiency DB 402 in FIG. 9 with the highest partial specification proficiency as the highlighted part DB 404. For example, when the partial specification proficiency DB 402 in FIGS. 9 and 10 is obtained and the representative value is the lowest value, the highlighted part extraction unit 403 extracts the partial specification proficiency DB 402 in FIG. 10 with the lowest partial specification proficiency as the highlighted part DB 404. Note that the representative value may be a representative value of statistical quantities such as the median, average value, and mode, in addition to the highest value and the lowest value. The specification proficiency calculation unit 107 outputs the data of the highlighted part DB 404.

[0058] <Operation> FIG. 11 is a flowchart showing the operation of the specification proficiency calculation device 101 according to the second embodiment.

[0059] In step S11, the deliverable analysis unit 102 analyzes and compares the deliverables 103 before and after the update, thereby generating an updated specification DB 201 corresponding to the update content of the specification DB 104 and the update content of the developer information. In step S12, the deliverable analysis unit 102 integrates the content of the updated specification DB 201 into the specification DB 104.

[0060] In step S13, the traceability analysis unit 301 analyzes the deliverable 103 to generate a traceability DB 302. In step S14, the traceability analysis unit 301 integrates the content of the traceability DB 302 into the specification DB 104. In step S15, the forgetting determination unit 108 determines whether the developer has forgotten the specification based on the familiarity elapsed time and the traceability DB 302. In step S16, the familiarity update unit 109 updates the presence or absence of familiarity in the specification familiarity DB 106 based on the determination result of the forgetting determination unit 108.

[0061] In step S17, the partial specification familiarity DB generation unit 401 generates a partial specification familiarity DB 402 by classifying the updated specification familiarity DB 106 for each specification group based on the user's designation. In step S18, the specification familiarity degree calculation unit 107 calculates the developer's specification familiarity degree based on the updated specification familiarity DB 106 and calculates the developer's partial specification familiarity degree based on the partial specification familiarity DB 402.

[0062] In step S19, the partial specification familiarity DB 402 corresponding to the representative value of the partial specification familiarity degree is extracted as the attention part DB 404. The specification familiarity degree calculation unit 107 outputs at least one of the data of the updated specification familiarity DB 106, the specification familiarity degree, the data of the partial specification familiarity DB 402, the partial specification familiarity degree, and the data of the attention part DB 404. Then, the operation of FIG. 11 ends.

[0063] <Summary of Embodiment 2> According to the second embodiment as described above, it is determined that the change in the work product 103 is reflected in the specification proficiency level, and the specification updated by the developer and the specification associated by the traceability DB 302 are not forgotten. As a result, for example, the user can grasp and manage the remaining tasks of the changed development by visualizing the specification proficiency level in line with the actual situation, so that the software development plan can be accurately established.

[0064] In the second embodiment, the partial specification proficiency DB 402 corresponding to the representative value of the partial specification proficiency is extracted as the attention part DB 404. As a result, for example, the user can easily grasp the specifications that should be prioritized for proficiency by visualizing the attention part DB 404.

[0065] <Embodiment 3> FIG. 12 is a block diagram showing the configuration of the specification proficiency calculator 101 according to the third embodiment. Hereinafter, among the components according to the third embodiment, the same or similar components as the above-described components are denoted by the same or similar reference numerals, and different components will be mainly described.

[0066] The configuration of FIG. 12 is the same as the configuration of FIG. 6 with the addition of a proficiency deadline acquisition unit 501, a risk level calculation unit 503, a reference configuration acquisition unit 601, and a risk level correction unit 603.

[0067] The proficiency deadline acquisition unit 501 acquires a proficiency deadline 502 which is the deadline for mastering the specifications within the specification group. The specification group may be the entire software or a group such as the traceability "REQ-01". In the third embodiment, the developers are a plurality of members of the development team, and the proficiency deadline 502 is acquired in units of the plurality of members. In the following description, a case where a two-person development team consisting of Mr. A and Mr. B is developing the work product 103 will be described as an example, but the plurality of members of the development team are not limited to this.

[0068] FIG. 13 is a diagram showing an example of the specification DB 104, FIG. 14 is a diagram showing an example of the specification proficiency DB 106 of Mr. A, and FIG. 15 is a diagram showing an example of the specification proficiency DB 106 of Mr. B. In the following, the proficiency deadline 502 includes development plan information. In the development plan information, taking as an example the case where it is stipulated that the development of a function to subtract a numerical value after one week (5 business days) is to be started and that at least one of Mr. A and Mr. B needs to be proficient in the specification of the traceability "REQ-01". Note that the proficiency deadline 502 may include, instead of the development plan information, for example, development strategy information, developer personnel transfer information, and personnel training plans.

[0069] Based on the proficiency deadline 502 acquired by the proficiency deadline acquisition unit 501 and the partial specification proficiency DB 402, the risk calculation unit 503 calculates the risk that a developer cannot be proficient in the specifications within the specification group within the proficiency deadline 502. As a result, a risk DB 504, which is a database of risks, is generated.

[0070] FIG. 16 is a diagram showing an example of the risk DB 504. First, based on the proficiency deadline 502, the risk calculation unit 503 sets the traceability and proficiency period in FIG. 16. Then, the risk calculation unit 503 acquires the partial specification proficiency DB 402 of the specification group with the traceability "REQ-01" of Mr. A and the partial specification proficiency DB 402 of the specification group with the traceability "REQ-01" of Mr. B. That is, the risk calculation unit 503 acquires the partial specification proficiency DB 402 from which the proficiency of the specifications with IDs 1, 2, 5, 7 to 13 has been extracted from the specification proficiency DB 106 in FIGS. 14 and 15.

[0071] The risk calculation unit 503 calculates the partial specification proficiency for each specification by taking the logical product (AND) of the presence or absence of proficiency in the partial specification proficiency DB 402 for Mr. A and the presence or absence of proficiency in the partial specification proficiency DB 402 for Mr. B, and calculates the partial specification proficiency based on the value obtained thereby. Among the specifications of ID1, 2, 5, 7 to 13 (10 specifications) in the partial specification proficiency DB 402 in FIGS. 14 and 15, the specification for which TRUE is set in both FIGS. 14 and 15 is the specification of ID7 (1 specification). For this reason, the risk calculation unit 503 calculates 10% (= 1 / 10 × 100) as the partial specification proficiency and sets it for the partial specification proficiency related to REQ-1 in FIG. 16.

[0072] The risk calculation unit 503 calculates the risk by applying the proficiency period and the partial specification proficiency in FIG. 16 to the following formula (4).

[0073]

Equation

[0074] Here, c is the amount of increase in the partial specification proficiency [%] per day. When c = 1, that is, when it is necessary to spend one day to improve the partial specification proficiency by 1%, and when the proficiency period and the partial specification proficiency in FIG. 16 are obtained, the risk calculation unit 503 calculates 85% (= 100 - 10 - 1×5) as the risk. Note that the value of c may be changed by the user.

[0075] Items not set in the proficiency deadline 502 may be excluded from the risk calculation. Also, for example, the traceability and the partial specification proficiency in FIG. 16 may be set based on the proficiency deadline 502 and the partial specification proficiency DB 402, and a "-" indicating exclusion may be set for the proficiency deadline and the risk in FIG. 16.

[0076] Note that the partial specification proficiency DB402 of the specification group "REQ-02" for tracing A and B corresponds to the DB in which the proficiency of the specifications with IDs 3, 4, 6, 7, 14, and 15 has been extracted from the specification proficiency DB106 in FIGS. 14 and 15. Among the specifications with IDs 3, 4, 6, 7, 14, and 15 (6 specifications) in the partial specification proficiency DB402 in FIGS. 14 and 15, the specification with ID 7 (1 specification) is the one for which TRUE is set in both FIGS. 14 and 15. Therefore, 17% (=1 / 6×100) is set as the partial specification proficiency related to REQ-2 in FIG. 16.

[0077] When the proficiency deadline 502 is defined for the entire software, the risk calculation unit 503 may use the partial specification proficiency DB402 or may use the specification proficiency DB106 without considering the specification group unit to calculate the risk for the entire software.

[0078] The specification proficiency calculation unit 107 outputs the data in the risk DB 504.

[0079] The reference configuration acquisition unit 601 acquires a reference configuration 602 that is the assignment of the specifications to be mastered by a plurality of members of the development team. The reference configuration 602 includes, for example, each of a plurality of members of the development team mastering the specifications (hereinafter referred to as "the former reference configuration 602"), or at least one of a plurality of members of the development team mastering the specifications (hereinafter referred to as "the latter reference configuration 602").

[0080] The risk correction unit 603 corrects the risk in the risk DB 504 based on the reference configuration 602. In the case of the former reference configuration 602, the risk correction unit 603 takes a logical product (AND) for each specification regarding the presence or absence of proficiency in the partial specification proficiency DB 402 of a plurality of members, and corrects the risk in the risk DB 504 based on the value obtained thereby. On the other hand, in the case of the latter reference configuration 602, the risk correction unit 603 takes a logical sum (OR) for each specification regarding the presence or absence of proficiency in the partial specification proficiency DB 402 of a plurality of members, and corrects the risk in the risk DB 504 based on the value obtained thereby. The risk in the risk DB 504 in the case of the former reference configuration 602 is the same as the risk in FIG. 16.

[0081] FIG. 17 is a diagram showing an example of the risk DB 504 in the case of the latter reference configuration 602. Among the specifications of ID1, 2, 5, 7 to 13 (10 specifications) in the partial specification proficiency DB 402 of FIGS. 14 and 15, TRUE is set in at least one of FIGS. 14 and 15 for all 10 specifications. Therefore, the risk correction unit 603 calculates 100% (= 10 / 10 × 100) as the partial specification proficiency and sets it to the partial specification proficiency related to REQ-1 in FIG. 17. The risk correction unit 603 calculates -5% (= 100 - 100 - 1 × 5) as the risk by applying the proficiency period and partial specification proficiency in FIG. 17 to Equation (4). The risk correction unit 603 may set a negative value such as -5% to the risk in FIG. 17, or may set 0% instead of the negative value.

[0082] For example, when the risk calculation unit 503 generates the risk DB 504 for the former reference configuration 602 and then the reference configuration acquisition unit 601 acquires the latter reference configuration 602, the risk correction unit 603 corrects the risk by correcting the risk DB 504 in FIG. 16 to the risk DB 504 in FIG. 17. When the risk correction unit 603 corrects the risk DB 504, the specification proficiency calculation unit 107 outputs the data of the corrected risk DB 504.

[0083] <Operation> FIG. 18 is a flowchart showing the operation of the specification proficiency calculator 101 according to Embodiment 3.

[0084] In step S21, the proficiency deadline acquisition unit 501 acquires the proficiency deadline 502. In step S22, the risk calculation unit 503 calculates the risk based on the proficiency deadline 502 and the partial specification proficiency DB 402, and the risk DB 504 is generated.

[0085] In step S23, the reference configuration acquisition unit 601 acquires the reference configuration 602. In step S24, the risk correction unit 603 corrects the risk DB 504 based on the reference configuration 602. In step S25, the specification proficiency calculation unit 107 outputs the data of the corrected risk DB 504. After that, the operation of FIG. 18 ends.

[0086] <Summary of Embodiment 3> According to Embodiment 3 as described above, the risk is calculated for the proficiency deadline 502 provided for various reasons. As a result, for example, the user can easily grasp the problem of the development status by visualizing the risk, and thus can appropriately formulate the future development policy.

[0087] Also, in Embodiment 3, the risk is corrected based on the reference configuration 602. As a result, the accuracy of the risk can be improved, and for example, the user can more appropriately formulate the future development policy.

[0088] <Embodiment 4> FIG. 19 is a block diagram showing the configuration of the specification proficiency calculator 101 according to Embodiment 4. Hereinafter, among the components according to Embodiment 4, the same or similar components as the above-described components are denoted by the same or similar reference numerals, and different components will be mainly described.

[0089] The configuration of FIG. 19 is the same as the configuration of FIG. 12 with the specification presentation unit 701 and the priority setting unit 801 added.

[0090] The specification presentation unit 701 presents the specifications in the specification DB 104 and the data in the specification proficiency DB 106 to users such as developers. Note that the method of presenting the specifications in the specification DB 104 may be, for example, simply presenting the specifications, or presenting the specifications in a quiz format and asking the user for an answer. The quiz mentioned here includes, for example, multiple-choice questions, true / false questions, multiple-selection questions, descriptive questions, fill-in-the-blank questions, rearrangement questions, combination questions, etc. The specification presentation unit 701 may finally present the specifications that are the correct answers to the quiz regardless of the content of the user's answer.

[0091] The timing at which the specification presentation unit 701 presents the specifications may be, for example, random timing, a regular schedule, or timing specified by the user. The specification presentation unit 701 includes the specifications confirmed by the developer in the confirmed specification DB 702. The confirmed specification DB 702 includes information such as the developer, the confirmation date, and the ID of the specification DB 104, corresponding to information on which developer confirmed which specification at what time.

[0092] Based on the confirmed specification DB 702, the forgetting determination unit 108 determines that the developer has not forgotten the presented specifications when the specifications presented by the specification presentation unit 701 are confirmed by the developer. As a result, the proficiency update unit 109 sets the proficiency of the specifications determined not to be forgotten in the specification proficiency DB 106 to TRUE. For example, in the specification proficiency DB 106 of FIG. 8 in the first embodiment, when the developer confirms the specification with ID 14, the proficiency update unit 109 updates the proficiency value of the specification with ID 14 from FALSE to TRUE and sets the confirmation date of the confirmed specification DB 702 as the proficiency date.

[0093] The priority setting unit 801 sets the priority of presenting the specifications in the specification presenting unit 701 based on at least one of the partial specification proficiency and the proficiency deadline 502, and outputs the priority to the specification presenting unit 701. For example, the priority setting unit 801 sets the priority so that the specification with the lowest partial specification proficiency among the specification DB 104 is presented preferentially, or so that the specification with the shortest proficiency deadline 502 and the proficiency set to FALSE among the specification DB 104 is presented preferentially. The specification presenting unit 701 presents the specifications based on the priority.

[0094] <Operation> FIG. 20 is a flowchart showing the operation of the specification proficiency calculation device 101 according to the fourth embodiment.

[0095] In step S31, the priority setting unit 801 sets the priority based on at least one of the partial specification proficiency and the proficiency deadline 502. In step S32, the specification presenting unit 701 presents the specifications in the specification DB 104 to the user, and includes the specifications confirmed by the developer in the confirmed specification DB 702. In step S33, the forgetting determination unit 108 determines whether the developer has forgotten the specifications based on the proficiency elapsed time and the confirmed specification DB 702. In step S34, the proficiency update unit 109 updates the presence or absence of proficiency in the specification proficiency DB 106 based on the determination result of the forgetting determination unit 108.

[0096] In step S35, the partial specification proficiency DB generation unit 401 generates the partial specification proficiency DB 402 by classifying the updated specification proficiency DB 106 for each specification group based on the user's designation. In step S36, the specification proficiency calculation unit 107 calculates the developer's specification proficiency based on the updated specification proficiency DB 106, and calculates the developer's partial specification proficiency based on the partial specification proficiency DB 402.

[0097] In step S37, a partial specification proficiency DB 402 corresponding to the representative value of the partial specification proficiency is extracted as the target partial DB 404. The specification proficiency calculation unit 107 outputs at least one of the data of the updated specification proficiency DB 106, the specification proficiency, the data of the partial specification proficiency DB 402, the partial specification proficiency, and the data of the target partial DB 404. Then, the operation in FIG. 20 ends.

[0098] <Summary of Embodiment 4> According to the fourth embodiment as described above, the specifications developed in the past are presented. Thereby, for example, developers can review the specifications developed in the past to suppress the forgetting of specifications over time and regularly master unfamiliar specifications, so that the specification reconfirmation process can be shortened.

[0099] Also, in the fourth embodiment, the priority of presenting the specifications by the specification presentation unit 701 is set based on at least one of the partial specification proficiency and the proficiency deadline 502. Thereby, developers can efficiently review the specifications that are most recently required in the development.

[0100] <Other Variations> The above-described work product analysis unit 102, specification proficiency DB generation unit 105, specification proficiency calculation unit 107, forgetting determination unit 108, and proficiency update unit 109 of FIG. 1 are hereinafter referred to as the "work product analysis unit 102, etc.". The work product analysis unit 102, etc. is realized by the processing circuit 81 shown in FIG. 21. That is, the processing circuit 81 includes a work product analysis unit 102 that analyzes a work product to generate a specification and developer information, a specification proficiency DB 105 that generates a specification proficiency DB 106 based on the specification and developer information, a forgetting determination unit 108 that determines whether a developer has forgotten a specification based on the elapsed proficiency time, a proficiency update unit 109 that updates the presence or absence of proficiency in the specification proficiency DB 106 based on the determination result, and a specification proficiency calculation unit 107 that calculates the developer's specification proficiency based on the updated specification proficiency DB 106. For the processing circuit 81, dedicated hardware may be applied, or a processor that executes a program stored in a memory may be applied. Examples of the processor include a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, and a DSP (Digital Signal Processor).

[0101] When the processing circuit 81 is 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 thereof. The functions of each part of the work product analysis unit 102, etc. may be realized by a circuit in which the processing circuit is distributed, or the functions of each part may be realized by a single processing circuit.

[0102] When the processing circuit 81 is a processor, functions such as the work product analysis unit 102 are realized in combination with software or the like. Note that the software or the like includes, for example, software, firmware, or software and firmware. The software or the like is described as a program and stored in a memory. As shown in FIG. 22, the processor 82 applied to the processing circuit 81 reads and executes the program stored in the memory 83 to realize the functions of each unit. That is, when executed by the processing circuit 81, the specification proficiency calculation device 101 includes steps of analyzing a work product to generate a specification and developer information, generating a specification proficiency DB 106 based on the specification and developer information, determining whether a developer has forgotten the specification based on the elapsed proficiency time, updating the presence or absence of proficiency in the specification proficiency DB 106 based on the determination result, and calculating the specification proficiency of the developer based on the updated specification proficiency DB 106. In other words, this program can be said to cause a computer to execute procedures and methods such as the work product analysis unit 102. Here, the memory 83 may be, for example, a non-volatile or volatile semiconductor memory such as a RAM (Random Access Memory), ROM (Read Only Memory), flash memory, EPROM (Erasable Programmable Read Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), an HDD (Hard Disk Drive), a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, a DVD (Digital Versatile Disc), their drive devices, or any storage medium to be used in the future.

[0103] The configurations in which each function such as the work product analysis unit 102 is realized by either hardware or software have been described above. However, the present invention is not limited to this, and a configuration in which a part of the work product analysis unit 102 or the like is realized by dedicated hardware and another part is realized by software or the like may be adopted. For example, regarding the work product analysis unit 102, its function can be realized by a processing circuit 81 as dedicated hardware, and for the rest, the processing circuit 81 as a processor 82 reads and executes a program stored in a memory 83 to realize its function.

[0104] As described above, the processing circuit 81 can realize each of the above-described functions by hardware, software, or a combination thereof.

[0105] It should be noted that it is possible to freely combine each embodiment and each modification example, or to appropriately modify or omit each embodiment and each modification example.

[0106] Hereinafter, aspects of the present disclosure will be summarized and described as appendices.

[0107] (Appendix 1) A work product analysis unit that analyzes the work products of software development and generates the specifications in the software development and developer information indicating the persons related to the specifications as developers; A specification familiarity database generation unit that generates a specification familiarity database indicating the presence or absence of familiarity of the developer for each of the plurality of specifications based on the specifications and the developer information; A forgetting determination unit that determines whether or not the developer has forgotten the specification based on the time elapsed since the developer became familiar with the specification; A familiarity update unit that updates the presence or absence of familiarity in the specification familiarity database based on the determination result of the forgetting determination unit; A specification familiarity degree calculation unit that calculates the specification familiarity degree of the developer based on the updated specification familiarity database A specification familiarity degree calculation device comprising:

[0108] (Appendix 2) The specification proficiency calculation device according to Appendix 1, wherein the deliverable analysis unit, when the deliverable is updated, analyzes the deliverable before and after the update to generate the updated content of the specification and the updated content of the developer information, wherein the proficiency update unit, updates the specification and the presence or absence of proficiency in the specification proficiency database based on the updated content of the specification and the updated content of the developer information. A specification proficiency calculation device.

[0109] (Appendix 3) The specification proficiency calculation device according to Appendix 1 or Appendix 2, further comprising a traceability analysis unit that analyzes the deliverable to generate traceability for associating the specifications with each other, wherein the forgetting determination unit, when the developer updates the specification, determines that the developer has not forgotten the specification updated by the developer and the specification associated by the traceability. A specification proficiency calculation device.

[0110] (Appendix 4) The specification proficiency calculation device according to any one of Appendices 1 to 3, a partial specification proficiency database generation unit, a highlighted part extraction unit and further comprising, wherein the partial specification proficiency database generation unit, generates a partial specification proficiency database by classifying the specification proficiency database for each specification group that is a group of specifications based on a user's designation, wherein the specification proficiency calculation unit, calculates the partial specification proficiency of the developer based on the partial specification proficiency database, wherein the highlighted part extraction unit, extracts, as a highlighted part, the partial specification proficiency database in which the partial specification proficiency corresponds to a representative value. A specification proficiency calculation device.

[0111] (Appendix 5) A specification proficiency calculation device according to Appendix 4, a proficiency deadline acquisition unit that acquires a proficiency deadline, which is the deadline by which the developer should be proficient in the specification within the specification group; a risk calculation unit that calculates a risk that the developer cannot be proficient in the specification within the specification group based on the proficiency deadline and the partial specification proficiency database; and further includes a specification proficiency calculation device.

[0112] (Appendix 6) A specification proficiency calculation device according to Appendix 5, wherein the developer includes a plurality of members of a development team, a reference configuration acquisition unit that acquires a reference configuration, which is an assignment of the specification that the plurality of members should be proficient in; a risk correction unit that corrects the risk based on the reference configuration; and further includes a specification proficiency calculation device.

[0113] (Appendix 7) A specification proficiency calculation device according to any one of Appendices 1 to 5, further includes a specification presentation unit that presents the specification in the specification proficiency database, wherein the forgetting determination unit, when the presented specification is confirmed by the developer, determines that the developer has not forgotten the presented specification, a specification proficiency calculation device.

[0114] (Appendix 8) A specification proficiency calculation device according to Appendix 4, a proficiency deadline acquisition unit that acquires a proficiency deadline, which is the deadline by which the developer should be proficient in the specification within the specification group; a specification presentation unit that presents the specification in the specification proficiency database; A priority setting unit that sets the priority of presenting the specification at the specification presentation unit based on at least one of the partial specification proficiency and the proficiency period. A specification proficiency calculation device further comprising the same.

[0115] (Appendix 9) Analyze the work products of software development to generate the specifications in the software development and developer information indicating the persons related to the specifications as developers. Based on the specifications and the developer information, generate a specification proficiency database indicating the presence or absence of proficiency of the developer for each of the plurality of specifications. Based on the time elapsed since the developer became proficient in the specification, determine whether the developer has forgotten the specification. Based on the determination result as to whether the developer has forgotten the specification, update the presence or absence of proficiency in the specification proficiency database. A specification proficiency calculation method for calculating the specification proficiency of the developer based on the updated specification proficiency database.

Explanation of Signs

[0116] 101 Specification proficiency calculation device, 102 Work product analysis unit, 103 Work product, 105 Specification proficiency DB generation unit, 106 Specification proficiency DB, 107 Specification proficiency calculation unit, 108 Forgetting determination unit, 109 Proficiency update unit, 301 Traceability analysis unit, 401 Partial specification proficiency DB generation unit, 402 Partial specification proficiency DB, 403 Attention part extraction unit, 501 Proficiency period acquisition unit, 502 Proficiency period, 503 Risk degree calculation unit, 601 Standard configuration acquisition unit, 602 Standard configuration, 603 Risk degree correction unit, 701 Specification presentation unit, 801 Priority setting unit.

Claims

1. An artifact analysis unit that analyzes the artifacts of software development and generates the specifications in the software development and developer information indicating the persons related to the specifications as developers; A specification proficiency database generation unit that generates a specification proficiency database indicating the presence or absence of proficiency of the developer for each of the plurality of specifications based on the specifications and the developer information; A forgetting determination unit that determines whether the developer has forgotten the specification based on the time elapsed since the developer became proficient in the specification; A proficiency update unit that updates the presence or absence of proficiency in the specification proficiency database based on the determination result of the forgetting determination unit; A specification proficiency calculation unit that calculates the specification proficiency of the developer based on the updated specification proficiency database A specification proficiency calculation device comprising:

2. The specification proficiency calculation device according to claim 1, wherein the artifact analysis unit when the artifact is updated, analyzes the artifact before and after the update, and generates the updated content of the specification and the updated content of the developer information; the proficiency update unit updates the specification and the presence or absence of proficiency in the specification proficiency database based on the updated content of the specification and the updated content of the developer information. A specification proficiency calculation device.

3. The specification proficiency calculation device according to claim 1, further comprising a traceability analysis unit that analyzes the artifact and generates traceability that associates the specifications with each other, wherein the forgetting determination unit when the developer updates the specification, determines that the developer has not forgotten the specification updated by the developer and the specification associated by the traceability. A specification proficiency calculation device.

4. The specification proficiency calculation device according to any one of claims 1 to 3, further comprising a partial specification proficiency database generation unit, a highlighted part extraction unit The partial specification proficiency database generation unit generates a partial specification proficiency database by classifying the specification proficiency database for each specification group that is a group of the specifications based on a user's designation, the specification proficiency calculation unit calculates the partial specification proficiency of the developer based on the partial specification proficiency database, the highlighted part extraction unit extracts, as a highlighted part, the partial specification proficiency database in which the partial specification proficiency corresponds to a representative value. A specification proficiency calculation device.

5. ​ The specification proficiency calculation device according to claim 4, comprising: a proficiency deadline acquisition unit that acquires a proficiency deadline, which is the deadline by which the developer should be proficient in the specification within the specification group; a risk calculation unit that calculates a risk level indicating that the developer cannot be proficient in the specification within the specification group based on the proficiency deadline and the partial specification proficiency database; The specification proficiency calculation device further comprising:

6. The specification proficiency calculation device according to claim 5, wherein: the developer includes a plurality of members of the development team; a reference configuration acquisition unit that acquires a reference configuration, which is an assignment of the specification to be mastered by the plurality of members; a risk correction unit that corrects the risk level based on the reference configuration; The specification proficiency calculation device further comprising:

7. The specification proficiency calculation device according to any one of claims 1 to 3, further comprising: a specification presentation unit that presents the specification in the specification proficiency database, wherein the forgetting determination unit determines that the developer has not forgotten the presented specification when the presented specification is confirmed by the developer. The specification proficiency calculation device.

8. The specification proficiency calculation device according to claim 4, comprising: a proficiency deadline acquisition unit that acquires a proficiency deadline, which is the deadline by which the developer should be proficient in the specification within the specification group; a specification presentation unit that presents the specification in the specification proficiency database; a priority setting unit that sets a priority for presenting the specification by the specification presentation unit based on at least one of the partial specification proficiency and the proficiency deadline; The specification proficiency calculation device further comprising:

9. Analyzing the work products of software development to generate the specifications in the software development and developer information indicating the persons related to the specifications as developers, Generating a specification proficiency database indicating whether the developer is proficient in each of the plurality of specifications based on the specifications and the developer information; Determining whether the developer has forgotten the specification based on the time elapsed since the developer became proficient in the specification; Updating the presence or absence of proficiency in the specification proficiency database based on the determination result as to whether the developer has forgotten the specification; A specification proficiency calculation method for calculating the specification proficiency of the developer based on the updated specification proficiency database.

Images