Simulink model, software integration system, software integration method and related device

Abstract

The invention discloses a simulink model, a software integration system, a software integration method and a related device, the simulink model comprises an integration module and a unit module, the integration module comprises at least one sub-component model, the integration module is used for generating a target component model based on the at least one sub-component model, and the target component model is used for performing an integration test; the unit module comprises any one sub-assembly model, the unit module is used for generating a test assembly model based on one sub-assembly model, and the test assembly model is used for carrying out unit testing. By means of the mode, integration testing and unit testing of the component model can be achieved in the simulink model.

Description

Technical Field

[0001] The present application relates to the field of software design technology, and in particular to a simulink model, a software integration system, a software integration method and related devices. Background Art

[0002] The AUTOSAR architecture is an open software architecture standardized by the automotive industry, which specifies the standard interface between application software and basic vehicle functions. Model-based design (hereinafter referred to as MBD) is widely used in software development in the current automotive industry, and the mainstream development tools are Matlab / Simulink. Matlab / Simulink is used for the detailed design of software components, that is, to build models and generate code according to algorithms. After the design of software components is completed, they need to be tested. Software testing includes integration testing of the software components as a whole and unit testing of some components in the software components. However, existing software developed based on Simulink cannot support integration testing and unit testing in Simulink at the same time. Summary of the invention

[0003] The main technical problem solved by the present application is to provide a simulink model, a software integration system, a software integration method and related devices, which can realize the integration test and unit test of the component model in the simulink model.

[0004] To solve the above technical problems, the first aspect of the present application provides a Simulink model, which includes: an integration module and a unit module, the integration module includes at least one sub-component model, the integration module is used to generate a target component model based on at least one sub-component model, and the target component model is used to perform integration testing; the unit module includes any sub-component model, the unit module is used to generate a test component model based on a sub-component model, and the test component model is used to perform unit testing.

[0005] In some embodiments, the integration module and / or the unit module include: a sub-component module, a first interface module and a second interface module, the sub-component module includes the sub-component model; the first interface module includes the input interface of the sub-component model; the second interface module includes the output interface of the sub-component model; the target component model and / or the test component model are generated based on the sub-component model, the input interface of the sub-component model and the output interface of the sub-component model.

[0006] In some embodiments, the sub-component model includes at least one component function, which at least represents the function of the sub-component model; the integration module and / or the unit module also includes a scheduling module, and the second interface module also includes a communication interface between each of the component functions; the scheduling module is used to define the scheduling order of the input interface, the output interface and the at least one component function.

[0007] In some embodiments, the subcomponent model includes multiple component functions, each of which corresponds to an execution cycle; the scheduling module is used to define the scheduling order of the input interface, the output interface and each component function in each execution cycle.

[0008] In some embodiments, the integration module is further used to export component configuration information of the target component model, and the component configuration information is used to generate software integration code.

[0009] To solve the above technical problems, the second aspect of the present application provides a software integration system, which includes an AUTOSAR tool and the simulink model provided by the above first aspect; the AUTOSAR tool is used to generate a software integration code for software integration based on component configuration information exported from the integration module of the simulink model.

[0010] To solve the above technical problems, the third aspect of the present application provides a software integration method, which is applied to the software integration system provided by the second aspect. The software integration method includes: generating a target component model using a simulink model, and sending component configuration information of the target component model to an AUTOSAR tool; generating a software integration code based on the component configuration information using the AUTOSAR tool; and performing software integration based on the software integration code.

[0011] In some embodiments, the component configuration information includes interface information; after sending the component configuration information of the target component model to the AUTOSAR tool, the method further includes: in response to the interface information update, sending the updated interface information to the simulink model, so that the simulink model regenerates the target component model based on the updated interface information.

[0012] To solve the above technical problems, the fourth aspect of the present application provides an electronic device, which includes a memory and a processor, the memory storing program instructions; the processor is used to execute the program instructions stored in the memory to implement the method provided in the third aspect.

[0013] To solve the above technical problems, the fifth aspect of the present application provides a computer-readable storage medium, which is used to store program instructions, and the program instructions can be executed by a processor to implement the method provided in the third aspect.

[0014] The beneficial effects of the present application are as follows: different from the prior art, the Simu Link model provided by the present application includes an integration module and a unit module, the integration module includes at least one sub-component model, the integration module is used to generate a target component model based on at least one sub-component model, and the target component model is used to perform integration testing, so that the integration testing of the component model can be realized in the Simu Link model; the unit module includes any sub-component model, the unit module is used to generate a test component model based on a sub-component model, and the test component model is used to perform unit testing, so that the unit testing of the component model can be realized in the Simu Link model. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 It is a schematic diagram of the framework structure of an existing software integration method based on the simulink model;

[0016] Figure 2 It is a schematic diagram of the framework structure of an embodiment of the simulink model provided by the present application;

[0017] Figure 3 It is a schematic diagram of the framework structure of an implementation scheme of an integrated module in a simulink model provided by the present application;

[0018] Figure 4 It is a schematic diagram of the framework structure of an implementation scheme of a unit module in the simulink model provided by the present application;

[0019] Figure 5 It is a schematic diagram of the framework structure of an implementation method of a software integration system provided by the present application;

[0020] Figure 6 It is a flowchart of an implementation method of a software integration method provided by the present application;

[0021] Figure 7 It is a schematic diagram of the framework structure of an embodiment of an electronic device provided by the present application;

[0022] Figure 8 It is a schematic diagram of the framework structure of an implementation scheme of a computer-readable storage medium provided in this application. DETAILED DESCRIPTION

[0023] The following is a clear and complete description of the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0024] It should be noted that in the embodiments of the present application, there are descriptions involving "first," "second," etc., which are only used for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first," "second" may explicitly or implicitly include at least one of the features.

[0025] In the description of the application, the meaning of "multiple" is at least two, for example, two, three, etc., unless otherwise clearly and specifically limited. In the embodiment of the present application, all directional indications (such as up, down, left, right, front, back ...) are only used to explain the relative position relationship, movement, etc. between the components under a certain specific posture (as shown in the drawings). If the specific posture changes, the directional indication also changes accordingly. In addition, the terms "including" and "having" and any of their deformations are intended to cover non-exclusive inclusions. For example, the process, method, system, product or equipment comprising a series of steps or units is not limited to the steps or units listed, but optionally also includes the steps or units not listed, or optionally also includes other steps or units inherent to these processes, methods, products or equipment.

[0026] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present invention. The appearance of the phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0027] First of all, it should be noted that software modeling can clarify the functional requirements of the system and ensure the development of a software system that meets user expectations. Take the development of the AUTOSAR architecture as an example. The AUTOSAR architecture is an open software architecture standardized by the automotive industry, which specifies the standard interface between application software and basic vehicle functions. Currently, software development in the automotive industry widely adopts the model-based design (hereinafter referred to as MBD) development method, and the mainstream development tool is Matlab / Simulin k.

[0028] As the complexity of automotive electrical and electronic systems increases, it is particularly important to ensure their safety. The international road vehicle functional safety standard ISO26262 is specifically aimed at safety-related systems such as specific electrical devices, electronic devices, programmable electronic devices used in the automotive industry. It aims to ensure the safety and reliability of automotive electrical and electronic systems by reducing the risk of system failures and improving safety. The standard covers the entire life cycle activities from the conceptual stage of product development to system, hardware, software design and development and related production, service and scrapping. Therefore, after the model is developed in the development tool, it is necessary to perform unit testing on the code generated by the model, integrate the code generated by the model, and perform integration testing on the integrated code to ensure that the developed model meets the standard.

[0029] Currently, the software modeling in Simulink model does not support integration testing, such as Figure 1 As shown, Figure 1 It is a schematic diagram of the framework structure of an implementation method of an existing software integration method based on a simulink model. Each component model is created in the simulink model, and each component model is an AUTOSAR software component (SoftwareComponent, SWC), that is, each component model is a model that can generate code independently. Each component model can contain one or more component functions (i.e., Runnable), and when generating code, the content in a single Runn able will be encapsulated into a function for calling. After completing the design of the component model in the simulink model, the description information of the component model can be exported as an ARXML file, and then imported into the AUTOSAR tool for architecture design. In the architecture design stage, multiple component models can be organized into an architecture model according to their functions, so that they have a certain hierarchical relationship. In the process configuration stage, each Runnable can be placed in the corresponding task and scheduled in a specified order. Specifically, in the process configuration stage, a task can be constructed for each execution cycle, and the component function corresponding to the target execution cycle of each component model needs to be specified in the target task corresponding to the target execution cycle. In other words, the prior art is to perform architecture design in the AUTOSAR tool and set the calling order of the component function of each component model. When the number of component models and component functions is large, scheduling order errors are prone to occur, resulting in the inability to complete software integration.

[0030] It can be seen that each component model in the prior art is independent. For large systems and software with complex functions, the number of component models is large, resulting in a rapid increase in the complexity of the model. When designing the architecture in the AUT OSAR tool, it is necessary to schedule each component model in a certain order, which increases the difficulty of integrated software design. And because each component model is independent, it is impossible to implement integrated testing of all component models in the simuli nk model. Based on this, the present application provides a simulink model that can implement integrated testing and unit testing of component models in the simulink model.

[0031] Please refer to Figure 2-4 , Figure 2 is a schematic diagram of the framework structure of an embodiment of the simulink model provided by the present application, Figure 3 is a schematic diagram of the framework structure of an implementation scheme of an integrated module in a simulink model provided by the present application, Figure 4 It is a schematic diagram of the framework structure of an implementation scheme of a unit module in the Simulink model provided by this application.

[0032] The simulink model includes an integration module and a unit module, and the integration module includes at least one sub-component model. The integration module is used to generate a target component model based on at least one sub-component model, and the target component model is used to perform integration testing. The sub-component model can be developed by R&D personnel, and the sub-component model is obtained after a detailed design of the component, and the detailed design includes defining the internal structure of the component and how to operate this structure, as well as the way in which the component interacts with the external system, etc. A component refers to a modular part that can be independently deployed and replaced in a software system. For example, a component can be a functional unit, a library, a service, a plug-in or other independent software unit. In this application, the sub-component model lacks the necessary configuration for generating code and cannot directly generate code. In one embodiment, after the development of each sub-component model is completed, each sub-component model can be added to the final integrated model by a model reference method to form a target component model. The target component model can be an independent model that can generate code, so the target component model can be integrated tested.

[0033] Since the sub-component model is a model that cannot generate code, it cannot be unit tested. In order to be able to perform unit tests on each sub-component model while implementing integrated testing, a unit module is added to the simulink model. The unit module can include any sub-component model. The unit module is used to generate a test component model based on a sub-component model. The test component model is a model that can generate code, so the test component model can be unit tested. It can be understood that the simulink model can include multiple unit modules, each of which includes different sub-component models; the simulink model can also include only one unit module, and a unit module is used to form a corresponding test component model based on each sub-component model. Taking the simulink model including a unit module as an example, when unit testing each sub-component model, the sub-component model to be tested can be selected from multiple sub-component models, the sub-component model to be tested can be added to the unit module, and the necessary configuration information required for the sub-component model to be tested to generate code is added to the unit module to generate the test component model, and then the test component model is unit tested. The subcomponent model to be tested can be selected from multiple subcomponent models by the user, or each subcomponent model can be used as the subcomponent model to be tested in turn. The necessary configuration information required to generate code for the subcomponent model to be tested includes but is not limited to the communication information between the component functions of the subcomponent model.

[0034] By setting an integration module and a unit module in a simulink model, the integration module includes at least one sub-component model, the integration module is used to generate a target component model based on at least one sub-component model, and the target component model is used to perform integration testing. In this way, the integration testing of the component model can be implemented in the simulink model; the unit module includes any sub-component model, the unit module is used to generate a test component model based on a sub-component model, and the test component model is used to perform unit testing. In this way, the unit testing of the component model can be implemented in the simulink model.

[0035] The integration test and unit test mentioned above both include at least one of the MIL test (Model In-the-Loop) and the SIL test (Software In-the-Loop). Among them, the MIL test refers to the simulation test of the model to verify the correctness of the algorithm; the SIL test is used to verify whether the model and the code generated by the model are equivalent.

[0036] In one embodiment, the above-mentioned integrated module and / or unit module may include a sub-component module, a first interface module, and a second interface module, wherein the sub-component module includes a sub-component model, the first interface module includes an input interface of the sub-component model, and the second interface module includes an output interface of the sub-component model. In combination with the sub-component model and the input interface and output interface corresponding to the sub-component model, a target component model and / or a test component model may be generated.

[0037] When the number of sub-component models includes at least 2 or the sub-component model includes at least 2 component functions, the integration module may further include a scheduling module; when the sub-component model includes at least 2 component functions, the unit module may further include a scheduling module. The scheduling module is used to define the scheduling order of the input interface, the output interface and at least one component function. Among them, the component function at least represents the function of the sub-component model. It can be understood that the component function may include the implementation logic, related code and other information of the sub-component model; each component function may correspond to an execution cycle. For example, the sub-component model includes two component functions, the execution cycle corresponding to the first component function is 2ms, and the execution cycle corresponding to the second component function is 10ms. The scheduling order is used to determine the software architecture when generating the final integrated software.

[0038] In a specific embodiment, Figure 3 As shown, the integration module includes a sub-component module, a first interface module, a second interface module, and a scheduling module. The sub-component module includes at least one sub-component model for generating a target component model, wherein the sub-component model may include at least one component function, and each sub-component function corresponds to a different execution cycle. Figure 3 As shown, taking the sub-component module including sub-component model 1 and sub-component model 2 as an example, sub-component model 1 may include component function 11 and component function 12, sub-component model 2 may include component function 21 and component function 22, component function 11 and component function 21 both belong to the first execution cycle, and component function 21 and component function 22 both belong to the second execution cycle.

[0039] The first interface module may include an input interface of each sub-component model. When the sub-component model includes multiple component functions, the input interface of the sub-component model may include an input interface corresponding to each component function. The first interface module may include multiple areas, each area corresponds to a different cycle, and each area stores the input interface of the sub-component model of the corresponding execution cycle. The second interface area may include an output interface of each sub-component model. When the sub-component model includes multiple component functions, the output interface of the sub-component model may include an output interface corresponding to each component function. Figure 3As shown, the first interface module includes a first area and a second area, one of the first area and the second area stores the input interface of the component function of each sub-component model corresponding to the first execution cycle, that is, the input interface of the sub-component model 1 corresponding to the component function 11, and the input interface of the sub-component model 2 corresponding to the component function 21. The other area stores the input interface of the component function of each sub-component model corresponding to the second execution cycle. The second interface area may include a third area and a fourth area, one area stores the output interface of the component function of each sub-component model corresponding to the first execution cycle, and the other area stores the output interface of the component function of each sub-component model corresponding to the second execution cycle.

[0040] The second interface area may also include communication interfaces between component functions, and the scheduling area may define input interfaces, output interfaces, and the scheduling order of component functions in each execution cycle. For example, in the first execution cycle, the scheduling area may define the input interfaces of component functions in each component model corresponding to the first execution cycle, the output interfaces of component functions in each component model corresponding to the first execution cycle, and the scheduling order of component functions in each component model corresponding to the first execution cycle.

[0041] Each sub-component model is stored in a sub-component module. By integrating each sub-component model, the component functions of each sub-component model can be integrated into a large target component function. The input interface of each sub-component model in the first interface module is integrated to obtain the input interface of the target component function. The output interface of each sub-component model in the second interface module is integrated to obtain the output interface of the target component function. In this way, the target component model can be generated. Further, a scheduling area is set. The order of each sub-component model of the target component model can be designed through the scheduling order defined in the scheduling area. In this way, the hierarchical target component model can be designed in the simulink model.

[0042] After the integration module obtains the target component model, the component configuration information of the target component model can be exported, and the component configuration information can be provided to the AUTOSAR tool to generate software integration code.

[0043] In a specific embodiment, Figure 4As shown, the unit module may also include a sub-component module, a first interface module, a second interface module and a scheduling module, the sub-component module includes a sub-component model, the first interface module includes an input interface of a component function corresponding to each execution cycle of the sub-component model, the second interface module includes an output interface of a component function corresponding to each execution cycle of the sub-component model, and a communication interface between component functions of the sub-component model. The scheduling module is used to define the order of input interface, component function, and output interface in each execution cycle. The unit model can be equivalent to a virtual software component (Devlopment Model), which can generate code for unit testing.

[0044] The simulink model provided above is mainly used to design the functions of some software components in the software, and to perform architecture design on some software components to form a target component model. In other words, the target component model is only a part of the overall software. Therefore, this application also provides a software integration system, please refer to Figure 5 , Figure 5 It is a schematic diagram of the framework structure of an implementation method of a software integration system provided in this application. The software integration system includes an AUTOSAR tool and a simulink model provided in the above implementation method, and the overall software is obtained by using the software integration system.

[0045] Specifically, the target component model can be obtained based on the integration of each sub-component model in the simulink model, and then the component configuration information of the target component model can be exported. The component configuration information can be an AR XML file, and the ARXML file can contain the component function information, interface information, port information, variable information between each component function, etc. of the target component model. After the AUTOSAR tool obtains the ARXML file, it performs architecture design in its architecture design module, and schedules and sets the calling order of the component functions of each component model in the process configuration module. Since the present application sets the scheduling order of the component functions of each sub-component model that forms the target component model in the simulink model, the target component function of the integrated target component model is formed according to the scheduling order of the component functions of each sub-component model. Therefore, the target scheduling function can be directly used in the process configuration module of the AUTOSAR tool without resetting the scheduling order of the component functions of each sub-component model, thereby saving processing time in the AUTOSAR tool.

[0046] like Figure 5As shown, the target component model is integrated by sub-component model 1 and sub-component model 2. Sub-component model 1 includes component function 11 and component function 12, and sub-component model 2 includes component function 21 and component function 22. Component function 11 and component function 21 correspond to an execution cycle of 2ms, and component function 21 and component function 22 correspond to an execution cycle of 10ms. The AUTOSAR tool can obtain the target component function 1 and the target component function 2 based on the ARXML file, wherein the target component function 1 can include component function 11 and component function 21, and the target component function 2 can include component function 21 and component function 22.

[0047] Based on the above embodiments, the present application also proposes a software integration method, which is applied to the above software integration system. Figure 6 , Figure 6 1 is a flowchart of an implementation method of a software integration method provided by the present application. Specifically, the software integration method of this embodiment includes the following steps:

[0048] S61: Generate a target component model using the Simulink model, and send component configuration information of the target component model to the AUTOSAR tool.

[0049] Specifically, after the development of each sub-component model is completed, each sub-component model can be added to the sub-component module through the model reference method, and the input interface of each sub-component model is added to the first interface module, the output interface of each sub-component model is added to the second interface module, and the communication interface between the component functions of each sub-component model is added to the second interface module. After the scheduling module defines the execution order of each input interface, each output interface and each component function, integration is performed to obtain the target component model. The component configuration information of the target component model is exported and sent to the AUTOSAR tool.

[0050] S62: Generate software integration code based on component configuration information using AUTOSAR tools.

[0051] The AUTOSAR tool designs the architecture of the target component model and other component models, and schedules the execution order of the target component functions of the target component model.

[0052] S63: Perform software integration based on the software integration code.

[0053] Through the above method, the Simulink model can be used to design the specific functions and architecture of some software components, and then the AUTOSAR tool can be used to integrate some software components to obtain the final software.

[0054] In one embodiment, the component configuration information includes interface information; after sending the component configuration information of the target component model to the AUTOSAR tool, the method further includes: in response to the interface information update, sending the updated interface information to the simulink model, so that the simulink model regenerates the target component model based on the updated interface information. It can be understood that the interface information update can be an update of the interface information of the target component model, or an update of the interface information of a subcomponent model in the target component model.

[0055] See also Figure 7 , Figure 7 It is a schematic diagram of the framework structure of an embodiment of an electronic device provided in the present application.

[0056] The electronic device 70 includes a memory 71 and a processor 72 coupled to each other, the memory 71 stores program instructions, and the processor 72 is used to execute the program instructions to implement the steps in any of the above method embodiments. Specifically, the electronic device 70 may include but is not limited to: a desktop computer, a laptop computer, a server, a mobile phone, a tablet computer, etc., which are not limited here.

[0057] Specifically, the processor 72 is used to control itself and the memory 71 to implement the steps in any of the above method embodiments. The processor 72 can also be called a CPU (Central Processing Unit). The processor 72 may be an integrated circuit chip with signal processing capabilities. The processor 72 can also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. In addition, the processor 72 can be implemented by an integrated circuit chip.

[0058] See also Figure 8 , Figure 8 It is a schematic diagram of the framework structure of an implementation scheme of a computer-readable storage medium provided in this application.

[0059] The computer-readable storage medium 80 stores program instructions 81 , and when the program instructions 81 are executed by a processor, they are used to implement the steps in any of the above method embodiments.

[0060] The computer-readable storage medium 80 may specifically be a medium that can store computer programs, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, or may be a server that stores the computer program. The server may send the stored computer program to other devices for execution, or may execute the stored computer program itself.

[0061] If the technical solution of this application involves personal information, the product using the technical solution of this application has clearly informed the personal information processing rules and obtained the individual's voluntary consent before processing the personal information. If the technical solution of this application involves sensitive personal information, the product using the technical solution of this application has obtained the individual's separate consent before processing the sensitive personal information, and at the same time meets the "explicit consent" requirement. For example, on personal information collection devices such as cameras, clear and prominent signs are set to inform that the personal information collection scope has been entered and personal information will be collected. If the individual voluntarily enters the collection scope, it is deemed that he or she agrees to the collection of his or her personal information; or on the device that processes personal information, the personal information processing rules are notified by obvious signs / information, and the individual's authorization is obtained through pop-up information or by asking the individual to upload his or her personal information; among them, the personal information processing rules may include information such as the personal information processor, the purpose of personal information processing, the processing method, and the type of personal information processed.

[0062] The above description is only an implementation method of the present application, and does not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly used in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A simulink model, characterized in that: The Simulink model includes: An integration module, the integration module comprising at least one sub-component model, the integration module being used to generate a target component model based on the at least one sub-component model, the target component model being used to perform integration testing; A unit module, wherein the unit module includes any of the sub-component models, and the unit module is used to generate a test component model based on one of the sub-component models, and the test component model is used to perform unit testing.

2. The model according to claim 1, characterized in that The integrated module and / or the unit module comprises: A subcomponent module, wherein the subcomponent module includes the subcomponent model; A first interface module, comprising an input interface of the subcomponent model; A second interface module, comprising an output interface of the subcomponent model; The target component model and / or the test component model is generated based on the sub-component model, the input interface of the sub-component model, and the output interface of the sub-component model.

3. The model according to claim 2, characterized in that The subcomponent model includes at least one component function, and the component function at least represents the function of the subcomponent model; the integration module and / or the unit module further includes a scheduling module, and the second interface module further includes a communication interface between the component functions; The scheduling module is used to define the scheduling order of the input interface, the output interface and the at least one component function.

4. The model according to claim 3, characterized in that The sub-component model includes a plurality of component functions, each of which corresponds to an execution cycle; The scheduling module is used to define the scheduling order of the input interface, the output interface and each component function in each execution cycle.

5. The model according to claim 1, characterized in that The integration module is also used to export component configuration information of the target component model, and the component configuration information is used to generate software integration code.

6. A software integration system, characterized in that: The software integration system comprises an AUTOSAR tool and a simulink model according to any one of claims 1 to 5; the AUTOSAR tool is used to generate software integration code for software integration based on component configuration information derived from an integration module of the simulink model.

7. A software integration method, characterized in that: The software integration method is applied to the software integration system according to claim 6, and the method comprises: Generate a target component model using a simulink model, and send component configuration information of the target component model to an AUTOSAR tool; Generate software integration code based on the component configuration information using the AUTOSAR tool; Software integration is performed based on the software integration code.

8. The method according to claim 7, characterized in that The component configuration information includes interface information; After sending the component configuration information of the target component model to the AUTOSAR tool, the method further includes: In response to the interface information being updated, the updated interface information is sent to a Simulink model, so that the Simulink model regenerates a target component model based on the updated interface information.

9. An electronic device, characterized in that: include: A memory and a processor, wherein the memory stores program instructions, and the processor retrieves the program instructions from the memory to execute the method according to any one of claims 7-8.

10. A computer-readable storage medium, characterized in that: include: Program data is stored, and when the program data is executed by a processor, it is used to implement the method according to any one of claims 7 to 8.

Images