JPH05313943A - Detection system for logical bug for software - Google Patents

Abstract

PURPOSE:To decrease the number of cases of detecting omission of the logical bugs and reduce the man-hour needed for detection of the logical bugs. CONSTITUTION:A deciding condition table 4 stores the satisgfying conditions (satisfying for a data group 2) which are based on the specifications of the software including a processing group 1 and the data group 2. A logical decision processing part 3 reads the value of the data (data included in the group 2) to decide the satisfying conditions contained in the table 4 and decides whether the read value of data is coincident with the satisfying conditions or not. If not, the part 3 outputs the information of an error to show the deciding result.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software logical bug detection method, and more particularly, depending on software specifications such as required functions (required specifications or basic specifications) depending on a processing group (a plurality of processing) and a data group (a plurality of data). The present invention relates to a software logic bug detection method for detecting a logic bug (a contradiction of data in a data group caused by a judgment process or the like) in software that realizes a required function).

[0002]

2. Description of the Related Art Generally, software has required functions (the contents of the required functions are various) as shown in FIG.
In order to realize the above, a processing group including n (a positive integer of 2 or more) processing (processing (1) to processing (n)) and m (a positive integer of 2 or more) data (data (1) to Data (m)).

Each process in the process group can be divided into three processes, that is, a sequential process, a repetitive process, and a judgment process because of its structure.

Further, each data in the data group is often shared by some processes, and its own value is often determined in association with the values of other data.

Process (1) in FIG. 2 (Externally, input (input data) (1) is input and output (output data) (1)
Output) internally reads the value of data (1) and the value of data (2) and writes the value to data (1). Similarly, the process (2) reads the value of the data (1) and the value of the data (2) and writes the value to the data (2). Such reading and writing with respect to a plurality of data is often found in the judgment processing (the processing (1) and the processing (2) are likely to be the judgment processing). For example, in the process (2), when the value of the data (2) is changed, the process (2) makes a determination based on the value of the data (1) and the value of the data (2) and determines whether to make the change. Considered to be processing.

Due to the existence of the above-described judgment processing (processing for reading and writing a plurality of data based on a certain condition), there is a condition (establishment condition) that can be established between each data in the data group. Will exist. For example, due to the existence of the processing (1) and the processing (2), a certain satisfaction condition exists between the data (1) and the data (2).

[0007] Here, if a certain process does not operate normally due to some error (a mistake such as manufacturing omission in software manufacturing), the appropriateness of the relation between the data based on the specifications is not maintained and the logic is not maintained. A bug (data inconsistency) occurs. For example, when the process (2), which is a determination process for determining whether to change the data (2), does not operate normally due to some error, the data (2) is irrelevant regardless of the value of the data (1). The value of) is changed, and a "data contradiction", that is, a logic bug, which violates the relationship between the data (1) and the data (2) indicated by the specification, occurs.

Conventionally, in the software logic bug detection method for detecting this kind of logic bug, an artificially set data group for logic bug detection is given to the processing group at the time of software inspection. The processing group is executed by the data group, and the logic bug is detected based on the human judgment work on the value of the data group during or after the execution.

[0009]

In the above-described conventional software logic bug detection method, a data group for logic bug detection that is artificially set for a processing group is given, and based on human judgment work. Since the logic bug has been detected, there is a problem that the number of steps for detecting the logic bug becomes large.

Further, since there is a high possibility that an error will occur in human judgment work, etc., a logical bug will be missed at the time of inspection of the software, and a logical bug will occur at the time of actual operation of the software. There is a problem in that the possibility that the software will operate inconsistent with the specifications increases.

In view of the above points, an object of the present invention is to provide a software logic bug detection method capable of reducing the number of steps for detecting logic bugs and reducing logic bug detection omissions. Especially.

[0012]

A logical bug detection method for software according to the present invention is a logical bug detection method for software that detects a logical bug in software that implements a required function by a processing group and a data group. A judgment condition table that stores a satisfaction condition for a data group based on the specification, and a value of data for making a judgment regarding the satisfaction condition in this judgment condition table are read, and whether or not the value of the data matches the satisfaction condition. And a logical determination processing unit that outputs an error notification indicating the determination result when it is determined that “the condition is not met”.

[0013]

In the software logical bug detection method of the present invention, the judgment condition table stores the satisfaction conditions for the data group based on the software specifications, and the logic judgment processing unit makes a judgment regarding the satisfaction conditions in the judgment condition table. The value of the data is read, it is determined whether or not the value of the data meets the satisfaction condition, and when it is determined that the condition is not met, an error notification indicating the determination result is output.

[0014]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram (illustrated in the form of a data flow diagram) showing the configuration of an embodiment of a software logic bug detection system of the present invention. In the software logical bug detection method of this embodiment, a processing group 1 (processing (1), processing (2), ..., Processing (n) for realizing a required function of software (function required according to software specifications). )), The data group 2 (data (1), data (2), ..., Data (m)) used to realize the required function of the software, the logical determination processing unit 3, and the determination condition table 4. It is configured to include and.

The judgment condition table 4 stores some conditions for the data group 2 (conditions based on software specifications and conditions for judging the appropriateness of the relation between the data in the data group 2). There is.

Here, the contents of the satisfaction condition for the data group 2 in the judgment condition table 4 are as follows. Here, for simplification, the value that each data can take is assumed to be either "0" or "1". Satisfaction condition: "The values of data (1), data (2), ..., Data (m) do not all become" 1 "at the same time." Satisfaction condition: "When the value of data (1) is" 0 " , The value of the data (2) is always "1." Satisfaction condition; "When the value of the data (2) is" 0 ", the value of the data (m) is always" 0 "."

Next, the operation of the logic bug detecting method of the software of the present embodiment thus constructed will be described.

The processes (1) to (n) in the process group 1 are
Each has an input (input data) (1) to input (n) and an output (output data) (1) to output (n), and reads and writes values of some data in the data group 2. (Processing (1) to processing (n) in processing group 1 requires one or more data in data (1) to data (m) in data group 2).

At the time when the software having the processing group 1 and the data group 2 is executed and the software is inspected, the logic judgment processing section 3 starts the trigger (see FIG. 1).
Generally, it is input when the software starts) and is started by the following processing. The logic determination processing unit 3 is often activated at the time of software inspection, but may be activated at the time of actual operation of the software (to detect a logic bug even after the inspection). "Starting at the time of operation" is useful).

In order to make a judgment regarding one satisfaction condition in the judgment condition table 4, the value of the data required for the judgment is read. For example, when the above-mentioned “establishment condition” is determined, all values of data (1) to data (m) are read. In addition, when the above-mentioned “establishment condition” is determined, the value of data (1) and the value of data (2) are read.

After that, it is determined whether or not the values of those data match the satisfaction condition (whether each data is consistent with the specification indicated by the satisfaction condition).

If it is determined that the condition is not met in (1), it means that a logical bug has occurred, so an error notification indicating the determination result is output. For example, when it is determined that "the value of data (2) is" 0 "when the value of data (1) is" 0 "" with respect to the above "establishment condition", an error indicating that Output a notification.

Here, various setting methods can be considered as to how to set the specific contents of the error notification. As an example, an error notification indicating the information indicating the detection of the logic bug and the identification information of the satisfaction condition related to the detection of the logic bug can be considered.

If it is determined that the condition is satisfied, the other conditions are determined (in this way, the determinations for each condition in the determination condition table 4 are repeated).

As described above, the logic judgment processing unit 3 repeats judgments regarding some of the conditions in the judgment condition table 4, and the start trigger is used as a trigger to constantly monitor the detection of logic bugs. When is detected, an error notification indicating that is output.

As a premise of the execution of the present embodiment, and by extension, the software logical bug detection method of the present invention, the reading and writing of each data in the data group 2 by each processing in the processing group 1 is performed correctly. I shall. That is, it is assumed that the defect of the storage device itself in which the data group 2 is stored is detected and removed by the parity check or the like.

The logic judgment processing unit 3 can be realized by software or hardware, and it is assumed that the logic judgment processing unit 3 itself (the logic judgment processing unit 3 itself) has no bug.

Further, it is assumed that the contents of the judgment condition table 4 (each satisfaction condition) are clearly defined in advance based on the software specifications (required specifications or basic specifications).

[0030]

As described above, the present invention is provided with the determination condition table for storing the satisfaction conditions based on the software specifications, and determines whether or not the data group matches the satisfaction conditions in the determination condition table. By being judged by the judgment processing unit, it is possible to automatically detect logic bugs (contradictions of data in the data group) due to judgment processing, etc., and it is possible to reduce the number of steps for detecting logic bugs. Therefore, there is an effect that the omission of detection of logic bugs can be reduced.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of an exemplary embodiment of the present invention.

FIG. 2 is a block diagram for explaining a conventional logic bug detection method of software.

[Explanation of symbols]

 1 processing group 2 data group 3 logic judgment processing unit 4 judgment condition table

Claims (1)

[Claims] 1. A determination condition table that stores a satisfaction condition for a data group based on software specifications in a software logical bug detection method that detects a logical bug in software that implements a required function by a processing group and a data group. , The value of the data for making the determination regarding the satisfaction condition in this determination condition table is read, and it is determined whether or not the value of the data matches the satisfaction condition, and it is determined that "the condition is not met". And a logic judgment processing unit that outputs an error notification indicating the judgment result in that case.