Defect information determination support system and defect information management system

Abstract

To support the assessment of the impact of defect information.SOLUTION: A defect information determination support system includes a calculation device that executes a program and a storage device that the calculation device can access. The storage device stores a defect information database that stores defect information related to software and a source code management database that stores source code for the software. In the defect information determination support system, the calculation device includes a determination support unit that compares the defect information with the source code, determines a relationship between the defect information and the source code, and distributes the result of the determination as a determination support result.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a defect information determination support system that supports the determination of defect information. [Background technology]

[0002] The following prior art is included as background art in this technical field. Patent Document 1 aims to "provide a fault identification device, a fault identification method, and a fault identification program capable of grasping faults that are estimated to have a high probability of occurring," and discloses, as a means for solving the problem, a fault identification device that includes an input unit for inputting configuration information, resource usage information, and log information of a server device, a storage unit for storing at least one fault information item including a fault content of a software fault and a plurality of occurrence conditions, a determination unit for determining whether or not each of the plurality of occurrence conditions is satisfied for the at least one fault information item based on the configuration information, resource usage information, and log information, an identification unit for identifying fault information of a software fault that is predicted to occur based on the result of the determination, and an output unit for outputting a first warning including a fault content included in the identified fault information (see Abstract of Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-128665 Summary of the Invention [Problem to be solved by the invention]

[0004] The fault identification device described in Patent Document 1 identifies fault information that will have an impact and issues a warning based on the configuration information, resource usage information, and log information of the server device that is the target of the fault information impact confirmation, but it is difficult to confirm the impact of fault information unless the software is run in advance and logs are obtained. [Means for solving the problem]

[0005] A representative example of the invention disclosed in this application is as follows: A defect information determination support system includes a calculation device that executes a program and a storage device accessible by the calculation device, the storage device storing a defect information database that stores defect information related to software and a source code management database that stores source code of the software, and the defect information determination support system is characterized in that the calculation device has a determination support unit that compares the defect information with the source code, determines the relationship between the defect information and the source code, and distributes the result of the determination as a determination support result. Effect of the Invention

[0006] According to one aspect of the present invention, it is possible to assist in checking the influence of defect information. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]

[0007] [Figure 1] 1 is a diagram showing an overview of a defect information determination support system according to a first embodiment. [Diagram 2] FIG. 11 is a diagram illustrating an example of a defect influence confirmation flow according to the first embodiment. [Diagram 3] FIG. 13 is a diagram illustrating an example of a configuration of a determination result of another project in the first embodiment. [Figure 4] FIG. 13 is a diagram illustrating an example of a task configuration of a judgment support result in the first embodiment. [Diagram 5] 11 is a flowchart of a determination support process of a defect influence confirmation flow in the first embodiment. [Figure 6] FIG. 2 is a diagram illustrating an example of a defect determination support according to the first embodiment. [Figure 7] FIG. 11 is a diagram illustrating an example of a configuration of a condition type database according to the first embodiment. [Figure 8] FIG. 2 is a diagram illustrating a hardware configuration of the defect information determination support system according to the first embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] The embodiments will be described in detail below with reference to the drawings.

[0009] FIG. 1 is a diagram illustrating an overview of a defect information determination support system according to a first embodiment.

[0010] The defect information determination support system 101 of this embodiment is connected to the process management systems 108a to 108n, and constitutes a defect information management system together with the process management systems 108a to 108n.

[0011] In this embodiment, the judgment support unit 104 of the defect information judgment support system 101 generates and outputs a judgment support result 112 to the process management unit 111 of the process management system 108a based on defect information 103 of the judgment support target acquired from the defect information database 102, source code 110 of the judgment support target acquired from the source code management unit 109 of the process management system 108a, and condition type 114 acquired from the condition type database 113, so that confirmation support of the effect of defect information on the source code of software under development or released can be made without executing software. The software handled by the defect information judgment support system 101 and the process management systems 108a to 108n is executed by, for example, an electronic control unit (vehicle ECU) or another computer. Also, the source code 110 is an example, and a setting file such as XML is also handled by the source code management unit 109 in the same way as the source code.

[0012] The defect information is information on defects in third-vendor products (hardware, software, development tools) and in-house software used in software development. The configuration of the defect information will be described later with reference to Fig. 2. Hereinafter in this specification, third-vendor products (hardware, software, development tools) and in-house software used in software development will be referred to simply as software components.

[0013] The process management systems 108a to 108n are systems that provide a function of supporting management of the development process of software for which defect information determination support is to be provided, and include definitions of information related to software components used in software development, definitions of work tasks occurring in software development, progress management, etc. In this embodiment, the process management systems 108a to 108n are provided corresponding to each of the software development projects a to n, and defect information determination support is possible using the multiple process management systems 108a to 108n.

[0014] The defect information database 102 of the defect information determination support system 101 is provided in the defect information determination support system 101 and is a database system that manages defect information. The defect information database 102 may have a plurality of pieces of defect information, but in this embodiment, the defect information database 102 has defect information 103 of a defect information determination support target as an example of defect information held by the defect information database 102. The defect information 103 of the determination support target is an example of information about a defect required to generate the determination support result 112.

[0015] The judgment support unit 104 of the defect information judgment support system 101 monitors the defect information database 102 at a predetermined timing (for example, at a predetermined time interval). When the judgment support unit 104 receives a request for judgment support for defect information from a member of the software development project, the judgment support unit 104 generates a judgment support result 112 as an operation task to be managed by a process management unit 111 based on defect information 103 of the judgment support target acquired from the defect information database 102 and source code 110 of the judgment support target acquired from a source code management unit 109. The components of the judgment support result 112 will be described later with reference to FIG. 3.

[0016] First, the judgment support unit 104 acquires one item of defect information 103 to be subjected to judgment support from among the defect information held in the defect information database 102 .

[0017] Next, the judgment support unit 104 acquires all source code held by the source code management unit 109, searches the source code for a portion that matches the condition of the defect information 103, and uses the matched condition and the value set for that condition to assign bidirectional association information between the defect information database 102 and the process management system 108a, and generates and outputs the judgment support result 112. A detailed method for generating the judgment support result will be described later with reference to Fig. 6. The generated judgment support result 112 allows members of the software development project to receive support for determining whether or not the defect information that affects software under development or that has already been released is relevant.

[0018] FIG. 8 is a diagram showing a hardware configuration of the defect information determination support system 101. As shown in FIG.

[0019] The defect information determination support system 101 is configured by a computer having a processor 801, a memory 802, an auxiliary storage device 803, and a communication interface 804. The processor 801 is an arithmetic device that executes a program stored in the memory 802. The processor 801 executes various programs to realize functions provided by the defect information determination support system 101. Note that a part of the processing performed by the processor 801 by executing the program may be executed by another arithmetic device (for example, hardware such as ASI or FPGA). The memory 802 includes a ROM 805 that is a non-volatile storage device and a RAM 806 that is a volatile storage device. The ROM 805 stores an immutable program (for example, BIOS) and the like. The RAM 806 is a high-speed and volatile storage device such as a DRAM (Dynamic Random Access Memory), and temporarily stores the program executed by the processor 801 and data used when the program is executed. The auxiliary storage device 803 is, for example, a large-capacity and non-volatile storage device such as a magnetic storage device, and stores the program executed by the processor 801 and data used by the processor 801 when the program is executed. The communication interface 804 is a network interface device that controls communications with other devices in accordance with a predetermined protocol.

[0020] The program executed by the processor 801 is provided to the defect information determination support system 101 via a removable medium (CD-ROM, flash memory, etc.) or a network, and is stored in a non-volatile auxiliary storage device 803, which is a non-transitory storage medium. For this reason, the defect information determination support system 101 should preferably have an interface for reading data from a removable medium and a network interface.

[0021] The defect information determination support system 101 is a computer system configured on one physical computer or on one or more logically or physically configured computers, and may operate on a virtual computer constructed on multiple physical computer resources. For example, the determination support unit 104 and the defect information database 102 may operate on separate physical or logical computers, or multiple computers may be combined to operate on a single physical or logical computer.

[0022] FIG. 2 is a diagram showing an example of defect information 201 and a defect effect confirmation flow 202 included in the defect information 201 in this embodiment.

[0023] The defect information 201 includes a defect impact confirmation flow 202, judgment results of other projects 209, and a defect information identifier 210 as components. The components 202 to 210 of the defect information 201 are stored in the defect information database 102 when a defect occurs. In this embodiment, as an example, the defect information 103 that is the target of judgment support will be described. Depending on the defect information 201, the judgment results 209 of other projects may not be included. Furthermore, the defect information 201 may include components other than those described above.

[0024] The defect information 201 is information about defects in third-vendor products (hardware, software, development tools) used in software development or incorporated as part of the software being developed, and in-house software.

[0025] The defect impact confirmation flow 202 is data that defines the defect impact confirmation flow, and includes as components a defect impact confirmation flow identifier 203, a condition 204, a condition type 205, a condition predicate 206, a transition destination 207 when the condition is True, and a transition destination 208 when the condition is False, and is created by an expert who is familiar with the software development domain related to the defect. There may be multiple components 203 to 208.

[0026] The defect impact confirmation flow identifier 203 is an ID or the like unique to each defect impact confirmation flow 202, and is assigned by, for example, a software development expert. The defect impact confirmation flow identifier 203 is used to specify a transition destination 207 when a condition is True or a transition destination 208 when a condition is False.

[0027] The condition 204 is written in a logical expression or natural language based on the condition under which the defect occurs, which is provided by the vendor that issued the defect information.

[0028] The type of condition 205 is an operator such as an inequality sign or a word that indicates the meaning of the condition, and is used to determine whether the condition is capable of providing defect determination support. The defect information determination support system 101 determines whether or not to provide determination support based on the type of condition 205.

[0029] The condition predicate 206 is written in a logical expression or natural language based on the condition under which the defect occurs, which is provided by the vendor that issued the defect information.

[0030] The transition destination 207 when the condition is True describes the result of the determination as to whether or not the defect affects the software being judged when the condition 204 is judged to be True, or an identifier 203 of the defect impact confirmation flow that next confirms the impact.

[0031] The transition destination 208 when the condition is False describes the result of the determination as to whether or not the defect affects the software being judged when the condition 204 is judged to be False, or the identifier 203 of the defect impact confirmation flow to be used next to confirm the impact.

[0032] The other project determination result 209 describes the result of judging the defect information 201 in the other project by integrating the judgment results for each defect impact confirmation flow. The other project determination result 209 may not be included depending on the defect information 201. The configuration of the other project determination result 209 will be described later with reference to FIG. 3.

[0033] The defect information identifier 210 is, for example, unique identification information issued by the source of the defect.

[0034] FIG. 3 is a diagram showing an example of the configuration of the judgment result 209 of other projects in this embodiment.

[0035] The judgment result 209 of the other project includes an judgment date 302, a judged software version 303, an identifier 304 of the judged defect information, an identifier 305 of the judged source code, and a judgment result 306 as components.

[0036] FIG. 4 is a diagram showing an example of a task configuration of a judgment support result in this embodiment.

[0037] A task 401 is generated each time defect information is judged and managed by the process management unit 111 of the process management system 108a. The task 401 includes an identifier 402 of the defect information for which judgment was assisted, a type 403 of the software component for which judgment was assisted, a judgment support result 404, a task deadline 409, and a person in charge of the task 410 as components, and defines a defect impact confirmation flow 202. The type 403 of the software component for which judgment was assisted holds a system to which the software component is applied (e.g., a microcomputer, AUTSAR, etc.). The judgment support result 404 includes an identifier 405 of the source code, a number of lines 406 of the source code that matches the condition, a value 407 set for the condition, and a number of occurrences 408 of the source code that matches the condition as components. The defect impact confirmation flow 202 describes what is obtained from the defect information 201, and the judgment support result 404 is created for each defect impact confirmation flow.

[0038] The determination support process of the defect effect confirmation flow will be described with reference to FIG.

[0039] S501: The judgment support unit 104 of the defect information judgment support system 101 refers to one defect information 103 to be judged from among the defect information stored in the defect information database 102. Then, the judgment support unit 104 acquires the defect effect confirmation flow 202 from the defect information 103 to be judged. At this time, if there is no defect information to be referred to, the defect information judgment support is not performed.

[0040] S502: The judgment support unit 104 of the defect information judgment support system 101 acquires the source code 110 to be judged and stored in the source code management unit 109 of the process management system 108a. At this time, if there is no defect impact confirmation flow to be referenced or no source code to be referenced, the defect information judgment support is not performed.

[0041] S503: Extract text that matches the condition 204 of the defect effect confirmation flow 202 acquired in step S501 from the source code 110 of the judgment support target acquired in step S502. An example of the extraction method will be described with reference to FIG.

[0042] S504: The judgment support unit 104 of the defect information judgment support system 101 acquires the judgment results 209 of other projects from the defect information 103 of the judgment support target referenced in step S501.

[0043] S505-S506: The defect information 103 of the judgment support target acquired in step S501, the text extracted in step S503, and the judgment results of other projects extracted in step S504 are input into the task 401, and the judgment support result 112 is generated and output, and is registered in the process management section 111 of the process management system 108a.

[0044] FIG. 6 is a diagram illustrating an example of the malfunction determination support.

[0045] A database of condition types 602 is searched for data matching the condition type of defect impact confirmation flow 601, and the availability of judgment support and tags are confirmed. If judgment support is YES, the number of lines 406 of source code matching the condition corresponding to the defect and the value 407 set for the condition are extracted from source code 603 based on the tag information.

[0046] FIG. 7 is a diagram illustrating an example of the configuration of a condition type database.

[0047] The condition type database 701 includes, as components, a condition type 702, availability of judgment support 703, and a tag 704. The condition type 702 holds, for example, the same information as the condition type 205 of the defect information 201. The condition type 702 may include information other than the condition type 205 of the defect information 201. Availability of judgment support 703 holds information on whether judgment support is to be implemented or not. The tag 704 holds, for example, a character string that serves as a marker for extracting a variable value or a value set in a configuration variable from a source code or a configuration file.

[0048] As described above, according to the embodiment of the present invention, it is possible to support confirmation of defect information for source code of software under development or released, without obtaining software execution logs. In addition to managing defect information related to software, it is possible to determine whether the defect information has an effect on the source code of the software, and it is possible to support the determination of defect information, without obtaining software execution logs.

[0049] The present invention is not limited to the above-described embodiments, and includes various modified examples and equivalent configurations within the spirit of the appended claims. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those including all of the configurations described. Furthermore, a part of the configuration of one embodiment may be replaced with the configuration of another embodiment. Furthermore, the configuration of another embodiment may be added to the configuration of one embodiment. Furthermore, a part of the configuration of each embodiment may be added, deleted, or replaced with another configuration.

[0050] In addition, each of the above-mentioned configurations, functions, processing units, processing means, etc. may be realized in hardware, for example by designing some or all of them as an integrated circuit, or may be realized in software by a processor interpreting and executing a program that realizes each function.

[0051] Information such as programs, tables, and files that realize each function can be stored in a storage device such as a memory, a hard disk, or an SSD (Solid State Drive), or in a recording medium such as an IC card, an SD card, or a DVD.

[0052] In addition, the control lines and information lines shown are those considered necessary for the explanation, and do not necessarily show all the control lines and information lines necessary for implementation. In reality, it can be considered that almost all components are connected to each other. [Explanation of symbols]

[0053] 101 Malfunction Information Judgment Support System 102 Defect information database 103 Defect information for which judgment support is required 104 Judgment Support Department 108a~108n Process control system 109 Source Code Management Department 110 Source code for which judgment support is required 111 Process Management Department 112 Judgment support results 113 Species Database 114 Type 201 Bug Information 401 Tasks 701 Condition Type Database

Claims

1. A defect information determination support system, A computing device that executes a program and a storage device that can be accessed by the computing device, The storage device stores a defect information database that stores defect information related to the software, and a source code management database that stores source code of the software; The defect information determination support system is characterized in that the calculation device has a determination support unit that compares the defect information with the source code, determines the relationship between the defect information and the source code, and distributes the result of the determination as a determination support result.

2. 2. The defect information determination support system according to claim 1, The defect information determination support system is characterized in that the judgment support unit refers to a defect impact confirmation flow stored in the defect information database, compares the source code with the conditions of the defect impact confirmation flow, and extracts defect information from the source code.

3. 3. The defect information determination support system according to claim 2, The defect information determination support system is characterized in that the determination support unit outputs an identifier and a line number of the source code as a result of the extraction.

4. 3. The defect information determination support system according to claim 2, The object extracted from the source code includes a predicate of the defect information, The defect information determination support system is characterized in that the determination support unit extracts text following an operator as a preceding descriptive word from the source code.

5. 3. The defect information determination support system according to claim 2, The defect information determination support system is characterized in that the determination support unit extracts text enclosed in predetermined tags from the source code as a condition or predicate of the defect information.

6. 2. The defect information determination support system according to claim 1, A defect information judgment support system, wherein the judgment support results include judgment results of defect information in other projects.

7. 7. The defect information determination support system according to claim 6, A defect information judgment support system characterized in that, when supporting the judgment of source code that is the same as the source code for which defect information was judged in the other project, the system outputs the result of the judgment in the other project.

8. 7. The defect information determination support system according to claim 6, A defect information determination support system characterized in that, when supporting the determination of a software component that is the same as the software component for which defect information was determined in the other project, the system outputs the result of the determination in the other project.

9. A defect information management system, A process management system for managing source code and a defect information judgment support system for extracting defect points in the source code, The defect information determination support system is configured with a computer having a calculation device that executes a program and a storage device that can be accessed by the calculation device, the storage device stores a defect information database for storing defect information related to software, and a source code management database for storing source code of the software; The defect information determination support system is characterized in that the calculation device has a determination support unit that compares the defect information contained in the defect information with the source code, determines the relationship with the source code, and distributes the result of the determination as a determination support result.

Images