Software development method and equipment for vehicle lamp controller and medium thereof

By adopting a V-model-based software development method that integrates ASPICE and functional safety based on the development of the headlight controller, automated processing and security analysis, the problems of high development costs, slow progress and high document repetition rate are solved, and efficient and accurate are achieved The development process meets ASPICE and functional safety requirements, reducing development costs and document duplication rates.

CN118916041APending Publication Date: 2024-11-08CHANGZHOU XINGYU AUTOMOTIVE LIGHTING SYST CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411077318.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-07
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In the development of the existing technology, the ASPICE and functional safety requirements need to be met at the same time, resulting in problems such as high development costs, slow progress, high document repetition rate and low efficiency.

Method used

A V-model-based software development method is adopted to automate code writing and security analysis by integrating ASPICE and functional safety requirements, reducing development costs and document duplication rates and improving development efficiency. Specific steps include requirements mining, system development design, software and hardware architecture design, security analysis and tool identification to ensure compliance with ASPICE and functional safety requirements.

Benefits of technology

It greatly reduces the workload of developers and testers, improves development progress and efficiency, ensures the accuracy and consistency of documents, meets the requirements of customers and regulations, and achieves the purpose of cost reduction and efficiency improvement.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118916041A_ABST
    Figure CN118916041A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of automobile controllers, in particular to a software development method for an automobile lamp controller, and the method comprises the steps: carrying out the fusion processing of a system process domain, a software process domain and a hardware process domain based on an Aspice process domain, and obtaining a system development demand design file, a software demand design file and a hardware demand design file; demand design files of system development, software and hardware are obtained, the design files are checked and processed, and a check report is formed; carrying out automatic code writing on the software demand design file according to a preset coding rule; performing security analysis on the demand design files of system development, software and hardware to obtain an analysis result; and acquiring information of the support process domain, and managing and controlling the information of the support process domain. According to the software development method for the vehicle lamp controller, the development cost is reduced, the development progress is fast, the document repetition rate is low, and the efficiency is high.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of automobile controllers, and in particular to a software development method, equipment and medium for a vehicle light controller. Background Art

[0002] ASPICE (Automotive Software Process Improvement and CapabilitydEtermination), as a software development standard for the automotive industry, aims to improve the quality and efficiency of automotive software development. It regulates all aspects of the software development process, including requirements management, design, development, testing, verification, etc. Through comprehensive management and control of these links, it can improve the quality of software development, reduce the software defect rate, and ultimately improve product quality.

[0003] Safety is one of the key elements in the development of future cars. New functions are not only used for assisted driving, but also for dynamic control of vehicles and active safety systems involving safety engineering. The development and integration of these functions will inevitably strengthen the demand for the development process of safety systems, and at the same time, provide evidence for meeting all expected safety purposes. The ISO / PAS21448-2019 Road Vehicles - Draft Standard for Intended Functional Safety issued by the ISO Standards Committee complements the ISO26262 Road Vehicles - Functional Safety Standard.

[0004] At present, for the development of headlight controllers, those that need to meet functional safety requirements are developed in accordance with functional safety requirements, and those that need to meet Aspice requirements are developed in accordance with Aspice requirements. However, for the same headlight controller, there may be a need to meet both functional safety requirements and Aspice requirements. Designers, developers and testers have many complaints about this, and many documents need to be output in duplicate to meet the requirements of two standard systems. In addition, in the process of executing these process requirements, unused automated tools or devices are used for automatic process control and processing, resulting in low efficiency, uncontrolled project development, and unguaranteed delivery quality. Summary of the invention

[0005] The technical problem to be solved by the present invention is: in order to solve the technical problems of high development cost, slow progress, high document duplication rate and low efficiency when the existing Aspice and functional safety requirements coexist in a headlight controller, the present invention provides a software development method for a headlight controller, which reduces the development cost, accelerates the development progress, has a low document duplication rate and high efficiency.

[0006] The technical solution adopted by the present invention to solve the technical problem is: a software development method for a vehicle light controller, the method is based on the V model, and the method specifically includes:

[0007] Based on the Aspice process domain, the system process domain, software process domain and hardware process domain are integrated to obtain the system development requirement design document, software requirement design document and hardware requirement design document;

[0008] Obtain the system development, software and hardware requirement design documents, inspect and process the design documents, and form an inspection report;

[0009] Automatically compile the software requirement design document into code according to pre-set coding rules;

[0010] A security analysis is performed on the system development, software and hardware requirement design documents to obtain analysis results.

[0011] Obtain information about supporting process areas and manage the information about the supporting process areas.

[0012] Further, specifically, the fusion processing of the system process domain includes:

[0013] Demand mining: mining Aspice requirements and functional safety requirements respectively; Aspice requirements include: customer requirements, laws and regulations, and industry dynamics; functional safety requirements include: customer functional safety requirements FSR, historical functional safety issues, and functional safety standards and regulations;

[0014] Analyze the ASpice requirements and functional safety requirements of the system requirements to form the system development and design requirements. The ASpice requirements analysis of the system requirements includes functional requirements, performance requirements, reliability requirements and structural requirements, and the functional safety requirements analysis of the system requirements includes safety mechanisms, safety measures and safety status.

[0015] Design the system development architecture based on the system development design requirements and form a system development requirements design document;

[0016] The system development architecture design includes the system dynamic behavior, static behavior, element interface, system safety architecture design and functional safety-related interface information required by Aspice.

[0017] Further, specifically, the fusion processing of the software process domain includes:

[0018] According to software development matters, software security requirements are added on the basis of original software requirements, and the requirements of the technical security requirements at the system level are assigned to the software elements to form software design requirements;

[0019] Design software architecture based on software design requirements and form software requirement design documents;

[0020] Among them, the software requirement design document includes the software security architecture design and the design of the security mechanism at the software level.

[0021] Further, specifically, the fusion processing of the hardware process domain includes:

[0022] According to hardware development matters, hardware security requirements are added on the basis of the original hardware requirements, and the requirements of the technical security requirements at the system level are assigned to the hardware elements to form hardware design requirements;

[0023] Perform hardware architecture design based on hardware design requirements and form hardware requirement design documents;

[0024] The hardware requirement design document includes the hardware architecture design and the design of the hardware-level security mechanism.

[0025] Further, specifically, the safety analysis includes: qualitative analysis of fault trees at each level, hardware quantitative analysis FTA, related failure analysis DFA at each level, safety FMEA analysis at each level, and quantitative FMEDA analysis;

[0026] By automatically analyzing whether each analysis object violates the safety goal under different failure modes, and combining the safety measures given in each requirement design document, analyzing whether there are related failures, and outputting the results, automatically forming analysis reports at all levels of safety analysis;

[0027] If the analysis result fails, improvement measures will be given in the analysis report. The improvement measures will be introduced into the design of each layer and the safety analysis will be performed again until the safety analysis result shows that it passes.

[0028] Further, specifically, the supporting process domain information includes:

[0029] Configuration management: adding configuration management activities for functional safety configuration items;

[0030] Problem management, to increase the management of problems in the functional safety development process;

[0031] Change management, adding change management for functional safety related items;

[0032] Product release: Add description of functional safety related items;

[0033] Tool qualification and evaluation, functional safety specific activities, are performed separately.

[0034] Further, specifically, obtaining information of the support process domain and managing the information of the support process domain specifically includes: managing the information of the support process domain, using the support process device to identify and evaluate the tool, and uniformly managing the problem management, configuration management and change management, and the support process device checks and analyzes the information of the support process domain to ensure compliance with the requirements of functional safety and Aspice;

[0035] When the inspection result shows that it has passed, the process ends. When the inspection result shows that it has failed, the process returns to solve the problem and then enters the support process processing device again until the result shows that it has passed. At this point, the product release process can be carried out.

[0036] Further, specifically, checking the design file includes checking the correctness, completeness and consistency.

[0037] A computer device comprising:

[0038] processor;

[0039] A memory for storing executable instructions;

[0040] The processor is used to read the executable instructions from the memory and execute the executable instructions to implement the software development method for the vehicle light controller as described above.

[0041] A computer-readable storage medium stores a computer program. When the computer program is executed by a processor, the processor implements the software development method for a vehicle light controller as described above.

[0042] The beneficial effect of the present invention is that a software development method for a vehicle light controller of the present invention integrates ASpice and functional safety, greatly reduces the workload of developers and testers, has a fast development progress, low document duplication, high efficiency, and fully and accurately meets ASpice and functional safety requirements, thereby meeting customer or regulatory requirements and having the purpose of reducing costs and increasing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The present invention is further described below in conjunction with the accompanying drawings and embodiments.

[0044] Figure 1 It is a schematic diagram of the method flow of embodiment 1 of the present invention.

[0045] Figure 2 It is a schematic diagram of the computer device structure of the second embodiment of the present invention.

[0046] In the figure, 10 is a computer device; 1002 is a processor; 1004 is a memory; and 1006 is a transmission device. DETAILED DESCRIPTION

[0047] The present invention will now be described in further detail with reference to the accompanying drawings. These drawings are simplified schematic diagrams, which only illustrate the basic structure of the present invention in a schematic manner, and therefore only show the components related to the present invention.

[0048] In the description of the present invention, it should be understood that the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside", "clockwise", "counterclockwise", "axial", "radial", "circumferential" and the like indicate positions or positional relationships based on the positions or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present invention. In addition, features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the present invention, unless otherwise specified, "multiple" means two or more.

[0049] In the description of the present invention, it should be noted that, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0050] Example 1

[0051] The embodiment of the present application provides a software development method for a vehicle light controller. The method is based on the V model and specifically includes:

[0052] Based on the Aspice process domain, the system process domain, software process domain and hardware process domain are integrated to obtain the system development requirement design document, software requirement design document and hardware requirement design document;

[0053] Obtain the system development, software and hardware requirement design documents, check and process the design documents, and form an inspection report;

[0054] Automatically compile software requirement design documents according to pre-set coding rules; avoid large-scale manual code writing, improve software development efficiency, shorten software development cycle, and enable developers to focus more on software requirements and design;

[0055] Conduct security analysis on system development, software and hardware requirement design documents and obtain analysis results.

[0056] Obtain information from supporting process areas and manage information from supporting process areas.

[0057] In an embodiment, the fusion processing of the system process domain includes:

[0058] Demand mining: mining Aspice requirements and functional safety requirements respectively; Aspice requirements include: customer requirements, laws and regulations, and industry dynamics; functional safety requirements include: customer functional safety requirements FSR, historical functional safety issues, and functional safety standards and regulations;

[0059] Analyze the ASpice requirements and functional safety requirements of the system requirements to form the system development and design requirements. The ASpice requirements analysis of the system requirements includes functional requirements, performance requirements, reliability requirements and structural requirements, and the functional safety requirements analysis of the system requirements includes safety mechanisms, safety measures and safety status.

[0060] Based on the system development and design requirements, the system development architecture design is carried out to form a system development requirement design document; among which, the system development architecture design includes the system dynamic behavior, static behavior, element interface, system safety architecture design and functional safety-related interface information required by Aspice.

[0061] In an embodiment, the fusion processing of the software process domain includes:

[0062] According to software development matters, software security requirements are added on the basis of original software requirements, and the requirements of the technical security requirements at the system level are assigned to the software elements to form software design requirements;

[0063] Design software architecture based on software design requirements and form software requirement design documents;

[0064] Among them, the software requirement design document includes the software security architecture design and the design of security mechanisms at the software level.

[0065] In addition, the fusion processing of the software process domain also includes the detailed design of the software, adding software security components, such as the design of security mechanisms, and behavioral monitoring of existing software components.

[0066] In an embodiment, the fusion processing of the hardware process domain includes:

[0067] According to hardware development matters, hardware security requirements are added on the basis of the original hardware requirements, and the requirements of the technical security requirements at the system level are assigned to the hardware elements to form hardware design requirements;

[0068] Perform hardware architecture design based on hardware design requirements and form hardware requirement design documents;

[0069] Among them, the hardware requirement design document includes the hardware architecture design and the design of the hardware-level security mechanism.

[0070] In an embodiment, the safety analysis includes: qualitative fault tree analysis at each level, hardware quantitative analysis FTA, dependent failure analysis DFA at each level, safety FMEA analysis at each level, and quantitative FMEDA analysis.

[0071] For example, FMEA analysis and related failure DFA analysis are performed at the system architecture level for the functional safety system; FMEA and related failure DFA analysis are performed at the software architecture level for software components; FMEA analysis of hardware components and FMEDA analysis of hardware components are performed at the hardware design level, etc. By automatically analyzing whether each analysis object violates the safety goal under different failure modes, and combining the safety measures given in each requirement design document, analyzing whether relevant failures are covered, and outputting the results, analysis reports at each level of safety analysis are automatically formed;

[0072] If the analysis result fails, improvement measures will be given in the analysis report, and the improvement measures will be introduced into the design of each layer, and the safety analysis will be carried out again until the safety analysis result shows passing.

[0073] In an embodiment, the supporting process domain information includes:

[0074] Configuration management: adding configuration management activities for functional safety configuration items;

[0075] Problem management, to increase the management of problems in the functional safety development process;

[0076] Change management, adding change management for functional safety related items;

[0077] Product release: Add description of functional safety related items;

[0078] Tool qualification and evaluation, functional safety specific activities, are performed separately.

[0079] In an embodiment, obtaining information of a support process domain and managing the information of the support process domain specifically includes: managing the information of the support process domain, using a support process device to identify and evaluate tools, and uniformly managing problem management, configuration management, and change management, and the support process device checks and analyzes the information of the support process domain to ensure compliance with functional safety and Aspice requirements;

[0080] When the inspection result shows that it has passed, the process ends. When the inspection result shows that it has failed, the process returns to solve the problem and then enters the support process processing device again until the result shows that it has passed. At this point, the product release process can be carried out.

[0081] In an embodiment, the design file is checked for correctness, completeness and consistency. In some embodiments, the design file that passes the check is also subject to verification testing, and test and verification cases are automatically generated. Automated testing is performed and test verification results are output. When the test verification results show that they pass, the process is terminated. When the results show that they fail, the process returns to the starting point, proposes new requirements or improves the existing design to re-execute the process.

[0082] Furthermore, verification testing includes verification testing of system development requirements design documents, software requirements design documents and hardware requirements design documents; verification testing of system development requirements design documents includes adding functional safety interfaces to system integration verification activities, verification of integration testing of system functional safety elements, and adding fault injection testing and review verification of technical safety requirements. Software requirements design document verification testing includes: adding verification activities for safety components, performing static and dynamic testing; adding verification activities for software safety architecture, software FMEA and DFA; adding verification activities for software safety requirements, and verifying software safety requirements through fault injection. Hardware requirements design document verification testing includes: adding verification of hardware safety design, hardware FMEA and FMEDA verification activities; adding verification activities for hardware safety requirements, and verifying hardware safety requirements through fault injection.

[0083] In summary, the software development method for a vehicle light controller of the present invention integrates ASpice and functional safety, greatly reduces the workload of developers and testers, has a fast development progress, low document duplication, high efficiency, and fully and accurately meets ASpice and functional safety requirements, thereby meeting customer or regulatory requirements and achieving the purpose of reducing costs and increasing efficiency.

[0084] Example 2

[0085] An embodiment of the present application provides a computer device, which includes a processor and a memory, wherein the memory stores at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by the processor to implement a software development method for a vehicle light controller as provided in the above method embodiment.

[0086] Figure 2The hardware structure diagram of a device for implementing a software development method for a vehicle light controller provided in an embodiment of the present application is shown. The device may participate in constituting or include the apparatus or system provided in an embodiment of the present application. Figure 2 As shown, the computer device 10 may include one or more processors 1002 (the processor may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 1004 for storing data, and a transmission device 1006 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 2 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 2 More or fewer components as shown, or with Figure 2 Different configurations are shown.

[0087] It should be noted that the one or more processors and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer device 10 (or mobile device). As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0088] The memory 1004 can be used to store software programs and modules of application software, such as a program instruction / data storage device corresponding to a software development method for a vehicle light controller in an embodiment of the present application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory 1004, that is, implementing the above-mentioned method. The memory 1004 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 1004 may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the computer device 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0089] The transmission device 1006 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer device 10. In one example, the transmission device 1006 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 1006 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0090] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer device 10 (or mobile device).

[0091] Example 3

[0092] An embodiment of the present application also provides a computer-readable storage medium, which can be set in a server to store at least one instruction or at least one program related to a software development method for a vehicle light controller in a method embodiment. The at least one instruction or the at least one program is loaded and executed by the processor to implement a software development method for a vehicle light controller provided in the above method embodiment.

[0093] Optionally, in this embodiment, the storage medium may be located in at least one of the multiple network servers of the computer network. Optionally, in this embodiment, the storage medium may include, but is not limited to, various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0094] Example 4

[0095] The embodiment of the present invention further provides a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes a software development method for a vehicle light controller provided in the above various optional embodiments.

[0096] It should be noted that the above-mentioned sequence of the embodiments of the present application is for description only and does not represent the advantages and disadvantages of the embodiments. The above-mentioned specific embodiments of the present application are described. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0097] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, equipment and storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0098] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0099] Based on the above ideal embodiments of the present invention, the relevant staff can make various changes and modifications without departing from the technical concept of the present invention through the above description. The technical scope of the present invention is not limited to the contents of the specification, and its technical scope must be determined according to the scope of the claims.

Claims

1. A software development method for a vehicle light controller, characterized in that: The method is based on the V model and specifically includes: Based on the Aspice process domain, the system process domain, software process domain and hardware process domain are integrated to obtain the system development requirement design document, software requirement design document and hardware requirement design document; Obtain the system development, software and hardware requirement design documents, inspect and process the design documents, and form an inspection report; Automatically compile the software requirement design document into code according to pre-set coding rules; Conduct security analysis on the system development, software and hardware requirement design documents to obtain analysis results; Obtain information about supporting process areas and manage the information about the supporting process areas.

2. The software development method for a vehicle light controller according to claim 1, characterized in that: The integration processing of the system process domain includes: Demand mining: mining Aspice demand and functional safety demand respectively; Aspice demand includes: customer demand, laws and regulations, and industry dynamics information; functional safety demand includes: customer functional safety requirements FSR, historical functional safety issues, functional safety standards and regulations; Analyze the ASpice requirements and functional safety requirements of system requirements to form system development and design requirements. The ASpice requirements analysis of system requirements includes functional requirements, performance requirements, reliability requirements and structural requirements, and the functional safety requirements analysis of system requirements includes safety mechanisms, safety measures and safety status. Design the system development architecture based on the system development design requirements and form a system development requirements design document; The system development architecture design includes the system dynamic behavior, static behavior, element interface, system safety architecture design and functional safety-related interface information required by Aspice.

3. The software development method for a vehicle light controller according to claim 1, characterized in that: The fusion processing of the software process domain includes: According to software development matters, software security requirements are added on the basis of original software requirements, and the requirements of the technical security requirements at the system level are assigned to the software elements to form software design requirements; Design software architecture based on software design requirements and form software requirement design documents; Among them, the software requirement design document includes the design of software security architecture and the design of security mechanism at the software level.

4. The software development method for a vehicle light controller according to claim 1, characterized in that: The fusion processing of the hardware process domain includes: According to hardware development matters, hardware security requirements are added on the basis of the original hardware requirements, and the requirements of the technical security requirements at the system level are allocated to the hardware elements to form hardware design requirements; Perform hardware architecture design based on hardware design requirements and form hardware requirement design documents; The hardware requirement design document includes: hardware architecture design and hardware-level security mechanism design.

5. The software development method for a vehicle light controller according to claim 1, characterized in that: The safety analysis includes: qualitative analysis of fault trees at each level, hardware quantitative analysis FTA, related failure analysis DFA at each level, safety FMEA analysis at each level and quantitative FMEDA analysis; By automatically analyzing whether each analysis object violates the safety goal under different failure modes, and combining the safety measures given in each requirement design document, analyzing whether there are related failures, and outputting the results, automatically forming analysis reports at all levels of safety analysis; If the analysis result fails, improvement measures will be given in the analysis report. The improvement measures will be introduced into the design of each layer and the safety analysis will be performed again until the safety analysis result shows passing.

6. The software development method for a vehicle light controller according to claim 1, characterized in that: The information supporting the process areas includes: Configuration management: adding configuration management activities for functional safety configuration items; Problem management, to increase the management of problems in the functional safety development process; Change management, adding change management for functional safety related items; Product release: Add description of functional safety related items; Tool qualification and evaluation, functional safety specific activities, are performed separately.

7. The software development method for a vehicle light controller according to claim 6, characterized in that: Acquire information of the support process domain and manage the information of the support process domain. Specifically include: manage the information of the support process domain, use the support process device to identify and evaluate the tools, and manage the problem management, configuration management and change management in a unified manner. The support process device checks and analyzes the information of the support process domain to ensure compliance with the requirements of functional safety and Aspice; When the inspection result shows that it has passed, the process ends. When the inspection result shows that it has failed, the process returns to solve the problem and then enters the support process processing device again until the result shows that it has passed. At this point, the product release process can be carried out.

8. The software development method for a vehicle light controller according to claim 1, characterized in that: Checking the design files includes checking the correctness, completeness and consistency.

9. A computer device, characterized in that: include: processor; A memory for storing executable instructions; The processor is used to read the executable instructions from the memory and execute the executable instructions to implement the software development method for a vehicle light controller as described in any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processor implements the software development method for a vehicle light controller according to any one of claims 1 to 8.