Design document checklist generation support system and design document checklist generation support method

Abstract

To support generation of a checklist, the checklist enabling appropriate checks capable of securing design quality of a system.SOLUTION: A design document checklist generation support system includes: a case characteristic list determination unit 11 that determines characteristics of past cases from design documents of the past cases and checklists of the design documents; a checklist item validity / invalidity determination unit 12 that determines validity / invalidity of each item of the past checklist for each of the design documents classified according to the case characteristics; a determination model generation unit 13 that acquires the determined case characteristics and determination results of the checklist item validity / invalid determination unit 12 and generates a determination model for each of the case characteristics; a filter determination unit 22 that determines validity / invalidity of each check item of a checklist of a design document of a new case on the basis of the generated determination model and case characteristics of the design document of the new case; and an output unit 23 that outputs the determined checklist.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a design document checklist creation support system and a design document checklist creation support method. [Background technology]

[0002] In the past, when designing various control systems, it was necessary to check whether the design documents that showed the system specifications were appropriate to prevent malfunctions. This design document checking work required, for example, an engineer who was well versed in the relevant technology to understand the contents of the design documents, which was extremely time-consuming and labor-intensive.

[0003] Patent Document 1 describes a failure sign detection system that automatically analyzes design documents and efficiently creates reviews of the design documents. The technology described in Patent Document 1 links word strings in failure information, which is information about past failures, with check items and failure numbers, and matches the features of the word strings extracted from the design documents with the word strings in the failure information, thereby predicting failures from the design documents. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2020-80024 Summary of the Invention [Problem to be solved by the invention]

[0005] The technology described in Patent Document 1 predicts the degree of correlation with past failures based on text processing of design documents, and the check items themselves are prepared. Therefore, when checking system specifications such as design documents, the technology described in Patent Document 1 does not determine whether the check items themselves are appropriate.

[0006] Engineers deal with system specifications from a wide range of fields, and they need to perform appropriate checks according to the industry and field of each system. If engineers always check design documents using the same check items, they may miss failures that could cause the system to lose proper control. In addition, checklists tend to add check items in response to problems that occur during actual operation, which increases the number of check items and makes them more complex, leading to an increasing number of cases where the rationale for adding or changing check items is unclear. As such, while checklists for checking design documents are important for verifying them, it cannot be said that appropriate checklists are always being created. If the check items when checking design documents are not appropriate, the design quality of the system cannot be guaranteed.

[0007] Furthermore, the design document checklists had variations in the way each check item was written, and some check items were specialized for specific accidents, so the descriptions were sometimes inappropriate, and in some cases the quality of the checklists themselves was also inappropriate.

[0008] An object of the present invention is to provide a design document checklist generation support system and a design document checklist generation support method that are capable of generating a checklist that allows appropriate checks to be performed to ensure the design quality of a system. [Means for solving the problem]

[0009] In order to solve the above problems, for example, the configurations described in the claims are adopted. The present application includes multiple means for solving the above-mentioned problems, and as one example, a design document checklist generation support system comprising a project characteristic list determination unit that determines the characteristics of past projects from the design documents of past projects and the checklists of those design documents; a checklist item valid / invalid determination unit that determines the validity or invalidity of each item in the checklist of the past design documents for each design document classified by the project characteristics determined by the project characteristic list determination unit; a determination model generation unit that acquires the project characteristics determined by the project characteristic list determination unit and the results of the determination by the checklist item valid / invalid determination unit and generates a determination model for each project characteristic; a filter determination unit that determines the validity or invalidity of each check item in the checklist of the design document of the new project based on the determination model generated by the determination model generation unit and the project characteristics of the design document of the new project; and an output unit that outputs the checklist determined by the filter determination unit. [Effects of the Invention]

[0010] According to the present invention, a checklist for a design document of a new project is generated by judgment using a judgment model generated based on the characteristics of past projects, so that an appropriate checklist for a design document of a new project can be automatically generated. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a configuration diagram showing an example of the overall configuration of a design document checklist generation support system according to an embodiment of the present invention; [Figure 2] 1 is a block diagram showing an example of the hardware configuration of a computer that constructs a design document checklist generation support system according to an embodiment of the present invention; [Figure 3] 1 is a flowchart illustrating an example of a model generation process performed by a design document checklist generation support system according to an embodiment of the present invention. [Figure 4]10 is a flowchart illustrating an example of a filtered checklist generation process performed by the design document checklist generation support system according to an embodiment of the present invention. [Figure 5] FIG. 1 is a diagram showing an example of a checklist handled by a design document checklist generation support system according to an embodiment of the present invention. [Figure 6] 1 is a diagram showing an example of a design document handled by a design document checklist generation support system according to an embodiment of the present invention; [Figure 7] FIG. 10 is a diagram showing an example of case characteristics determined by the design document checklist generation support system according to an embodiment of the present invention. [Figure 8] FIG. 10 is a diagram showing an example of a case characteristic determination result by the design document checklist generation support system according to an embodiment of the present invention. [Figure 9] FIG. 10 is a diagram showing an example of a valid / invalid determination result of a check item by the design document checklist generation support system according to an embodiment of the present invention. [Figure 10] FIG. 1 is a diagram showing an example of a valid / invalid determination model by a design document checklist generation support system according to an embodiment of the present invention. [Figure 11] FIG. 10 is a diagram showing an example of a screen for determining whether the case characteristics of a new case are valid or invalid by the design document checklist generation support system according to an embodiment of the present invention. [Figure 12] FIG. 10 is a diagram showing an example of a screen for determining whether a check item is valid or invalid based on the results of past cases in an embodiment of the design document checklist generation support system of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0012] A design document checklist creation support system and a design document checklist creation support method according to one embodiment of the present invention (hereinafter referred to as "this embodiment") will be described below with reference to the accompanying drawings. In the drawings, checklists are abbreviated as "CL."

[0013] [Configuration of the design document checklist generation support system] FIG. 1 shows an example of the configuration of the design document checklist generation support system of this example. The design document checklist generation support system shown in FIG. 1 stores a plurality of past cases 111, 112, . . . , and also acquires a new case 211, and supports the generation of a checklist for a design document 211a of the new case 211. The past cases 111, 112, etc. have a design document (for example, design document 111a) that shows the system specifications of a control system, etc., and an implemented checklist (for example, checklist 111b). The implemented checklist 111b has data added for each check item indicating whether it is valid or invalid for checking the design document 111a.

[0014] A new project 211 also has a design document 211a that indicates the system specifications of the new project 211, and a checklist 211b. The checklist 211b of the new project 211 is an unimplemented checklist in its initial state, and a filtered checklist 211c is generated through processing by the design document checklist generation support system of this example. By generating the filtered checklist 211c, the unimplemented checklist 211b is updated to an appropriate checklist that is suited to the design document 211a of the new project 211.

[0015] 1 includes a model generation unit 10 and a judgment processing unit 20. The model generation unit 10 and the judgment processing unit 20 are processing function units formed on a memory by executing a program implemented in a computer that constitutes the design document checklist generation support system. The model generation unit 10 acquires a case characteristic list 110 and a plurality of past cases 111, 112, .... The case characteristic list 110 indicates the characteristics of a system indicated in the design documents of the plurality of past cases 111, 112, .... Specific examples of the case characteristics will be described later.

[0016] The model generation unit 10 includes a case characteristic list determination unit 11, a checklist item valid / invalid determination unit 12, and a checklist item valid / invalid determination model generation unit 13. The case characteristic list determination unit 11 acquires the case characteristic list 110 and the past cases 111, 112, ..., performs a case characteristic list determination process to determine the case characteristics of each of the past cases 111, 112, ..., and obtains a case characteristic determination result 120. Specific examples of case characteristics will be described later. The case characteristic determination result 120 is supplied to the checklist item validity / invalidity determination unit 12. The case characteristic determination result 120 is also supplied to the checklist item validity / invalidity determination model generation unit 13.

[0017] The checklist item validity / invalidity determination unit 12 performs a check item validity / invalidity determination process based on the case characteristic determination result 120, and obtains a validity / invalidity determination result 130 of the check items of each past case 111, 112, . . . The check item validity / invalidity determination result 130 is supplied to the checklist item validity / invalidity determination model generation unit 13 .

[0018] The checklist item valid / invalid judgment model generation unit 13 acquires the case characteristic judgment result 120 and the valid / invalid judgment result 130, performs a valid / invalid judgment model generation process to generate a judgment model for each case characteristic, and generates a checklist item valid / invalid judgment model 140. The generated checklist item valid / invalid judgment model 140 is stored in the system of this example. The case characteristic judgment results 120 and the check item valid / invalid judgment results 130 in this model generation unit 10 are acquired each time a new past case is obtained, and the judgment model generated in the checklist item valid / invalid judgment model generation unit 13 is updated as needed.

[0019] The checklist item valid / invalid judgment model 140 is sent to the judgment processing unit 20, where a filter judgment of the checklist for the new case 211 is performed. The configuration of the determination processing unit 20 will be described. The determination processing unit 20 includes a case characteristic list determination unit 21, a filter determination unit 22, and an output unit 23. The case characteristic list determining unit 21 acquires the design specification 211a of the new case 211 and the case characteristic list 210, determines the case characteristics of the design specification 211a, and obtains the case characteristics 220 as the determination result.

[0020] Then, the filter determination unit 22 acquires the case characteristics 220 of the design document 211a of the new case 211, the unimplemented checklist 211b, and the valid / invalid determination model 140 of the checklist items obtained by the model generation unit 10. Note that the filter determination unit 22 may acquire case characteristics 230 input by the operator of this system in addition to the case characteristics 220 obtained by the case characteristics list determination unit 21.

[0021] The filter determination unit 22 performs a filter determination process to determine whether the unexecuted checklist 211b is valid or invalid based on the checklist item validity / invalidity determination model 140 and the case characteristics 220, and generates a filtered checklist 211c. The filter determination process in the filter determination unit 22 involves, for example, analyzing the correlation between the case characteristics of past cases included in the valid / invalid determination model 140 and the case characteristics of the new case 211, and generating a filtered checklist 211c based on the past cases with high correlations based on the correlation analysis. The filtered checklist 211c is output from the output unit 23. For example, a display device is used as the output unit 23, and the filtered checklist 211c is displayed on the screen of the display device. The output unit 23 also performs processing to output the generated filtered checklist 211c as data for the new case 211. Then, the checklist 211b held by the system is updated with the filtered checklist 211c.

[0022] [Computer hardware configuration as a design document checklist generation support system] FIG. 2 shows the hardware configuration of a computer 1 as a design document checklist generation support system. As shown in FIG. 2, the computer 1 includes a CPU (Central Processing Unit) 1a, a memory 1b, an external storage device 1c, a display device 1d, an input device 1e, an external media output device 1f, and a network communication device 1g. The CPU 1a executes a program stored in the memory 1b or the external storage device 1c.

[0023] The memory 1b is configured as, for example, a RAM (Random Access Memory), and stores computer programs and calculation result data, and also provides the CPU 1a with a work area required for each process. In this example, the CPU 1a executes a program, and thereby the model generation unit 10 and the determination processing unit 20 shown in FIG. 1 are configured in the work area in the memory 1b. The external storage device 1c is configured with a hard disk drive (HDD) or a solid state drive (SSD), and stores computer programs as well as data required for calculations and calculation result data. For example, the external storage device 1c stores data on past cases 111, 112, ..., data on a new case 211, and data on case characteristic lists 110 and 210.

[0024] The display device 1d displays data entered by the operator, calculation results, and the like. An external medium such as a memory card is connected to the external medium output device 1f, and data is exchanged via the external medium. For example, data on past cases 111, 112, etc. and data on a new case 211 shown in Fig. 1 can be acquired from the external medium attached to the external medium output device 1f, and data such as a filtered checklist can be sent to the external medium attached to the external medium output device 1f. The input device 1e is composed of input devices such as a keyboard and a mouse, and allows the operator to input various data and instructions.

[0025] The network communication device 1g communicates with external servers and terminals via a network to which the computer is connected. By performing communication using the network communication device 1g, data such as a filtered checklist obtained by the system of this example can be sent to another terminal. In addition, the network communication device 1g performs communication processing required when some calculation processing is performed on an external server.

[0026] [Model generation process] FIG. 3 is a flowchart showing the flow of processing in the model generation unit 10 to generate a valid / invalid determination model for checklist items. First, the case characteristic list determination unit 11 of the model generation unit 10 acquires the case characteristic list 110 and one piece of past case data (here, past case 111) (step S11). The case characteristic list 110 acquired here is an empty list. Then, the case characteristic list determination unit 11 acquires a case characteristic determination result 120 that determines the case characteristics of the past case 111 based on the acquired data (step S12). This case characteristic determination result 120 acquired in step S12 is saved by the design document checklist generation support system (step S13).

[0027] Then, the checklist item validity / invalidity determination unit 12 acquires the case characteristic determination result 120 and determines whether the completed checklist items of the past case 111 are valid / invalid (step S14). After determining whether the completed checklist items of the past case 111 are valid / invalid in step S14, the checklist item validity / invalidity determination unit 12 determines whether there are any unprocessed cases among the past cases 111 (step S15). If there are any unprocessed cases in step S15 (YES in step S15), the checklist item validity / invalidity determination unit 12 executes the processes of steps S11 to S15 for the unprocessed cases.

[0028] When there are no unprocessed cases in step S15 (NO in step S15), the checklist item valid / invalid judgment model generation unit 13 generates a valid / invalid judgment model 140 for checklist items of past cases based on the judgment result in the checklist item valid / invalid judgment unit 12 (step S16). The judgment model 140 generated in step S16 is used to generate a checklist for a new case.

[0029] [Filtered checklist generation process] FIG. 4 is a flowchart showing the flow of the process of generating a filtered checklist for a new case in the judgment processing unit 20. First, the case characteristic list determining unit 21 acquires the new case 211 and the case characteristic list 210 (step S21). The case characteristic list 210 acquired here is an empty list. Then, the case characteristic list determination unit 21 determines the case characteristics of the corresponding new case from the acquired new case 211, and obtains case characteristics 220 as the determination result (step S22). Note that in step S22, in addition to the case characteristics 220 as the determination result, case characteristics 230 input by the operator of this system may also be obtained.

[0030] Next, the filter determination unit 22 acquires, from the determination models 140, a determination model of a group that is highly related to the case characteristics obtained from the case characteristics 220 as the determination result (step S23). Then, the filter determination unit 22 performs a filter determination process to determine whether each checklist item of the determination model acquired in step S23 is valid or invalid (step S24). The output unit 23 outputs (displays) the filtered checklist 211c as a result of the filter determination process in step S24 (step S25).

[0031] [Checklist example] FIG. 5 shows an example of an executed checklist 111b of a past case 111 handled by the design document checklist generation support system. As shown in FIG. 5, the completed checklist 111b has columns for ID, classification, check content, document to be checked (description location), check result, reason for judgment, person in charge of check, check date and time, . . . , and valid / invalid. The ID is an identification number assigned to each check item. The category column indicates the category of the check item. For example, the categories of check items include categories according to the purpose of checking, such as "compliance with standards," "compliance with procedures," and "prevention of recurrence." The check content column shows the specific items to be checked. For example, specific check contents may include "Has all XX been resolved?", "Are all XXs satisfied?", "Has XX been requested to YY?", "Is the handling of XX clear?", "Has XX been confirmed?", and "Has XX been implemented?". Here, "XX" and "YY" represent the specific contents according to the check item.

[0032] The column for the document to be checked indicates the section of the design document that is described. For example, the document to be checked may be something like "XX Design Document, Section 1.2," which identifies the section where the document is described. The check result column indicates whether the check was "OK" or "NG." The reason for the judgment is, for example, a detailed reason for the judgment when the check result is "NG". Alternatively, a detailed reason for the judgment when the check result is "OK" may be shown. Also, inputting information into this column for the reason for the judgment may be omitted.

[0033] The checker column indicates the name of the person who performed the check for the relevant item. The check date and time column indicates the date and time when the check work for the corresponding item was carried out. The valid / invalid column indicates whether the corresponding check item is valid or invalid. The model generation unit 10 is supplied with the completed checklist 111b as shown in FIG.

[0034] [Example of design document] FIG. 6 shows an example of a design document handled by the design document checklist generation support system. For example, the design document includes items such as "reliability" and "maintainability." Specific items related to reliability, such as "maturity," "fault tolerance," and "recovery," are also included under "reliability," and the specific details of each are described in the design document. While Figure 6 shows one design document, many design documents have been prepared for past projects.

[0035] [Examples of project characteristics] FIG. 7 shows an example of a case characteristic list 110 for past cases. The case characteristic list 110 shown in FIG. 7 has columns for ID, classification, case characteristic item, and judgment. The ID column is an identification number assigned to each case characteristic. The category column indicates the category of the project characteristics. For example, categories include items such as "system characteristics," "OS," and "industry."

[0036] The project characteristic item column shows the specific content of the project characteristics. For example, project characteristic items for the "System Characteristics" category include "Is there an existing system?", "Is there a disaster recovery environment?", and "Will it be built in a cloud environment?". Project characteristic items for the "OS" category include "Is an XX server present?" and "Is a YY server present?", where XX and YY are the names of specific operating systems. Project characteristic items for the "Industry" category include "Is it a local government system?", "Is it a financial system?", and other specific industry names to which the system will be applied. The judgment column shows two values, "Yes" or "No," as the judgment result. Showing the judgment result as two values ​​(two levels) is just an example, and the judgment result may be shown in other levels. Although FIG. 7 shows the case characteristic list 110 for past cases, the case characteristics 220 for new cases also have similar classifications and case characteristic items.

[0037] [Example of case characteristic determination results in the case characteristic list determination section] FIG. 8 shows an example of a case characteristic determination result 120 of a past case obtained by the determination in the case characteristic list determination unit 11. In FIG. The case characteristic determination result 120 shown in FIG. 8 has columns for ID, classification, case characteristic item, and evaluation value of each past case. The ID column indicates the identification number assigned to each case characteristic item. The category column indicates the category of the case characteristics. The item attribute column indicates the specific content of the item attribute. The classification and item attribute columns are the same as the classification and item attribute columns of the item attribute list 110 shown in FIG.

[0038] The evaluation value column for each past project shows the evaluation value of each past project. This evaluation value is a value between 0 and 100. When there is no corresponding entry in the "Project Characteristics" column in the design document, meaning that the judgment is predicted to be "No," the evaluation value of the past project will be "0." When there is a corresponding entry in the "Project Characteristics" column in the design document, meaning that the judgment is predicted to be "Yes," the evaluation value of the past project will be "100." In reality, as shown in Figure 8, when a "No" prediction is highly likely, the evaluation value will be "10," and when a "Yes" prediction is highly likely, the evaluation value will be "90," so the evaluation value is likely to be somewhere between "0" and "100."

[0039] For example, as shown in Figure 8, the result of the determination of "Is there a current system?" is a predicted evaluation value based on the evaluation results of the design documents of each past project, such as past project A with an evaluation value of "10," past project B with an evaluation value of "30," past project C with an evaluation value of "15," and past project D with an evaluation value of "90." Note that the evaluation values ​​are shown as values ​​ranging from "0" to "100" only as an example, and the evaluation values ​​may be shown as values ​​with other levels.

[0040] [Example of checklist item valid / invalid judgment result in the checklist item valid / invalid judgment section] FIG. 9 shows an example of a checklist item valid / invalid determination result 130 obtained by the determination in the checklist item valid / invalid determining unit 12. As shown in FIG. The checklist item valid / invalid determination result 130 shown in FIG. 9 has columns for ID, classification, check content, and evaluation value of each past case. The ID column indicates the identification number assigned to each case characteristic item. The category column indicates the category of the case characteristic, which is the same as the category of the case characteristic list 110 shown in FIG. The check content column shows the specific content checked in the design document. For example, as shown in Figure 9, it shows the evaluation value based on the judgment of the check content "Has all XX been resolved?" in the category "Compliance with standards" and another check content "Are all XXs satisfied?". The check content column also shows the evaluation value based on the judgment of the check content "Has XX been requested to YY?" in the category "Compliance with procedures" and another check content "Is the handling of XX clear?".

[0041] The evaluation value in this case is a value ranging from "0" (predicted as invalid) to "100" (predicted as valid) that evaluates the validity / invalidity of each check content, similar to the evaluation value of the case characteristic determination result 120. However, this evaluation value is also shown as a value ranging from "0" to "100", which is just an example, and the evaluation value may be shown as a value with other levels.

[0042] [Example of a model for determining whether a checklist item is valid or invalid] FIG. 10 shows an example of a checklist item valid / invalid judgment model 140 generated by the checklist item valid / invalid judgment model generation unit 13, and a filter judgment performed by the filter judgment unit 22 using the checklist item valid / invalid judgment model 140. Data D1 shown in the upper part of FIG. 10 indicates part of the evaluation values ​​of the case characteristic items for new cases determined by the case characteristic list determination unit 21 of the determination processing unit 20. Data D2 shown in the middle of FIG. 10 indicates a part of the case characteristic determination result 120 of the past case obtained by the determination in the case characteristic list determination unit 11.

[0043] Here, the filter determination unit 22 performs a process of searching for a group of cases whose values ​​(vectors) are close to the evaluation values ​​of the case characteristic items of the new cases in the data D1 shown in the upper part of Figure 10 from the case characteristic determination results 120 of past cases in the data D2 shown in the middle part of Figure 10. Specifically, when the evaluation values ​​of the new project data D1 for the three project characteristic items "Is there a current system?", "Is there a disaster recovery environment?", and "Should it be built in a cloud environment?" are 10, 50, and 10, the filter determination unit 22 searches for similar evaluation values ​​from the past project data D2. For simplicity of explanation, only the evaluation values ​​of three items are shown here, but in reality, a group of past projects with similar values ​​will be found from the evaluation values ​​of all items.

[0044] In the example shown in FIG. 10, the evaluation values ​​of the three items in the past case group Q are "15," "55," and "5," which are closest to the evaluation values ​​of the new case in the data D1. At this time, the evaluation value of the validity / invalidity judgment of the checklist items of the past case group Q is used as the validity / invalidity judgment of the checklist items of the new case of the data D1. That is, as shown in the lower part of FIG. 10, the filter determination unit 22 applies the evaluation value of the past case group Q of the data D3 to the new case of the data D1, and performs a filter determination as to whether the check contents are valid or invalid.

[0045] In the example of Figure 10, for example, the check item "Have all XX been resolved?" in the category "Compliance with standards" has an evaluation value of "10" in past case group Q, and another check item "Have all XX been met?" has an evaluation value of "80" in past case group Q. At this time, the filter determination unit 22 sets the evaluation value of the check content "Are all XX resolved?" of the classification "Compliance with standards" of the new case data D1 to 10, and sets the evaluation value of the check content "Are all XX met?" of the classification "Compliance with standards" of the new case data D1 to 80.

[0046] In this way, the validity / invalidity determination results of the checklist items of the grouped past cases are adopted for the new case, and an evaluation value for each item of the checklist for the new case is obtained. The evaluation value of each item in the checklist for this new case is output from the output unit 23. The evaluation value for each item in the new case checklist generated in this way is output and displayed, for example, on the output unit 23, allowing a worker who checks this display to determine whether each item in the new case checklist is valid or invalid. For example, an item with a low evaluation value, such as "10," is likely to be invalid, while an item with a high evaluation value, such as "90," is likely to be valid. Therefore, after checking the evaluation value of each item, the worker can generate a checklist of a design document having appropriate items for a new project.

[0047] [Example of display screen] Next, an example of a display screen will be described as an example of what the output unit 23 outputs. FIG. 11 shows an example of a screen for determining whether the case characteristics of a new case are valid or invalid. FIG. 11 shows an example of displaying check items for a design document 211 a of a new project 211 . 11 displays a selection point for the target checklist and a selection point for the design document storage location. The operator selects each selection point to specify the case characteristics list 210 and the design document 211a based on the target checklist.

[0048] By specifying the case characteristic list 210 or the design document 211a, a list of case characteristics by category is displayed, as shown in Fig. 11. In the state shown in Fig. 11, a list of IDs, categories, and case characteristics is displayed, and the determination of "Yes" or "No" is left undetermined. With this project characteristic list 210 displayed, the project characteristic list determination unit 21 performs a determination on the design document 211a to obtain determined project characteristics 220. By obtaining the determined project characteristics 220, the determination column shown in FIG. 11 displays a determination result of either "Yes" or "No."

[0049] In addition to the case where the project characteristic list determination unit 21 determines the design document 211a, there is also a case where the operator determines the project characteristic 230 that has been determined. In this case, for example, the operator can select either the determination of "Yes" or "No" on the screen shown in FIG. 11 to obtain the project characteristic 230 that has been determined. Alternatively, the operator may determine and correct some of the determined case characteristics 220 output by the case characteristic list determination unit 21. Alternatively, if there are case characteristics that cannot be determined by the case characteristic list determination unit 21, the operator may input the undetermined case characteristics at his / her discretion.

[0050] 12 shows an example of a display in which the validity / invalidity of check contents is determined for the design document 211a of a new project based on the past project determination model 140. As explained in FIG. 10 and other figures, the validity / invalidity of the check contents is determined based on the evaluation values ​​of a group of past projects that have similar project characteristics to the new project, and the evaluation values ​​of the past projects are displayed following each check content.

[0051] That is, as shown in Fig. 12, the validity / invalidity of the check contents is displayed by displaying an evaluation value based on the evaluation values ​​of groups of past cases following a column of detailed check contents for each category. This evaluation value is the same as the evaluation value explained in Fig. 9 etc., and is a value ranging from evaluation value "0" (predicted as invalid) to evaluation value "100" (predicted as valid). 12, a column for links to past projects is provided, and when the operator selects a link in this "link" column, the details of the corresponding past project are displayed on the screen. For example, when the operator selects a link in the "link" column, a list of project characteristics of past projects or a list of group design documents is displayed on the screen.

[0052] The judgment column shown in Fig. 12 is a column where the operator can select "valid" or "invalid" for the corresponding check item. The operator can select "valid" or "invalid" in this judgment column based on the evaluation value. Alternatively, the filter determination unit 22 may automatically select "enabled" or "disabled" based on the evaluation value. For example, the filter determination unit 22 may automatically set a check item whose evaluation value is equal to or greater than a certain value as enabled. If the filter determination unit 22 automatically sets "enabled" or "disabled," the operator may be able to modify the setting.

[0053] Below the display of whether the check contents are valid or invalid, an execute button and a cancel button are displayed. When the operator selects the execute button, the check contents that have been set to "valid" are confirmed as the check contents in the checklist for the corresponding new case.

[0054] As explained above, according to the design document checklist generation support system of this example, candidate items indicating the check contents of the checklist for the design document of a new project are automatically selected based on the results of past projects, thereby enabling appropriate support for the generation of the design document checklist. In this case, the candidate items are selected by filtering judgment based on a comparison of the project characteristics of the new project with the project characteristics of past projects, and items indicating appropriate check contents are selected.

[0055] [Variations] The embodiment examples described so far have been described in detail to clearly explain the present invention, and are not necessarily limited to those having all of the configurations described. For example, in the above-described embodiment, the case characteristics and check items shown in each drawing are merely examples, and the present invention is not limited to the examples shown in the drawings.

[0056] Furthermore, when the filter determination unit 22 determines the similarity of the project characteristics between a new project and a past project, it may perform a similarity determination of the design documents of each project and add the results of the similarity determination of the design documents. When determining the similarity of the design documents, for example, it may perform a matching determination of keywords contained in the design documents or an implication analysis of the design documents. When performing the implication analysis of the design documents here, for example, natural language processing or a language model can be applied. By performing a similarity assessment of the design documents for each project in this way, it becomes possible to support the creation of more appropriate checklists for design documents for new projects.

[0057] The filter determination unit 22 may also compare the case characteristics of the design document of the past case included in the determination model with the case characteristics of the design document of the new case to determine the items newly added to the design document of the new case, and generate a checklist to which check items for the determined newly added items have been added. The checklist to which the check items generated by the filter determination unit 22 have been added is output (displayed) by the output unit 23. By making a judgment only on newly added items in this way, it becomes possible to appropriately support the generation of checklists for design documents that have newly added items.

[0058] In addition, the configuration diagrams shown in Figures 1 and 2 only show control lines and information lines that are considered necessary for explanation, and do not necessarily show all control lines and information lines in the product. In reality, it can be assumed that almost all components are interconnected. Furthermore, the flowcharts shown in FIGS. 3 and 4 are also examples, and as long as the processing results are the same, the order of some of the processing may be changed or multiple processes may be executed simultaneously.

[0059] Furthermore, the design document checklist generation support system described in the above-mentioned embodiment is configured by implementing a program that executes the processes shown in the flowcharts of Figures 3 and 4, and in this case, the program is prepared in the memory within the computer or in an external storage device shown in Figure 2. Alternatively, the program executed by the computer serving as the design document checklist generation support system may be stored in a recording medium such as an external memory, IC card, SD card, or optical disk, and transferred to the computer serving as the design document checklist generation support system.

[0060] 1 is configured on one computer is just an example, and the model generation unit 10 and the judgment processing unit 20 may be distributed on different computers. For example, the model generation process in the model generation unit 10 may be performed by a server connected to a network, and the checklist generation support process in the judgment processing unit 20 may be performed by a computer serving as a terminal carried by an engineer. Data on past cases may also be stored in an external database. [Explanation of symbols]

[0061] 1...computer, 1a...CPU, 1b...memory, 1c...external storage device, 1d...display device, 1e...input device, 1f...external medium output device, 1g...network communication device, 10...model generation unit, 11...case characteristic list determination unit, 12...checklist item valid / invalid determination unit, 13...valid / invalid determination model generation unit, 15...evaluation value, 20...determination processing unit, 21...case characteristic list determination unit, 22...filter determination unit, 23...output unit, 110...past case characteristic list, 111a...design document, 111b...checklist, 120...case characteristic determination result, 130...checklist item valid / invalid determination result, 140...valid / invalid determination model, 210...case characteristic list, 211...new case, 211a...design document, 211b...checklist, 211c...filtered checklist, 220...Case characteristics (judgment result), 230...Case characteristics (input case characteristics)

Claims

1. a case characteristic list determination unit that determines the characteristics of the past cases from design documents of past cases and checklists of the design documents; a checklist item validity / invalidity determination unit that determines whether each item of a checklist of a past design document is valid or invalid for each design document classified by the case characteristics determined by the case characteristic list determination unit; a judgment model generation unit that acquires the case characteristics determined by the case characteristic list determination unit and the results of the determination by the checklist item validity / invalidity determination unit, and generates a judgment model for each case characteristic; a filter determination unit that determines whether each check item in a checklist of a design document of a new project is valid or invalid based on the determination model generated by the determination model generation unit and project characteristics of the design document of the new project; an output unit that outputs the check list determined by the filter determination unit; A design document checklist generation support system.

2. a new project characteristic determination unit that determines characteristics of the design document of the new project; The filter determination unit acquires the case characteristics of the new case determined by the new case characteristic determination unit. The design document checklist generation support system according to claim 1 .

3. As the case characteristics of the past cases, an evaluation value is obtained for each item of the case characteristics, which is set in a plurality of stages between valid and invalid; Grouping projects with similar evaluation values ​​for each item of project characteristics, The filter determination unit finds a group of past cases that is close to the evaluation value of the case characteristics of the new case, and sets the validity or invalidity of the check items of the found group of past cases to the validity or invalidity of the check items of the checklist of the design document of the new case. The design document checklist generation support system according to claim 1 .

4. The validity or invalidity of check items in the checklist for new project design documents is determined by an evaluation value set in multiple stages between valid and invalid for each check item. The output unit outputs an evaluation value for each check item. The design document checklist generation support system according to claim 3.

5. The filter determination unit performs a similarity determination between the design document of the past project included in the determination model and the design document of the new project. The design document checklist generation support system according to claim 1 .

6. The filter determination unit compares the case characteristics of the design document of the past case included in the determination model with the case characteristics of the design document of the new case, determines the items newly added to the design document of the new case, generates a checklist with check items added for the determined newly added items, and the output unit outputs the checklist. The design document checklist generation support system according to claim 1 .

7. a case characteristic list determination process for determining the characteristics of the past cases from the design documents of the past cases and the checklists of the design documents; a checklist item validity / invalidity determination process for determining whether each item in the checklist of the past design document is valid or invalid for each design document classified by the case characteristics determined by the case characteristic list determination process; a judgment model generation process for acquiring the case characteristics determined by the case characteristic list determination process and the results determined by the checklist item valid / invalid determination process, and generating a judgment model for each case characteristic; a filter judgment process for judging whether each check item in the checklist of the design document of the new project is valid or invalid based on the judgment model generated by the judgment model generation process and project characteristics of the design document of the new project; and an output process for outputting the check list determined by the filter determination process. A method for supporting the generation of design document checklists.

Images