Vehicle controller test device and method therefor

Abstract

A vehicle controller test device and a method thereof are disclosed. A vehicle controller test method according to an embodiment of the present invention comprises: a) a step of classifying a test case (TC) in which a failure occurred as a result of testing a function while one or more controllers are connected to a vehicle; b) a step of generating binary code according to control flow information by performing a system-level simulation on the test case (TC); c) a step of generating a Hierarchical Control Flow Model (HCFM) of binary code-based controller software (SW) for the test case (TC) using a writing tool; and d) a step of detecting the location of the source code where the failure occurred and outputting an analysis result report through a test code analysis scenario that compares the HCFM based on a reference HCFM corresponding to the entire code.

Description

Technology Field

[0001] The present invention relates to a vehicle controller test device and a method thereof, and more specifically, to a vehicle controller test device and a method thereof for analyzing the cause of an error. Background Technology

[0002] Generally, vehicles are equipped with numerous controllers that interoperate to control various functions, and during the development of controllers and their software, various test analyses and modifications are performed to ensure stable functionality.

[0003] Since man-hours and work efficiency are determined by how stably and quickly the functionality is implemented, these test analysis and modification tasks act as key variables in driving an effective development innovation process.

[0004] For example, conventionally, when a failure occurs while performing functional tests with numerous controllers connected within a vehicle, the task of analyzing and correcting it frequently occurs. However, conventional test analysis and correction work consumes an excessive amount of time and manpower, leading to a decrease in man-hours, and this is because it requires going through the following three processes.

[0005] First, at the vehicle unit level, since there are numerous controllers installed within the vehicle that are interconnected regarding a single function, it is necessary to identify the controller causing the failure.

[0006] Second, after identifying the controller causing the problem, you must find functional issues by directly simulating at the controller unit level.

[0007] Third, since the software structure of the controller is divided into BSW (Basic Software) and ASW (Application Software), it is necessary to analyze where the problem is caused.

[0008] In particular, although various methodologies exist for analyzing test cases that cause failure in controller software, the following problems are occurring, so a method to efficiently resolve them is required.

[0009] For example, in the case of analysis methods performed by software developers, the source code must be analyzed to find the location where a failure occurs by changing arbitrary values ​​(e.g., temporary code) in line-by-line debugging mode, and the actual code where errors are found must be corrected immediately. However, this analysis takes a significant amount of time and necessarily requires a software developer, while also relying heavily on their experience and know-how; furthermore, there are often cases where other problems arise when adopting the method of modifying temporary code.

[0010] Furthermore, while the analysis method performed by test engineers identifies the location of failures based on test scenarios, there is a problem in accurately analyzing the cause in the relationship between BSW and ASW when the code is not disclosed. Additionally, similar to the above, there is a problem in ensuring the reliability of the analysis because it requires the test engineer's experience and professional theoretical knowledge regarding specifications.

[0011] The matters described in this background technology section are written to enhance understanding of the background of the invention and may include matters that are not prior art already known to those skilled in the art to which this technology belongs. The problem to be solved

[0012] The embodiment of the present invention aims to provide a vehicle controller test device and a method thereof that automatically generates a Hierarchical Control Flow Model (HCFM) of controller software according to test case control flow information using a binary code-based tool for analyzing the causes of errors by function applied to a vehicle.

[0013] Another objective of the present invention is to provide a vehicle controller test device and a method thereof that implement a test code analysis scenario in which a failure occurs according to the automatic generation of the binary code-based controller SW HCFM. means of solving the problem

[0014] According to one aspect of the present invention, a vehicle controller test method of a vehicle controller test device comprises: a) a step of classifying a test case (TC) in which a failure occurred as a result of testing a function while one or more controllers are connected to a vehicle; b) a step of generating binary code according to control flow information by performing a system-level simulation on the test case (TC); c) a step of generating a Hierarchical Control Flow Model (HCFM) of binary code-based controller software (Software, SW) for the test case (TC) using a writing tool; and d) a step of detecting the location of the source code where the failure occurred through a test code analysis scenario that compares the HCFM based on a reference HCFM corresponding to the entire code, and outputting an analysis result report.

[0015] In addition, step c) above may include the step of assigning the test case (TC) in which the failure occurred to the controller SW and dynamically creating HCFM during the execution process of the controller SW.

[0016] In addition, step c) above may include a step of layering the structure of the controller SW using a module concept to represent the execution path during the creation process of the HCFM.

[0017] The step of hierarchizing the structure of the above SW may include: b-1) defining a sequential set of instructions from the instruction following one branch statement to the instruction immediately preceding the next branch statement as a basic block; b-2) expressing the basic block at the same level as a single command line, wherein the complex flow occurring consecutively by a single function call is expressed in the same way as a single command line, and the first basic block is written in a form that contains the HCFM of multiple sub-modules; and b-3) expressing the second basic block selected by the next branch statement by connecting it with a junction block, and expressing a branch condition that triggers the corresponding branch as input data at the edge connecting the two.

[0018] Additionally, the above function call calls the submodule included within the first basic block, and may include a step of detecting a new submodule at the time of the function call and representing it in a hierarchical structure.

[0019] Additionally, step d) may include: a step of comparing with the reference HCFM when the creation of the HCFM corresponding to the test case (TC) is completed; and a step of detecting the source code location of the controller SW where the failure occurred.

[0020] Additionally, the source code location may include a step of detecting the last path location file where the HCFM creation was stopped due to an error in the control flow information, or detecting the path location file where a difference occurred from the reference HCFM.

[0021] Meanwhile, according to one aspect of the present invention, a vehicle controller test device comprises: a communication unit that collects state data of a controller operating according to function execution by connecting a vehicle and diagnostic communication; a simulation unit that constructs virtual controller software (SW) in the same environment as the vehicle and simulates various functions based thereon; a database (DB) that stores various programs and data for vehicle controller testing; and a control unit that classifies a test case (TC) in which a failure occurred as a result of executing a function test through the communication unit or the simulation unit, performs a system-level simulation on the test case (TC) to generate binary code according to control flow information, generates a Hierarchical Control Flow Model (HCFM) of the binary code-based controller software (SW) for the test case (TC), and then detects the location of the source code in which the failure occurred through a test code analysis scenario that compares the HCFM based on a reference HCFM corresponding to the entire code, and outputs an analysis result report.

[0022] In addition, the control unit may include an HCFM creation tool that automates the creation of the HCFM using the binary code having the minimum information to be expressed when creating the HCFM of the controller SW.

[0023] In addition, the control unit defines a sequential set of instructions from the instruction following one branch statement to the instruction immediately preceding the next branch statement as a basic block when creating the HCFM, and expresses the complex flow that occurs consecutively by one function call at the same level as a single command line, and creates the first basic block in a form that contains the HCFM of multiple sub-modules, and the second basic block selected by the next branch statement is expressed by connecting it with a junction block, and can express a branch condition that triggers the corresponding branch as input data at the edge connecting the two.

[0024] Meanwhile, according to another aspect of the present invention, a vehicle controller test method of a vehicle controller test device may include: a) a step of classifying a test case (TC) in which a failure occurs as a result of testing a function while one or more controllers are connected to a vehicle; b) a step of generating binary code according to control flow information by performing a system-level simulation on the test case (TC); c) a step of creating a Hierarchical Control Flow Model (HCFM) of binary code-based controller software (SW) for the test case (TC) using a creation tool; and d) a step of detecting the last path location where the creation of the HCFM was interrupted due to the failure and outputting it as an analysis result report. Effects of the invention

[0025] According to an embodiment of the present invention, an HCFM is automatically generated based on the test case control flow information of the controller software applied to the vehicle, thereby facilitating the tracking of the source code location that is the cause of the error.

[0026] In addition, by automating the creation of HCFM using a binary code containing the minimum information required for creating HCFM of controller software, the man-hours required for error cause analysis of controller software can be reduced.

[0027] In addition, by reducing the man-hours required for analyzing the causes of errors in the controller software, sufficient time can be secured for modifying the source code necessary for software development, thereby improving the completeness of the controller. Brief explanation of the drawing

[0028] Figure 1 schematically shows the configuration of a vehicle controller test device according to an embodiment of the present invention. Figure 2 shows an example of binary code generation for HCFM writing according to an embodiment of the present invention. Figure 3 shows an example of creating a hierarchical control flow model (HCFM) according to an embodiment of the present invention. FIG. 4 is a flowchart schematically illustrating a vehicle controller test method according to an embodiment of the present invention. FIG. 5 is a flowchart schematically illustrating a vehicle controller test method according to an additional embodiment of the present invention. Specific details for implementing the invention

[0029] Below, with reference to the attached drawings, embodiments of the present invention are described in detail so that those skilled in the art can easily implement the invention.

[0030] The terms used herein are for the purpose of describing specific embodiments only and are not intended to limit the invention. As used herein, singular forms are intended to include plural forms as well, unless explicitly otherwise indicated in the context. It will also be understood that the terms “include” and / or “include,” as used herein, specify the presence of the mentioned features, integers, steps, operations, components and / or components, but do not exclude the presence or addition of one or more of other features, integers, steps, operations, components, components and / or groups thereof. As used herein, the term “and / or” includes any one or all combinations of the associated items listed.

[0031] Terms such as "vehicle" or "of a vehicle" as used herein, or other similar terms, are understood to include not only railway vehicles but also passenger cars, buses, trucks, and various commercial vehicles, including sports utility vehicles (SUVs).

[0032] Throughout the specification, terms such as first, second, A, B, (a), (b), etc., may be used to describe various components, but said components shall not be limited by said terms. These terms are intended only to distinguish a component from other components, and the nature, order, or sequence of said component is not limited by said terms.

[0033] Throughout the specification, when it is stated that one component is 'connected' or 'joined' to another component, it should be understood that it may be directly connected or joined to that other component, or that there may be other components in between. On the other hand, when it is stated that one component is 'directly connected' or 'directly joined' to another component, it should be understood that there are no other components in between.

[0034] Additionally, it is understood that one or more of the methods or aspects thereof described below may be executed by at least one controller. The term "controller" may refer to a hardware device comprising memory and a processor. The memory is configured to store program instructions, and the processor is specifically programmed to execute program instructions to perform one or more processes described in more detail below. The controller may control the operation of units, modules, components, devices, or similar things as described herein. Furthermore, it is understood that the methods below may be executed by a device comprising a controller together with one or more other components, as recognized by those skilled in the art.

[0035] Additionally, the controller of the present disclosure may be implemented as a non-transient computer-readable recording medium comprising executable program instructions executed by a processor. Examples of computer-readable recording media include, but are not limited to, ROM, RAM, Compact Disc (CD) ROM, magnetic tapes, floppy disks, flash drives, smart cards, and optical data storage devices. The computer-readable recording medium may also be distributed across a computer network so that program instructions can be stored and executed in a distributed manner, such as, for example, a telematics server or a Controller Area Network (CAN).

[0036] Now, a vehicle controller test device and a method according to an embodiment of the present invention will be described in detail with reference to the drawings.

[0037] Figure 1 schematically shows the configuration of a vehicle controller test device according to an embodiment of the present invention.

[0038] Referring to FIG. 1, a vehicle controller test device (20) is shown that is connected to the OBD-II (10) of a vehicle according to an embodiment of the present invention and tests and analyzes various controller (Electronic Control Unit, ECU) software (Software, SW) by function.

[0039] The vehicle connects at least one controller (ECU) through an internal network and a gateway (GW) and establishes diagnostic communication with an external vehicle controller test device (20) through OBD-II (10).

[0040] The vehicle controller test device (20) includes a communication unit (21), a simulation unit (22), a database (DB) (23), and a control unit (24), and can be configured in a computing system such as a server or a portable information and communication terminal.

[0041] The communication unit (21) connects to diagnostic communication via OBD-II (10) and collects status data of the controller that operates according to the execution of the vehicle's functions. To this end, the communication unit (21) can transmit virtual control commands for the execution of specific functions.

[0042] The simulation unit (22) constructs a virtual controller SW in an environment identical to that of a vehicle and simulates various functions based on it. For example, the simulation unit (22) may include various controllers and SW to simulate the operating status of the engine, transmission, air conditioner, exhaust system, and electrical load applied according to the vehicle type and specifications.

[0043] DB (23) stores various programs and data for the operation of the vehicle controller test device (20) according to an embodiment of the present invention, and stores data generated according to the operation.

[0044] The control unit (24) is a central processing unit that controls the overall operation of the vehicle controller test device (20) for improving the analysis of the cause of errors (or failures) of the controller applied to the vehicle. Therefore, the control unit (24) can be described as the actual entity that controls the vehicle controller test method according to the execution of various programs stored in the respective units and DB (23).

[0045] The control unit (24) executes a functional test of the actual vehicle through the communication unit (21) or executes a functional test through the simulation unit (22), monitors the control flow during the operation of the controller SW, and classifies test cases (TC) in which an error occurs according to the result.

[0046] The control unit (24) automatically generates a Hierarchical Control Flow Model (HCFM) of the controller SW according to the test case (TC) control flow information to detect the source code location of the cause of the error when an error is detected in the controller SW applied to the vehicle.

[0047] The control unit (24) includes an HCFM creation tool (25) that automates the creation of an HCFM using binary code containing minimal information to be expressed when creating an HCFM of the controller SW.

[0048] The control unit (24) detects the source code that failed by comparing the HCFM with the reference HCFM based on the full code built in the normal state in advance, and outputs an analysis result report.

[0049] Through this, by simplifying the test case (TC) analysis procedure for analyzing the causes of errors in the controller software, man-hours can be reduced and the completeness of the controller can be improved by addressing error issues.

[0050] Meanwhile, Figure 2 shows an example of binary code generation for HCFM creation according to an embodiment of the present invention.

[0051] Referring to FIG. 2, the control unit (24) performs a function test with numerous controllers connected within the vehicle.

[0052] The control unit (24) identifies the path where a test case (TC) is executed to analyze the cause of an error in the controller SW, and generates binary code to obtain only the minimum necessary information. Then, HCFM is written based on the binary code.

[0053] At this time, the information required to obtain control flow information of the controller SW can be defined as a file identification code, line number, sentence type code, and an index for each code. This information can be inserted into an HCFM writing tool (25) to compile and execute.

[0054] Here, the above sentence type code can be defined as follows.

[0055] - BLB (basic Block Begin) refers to a block of statements that does not contain any conditional branches.

[0056] - UFN (User Function): Refers to a user-defined function.

[0057] - LFN(Library Function) refers to a general library function.

[0058] - BLF (Blocking Function) refers to a synchronous function.

[0059] - SCL (System Call) refers to the system call trigger function.

[0060] - JCN(JunCtioN) inserts branching conditions such as if, while, etc.

[0061] Unlike other codes, QUIT does not specify a separate index.

[0062] Figure 3 shows an example of creating a hierarchical control flow model (HCFM) according to an embodiment of the present invention.

[0063] Referring to FIG. 3, the control unit (24) assigns an error-prone test case to the target controller SW and dynamically generates an HCFM through an HCFM creation tool (25) during the execution of the SW. In this process, a module concept is used to represent the execution path, and the structure of the SW is layered.

[0064] At this time, the method of creating HCFM by layering the structure of the above SW is as follows.

[0065] The control unit (24) defines a sequential set of instructions (e.g., Fun1, Fun2, …) from the instruction following one branch statement (e.g., Main) to the instruction immediately before the next branch statement as a basic block. That is, the basic block refers to a set of instructions that does not contain any branch statements.

[0066] The above basic block represents a complex flow that occurs sequentially by a single function call at the same level as a single command line, and can be written in such a way that a single first basic block (B1) contains the HCFM of multiple sub-modules. Here, the function call is to call the sub-module included within the first basic block (B1), and when the function call is made, a new sub-module can be detected and represented in a hierarchical structure.

[0067] In addition, the second basic block (B2) selected by the above-mentioned branch statement is expressed by connecting it to a junction block, and a branch condition that triggers the corresponding branch can be expressed as input data at the edge connecting the two. The branch condition refers to the relationship between the second basic blocks (B2) connected to the junction block.

[0068] In the method for creating the HCFM of the present invention, the term 'express' means to create it so as to track the control flow information of the controller SW and display it visually.

[0069] Therefore, by comparing with the above-mentioned standard HCFM, source code that failed can be detected, and the scope of modification by the software developer on the HCFM can be determined and output as an analysis result report.

[0070] In addition, conventional controller SW error analysis technology verifies by following down from the corresponding function to the sub-functions in a tree structure, making it impossible to detect errors linked by a single function call. However, the HCFM written based on binary code according to an embodiment of the present invention has the effect of being able to track all possible steps by representing the sub-modules of a complex flow that can occur sequentially by a single function call of a basic block at the same level as a single command line.

[0071] This control unit (24) may be implemented as one or more processors that operate according to a set program, and the set program may be programmed to perform each step of the vehicle controller test method for error cause analysis according to an embodiment of the present invention.

[0072] This vehicle controller test method will be explained in more detail with reference to the drawing below.

[0073] FIG. 4 is a flowchart schematically illustrating a vehicle controller test method according to an embodiment of the present invention.

[0074] Referring to FIG. 4, the vehicle controller test method according to an embodiment of the present invention is assumed to generate binary code by inputting random code or full code into normal SW, and to proceed after the reference HCFM has been completed in advance based on this.

[0075] The control unit (24) classifies test cases (TC) in which a failure occurred as a result of testing the function while one or more controllers applied to the vehicle are connected, and performs a system-level simulation on the test cases (TC) to generate binary code containing control flow information (S110).

[0076] The control unit (24) creates a binary code-based hierarchical control flow model (HCFM) for the test case (TC) using an HCFM creation tool (25) (S120).

[0077] When the control unit (24) completes the creation of the HCFM corresponding to the test case (TC) (S130), it detects the source code of the SW that failed through a test code analysis scenario that compares the HCFM based on the reference HCFM corresponding to the entire code (S140). At this time, the control unit (24) can detect the last path location file where the creation of the HCFM was stopped due to an error in the control flow information compared with the reference HCFM, or detect the path location file where a difference occurred.

[0078] The control unit (24) generates an analysis result report showing the source code location of the SW where the failure occurred and outputs it to the software developer or engineer (S150).

[0079] In this way, according to an embodiment of the present invention, an HCFM is automatically generated based on the test case control flow information of the controller software applied to the vehicle, thereby making it easy to track the source code location that is the cause of the error.

[0080] This resolves the problem where, in the past, when a test case failed during testing, it was difficult to identify the exact location of the software's cause because engineers could only proceed with simulation without being able to view the source code.

[0081] In addition, conventionally, there was a problem where man-hours increased exponentially because the location of the problematic software had to be found through multiple steps to locate the cause of the failure.

[0082] Accordingly, according to an embodiment of the present invention, by automating the creation of an HCFM through a binary code containing the minimum information required for creating an HCFM of controller software, the man-hours required for analyzing the cause of errors in controller software can be reduced.

[0083] Furthermore, by reducing the man-hours required for analyzing the causes of errors in the controller software, sufficient time can be secured for modifying the source code necessary for software development, thereby allowing for the expectation of improved completeness of the controller.

[0084] Although embodiments of the present invention have been described above, the present invention is not limited to the above-described embodiments and various other modifications are possible.

[0085] For example, in the embodiment of the present invention illustrated in FIG. 4, it was explained that the source code location of the SW where a failure occurred is detected by comparing the HCFM based on a reference HCFM corresponding to a pre-generated entire code. However, the embodiment of the present invention is not limited thereto, and the source code location of the SW where a failure occurred can be detected even in a situation where there is no reference HCFM.

[0086] For example, FIG. 5 is a flowchart schematically illustrating a vehicle controller test method according to an additional embodiment of the present invention.

[0087] Hereinafter, the additional embodiment of the present invention described through FIG. 5 is identical to the previous embodiment in that the vehicle controller test device (20) is the same and only the vehicle controller test method differs in some ways, so redundant descriptions are omitted and the differences are explained mainly.

[0088] Referring to FIG. 5, a control unit (24) according to another embodiment of the present invention generates binary code according to the control flow by inputting random code into the SW when developing the controller SW even in a situation where there is no reference HCFM (S210), and writes HCFM based on the binary code (S220).

[0089] At this time, if the creation of the HCFM is interrupted due to an error in the control flow information (S230), the control unit (24) detects the source code of the last path location where the creation of the HCFM was interrupted (S240).

[0090] And, the control unit (24) can generate an analysis result report showing the source code location of the SW where the failure occurred and output it to the software developer or engineer (S250).

[0091] As such, according to an additional embodiment of the present invention, even without the above-mentioned standard HCFM, there is an advantage in being able to analyze the location of failure where creation is stopped at a specific path due to an error in the SW control flow by monitoring the creation flow of the HCFM created during the software development process.

[0092] The embodiments of the present invention are not limited to being implemented only through the apparatus and / or methods described above, but may also be implemented through a program for realizing a function corresponding to the configuration of the embodiments of the present invention, a recording medium on which the program is recorded, etc., and such implementation can be easily achieved by a person skilled in the art to which the present invention pertains from the description of the embodiments described above.

[0093] Although embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements by those skilled in the art using the basic concept of the present invention as defined in the following claims also fall within the scope of the present invention. Explanation of the symbols

[0094] 10: OBD-II 20: Vehicle controller test device 21: Communications Department 22: Simulation Department 23: Database (DB) 24: Control unit 25: HCFM Writing Tool

Claims

Claim 1 A vehicle controller test method for a vehicle controller test device comprises: a) a step of classifying a test case (TC) in which a failure occurred as a result of testing a function while one or more controllers are connected to a vehicle; b) a step of generating binary code according to control flow information by performing a system-level simulation on the test case (TC); c) a step of generating a Hierarchical Control Flow Model (HCFM) of a binary code-based controller software (Software, SW) for the test case (TC) using a writing tool; and d) a step of detecting the location of the source code in which the failure occurred and outputting an analysis result report through a test code analysis scenario that compares the HCFM based on a reference HCFM corresponding to the entire code; wherein step c) includes a step of assigning the test case (TC) in which the failure occurred to the controller SW and dynamically generating the HCFM during the execution process of the controller SW. Claim 2 delete Claim 3 A vehicle controller test method according to claim 1, wherein step c) includes the step of layering the structure of the controller SW using a module concept for representing the execution path during the creation of the HCFM. Claim 4 In claim 3, the step of hierarchizing the structure of the SW comprises: b-1) defining a sequential set of instructions from the instruction following one branch statement to the instruction immediately preceding the next branch statement as a Basic block; b-2) expressing the Basic block at the same level as a single command line, wherein a complex flow occurring consecutively by a single function call is expressed in a form in which a first Basic block contains the HCFM of multiple sub-modules; and b-3) expressing the second Basic block selected by the next branch statement by connecting it with a Junction block, wherein a branch condition that triggers the corresponding branch is expressed as input data at the edge connecting the two; a vehicle controller test method. Claim 5 A vehicle controller test method according to claim 4, wherein the function call is to call the submodule included within the first basic block, and includes the step of detecting a new submodule upon the function call and representing it in a hierarchical structure. Claim 6 A vehicle controller test method according to claim 1, wherein step d) comprises: a step of comparing with a reference HCFM when the creation of the HCFM corresponding to the test case (TC) is completed; and a step of detecting the source code location of the controller SW where the failure occurred. Claim 7 A vehicle controller test method according to claim 1 or 6, wherein the source code location includes the step of detecting the last path location file where the creation of the HCFM was stopped due to an error in the control flow information, or detecting the path location file where a difference occurred from the reference HCFM. Claim 8 A communication unit that collects status data of a controller operating according to function execution by connecting to a vehicle and diagnostic communication; a simulation unit that constructs virtual controller software (SW) in the same environment as the vehicle and simulates various functions based thereon; and a database (DB) that stores various programs and data for testing the vehicle controller. A vehicle controller test device comprising: a control unit that classifies a test case (TC) in which a failure occurred as a result of executing a functional test through the communication unit or simulation unit, performs a system-level simulation on the test case (TC) to generate binary code according to control flow information, generates a Hierarchical Control Flow Model (HCFM) of the binary code-based controller software (SW) for the test case (TC), and then detects the location of the source code in which the failure occurred through a test code analysis scenario that compares the HCFM based on a reference HCFM corresponding to the entire code, and outputs an analysis result report; wherein the control unit includes an HCFM generation tool that automates the generation of the HCFM using the binary code having the minimum information to be expressed when generating the HCFM of the controller SW. Claim 9 delete Claim 10 In claim 8, the control unit defines a sequential set of instructions from the instruction following one branch statement to the instruction immediately preceding the next branch statement as a basic block when creating the HCFM, and expresses the basic block at the same level as a single command line, wherein a complex flow occurring consecutively by a single function call is written in a form in which a first basic block contains the HCFM of multiple sub-modules, and the second basic block selected by the next branch statement is expressed by connecting it with a junction block, and expresses a branch condition that triggers the corresponding branch as input data at the edge connecting the two. Claim 11 A vehicle controller test method for a vehicle controller test device comprising: a) a step of classifying a test case (TC) in which a failure occurs as a result of testing a function while one or more controllers are connected to a vehicle; b) a step of generating binary code according to control flow information by performing a system-level simulation on the test case (TC); c) a step of creating a Hierarchical Control Flow Model (HCFM) of binary code-based controller software (SW) for the test case (TC) using a creation tool; and d) a step of detecting the last path location where the creation of the HCFM was interrupted due to the failure and outputting it as an analysis result report.

Images