Vehicle-mounted controller software research and development management method, device, equipment and medium

By building a software R&D management system based on existing workbenches and auxiliary tools, the problem of high R&D costs when complying with ASPICE standards is solved, and effective management and quality improvement of vehicle controller software is achieved.

CN119718257AActive Publication Date: 2025-03-28VOYAH AUTOMOBILE TECH CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
CN202411613497.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-11-13
Publication Date
2025-03-28
Estimated Expiration
2044-11-13

AI Technical Summary

Technical Problem

In the process of developing on-board controller software, following the ASPICE standard requires the use of a variety of professional tools, resulting in high R&D costs.

Method used

By obtaining project planning information, filtering software requirements, and based on preset ASPICE standards, we determine the core workbench and target auxiliary tools from existing workbenches and auxiliary tools, build a software R&D management system, and manage the software R&D process to meet ASPICE needs.

Benefits of technology

Reduces the costs incurred by the development of on-board controller software to comply with the ASPICE standards, avoids the need for professional tools, purchase licenses and configure professionals, and improves product development quality.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119718257A_ABST
    Figure CN119718257A_ABST
Patent Text Reader

Abstract

The invention discloses a vehicle-mounted controller software research and development management method and device, equipment and a medium. The method comprises the steps that software requirements corresponding to a vehicle-mounted controller to be researched and developed are screened out from project plan information; according to a software demand and an ASI CE demand, determining a core workbench from a plurality of existing to-be-selected workbenches, and determining a plurality of target auxiliary tools from a plurality of existing to-be-selected auxiliary tools; constructing a software research and development management system according to the core workbench and the multiple target auxiliary tools; and based on the software research and development management system, carrying out research and development management on the research and development process of the software requirement corresponding to the vehicle-mounted controller to be researched and developed, so as to meet the preset automobile software process improvement and capability evaluation standard requirements. According to the method, on the premise of meeting the ASI CE requirement, complete software requirement management is carried out on a software research and development product of the vehicle-mounted controller in the life cycle of the software research and development product, and the cost of purchasing research and development management tools by an enterprise is greatly reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

[0002] As the automotive industry's requirements for software quality increase, ASPICE (Automotive Software Process Improvement and Capacity dEtermination) has become an important standard for evaluating the maturity and capability of automotive software processes. In the automotive software development process, the ASPICE standard provides a comprehensive set of software process improvement and capability determination guidelines.

[0003] However, in the process of developing vehicle controller software, following the ASPICE standard often requires the use of a variety of development and management tools to support various stages such as demand management, analysis, design, implementation, testing and verification. These tools require professional training, need to purchase licenses, and incur corresponding maintenance costs. They require professional system configuration personnel and are difficult to use, resulting in high development costs for vehicle controllers. Therefore, how to reduce the development costs of vehicle controller software in order to follow the ASPICE standard is an issue that needs to be solved urgently. Summary of the invention

[0004] The embodiments of the present application provide a method, device, equipment and medium for managing the development of vehicle-mounted controller software, thereby solving the technical problem that in the prior art, in order to comply with the ASPICE standard, professional tools need to be used, licenses need to be purchased, maintenance costs need to be incurred and professional personnel need to be deployed, resulting in high development costs for the vehicle-mounted controller. The embodiments of the present application achieve the technical effect of managing the software development process of the vehicle-mounted controller by using existing workbenches and existing tools, thereby reducing the development costs of the vehicle-mounted controller software incurred in complying with the ASPICE standard.

[0005] In a first aspect, the present application provides a vehicle controller software development management method, the method comprising:

[0006] Obtain project plan information for vehicle controllers to be developed;

[0007] Filtering out software requirements corresponding to the vehicle controller to be developed from the project plan information;

[0008] According to the software requirements and the preset automotive software process improvement and capability assessment standard requirements, a core workbench for managing the software development process is determined from a plurality of existing workbenches to be selected, and a plurality of target auxiliary tools for realizing the software requirements are determined from a plurality of existing auxiliary tools to be selected;

[0009] Constructing a software development management system based on the core workbench and a plurality of target auxiliary tools;

[0010] Based on the software R&D management system, the R&D process of the software requirements corresponding to the on-board controller to be developed is managed to meet the preset automotive software process improvement and capability assessment standard requirements.

[0011] Furthermore, the filtering out software requirements corresponding to the vehicle controller to be developed from the project plan information includes:

[0012] Decomposing the project plan information to obtain software requirements;

[0013] Classifying the software requirements according to functional types to obtain multiple software functional requirements;

[0014] Dividing each of the software functional requirements according to functional granularity to obtain a plurality of software component requirements corresponding to each of the software functional requirements;

[0015] The software requirements corresponding to the vehicle-mounted controller to be developed include a plurality of software component requirements corresponding to each of the software function requirements.

[0016] Further, the determining of a core workbench for managing the software development process from a plurality of existing workbenches to be selected, and determining a plurality of target auxiliary tools for realizing the software requirements from a plurality of existing auxiliary tools to be selected, according to the software requirements and the preset automotive software process improvement and capability assessment standard requirements, includes:

[0017] According to the software requirements and the preset automotive software process improvement and capability assessment standard requirements, a workbench that covers the software requirements and the preset automotive software process improvement and capability assessment standard requirements to the greatest extent is selected from a plurality of existing workbenches to be selected as the core workbench for managing the software development process;

[0018] According to the software requirements and the preset automotive software process improvement and capability assessment standard requirements, auxiliary tools that meet the software requirements and the preset automotive software process improvement and capability assessment standard requirements are selected from multiple existing auxiliary tools to be selected as multiple target auxiliary tools for realizing the software requirements.

[0019] Furthermore, the software development management system is constructed based on the core workbench and the plurality of target auxiliary tools, including:

[0020] Through an application programming interface or a plug-in, a connection is established between the core workbench and each of the target auxiliary tools, so that data and functions are shared between the core workbench and each of the target auxiliary tools to obtain the software development management system.

[0021] Furthermore, the software development management system is constructed based on the core workbench and the plurality of target auxiliary tools, including:

[0022] Determining a target data format and a target interface standard according to the data formats and interface standards respectively corresponding to each of the target auxiliary tools;

[0023] Establishing, on the core workbench, a format conversion relationship between the data formats corresponding to the target auxiliary tools and the target data formats, and establishing, on the core workbench, an interface conversion relationship between the interface standards corresponding to the target auxiliary tools and the target interface standards;

[0024] Each of the target auxiliary tools obtains the software development and management system with data function sharing based on the format conversion relationship and the interface conversion relationship of the core workbench.

[0025] Furthermore, based on the software development management system, the development process of the software requirements corresponding to the vehicle controller to be developed is managed to meet the preset automotive software process improvement and capability assessment standard requirements, including:

[0026] In the software development management system, the core workbench distributes software development tasks to a plurality of target auxiliary tools according to the software requirements;

[0027] The core workbench manages the progress of each of the target auxiliary tools in executing the corresponding software development tasks, and transfers the results of each of the software development tasks to the corresponding downstream auxiliary tools in each of the target auxiliary tools, so as to manage the development process of the software requirements corresponding to the on-board controller to be developed, and meet the preset automotive software process improvement and capability assessment standard requirements.

[0028] Further, after constructing a software development management system according to the core workbench and the plurality of target auxiliary tools, or in the process of managing the development process of the software requirements corresponding to the vehicle controller to be developed based on the software development management system, the method further includes:

[0029] Monitoring whether there are any updates to the preset automotive software process improvement and capability assessment standard requirements;

[0030] In the event that there are updates to the preset automotive software process improvement and capability assessment standard requirements, return to the steps of determining a core workbench for managing the software development process and determining a plurality of target auxiliary tools for implementing the software requirements based on the software requirements and the preset automotive software process improvement and capability assessment standard requirements.

[0031] In a second aspect, the present application provides a vehicle controller software development and management device, the device comprising:

[0032] An information acquisition module is used to obtain project plan information of the vehicle controller to be developed;

[0033] A software requirement screening module, used to screen out software requirements corresponding to the vehicle controller to be developed from the project plan information;

[0034] A platform determination module, for determining a core workbench for managing the software development process from a plurality of existing workbenches to be selected, and determining a plurality of target auxiliary tools for realizing the software requirements from a plurality of existing auxiliary tools to be selected, according to the software requirements and preset automotive software process improvement and capability assessment standard requirements;

[0035] A system construction module, used to construct a software development management system based on the core workbench and a plurality of the target auxiliary tools;

[0036] The software R&D management module is used to manage the R&D process of the software requirements corresponding to the vehicle controller to be developed based on the software R&D management system, so as to meet the preset automotive software process improvement and capability assessment standard requirements.

[0037] Furthermore, the software requirement screening module is used to:

[0038] Decomposing the project plan information to obtain software requirements;

[0039] Classifying the software requirements according to functional types to obtain multiple software functional requirements;

[0040] Dividing each of the software functional requirements according to functional granularity to obtain a plurality of software component requirements corresponding to each of the software functional requirements;

[0041] The software requirements corresponding to the vehicle-mounted controller to be developed include a plurality of software component requirements corresponding to each of the software function requirements.

[0042] Furthermore, the platform determination module is used to:

[0043] According to the software requirements and the preset automotive software process improvement and capability assessment standard requirements, a workbench that covers the software requirements and the preset automotive software process improvement and capability assessment standard requirements to the greatest extent is selected from a plurality of existing workbenches to be selected as the core workbench for managing the software development process;

[0044] According to the software requirements and the preset automotive software process improvement and capability assessment standard requirements, auxiliary tools that meet the software requirements and the preset automotive software process improvement and capability assessment standard requirements are selected from multiple existing auxiliary tools to be selected as multiple target auxiliary tools for realizing the software requirements.

[0045] Furthermore, the system builds modules for:

[0046] Through an application programming interface or a plug-in, a connection is established between the core workbench and each of the target auxiliary tools, so that data and functions are shared between the core workbench and each of the target auxiliary tools to obtain the software development management system.

[0047] Furthermore, the system builds modules for:

[0048] Determining a target data format and a target interface standard according to the data formats and interface standards respectively corresponding to each of the target auxiliary tools;

[0049] Establishing, on the core workbench, a format conversion relationship between the data formats corresponding to the target auxiliary tools and the target data formats, and establishing, on the core workbench, an interface conversion relationship between the interface standards corresponding to the target auxiliary tools and the target interface standards;

[0050] Each of the target auxiliary tools obtains the software development and management system with data function sharing based on the format conversion relationship and the interface conversion relationship of the core workbench.

[0051] Furthermore, the software development management module is used to:

[0052] In the software development management system, the core workbench distributes software development tasks to a plurality of target auxiliary tools according to the software requirements;

[0053] The core workbench manages the progress of each of the target auxiliary tools in executing the corresponding software development tasks, and transfers the results of each of the software development tasks to the corresponding downstream auxiliary tools in each of the target auxiliary tools, so as to manage the development process of the software requirements corresponding to the on-board controller to be developed, and meet the preset automotive software process improvement and capability assessment standard requirements.

[0054] Furthermore, the device also includes an updating module, which is used to:

[0055] After constructing a software development management system based on the core workbench and the plurality of target auxiliary tools, or in the process of managing the development process of the software requirements corresponding to the vehicle controller to be developed based on the software development management system, monitoring whether the preset automotive software process improvement and capability assessment standard requirements are updated;

[0056] In the event that there are updates to the preset automotive software process improvement and capability assessment standard requirements, return to the steps of determining a core workbench for managing the software development process and determining a plurality of target auxiliary tools for implementing the software requirements based on the software requirements and the preset automotive software process improvement and capability assessment standard requirements.

[0057] In a third aspect, the present application provides an electronic device, including:

[0058] processor;

[0059] a memory for storing instructions executable by the processor;

[0060] Among them, the processor is configured to execute to implement a vehicle controller software development and management method as provided in the first aspect.

[0061] In a fourth aspect, the present application provides a non-temporary computer-readable storage medium. When the instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to implement a vehicle controller software development and management method as provided in the first aspect.

[0062] One or more technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages:

[0063] The embodiment of the present application obtains the project plan information of the on-board controller to be developed; selects the software requirements corresponding to the on-board controller to be developed from the project plan information; determines the core workbench for managing the software development process from multiple existing workbenches to be selected, and determines multiple target auxiliary tools for realizing the software requirements from multiple existing auxiliary tools to be selected according to the software requirements and the preset automotive software process improvement and capability assessment standard requirements; constructs a software development management system according to the core workbench and the multiple target auxiliary tools; and based on the software development management system, conducts development management on the development process of the software requirements corresponding to the on-board controller to be developed to meet the preset automotive software process improvement and capability assessment standard requirements. It can be seen that the embodiment of the present application constructs a software development management system based on the existing workbench and the existing auxiliary tools, and realizes the complete software requirements management of the software development product of the on-board controller during its life cycle under the premise of meeting the ASPICE requirements, so that there is no need to use professional tools, purchase licenses, generate maintenance costs, and configure professional personnel, which greatly reduces the cost of enterprises purchasing R&D management tools, reduces the cost of engineer personnel configuration and engineer learning, and improves the quality of product development. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0065] Figure 1 A flowchart of a vehicle controller software development management method provided in an embodiment of the present application;

[0066] Figure 2 A logical diagram of the division of software requirements for the central integrated regional controller provided in an embodiment of the present application;

[0067] Figure 3 A schematic diagram of the structure of the software development management system corresponding to the central integrated regional controller provided in the embodiment of the present application;

[0068] Figure 4 A schematic diagram of the structure of a vehicle controller software development and management device provided in an embodiment of the present application;

[0069] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0070] The embodiment of the present application provides a vehicle controller software development management method to solve the technical problem that in the prior art, in order to comply with the ASPICE standard, it is necessary to use professional tools, purchase licenses, incur maintenance costs and deploy professional personnel during the process of developing vehicle controller software, resulting in high research and development costs for vehicle controllers.

[0071] The technical solution of the embodiment of the present application is to solve the above technical problems, and the overall idea is as follows:

[0072] The embodiment of the present application obtains project plan information of a vehicle controller to be developed; selects software requirements corresponding to the vehicle controller to be developed from the project plan information; determines a core workbench for managing the software development process from multiple existing workbenches to be selected, and determines multiple target auxiliary tools for realizing the software requirements from multiple existing auxiliary tools to be selected; constructs a software development management system based on the core workbench and the multiple target auxiliary tools; and based on the software development management system, manages the development process of the software requirements corresponding to the vehicle controller to be developed to meet the preset automotive software process improvement and capability assessment standard requirements.

[0073] It can be seen that the embodiment of the present application builds a software development management system based on the existing workbench and existing auxiliary tools. On the premise of meeting the ASPICE requirements, it realizes the complete software demand management of the software development products of the vehicle controller during its life cycle. In this way, there is no need to use professional tools, purchase licenses, incur maintenance costs, and configure professional personnel, which greatly reduces the cost of enterprises purchasing R&D management tools, reduces the cost of engineer staffing and engineer learning, and improves the quality of product development.

[0074] In order to better understand the above technical solution, the above technical solution will be described in detail below in conjunction with the accompanying drawings and specific implementation methods.

[0075] First of all, the term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0076] An embodiment of the present application provides a vehicle controller software development management method, which can be applied to the development management process of the vehicle controller. The method includes steps S11 to S15.

[0077] Step S11, obtaining project plan information of the vehicle controller to be developed;

[0078] Step S12, filtering out software requirements corresponding to the vehicle controller to be developed from the project plan information;

[0079] Step S13, according to the software requirements and the preset automotive software process improvement and capability assessment standard requirements, determining a core workbench for managing the software development process from a plurality of existing workbenches to be selected, and determining a plurality of target auxiliary tools for realizing the software requirements from a plurality of existing auxiliary tools to be selected;

[0080] Step S14, constructing a software development management system according to the core workbench and the plurality of target auxiliary tools;

[0081] Step S15, based on the software development management system, the development process of the software requirements corresponding to the vehicle controller to be developed is managed to meet the preset automotive software process improvement and capability assessment standard requirements.

[0082] The present application embodiment now provides the following description for each step.

[0083] Regarding step S11, the project plan information of the vehicle controller to be developed is obtained.

[0084] During the vehicle development process, the types and quantities of vehicle controllers for each vehicle are not fixed, and the vehicle controller to be developed can be any of the vehicle controllers that need to be developed. The project plan information can be in the form of a document, which contains the product manager's expected requirements for the current vehicle controller to be developed, which can include software requirements, hardware requirements, mechanical requirements, and other requirements.

[0085] Regarding step S12, the software requirements corresponding to the vehicle controller to be developed are screened out from the project plan information.

[0086] First, the project plan information is decomposed to obtain software requirements, which may be overall requirements or detailed requirements corresponding to the user's perspective.

[0087] Then, the software requirements are classified according to the functional type to obtain multiple software functional requirements. The functional type is to divide the software requirements according to different functions. For example, when the vehicle controller to be developed is a central integrated regional controller, the software functional requirements include vehicle management function, communication function, diagnosis function, OTA (Over-the-Air Technology) function, safety function, input and output function and hardware driver function, etc. Figure 2 shown.

[0088] Next, each software function requirement is divided according to the functional granularity to obtain multiple software component requirements corresponding to each software function requirement. Functional granularity refers to further subdividing each software function requirement to obtain multiple corresponding software component requirements. For example, Figure 2 As shown, when the vehicle controller to be developed is a central integrated regional controller, the vehicle management function is further subdivided into software component requirements such as power management components, time management components, network management components, power on and off management components, and OS (Operating System) task management components.

[0089] The communication functions are further subdivided into CAN (Controller Area Network) communication components, CANFD (Controller Area Network with Flexible Data Rate) communication components, LIN (Local Interconnect Network) communication components, Ethernet communication components, and software component requirements such as routing and forwarding functions.

[0090] OTA functions are further subdivided into software component requirements such as upgrade management components, OTA client management components, download management components, installation components, vehicle status management components, and human-computer interaction interface components.

[0091] Security functions are further subdivided into software component requirements such as functional safety components and information security components.

[0092] The input and output functions are further subdivided into software component requirements such as various types of sensor input components, analog signal input components, digital signal input components, and output control components of various actuators.

[0093] The hardware driver function is further subdivided into software component requirements such as Mcal (MicroController Abstraction Layer) components, boot loader components, hardware input and output interface abstraction layer components, and memory resource management components.

[0094] The software requirements corresponding to the vehicle-mounted controller to be developed include a plurality of software component requirements corresponding to each of the software function requirements.

[0095] Regarding step S13, based on the software requirements and the preset automotive software process improvement and capability assessment standard requirements, a core workbench for managing the software development process is determined from multiple existing workbenches to be selected, and multiple target auxiliary tools for realizing the software requirements are determined from multiple existing auxiliary tools to be selected.

[0096] The automotive software process improvement and capability assessment standard requirements refer to the ASPICE standard. Specifically, according to the software requirements and the preset ASPICE standard, a core workbench for managing the software development process is determined from a plurality of existing workbenches to be selected, and a plurality of target auxiliary tools for realizing the software requirements are determined from a plurality of existing auxiliary tools to be selected.

[0097] Among them, according to the software requirements and the preset automotive software process improvement and capability assessment standard requirements, a workbench that covers the software requirements and the preset ASPICE standard to the greatest extent is selected from multiple existing workbenches to be selected as the core workbench for managing the software development process. The workbench that covers the software requirements and the preset ASPICE standard to the greatest extent refers to the workbench that can meet the most requirements among the multiple workbenches to be selected. In other words, the embodiment of the present application uses a general, existing, easy-to-use tool that can add a small amount of secondary development as the core workbench.

[0098] For example, the core workbench can integrate the complete development environment and tools necessary for software development, including management tools, configuration tools, quality tools, continuous development integration tools, testing tools, large model tools, AI artificial intelligence tools, etc. The core workbench also meets the requirements of development, support, management and other processes in ASPICE development activities. Taking the central integrated regional controller as an example, the R&D workbench is based on the Feishu workbench. The secondary development integrates all R&D tool entrances and uses message robots. Each development engineer works based on this workbench.

[0099] According to the software requirements and the preset automotive software process improvement and capability assessment standard requirements, auxiliary tools that meet the software requirements and the preset ASPICE standard are selected from the multiple existing auxiliary tools to be selected as multiple target auxiliary tools for implementing the software requirements. These target auxiliary tools can correspond to the software component requirements mentioned above, and the same target auxiliary tool can be used to implement one or more software component requirements.

[0100] Regarding step S14, a software development management system is constructed based on the core workbench and the plurality of target auxiliary tools.

[0101] Through an application programming interface (API) or a plug-in, a connection is established between the core workbench and each of the target auxiliary tools, so that data and functions are shared between the core workbench and each of the target auxiliary tools to obtain the software development management system.

[0102] Connect the target assistance tool with the core workbench through API or plug-in to share the data and functions required for development. This integration can improve work efficiency, reduce data silos, and ensure information consistency.

[0103] Take the central integrated zone controller as an example. Figure 3 As shown, by linking tool APIs, enterprise knowledge management and collaboration software Confluence, project and transaction management software Jira, model development software MATLAB / Simulink, code review software Gerrit, code repository GitLab, continuous integration Jenkins, static code detection and unit testing software Parasoft, integration testing and functional verification software ECUTESTING, and software artifact library management tool JFrog are linked to the core workbench, enabling the sharing of development requirement documents, development tool chains, development professional skills and experience, which is conducive to ensuring information consistency among all parties while improving work efficiency.

[0104] In addition, the embodiment of the present application also determines the target data format and the target interface standard according to the data formats and interface standards respectively corresponding to each of the target auxiliary tools.

[0105] A format conversion relationship between the data formats corresponding to each of the target auxiliary tools and the target data format is established on the core workbench, and an interface conversion relationship between the interface standards corresponding to each of the target auxiliary tools and the target interface standard is established on the core workbench.

[0106] Each of the target auxiliary tools obtains the software development and management system with data function sharing based on the format conversion relationship and the interface conversion relationship of the core workbench.

[0107] Unified document templates, checklists and review lists can also be established on the core workbench to develop unified data formats, interface standards, document templates, checklists and review lists to ensure compatibility between different tools, ensure that R&D personnel corresponding to different software requirement components have consistent understanding of requirements during the R&D process, and achieve effective integration and data exchange in the R&D process. This is conducive to developing detailed integration and compatibility testing plans to ensure the stability and reliability of the integration platform.

[0108] Regarding step S15, based on the software development management system, the development process of the software requirements corresponding to the vehicle controller to be developed is managed to meet the preset automotive software process improvement and capability assessment standard requirements.

[0109] In the software development management system, the core workbench distributes software development tasks to multiple target auxiliary tools according to the software requirements. The core workbench manages the progress of each target auxiliary tool in executing the corresponding software development task, and transfers the results of each software development task to the corresponding downstream auxiliary tool in each target auxiliary tool, so as to manage the development process of the software requirements corresponding to the vehicle controller to be developed, and meet the preset automotive software process improvement and capability assessment standard requirements.

[0110] The software development management system implements the requirements management process to ensure that the collection, analysis, definition, tracking and change management of requirements are all carried out through the core workbench. The software development management system implements a comprehensive requirements management process, which includes the collection, analysis, definition, tracking and change management of requirements. This process is implemented through the core workbench to ensure that all activities of each software component requirement are carried out in a unified environment, and the message robot of the core workbench notifies each software component requirement and the flow process of each target auxiliary tool.

[0111] Taking the central integrated regional controller as an example, the message robot is used to notify the relevant R&D personnel of the issued software component requirements at each R&D stage of the model development process according to the start time and end time of the nodes of each software component requirement to carry out corresponding work and complete the integration and flow of the process.

[0112] After constructing a software R&D management system based on the core workbench and multiple target auxiliary tools, or in the process of R&D management of the R&D process of the software requirements corresponding to the vehicle controller to be developed based on the software R&D management system, or after managing the R&D process of the software requirements corresponding to the vehicle controller to be developed based on the software R&D management system, the method also includes steps S21-S22.

[0113] Step S21, monitoring whether the preset automotive software process improvement and capability assessment standard requirements are updated;

[0114] Step S22, when there is an update to the preset automotive software process improvement and capability assessment standard requirements, returns to execute the steps of determining the core workbench for managing the software development process and determining multiple target auxiliary tools for implementing the software requirements based on the software requirements and the preset automotive software process improvement and capability assessment standard requirements.

[0115] Demand management is a dynamic process that requires continuous optimization and maintenance as the ASPICE standard version changes and the project requirements evolve. In other words, the ASPICE standard will be updated and changed from time to time, so it is necessary to monitor whether there are any updates to the ASPICE standard. If there are any updates, re-execute steps S13-S15 to adapt to the changes in the ASPICE standard and industry requirements.

[0116] It can be seen that the embodiment of the present application continuously optimizes and maintains the software development management system to adapt to changes in the ASPICE standard and industry requirements, and to control R&D costs. This helps to ensure that the software development management system is always in the best condition, can adapt to the ever-changing environment and the constantly updated industry standard requirements, and adapt to the company's cost reduction strategy.

[0117] In summary, the embodiment of the present application obtains the project plan information of the on-board controller to be developed; selects the software requirements corresponding to the on-board controller to be developed from the project plan information; determines the core workbench for managing the software development process from multiple existing workbenches to be selected, and determines multiple target auxiliary tools for realizing the software requirements from multiple existing auxiliary tools to be selected according to the software requirements and the preset automotive software process improvement and capability assessment standard requirements; constructs a software development management system according to the core workbench and multiple target auxiliary tools; and based on the software development management system, conducts development management on the development process of the software requirements corresponding to the on-board controller to be developed to meet the preset automotive software process improvement and capability assessment standard requirements. It can be seen that the embodiment of the present application constructs a software development management system based on the existing workbench and the existing auxiliary tools, and realizes the complete software requirements management of the software development product of the on-board controller during its life cycle under the premise of meeting the ASPICE requirements, so that there is no need to use professional tools, purchase licenses, generate maintenance costs, and configure professional personnel, which greatly reduces the cost of enterprises to purchase R&D management tools, reduces the cost of engineer personnel configuration and engineer learning, and improves the quality of product development.

[0118] That is to say, the embodiments of the present application integrate and optimize existing tools, methods and processes, reduce dependence on professional single tools, and achieve complete software requirement management of vehicle-mounted controller software development products throughout their life cycle, without increasing R&D costs or requiring the purchase of a development environment for specific R&D management tools. This reduces the complexity and cost of the ASPICE software requirement management process, which is of great significance to the R&D efficiency, cost control, process quality and audit certification of all vehicle models and controllers.

[0119] The embodiment of the present application utilizes the existing R&D workbench to build a unified entry for all data and tools required for demand management and development activities, formulates a unified data format and data interface standard, improves project development efficiency, shortens product development cycle, reduces learning costs for developers, and greatly reduces the procurement cost of enterprise R&D management tools, which is of great significance to enterprises in reducing costs and increasing efficiency.

[0120] The embodiments of the present application continuously optimize platform tools to adapt to changes in ASPICE standards and changes in industry requirements, thereby reducing dependence on professional single tools, reducing the cost of enterprise fixed assets, reducing the cost of purchasing and maintaining R&D tools, and at the same time improving the efficiency of software demand management and product quality, which is of great significance to product compliance with industry standards, improving product quality, and enhancing market competitiveness.

[0121] Based on the same inventive concept, the present application embodiment provides the following Figure 4 A vehicle controller software development and management device is shown, the device comprising:

[0122] The information acquisition module 41 is used to acquire the project plan information of the vehicle controller to be developed;

[0123] A software requirement screening module 42 is used to screen out software requirements corresponding to the vehicle controller to be developed from the project plan information;

[0124] A platform determination module 43 is used to determine a core workbench for managing the software development process from a plurality of existing workbenches to be selected, and to determine a plurality of target auxiliary tools for realizing the software requirements from a plurality of existing auxiliary tools to be selected, according to the software requirements and the preset automotive software process improvement and capability assessment standard requirements;

[0125] A system construction module 44, used to construct a software development management system according to the core workbench and a plurality of the target auxiliary tools;

[0126] The software development management module 45 is used to manage the development process of the software requirements corresponding to the vehicle controller to be developed based on the software development management system, so as to meet the preset automotive software process improvement and capability assessment standard requirements.

[0127] Furthermore, the software requirement screening module 42 is used to:

[0128] Decomposing the project plan information to obtain software requirements;

[0129] Classifying the software requirements according to functional types to obtain multiple software functional requirements;

[0130] Dividing each of the software functional requirements according to functional granularity to obtain a plurality of software component requirements corresponding to each of the software functional requirements;

[0131] The software requirements corresponding to the vehicle-mounted controller to be developed include a plurality of software component requirements corresponding to each of the software function requirements.

[0132] Furthermore, the platform determination module 43 is used to:

[0133] According to the software requirements and the preset automotive software process improvement and capability assessment standard requirements, a workbench that covers the software requirements and the preset automotive software process improvement and capability assessment standard requirements to the greatest extent is selected from a plurality of existing workbenches to be selected as the core workbench for managing the software development process;

[0134] According to the software requirements and the preset automotive software process improvement and capability assessment standard requirements, auxiliary tools that meet the software requirements and the preset automotive software process improvement and capability assessment standard requirements are selected from multiple existing auxiliary tools to be selected as multiple target auxiliary tools for realizing the software requirements.

[0135] Furthermore, the system building block 44 is used to:

[0136] Through an application programming interface or a plug-in, a connection is established between the core workbench and each of the target auxiliary tools, so that data and functions are shared between the core workbench and each of the target auxiliary tools to obtain the software development management system.

[0137] Furthermore, the system building block 44 is used to:

[0138] Determining a target data format and a target interface standard according to the data formats and interface standards respectively corresponding to each of the target auxiliary tools;

[0139] Establishing, on the core workbench, a format conversion relationship between the data formats corresponding to the target auxiliary tools and the target data formats, and establishing, on the core workbench, an interface conversion relationship between the interface standards corresponding to the target auxiliary tools and the target interface standards;

[0140] Each of the target auxiliary tools obtains the software development and management system with data function sharing based on the format conversion relationship and the interface conversion relationship of the core workbench.

[0141] Furthermore, the software development management module 45 is used to:

[0142] In the software development management system, the core workbench distributes software development tasks to a plurality of target auxiliary tools according to the software requirements;

[0143] The core workbench manages the progress of each of the target auxiliary tools in executing the corresponding software development tasks, and transfers the results of each of the software development tasks to the corresponding downstream auxiliary tools in each of the target auxiliary tools, so as to manage the development process of the software requirements corresponding to the on-board controller to be developed, and meet the preset automotive software process improvement and capability assessment standard requirements.

[0144] Furthermore, the device also includes an updating module, which is used to:

[0145] After constructing a software development management system based on the core workbench and the plurality of target auxiliary tools, or in the process of managing the development process of the software requirements corresponding to the vehicle controller to be developed based on the software development management system, monitoring whether the preset automotive software process improvement and capability assessment standard requirements are updated;

[0146] In the event that there are updates to the preset automotive software process improvement and capability assessment standard requirements, return to the steps of determining a core workbench for managing the software development process and determining a plurality of target auxiliary tools for implementing the software requirements based on the software requirements and the preset automotive software process improvement and capability assessment standard requirements.

[0147] Based on the same inventive concept, the present application embodiment provides the following Figure 5 An electronic device as shown includes:

[0148] Processor 51;

[0149] A memory 52 for storing instructions executable by the processor 51;

[0150] The processor 51 is configured to execute to implement a vehicle controller software development and management method as provided above.

[0151] Based on the same inventive concept, an embodiment of the present application provides a non-temporary computer-readable storage medium. When the instructions in the storage medium are executed by a processor of an electronic device, the electronic device can execute and implement a vehicle controller software development and management method as provided above.

[0152] Since the electronic device introduced in this embodiment is an electronic device used to implement the information processing method in the embodiment of the present application, based on the information processing method introduced in the embodiment of the present application, a person skilled in the art can understand the specific implementation of the electronic device of the present embodiment and its various variations, so how the electronic device implements the method in the embodiment of the present application is not described in detail here. As long as a person skilled in the art implements the electronic device used by the information processing method in the embodiment of the present application, it belongs to the scope of protection of this application.

[0153] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0154] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0155] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0156] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0157] Although the preferred embodiments of the present invention have been described, those skilled in the art may make other changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention.

[0158] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A vehicle controller software development management method, characterized in that: The method comprises: Obtain project plan information for vehicle controllers to be developed; Filtering out software requirements corresponding to the vehicle controller to be developed from the project plan information; According to the software requirements and the preset automotive software process improvement and capability assessment standard requirements, a core workbench for managing the software development process is determined from a plurality of existing workbenches to be selected, and a plurality of target auxiliary tools for realizing the software requirements are determined from a plurality of existing auxiliary tools to be selected; Constructing a software development management system based on the core workbench and a plurality of target auxiliary tools; Based on the software R&D management system, the R&D process of the software requirements corresponding to the on-board controller to be developed is managed to meet the preset automotive software process improvement and capability assessment standard requirements.

2. The method according to claim 1, characterized in that The step of selecting software requirements corresponding to the vehicle controller to be developed from the project plan information includes: Decomposing the project plan information to obtain software requirements; Classifying the software requirements according to functional types to obtain multiple software functional requirements; Dividing each of the software functional requirements according to functional granularity to obtain a plurality of software component requirements corresponding to each of the software functional requirements; The software requirements corresponding to the vehicle-mounted controller to be developed include a plurality of software component requirements corresponding to each of the software function requirements.

3. The method according to claim 1, characterized in that The step of determining a core workbench for managing the software development process from a plurality of existing workbenches to be selected based on the software requirements and the preset automotive software process improvement and capability assessment standard requirements, and determining a plurality of target auxiliary tools for realizing the software requirements from a plurality of existing auxiliary tools to be selected, includes: According to the software requirements and the preset automotive software process improvement and capability assessment standard requirements, a workbench that covers the software requirements and the preset automotive software process improvement and capability assessment standard requirements to the greatest extent is selected from a plurality of existing workbenches to be selected as the core workbench for managing the software development process; According to the software requirements and the preset automotive software process improvement and capability assessment standard requirements, auxiliary tools that meet the software requirements and the preset automotive software process improvement and capability assessment standard requirements are selected from multiple existing auxiliary tools to be selected as multiple target auxiliary tools for realizing the software requirements.

4. The method according to claim 1, characterized in that The software development management system is constructed according to the core workbench and the plurality of target auxiliary tools, including: Through an application programming interface or a plug-in, a connection is established between the core workbench and each of the target auxiliary tools, so that data and functions are shared between the core workbench and each of the target auxiliary tools to obtain the software development management system.

5. The method according to claim 1, characterized in that The software development management system is constructed according to the core workbench and the plurality of target auxiliary tools, including: Determining a target data format and a target interface standard according to the data formats and interface standards respectively corresponding to each of the target auxiliary tools; Establishing, on the core workbench, a format conversion relationship between the data formats corresponding to the target auxiliary tools and the target data formats, and establishing, on the core workbench, an interface conversion relationship between the interface standards corresponding to the target auxiliary tools and the target interface standards; Each of the target auxiliary tools obtains the software development and management system with data function sharing based on the format conversion relationship and the interface conversion relationship of the core workbench.

6. The method according to claim 1, characterized in that Based on the software development management system, the development process of the software requirements corresponding to the vehicle controller to be developed is managed to meet the preset automotive software process improvement and capability assessment standard requirements, including: In the software development management system, the core workbench distributes software development tasks to a plurality of target auxiliary tools according to the software requirements; The core workbench manages the progress of each of the target auxiliary tools in executing the corresponding software development tasks, and transfers the results of each of the software development tasks to the corresponding downstream auxiliary tools in each of the target auxiliary tools, so as to manage the development process of the software requirements corresponding to the on-board controller to be developed, and meet the preset automotive software process improvement and capability assessment standard requirements.

7. The method according to claim 1, characterized in that After constructing a software development management system according to the core workbench and the plurality of target auxiliary tools, or in the process of managing the development process of the software requirements corresponding to the vehicle controller to be developed based on the software development management system, the method further includes: Monitoring whether there are any updates to the preset automotive software process improvement and capability assessment standard requirements; In the event that there are updates to the preset automotive software process improvement and capability assessment standard requirements, return to the steps of determining a core workbench for managing the software development process and determining a plurality of target auxiliary tools for implementing the software requirements based on the software requirements and the preset automotive software process improvement and capability assessment standard requirements.

8. A vehicle controller software development and management device, characterized in that: The device comprises: An information acquisition module is used to obtain project plan information of the vehicle controller to be developed; A software requirement screening module, used to screen out software requirements corresponding to the vehicle controller to be developed from the project plan information; A platform determination module, for determining a core workbench for managing the software development process from a plurality of existing workbenches to be selected, and determining a plurality of target auxiliary tools for realizing the software requirements from a plurality of existing auxiliary tools to be selected, according to the software requirements and preset automotive software process improvement and capability assessment standard requirements; A system construction module, used to construct a software development management system based on the core workbench and a plurality of the target auxiliary tools; The software R&D management module is used to manage the R&D process of the software requirements corresponding to the vehicle controller to be developed based on the software R&D management system, so as to meet the preset automotive software process improvement and capability assessment standard requirements.

9. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute to implement a vehicle controller software development and management method as described in any one of claims 1 to 7.

10. A non-temporary computer-readable storage medium, when the instructions in the storage medium are executed by a processor of an electronic device, enables the electronic device to implement a vehicle controller software development and management method as described in any one of claims 1 to 7.

Citation Information

Patent Citations

  • Continuous integration and automatic test method for automobile electronic software

    CN113110824A

  • Function switch management method and device for automobile software development

    CN115562712A

  • Automobile software development method and system, computer and readable storage medium

    CN116204161A

  • Method and system for automatic test plan generation

    WO2024104781A1