KR102505850B1 - System and method for developing automotive software - Google Patents

Abstract

The present invention relates to a vehicle software development system and method capable of designing and verifying vehicle software according to design requirements of a vehicle controller. The present invention, a requirement analysis unit for extracting an input signal and an output signal from a controller specification written in the design requirements and generating a function list for the correlation between the input signal and the output signal; and a control model generator configured to abstractly define the input and output signals and generate control logic according to the control model.

Description

Vehicle software development system and method {SYSTEM AND METHOD FOR DEVELOPING AUTOMOTIVE SOFTWARE}

The present invention relates to a vehicle software development system and method. More specifically, the present invention relates to a vehicle software development system and method capable of designing and verifying vehicle software according to design requirements of a vehicle controller.

Recently, various new functions and cooperative control functions according to the autonomous driving connected car environment are being applied in the automobile industry, which increases the number of ECUs to control each function. As controllers that provide new functions as well as existing functions are newly developed, the need for standard specification development and software platforms to manage software mounted on multiple controllers is gradually expanding, and each field of vehicle develops its own platform for this. Research on is ongoing.

In particular, the development of standard specifications for the required specifications is the cornerstone for the software development of the controller, and if the technical level of the specified format and specification is not set and managed identically with the upper level specification document, the clarity of the specification is reduced and it is not consistent with the software. It increases the development period and causes the quality to deteriorate.

In addition, when designing an integrated controller that integrates multiple controllers, if the requirements among existing controllers are not standardized, it is impossible to match the input/output signals during specification development, and it takes a lot of time to optimize control logic that performs the same function. .

Republic of Korea Patent Publication No. 10-2013-0138468

It is desirable to efficiently develop standard specifications according to the diversification and integration of functions and to supply software that ensures consistency with the required specifications. To this end, the vehicle software development process requires a new development process rather than the existing method. In addition, the requirements design platform needs to provide an integrated solution that can provide standard function specifications and mass production software at once through a unified software development process from requirements design to software mass production and verification when developing controller specifications to meet these needs. there is.

In order to solve these needs, an object of the present invention is to provide a vehicle software development system and method capable of designing and verifying vehicle software according to design requirements of a vehicle controller.

The present invention, a requirement analysis unit for extracting an input signal and an output signal from a controller specification written in the design requirements and generating a function list for the correlation between the input signal and the output signal; and a control model generator configured to abstractly define the input and output signals and generate control logic according to the control model.

In one embodiment, the requirement analysis unit may include an input/output signal extraction unit for extracting and distinguishing the input signal and the output signal from the controller specification; a variable extraction unit extracting variables from the controller specification; and a function list generating unit generating the function list.

The input/output signal extraction unit may classify the input signal and the output signal into an internal signal indicating a connection between functions, a HW signal connected to a hardware component, or a communication signal in a communication protocol according to a connection relationship.

In addition, the control model generator may include an input/output signal setting unit for abstracting signals according to characteristics of the input and output signals; a parameter setting unit for setting attribute values of the input and output signals or parameters of variables included in the specification; and a control logic generation unit configured to generate control logic according to the input and output signals and the attribute value or the parameter.

In addition, the input/output signal setting unit may generate a standard signal name for the input and output signals by using the input or output classification, the connection relationship between the input signal and the output signal, and the names of the input and output signals. .

Also, the parameter setting unit may generate and manage a file separate from the control logic with respect to the attribute value or the parameter.

Also, the control logic generation unit may generate a test scenario including a connection of the function list and a conditional operator.

Also, the control logic generation unit may select a valid test case from among the test scenarios and generate a test case according to conditions exclusive to conditions of the valid test case.

In one embodiment, the vehicle software development system may further include a verification unit verifying the control logic.

The verification unit may include a unit verification unit that verifies the control logic generated for each function, and an integrated verification unit that performs integrated verification that generates and verifies an integrated model by integrating at least two control logics. there is.

In addition, the integrated verification unit, when an output signal from one of the at least two control logics becomes an input signal of another control logic, an output signal from the one control logic and the other one The signal characteristics of the input signal of the control logic of can be set to an internal signal representing the connection between functions.

In addition, the integrated verification unit may generate a test case based on the input signal and output signal of the integrated model.

The present invention includes: (a) a requirement analysis unit extracting an input signal and an output signal from a controller specification in which design requirements are described, and generating a function list for correlation between the input signal and the output signal; and (b) abstractly defining the input and output signals by a control model generation unit and generating control logic according to the control model.

In one embodiment, in the step (a), the input signal and the output signal may be divided into an internal signal indicating a connection between functions, a HW signal connected to a hardware component, or a communication signal in a communication protocol according to a connection relationship. can

In one embodiment, in the step (b), the control model generating unit, for the input and output signals, input or output classification, the connection relationship between the input signal and the output signal, and the input and output signals A standard signal name can be created using the name.

Also, in step (b), a test scenario including a connection of the function list and a conditional operator is created, and validity of a test case of the test scenario may be determined.

The method further includes (c) a verification step of verifying the control logic by a verification unit, and in the verification step, verification of the control logic generated for each individual function is performed, and the control logic is configured to include at least two Integration verification can be performed to create and verify an integrated model by integrating two models.

In addition, in the step (c), when an output signal from one of the at least two control logics becomes an input signal of another control logic, the output signal from the one control logic and the A signal characteristic of an input signal of another control logic may be set as an internal signal representing a connection between functions.

According to the present invention, it is possible to facilitate the development of vehicle software by enabling integrated design and verification from requirements for vehicle design to software design.

In addition, traceability from requirements to software is ensured, so even if requirements are changed, software can be changed quickly.

In addition, when integrating the controllers developed according to the present invention, since they have the same design structure, integrated design and verification are easy.

As a result, in response to increasingly complex vehicle systems, there is an advantage in effectively designing vehicle software with productivity and quality secured.

1 is a diagram schematically illustrating a vehicle software development system according to an embodiment of the present invention.
2 is a diagram illustrating an analysis result of a requirement analysis unit in a vehicle software development system according to an embodiment of the present invention.
3 shows a script file of parameters generated by a parameter setting unit in a vehicle software development system according to an embodiment of the present invention.
4 is a diagram illustratively illustrating control logic generation by a control logic generation unit in a vehicle software development system according to an embodiment of the present invention.
5 illustrates automatic generation of a test scenario as a control logic generating unit generating an input/output operation list in a vehicle software development system according to an embodiment of the present invention.
6 illustrates that a control logic generation unit generates an input/output operation list in a vehicle software development system according to an embodiment of the present invention, and confirms the validity of a test scenario (activation check).
7 illustrates that a control logic generation unit automatically generates a test scenario by applying an exclusive condition of an activation condition in a vehicle software development system according to an embodiment of the present invention.
8A shows that the control logic generation unit generates control logic according to an output operation according to an input condition in the vehicle software development system according to an embodiment of the present invention.
8B shows that the control logic generation unit generates control logic for adding input/output conditions according to parameter conditions in the vehicle software development system according to an embodiment of the present invention.
9 is a diagram illustrating that an integrated verification unit generates an integrated model in a vehicle software development system according to an embodiment of the present invention.
10 is a flowchart illustrating a vehicle software development method according to an embodiment of the present invention.
11 is a flowchart illustrating a process of generating a control model in a vehicle software development method according to an embodiment of the present invention.
12 is a flowchart illustrating a process of generating an integrated model for integrated verification from a control model for a unit function in a vehicle software development method according to an embodiment of the present invention.

In the following, the content of the present invention will be described clearly and in detail to the extent that a person skilled in the art can easily implement the present invention using drawings.

Since the present invention can have various changes and various forms, specific embodiments will be illustrated in the drawings and described in detail in the text. However, this is not intended to limit the present invention to a specific form disclosed, and should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention. Terms such as first and second may be used to describe various components, but the components should not be limited by the terms.

The terms may be used for the purpose of distinguishing one component from another. For example, a first element may be termed a second element, and similarly, a second element may be termed a first element, without departing from the scope of the present invention. It is understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, but other elements may exist in the middle. It should be. On the other hand, when an element is referred to as “directly connected” or “directly connected” to another element, it should be understood that no other element exists in the middle.

Other expressions describing the relationship between elements, such as "between" and "directly between" or "adjacent to" and "directly adjacent to", etc., should be interpreted similarly. Terms used in this application are only used to describe specific embodiments, and are not intended to limit the present invention. Singular expressions include plural expressions unless the context clearly dictates otherwise.

In this application, the terms "comprise" or "have" are intended to designate that there is an embodied feature, number, step, operation, component, part, or combination thereof, but one or more other features or numerals. However, it should be understood that it does not preclude the possibility of existence or addition of steps, operations, components, parts, or combinations thereof. Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which the present invention belongs. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the related art, and unless explicitly defined in this application, they are not interpreted in an ideal or excessively formal meaning. .

Vehicle software development system (10)

1 is a diagram schematically illustrating a vehicle software development system according to an embodiment of the present invention.

In one embodiment, the vehicle software development system according to the present invention may be implemented based on AUTOSAR, an automotive software platform. AUTOSAR provides a platform that can unify the common elements of vehicle software and enables the development of application software based on this platform.

In the vehicle software development system according to the present invention, when developing vehicle software according to the required specifications, input/output signals and signals are abstracted and defined, classified into functional units to develop a control model, and unit function verification and integrated system verification of the control model. It is characterized in that it is possible to generate control function specifications and vehicle application software from control requirements through.

Referring to FIG. 1 , the vehicle software development system 10 according to the present invention may be implemented as an application layer of AUTOSAR. The vehicle software development system 10 may include a requirement analysis unit 100 , a control model generation unit 200 , a verification unit 300 and a result generation unit 400 . In addition, the vehicle software development system 10 may further include a configuration management unit 500 for coordinating or controlling the operation of each component.

Requirements Analysis Unit (100)

The requirement analysis unit 100 may extract an input signal and an output signal from a controller specification in which design requirements are described, and may generate a function list for a correlation between the input signal and the output signal. In one embodiment, the requirement analysis unit 100 includes an input/output signal extraction unit 110, a variable extraction unit 120, and a function list generation unit 130.

The input/output signal extraction unit 110 extracts input/output signals for required specifications from the controller specification. Typically, vehicle controller specifications for vehicle control are prepared as text files (eg, MS-word files) and provided to software design companies. Here, the logic of the vehicle controller may be provided in the form of an MS-Visio file, and parameter values for logic control may be provided in the form of a table.

The variable extraction unit 120 extracts variables (parameters, etc.) from the controller specification.

The function list generator 130 constructs a function list by connecting the correlation between the input signal and the output signal.

In the implementation of the present invention, the requirement analysis unit 100 may extract input/output signals and variables from a controller specification or controller logic, and may automatically extract a function list for a correlation between an input signal and an output signal. However, in some cases, the requirement analysis unit 100 may provide a user (designer) with an appropriate interface and directly receive input/output signals, variables, or at least a part of the function list from the user.

These input/output signals, variables, and functions can be defined as shown in Table 1 below.

division explanation Function Vehicle functions as an independent control unit Input/Output Signal (IO Data Flow) Flow between input signal, output signal and signal to perform function Variable Various parameters and calibration elements required to perform a function

2 is a diagram illustrating an analysis result of a requirement analysis unit in a vehicle software development system according to an embodiment of the present invention. Hereinafter, analysis of requirements for the rear window defrosting (heating wire) function of a vehicle is exemplified.

The specification for the "rear window defrosting (heating)" function required by the vehicle is "If you press the button with the engine started, the indicator light in the button turns on to inform you that it is in use, and the heating wire operates to defrost the rear window. .If you press the button once more, the operation will stop. After pressing the rear window defrost button, the operation will stop working if about 20 minutes have elapsed in the operating condition. Also, if the engine is turned off and then started again during operation, the operation will stop. It will be returned to its original state.” It is presented as an example.

First, the input/output signal extraction unit 110 extracts and distinguishes input and output signals from the presented functional requirements (Input and Output), and classifies them according to the values of the input and output signals and signal characteristics. Classification according to signal characteristics is divided into CAN communication, LIN communication, and Ethernet communication according to internal signal (Internal) corresponding to connection between functions, HW signal with physically connected hardware components, and communication protocol.

Also, the variable extractor 120 extracts variables for the required specifications.

The function list generating unit 130 creates a function list by connecting correlations between input signals and output signals according to the connection influences of input/output signals and signals for which variables have been configured.

In FIG. 2, according to the description of the required specifications for functions, input/output signals, and variables, the extraction results (Value, I/O, characteristics) of the input/output signals (I/O Data) and the variables (Variable) An example of an extraction result and a function list (Link to) is shown. Here, the names of the input/output signals and variables may be preset and provided according to control objects or input hardware, or the names may be directly input by the user. Alternatively, the name may be selected by the user after presenting a list of input/output signals and variables to the user.

Control model generation unit 200

The control model generating unit 200 may abstractly define input/output signals extracted from specifications, set related parameters, and generate control logic according to the control model. The control model generation unit 200 may include an input/output signal setting unit 210, a parameter setting unit 220, and a control logic generation unit 230.

The input/output signal setting unit 210 abstracts the input/output signals extracted by the input/output signal extraction unit 110 according to signal characteristics. The input/output signal setting unit 210 sets the input/output signal to 1) whether it is an input or output signal, 2) whether the signal characteristics are a connection between functions (INT), a physical connection (HW), and what kind of communication signal (CAN, LIN, ETHernet) can be distinguished according to In one embodiment, the input/output signal setting unit 210 may automatically assign input/output status, signal characteristics, and signal names as "standard signal names" to the input/output signals. Preferably, in giving a standard signal name, the input/output signal setting unit 210 can infer the operation of the corresponding function only with the name, and can infer the properties required for the signal or the operation according to the corresponding property. there is.

Table 2 shows input/output signals set by the input/output signal setting unit 210 by way of example.

input/output signal name standard signal name property Input startup status Input_INT_EngineRunningState - Engine Stop
-Engine Running
-Cranking button Input_HW_RearDefoggerSw -Off
-On Output thermic rays Output_HW_RearDefogger -Off
-On indicator light Output_CAN_RearDefoggerInd -Off
-On

The parameter setting unit 220 sets parameters of the variables extracted by the variable extraction unit 120 . The parameter setting unit 220 may set changeable or constant items, such as a 20-minute time limit in the rear window defrost function, as parameters. In one embodiment, it is preferable that parameters are set to be used only within a corresponding function and not overlapped with other functions. In addition, the parameter setting unit 220 may automatically assign a name to the corresponding parameter or receive a name of the parameter from the user. It may be desirable that the name of the parameter be presented intuitively so that the role and purpose of the parameter can be inferred like the standard signal names presented in Table 2. Table 3 below shows parameters set by the parameter setting unit 220 as an example.

parameter name value Par_RearDefoggerMaxTime 20min

In addition, in the implementation of the present invention, the parameter setting unit 220 may define and generate the attribute values and parameter values of the input/output signals as separate script files instead of defining them as data within each control logic. This is for judging compatibility between functions and verifying independence, and FIG. 3 shows a script file of parameters generated by a parameter setting unit in a vehicle software development system according to an embodiment of the present invention.

The control logic generation unit 230 generates control logic for performing a corresponding function according to set input/output signals and parameters. The control logic generation unit 230 may generate control logic according to the connection relationship and properties of the function list generated by the function list generation unit 130 (refer to the “Link to” item in FIG. 2 ). Also, the control logic generation unit 230 may automatically generate a test scenario including a conditional operator according to the connection relationship of the function list and check the validity of the test scenario to generate the control logic.

4 is a diagram illustratively illustrating control logic generation of a control logic generation unit in a vehicle software development system according to an embodiment of the present invention, and is presented in the form of a Mathlab Similink Subsystem.

The control logic generation unit 230 may generate control logic of the form shown in FIG. 4 after standard input/output signals and parameter settings are completed. In FIG. 4, a subsystem representing a function is created in the center, and input and output ports are placed on the left and right sides.

Control logic generation in the control logic generation unit 230 may be written in the form of a state chart, flow graph, or truth table. In the case of a function in which outputs according to input combinations always match, logic may be created using a flow graph or truth table. On the other hand, even if the combination of inputs is the same, if the output changes according to the current function operation state or the operation changes according to time, it can be written as a state chart. In the case of the rear window defrosting function, the output state of the hot wire is changed for each switch input, and since the output is stopped 20 minutes after the hot wire is output, control logic can be created in the form of a state transition diagram.

A specific example of generating the control logic in the control logic generation unit 230 will be described with respect to the aforementioned rear window defrosting function.

5 illustrates automatic generation of a test scenario by a control logic generation unit generating an input/output operation list in a vehicle software development system according to an embodiment of the present invention, and FIG. 6 illustrates a vehicle according to an embodiment of the present invention. In the software development system, the control logic generation unit generates an input/output operation list, which illustrates checking the validity of a test scenario (activation check), and FIG. 7 shows control logic generation in a vehicle software development system according to an embodiment of the present invention. An example of automatically generating test scenarios by applying exclusive conditions of additional activation conditions. 8A shows that the control logic generation unit generates control logic according to an output operation according to an input condition in the vehicle software development system according to an embodiment of the present invention, and FIG. 8B shows a vehicle according to an embodiment of the present invention. In the software development system, the control logic generator generates control logic for adding input/output conditions according to parameter conditions.

Referring to FIG. 5 , the control logic generation unit 230 may automatically generate all test scenarios including conditional operators according to the link to function list (Link to) of input/output signals. In FIG. 5, according to the test cases TC1 and TC2 and the state, a test case corresponding to Event (input signal), Value (input signal value), Expected (output signal), and Value (output signal value) is automatically What was created is exemplified. Among the test cases in FIG. 5 , invalid test cases may also be included.

Referring to FIG. 6 , the control logic generation unit 230 checks actual valid test cases among all automatically generated test scenarios. That is, among all test cases in which input signals, output signals, and their values correspond, test cases that can actually be operated effectively are selected (Activation Check).

Referring to FIG. 7 , the control logic generation unit 230 automatically generates an inactivation test scenario as an exclusive condition of the activation condition of the valid test case in FIG. 6 . That is, TC1 in FIG. 7 is a test case of an activation condition, and test cases such as TC2 and TC3 correspond to an inactivation test case as an exclusive condition of TC1.

Control logic as shown in FIG. 8A is automatically generated according to the activation condition and the inactivation condition confirmed through this process. Thereafter, the control logic generation unit 230 may automatically generate control logic to which parameters are applied, as shown in FIG. 8B.

verification unit 300

The verification unit 300 may perform verification of control logic generated for each individual function and integrated verification of generating and verifying an integrated model by integrating a plurality of control logics for each individual function. This verification unit 300 may include a unit verification unit 310 and an integrated verification unit 320 .

The unit verification unit 310 may perform verification of individual functional units. The unit verification unit 310 may perform verification of the control logic for each function generated by the control logic generation unit 230 . In one embodiment, the unit verification unit 310 may perform verification for individual functions based on test cases. In one embodiment, the test case may be one using an Activation/Inactivation-based test case generated by the control logic generation unit 230 or separately provided to the unit verification unit 310.

Meanwhile, verification of individual functions may include static verification and dynamic verification. Static verification reviews whether the written control logic requirements are implemented and checks compliance with the modeling guide. The modeling guide checks both Mandatory items that must be applied and Recommended items that are recommendations, and according to the evaluation results, when creating the final software code, the readability of the code can be secured and the optimized source code can be created. Dynamic verification proceeds with Condition Coverage and Decision Coverage verification to verify the consistency and integrity of the logic from the control logic written in the state chart, and each condition and decision is verified by generating a test case according to the state chart transition condition according to the input/output signal. can do.

The integrated verification unit 320 generates an integrated verification model by integrating the individual functions verified by the unit verification unit 310, checks the consistency of the internal signal connection between each unit function control model, and checks whether the external input/output signal is You can verify that it has been assigned correctly.

The integrated verification unit 320 generates an integrated model by integrating at least two unit function control models generated by the control model generation unit 200 to determine the consistency of internal signal connections between the unit function control models and the allocation of external input/output signals. can be verified.

In addition, the integrated verification unit 320 automatically creates a test case based on the input/output signals and variables included in the integrated model, secures a valid test case based on the automatically generated control logic, and based on the test case. It may also be possible to perform verification of the integrated model with The automatic generation of test cases and the generation of integrated control logic based on such an integrated model may be performed by applying the method for the unit function control model described with reference to FIGS. 5 to 8B.

9 is a diagram illustrating that an integrated verification unit generates an integrated model in a vehicle software development system according to an embodiment of the present invention. 9(a) is a diagram showing a function model for unit functions of controller A 20 and a control model for unit functions of controller B 30 linked together, and FIG. 9(b) shows controller A ( 20) and the integrated model 40 integrating the unit functions of the B controller 30.

Referring to (a) of FIG. 9, in the control model according to the A specification of the A controller 20, input signals of 'Input_HW_External 1' and 'Input_CAN_External 1' are input to the A controller 20, The A controller 20 outputs output signals of 'Output_CAN_other controller 1', 'Output_HW_AA1' and 'Output_CAN_AA2'.

In the control model according to the B specification of the B controller 30, the B controller 30 receives 'Output_HW_AA1' and 'Output_CAN_AA2', which are output signals of the A controller 20, as input signals, and receives 'Output_HW_other controller 2' as input signals. outputs the output signal of

As described above, in generating a control module for each function, the input/output signal setting unit 210 abstracts the input/output signal according to the signal characteristic, and depending on the input or output, whether the signal characteristic is a connection between functions (INT), physical Depending on whether it is connected (HW) or what type of communication signal it is (CAN, LIN, ETHernet), input/output signals are abstracted and standardized names are given.

Even in generating the integrated model, the abstraction of the input/output signals can use what was set in the input/output signal setting unit 210. As shown in FIG. 9, the output signal of controller A 20 is the input signal of controller B 30 , the corresponding signal corresponds to an inter-function connection. Accordingly, attribute values such as '_HW' and '_CAN' are changed to '_INT' and input/output signals are newly set.

Referring to (b) of FIG. 9, in generating the integrated model 40 in which the A controller 20 and the B controller 30 are interlocked, 'Output_HW_AA1' and 'Output_CAN_AA2', which are output signals of the A controller, are 'Output_INT_AA1' ' and 'Output_INT_AA2', and the signal characteristics of 'Input_HW_AA1' and 'Input_CAN_AA2', which are input signals of the B controller, are changed to 'Input_INT_AA1' and 'Input_INT_AA2'.

The integrated verification unit 320 creates an integrated model by integrating control modules for unit functions in the method shown in FIG. automatically generate In addition, the integrated verification unit 320 may secure a valid test case list from automatically generated test cases. The function of the integrated verification unit 320 may be performed in the same way as the control logic generation unit 230 generates control logic for unit functions and generates test cases.

Result generator 400

The output generator 400 may include a function specification generator 410 and an application program generator 420 .

The function specification generation unit 410 may extract a function requirement specification from a control model created based on a requirement. The application program generator 420 may generate an application program from the verified control logic.

How to develop vehicle software

10 is a flowchart illustrating a vehicle software development method according to an embodiment of the present invention.

The requirement analysis unit 100 extracts an input signal and an output signal from the controller specification in which the design requirements are described, and generates a function list for correlation between the input signal and the output signal (S100).

The control model generation unit 200 abstractly defines the input and output signals and generates control logic according to the control model (S200).

The verification unit 300 performs unit verification on the control logic generated for each individual function, and when a plurality of control logics connected to each other exist, integrated verification of generating and verifying an integrated model by integrating a plurality of control logics. It is performed (S300).

After the verification is completed, the result generating unit 400 extracts a functional requirement specification from the control model prepared based on the requirements, and generates an application program from the control logic for which verification has been completed (S400).

Create control models for unit functions

11 is a flowchart illustrating a process of generating a control model in a vehicle software development method according to an embodiment of the present invention. Referring to FIG. 11 , a process in which the control model generation unit 200 generates control logic according to the control model will be described in more detail.

The requirement specification analysis unit 100 receives input/output data from the controller specification written in the design requirements (S202), and classifies the input signal and output signal according to their characteristics (S204). The requirement analysis unit 100 extracts and distinguishes input and output signals from input and output signals (Input and Output), and can classify input and output signals according to values and signal characteristics.

Depending on the characteristics of the input and output signals, the input/output signal is an internal signal corresponding to the connection between functions, or a HW signal with physically connected hardware components, and CAN communication, LIN communication, or Ethernet communication depending on the communication protocol. It can be determined whether it is a signal (S206).

The control model generating unit 200 abstracts the extracted input/output signal according to signal characteristics (S208).

The control model generation unit 200 generates an IO Data Table according to characteristics of input signals and output signals (S210). Here, the input/output data table is primarily generated by the requirement analysis unit 100, and the control model generation unit 200 may directly or modify it to utilize it.

A connection relationship (function list) between an input signal and an output signal is checked (S212), and a function operation list according to the function list is generated based on the attribute value through the connection between the input signal and the output signal (S214). This function operation list is an input/output operation list as shown in FIG. 5, and all possible test scenarios can be generated in step S214.

The control model generating unit 200 checks test cases having valid conditions among the test cases included in the test scenarios (S216).

It is determined whether the test case is valid (activation condition satisfied or not) (S218), a test case (which can also be understood as a function list) according to the valid condition is created (S220), and as an exclusive condition for the valid condition A test case according to the inactivation condition is created (S230).

Next, the presence or absence of parameters may be determined (S224). If the parameter exists, it is checked whether the parameter is related to the input signal or the output signal (S226), and a control model is created (S228). Here, the control model may be a state chart, but is not limited thereto.

Create an integrated model

12 is a flowchart illustrating a process of generating an integrated model for integrated verification from a control model for a unit function in a vehicle software development method according to an embodiment of the present invention.

The integrated verification unit 320 of the verification unit 300 performs a function of generating and verifying an integrated model by integrating at least two control logics.

A plurality of control models are input (S302).

The integrated verification unit 320 analyzes the characteristics of the input/output signals included in the plurality of control models (S304).

Whether the external output signal of the first control model (Unit1) corresponds to the external input signal of the second control model (Unit2), or whether the external input signal of the first control model (Unit1) corresponds to the external output signal of the second control model (Unit2) It is determined whether it corresponds to a signal (S306).

If it is determined as No in step S306, an external output signal or external input signal from each control model (Unit1, Unit2) is added (S308, S312).

If, as a result of the determination in step S306, when the output signal of one control model becomes the input signal of another control model, the output signal of the one control model and the input signal of the other control model The signal characteristic of is set to an internal signal representing the connection between functions (S310).

The data flow of input/output signals is determined (S314), related parameters are defined (S316), and an integrated control model is generated (S318).

When it is determined that the configuration of all input/output data flows is completed (S320), the creation of the integrated model is completed by completing the generation of the control model (S322).

Additionally, dynamic or static verification of the integrated model may be performed by the verification unit 300 (S324).

After the verification is complete, a functional requirement specification and an application program may be generated (S326).

The above description is merely an example of the technical idea of the present invention, and those skilled in the art can make various modifications, changes, and substitutions without departing from the essential characteristics of the present invention. will be. Therefore, the embodiments disclosed in the present invention and the accompanying drawings are not intended to limit the technical idea of the present invention, but to explain, and the scope of the technical idea of the present invention is not limited by these embodiments and the accompanying drawings. . The protection scope of the present invention should be construed according to the following claims, and all technical ideas within the equivalent range should be construed as being included in the scope of the present invention.

10: vehicle software development system 100: requirements analysis unit
110: input/output signal extraction unit 120: variable extraction unit
130: function list generation unit 200: control model generation unit
210: signal setting unit 220: parameter setting unit
230: control logic generation unit 300: verification unit
310: unit verification unit 320: integrated verification unit
400: result generation unit 410: function specification generation unit
420: application generator

Claims (18)

a requirement analysis unit for extracting an input signal and an output signal from a controller specification written with design requirements and generating a function list for a correlation between the input signal and the output signal;
a control model generation unit that abstractly defines the input and output signals and generates control logic according to the control model; and
a verification unit having an integrated verification unit that performs integrated verification for generating and verifying an integrated model by integrating at least two of the control logics;
including,
The control model generating unit includes an input/output signal setting unit for abstracting signals according to characteristics of the input and output signals,
The input/output signal setting unit generates a standard signal name for the input and output signals by using the input or output classification, the connection relationship between the input signal and the output signal, and the names of the input and output signals,
The integrated verification unit, when an output signal from any one control logic of the at least two control logic becomes an input signal of another control logic, the output signal from the one control logic and the other control logic Characterized in that the signal characteristic of the input signal of the logic is set to an internal signal representing the connection between functions, a vehicle software development system. According to claim 1,
The requirements analysis unit,
an input/output signal extraction unit for extracting and distinguishing the input signal and the output signal from the controller specifications;
a variable extraction unit extracting variables from the controller specification; and
A vehicle software development system comprising a function list generating unit generating the function list. According to claim 2,
The input/output signal extraction unit divides the input signal and the output signal into an internal signal indicating a connection between functions, a HW signal connected to a hardware component, or a communication signal in a communication protocol according to a connection relationship, vehicle software. development system. According to claim 1,
The control model generation unit,
a parameter setting unit for setting attribute values of the input and output signals or parameters of variables included in the specification; and
The vehicle software development system of claim 1, further comprising a control logic generation unit generating control logic according to the input and output signals and the attribute value or the parameter. delete According to claim 4,
The vehicle software development system, characterized in that the parameter setting unit creates and manages a file separate from the control logic for the attribute value or the parameter. According to claim 4,
The vehicle software development system, characterized in that, the control logic generation unit generates a test scenario including a connection of the function list and a conditional operator. According to claim 7,
The vehicle software development system, characterized in that, the control logic generating unit selects a valid test case from among the test scenarios and generates a test case according to conditions exclusive to conditions of the valid test case. delete According to claim 1,
The vehicle software development system, characterized in that the verification unit further comprises a unit verification unit performing verification on the control logic generated for each function. delete According to claim 1,
The vehicle software development system, characterized in that the integrated verification unit generates a test case based on the input signal and the output signal of the integrated model. (a) extracting an input signal and an output signal from a controller specification in which design requirements are described by a requirement analysis unit and generating a function list for correlation between the input signal and the output signal;
(b) abstracting and defining the input and output signals by a control model generation unit and generating control logic according to the control model; and
(c) a verification step of verifying the control logic by a verification unit;
including,
In the step (b), the control model generation unit uses standard signal names for the input and output signals by using the input or output classification, the connection relationship between the input signal and the output signal, and the names of the input and output signals. create,
In the step (c), an integrated verification of generating and verifying an integrated model by integrating at least two control logics is performed,
In the step (c), when an output signal from one of the at least two control logics becomes an input signal of another control logic, the output signal from the one control logic and the other control logic Characterized in that the signal characteristics of the input signal of the control logic of the vehicle software development method is set to an internal signal representing the connection between functions. According to claim 13,
In the step (a), the input signal and the output signal are classified into an internal signal indicating a connection between functions, a HW signal connected to a hardware component, or a communication signal in a communication protocol according to a connection relationship. software development methods. delete According to claim 13,
In the step (b), a test scenario including a connection of the function list and a conditional operator is generated, and validity of a test case of the test scenario is determined. The method of any one of claims 13, 14 and 16,
In the step (c), verification of the control logic generated for each function is further performed. delete

Images