KR20200114144A - Apparatus and method for automatically setting reliability test tool - Google Patents

Abstract

According to one embodiment, provided is a reliability test tool automatic setting device, which comprises: a hardware information acquisition unit which acquires information on hardware on which weapon system software is to be installed; an interface unit which receives input from among a plurality of reliability test tools to be used for a reliability test of the weapon system software; a database unit which stores test rules and setting files for each of the plurality of reliability test tools; a file generation unit which acquires test rules and setting files for the reliability test tool corresponding to the input information from the database unit, and generating an environment setting file for the reliability test tool corresponding to the received information based on information on the hardware acquired by the hardware information acquisition unit and the acquired test rules and the acquired setting files.

Description

Reliability test tool setting device and method {APPARATUS AND METHOD FOR AUTOMATICALLY SETTING RELIABILITY TEST TOOL}

The present invention relates to a reliability test tool setting apparatus and method.

The weapon system software reliability test refers to a test to identify and eliminate defects that may occur in the software code in advance. There are two types of reliability tests: static test and dynamic test. Among them, the static test refers to a test that detects potential defects without running software, and may include coding rule verification, vulnerability check, and source code metric check. Dynamic test refers to a test that checks whether a function operates normally while executing software based on the requirements and structure of the software.

Korean Patent Application Publication No. 10-2011-0072989 (published on June 29, 2011)

As the weight of software increases in weapon system development, the number of reliability test tools is increasing. Accordingly, the user performing the reliability test must be familiar with and set the test rules and setting methods for each reliability test tool, and this process may take the user's effort and time.

Accordingly, it is an object to be solved by the present invention to provide a technology that enables automatic setting of test rules and setting methods for each reliability test tool of weapon system software.

However, the problem to be solved of the present invention is not limited to the ones mentioned above, and another problem to be solved that is not mentioned can be clearly understood by those of ordinary skill in the art from the following description. will be.

The apparatus for setting a reliability test tool according to an embodiment includes a hardware information acquisition unit that obtains information on hardware on which weapon system software is to be installed, and an interface unit that receives a plurality of reliability test tools to be used for reliability testing of the weapon system software. And, a database unit for storing a test rule and a setting file for each of the plurality of reliability test tools, and a test rule and setting file for the reliability test tool corresponding to the received information from the database unit, and the hardware And a file generator for generating an environment setting file for a reliability test tool corresponding to the input information based on the information on the hardware obtained by the information acquisition unit, the obtained test rule, and the obtained configuration file.

Further, the plurality of reliability test tools may include a reliability test tool used for a static test and a reliability test tool used for a dynamic test.

In addition, the reliability test tool used in the static test may check at least one of coding rules, weaknesses, and metrics applied to the test target weapon system software without executing the test target weapon system software.

In addition, the coding rule may be based on a standard coding rule.

In addition, the vulnerability may be based on a standard vulnerability check rule.

In addition, the metric may be based on the type and limit value of the function metric.

In addition, the reliability test tool used in the dynamic test can check a predetermined item while executing the weapon system software to be tested.

In addition, the reliability test tool used for the dynamic test can set the frequency of occurrence of defects in the weapon system software, the influence of the defects, and the controllability of the defects.

In addition, the reliability test tool used for the dynamic test may receive a selection of code coverage included in the software.

In addition, the reliability test tool used for the dynamic test may set a test object in a file or function unit according to the selected code execution rate.

In the reliability test tool setting method according to an embodiment, a reliability test tool setting device performs the steps of acquiring information on hardware on which weapon system software is to be installed, and a plurality of reliability test tools to be used for the reliability test of the weapon system software. Receiving input from among the dogs, obtaining a test rule and a setting file for the received reliability test tool from a test rule and setting file for each of the plurality of reliability test tools, the obtained test rule, and the obtained And generating an environment setting file for the received reliability test tool based on a setting file and information obtained on hardware on which the weapon system software is to be mounted.

A computer program stored in a computer-readable recording medium according to an embodiment is programmed to be performed including each step included in the method for setting a reliability test tool described above.

The computer-readable recording medium according to an embodiment stores a computer program programmed to be performed including each step included in the method for setting a reliability test tool described above.

According to an embodiment, a test rule and a setting method for each reliability test tool of the weapon system software may be automatically set or generated. Therefore, when the user performing the reliability test utilizes the technology according to this embodiment, the reliability test of the weapon system software can be more easily performed.

1 is a schematic configuration diagram of an apparatus for setting a reliability test tool according to an embodiment.
FIG. 2 is a diagram illustrating types of information that can be used to obtain information about hardware.
3 is a diagram illustrating types of information that can be obtained for hardware by way of example.
4 is an exemplary flow chart for a procedure of a method for setting a reliability test tool according to an embodiment.
5 to 7 are detailed flowcharts of some of the procedures of a method for setting a reliability test tool according to an exemplary embodiment.

Advantages and features of the present invention, and a method of achieving them will become apparent with reference to the embodiments described below in detail together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in a variety of different forms, and only these embodiments make the disclosure of the present invention complete, and are common knowledge in the art It is provided to completely inform the scope of the invention to those who have, and the invention is only defined by the scope of the claims.

In describing the embodiments of the present invention, if it is determined that a detailed description of a known function or configuration may unnecessarily obscure the subject matter of the present invention, a detailed description thereof will be omitted. In addition, terms to be described later are terms defined in consideration of functions in an embodiment of the present invention, which may vary according to the intention or custom of users or operators. Therefore, the definition should be made based on the contents throughout this specification.

1 is a schematic configuration diagram of an apparatus 1000 for setting a reliability test tool according to an exemplary embodiment. Referring to FIG. 1, the apparatus 1000 for setting a reliability test tool includes a hardware information acquisition unit 100, an interface unit 200, a database unit 300, and a file generation unit 400. Here, the configuration of the apparatus 1000 for setting a reliability test tool shown in FIG. 1 is only an example. That is, according to an embodiment, the apparatus 1000 for setting a reliability test tool may not include at least one of the configurations illustrated in FIG. 1 and/or may be implemented to include a configuration not illustrated in FIG. 1. In addition, each component included in the reliability test tool setting device 1000, that is, the hardware information acquisition unit 100, the interface unit 200, the database unit 300, and the file generation unit 400 are respectively a software module or a hardware module. It may be implemented in a form or a combination of a software module and a hardware module.

First, the hardware information acquisition unit 100 is configured to acquire information on hardware on which weapon system software is to be mounted. Here, the weapon system software refers to software to be mounted on the weapon system hardware, and hereinafter, it will be referred to as'software'.

The hardware information acquisition unit 100 will be described in more detail with reference to FIGS. 2 and 3. Referring to FIG. 2 first, the hardware information acquisition unit 100 parses at least one of the makefile 111, the project configuration 112, and the HW information 113 for the hardware on which the software is to be installed, and analyzes it. )can do. Here, the information shown in FIG. 2 may be acquired from an external device or may be acquired from a user by the interface unit 200 to be described below.

In addition, referring to FIG. 3, the hardware information acquisition unit 100 uses the parsed and analyzed results as described above for the architecture 121, the compiler 122, and the development language 123 for the hardware on which the corresponding software is to be mounted. At least one of the information can be obtained. Here, the types of information shown in FIGS. 2 and 3 are merely exemplary.

The interface unit 200 is configured to receive a predetermined input from a user or an external device to perform the reliability test. Through this interface unit 200, a user or an external device may select a reliability test tool to be used for a reliability test of software.

Here, the reliability test tool that can be used for the reliability test of the software may include a reliability test tool to be used for the static test and the reliability test tool to be used for the dynamic test.

Among these, the static test may refer to checking at least one of a coding rule, a vulnerability, and a metric applied to the test target software while the test target software is not executed. Here, the coding rule is based on a standard coding rule, the vulnerability is based on a standard vulnerability check rule, and the metric may be based on the type and limit value of the function metric.

On the contrary, the dynamic test may refer to checking a predetermined item while running the software to be tested. In the reliability test tool used in such dynamic tests, the frequency of occurrence of defects in software, the influence of the defects, and the controllability of the defects can be set. In addition, the reliability test tool used in the dynamic test can receive a selection of code coverage included in the software. In addition, according to the code execution rate selected in this way, setting of the software to be tested may be performed in units of files or functions.

The database unit 300 is configured to store information. In the database unit 300, for example, test rules and configuration files for each of a plurality of reliability test tools are stored. In addition, the database unit 300 may store information on hardware acquired by the hardware information acquisition unit 100.

The file generation unit 400 generates an environment setting file for a reliability test tool. Specifically, the file generation unit 400 is based on the test rule and configuration file for the reliability test tool to be used for the reliability test of the software, and the information on the hardware acquired by the hardware information acquisition unit 100, the reliability of the software. Create an environment configuration file for a reliability test tool to be used in the test.

4 is an exemplary flow chart for a procedure of a method for setting a reliability test tool according to an embodiment. The reliability test tool setting method shown in this flow chart may be performed by the reliability test tool setting apparatus 1000 described so far. In addition, since the flow chart shown in FIG. 4 is only an example, the method of setting a reliability test tool is not limitedly interpreted by the flow chart shown in FIG. 4. For example, the method of setting the reliability test tool may be performed differently from the order shown in the flowchart of FIG. 4.

Referring to FIG. 4, a step (S100) of acquiring information on hardware on which the weapon system software is to be mounted is performed. That is, software, which is a reliability test object, is mounted on predetermined hardware, and information on such hardware is required for the reliability test of software. This step S100 may be performed by the hardware information acquisition unit 100.

Here, the type of information that can be obtained by step S100 may include at least one of information on the architecture 121, the compiler 122, and the development language 123 for hardware as shown in FIG. 3, but is limited thereto. It does not become. The information obtained by the hardware information acquisition unit 100 is transmitted to the file generation unit 400.

In addition, in the process of obtaining hardware information, the hardware information obtaining unit 100 may parse and analyze various types of information. Here, the information subject to parsing and analysis may include at least one of a makefile 111, a project configuration 112, and HW information 113 for the hardware on which the software is to be mounted, as shown in FIG. 2, but is limited thereto. It is not.

Next, a step (S200) of receiving a reliability test tool to be used for a reliability test of software is performed. This step may be performed by the interface unit 200.

Next, a step (S300) of obtaining a test rule and a setting file for the received reliability test tool from the database unit 300 is performed.

Here, the database unit 300 stores test rules and configuration files for each of the plurality of reliability test tools. That is, the database unit 300 stores test rules and configuration files for each of the reliability test tools used for the static test and the reliability test tools used for the dynamic test described above.

Here, test rules and configuration files for each reliability test tool may be different from each other.

For example, when looking at the static test, the coding rule may be verified in the static test, and the database unit 300 includes a standard coding rule (DAPA SCR-G Defense Acquisition Program Administration coding rule, MISRA Motor Industry Software Reliability Association, -C, C++ JSF++ Joint Strike Fighter Air Vehicle C++, Code Conventions for the Java Programming Language (Oracle), C# Coding conventions (Microsoft)) tailored in whole or in part can be stored as test rules.

In addition, vulnerabilities can be checked in the static test, and the database unit 300 stores tailored all or part of the standard vulnerability check rule (CWE Common Weakness Enumeration-658/659/660), one of these vulnerabilities, as a test rule. Can be.

In addition, a metric can be checked in a static test, and the database unit 300 includes a type of function metric (Cyclomatic Complexity, Call Levels, Function Parameters, Calling Functions, Called Functions, Executable Code Lines) and limit values, which are one of these metrics. What is tailored can be saved as a test rule.

Next, referring to the dynamic test, in the dynamic test, the frequency of occurrence of defects in the software, the influence of the defect, and the controllability of the defect may be set, and related matters may be stored in the database unit 300. In addition, in the dynamic test, a code coverage may be selected, and according to the selected code execution rate, setting of the test object may be performed in units of files or functions. The database unit 300 includes related items. Can be saved.

Next, based on the information on the hardware obtained in step S100 and the information on the test rule/configuration file obtained in S300, a step (S400) of generating an environment setting file for the reliability test tool is performed. This step S400 can be performed by the file generation unit 400.

5 to 7 are detailed flowcharts that can be performed in steps S200 and S300. Hereinafter, it will be described with reference to FIGS. 5 to 7, but the spirit of the present invention is not limited to those illustrated in FIGS. 5 to 7.

Referring first to FIG. 5, a process of selecting a reliability test tool to be used for the reliability test may be performed through the interface unit 200 (S201 ). If the reliability test tool for the static test is selected, a process of receiving input for a detailed test mode through the interface unit 200 may be performed (S202), and in this case, a process of selecting a coding rule (S203) may be performed. .

The coding rules selectable in step S203 may include DAPA SCR-G (S204), MISRA (S206), or coding convention (S208), and in each case, a rule set may be set in detail (S205, S207, S209). . However, if no coding rule is selected among steps S204, S206, and S208, or if a coding rule that does not belong to any of steps S204, S206 and S208 is selected, an exception processing process (S210) may be performed.

After any one of steps S205, S207, and S209 is performed, detailed setting details as a result of the execution may be stored in the database unit 300 (S211). If setting is continuously required, the steps from S201 are performed again. However, if the setting is not required continuously, the process goes to step S400 shown in FIG.

On the other hand, when the detailed test mode is not selected in step S202, the process shown in FIG. 6 is performed. Referring to FIG. 6, whether it is a vulnerability check (S230) or a metric check (S232) is checked, and in each case, a rule set may be set and stored in detail (S231, S233, S234).

However, in the case of neither vulnerability check nor metric check, exception handling process (S235) is performed.

After that, if the setting is continuously required, it is performed again from step S201. However, if the setting is not required continuously, the process goes to step S400 shown in FIG.

Meanwhile, in step S201, a reliability tool for dynamic testing rather than a reliability tool for static testing may be selected. In this case, the process shown in FIG. 7 may be performed.

Referring to FIG. 7, when a reliability test tool for dynamic testing is selected, detailed test criteria are set (S240), and code coverage is selected (S241).

According to the result selected in steps S240 and S241, there may be a statement (S242), a branch (S243), or an MC/DC (S244). In each case, details of the test object may be set and stored in a test object file or function unit (S245, S246). However, according to the result selected in steps S240 and S241, if none of the statement, branch, and MC/DC are used, the exception processing process S247 may be performed.

After that, if setting is continuously required, the process returns to before step S201 and steps from S201 are performed. However, if the setting is not required continuously, the process goes to step S400 shown in FIG.

As described above, according to an embodiment, a reliability test tool for weapon system software may be automatically set. That is, if a user or an external device simply selects a reliability test tool, a test rule and a setting file necessary for the selected reliability test tool are obtained, and an environment setting file necessary for the reliability test tool may be generated based on this. According to this, many resources required for environment setting of a reliability test tool for weapon system software can be effectively managed.

On the other hand, the method according to this embodiment can be implemented in the form of a computer program stored in a computer-readable recording medium programmed to perform each step of the method, and also includes a computer program programmed to perform each step of the method. It can be implemented in the form of a computer-readable recording medium to store.

The above description is merely illustrative of the technical idea of the present invention, and those of ordinary skill in the art to which the present invention pertains will be able to make various modifications and variations without departing from the essential quality of the present invention. Accordingly, the embodiments disclosed in the present invention are not intended to limit the technical idea of the present invention, but to explain the technical idea, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be interpreted by the following claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of the present invention.

100: reliability test tool setting device

Claims (13)

A hardware information acquisition unit that acquires information on hardware on which the weapon system software is to be installed,
An interface unit that receives information on a reliability test tool to be used for a reliability test of the weapon system software among a plurality of reliability test tools;
A database unit for storing test rules and setting files for each of the plurality of reliability test tools;
Obtain a test rule and a setting file for a reliability test tool corresponding to the inputted information from the database unit, and obtain the information on the hardware obtained by the hardware information acquisition unit, the obtained test rule and the obtained setting file Including a file generator for generating an environment setting file for the reliability test tool corresponding to the received information on the basis
Reliability test tool setting device. The method of claim 1,
The plurality of reliability test tools
Containing reliability test tools used for static tests and reliability test tools used for dynamic tests
Reliability test tool setting device. The method of claim 2,
The reliability test tool used in the static test,
Checking at least one of the coding rules, vulnerabilities, and metrics applied to the test target weapon system software without executing the test target weapon system software
Reliability test tool setting device. The method of claim 3,
The coding rules are:
Is based on standard coding rules
Reliability test tool setting device. The method of claim 3,
The above vulnerability is:
Based on standard vulnerability check rules
Reliability test tool setting device. The method of claim 3,
The metric is:
Is based on the type and limit of the function metric
Reliability test tool setting device. The method of claim 2,
The reliability test tool used in the dynamic test,
Checking certain items while running the weapon system software to be tested
Reliability test tool setting device. The method of claim 2,
The reliability test tool used in the dynamic test,
To set the frequency of occurrence of defects in the weapon system software to be tested, the influence of the defects, and the controllability of the defects
Reliability test tool setting device. The method of claim 2,
The reliability test tool used in the dynamic test,
To receive a selection of code coverage included in the weapon system software to be tested
Reliability test tool setting device. The method of claim 9,
The reliability test tool used in the dynamic test,
Depending on the selected code execution rate, setting the test target software indefinitely in units of files or functions
Reliability test tool setting device. As a reliability test tool setting method performed by the reliability test tool setting device,
Obtaining information on the hardware on which the weapon system software will be installed,
Receiving information on a reliability test tool to be used for a reliability test of the weapon system software among a plurality of reliability test tools; and
Obtaining a test rule and a setting file for a reliability test tool corresponding to the input information;
And a file generator for generating an environment setting file for a reliability test tool corresponding to the received information based on the acquired information on the hardware, the acquired test rule, and the acquired setting file.
How to set up a reliability test tool. A computer program stored on a computer-readable recording medium programmed to perform each step included in the method according to claim 11. A computer-readable recording medium storing a computer program programmed to perform, including each step included in the method according to claim 11.

Images