Multi-dimensional visual analysis system and method for code review of in-vehicle infotainment system

Abstract

The invention discloses a multi-dimensional visual analysis system and method for code review of a vehicle-mounted infotainment system, and relates to the field of vehicle-mounted infotainment systems, and the system comprises a data collection layer, a core processing layer, a visual display layer and a user interaction layer. The data acquisition layer is used for acquiring multi-source heterogeneous data by being in butt joint with an external tool; the core processing layer is used for processing the collected various data sources through a code analysis engine, a dependency analysis engine, a risk assessment engine, a demand mapping engine and a view template engine; the processing comprises code analysis, dependency relationship analysis, risk quantitative evaluation, mapping of requirements, codes and test cases, and view template configuration; the visual display layer is used for generating and displaying data related to code review of the in-vehicle infotainment system; the user interaction layer is used for providing an operation interface for role customization, and role customization comprises multi-dimensional screening, interactive labeling, real-time cooperation and creation, storage and sharing of a self-defined template.

Description

Technical Field

[0001] This application relates to the field of vehicle infotainment systems, and in particular to a multi-dimensional visualization analysis system for vehicle infotainment system code review, a multi-dimensional visualization analysis method for vehicle infotainment system code review, electronic devices, and storage media. Background Technology

[0002] Current vehicle infotainment system code reviews largely rely on manual code reading, supplemented by simple class diagram tools. For example, SonarQube only provides a list of code quality data and lacks dynamic correlation display; traditional version control tools are difficult to intuitively present the code evolution path.

[0003] Problems include: low efficiency in understanding code structure, reliance on experience for assessing the impact of changes, lack of visual guidance for identifying security risks, and difficulty in adapting to the review needs of different roles. Summary of the Invention

[0004] In view of this, the purpose of the present invention is to provide a multi-dimensional visualization analysis system for vehicle infotainment system code review, a multi-dimensional visualization analysis method for vehicle infotainment system code review, an electronic device and a storage medium, in order to solve the technical problems in the prior art.

[0005] This invention provides the following solution: According to one aspect of the invention, a multi-dimensional visualization analysis system for vehicle infotainment system code review is provided, comprising:

[0006] Data acquisition layer, core processing layer, visualization layer, and user interaction layer;

[0007] The data acquisition layer is used to connect to external tools through a plug-in mechanism to collect data from multiple data sources.

[0008] The core processing layer is used to process various data sources collected through a code parsing engine, a dependency analysis engine, a risk assessment engine, a requirement mapping engine, and a view template engine.

[0009] Complete code parsing, dependency analysis, risk quantification and assessment, mapping of requirements to code and test cases, and view template configuration;

[0010] The visualization layer is used to generate and display data related to the code review of the vehicle infotainment system.

[0011] The user interaction layer is used to provide a customized user interface for each role.

[0012] Role customization includes multi-dimensional filtering, interactive annotation, real-time collaboration, and the creation, saving, and sharing of custom templates.

[0013] Furthermore, including:

[0014] External tools that can be integrated include: code repositories, requirements management tools, test case management systems, static code analysis tools, and performance analysis tools.

[0015] Furthermore, including:

[0016] The code parsing engine includes: performing lexical and syntactic analysis on the vehicle infotainment system code using the ANTLR tool to generate an AST tree;

[0017] Based on the AST tree, obtain the code elements and their inheritance and calling relationships.

[0018] Furthermore, including:

[0019] The workflow of a analytics engine includes:

[0020] The code elements and their inheritance and calling relationships are compiled, and a compilation log is generated.

[0021] Analyze the compilation logs to obtain the dependency information of each component;

[0022] Based on the dependency information of each component, obtain structured dependency data;

[0023] The structured dependency data is used to construct a dependency graph using a force-directed algorithm;

[0024] Furthermore, including:

[0025] The workflow of the risk assessment engine includes:

[0026] Receive code change data, compare the AST trees before and after the change using the diff algorithm, and identify newly added, deleted, and modified code nodes;

[0027] The code dependency graph built based on the dependency analysis engine uses a breadth-first search to traverse and determine the scope of modules affected by changes;

[0028] By combining the attributes and change types of the affected modules, a risk quantification model is constructed to generate a risk score of 0-10.

[0029] The risk score is associated with the corresponding code node and output to the visualization layer for risk visualization presentation.

[0030] Furthermore, including:

[0031] The demand mapping engine includes:

[0032] Establish a ternary mapping model, in which the requirement node stores the requirement ID, description and priority attributes, the code node is associated with the function implementation node in the AST tree, and the test case node stores the test case ID and input / output parameters;

[0033] Store the ternary mapping model data in a graph database;

[0034] Receive interaction requests from the visualization layer;

[0035] When a requirement node query is triggered, the associated code nodes and test case nodes are automatically retrieved, and coverage status data is output.

[0036] It calculates requirement coverage and test case execution rate, generates multi-dimensional filtering reports, and provides data support to the visualization layer.

[0037] Furthermore, including:

[0038] The visualization layer includes:

[0039] Visualizing 3D code structure and creating 3D spatiotemporal evolution maps based on WebGL technology;

[0040] Interactive dependency graphs and security risk heatmaps based on SVG technology;

[0041] It supports multi-granularity display control, and enables dynamic switching of visualization granularity from system level, module level to function level through slider control;

[0042] It receives code parsing, risk assessment, and requirement mapping data output from the core processing layer, and renders the corresponding visualization components in real time to ensure that the data and visualization views are updated synchronously.

[0043] Furthermore, including:

[0044] The core processing layer is also used to implement security risk visualization functions, specifically including:

[0045] The scan results from the integrated static code analysis tool and the OWASP ZAP tool are used to unify the vulnerability levels according to a preset standard, which includes high, medium and low vulnerability levels;

[0046] The vulnerability information is associated with the corresponding nodes in the code visualization diagram, with high-risk vulnerabilities marked in red, medium-risk vulnerabilities marked in yellow, and patched vulnerabilities marked in green.

[0047] For each vulnerable node, a link to the remediation guide is provided, offering code modification examples.

[0048] According to a second aspect of this application, a multi-dimensional visualization method for reviewing vehicle infotainment system code is provided, comprising the following steps:

[0049] Data acquisition steps: Connect to external tools through a plug-in mechanism to collect multi-source data and perform standardized processing;

[0050] Core processing steps: Perform lexical and syntactic analysis on the vehicle infotainment system code to extract code elements and their inheritance and calling relationships;

[0051] The code element relationships are compiled to generate logs, the logs are parsed to obtain structured dependency data, and a dependency graph is constructed using a force-directed algorithm;

[0052] By comparing the AST trees before and after the change, the change nodes are identified; by traversing the dependency graph, the scope of impact is assessed; and by combining module attributes and change types, a risk score is generated.

[0053] Establish a ternary mapping model and store it in a graph database, calculate the coverage and generate reports;

[0054] Based on the configuration file, the visibility, highlighting and layout rules of different roles are defined to generate customized view templates for the roles;

[0055] Visualization steps: Based on WebGL and SVG technologies, generate visual components that support multi-granularity display control;

[0056] User interaction steps: Provides a role-customized operation interface, supports multi-dimensional filtering, interactive annotation, real-time collaboration, and the creation, saving and sharing of custom templates, while recording review operations and generating review reports.

[0057] 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;

[0058] The memory stores a computer program, which, when executed by the processor, causes the processor to perform steps of a multi-dimensional visualization method for reviewing vehicle infotainment system code.

[0059] 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 multi-dimensional visualization method for reviewing vehicle system code.

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

[0061] This application improves review efficiency through multi-dimensional visualization, reduces change risks through dynamic correlation analysis, adapts customized templates to different scenarios, and shortens the code familiarization period for new members.

[0062] This application uses AST analysis and graph visualization, which allows reviewers to intuitively identify highly coupled modules and circular dependency issues, thus improving the efficiency of related analysis.

[0063] This application helps developers grasp the system architecture from a macro perspective through dynamic granularity control, while allowing developers to examine the code logic in detail.

[0064] This application solves the problem of data fragmentation in traditional tools by unifying the modeling of heterogeneous data such as code structure, version history, and requirements documents, enabling reviewers to analyze the code from a global perspective.

[0065] This application uses a combination of time and spatial structure to visually demonstrate the evolution of the codebase, helping teams quickly understand architectural changes and reducing knowledge transfer costs.

[0066] This application automatically assesses the potential impact of code changes using a graph traversal and risk quantification model, significantly improving accuracy compared to manual assessment.

[0067] This application achieves a personalized review experience by dynamically adjusting the visualization content based on user roles and review scenarios, thereby significantly improving work efficiency. Attached Figure Description

[0068] 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.

[0069] Figure 1 This is a structural diagram of a multi-dimensional visualization analysis system for vehicle infotainment system code review provided by one or more embodiments of the present invention.

[0070] Figure 2 This is a flowchart of a multi-dimensional visualization analysis method for vehicle infotainment system code review provided by one or more embodiments of the present invention.

[0071] Figure 3 This is a flowchart of a multi-dimensional visualization analysis method for vehicle infotainment system code review, according to a specific embodiment of the present invention.

[0072] Figure 4 This is a flowchart of a code change impact analysis sub-process according to a specific embodiment of the present invention.

[0073] Figure 5 This is a flowchart of a security risk visualization sub-process according to a specific embodiment of the present invention.

[0074] Figure 6 This is an electronic device structure diagram of a multi-dimensional visualization analysis method for vehicle system code review provided by one or more embodiments of the present invention. Detailed Implementation

[0075] 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.

[0076] Figure 1 This is a structural diagram of a multi-dimensional visualization analysis system for vehicle infotainment system code review provided by one or more embodiments of the present invention.

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

[0078] Data acquisition layer, core processing layer, visualization layer, and user interaction layer;

[0079] The data acquisition layer is used to connect to external tools through a plug-in mechanism to collect data from multiple data sources.

[0080] The core processing layer is used to process various data sources collected through a code parsing engine, a dependency analysis engine, a risk assessment engine, a requirement mapping engine, and a view template engine.

[0081] Complete code parsing, dependency analysis, risk quantification and assessment, mapping of requirements to code and test cases, and view template configuration;

[0082] The visualization layer is used to generate and display data related to the code review of the vehicle infotainment system.

[0083] The user interaction layer is used to provide a customized user interface for each role.

[0084] Role customization includes multi-dimensional filtering, interactive annotation, real-time collaboration, and the creation, saving, and sharing of custom templates.

[0085] Specifically, the data sources involved in the code review of the vehicle infotainment system are complex (such as Git version control system, SonarQube vulnerability scan results, JUnit test reports, data from the requirements management system, etc.). The data formats and interface specifications of different tools vary greatly, and traditional manual integration is costly and prone to errors.

[0086] By dividing the system into a data acquisition layer, a core processing layer, a visualization layer, and a user interaction layer, and with each layer interacting with data through standardized interfaces, the scalability and maintainability of the system are ensured.

[0087] Through a plug-in mechanism (such as standardized interfaces and adaptation layer plugins), it enables plug-and-play integration with tools such as Git, SonarQube, and OWASP, breaking down data silos and covering all review data including code, vulnerabilities, tests, and requirements.

[0088] Furthermore, including:

[0089] External tools that can be integrated include: code repositories, requirements management tools, test case management systems, static code analysis tools, and performance analysis tools.

[0090] Furthermore, including:

[0091] The code parsing engine includes: performing lexical and syntactic analysis on the vehicle infotainment system code using the ANTLR tool to generate an AST tree;

[0092] Based on the AST tree, obtain the code elements and their inheritance and calling relationships.

[0093] Specifically, tools such as ANTLR are used to perform lexical and syntactic analysis on the vehicle infotainment system code (C / C++ / Java, etc.), generate an AST tree, and extract code elements such as classes, functions, and variables, as well as their inheritance and calling relationships.

[0094] By extracting code elements and relationships across languages, it supports multilingual scenarios in vehicle infotainment systems, further improving parsing accuracy.

[0095] Furthermore, including:

[0096] The workflow of a analytics engine includes:

[0097] The code elements and their inheritance and calling relationships are compiled, and a compilation log is generated.

[0098] Analyze the compilation logs to obtain the dependency information of each component;

[0099] Based on the dependency information of each component, obtain structured dependency data;

[0100] The structured dependency data is used to construct a dependency graph using a force-directed algorithm;

[0101] Specifically, the code module relationship graph is constructed using the force-directed algorithm in graph theory, where nodes represent classes / functions, edges represent dependencies, and the weight of an edge is determined by the call frequency.

[0102] By using a dependency analysis engine to construct module relationship graphs based on graph theory algorithms (such as force-directed algorithms), problems such as circular dependencies and highly coupled omnipotent classes can be automatically identified, improving analysis efficiency by more than 10 times compared to manual analysis.

[0103] Furthermore, including:

[0104] The workflow of the risk assessment engine includes:

[0105] Receive code change data, compare the AST trees before and after the change using the diff algorithm, and identify newly added, deleted, and modified code nodes;

[0106] The code dependency graph built based on the dependency analysis engine uses a breadth-first search to traverse and determine the scope of modules affected by changes;

[0107] By combining the attributes and change types of the affected modules, a risk quantification model is constructed to generate a risk score of 0-10.

[0108] The risk score is associated with the corresponding code node and output to the visualization layer for risk visualization presentation.

[0109] Furthermore, including:

[0110] The demand mapping engine includes:

[0111] Establish a ternary mapping model, in which the requirement node stores the requirement ID, description and priority attributes, the code node is associated with the function implementation node in the AST tree, and the test case node stores the test case ID and input / output parameters;

[0112] Store the ternary mapping model data in a graph database;

[0113] Receive interaction requests from the visualization layer;

[0114] When a requirement node query is triggered, the associated code nodes and test case nodes are automatically retrieved, and coverage status data is output.

[0115] It calculates requirement coverage and test case execution rate, generates multi-dimensional filtering reports, and provides data support to the visualization layer.

[0116] Specifically, the requirement mapping engine establishes a requirement-code-test ternary mapping through a graph database (such as Neo4j), enabling users to trace the associated code and test coverage status by clicking on a requirement, reducing the requirement omission rate to 0.

[0117] Furthermore, including:

[0118] The visualization layer includes:

[0119] Visualizing 3D code structure and creating 3D spatiotemporal evolution maps based on WebGL technology;

[0120] Interactive dependency graphs and security risk heatmaps based on SVG technology;

[0121] It supports multi-granularity display control, and enables dynamic switching of visualization granularity from system level, module level to function level through slider control;

[0122] It receives code parsing, risk assessment, and requirement mapping data output from the core processing layer, and renders the corresponding visualization components in real time to ensure that the data and visualization views are updated synchronously.

[0123] Furthermore, including:

[0124] The core processing layer is also used to implement security risk visualization functions, specifically including:

[0125] The scan results from the integrated static code analysis tool and the OWASP ZAP tool are used to unify the vulnerability levels according to a preset standard, which includes high, medium and low vulnerability levels;

[0126] The vulnerability information is associated with the corresponding nodes in the code visualization diagram, with high-risk vulnerabilities marked in red, medium-risk vulnerabilities marked in yellow, and patched vulnerabilities marked in green.

[0127] For each vulnerable node, a link to the remediation guide is provided, offering code modification examples.

[0128] Specifically, the raw data has poor readability. When data such as code structure, dependencies, and risk scores are presented in the form of tables or text, the information density is low, and reviewers need a lot of time to interpret it (such as finding highly coupled modules from a list of thousands of dependencies).

[0129] Key information such as high-risk vulnerabilities and architectural degradation points in vehicle infotainment systems are mixed in with massive amounts of data, and are easily missed by manual identification (for example, a buffer overflow vulnerability in a certain function is hidden in hundreds of warnings).

[0130] The separation of the time dimension of code evolution (such as the change trend of a module within 3 months) from the spatial structure (dependencies between modules) makes it difficult to analyze the reasons for architectural degradation.

[0131] By transforming code structure and dependencies into a node-edge graph, and using color / size to label risk levels and vulnerability status (e.g., red nodes represent high-risk vulnerabilities), reviewers can grasp the core issues within 10 minutes.

[0132] Automatically highlights critical nodes such as highly coupled all-purpose classes, circular dependencies, and high-risk vulnerabilities. Combined with dynamic granular control (from system level to function level), the efficiency of identifying critical issues is improved by 60%.

[0133] The code evolution is presented through 3D visualization (X / Y axes represent structure, Z axis represents time), which intuitively shows the architectural degradation points (such as the time point when a module goes from low coupling to high coupling), providing data basis for refactoring.

[0134] Figure 2 This is a flowchart of a multi-dimensional visualization analysis method for vehicle infotainment system code review provided by one or more embodiments of the present invention.

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

[0136] Data acquisition step S1: Connect to external tools through a plug-in mechanism to collect multi-source data and perform standardized processing;

[0137] Core processing step S2: Perform lexical and syntactic analysis on the vehicle infotainment system code to extract code elements and their inheritance and calling relationships;

[0138] The code element relationships are compiled to generate logs, the logs are parsed to obtain structured dependency data, and a dependency graph is constructed using a force-directed algorithm;

[0139] By comparing the AST trees before and after the change, the change nodes are identified; by traversing the dependency graph, the scope of impact is assessed; and by combining module attributes and change types, a risk score is generated.

[0140] Establish a ternary mapping model and store it in a graph database, calculate the coverage and generate reports;

[0141] Based on the configuration file, the visibility, highlighting and layout rules of different roles are defined to generate customized view templates for the roles;

[0142] Visualization step S3: Based on WebGL and SVG technologies, generate visual components that support multi-granularity display control;

[0143] User interaction step S4: Provides a role-customized operation interface, supports multi-dimensional filtering, interactive annotation, real-time collaboration, and the creation, saving and sharing of custom templates, while recording review operations and generating review reports.

[0144] Figure 3 This is a flowchart of a multi-dimensional visualization analysis method for vehicle infotainment system code review, according to a specific embodiment of the present invention.

[0145] like Figure 3 As shown, the specific process is as follows: 1. Process Startup and Initialization

[0146] User-initiated code review: The starting point of the process, initiated by the user.

[0147] Select target code repository: The user specifies the code repository that needs to be reviewed.

[0148] 2. Data Collection Branch (Distinguishing between initial review and non-initial review)

[0149] Determine if it is the first review: This is the first branch point in the process, and different data processing paths are selected based on whether it is the first review.

[0150] If it is the first review:

[0151] Perform initial data collection: Initialize and collect all data in the codebase.

[0152] Perform multi-source data collection: collect data from multiple dimensions (such as code structure, syntax, dependencies, etc.).

[0153] If not the first review:

[0154] Load historical data: Recall historical data from previous reviews to avoid duplicate data collection.

[0155] Perform data update checks: Only perform data verification and collection on the newly added or modified parts of the codebase.

[0156] 3. Core Processing and Visualization

[0157] Core engine processing: Perform core logic analysis on the collected data (such as code quality detection, vulnerability scanning, etc.).

[0158] Generate visualization models: Transform the analysis results into visualization models (such as charts, graphs, etc.) to facilitate user understanding.

[0159] Load user role configuration: Load the corresponding permissions and view configurations based on the user's role (such as developer, tester, architect).

[0160] Render customized views: Display customized review interfaces for users with different roles.

[0161] 4. User Interaction and Analysis / Reporting Branch (Distinguish whether analysis is required)

[0162] User interaction operations: Users perform operations on the visual interface (such as viewing questions, marking important information, etc.).

[0163] Determine if analysis is needed: Based on user needs or review rules, decide whether to conduct a specific analysis.

[0164] If analysis is required:

[0165] Trigger targeted analysis: Initiate in-depth analysis (such as performance analysis, security vulnerability scanning, etc.).

[0166] Execute analysis algorithm: Run the algorithm logic for specific analysis and output more refined analysis results.

[0167] If no analysis is required:

[0168] Save review records: Record and archive the process and results of this review.

[0169] Generate a review report: Automatically generate a report that includes review results, a list of issues, and optimization suggestions.

[0170] 5. Process Closure

[0171] End of scan cycle: Regardless of whether a specific analysis is performed, the scan cycle for this code review will eventually end, and the process will be completed.

[0172] By adopting a layered and modular architecture, the system is divided into a data acquisition layer, a core processing layer, a visualization layer, and a user interaction layer. Each layer achieves data interaction through standardized interfaces, ensuring the scalability and maintainability of the system.

[0173] Data Acquisition Layer: Connects to various data sources through a plug-in mechanism, including code repositories (Git / SVN), requirement management tools (Jira / Confluence), test case management systems (TestRail), static code analysis tools (SonarQube), performance analysis tools (JProfiler), etc.

[0174] The core processing layer comprises five core modules: a code parsing engine, a dependency analysis engine, a risk assessment engine, a requirement mapping engine, and a view template engine.

[0175] Visualization layer: Based on WebGL and SVG technologies, it realizes various visualization components such as 3D code structure visualization, dynamic evolution map, and interactive dependency graph.

[0176] User interaction layer: Provides a role-customizable operation interface, supporting functions such as multi-dimensional filtering, interactive annotation, and real-time collaboration.

[0177] In another embodiment, such as Figure 4 As shown, the code structure visualization includes: Abstract Syntax Tree (AST) parsing: using tools such as ANTLR to perform lexical and syntactic analysis on the vehicle system code (C / C++ / Java, etc.), generating an AST tree, and extracting code elements such as classes, functions, and variables, as well as their inheritance and calling relationships.

[0178] Module relationship modeling: The code module relationship graph is constructed using the force-directed algorithm in graph theory. Nodes represent classes / functions, edges represent dependencies, and the weight of the edges is determined by the call frequency.

[0179] Multi-granularity display control: Supports dynamic adjustment of visualization granularity via slider control, from system level (vehicle functional modules) to module level (subsystem) and then to function level (specific implementation).

[0180] By using AST analysis and graph visualization, reviewers can intuitively identify highly coupled all-purpose classes (highly coupled modules) and circular dependency issues, further improving efficiency.

[0181] Dynamic granular control helps architects grasp the system architecture from a macro perspective, while allowing developers to examine the code logic in detail.

[0182] The dynamic evolution map includes: version history data collection: real-time capture of code commit records through Git hooks, extracting metadata such as commit time, author of changes, list of modified files, and change type (add / delete / modify).

[0183] Time-dimensional modeling: The code repository is viewed as a dynamic graph that changes over time, with each timestamp corresponding to a snapshot of the code state, and a directed acyclic graph (DAG) is used to record the version evolution relationship.

[0184] 3D spatiotemporal visualization: In 3D space, the X / Y axes represent the code structure, the Z axis represents time, and different colors and transparency are used to indicate the life cycle (addition / modification / deletion) of code elements.

[0185] 3D spatiotemporal visualization helps new members quickly grasp the evolution of the codebase, significantly improving efficiency compared to traditional document browsing methods.

[0186] The historical change tracking function enables reviewers to quickly locate architectural degradation points, providing data support for restructuring decisions.

[0187] In another embodiment, the risk assessment engine also includes: a security risk visualization scheme, such as... Figure 5 As shown;

[0188] Specifically, this includes: multi-source vulnerability data fusion: integrating scan results from tools such as SonarQube and OWASP ZAP, and unifying vulnerability levels (high / medium / low) according to the CVSS v3 standard.

[0189] Vulnerability location mapping: Associate vulnerability information with corresponding nodes (such as functions and variables) in the code visualization diagram, using different colors for labeling:

[0190] Red: High-risk vulnerabilities (such as buffer overflows);

[0191] Yellow: Medium-risk vulnerabilities (such as unencrypted sensitive data transmission);

[0192] Green: Vulnerability has been fixed;

[0193] Recommended remediation solution: For each vulnerable node, link to the enterprise internal knowledge base or the official OWASP remediation guide, providing code modification examples.

[0194] Visualized vulnerability localization improves security audit efficiency, reducing the high-risk vulnerability failure rate from 15% to below 3%.

[0195] Automated remediation recommendations help developers reduce the average time to remediate a vulnerability by 2 hours.

[0196] In another embodiment, the requirement mapping engine includes a requirement tracing and test coverage scheme, specifically a ternary mapping model: establishing a many-to-many mapping relationship between requirements, code, and test cases, stored in a graph database (such as Neo4j).

[0197] Requirement node: Includes attributes such as requirement ID, description, and priority.

[0198] Code node: corresponds to the functional implementation node in the AST.

[0199] Test case node: contains test case ID and input / output parameters.

[0200] Interactive tracing interface: In the visualization, clicking on a requirement node will automatically highlight the associated code block and test case, and display the coverage status (covered / not covered).

[0201] Coverage statistics charts: Generate visual reports such as requirement coverage and test case execution rate, and support filtering by module, priority and other dimensions.

[0202] By tracing the functionality, we can ensure that requirements can be traced back to the code implementation, avoid missing features, and improve test coverage.

[0203] Visualized reports help project managers keep track of development progress in real time and reduce rework caused by changes in requirements.

[0204] In another embodiment, the view template engine also includes: a character-customized view scheme.

[0205] Specifically: View Configuration Language: Defines a JSON-formatted view configuration file, containing:

[0206] Visibility rules: Which code elements are visible to the current user (e.g., testers only see API functions).

[0207] Highlighting rules: Automatically highlight nodes based on specific conditions (such as high-complexity functions).

[0208] Layout rules: Custom diagram layout (e.g., using a layered layout for the architect view).

[0209] Dynamic view generation: Load the corresponding configuration file according to the user role (developer / architect / tester / security) and filter and render the visualization in real time.

[0210] Custom template management: Supports users to create, save, and share custom view templates to meet specific project needs.

[0211] By using a role-customized view, the average efficiency of review for different positions is significantly improved, and interference from irrelevant information is reduced.

[0212] Template sharing mechanisms promote the accumulation of best practices within the team, shortening the onboarding time for new members.

[0213] Figure 6 This is an electronic device structure diagram of a multi-dimensional visualization analysis method for vehicle system code review provided by one or more embodiments of the present invention.

[0214] 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;

[0215] The memory stores a computer program, which, when executed by the processor, causes the processor to perform the steps of a multi-dimensional visualization analysis method for vehicle system code review.

[0216] 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 multi-dimensional visualization analysis method for vehicle system code review.

[0217] 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.

[0218] 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.

[0219] 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 multi-dimensional visualization analysis system for vehicle infotainment system code review, characterized in that, include: Data acquisition layer, core processing layer, visualization layer, and user interaction layer; The data acquisition layer is used to collect multi-source heterogeneous data by connecting to external tools; The core processing layer is used to process the collected multi-source heterogeneous data through a code parsing engine, a dependency analysis engine, a risk assessment engine, a requirement mapping engine, and a view template engine. The processing includes: completing code parsing, dependency analysis, risk quantification assessment, mapping requirements to code and test cases, and view template configuration; The visualization layer is used to generate and display data related to the code review of the vehicle system. The user interaction layer is used to provide a customized operation interface for roles, which includes multi-dimensional filtering, interactive annotation, real-time collaboration, and the creation, saving, and sharing of custom templates.

2. The multi-dimensional visualization analysis system for vehicle infotainment system code review according to claim 1, characterized in that, The external tools to be integrated include: code repositories, requirements management tools, test case management systems, static code analysis tools, and performance analysis tools; The multi-source heterogeneous data includes: code structure data, version history data, requirement data, test case data, and vulnerability data of the vehicle system.

3. The multi-dimensional visualization analysis system for vehicle infotainment system code review according to claim 1, characterized in that, The workflow of the code parsing engine includes: performing lexical and syntactic analysis on the vehicle system code using a syntax parsing tool to generate an abstract syntax tree; Based on the abstract syntax tree, obtain the code elements and their inheritance and calling relationships.

4. The multi-dimensional visualization analysis system for vehicle infotainment system code review according to claim 3, characterized in that, The workflow of the dependency analysis engine includes: The obtained code elements and their inheritance and calling relationships are compiled to generate a compilation log; Analyze the compilation logs to obtain the dependency information of each component; Based on the parsed dependency information of each component, structured dependency data is obtained; The structured dependency data is used to construct a dependency graph using a force-directed algorithm.

5. A multi-dimensional visualization analysis system for vehicle infotainment system code review according to claim 4, characterized in that, The workflow of the risk assessment engine includes: By comparing the abstract syntax tree before and after the change using a dataset difference algorithm, the added, deleted, and modified code nodes can be identified. Based on the dependency graph, a breadth-first search is used to traverse and determine the scope of modules affected by the changes; By combining the attributes and change types of the affected modules, a risk quantification model is constructed to generate a risk score; The risk score is associated with the corresponding code node and output to the visualization layer for risk visualization presentation.

6. The multi-dimensional visualization analysis system for vehicle infotainment system code review according to claim 1, characterized in that, The workflow of the demand mapping engine includes: Establish a three-element mapping model, including: requirement node, code node, and test case node; The requirement node stores the requirement ID, description, and priority attributes; Code nodes are associated with functional implementation nodes in the abstract syntax tree; The test case node stores the test case ID and input / output parameters; Store the ternary mapping model data in a graph database; Receive interaction requests from the visualization layer; When a requirement node query is triggered, the associated code nodes and test case nodes are automatically retrieved, and coverage status data is output. Based on the coverage status data, the requirement coverage rate and test case execution rate are statistically analyzed, and multi-dimensional filtering reports are generated to provide data support to the visualization layer.

7. The multi-dimensional visualization analysis system for vehicle infotainment system code review according to claim 1, characterized in that, The visualization layer includes: Achieving visualization of 3D code structure and 3D spatiotemporal evolution map based on 3D graphics rendering; Implement interactive dependency graphs and security risk heatmaps based on scalable vector graphics; It supports multi-granularity display control, and enables dynamic switching of visualization granularity from system level, module level to function level through slider control; It receives code parsing, risk assessment, and requirement mapping data output from the core processing layer, and renders the corresponding visualization components in real time, enabling the data and visualization view to be updated synchronously.

8. A multi-dimensional visualization method for vehicle infotainment system code review, characterized in that, Includes the following steps: Data acquisition steps: Connect to external tools through a plug-in mechanism to collect multi-source data and perform standardized processing; Core processing steps: Perform lexical and syntactic analysis on the vehicle infotainment system code to extract code elements and their inheritance and calling relationships; The code element relationships are compiled to generate logs, the logs are parsed to obtain structured dependency data, and a dependency graph is constructed using a force-directed algorithm; By comparing the abstract syntax tree before and after the change, the change nodes are identified; by traversing the dependency graph, the scope of impact is assessed; and by combining module attributes and change types, a risk score is generated. Establish a ternary mapping model and store it in a graph database, calculate the coverage and generate reports; Based on the configuration file, the visibility, highlighting and layout rules of different roles are defined to generate customized view templates for the roles; Visualization steps: Based on 3D graphics rendering and scalable vector graphics, generate visual components that support multi-granularity display control; User interaction steps: Provides a role-customized operation interface, supports multi-dimensional filtering, interactive annotation, real-time collaboration, and the creation, saving and sharing of custom templates, while recording review operations and generating review reports.

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, which, when executed by the processor, causes the processor to perform the steps of the multi-dimensional visualization method for code review of a vehicle infotainment system as described in claim 8.

10. A computer-readable storage medium, characterized in that, It stores a computer program that can be executed by an electronic device. When the computer program runs on the electronic device, it causes the electronic device to perform the steps of the multi-dimensional visualization method for code review of a vehicle system as described in claim 8.

Images