Tool chain for V-shaped development test left shift based on automobile electric control software

Abstract

The invention relates to the technical field of automobile electronic control software development, and particularly discloses a tool chain based on automobile electronic control software V-shaped development test left shift, a plurality of modules are constructed by adopting modular design, and each module adopts standardized design and is called in V-shaped development test left shift; in the construction process, a software development process is followed; in the development and maintenance process, version control is carried out; through automatic construction and deployment, scripted configuration and dependency management are carried out; the method has cross-platform and transportability; and performing performance optimization and resource management. A plurality of modules are constructed by adopting modular design, software in each module is quickly called in V-shaped development test left shift, and meanwhile, data transmission and interaction obstacles among the modules are reduced due to a highly integrated software tool chain, so that data flow is smoother, the simulation period is shortened, and the simulation efficiency is improved. The simulation test can be completed in a shorter time, and the development speed and efficiency of the whole V process are improved.

Description

Technical Field

[0001] The present invention relates to the technical field of automobile electronic control software development, and in particular to a tool chain based on V-shaped development and testing left shift of automobile electronic control software. Background Art

[0002] The electronic control unit software development tool chain service can support the integration of all mainstream development and testing software and self-developed program scripts into the tool chain program through its own standardized tool interface, development and testing tool chain building function, and the SSH command-based tool integration interface provided by the platform. All files in the platform can directly call the development and testing tools in the third-party development and testing platform or cloud platform to form a tool chain and quickly call development and testing. It mainly includes the following aspects.

[0003] (1) Data integrity and consistency

[0004] Data standardization: Develop and promote the use of unified data standards and formats to ensure data integration and consistency.

[0005] Data governance: Establish a data governance mechanism to perform data verification, data update and data synchronization to ensure data integrity and consistency.

[0006] (2) Test accuracy and efficiency

[0007] Parallel and distributed computing: Use cloud platform parallel computing and distributed computing technologies to improve the processing capabilities of large-scale testing and verification.

[0008] Adaptive testing technology: Integrate cloud platform adaptive testing technology to dynamically adjust test accuracy and calculation range according to test requirements and resource conditions.

[0009] (3) Interdisciplinary collaboration

[0010] Collaborative work platform: Build a research and development project management mechanism, build a cloud platform that supports multi-user and multi-team collaborative work, and realize cross-disciplinary information exchange and collaborative work.

[0011] Standardized communication mechanisms: Develop interdisciplinary communication standards and mechanisms to promote effective communication and cooperation among experts in different fields.

[0012] (4) Compatibility of tools and platforms

[0013] Unified interface standards: Develop unified interface standards to ensure data exchange and interoperability between different modeling and simulation tools.

[0014] Integrated Development Environment: Build an integrated development environment (IDE) to support seamless integration of multiple modeling and simulation tools.

[0015] Compatibility testing framework: Establish a compatibility testing framework to ensure the compatibility and stability of different tools and platforms.

[0016] (5) User-friendliness and operability

[0017] User-centered design: Adopt the user-centered design concept to design a simple and intuitive user interface to improve the convenience of user operation.

[0018] Comprehensive training and support: Provide comprehensive user training and technical support to help users master the use of simulation tools and platforms.

[0019] Feedback and improvement mechanism: Establish a user feedback mechanism to promptly collect and respond to user opinions and suggestions, and continuously optimize and improve tools and platforms.

[0020] (6) Combined with the V-shaped development process test left shift method

[0021] A V-shaped development process is built through the tool chain in the platform. It can also be understood as quickly calling modules and software in the tool chain in the V-shaped development process.

[0022] At present, the following problems are common in my country's automotive electronic control unit software development projects:

[0023] (1) Development tools are isolated

[0024] The software development tools at different stages of the V-shaped process are isolated from each other, resulting in low software development efficiency.

[0025] (2) Information feedback is not timely

[0026] Information flow is not smooth, and updates on project progress and work status are delayed, resulting in management and team members being unable to understand project status in a timely manner, affecting decision-making and adjustments.

[0027] (3) Inefficient process

[0028] Reliance on paper document circulation and manual approval is inefficient, error-prone, and difficult to track and audit.

[0029] (4) Difficulty in resource coordination

[0030] As the number of projects increases, resource allocation and scheduling become complex, making resource conflicts and schedule delays more likely to occur.

[0031] (5) Communication and collaboration barriers

[0032] Poor communication and low collaboration efficiency across departments or remote teams affect team morale and project progress.

[0033] (6) Lack of risk management

[0034] Failure to identify and address potential risks causes problems to suddenly erupt and affect project success.

[0035] (7) Discrete development tools

[0036] The development tool versions are inconsistent and there is a lack of unified management. The numerous development and testing tools do not form a development chain, resulting in low development efficiency and a high probability of problems.

[0037] After investigation and research, the inventors summarized the causes and results of problems in the process of automotive electronic control unit software development as follows:

[0038] (1) Insufficient integration and compatibility:

[0039] Reason: Existing automotive simulation software tool chains are often composed of multiple independent software modules, and the integration between these modules is not high, resulting in low efficiency in data transmission and interaction. At the same time, different software modules may use different data formats and communication protocols, making compatibility a major problem.

[0040] Result: Users need to spend a lot of time and energy on software configuration and data conversion, which reduces work efficiency.

[0041] (2) Simulation accuracy and real-time performance are limited:

[0042] Reason: Traditional simulation software may be limited by computing power when dealing with complex scenarios and high-precision models, resulting in simulation accuracy and real-time performance that cannot meet the requirements of autonomous driving technology.

[0043] Result: Simulation results may not accurately reflect real-world conditions, which can affect the development and optimization of autonomous driving algorithms.

[0044] (3) Lack of standardization and scalability:

[0045] Reason: The existing automotive simulation software tool chain lacks unified standards and specifications in the design and development process, resulting in inconsistent interfaces and data formats between different software modules. At the same time, the software has poor scalability and is difficult to adapt to the rapid development of autonomous driving technology.

[0046] Result: Users need to constantly adapt to new software versions and interface changes when using the software, which increases the learning and usage costs.

[0047] Based on this technical background, the present invention studies a tool chain based on V-shaped development and testing left shift of automotive electronic control software. Summary of the invention

[0048] In view of the deficiencies in the prior art, the present invention provides a tool chain based on the V-shaped development and test left shift of automotive electronic control software. A plurality of modules are constructed by modular design. The software in each module is quickly called in the V-shaped development and test left shift. At the same time, the highly integrated software tool chain reduces the data transmission and interaction barriers between modules, making the data flow smoother, shortening the simulation cycle, completing the simulation test in a shorter time, and improving the development speed and efficiency of the overall V process.

[0049] In order to achieve the above-mentioned object, the present invention provides a tool chain based on V-shaped development and test left shift of automotive electronic control software, which adopts modular design to construct multiple modules, each module adopts standardized design and is called in the V-shaped development and test left shift;

[0050] During the build process, follow the software development process;

[0051] Perform version control during development and maintenance;

[0052] Scripted configuration and dependency management through automated build and deployment;

[0053] Cross-platform and portable;

[0054] Perform performance optimization and resource management.

[0055] The beneficial effects of the present invention include:

[0056] (1) The tool chain based on the V-shaped development and test left shift of automotive electronic control software proposed in the present invention adopts modular design to construct multiple modules. The software in each module is quickly called in the V-shaped development and test left shift. At the same time, the highly integrated software tool chain reduces the data transmission and interaction barriers between modules, making the data flow smoother, shortening the simulation cycle, and completing the simulation test in a shorter time, thereby improving the development speed and efficiency of the overall V process.

[0057] (2) The tool chain proposed in the present invention is based on the V-shaped left-shift of development and testing of automotive electronic control software. The unified data interface and protocol reduce the user's configuration and data conversion costs between different software modules. At the same time, the highly integrated tool chain reduces software maintenance costs and reduces the total R&D cost. Through automated construction and deployment, scripted configuration and dependency management can more accurately simulate vehicle behaviors and traffic scenarios in the real world, thereby improving the authenticity and accuracy of the simulation.

[0058] (3) The tool chain based on the V-shaped development and test left shift of automotive electronic control software proposed in the present invention is cross-platform and portable, and performs performance optimization and resource management so that users can easily add or delete modules and adjust simulation parameters and scenarios as needed. Users can customize the simulation tool chain as needed to meet different testing requirements and improve the flexibility and adaptability of testing.

[0059] Other features and advantages of the present invention will be described in detail in the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] The above and other objects, features and advantages of the present invention will become more apparent through a more detailed description of exemplary embodiments of the present invention with reference to the accompanying drawings.

[0061] Figure 1 This is a schematic diagram of the module technology architecture in a specific implementation of the tool chain based on V-shaped development and test left shift of automotive electronic control software proposed by the present invention.

[0062] Figure 2 This is a schematic diagram of the module RESTFul Web API call architecture in a specific implementation of the tool chain based on V-shaped development and test left shift of automotive electronic control software proposed by the present invention.

[0063] Figure 3 This is an example diagram of module RESTful call object operation commands in a specific implementation of the tool chain based on V-shaped development and test left shift of automotive electronic control software proposed by the present invention.

[0064] Figure 4 A schematic diagram of a large V-shaped development process of a specific implementation of the test left-shift method for the V-shaped development process of automotive electronic control software proposed by the present invention.

[0065] Figure 5 This is a schematic diagram of a small V-shaped requirement analysis process in a specific implementation of the test left-shift method for the V-shaped development process of automotive electronic control software proposed by the present invention.

[0066] Figure 6 This is a schematic diagram of a small V-shaped system design process in a specific implementation of the test left-shift method for the V-shaped development process of automotive electronic control software proposed by the present invention.

[0067] Figure 7 This is a schematic diagram of the small V-shaped architecture design process in a specific implementation of the test left-shift method for the automotive electronic control software V-shaped development process proposed by the present invention.

[0068] Figure 8 This is a schematic diagram of the small V-shaped module design process in a specific implementation of the test left-shift method for the automotive electronic control software V-shaped development process proposed by the present invention. DETAILED DESCRIPTION

[0069] The preferred embodiments of the present invention will be described in more detail below. Although the preferred embodiments of the present invention are described below, it should be understood that the present invention can be implemented in various forms and should not be limited to the embodiments set forth herein.

[0070] The present invention provides a tool chain based on V-shaped development and testing left shift of automotive electronic control software, such as Figure 1 As shown, modular design is used to build multiple modules, each module adopts standardized design and is called in the V-shaped development and testing left shift;

[0071] During the build process, follow the software development process;

[0072] Perform version control during development and maintenance;

[0073] Scripted configuration and dependency management through automated build and deployment;

[0074] Cross-platform and portable;

[0075] Perform performance optimization and resource management.

[0076] In the present invention, a modular design is adopted to construct multiple modules, and the software in each module is quickly called in the V-shaped development and test left shift. At the same time, the highly integrated software tool chain reduces the data transmission and interaction barriers between modules, making the data flow smoother, shortening the simulation cycle, and completing the simulation test in a shorter time, thereby improving the development speed and efficiency of the overall V process.

[0077] According to the present invention, V-shaped development and testing shift left includes:

[0078] In the big V-shaped development process, system personnel or developers and testers jointly participate in each stage of requirement analysis, system design, architecture design and module design. Each stage forms its own small V-shaped process to carry out continuous integration and testing of the software to ensure that every change in the software development process can be verified and tested in a timely manner.

[0079] According to the present invention, each of the plurality of modules is responsible for a specific function or task;

[0080] Modular design is used to make the tool chain construction more flexible, easy to expand and maintain;

[0081] Standardized design includes the standardization of data interfaces, data formats, and communication protocols to ensure effective integration and interaction between different modules.

[0082] According to the present invention, the software development process includes software requirements analysis, design, coding, testing and deployment;

[0083] Follow the software development process to ensure the quality and stability of the tool chain;

[0084] Version control is used to help teams work together, manage code changes, and track and fix issues.

[0085] According to the present invention, automated building and deployment are achieved through build scripts and continuous integration / continuous deployment tools to improve development efficiency and reduce human errors;

[0086] Scripted configuration is used to easily manage toolchain configuration information;

[0087] Configuration information includes environment variables and database connections.

[0088] Preferably, dependency management includes dependency resolution and version compatibility:

[0089] Dependency resolution is used to automatically resolve and install dependencies during the toolchain build process. Dependencies include multiple external libraries or tools.

[0090] Version compatibility is used to regularly check and update dependencies to avoid version conflicts or compatibility issues.

[0091] In the present invention, unified data interfaces and protocols reduce the user's configuration and data conversion costs between different software modules, while the highly integrated tool chain reduces software maintenance costs and reduces the total R&D cost; through automated construction and deployment, scripted configuration and dependency management can more accurately simulate vehicle behaviors and traffic scenarios in the real world, thereby improving the authenticity and accuracy of the simulation.

[0092] According to the present invention, cross-platform and portability include:

[0093] Containerization technology is used to encapsulate the tool chain and its dependencies into an independent container to achieve seamless cross-platform deployment and operation, ensuring that the tool chain runs on different operating systems and hardware platforms.

[0094] According to the present invention, performance optimization and resource management include:

[0095] Analyze the performance of the tool chain, identify bottlenecks and optimize them to improve the efficiency of the tool chain operation;

[0096] Reasonably allocate and manage system resources to ensure stable operation and efficient execution of the tool chain;

[0097] System resources include CPU, memory, and disk space.

[0098] According to the present invention, the standardization of data interfaces, data formats and communication protocols to ensure effective integration and interaction between different modules includes:

[0099] Use RESTFul Web API data interface for data access to ensure effective integration and interaction between different modules;

[0100] The RESTFul Web API data interface follows international standard specifications and is used to obtain and transmit data to all third-party development and testing tools.

[0101] According to the present invention, third-party development and testing tools include third-party development tools, testing tools, customized software and self-developed programs;

[0102] RESTFul WebAPI is created to utilize the OData standard protocol.

[0103] The tool chain in the present invention is cross-platform and portable, and performs performance optimization and resource management so that users can easily add or delete modules and adjust simulation parameters and scenarios as needed. Users can customize the simulation tool chain as needed to meet different testing requirements and improve the flexibility and adaptability of testing.

[0104] The present invention will be described in more detail below by way of examples.

[0105] Embodiment 1:

[0106] This embodiment proposes a tool chain based on V-shaped development and testing left shift of automotive electronic control software, which is established by the following technical means:

[0107] (1) System construction and integration theory:

[0108] a. Modular design: Tool chains are often composed of multiple modules, each of which is responsible for a specific function or task. Modular design makes the construction of tool chains more flexible, easy to expand and maintain;

[0109] b. Interface standardization: In order to ensure effective integration and interaction between different modules, a unified interface standard needs to be formulated; this includes standardization of data formats, communication protocols, etc.;

[0110] (2) Software Engineering Theory:

[0111] Software development process: The tool chain construction process needs to follow certain software development processes, such as requirements analysis, design, coding, testing, deployment, etc. These processes ensure the quality and stability of the tool chain;

[0112] Version control: Version control is very important in the development and maintenance of the tool chain; it can help teams work together, manage code changes, and track and fix problems;

[0113] (3) Automation and scripting technology:

[0114] Automated build and deployment: Automated build and deployment of tool chains can significantly improve development efficiency and reduce human errors; this usually involves the use of tools such as build scripts and continuous integration / continuous deployment (CI / CD);

[0115] Scripted configuration: Through scripted configuration, you can easily manage the configuration information of the toolchain, such as environment variables, database connections, etc.; this helps to maintain the consistency and portability of the configuration;

[0116] (4) Dependency Management:

[0117] Dependency resolution: During the toolchain construction process, you may need to rely on multiple external libraries or tools; dependency resolution technology can help automatically resolve and install these dependencies;

[0118] Version compatibility: Managing version compatibility between different modules or tools is key to ensuring the stable operation of the toolchain; dependencies need to be checked and updated regularly to avoid version conflicts or compatibility issues;

[0119] (5) Cross-platform and portability:

[0120] Cross-platform support: The toolchain needs to support running on different operating systems and hardware platforms; this requires that cross-platform compatibility and portability be taken into consideration during design;

[0121] Containerization technology: Containerization technology (such as Docker) can be used to encapsulate the tool chain and its dependencies into an independent container, thereby achieving seamless deployment and operation across platforms;

[0122] (6) Performance optimization and resource management:

[0123] Performance analysis: Analyzing the performance of the tool chain, identifying bottlenecks and optimizing them is the key to improving the efficiency of the tool chain;

[0124] Resource management: Rationally allocate and manage system resources (such as CPU, memory, disk space, etc.) to ensure stable operation and efficient execution of the tool chain;

[0125] In this embodiment, the software development tool chain module technical architecture is as follows Figure 1 As shown;

[0126] Based on the special positioning of software development and testing integration platform, the software development tool chain module has developed a variety of standardized data interfaces for various third-party programs, development and testing tools, development tools, customized software, self-developed programs, and third-party platforms at the beginning of its design, mainly using standardized RESTful interfaces for access;

[0127] The software development tool chain module provides a RESTFul WebAPI data interface based on the OData standard protocol, and provides complete API call examples and interface documentation;

[0128] The RESTFul interface complies with international standards and general specifications. All third-party development and testing tools can call this interface to obtain and transmit data.

[0129] The RESTful API of the software development toolchain module uses the Open Data Protocol (OData) to create and use RESTful APIs; JSON enables the software development toolchain module to communicate with the server more efficiently by using a more compact and faster data format; the software development toolchain module also allows communication with other systems that support the OData protocol;

[0130] In this embodiment, the software development tool chain module RESTful API call architecture is as follows Figure 2 As shown, the software development tool chain module RESTful call object operation command list is shown in Table 1, and the software development tool chain module RESTful call object operation command example is shown in Figure 3 shown.

[0131] Figure 1 Software Development Toolchain Module RESTful Call Object Operation Command List

[0132]

[0133] In this embodiment, the large V-type development process is as follows Figure 4 As shown in the figure, the implementation process of V-shaped development and testing left shift includes:

[0134] In the big V-shaped development process, system personnel or developers and testers jointly participate in each stage of requirements analysis, system design, architecture design and module design. Each stage forms its own small V-shaped process to carry out continuous integration and testing of the software to ensure that every change in the software development process can be verified and tested in a timely manner;

[0135] like Figure 5 As shown in the figure, the process of the small V-shaped demand analysis phase includes:

[0136] Test plan formulation: During the requirements analysis phase, the test team begins to participate in and review the requirements documents, formulate a test plan based on the requirements documents, and clarify the test scope, test strategy, test resources, etc.

[0137] Test case design: Based on the requirements document, the test team can start designing preliminary test cases to ensure that each functional point in the requirements is covered by a corresponding test case;

[0138] Requirements collation: System personnel collect development requirements, including functional requirements, performance requirements, and interface requirements, and organize the collected requirements, remove redundant and conflicting parts, and form a preliminary requirements document;

[0139] Requirements review: Organize system personnel to conduct requirements review to ensure that the requirements document accurately reflects customer needs;

[0140] Test case review: Testers jointly review test cases;

[0141] like Figure 6 As shown in the figure, the small V-type system design process includes:

[0142] System design: System personnel define and design the system's functional modules and main functional points based on the requirements document to form a system design document;

[0143] System document review: Organize system personnel to review system design documents to ensure that the system design meets the requirements of the requirement documents;

[0144] System test case design: Testers write test cases suitable for right-side system testing;

[0145] Test case review: Testers jointly review test cases;

[0146] like Figure 7 As shown in the figure, the small V-shaped architecture design process includes:

[0147] Design review: The test team participates in the review of the architecture design phase to ensure that the design solutions in the design documents meet the requirements and check whether there are potential defects or problems in the design;

[0148] Test case design: Based on the architecture design document, the test team can write integrated test cases, including test data preparation, test environment construction, etc.

[0149] Architecture design: System personnel define and design the architecture according to the system design document to form an architecture design document;

[0150] Architecture review: Organize system personnel to conduct functional reviews to ensure that the architecture design meets the requirements of the system design documents;

[0151] Test case review: Testers jointly review test cases;

[0152] like Figure 8 As shown in the figure, the small V-shaped module design process includes:

[0153] Module design: Developers design the specific implementation plan for each module based on the architecture design document, including the module's input / output, processing logic, etc.

[0154] Module review: The module design is confirmed by the developers to ensure that it meets the overall system requirements;

[0155] Unit test case design: Testers write test cases suitable for unit testing;

[0156] Test case review: Testers jointly review the test cases.

[0157] The tool chain based on V-shaped development and test left shift of automotive electronic control software proposed in the embodiment of the present invention adopts modular design to construct multiple modules. The software in each module is quickly called in the V-shaped development and test left shift. At the same time, the highly integrated software tool chain reduces data transmission and interaction barriers between modules, making data flow smoother, shortening the simulation cycle, and completing simulation testing in a shorter time, thereby improving the development speed and efficiency of the overall V process.

[0158] The embodiments of the present invention have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments.

Claims

1. A tool chain based on V-shaped development and testing left shift of automotive electronic control software, characterized in that: The toolchain: Adopt modular design to build multiple modules, each module adopts standardized design and is called in the V-shaped development and testing left shift; During the build process, follow the software development process; Perform version control during development and maintenance; Scripted configuration and dependency management through automated build and deployment; Cross-platform and portable; Perform performance optimization and resource management.

2. The tool chain according to claim 1, characterized in that: The V-shaped development and testing shift left includes: In the big V-shaped development process, system personnel or developers and testers jointly participate in each stage of requirement analysis, system design, architecture design and module design. Each stage forms its own small V-shaped process to carry out continuous integration and testing of the software to ensure that every change in the software development process can be verified and tested in a timely manner.

3. The tool chain according to claim 1, characterized in that: Each module in the plurality of modules is responsible for a specific function or task; The modular design is used to make the tool chain construction more flexible, easy to expand and maintain; The standardized design includes the standardization of data interfaces, data formats and communication protocols to ensure effective integration and interaction between different modules.

4. The tool chain according to claim 1, characterized in that: The software development process includes software requirement analysis, design, coding, testing and deployment; The software development process is followed to ensure the quality and stability of the tool chain; Version control is used to help teams work together, manage code changes, and track and fix problems.

5. The tool chain according to claim 1, characterized in that: The automated construction and deployment are implemented through build scripts and continuous integration / continuous deployment tools to improve development efficiency and reduce human errors; The scripted configuration is used to conveniently manage the configuration information of the toolchain; The configuration information includes environment variables and database connections.

6. The tool chain according to claim 1, characterized in that: The dependency management includes dependency resolution and version compatibility: The dependency parsing is used to automatically parse and install dependencies during the toolchain construction process, wherein the dependencies include multiple external libraries or tools; The version compatibility is used to regularly check and update the dependencies to avoid version conflicts or compatibility issues.

7. The tool chain according to claim 1, characterized in that: The cross-platform and portability include: The tool chain and its dependencies are encapsulated into an independent container using containerization technology to achieve seamless cross-platform deployment and operation, ensuring that the tool chain runs on different operating systems and hardware platforms.

8. The tool chain according to claim 1, characterized in that: The performance optimization and resource management include: Analyze the performance of the tool chain, identify bottlenecks and optimize them to improve the efficiency of the tool chain operation; Reasonably allocate and manage system resources to ensure stable operation and efficient execution of the tool chain; The system resources include CPU, memory, and disk space.

9. The tool chain according to claim 3, characterized in that: Standardization of data interfaces, data formats, and communication protocols to ensure effective integration and interaction between different modules, including: Use RESTFul Web API data interface for data access to ensure effective integration and interaction between different modules; The RESTFul Web API data interface complies with international standard general specifications and is used to obtain and transmit data to all third-party development and testing tools.

10. The tool chain according to claim 9, characterized in that: The third-party development and testing tools include third-party development tools, testing tools, customized software and self-developed programs; The RESTFul Web API is created using the OData standard protocol.

Images