Software development methods, devices, equipment, media, and computer programs for turn signals

Abstract

The application relates to the technical field of software design, in particular to a software development method and device for a turn signal, equipment, medium and computer program, wherein the method comprises the following steps: acquiring a plurality of function scenes of a turn signal; establishing a software component of each function scene in the plurality of function scenes, generating a software framework of the turn signal based on the software component; and completing mapping of a corresponding interface of the software component in the software framework to obtain development software of the turn signal. Therefore, the problems that a software architecture and a development mode in the related art cannot adapt to complex function requirements, and that software development is difficult to maintain and high in cost in the later stage are solved.

Description

Technical Field

[0001] This application relates to the field of software design technology, and in particular to a software development method, apparatus, device, medium and computer program for a turn signal. Background Technology

[0002] With the expansion of automotive functions and the improvement of performance, as well as the increase in some non-functional requirements, traditional software architecture and development models can no longer meet the increasingly complex automotive software needs.

[0003] As a crucial module in vehicle electronics, turn signals are used in numerous scenarios and involve complex interactions. Their software components are highly coupled, and their application programming interfaces (APIs) are unclear, leading to difficulties in software development and maintenance. Therefore, improving the efficiency of turn signal software development is a pressing technical problem that needs to be addressed by those skilled in the art. Summary of the Invention

[0004] This application provides a software development method, apparatus, device, medium, and computer program for turn signals, in order to solve the problems that the software architecture and development model in related technologies cannot adapt to complex functional requirements, resulting in high difficulty and cost of later software maintenance.

[0005] The first aspect of this application provides a software development method for a turn signal, comprising the following steps: obtaining multiple functional scenarios of the turn signal; establishing software components for each functional scenario in the multiple functional scenarios; generating a software framework for the turn signal based on the software components; and completing the mapping of the corresponding interfaces of the software components in the software framework to obtain the development software for the turn signal.

[0006] Optionally, in one embodiment of this application, the software framework for generating turn signals based on software components includes: defining target information for each software component; generating a target interface file based on the target information; and importing the target file into a visualization simulation tool to generate the software framework for turn signals.

[0007] Optionally, in one embodiment of this application, the target information includes one or more of the following: docking port, first interface, second interface, data type, and running entity.

[0008] Optionally, in one embodiment of this application, generating a target interface file based on target information includes: identifying a first interface and a second interface for each software component; and running the first interface and the second interface into the runtime entity corresponding to the software component to obtain the target interface file.

[0009] Optionally, in one embodiment of this application, after obtaining the software development of the turn signal, the method further includes: developing a turn signal model using a visual simulation tool; establishing a test project based on the turn signal model; and using the test project to perform simulation testing on the development software of the turn signal.

[0010] A second aspect of this application provides a software development apparatus for a turn signal, comprising: an acquisition module for acquiring multiple functional scenarios of the turn signal; an establishment module for establishing software components for each functional scenario and generating a software framework for the turn signal based on the software components; and a mapping module for mapping the corresponding interfaces of the software components within the software framework to obtain the development software for the turn signal.

[0011] Optionally, in one embodiment of this application, the establishment module is further used to define the target information of each software component; generate a target interface file based on the target information; and import the target file into a visualization simulation tool to generate the software framework for the turn signal.

[0012] Optionally, in one embodiment of this application, the target information includes one or more of the following: docking port, first interface, second interface, data type, and running entity.

[0013] Optionally, in one embodiment of this application, the establishment module is further used to identify the first interface and the second interface of each software component; and to run the first interface and the second interface into the running entity corresponding to the software component to obtain the target interface file.

[0014] Optionally, in one embodiment of this application, the turn signal software development apparatus further includes: a testing module, used to develop a turn signal model using a visual simulation tool after obtaining the turn signal development software; to establish a test project based on the turn signal model; and to perform simulation testing on the turn signal development software using the test project.

[0015] A third aspect of this application provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to perform the software development method for a turn signal as described in the above embodiments.

[0016] A fourth aspect of this application provides a computer-readable storage medium having a computer program stored thereon, which is executed by a processor to perform the software development method for a turn signal as described in the above embodiments.

[0017] A fifth aspect of this application provides a computer program that, when executed, is used to implement the software development method for turn signals as described in the above embodiments.

[0018] Therefore, this application has at least the following beneficial effects:

[0019] This application's embodiments achieve multi-scenario decoupling by establishing software components for each functional scenario of the turn signal, facilitating development and maintenance. Furthermore, the mapping of corresponding interfaces for these software components within the software framework standardizes these interfaces, reducing the difficulty of later software maintenance and lowering development complexity. This solves the problems in related technologies where software architectures and development models cannot adapt to complex functional requirements, leading to high maintenance difficulty and costs in later software development.

[0020] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0021] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0022] Figure 1 This is a flowchart illustrating a software development method for a turn signal according to an embodiment of this application;

[0023] Figure 2 This is an example diagram of a software component provided according to an embodiment of this application;

[0024] Figure 3 This is an example diagram of the turn signal application layer software structure according to an embodiment of this application;

[0025] Figure 4 This is a schematic diagram illustrating the software development and testing of a turn signal according to an embodiment of this application;

[0026] Figure 5 This is an example diagram of a software development apparatus for a turn signal according to an embodiment of this application;

[0027] Figure 6 This is a schematic diagram of the structure of an electronic device provided according to an embodiment of this application. Detailed Implementation

[0028] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0029] The following description, with reference to the accompanying drawings, outlines a software development method, apparatus, electronic device, storage medium, and computer program for turn signals according to embodiments of this application. Addressing the problems mentioned in the background section, this application provides a software development method for turn signals. In this method, by establishing software components for each functional scenario of the turn signal, multi-scenario decoupling is achieved, facilitating development and maintenance. Furthermore, the mapping of corresponding interfaces for software components is completed within the software framework, and standardized interfaces reduce the difficulty of later software maintenance while lowering development complexity. This solves the problems in related technologies where software architecture and development models cannot adapt to complex functional requirements, leading to high maintenance difficulty and costs in later software development.

[0030] Specifically, Figure 1 This is a flowchart illustrating a software development method for a turn signal provided in an embodiment of this application.

[0031] like Figure 1 As shown, the software development method for this turn signal includes the following steps:

[0032] In step S101, multiple functional scenarios of the turn signal are obtained.

[0033] The functional scenarios may include: lane changing, collision warning, emergency braking, vehicle location prompt, etc.

[0034] In step S102, software components for each functional scenario in multiple functional scenarios are established, and the software framework for the turn signal is generated based on the software components.

[0035] It is understood that the embodiments of this application can refine the complex software logic by splitting the turn signal sub-function scenarios, thereby achieving multi-scenario decoupling, facilitating development and maintenance, and treating each scenario as a different SWC (Software Component). The SWC, as a collection of detailed requirements, can unify the structure of each application scenario by defining standardized service interfaces.

[0036] In one embodiment of this application, a software framework for generating turn signals based on software components includes: defining target information for each software component; generating a target interface file based on the target information; and importing the target file into a visualization simulation tool to generate the software framework for turn signals.

[0037] The target information includes one or more of the following: docking port, first interface, second interface, data type, and running entity.

[0038] In the embodiments of this application, software components (SWCs) can be broadly divided into Atomic SWCs and Composition SWCs. Generally, a Composition SWC can contain several Atomic SWCs. For example... Figure 2 As shown, this demonstrates the basic elements of a software component, including a running entity, a docking port, an interface, and internal runnable variables. It can serve as a basic example for Atomic SWC development. Composition SWC can integrate multiple Atomic SWCs, and the interactive interface can automatically connect them.

[0039] In one embodiment of this application, generating a target interface file based on target information includes: identifying a first interface and a second interface for each software component; and running the first interface and the second interface into the runtime entity corresponding to the software component to obtain the target interface file.

[0040] The first interface can be a CS interface, and the second interface can be an SR interface.

[0041] It is understood that, in the embodiments of this application, a triggering event time (e.g., 10ms) period can be added to each running entity; the CS interface and SR interface required for each scenario can be put into the running entity to obtain the target interface file.

[0042] Furthermore, in this embodiment of the application, the internal algorithm is implemented by importing the target interface file of the software component into a visualization tool (such as Matlab / Simulink), and then Matlab / Simulink is used to generate code and description file arxml that conform to the specification.

[0043] In step S103, the mapping of the corresponding interfaces of the software components is completed in the software framework to obtain the development software for the turn signals.

[0044] In this embodiment of the application, the corresponding interface is the first interface, namely the CS interface in the above embodiment.

[0045] The embodiments of this application can complete the CS interface mapping in the software framework by setting solver configuration specifications, including discretization settings, step size settings, and language settings. The standardized interface design reduces the difficulty of later software maintenance.

[0046] Furthermore, each scene is subdivided into different software components. Within each software component, only the interfaces required for that scene are added. Different software components represent different trigger sources and corresponding scene effects, such as... Figure 3 As shown, when a new scene is triggered, whether the current turn signal scene can be interrupted or overridden needs to be determined by priority judgment. Finally, the command for that scene is issued and the actual turn signal effect is output.

[0047] In one embodiment of this application, after obtaining the software development of the turn signal, the method further includes: developing a turn signal model using a visualization simulation tool; establishing a test project based on the turn signal model; and using the test project to perform dynamic simulation testing on the visualization framework.

[0048] This application embodiment can use Simulink / Stateflow to complete model development, establish a Simulink Test project based on the model, and perform software testing. For multi-model software frameworks under scenario-based development modes, the following steps are required: introducing a Model Reference framework; creating a Test Harness model; writing test cases using Test Sequences; and using the test cases to verify the turn signal software development, which greatly improves software testing efficiency, while reducing development costs and saving resources.

[0049] Furthermore, in this embodiment of the application, the CS call status of each software component can be viewed in the viewer of the visualization simulation tool, thus achieving visualized dynamic simulation.

[0050] The following is combined with Figure 4 The software development method for turn signals according to embodiments of this application will be described in detail, including the following steps:

[0051] Step 1: Decompose the sub-functional scenarios of the turn signal;

[0052] Step 2: For each scenario, treat it as a different software component and place the required CS interface and SR interface into the running entity;

[0053] Step 3: Complete the software component framework design and import the arxml file;

[0054] Step 4: Complete the CS interface mapping in the Simulink framework and use Simulink / Stateflow to complete the model development;

[0055] Step 5: Create a SimulinkTest test project.

[0056] The software development method for turn signals proposed in this application establishes software components for each functional scenario of the turn signal, thereby decoupling multiple scenarios, facilitating development and maintenance. Furthermore, the mapping of corresponding interfaces for software components is completed within the software framework, and standardized interfaces reduce the difficulty of later software maintenance while lowering development complexity. This solves the problems in related technologies where software architecture and development models cannot adapt to complex functional requirements, leading to high maintenance difficulty and costs in the later stages of software development.

[0057] Next, the software development apparatus for turn signals according to embodiments of this application is described with reference to the accompanying drawings.

[0058] Figure 5 This is a block diagram of a software development device for a turn signal according to an embodiment of this application.

[0059] like Figure 5 As shown, the software development device 10 for the turn signal includes: an acquisition module 100, a creation module 200, and a mapping module 300.

[0060] The acquisition module 100 is used to acquire multiple functional scenarios of the turn signal; the establishment module 200 is used to establish software components for each functional scenario in the multiple functional scenarios, and generate the software framework of the turn signal based on the software components; the mapping module 300 is used to complete the mapping of the corresponding interfaces of the software components in the software framework to obtain the development software of the turn signal.

[0061] In one embodiment of this application, the establishment module 200 is further used to define target information for each software component; generate a target interface file based on the target information; and import the target file into a visualization simulation tool to generate the software framework for the turn signal.

[0062] In one embodiment of this application, the target information includes one or more of the following: docking port, first interface, second interface, data type, and running entity.

[0063] In one embodiment of this application, the establishment module 200 is further used to identify the first interface and the second interface of each software component; and to run the first interface and the second interface into the running entity corresponding to the software component to obtain the target interface file.

[0064] In one embodiment of this application, the turn signal software development apparatus 10 further includes: a testing module, used to develop a turn signal model using a visual simulation tool after obtaining the turn signal development software; to establish a test project based on the turn signal model; and to perform simulation testing on the turn signal development software using the test project.

[0065] It should be noted that the foregoing explanation of the software development method embodiment for turn signals also applies to the software development device for turn signals in this embodiment, and will not be repeated here.

[0066] The turn signal software development apparatus proposed in this application, by establishing software components for each functional scenario of the turn signal, achieves multi-scenario decoupling, facilitating development and maintenance. Furthermore, the mapping of corresponding interfaces for software components is completed within the software framework, and standardized interfaces reduce the difficulty of later software maintenance while lowering development complexity. This solves the problems in related technologies where software architecture and development models cannot adapt to complex functional requirements, leading to high maintenance difficulty and costs in later software development.

[0067] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device may include:

[0068] The memory 601, the processor 602, and the computer program stored on the memory 601 and capable of running on the processor 602.

[0069] When the processor 602 executes the program, it implements the software development method for the turn signal provided in the above embodiments.

[0070] Furthermore, electronic devices also include:

[0071] Communication interface 603 is used for communication between memory 601 and processor 602.

[0072] The memory 601 is used to store computer programs that can run on the processor 602.

[0073] The memory 601 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0074] If the memory 601, processor 602, and communication interface 603 are implemented independently, then the communication interface 603, memory 601, and processor 602 can be interconnected via a bus to complete communication between them. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 6 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0075] Optionally, in a specific implementation, if the memory 601, processor 602, and communication interface 603 are integrated on a single chip, then the memory 601, processor 602, and communication interface 603 can communicate with each other through an internal interface.

[0076] The processor 602 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0077] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the software development method for the turn signal as described above.

[0078] This application also provides a computer program, which, when executed, is used to implement the software development method for turn signals as described in the above embodiments.

[0079] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0080] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0081] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0082] It should be understood that the various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or more of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0083] Those skilled in the art will understand that all or part of the steps of the methods described in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it includes one or a combination of the steps of the method embodiments.

Claims

1. A software development method for a turn signal, characterized by, The method comprises the following steps: obtaining a plurality of function scenes of a turn signal; establishing a software component of each function scene in the plurality of function scenes, and generating a software framework of the turn signal based on the software component; completing mapping of a corresponding interface of the software component in the software framework to obtain development software of the turn signal; the generating of the software framework of the turn signal based on the software component comprises: defining target information of each software component, wherein the target information comprises one or more of a docking port, a first interface, a second interface, a data type and a running entity; generating a target interface file according to the target information; and importing the target interface file into a visual simulation tool to generate the software framework of the turn signal; the generating of the target interface file according to the target information comprises: identifying the first interface and the second interface of each software component; and running the first interface and the second interface into a corresponding running entity of the software component to obtain the target interface file.

2. The software development method for a turn signal according to claim 1, characterized in that, After the development software of the turn signal is obtained, the method further comprises: developing a turn signal model by using the visual simulation tool; establishing a test project according to the turn signal model, and performing simulation testing on the development software of the turn signal by using the test project.

3. A software development device for a turn signal, characterized by The method comprises: an obtaining module configured to obtain a plurality of function scenes of a turn signal; an establishing module configured to establish a software component of each function scene in the plurality of function scenes, and generate a software framework of the turn signal based on the software component; a mapping module configured to complete mapping of a corresponding interface of the software component in the software framework to obtain development software of the turn signal; the establishing module is further configured to define target information of each software component, wherein the target information comprises one or more of a docking port, a first interface, a second interface, a data type and a running entity; generate a target interface file according to the target information; and import the target interface file into a visual simulation tool to generate the software framework of the turn signal; the establishing module is further configured to identify the first interface and the second interface of each software component; and run the first interface and the second interface into a corresponding running entity of the software component to obtain the target interface file.

4. An electronic device, comprising: The method comprises: a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the software development method of the turn signal according to claim 1 or 2.

5. A computer-readable storage medium having stored thereon a computer program, characterized in that, The program is executed by the processor to implement the software development method of the turn signal according to claim 1 or 2.

6. A computer program product, characterised in that, The computer program is executed to implement the software development method of the turn signal according to claim 1 or 2.

Images