A function-decoupled digital cockpit CI / CD double-track quality management and control system and method

Abstract

The application discloses a function-decoupled digital cockpit CI / CD double-track quality management and control system and method, and belongs to the technical field of intelligent cockpit software development. The method comprises the following steps: responding to a code writing request, performing static checking of coding specifications and syntax errors; rejecting unqualified codes and rectifying them by the development end, and positioning code problems if the codes are qualified; generating a review report for manual review if the codes are qualified, and entering CI / CD compilation and deployment if the review is passed, otherwise, rectification is prompted and the result is fed back. The application avoids repeated checking by decoupling the functions of modules, shortens the pipeline cycle, and adapts to high-frequency iteration of cockpit software; the application is consistent with automobile safety specifications to realize double-layer quality management and control, improve the code qualification rate, build a progressive quality access control, balance development efficiency and operation safety, adapt to existing pipelines, has low deployment cost, supports personalized configuration of rules, forms a checking-review-optimization closed loop, and continuously improves the quality management and control capability of digital cockpit software.

Description

Technical Field

[0001] This application relates to the field of intelligent cockpit software development technology, and in particular to a functionally decoupled digital cockpit CI / CD dual-track quality control system, a functionally decoupled digital cockpit CI / CD dual-track quality control method, electronic equipment, and storage medium. Background Technology

[0002] With the rapid development of automotive intelligence and connectivity, the digital cockpit has become the core interactive carrier of automobiles. Its software system complexity is constantly increasing, involving the collaborative work of multiple modules such as in-vehicle infotainment, driver assistance, and body control. This places stringent requirements on the software's functional safety, coding standards, logical rationality, and cross-module compatibility. The CI / CD (Continuous Integration / Continuous Delivery) pipeline, as the core support in the digital cockpit software development process, plays a crucial role in code quality control, automated verification, and efficient delivery. Its quality control capabilities directly determine the reliability and security of the digital cockpit software.

[0003] Currently, quality control in traditional digital cockpit CI / CD pipelines often adopts a single architecture model of "static inspection and code review coupling". That is, static inspection tools and code review processes are bound together, and the two share some verification logic without clear functional boundary division. This is the mainstream technical solution in the industry.

[0004] The existing technology has the following shortcomings, all of which can be solved by the present invention:

[0005] 1. Functional coupling leads to inefficiency: The scope of static inspection and code review overlaps, and repetitive verification work consumes a lot of computing resources, resulting in an excessively long CI / CD pipeline execution cycle, which is difficult to adapt to the high-frequency iteration development needs of digital cockpit software. The core reason for this problem is that the functional boundaries of the two are not clearly defined, resulting in wasted resources.

[0006] 2. Insufficient verification targeting: The traditional architecture has not been customized to adapt to the characteristics of the digital cockpit scenario. Static checks do not fully comply with functional safety specifications such as MISRA and ISO 26262 in the automotive industry. Code reviews rely heavily on manual work, which makes it difficult to cover deep quality issues such as logical rationality and cross-module compatibility. In addition, manual reviews are inefficient, subjective, and prone to omissions. The main reasons are the lack of customized verification rules adapted to the automotive scenario and the lack of efficient intelligent review methods.

[0007] 3. Inadequate quality access control mechanism: The results of static inspection and code review have not formed an effective progressive collaborative control, lack clear joint judgment logic, and cannot accurately distinguish between different levels of quality problems. Either the overly strict requirements lead to a decrease in development efficiency, or the lax control allows unqualified code to flow into subsequent stages, which in turn causes problems such as digital cockpit software functional failures and security risks. The core reason is that a scientific dual-track result joint judgment mechanism has not been established, and the collaborative control between the two cannot be achieved.

[0008] In addition, although some existing technologies have attempted to introduce AI-assisted code review or optimize static inspection processes, none of them have achieved functional decoupling between static inspection and AI review, nor have they built a highly adaptable dual-track quality control system to address the core needs of multi-module collaboration and functional safety compliance in digital cockpits. They cannot fundamentally solve the above-mentioned technical pain points, and in practical applications, there is still a problem of balancing efficiency and quality. Summary of the Invention

[0009] In view of this, the purpose of the present invention is to provide a functionally decoupled digital cockpit CI / CD dual-track quality control system, a functionally decoupled digital cockpit CI / CD dual-track quality control method, electronic equipment and storage medium, which aims to address one of the technical problems in the prior art, namely, low efficiency, insufficient targeting, unclear judgment logic and inability to adapt to multi-module collaborative scenarios.

[0010] This invention provides the following solution:

[0011] According to one aspect of the present invention, a functionally decoupled digital cockpit CI / CD dual-track quality control system is provided, comprising:

[0012] Architecture layer, verification layer, access control layer, and data interaction layer;

[0013] The architecture layer is used to achieve the overall deployment of the system's dual-track architecture and the complete decoupling of business functions;

[0014] The verification layer is used to perform specific code quality verification tasks and provides dedicated verification criteria for the architecture layer.

[0015] The access control layer is used to determine quality based on the verification results of the verification layer and control the flow of code in the CI / CD pipeline.

[0016] The data interaction layer is used to realize data transmission and interaction between various modules, and to provide standardized data interaction interfaces.

[0017] Furthermore, the architecture layer includes: a static analysis module and a large model intelligent review module;

[0018] The static checking module is used to perform low-level static checks on coding standard compliance and syntax errors.

[0019] This is used to dynamically adjust the rule activation status and verification thresholds based on the security level requirements of different functional modules in the digital cockpit, as well as subsequent verifications triggered by the large model intelligent review module after the underlying static verification is passed.

[0020] The large-scale intelligent review module is used to obtain the dependencies between multiple modules. It builds a proprietary knowledge base by accessing the digital cockpit software requirements document, architecture design document, and cross-module interface definition document to adapt to the multi-module collaboration scenario of the digital cockpit. It obtains the verification results of the static inspection module through the data interaction layer, and at the same time completes the division of responsibilities and functional decoupling with the static inspection module.

[0021] Furthermore, the verification layer includes:

[0022] Static validation rule base and intelligent review rule base;

[0023] The static validation rule base specifically includes: required rules and recommended rules.

[0024] The mandatory rules include: prohibiting uninitialized variables, prohibiting dynamic memory allocation, and prohibiting array out-of-bounds access;

[0025] Recommended rules include: consistent coding style, mandatory comments, and avoiding magic numbers, in order to standardize coding style and improve code maintainability;

[0026] The intelligent review rule base specifically includes: logical rationality verification rules, requirement matching degree verification rules, functional safety risk verification rules, and cross-module adaptability verification rules;

[0027] Logical rationality verification rules are used to detect logical contradictions, infinite loops, and missing exception handling in the code;

[0028] Requirements matching verification rules are used to compare the consistency between the code implementation and the requirements document;

[0029] Functional safety risk verification rules are used to identify potential safety hazards that violate preset specifications;

[0030] Cross-module compatibility verification rules are used to combine manual review feedback with historical verification data to detect abnormal interface calls and data interaction errors between different modules.

[0031] Furthermore, the access control layer includes:

[0032] A dual-track result joint judgment unit and a manual review auxiliary unit;

[0033] The dual-track result joint judgment unit is used to execute the preset joint access control mechanism to jointly judge the verification results of the static inspection module and the large model intelligent review module.

[0034] If any module fails the verification, the code rejection is triggered directly, preventing the unqualified code from flowing into the subsequent stages of the CI / CD pipeline;

[0035] The code is allowed to proceed to the manual review stage only if both module verification results are satisfactory.

[0036] The manual review auxiliary unit is used to summarize and organize the verification results and problem location information of the static inspection module and the AI ​​large model intelligent review module, generate a visual review report, and feed back the manual review results and modification suggestions to the large model intelligent review module to optimize the review rules and model parameters, realize the continuous iteration of review capabilities, and build a closed-loop management and control mechanism.

[0037] Furthermore, the data interaction layer includes:

[0038] Data interaction interface;

[0039] The data interaction interface is used to adopt the standardized RESTful protocol and configure AES data encryption and verification mechanisms.

[0040] Furthermore, the data interaction layer also includes:

[0041] Data interaction content;

[0042] The data interaction content specifically includes the verification results between the static inspection module and the large model intelligent review module, the transmission of verification logs, the verification results between the verification layer and the access control layer, and the transmission of problem location information;

[0043] Furthermore, the data interaction layer is also used to record the interaction logs of each module, which include: data transmission time, data type, verification result, and interaction status.

[0044] According to a second aspect of the present invention, a dual-track quality control method for a functionally decoupled digital cockpit CI / CD system is provided, comprising the following steps:

[0045] In response to a write request, the static validation rule library is invoked to perform coding standard compliance and syntax error validation on the code, generating static check results and validation logs;

[0046] If the static check result is unsatisfactory, code rejection will be triggered, and the development team will be stopped from modifying the code based on the verification log.

[0047] If the static check result is qualified, the intelligent review rule library is called to conduct a second review of the code, and generate the second review result and problem location information.

[0048] Based on the results of the second review, if the second review is satisfactory, a visual review report will be generated and submitted to the manual review platform.

[0049] Complete the code review based on the review report. If the review is successful, the code will enter the compilation and deployment phase of the CI / CD pipeline.

[0050] If the review fails, the developer will be prompted to make modifications.

[0051] The review results will be provided at the same time.

[0052] According to three aspects of the present invention, an electronic device is provided, comprising: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0053] The memory stores a computer program, which, when executed by a processor, causes the processor to perform steps of a functionally decoupled digital cockpit CI / CD dual-track quality control method.

[0054] According to four aspects of the present invention, a computer-readable storage medium is provided that stores a computer program executable by an electronic device, which, when run on the electronic device, causes the electronic device to perform the steps of a functionally decoupled digital cockpit CI / CD dual-track quality control method.

[0055] Compared with the prior art, the present invention has the following advantages:

[0056] This invention achieves functional decoupling, allowing the AI ​​review module to skip repetitive verification work already completed by static checks, thus avoiding resource waste and significantly shortening the execution cycle of the CI / CD pipeline. Actual testing shows that the pipeline execution efficiency is greatly improved, making it suitable for the high-frequency iteration development needs of digital cockpit software.

[0057] This invention adapts to automotive MISRA and ISO 26262 standards through a static inspection module, eliminating potential security risks in basic coding from the source; the AI ​​intelligent review module focuses on deep-seated quality issues and improves review accuracy by combining a proprietary knowledge base, further enhancing the quality pass rate of digital cockpit software code and solving the problems of low efficiency and numerous omissions in manual review.

[0058] This invention constructs a progressive access control mechanism of "static inspection pre-trigger and dual-track result joint judgment", which clarifies the rejection conditions for unqualified codes and the release logic for qualified codes. This avoids the decline in development efficiency caused by excessive strictness, eliminates the security risks caused by lax control, and reduces the failure rate after the digital cockpit software goes online.

[0059] This invention adapts to existing CI / CD pipeline deployment environments through a data interaction interface, and can directly interface with existing code repositories, compilation tools, and deployment platforms without large-scale modifications, reducing deployment costs and implementation difficulty; at the same time, it supports dynamic rule updates and personalized configurations, adapting to the digital cockpit development needs of different vehicle models and different safety levels, making it widely applicable;

[0060] This invention achieves continuous optimization of AI review rules and model parameters through a manual review result feedback mechanism, forming a closed-loop control of "verification-review-optimization" to continuously improve quality control capabilities. Attached Figure Description

[0061] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0062] Figure 1 This is a structural diagram of a functionally decoupled digital cockpit CI / CD dual-track quality control system provided by one or more embodiments of the present invention.

[0063] Figure 2 This is a flowchart of a functionally decoupled digital cockpit CI / CD dual-track quality control method provided by one or more embodiments of the present invention.

[0064] Figure 3 This is an architecture diagram of a functionally decoupled digital cockpit CI / CD dual-track quality control architecture in a specific embodiment of the present invention.

[0065] Figure 4 This is a schematic diagram of the dual-track verification process in a specific embodiment of the present invention.

[0066] Figure 5 This is a schematic diagram of the joint access control determination logic in a specific embodiment of the present invention.

[0067] Figure 6 This is a block diagram of an electronic device for a functionally decoupled digital cockpit CI / CD dual-track quality control method provided by one or more embodiments of the present invention. Detailed Implementation

[0068] The technical solution of the present invention will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0069] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the application. The singular forms “a,” “said,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms, and “multiple” generally includes at least two unless the context clearly indicates otherwise.

[0070] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0071] It should be understood that although the terms first, second, third, etc., may be used in the embodiments of this application, these descriptions should not be limited to these terms. These terms are only used to distinguish the descriptions. For example, first may also be referred to as second without departing from the scope of the embodiments of this application, and similarly, second may also be referred to as first.

[0072] Depending on the context, the words "if" or "if" as used here can be interpreted as "when," "when," "in response to determination," or "in response to detection." Similarly, depending on the context, the phrases "if determination" or "if detection (of the stated condition or event)" can be interpreted as "when determination," "in response to determination," "when detection (of the stated condition or event)," or "in response to detection (of the stated condition or event)."

[0073] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that an article or device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such an article or device. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the article or device that includes said element.

[0074] Figure 1 This is a structural diagram of a functionally decoupled digital cockpit CI / CD dual-track quality control system provided by one or more embodiments of the present invention.

[0075] like Figure 1 As shown, it includes:

[0076] Architecture layer, verification layer, access control layer, and data interaction layer;

[0077] The architecture layer is used to achieve the overall deployment of the system's dual-track architecture and the complete decoupling of business functions;

[0078] Specifically, the architecture layer includes: a static analysis module and a large model intelligent review module;

[0079] The static checking module is used to perform low-level static checks on coding standard compliance and syntax errors.

[0080] This is used to dynamically adjust the rule activation status and verification thresholds based on the security level requirements of different functional modules in the digital cockpit, as well as subsequent verifications triggered by the large model intelligent review module after the underlying static verification is passed.

[0081] The large-scale intelligent review module is used to obtain the dependencies between multiple modules. It builds a proprietary knowledge base by accessing the digital cockpit software requirements document, architecture design document, and cross-module interface definition document to adapt to the multi-module collaboration scenario of the digital cockpit. It obtains the verification results of the static inspection module through the data interaction layer, and at the same time completes the division of responsibilities and functional decoupling with the static inspection module.

[0082] The verification layer is used to perform specific code quality verification tasks and provides dedicated verification criteria for the architecture layer.

[0083] Specifically, the verification layer includes:

[0084] Static validation rule base and intelligent review rule base;

[0085] The static validation rule base specifically includes: required rules and recommended rules.

[0086] The mandatory rules include: prohibiting uninitialized variables, prohibiting dynamic memory allocation, and prohibiting array out-of-bounds access, in order to prevent coding problems that could lead to functional safety risks;

[0087] Recommended rules include: consistent coding style, mandatory comments, and avoiding magic numbers, in order to standardize coding style and improve code maintainability;

[0088] Specifically, magic values ​​are literal constants in program code that are hard-coded without semantic naming or comments. They belong to non-standard hard-coded literals in programming and are a form of code writing that lacks semantic abstraction and maintainable design.

[0089] The intelligent review rule base specifically includes: logical rationality verification rules, requirement matching degree verification rules, functional safety risk verification rules, and cross-module adaptability verification rules;

[0090] Logical rationality verification rules are used to detect logical contradictions, infinite loops, and missing exception handling in the code;

[0091] Requirements matching verification rules are used to compare the consistency between the code implementation and the requirements document;

[0092] Functional safety risk verification rules are used to identify potential safety hazards that violate preset specifications;

[0093] Cross-module compatibility verification rules are used to combine manual review feedback with historical verification data to detect abnormal interface calls and data interaction errors between different modules.

[0094] The access control layer is used to determine quality based on the verification results of the verification layer and control the flow of code in the CI / CD pipeline.

[0095] Specifically, the access control layers include:

[0096] A dual-track result joint judgment unit and a manual review auxiliary unit;

[0097] The dual-track result joint judgment unit is used to execute the preset joint access control mechanism to jointly judge the verification results of the static inspection module and the large model intelligent review module.

[0098] If any module fails the verification, the code rejection is triggered directly, preventing the unqualified code from flowing into the subsequent stages of the CI / CD pipeline;

[0099] The code is allowed to proceed to the manual review stage only if both module verification results are satisfactory.

[0100] The manual review auxiliary unit is used to summarize and organize the verification results and problem location information of the static inspection module and the AI ​​large model intelligent review module, generate a visual review report, and feed back the manual review results and modification suggestions to the large model intelligent review module to optimize the review rules and model parameters, realize the continuous iteration of review capabilities, and build a closed-loop management and control mechanism.

[0101] The data interaction layer is used to realize data transmission and interaction between various modules, and to provide standardized data interaction interfaces.

[0102] Specifically, the data interaction layer includes:

[0103] Data interaction interface;

[0104] The data interaction interface is used to adopt the standardized RESTful protocol and configure AES data encryption and verification mechanisms.

[0105] The modules interact with each other and transmit commands through a standardized RESTful communication interface;

[0106] Data encryption and integrity verification mechanisms are used to encrypt and verify the legitimacy of transmitted data;

[0107] In this embodiment, the AES algorithm can be used as the preferred encryption algorithm, or other symmetric encryption algorithms such as SM4 can be used.

[0108] The data interaction layer also includes:

[0109] Data interaction content;

[0110] The data interaction content specifically includes the verification results between the static inspection module and the large model intelligent review module, the transmission of verification logs, the verification results between the verification layer and the access control layer, and the transmission of problem location information;

[0111] Furthermore, the data interaction layer is also used to record the interaction logs of each module, which include: data transmission time, data type, verification result, and interaction status.

[0112] Specifically, through functional decoupling design, the AI ​​review module can skip repetitive verification work already completed by static checks, effectively avoiding resource waste and significantly shortening the execution cycle of the CI / CD pipeline. Actual testing has shown that pipeline execution efficiency has been further improved, making it well-suited to the high-frequency iteration development needs of digital cockpit software. Meanwhile, the static check module is compatible with automotive MISRA and ISO 26262 standards, eliminating basic coding security risks at the source. The AI ​​intelligent review module focuses on deep-seated quality issues, combining a proprietary knowledge base to improve review accuracy, further increasing the quality pass rate of digital cockpit software code and effectively solving the industry pain points of low efficiency and numerous omissions in manual reviews. Furthermore, by constructing a progressive access control mechanism of "static check pre-triggered, dual-track result joint judgment," the rejection conditions for unqualified code and the release logic for qualified code are clearly defined. This avoids both excessive stringency leading to decreased development efficiency and lax control causing security risks, effectively reducing the failure rate of digital cockpit software after its deployment.

[0113] On the other hand, the data interaction interface of this embodiment is compatible with the existing CI / CD pipeline deployment environment and can directly interface with existing code repositories, compilation tools, and deployment platforms without large-scale modifications, significantly reducing deployment costs and implementation difficulties. At the same time, it supports dynamic rule updates and personalized configurations, and can adapt to the digital cockpit development needs of different vehicle models and different safety levels, making it widely applicable.

[0114] Finally, through the feedback mechanism of manual review results, the AI ​​review rules and model parameters are continuously optimized, forming a closed-loop control of "verification-review-optimization". This can sustainably improve the quality control capabilities of digital cockpit software, and comprehensively improve the development efficiency, product quality and control level of digital cockpit software, which has extremely high practicality and application value.

[0115] It is worth noting that although only some basic functional modules are disclosed in this embodiment, it does not mean that the composition of this system is limited to the above-mentioned basic functional modules. On the contrary, what this embodiment intends to express is that, based on the above-mentioned basic functional modules, those skilled in the art can arbitrarily add one or more functional modules in combination with existing technology to form an infinite number of embodiments or technical solutions. That is to say, this system is open rather than closed. The fact that this embodiment only discloses a few basic functional modules does not mean that the scope of protection of the claims of this invention is limited to the disclosed basic functional modules. At the same time, for the convenience of description, the above device is described separately according to its functions as various units and modules. Of course, in implementing this invention, the functions of each unit and module can be implemented in one or more software and / or hardware.

[0116] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0117] Figure 2 This is a flowchart of a functionally decoupled digital cockpit CI / CD dual-track quality control method provided by one or more embodiments of the present invention.

[0118] like Figure 2 As shown, it includes the following steps:

[0119] Step S1: In response to the write request, call the static validation rule library to perform coding standard compliance and syntax error validation on the code, and generate static check results and validation logs;

[0120] Step S2: If the static check result is unqualified, code rejection is triggered, and the development side is stopped from modifying the code according to the verification log.

[0121] If the static check result is qualified, the intelligent review rule library is called to conduct a second review of the code, and generate the second review result and problem location information.

[0122] Step S3: Based on the results of the second review, if the second review result is qualified, generate a visual review report and submit it to the manual review terminal;

[0123] Step S4: Complete the code review based on the review report. If the review is successful, the code will enter the compilation and deployment phase of the CI / CD pipeline.

[0124] If the review fails, the developer will be prompted to make modifications.

[0125] Step S5, and simultaneously provide feedback on the review results.

[0126] Figure 3 This is an architecture diagram of a functionally decoupled digital cockpit CI / CD dual-track quality control architecture in a specific embodiment of the present invention.

[0127] like Figure 3 As shown, the quality control architecture includes an architecture layer, a verification layer, an access control layer, and a data interaction layer. These layers work together to form a complete quality control system. The specific structure and functions of each layer are as follows:

[0128] The architecture layer, as the core of the entire architecture, is used to realize the overall deployment and functional decoupling of the dual-track architecture. It includes the static inspection module and the AI ​​large model intelligent review module. The two form a progressive collaborative relationship of front-end and back-end. That is, the static inspection module serves as a prerequisite for the AI ​​large model intelligent review module. The AI ​​large model intelligent review module is only triggered to start verification after the static inspection module completes the verification and the result is qualified, thus avoiding invalid verification.

[0129] In one embodiment, the static inspection module is developed using the sonar / static tool and is compatible with commonly used automotive development languages ​​such as C, C++, and Python for digital cockpit software. Its core functions focus only on coding standard compliance and syntax error checking, without involving deep quality issues. This module supports dynamic updates and personalized configuration of rules, and can flexibly adjust the activation status and verification threshold of rules according to the security level requirements of different modules in the digital cockpit (such as the driver assistance module and the in-vehicle infotainment module).

[0130] In one embodiment, the AI ​​large-scale intelligent review module employs a hybrid expert model (MoE) that supports contextual understanding of ultra-long code, specifically the DeepSeek Coder-33B model, which supports understanding ultra-long code with 2 million tokens and can accurately capture the dependencies between multiple modules of the digital cockpit. It builds a proprietary knowledge base by accessing the digital cockpit software's requirements documents, architecture design documents, and cross-module interface definition documents, achieving accurate adaptation to multi-module collaborative scenarios in the digital cockpit. Its core functions focus solely on verifying logical rationality, requirement matching, functional safety risks, and cross-module compatibility. Furthermore, it obtains the verification results from the static inspection module through the data interaction layer, skipping repetitive verification work such as coding standards and syntax errors, and only performing verification tasks within its own scope of responsibility, thus improving verification efficiency.

[0131] Verification layer: Used to perform specific code quality verification tasks, providing dedicated verification criteria for the two modules of the architecture layer, including a static verification rule base and an AI intelligent review rule base. The two rule bases are independent of each other to avoid rule confusion and duplication.

[0132] In one embodiment, the static validation rule base is adapted to the automotive industry's MISRA C:2012 and ISO 26262-6 standards using the sonar / static tool. The rules are divided into required rules and recommended rules. The required rules include 120 rules such as prohibiting uninitialized variables, prohibiting dynamic memory allocation, and prohibiting array out-of-bounds access. These correspond to the mandatory coding guidelines in the MISRA and ISO 26262 standards and are used to eliminate coding problems that may cause functional safety risks. The recommended rules include 80 rules such as unifying coding style, mandating comments, and avoiding magic numbers, used to standardize coding style and improve code maintainability. This rule base supports dynamic updates and can be flexibly adjusted according to industry standard updates and actual development needs.

[0133] In one embodiment, the AI-powered intelligent review rule base is built to address the multi-module collaborative characteristics of the digital cockpit. It includes four core rule categories, corresponding to the four core functions of the AI ​​large-scale intelligent review module: Logical rationality verification rules, used to detect issues such as logical contradictions, infinite loops, and missing exception handling in the code; requirement matching verification rules, used to compare the consistency between the code implementation and the requirement document (e.g., whether the preset voice interaction function is implemented); functional safety risk verification rules, used to identify potential safety hazards that violate the ISO 26262 standard (e.g., failure to implement fault redundancy mechanisms); and cross-module adaptability verification rules, used to detect issues such as abnormal interface calls and data interaction errors between different modules. This rule base can be automatically optimized by the AI ​​large-scale intelligent review module by combining manual review feedback and historical verification data, continuously improving the accuracy of the review.

[0134] Access control layer: Used to determine quality based on the verification results of the verification layer, and control the flow of code in the CI / CD pipeline, including a dual-track result joint judgment unit and a manual review auxiliary unit;

[0135] In one embodiment, the dual-track result joint judgment unit executes a preset joint access control mechanism. The specific judgment logic is as follows: if the static inspection module verification result is unqualified (recorded as -1) or the AI ​​large model intelligent review module verification result is unqualified (recorded as -1), code rejection is directly triggered, prohibiting unqualified code from flowing into the subsequent CI / CD stage; only when the static inspection module verification result is qualified (recorded as +1) and the AI ​​large model intelligent review module verification result is qualified (recorded as +1) is the code allowed to enter the manual review stage. Only after passing the manual review can it enter the next stage of the CI / CD pipeline. This judgment logic clarifies the collaborative relationship of the dual-track verification results and solves the problem of the imperfection of the existing access control mechanism.

[0136] In one embodiment, the manual review assistance unit is used to summarize and organize the verification results and problem location information (such as the line number of the violation code, the description of the violation rule, and the risk level) of the static inspection module and the AI ​​large model intelligent review module, and generate a visual review report to help manual reviewers quickly locate problems and improve review efficiency. At the same time, the manual review results (pass / rejection and modification suggestions) can be fed back to the AI ​​large model intelligent review module to optimize the AI ​​review rules and model parameters, forming a closed-loop management of "verification-review-optimization".

[0137] Data Interaction Layer: Used to realize data transmission and interaction between various modules, ensuring the accuracy, efficiency and security of data transmission, and has standardized data interaction interfaces;

[0138] In one embodiment, the data interaction interface adopts a standardized RESTful protocol and is equipped with an AES data encryption and verification mechanism to ensure the security and integrity of transmitted data and prevent data leakage or tampering. It can directly interface with the existing code repository, compilation tools, and deployment platform of the digital cockpit CI / CD pipeline without requiring large-scale modifications to the existing pipeline, thus reducing the difficulty of implementation.

[0139] In one embodiment, the data interaction content includes the transmission of verification results and verification logs between the static inspection module and the AI ​​large model intelligent review module, and the transmission of verification results and problem location information between the verification layer and the access control layer. At the same time, the data interaction layer records the interaction logs of each module, including information such as data transmission time, data type, verification results, and interaction status, for subsequent quality traceability and problem investigation, meeting the requirements of ISO 26262 for full lifecycle traceability.

[0140] In one embodiment, see Figure 4 and Figure 5 ;

[0141] Includes the following steps:

[0142] Step 1: After the developers complete the digital cockpit software code, they submit the code to the CI / CD pipeline's code repository;

[0143] Step 2: The code repository triggers the static analysis module to start. The static analysis module calls the rules in the static verification rule base and uses the sonar / static tool to check the code for coding style compliance and syntax errors, generating static analysis results (pass / fail) and verification logs;

[0144] Step 3: The dual-track result joint judgment unit obtains the static inspection result. If the result is unqualified (-1), code rejection is triggered, and the developers are notified to modify the code according to the verification log. After the modification is completed, the code is resubmitted. If the result is qualified (+1), the static inspection result and verification log are transmitted to the AI ​​large model intelligent review module through the data interaction interface, triggering the AI ​​review to start.

[0145] Step 4: After obtaining the static inspection results, the AI ​​large model intelligent review module skips the repetitive verification work such as coding standard and syntax error, calls the rules in the AI ​​intelligent review rule base, and performs logical rationality, requirement matching degree, functional safety risk, and cross-module adaptability verification on the code, generating AI review results (pass / fail) and problem location information.

[0146] Step 5: The dual-track result joint judgment unit obtains the AI ​​review result. If the result is unqualified (-1), the code rejection is triggered, and the developers are notified to modify the code according to the problem location information. If the result is qualified (+1), the manual review assistance unit is triggered to generate a visual review report and submit it to the manual reviewer.

[0147] Step 6: The human reviewers complete the code review based on the review report. If the review is successful, the code enters the compilation and deployment stage of the CI / CD pipeline; if the review is rejected, the developers are notified to modify and resubmit; at the same time, the human review results are fed back to the AI ​​large model intelligent review module to optimize the AI ​​review rules and model parameters.

[0148] Step 7: The data interaction layer records the interaction logs throughout the entire process for subsequent quality traceability and problem investigation.

[0149] Specifically, by decoupling static inspection from AI intelligent review at the architecture layer and clarifying the functional boundaries of the two, the AI ​​review module skips repetitive verification work, reduces the consumption of computing resources, directly shortens the pipeline execution cycle, and achieves an efficiency improvement of more than 30%.

[0150] The static validation rule base is adapted to the functional safety specifications of the automotive industry, eliminating potential security risks in basic coding from the source; the AI ​​intelligent review module combines a proprietary knowledge base with a long contextual understanding capability to accurately cover deep quality issues, replace some manual reviews, solve the shortcomings of manual reviews, and improve the code quality pass rate by more than 40%.

[0151] The clear logic of the dual-track result joint judgment unit enables progressive control of "basic verification - in-depth review - manual review", which avoids both excessive strictness and lax control, and reduces the software failure rate.

[0152] Standardized RESTful data interaction interfaces adapt to existing pipelines without requiring large-scale modifications, reducing deployment costs; dynamic rule updates and personalized configuration functions adapt to different scenario requirements, improving applicability.

[0153] The results of manual review are fed back to the AI ​​review module, enabling continuous optimization of rules and models and ensuring that quality control capabilities are constantly improved.

[0154] Figure 6 This is a block diagram of an electronic device for a functionally decoupled digital cockpit CI / CD dual-track quality control method provided by one or more embodiments of the present invention.

[0155] like Figure 6 As shown, this application provides an electronic device, including: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0156] The memory stores a computer program that, when executed by a processor, causes the processor to perform the steps of a functionally decoupled digital cockpit CI / CD dual-track quality control method.

[0157] This application also provides a computer-readable storage medium storing a computer program executable by an electronic device, which, when run on the electronic device, causes the electronic device to perform the steps of a functionally decoupled digital cockpit CI / CD dual-track quality control method.

[0158] For the sake of simplicity, the method embodiments are described as a series of actions. However, those skilled in the art should understand that the embodiments of the present invention are not limited to the described order of actions, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions involved are not necessarily essential to the embodiments of the present invention.

[0159] As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in various embodiments or some parts of the embodiments of this application.

[0160] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A functionally decoupled digital cockpit CI / CD dual-track quality control system, characterized in that, include: Architecture layer, verification layer, access control layer, and data interaction layer; The architecture layer is used to realize the overall deployment of the system's dual-track architecture and the complete decoupling of business functions; The verification layer is used to perform specific code quality verification tasks and provide dedicated verification basis for the architecture layer; The access control layer is used to determine the quality based on the verification result of the verification layer and control the flow of code in the CI / CD pipeline. The data interaction layer is used to realize data transmission and interaction between modules, and to provide standardized data interaction interfaces.

2. The functionally decoupled digital cockpit CI / CD dual-track quality control system according to claim 1, characterized in that, The architecture layer includes: a static inspection module and a large model intelligent review module; The static checking module is used to perform low-level static checks on coding standard compliance and syntax errors; This is used to dynamically adjust the rule activation status and verification thresholds based on the security level requirements of different functional modules in the digital cockpit, as well as subsequent verifications triggered by the large model intelligent review module after the underlying static verification is passed. The large model intelligent review module is used to obtain the dependencies between multiple modules, and build a proprietary knowledge base by accessing the digital cockpit software requirements document, architecture design document and cross-module interface definition document to adapt to the multi-module collaboration scenario of the digital cockpit. The verification results of the static inspection module are obtained through the data interaction layer, and the responsibilities and functions of the static inspection module are separated and decoupled.

3. The functionally decoupled digital cockpit CI / CD dual-track quality control system according to claim 1, characterized in that, The verification layer includes: Static validation rule base and intelligent review rule base; Specifically, the static validation rule base includes: mandatory rules and recommended rules. The mandatory rules include: prohibiting uninitialized variables, prohibiting dynamic memory allocation, and prohibiting array out-of-bounds access; The recommended rules include: unifying coding style and mandating the addition of comments, in order to standardize coding style and improve code maintainability; The intelligent review rule base specifically includes: logical rationality verification rules, requirement matching degree verification rules, functional safety risk verification rules, and cross-module adaptability verification rules; The aforementioned logic rationality verification rules are used to detect logical contradictions, infinite loops, and missing exception handling in the code. The requirement matching verification rules are used to compare the consistency between the code implementation and the requirement document; The functional safety risk verification rules are used to identify potential safety hazards that violate preset specifications; The cross-module compatibility verification rules are used to detect interface call anomalies and data interaction errors between different modules by combining manual review feedback and historical verification data.

4. The functionally decoupled digital cockpit CI / CD dual-track quality control system according to claim 1, characterized in that, The access control layer includes: A dual-track result joint judgment unit and a manual review auxiliary unit; The dual-track result joint judgment unit is used to execute a preset joint access control mechanism to jointly judge the verification results of the static inspection module and the large model intelligent review module. If the verification result of either module is unqualified, the code rejection is directly triggered, and the unqualified code is prohibited from flowing into the subsequent stages of the CI / CD pipeline. The code is allowed to enter the manual review stage only when the verification results of both modules are qualified. The manual review auxiliary unit is used to summarize and organize the verification results and problem location information of the static inspection module and the AI ​​large model intelligent review module, generate a visual review report, and feed back the manual review results and modification suggestions to the large model intelligent review module to optimize the review rules and model parameters, realize the continuous iteration of review capabilities, and build a closed-loop management and control mechanism.

5. The functionally decoupled digital cockpit CI / CD dual-track quality control system according to claim 1, characterized in that, The data interaction layer includes: Data interaction interface; The data interaction interface is used to adopt a common standard communication protocol and configure data encryption and verification mechanisms.

6. The functionally decoupled digital cockpit CI / CD dual-track quality control system according to claim 5, characterized in that, The data interaction layer also includes: Data interaction content; The data interaction content specifically includes the verification results between the static inspection module and the large model intelligent review module, the transmission of verification logs, the verification results between the verification layer and the access control layer, and the transmission of problem location information.

7. The functionally decoupled digital cockpit CI / CD dual-track quality control system according to claim 6, characterized in that, include: The data interaction layer is also used to record the interaction logs of each module. The interaction logs include: data transmission time, data type, verification result, and interaction status.

8. A functionally decoupled digital cockpit CI / CD dual-track quality control method, characterized in that, Includes the following steps: In response to a write request, the static validation rule base is invoked to perform coding standard compliance and syntax error validation on the code, generating static check results and validation logs; If the static check result is unqualified, code rejection is triggered, and the development team is stopped from modifying the code based on the verification log. If the static check result is qualified, the intelligent review rule library is called to perform a second review on the code, and generate the second review result and problem location information; Based on the results of the second review, if the results are satisfactory, a visual review report is generated and submitted to the manual review platform. Complete the code review based on the review report. If the review is successful, the code will enter the compilation and deployment phase of the CI / CD pipeline. If the review fails, the developer will be prompted to make modifications. The review results will be provided at the same time.

9. An electronic device, characterized in that, include: The processor, communication interface, memory, and communication bus are connected, with the processor, communication interface, and memory communicating with each other via the communication bus. The memory stores a computer program that, when executed by the processor, causes the processor to perform the steps of the functionally decoupled digital cockpit CI / CD dual-track quality control method as described in claim 8.

10. A computer-readable storage medium, characterized in that, It stores a computer program executable by an electronic device, which, when run on the electronic device, causes the electronic device to perform the steps of the functionally decoupled digital cockpit CI / CD dual-track quality control method as described in claim 8.

Images