Update release report generation method and system, computer equipment and program product

Abstract

The invention provides an update release report generation method and system, computer equipment and a program product, and the method comprises the steps: determining a business update target corresponding to each business module of a vehicle according to a whole vehicle update target of the vehicle, and synchronizing the business update target to a part function management system; the part function management system is used for determining a version function corresponding to each service module according to the service updating target; obtaining a version function from the part function management system, obtaining part information of each service part researched and developed according to the version function, creating a new whole vehicle version according to the part information, and initiating a test request to a test system; obtaining a service test report obtained after the test system tests the service parts in each service module according to the whole vehicle version; and generating an update release report of the vehicle according to the version function, the whole vehicle update target, the business update target, the business test report and the part information.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a method, system, computer device and program product for generating an update release report. Background Art

[0002] As vehicles develop towards automation and intelligence, more and more intelligent parts are installed on vehicles. In order to better maintain vehicle functions, more and more intelligent parts are beginning to support Over-the-Air Technology (OTA) upgrades. However, before performing OTA upgrades on intelligent parts, it is necessary to test the new version of the software in the intelligent parts from multiple links, and then integrate the test results of each link to obtain a professional test report, so that professionals can determine whether the new version of the software needs to be released based on the test report.

[0003] However, the conventional test report generation method requires the participants in each link to communicate and coordinate each link offline, and then manually collect and organize the test results of each link to obtain the final test report. The entire report generation process requires a lot of manual participation, which reduces the efficiency of report generation. Summary of the invention

[0004] The embodiments of the present disclosure at least provide a method, system, computer device and program product for generating an update release report.

[0005] In a first aspect, an embodiment of the present disclosure provides a method for generating an update release report, which is applied to a vehicle software management platform VSP, comprising:

[0006] According to the vehicle's complete vehicle update target, the business update targets corresponding to each business module of the vehicle are determined and synchronized to the parts function management system; the parts function management system is used to determine the version function corresponding to each business module according to the business update target;

[0007] Obtaining the version function of each of the business modules from the part function management system, and obtaining the part information of each business part developed according to the version function, and creating a new vehicle version according to the part information and initiating a test request to the test system;

[0008] Obtaining a business test report obtained after the test system tests the business parts in each of the business modules according to the vehicle version;

[0009] An update release report for the vehicle is generated based on the version function, the whole vehicle update target, the business update target, the business test report and the parts information; the update release report is used to indicate whether the whole vehicle version can be released to the production stage, as well as test details in multiple dimensions.

[0010] In this implementation mode, after obtaining the vehicle update target, VSP can refine the vehicle update target by splitting the entire update target into the business update targets of each business module on each vehicle. By synchronizing the business update target to the parts function management system, the automatic association between VSP and the parts function management system can be achieved, which facilitates the parts function management system to focus on the version function of the business module. Then, after obtaining the parts information of each business part developed by the developer according to the version function, VSP integrates the parts information into the vehicle version and submits it for testing, so that the test system can focus on the testing of each business module according to the entire version, thereby outputting the business test report of each business module. Finally, by automatically obtaining the business test report from the test system, and according to the business test report, version function, vehicle update target, business update target, and parts information, an update release report containing multi-dimensional information can be automatically aggregated. The entire solution realizes the automatic generation of update release reports through the association and information transmission between VSP, parts function management system and test system, greatly reducing the cost of manual participation and improving the efficiency of report generation. And through the connection and information transmission between the three parts, personnel in each department only need to focus on their own work to complete the version update test, which not only reduces offline communication costs, but also avoids business deviations during the update test process.

[0011] In a possible implementation, generating an update release report for the vehicle according to the version function, the vehicle update target, the service update target, the service test report and the parts information includes:

[0012] Generate vehicle software information according to the parts information, the version information and version usage information of the vehicle version, and the vehicle system version on which the vehicle version depends;

[0013] Generate vehicle update information according to the version function, the vehicle update target, the business test report and the multiple dimensions, and generate business update information according to the business update target and the business test report; the multiple dimensions at least include version delivery dimension, version production dimension, and version compatibility dimension;

[0014] The update release report is generated according to the whole vehicle software information, the whole vehicle update information, and the business update information.

[0015] This implementation method can improve the comprehensiveness of the information in the update release report by integrating the whole vehicle software information, whole vehicle update information, and business update information in the update release report, and provide information support for the release of new version software and subsequent after-sales and factory software upgrades.

[0016] In a possible implementation manner, the business test report includes the business completion status of the business module and the priority distribution of the faults corresponding to the failed test cases in the test cases used to test the business parts; the faults corresponding to the failed test cases are stored in the part function management system;

[0017] The generating the vehicle update information according to the version function, the vehicle update target, the business test report and the multiple dimensions includes:

[0018] Determining the completion status of the vehicle version according to the completion status of each of the businesses and the multiple dimensions;

[0019] Obtaining the stored faults corresponding to the respective failed test cases from the part function management system, and generating a fault distribution diagram according to the priority distribution and the faults;

[0020] According to the priority of each of the faults, select risk faults whose risk levels meet the requirements from the faults;

[0021] According to the function priority of the version function, from the obtained version functions, filter each version function whose function priority meets the target priority;

[0022] The whole vehicle update information is generated according to the completion status of the whole vehicle version, the fault distribution map, the risk faults and each version function that meets the target priority.

[0023] This implementation method, by integrating the completion status of the whole vehicle version, the fault distribution map of the faults corresponding to the failed test cases, the risk faults and the functions of each version that meet the target priority, can make the whole vehicle update information not only reflect the whole vehicle update status, but also reflect the various risks and update priorities that arise during the update process, thereby facilitating the generation of a more comprehensive update release report based on the whole vehicle update information.

[0024] In a possible implementation manner, after generating the update release report, the method further includes:

[0025] An editing operation for the update release report is received, and the update release report is updated according to the editing operation to obtain an updated update release report.

[0026] This implementation method supports editing of the update release report, so that the update release report can be further improved with human participation.

[0027] In a possible implementation manner, after determining the service update targets respectively corresponding to the service modules of the vehicle, the method further includes:

[0028] The business update target is synchronized to the test system, so that the tester can create a test case for testing the business component according to the business update target and test the business component.

[0029] This implementation method, by synchronizing the business update target to the test system, makes it easier for testers to create test cases that meet the target, thereby improving the rationality of business testing.

[0030] In a second aspect, an embodiment of the present disclosure provides a method for generating an update release report, which is applied to a test system, and includes:

[0031] Receive a test request initiated by a vehicle software management platform VSP; the test request is used to test a new vehicle version, the new vehicle version is created by the VSP according to the parts information of each business part developed according to the version function; the version function is determined by the parts function management system according to the business update target of each business module; the business update target is determined by the VSP according to the vehicle update target of the vehicle;

[0032] According to the vehicle version, the business parts in each business module are tested respectively to obtain a business test report for each business module;

[0033] The service test report is sent to the VSP; the VSP is used to generate an update release report for the vehicle based on the version function, the vehicle update target, the service update target, the service test report and the parts information obtained from the parts function management system.

[0034] This implementation method enables the test system to obtain the version functions of each business module in a timely manner through the association and information transmission between the test system and the VSP. Then, the version function can be used to focus on testing the business parts in the business module and obtain a business test report that meets the business update target. Then, by feeding back the business test report to the VSP, the VSP can automatically extract and integrate a comprehensive update release report.

[0035] In a possible implementation, the business parts in each of the business modules are tested separately according to the vehicle version to obtain a business test report for each of the business modules, including:

[0036] Obtain the service update target synchronized by the VSP, and write multiple test cases according to the service update target and the vehicle version;

[0037] Using the test cases, the business parts in each of the business modules are tested respectively, the test cases that pass the test and the test cases that fail the test are determined, and faults corresponding to the test cases that fail the test are created in the part function management system;

[0038] Determine the service completion status of each service module according to the test cases that have passed the test and the test cases that have not passed the test, and determine the priority distribution according to the priority of the faults corresponding to each of the test cases that have not passed the test;

[0039] The service test report is generated according to the service completion status and the priority distribution status.

[0040] In this implementation, by creating a fault corresponding to a failed test case in the part function management system, the part function management system can be used to manage the fault problem.

[0041] In a third aspect, an embodiment of the present disclosure provides an update release report generation system, including an automotive software management platform VSP, a parts function management system, and a testing system, wherein:

[0042] The VSP is configured to determine the business update targets corresponding to each business module of the vehicle according to the vehicle update target and synchronize them to the part function management system; obtain the version function of each business module from the part function management system, and obtain the part information of each business part developed according to the version function determined by the part function management system, and create a new vehicle version according to the part information and initiate a test request to the test system; and generate an update release report for the vehicle according to the version function, the vehicle update target, the business update target, the business test report fed back by the test system and the part information; the update release report is used to indicate whether the vehicle version can be released to the production stage, as well as test details in multiple dimensions;

[0043] The part function management system is configured to determine the version function corresponding to each business module according to the business update target;

[0044] The testing system is configured to test the business parts in each of the business modules separately according to the vehicle version, obtain a business test report and synchronize it to the VSP.

[0045] In a fourth aspect, an optional implementation of the present disclosure further provides a computer device, a processor, and a memory, wherein the memory stores machine-readable instructions executable by the processor, and the processor is used to execute the machine-readable instructions stored in the memory, and when the machine-readable instructions are executed by the processor, the steps in the above-mentioned first aspect, or any possible implementation of the first aspect are executed; or, when the machine-readable instructions are executed by the processor, the steps in the above-mentioned second aspect, or any possible implementation of the second aspect are executed.

[0046] In a fifth aspect, an optional implementation of the present disclosure further provides a computer program product, which, when run, executes the steps of the above-mentioned first aspect, or any possible implementation of the first aspect; or, the computer program product, when run, executes the above-mentioned second aspect, or any possible implementation of the second aspect.

[0047] For a description of the effects of the above-mentioned update release report generation system, computer device, and computer program product, please refer to the description of the above-mentioned update release report generation method, which will not be repeated here.

[0048] In order to make the above-mentioned objectives, features and advantages of the present disclosure more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the following is a brief introduction to the drawings required for use in the embodiments. The drawings herein are incorporated into the specification and constitute a part of the specification. These drawings illustrate embodiments consistent with the present disclosure and are used together with the specification to illustrate the technical solutions of the present disclosure. It should be understood that the following drawings only illustrate certain embodiments of the present disclosure and should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can also be obtained based on these drawings without creative work.

[0050] Figure 1 A flow chart of a method for generating an update release report applied to an automobile software management platform provided by an embodiment of the present disclosure is shown;

[0051] Figure 2 A flow chart of a method for generating an update release report applied to a test system provided by an embodiment of the present disclosure is shown;

[0052] Figure 3 A schematic diagram of the structure of an update release report generation system provided by an embodiment of the present disclosure is shown;

[0053] Figure 4An interactive schematic diagram of an update release report generation system provided by an embodiment of the present disclosure is shown;

[0054] Figure 5 A schematic diagram of the structure of a computer device provided by an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0055] In order to make the purpose, technical scheme and advantages of the embodiments of the present disclosure clearer, the technical scheme in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all of the embodiments. The components of the embodiments of the present disclosure generally described and shown here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present disclosure is not intended to limit the scope of the present disclosure claimed for protection, but merely represents the selected embodiments of the present disclosure. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present disclosure.

[0056] In addition, the terms "first", "second", etc. in the description and claims of the embodiments of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein.

[0057] The "multiple or several" mentioned in this article refers to two or more. "And / or" describes the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0058] Research has found that there are more and more intelligent parts on vehicles that support OTA. However, in order to ensure the stability of the software functions of the new version of the software on the intelligent parts, it is necessary to test multiple links before releasing the new version of the software, such as part software testing, part subsystem testing, vehicle integration testing, industrial application testing, etc. Through the collaboration between personnel in each link, the coordination of the tests in each link can be achieved to obtain the final test report. However, the current test report generation process often has the following problems:

[0059] 1. There are many people involved in the whole process, including parts testers / parts R&D personnel, integration testers / integration R&D personnel, business testers / business R&D personnel, project coordinators, software integrators, etc. Therefore, in the process of testing and report generation, it is necessary to unify the software goals of all personnel and complete the testing of each link according to the rhythm of the vehicle integration plan. During this period, communication needs to be completed through online meetings and / or offline communication, which is extremely inefficient and may result in untimely notification and information asymmetry.

[0060] 2. When each business version is officially released, the test results and issues of any business module need to be manually classified and summarized to form a corresponding test report, which results in high labor costs and low efficiency.

[0061] 3. The testing process is usually completed in the test system, and the software integrators manage the report information based on the vehicle version in the VSP. Therefore, when each vehicle version is officially released, the software integrators need to re-integrate the test reports corresponding to all test links to obtain a comprehensive release report, which further increases labor costs and reduces generation efficiency.

[0062] Based on the above research, the present disclosure provides a method, system, computer device and program product for generating update release reports. The entire solution realizes the automatic generation of test reports corresponding to each business module and update release reports corresponding to the whole vehicle through the association and information transmission between VSP, part function management system and test system, which greatly reduces the cost of manual participation and improves the efficiency of report generation. And through the association and information transmission between the three parts, the personnel of each part only need to focus on their own work to complete the version update test, which not only reduces the offline communication cost, but also avoids business deviations during the update test process.

[0063] The defects existing in the above solutions are the results obtained by the inventor after practice and careful research. Therefore, the discovery process of the above problems and the solutions proposed by the present disclosure for the above problems below should be the contributions made by the inventor to the present disclosure during the disclosure process.

[0064] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, further definition and explanation thereof is not required in subsequent drawings.

[0065] It is understandable that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, scope of use, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0066] It should be noted that the specific terms mentioned in the embodiments of the present disclosure include:

[0067] Vehicle version: Aggregates the versions of all intelligent parts that need to be upgraded and those that do not need to be upgraded on the vehicle;

[0068] Vehicle Software Platform, or VSP for short, is used to manage the software information of each component on the vehicle;

[0069] Jira system: a project and transaction tracking tool, which can be used to manage the version functions and vulnerability bugs of parts in the disclosed embodiment;

[0070] Test system: A system used to manage test cases and test results.

[0071] To facilitate understanding of this embodiment, first of all, a method for generating an update release report disclosed in the embodiment of the present disclosure is introduced in detail. The execution subject of the update release report generation method provided in the embodiment of the present disclosure is generally a terminal device or other processing device with a certain computing power, wherein the terminal device can be a user equipment (UserEquipment, UE), a mobile device, a user terminal, a terminal, a personal digital assistant device (Personal Digital Assistant, PDA), a handheld device, a computer device, etc.; in the terminal device or other processing device, a VSP, a test system and a jira system can be deployed. In the use of terminal devices or other processing devices, it can be implemented by the VSP, the test system and the jira system deployed in these devices. In some possible implementations, the update release report generation method can be implemented by a processor calling a computer-readable instruction stored in a memory.

[0072] The following describes the update release report generation method provided by the embodiment of the present disclosure by taking the execution subject as VSP as an example.

[0073] like Figure 1 As shown, it is a flowchart of a method for generating an update release report applied to an automobile software management platform provided by an embodiment of the present disclosure, which may include the following steps:

[0074] S101: According to the vehicle update target, the business update targets corresponding to each business module of the vehicle are determined and synchronized to the parts function management system; the parts function management system is used to determine the version function corresponding to each business module according to the business update target.

[0075] Here, the vehicle update target is used to indicate the overall goal and functions to be achieved by the vehicle after the vehicle function is updated. The business module is obtained by dividing the vehicle into modules according to different vehicle business dimensions and business functions in advance. The business module may specifically include but is not limited to the infrastructure module, vehicle control module, motion control module, automatic driving module, smart cockpit module, Internet of Vehicles module, and industrialization module. The business update target is used to indicate the business goal to be achieved by the business module after the function is updated, and may specifically include the specific software information of the software in each business part. The business part may be an intelligent part on the vehicle. The business update target can be quantified from the functional implementation scope, performance indicators, OTA success rate, number of legacy bugs, etc. of the business module. The part function management system is used to manage the part version functions and bugs in the part testing process. The part function management system may specifically be a jira system. The version function is used to indicate the function of the part under the corresponding version.

[0076] In specific implementation, when it is determined that the whole vehicle function needs to be updated, the whole vehicle function manager can formulate the whole vehicle update target according to the functions that need to be realized and input it into the VSP. Then, the VSP can display the whole vehicle update target to the managers of different business modules. The managers of each business module can separate and set the software information of each business part in each business module from the whole vehicle update target according to the functional control scope corresponding to each business module indicated by the whole vehicle update target and the corresponding software status of each business part under the business module in the previous stage. After the setting is completed, the set software information of each business module can be used as the business update target of each business module. Then, the business update target can be input into the VSP. In this way, the VSP can obtain the business update target corresponding to each business module.

[0077] Furthermore, after obtaining the business update targets of each business module, VSP can synchronize each business update target to the jira system. Then, the jira system can be used to maintain the specific version functions of each business part in the business module according to the business update targets, and associate the corresponding part version for each business part. Here, for business parts that need to be updated, the part version can be the version obtained after the corresponding update of the business part; for business parts that do not need to be updated, the part version is the version currently used by the business part. Among them, since one or more ECUs can be deployed on a business part, the version function of the business part can be reflected in the version function of the ECU included therein.

[0078] S102: Obtain the version function of each business module from the part function management system, and obtain the part information of each business part developed according to the version function, create a new vehicle version according to the part information, and initiate a test request to the test system.

[0079] Here, the part information may specifically include the version information and software package of the business parts. The vehicle version is used to indicate the part version and software package of each business part required to be used on the vehicle. The test request is a request for testing the vehicle version, and the test request can be used to perform multi-link testing on each business part corresponding to the vehicle version.

[0080] In specific implementation, in order to integrate the version functions of each business module into the release test report finally generated, the VSP system can also obtain these version functions from the jira system after the jira system determines the version functions of each business module. Alternatively, after the jira system determines the version functions of each business module, it can actively synchronize the various version functions to the VSP system. At the same time, the parts R&D personnel can carry out part function development according to the version functions of each business part that needs to be updated as indicated by the jira system, so as to obtain the parts information of each new version of the business parts, and can submit the parts information of each business part to the VSP for management. Then. The software integrator can create a whole vehicle version in the VSP based on the parts information of each new version of the business parts in the VSP, and initiate a test request operation after the whole vehicle version is created. The VSP can generate a test request related to the whole vehicle version based on the test request operation and send it to the test system, and the VSP can send the whole vehicle version to the test system.

[0081] S103: Obtain a business test report obtained after the test system tests the business parts in each business module according to the vehicle version.

[0082] Here, a business test report corresponds to a business module, and the business test report is used to indicate the corresponding test status of the business parts in the business module under each link test. Among them, each link test can include part software testing, part subsystem testing, vehicle integration testing, industrial application testing, etc. The business test report can include the pass rate of the test cases tested on the business module, the priority distribution of legacy bugs, test details, business completion status, business update risks, legacy issues and corresponding response strategies, etc.

[0083] In specific implementation, after initiating a test request to the test system, the test system can write test cases corresponding to each business module in each link according to the vehicle version through the test personnel, and input the test cases into the test system. Then use the test cases to test the business parts in each business module one by one to obtain the test results of each link. Then, based on the test results of each link and the preset business test report template, generate the business test report corresponding to each business module and feedback it to the VSP. Among them, when using the business test report template to generate the business test report, if there is no relevant content in the test result, it can be set to the default value for output, and if the test result contains relevant content, the corresponding information can be filled in to obtain the business test report. After obtaining the business test report, the business test report can be sent directly to the VSP, or the test personnel can check the business test report, and after determining that there is a problem, modify the business test report to obtain the modified business test report, and then the test system can send the modified business test report to the VSP. Among them, the modification of the business test report can be, for example, modifying the default value in the business test report, modifying the error in the business test report, etc.

[0084] Furthermore, the VSP can obtain the service test report corresponding to each service module fed back by the test system.

[0085] S104: Generate a vehicle update release report based on version functions, vehicle update targets, business update targets, business test reports and parts information; the update release report is used to indicate whether the vehicle version can be released to the production stage, as well as test details in multiple dimensions.

[0086] Here, the multiple dimensions may be preset dimensions, for example, version delivery dimension, version production dimension, version compatibility dimension, etc. The version delivery dimension may be used to indicate whether the vehicle version can be delivered on time, the version generation dimension may be used to indicate the time when the vehicle version can be put into production, and the version compatibility dimension may be used to indicate the compatibility possibility and compatibility method with future newly added parts.

[0087] The update release report is used to indicate whether the vehicle version can be released to the production stage, as well as test details related to multiple dimensions during the testing process, the impact on various update issues, and other information. This report can provide information support for software release and subsequent after-sales and factory software upgrades.

[0088] In specific implementation, after obtaining the business test reports corresponding to each business module, VSP can use a fixed release report template to extract and aggregate effective information on the vehicle update goals, business update goals, business test reports, parts information, and version functions obtained from the jira system, thereby obtaining the various parts of the content that match the template, and fill in the various parts of the content into the corresponding template to obtain the final update release report.

[0089] In this way, after obtaining the vehicle update target, VSP can refine the vehicle update target by splitting the entire update target into the business update targets of each business module on each vehicle. By synchronizing the business update target to the parts function management system, the automatic association between VSP and the parts function management system can be realized, which facilitates the parts function management system to focus on the version function of the business module. Then, after obtaining the parts information of each business part developed by the developers according to the version function, VSP integrates the parts information into the vehicle version and submits it for testing, which facilitates the test system to focus on the testing of each business module according to the entire version, thereby outputting the business test report of each business module. Finally, by automatically obtaining the business test report from the test system, and according to the version function, business test report, vehicle update target, business update target, and parts information, an update release report containing multi-dimensional information can be automatically aggregated. The entire solution realizes the automatic generation of update release reports through the association and information transmission between VSP, parts function management system and test system, greatly reducing the cost of manual participation and improving the efficiency of report generation. And through the connection and information transmission between the three parts, personnel in each department only need to focus on their own work to complete the version update test, which not only reduces offline communication costs, but also avoids business deviations during the update test process.

[0090] In one embodiment, S104 may be implemented according to the following steps:

[0091] S104-1: Generate vehicle software information based on parts information, version information and version usage information of the vehicle version, and the vehicle system version on which the vehicle version depends.

[0092] Here, the version usage information is used to indicate the functional usage of the updated vehicle version, for example, whether it will be applied to the reversing stage, the turning stage, the vehicle breaking stage, whether it is 2c (that is, whether it needs to reach the user), etc. The vehicle system version is the version of the vehicle system that the updated vehicle version depends on when running. The part information may include the part version number, part software package and dependency information of each ECU in the business part. The version information of the vehicle version may specifically be the vehicle version number.

[0093] The vehicle software information is used to indicate various information related to the software in the business parts of the version update. It is understandable that since the software information can be managed in the VSP, various information that can be used to generate the vehicle software information can be obtained from the vehicle version details information of the VSP.

[0094] During specific implementation, VSP can be used to store the ECU parts information in each business part (this can be the parts information of the updated business parts or the parts information of all business parts in the whole vehicle version), the version number and version usage information of the whole vehicle version, and the dependent vehicle system version, etc., to form the whole vehicle software information.

[0095] S104-2: Generate vehicle update information based on version functions, vehicle update goals, business test reports and multiple dimensions, and generate business update information based on business update goals and business test reports; the multiple dimensions at least include version delivery dimension, version production dimension, and version compatibility dimension.

[0096] Here, the vehicle update information is used to characterize the update status of the vehicle version, and the business update information is used to characterize the update status of each business module.

[0097] During specific implementation, the completion status of the whole vehicle target can be determined according to the whole vehicle update target and the business test report, and the first key information matching the release report template can be extracted from the business test report corresponding to each business module, and the information in the business test report corresponding to each business module can be summarized and refined according to each dimension to obtain the second key information under each dimension. Then, the version function, the completion status of the whole vehicle target, the first key information and the second key information under each dimension can be used as the whole vehicle update information.

[0098] At the same time, the business completion status of each business module can be determined according to the business update target and the business test report, and the business test report corresponding to each business module can be extracted and summarized according to the template information related to each business module in the release report template, so as to obtain the summary information corresponding to each business module. The business completion status and summary information corresponding to each business module are used as business update information.

[0099] S104-3: Generate an update release report based on the vehicle software information, vehicle update information, and business update information.

[0100] In specific implementation, the vehicle software information, vehicle update information, and business update information can be filled into the release report template according to the release report template to obtain an updated release report. Optionally, in order to ensure the comprehensiveness of the test information, the updated release report may include supplementary information in addition to the vehicle software information, vehicle update information, and business update information. The supplementary information may include complete business test reports corresponding to each business module, bug lists of each bug corresponding to the vehicle version, function lists corresponding to the version functions of each business part, and other information, so that relevant personnel can obtain it according to their needs. Among them, each information in the supplementary information can be obtained from the test system and the jira system.

[0101] In one embodiment, the business test report may include the business completion of the business module and the priority distribution of the faults corresponding to the failed test cases in each test case used to test the business parts. Here, the business completion can be used to characterize the completion of the business goals corresponding to the business module, such as business goal achievement, business goal failure, percentage of business goal achievement, etc. The test case is written by the tester and input into the test system, which is used to test the business parts in the business module. The failed test case is the case that failed the test when the business module is tested. In the case that the test case fails to pass the test, it means that there are currently one or more faults (bugs) corresponding to the test case. Different bugs may cause different effects. Therefore, in order to facilitate the management of bugs, the priority of the fault can also be determined and filled in the business test report. The priority of the fault corresponding to the test case is related to the scope of influence of the business part associated with the bug on the vehicle function. For example, in the case of affecting the driving safety of the vehicle, the bug will have a higher priority; in the case of affecting the vehicle display or uncommon functions, the bug will have a lower priority. The priority of the bug is specified by the tester when generating the business test report, and can also be automatically determined by the test system.

[0102] Priority distribution is used to indicate the number of bugs distributed under each priority. For example, there are 3 bugs with priority 0, 1 bug with priority 1, 1 bug with priority 2, and 5 bugs with priority 3. Business risk is used to indicate the potential risk that the bugs corresponding to the failed test cases will bring to the vehicle version upgrade. The bugs corresponding to the failed test cases can be stored in the parts function management system.

[0103] Specifically, when using test cases to test business modules, if a test case passes, the test status of the test case can be set to passed in the test system. If a test case fails, various bugs related to the failed test case can be created in the jira system, and the jira system notifies the R&D personnel to handle the bugs. After the handling is completed, the test case can be used for testing again. If the test passes, the test status of the test case can be set to passed in the test system. If the test fails, the failed test case and various bugs under the failed test case can be stored in the jira system for easy management using the jira system.

[0104] The step of "generating vehicle update information according to version functions, vehicle update targets, business test reports and multiple dimensions" in S104-2 can be implemented as follows:

[0105] S104-2-1: Determine the completion status of the vehicle version based on the completion status of each business and multiple dimensions.

[0106] Here, the completion status of the whole vehicle version is used to indicate whether the whole vehicle version has been updated, the degree of update completion, completed targets, uncompleted targets, the impact of uncompleted targets on the whole vehicle version, and other information.

[0107] In specific implementation, VSP can integrate the business completion status of each business module and the importance of each business module to obtain the business integration status of the whole vehicle version. At the same time, it can determine the dimension information related to each dimension in multiple dimensions based on the business integration status and business completion status and relevant information in the business test report. Finally, the completion status of the whole vehicle version can be generated based on the business integration status and the dimension information related to each dimension.

[0108] S104-2-2: Obtain the faults corresponding to each failed test case stored in the part function management system, and generate a fault distribution map based on the priority distribution and the faults.

[0109] In specific implementation, based on the above introduction, if a test case fails, the test system will create a corresponding bug in the jira system. Therefore, when generating vehicle update information, you can also obtain the bug details corresponding to each failed test case from the jira system. The bug details may include the specific content of the bug, the bug repair status, the repair difficulty, etc. At the same time, you can obtain the priority distribution of the bug from the business test report corresponding to each business module.

[0110] Then, a detailed bug distribution pie chart can be generated based on the bug details and priority distribution of each bug corresponding to the failed test case obtained from the jira system, and the distribution pie chart can be used as a fault distribution chart. In this way, by generating a fault distribution chart, when the update release report is subsequently presented to relevant personnel, the distribution chart can be displayed intuitively, making it easier for relevant personnel to clearly and directly understand the vulnerability situation during the update process.

[0111] S104-2-3: According to the priority of each fault, select the risk faults that meet the requirements from the faults.

[0112] Here, the priority is usually related to the business risk, and the higher the priority, the higher the business risk. Complying with the requirements may specifically mean that the priority meets the preset level.

[0113] In specific implementation, according to the priority of each fault in the business test report, a bug with a preset priority level can be screened out from each fault, and the bug can be used as a risk fault. For example, the priority can include P0 to P3, and a bug with a priority of P0 is displayed as a risk bug.

[0114] In this way, by filling the bugs with higher risk levels in the update release report, it is convenient for relevant personnel to quickly obtain high-risk issues from the update release report and solve them in priority.

[0115] S104-2-4: According to the function priority of the version function, from the obtained version functions, filter each version function whose function priority meets the target priority.

[0116] Here, different version functions also have different function priorities. A version function with a higher function priority is relatively more important. The target priority may be a priority pre-specified based on experience.

[0117] The priority of each version function can be determined by the JIRA system based on the demand for the version function and the scope of vehicles involved, or it can be pre-set in the JIRA system by relevant personnel.

[0118] During specific implementation, the function priority of each version function can be obtained from the JIRA system, and then the version functions whose function priority is greater than or equal to the target priority can be filtered out as the target version functions.

[0119] For example, version functions with function priorities of priority 0 and priority 1 may be used as target version functions.

[0120] Optionally, the VSP system can obtain the priority of each version function while obtaining each version function from the jira system. Alternatively, the VSP system can also obtain each version function and the function priority of each version function from the jira system when it needs to generate vehicle update information. The specific time to obtain the version function can be set based on experience, and the embodiment of the present disclosure does not specifically limit it.

[0121] S104-2-5: Generate vehicle update information based on the completion status of the vehicle version, fault distribution map, risk faults and various version functions that meet the target priority.

[0122] During specific implementation, the vehicle version, the completion status of the vehicle version, the fault distribution map, the risk faults and the functions of each target version can be filled in the corresponding positions in the release report template according to the release report template to obtain the vehicle update information.

[0123] With respect to the step of "generating business update information according to the business update target and the business test report" in S104-2, the completion status of the business update target can be determined according to the test status of each business module indicated in the business test report, and the completion status can be used as the completion status of the business target. The completion status of the business target can include business completion, business incompleteness, business completion percentage, etc. It is understandable that the completion status of the business update target can also be included in the business test report, and directly obtained when needed, and the update evaluation of the business target can be generated according to the completion status of the business target and the importance of the business update target.

[0124] At the same time, the information in each business test report can be regulated and aggregated to obtain test summary information, and the business risks appearing in the business test report can be clustered and summarized to obtain risk summary information. Then, the test summary information, risk summary information, the completion status of the business update goals corresponding to each business module, update evaluation, and the response strategies for each business risk in the business test report are used as business update information.

[0125] Alternatively, the business test reports of each business module may be refined and summarized for key information according to preset summary goals and business update goals to obtain business update information.

[0126] In one embodiment, in order to further improve the rationality of the update release report, an editing operation for the update release report may be received, and the update release report may be updated according to the editing operation to obtain an updated update release report.

[0127] That is, the disclosed embodiment also supports software integrators to modify the update release report, thereby facilitating the software integrators to conduct an overall check and supplement the update release report, and to modify and adjust the update completion status of the vehicle version based on the basic data in the update release report.

[0128] For example, the update release report is generated according to the release report template, so it may include some default values ​​or incorrect places. Therefore, after using VSP to display the update release report to the software integrator, the software integrator can also edit the update release report on VSP and obtain the updated update release report after the editing is completed. For example, the software integrator can add missing issues to the update release report, modify the corresponding response measures for business risks, add problem analysis and response information for vehicle after-sales personnel, and modify the completion status of the vehicle version.

[0129] It is understandable that for the business test report generated by the test system, the business test report can also support the tester to edit and modify the initial business test report generated by the test system, so as to obtain a more complete and accurate business test report. For example, the tester can enter the test results in the initial business test report, modify the completion of the business update target, add potential business risks and corresponding countermeasures, add missed bug issues, etc.

[0130] In one embodiment, in order to facilitate testers to better write test cases for business modules, the update release report generation method provided in the embodiment of the present disclosure can also synchronize the business update targets to the test system after determining the business update targets corresponding to each business module of the vehicle, so that testers can create test cases for testing business parts according to the business update targets and test the business parts.

[0131] Exemplarily, while VSP synchronizes the business update targets of each business module to the jira system, it can also synchronize the business update targets to the test system. In this way, after initiating a test request to the test system, the test system can be tested by relevant testers. Testers can view the business update targets of each business module in the test system, and view the version functions of each business part in the jira system. Then, according to the business update targets and version functions, write the test cases corresponding to each business module in each link, and input the test cases into the test system for relevant testing.

[0132] Since the update release report generation method provided by the embodiment of the present disclosure requires interaction between the jira system, the VSP and the test system, the embodiment of the present disclosure also provides an update release report generation method applied to the test system. Figure 2As shown, it is a flowchart of a method for generating an update release report applied to a test system provided by an embodiment of the present disclosure, which may include the following steps:

[0133] S201: Receive a test request initiated by the automotive software management platform VSP; the test request is used to test a new vehicle version, which is created by the VSP based on the parts information of each business part developed according to the version function; the version function is determined by the part function management system based on the business update goals of each business module; the business update goal is determined by the VSP based on the vehicle update goal of the vehicle.

[0134] Here, the new vehicle version is the vehicle version created in the VSP by the software integrator based on the parts information of each new version of the business parts in the VSP.

[0135] Exemplarily, VSP can be responsible for maintaining the business update goals of each business module under each vehicle version and the vehicle update goals of the vehicle, and maintain the functional scope of each business part based on the version function in the Jira system in advance. After the functional developers have developed the business parts according to the version functions of each business part that needs to be updated, they can submit the part information of the business parts in VSP. Software integrators can create a vehicle version in VSP based on the part information of each new version of the business parts in VSP, and initiate a test request after the vehicle version is created for testing in each link. In this way, the test system can receive the test request from VSP.

[0136] S202: testing the business parts in each business module respectively according to the vehicle version, and obtaining a business test report for each business module.

[0137] In specific implementation, after initiating a test request to the test system, the test system can write test cases corresponding to each business module in each link according to the vehicle version through testers and input the test cases into the test system. Then use the test cases to test the business parts in each business module one by one to obtain the test results of each link. That is, the test system will perform tests based on the business update goals and vehicle versions set by the VSP, output test cases based on the business update goals, and perform tests. Furthermore, the test system can generate business test reports corresponding to each business module based on the test results of each link and the preset business test report template.

[0138] S203: Send the service test report to the VSP; the VSP is used to generate a vehicle update release report based on the version function, vehicle update target, service update target, service test report and parts information obtained from the parts function management system.

[0139] Exemplarily, the test system can send the business test reports corresponding to each business module to the VSP. After obtaining the business test reports corresponding to each business module, the VSP can extract and aggregate effective information based on the fixed release report template for the vehicle update target, business update target, business test report, parts information and version functions obtained from the parts function management system, thereby obtaining the parts that match the template, and fill the parts into the corresponding template to obtain the final update release report. Then, relevant personnel can decide whether to release the vehicle version based on the content in the update release report. After the version is released, the information in the update release report will also provide a reference for after-sales and factory software upgrades, and make plans for possible problems in advance.

[0140] In one embodiment, S202 may be implemented according to the following steps:

[0141] S202-1: Obtain the business update target of VSP synchronization, and write multiple test cases according to the business update target and vehicle version.

[0142] Exemplarily, after obtaining the business update target of each business module, VSP can synchronize the business update target to the test system. Then, the test system can obtain the business update target. Notify the tester to write the test cases corresponding to each business module in each link according to the vehicle version, business update target, and the version function of each business part in the jira system, and input the test cases into the test system. Among them, the test case can include one or more test cases for each business part. In this way, the test system can obtain each test case.

[0143] S202-2: Use test cases to test the business parts in each business module respectively, determine the test cases that pass the test and the test cases that fail the test, and create faults corresponding to the test cases that fail the test in the part function management system.

[0144] Specifically, when using test cases to test the business parts in the business module one by one, if a test case passes, the test status of the test case can be set to passed in the test system. If a test case fails, various bugs related to the failed test case can be created in the jira system, and the jira system notifies the R&D personnel to handle the bug. After the handling is completed, the test case is used for testing again. If the test passes, the test status of the test case can be set to passed in the test system. If the test fails, the failed test case and various bugs under the failed test case can be stored in the jira system for easy management using the jira system.

[0145] S202-3: Determine the service completion status of each service module according to the test cases that have passed and the test cases that have failed, and determine the priority distribution according to the priority of the faults corresponding to each test case that has failed.

[0146] Exemplarily, the test system can determine the pass rate, failure rate, etc. of each business module based on the number of test cases that passed the test, the number of test cases that failed the test, and the total number of test cases. At the same time, the business completion status of each business module can be determined based on the business update goals of each business module, as well as information such as the test cases that passed the test and the missed bugs. Among them, the business completion status can be used to characterize the completion status of the business goals corresponding to the business module, such as business goal achievement, business goal failure, percentage of business goal achievement, etc. At the same time, the priority distribution of the bugs corresponding to the failed test cases in each test case can be determined based on the priority of each missed bug in the jira system.

[0147] S202-4: Generate a business test report based on the business completion status and priority distribution.

[0148] In specific implementation, when generating a business test report, the business update risks, legacy issues, and corresponding response strategies of the business update can also be determined based on the test results of each business module. Among them, the business update risk can be determined based on the impact of each bug on the vehicle. Then, the preset business test report template can be used to fill in the business completion status, priority distribution, business update risks, legacy issues, and corresponding response strategies in the corresponding positions to obtain a business test report.

[0149] Optionally, the service test report can also be edited by the tester. For example, after the service test report is generated, the tester or other relevant personnel can view the test report in the test system, modify the problems in the service test report, add information to the service test report, supplement the summary information based on the summary of the test situation, etc. After the modification is completed, the final service test report is obtained and fed back to the VSP.

[0150] In this way, through the association and information transmission between the test system and VSP, the test system can obtain the version functions of each business module in a timely manner. Then, the version function can be used to focus on testing the business parts in the business module and obtain a business test report that meets the business update goals. Then, by feeding back the business test report to the VSP, the VSP can automatically refine and integrate a comprehensive update release report.

[0151] In addition, since the update release report generation method provided by the embodiment of the present disclosure requires interaction between the jira system, VSP and the test system, the embodiment of the present disclosure also provides an update release report generation system. Figure 3 FIG. 1 is a schematic diagram of a structure of an update release report generation system provided by an embodiment of the present disclosure, including an automotive software management platform VSP, a parts function management system and a test system, wherein:

[0152] The VSP is configured to determine the business update targets corresponding to each business module of the vehicle according to the vehicle update target and synchronize them to the part function management system; obtain the version function of each business module from the part function management system, and obtain the part information of each business part developed according to the version function determined by the part function management system, and create a new vehicle version according to the part information and initiate a test request to the test system; and generate an update release report for the vehicle according to the version function, the vehicle update target, the business update target, the business test report fed back by the test system and the part information; the update release report is used to indicate whether the vehicle version can be released to the production stage, as well as test details in multiple dimensions;

[0153] The part function management system is configured to determine the version function corresponding to each business module according to the business update target;

[0154] The testing system is configured to test the business parts in each of the business modules separately according to the vehicle version, obtain a business test report and synchronize it to the VSP.

[0155] Regarding the operations to be performed by various parts in the above-mentioned update release report generation system, and the interactions between them, reference may be made to the introduction of the above-mentioned embodiments, which will not be described in detail here.

[0156] like Figure 4As shown, it is an interactive schematic diagram of an update release report generation system provided by an embodiment of the present disclosure, wherein VSP can be used to formulate a vehicle update target, and split the vehicle update target to obtain the business update target corresponding to each business module. For example, the business update targets corresponding to the infrastructure module, vehicle control module, motion control module, automatic driving module, smart cockpit module, Internet of Vehicles module, industrialization module and other modules are split. At the same time, VSP can synchronize the business update target to the jira system. Then, the jira system can be used to maintain the specific version functions of each business part in the business module according to the business update target and synchronize it to VSP. After the functional development personnel develop the business parts according to the version functions of each business part that needs to be updated, they can submit the part information of the business parts in VSP. Software integrators can create a vehicle version in VSP based on the part information of each new version of the business parts in VSP, and initiate a test request after the vehicle version is created for testing in each link, so that the test system can receive the test request from VSP. The test system will perform tests based on the business update goals and vehicle versions set by the VSP, output test cases based on the business update goals, and perform tests. If a bug occurs during the test process, it will be submitted to the Jira system and a responsible person will be assigned. After all test cases are completed, a business test report will be generated based on the pass status of the test cases, bug status, etc., and passed back to the VSP. The VSP will generate an update release report in a fixed format based on the vehicle version information, version functions, and business test reports. Ultimately, it will decide whether to release the vehicle version based on the content in the update release report. After the vehicle version is released, the information in the update release report will also provide a reference for after-sales and factory software upgrades, and prepare plans for possible problems in advance. The update release report includes vehicle software information, vehicle update information, business update information, and supplementary information. In Figure 4 In the update release report, the detailed contents under each part of the information are represented by different types of rectangular boxes. If the rectangular box corresponding to a certain information is a solid rectangular box, it means that the information can be obtained from VSP or edited by relevant personnel in VSP; if the rectangular box corresponding to a certain information is a dotted rectangular box, it means that the information can be obtained from the test system; if the rectangular box corresponding to a certain information is a rounded rectangular box, it means that the information can be obtained from the jira system.

[0157] In this way, compared with the prior art in which software management is performed in VSP, test management is performed in the test system, bug and function management is performed in Jira, and finally the related information is aggregated manually, this application associates VSP, test system, and Jira system. Based on the association and information transmission between VSP, jira system and test system, each vehicle version can automatically generate a fixed template update release report based on the business module, which improves the integration efficiency of the release report and reduces the communication cost of offline personnel. In addition, personnel in various positions can perform their duties and complete corresponding work in a dedicated system without taking into account multiple systems, thereby improving office efficiency. That is, the person in charge of parts software and software integrators complete software submission, version integration and release work in the VSP system. Testers and R&D personnel complete testing and bug maintenance in the test system. The test information, function and bug information required for the release report in VSP are automatically obtained through the linkage between VSP, test system and Jira system. Before each version iteration, all personnel have clear business goals, which are transmitted from top to bottom. According to the vehicle update goals, relevant software integration, testing and release work are carried out to effectively avoid deviations in the realization of the goals.

[0158] Those skilled in the art will appreciate that, in the above method of specific implementation, the order in which the steps are written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of the steps should be determined by their functions and possible internal logic.

[0159] Based on the same technical concept, the embodiment of the present application also provides a computer device. Figure 5 FIG. 1 is a schematic diagram of a computer device provided in an embodiment of the present application, including:

[0160] Processor 501, memory 502 and bus 503. Among them, memory 502 stores machine-readable instructions executable by processor 501, and processor 501 is used to execute machine-readable instructions stored in memory 502. When the machine-readable instructions are executed by processor 501, processor 501 performs the following steps: S101: According to the vehicle update target of the vehicle, determine the business update target corresponding to each business module of the vehicle and synchronize it to the part function management system; the part function management system is used to determine the version function corresponding to each business module according to the business update target; S102: Obtain the version function of each business module from the part function management system, and obtain the part information of each business part developed according to the version function, and create a new vehicle version according to the part information and initiate a test request to the test system; S103: Obtain the business test report obtained by the test system after testing the business parts in each business module according to the vehicle version; and S104: Generate the vehicle update according to the version function, vehicle update target, business update target, business test report and part information. Release report; the update release report is used to indicate whether the vehicle version can be released to the production stage, as well as test details in multiple dimensions; or, when the machine-readable instructions are executed by the processor 501, the processor 501 performs the following steps: S201: receiving a test request initiated by the automotive software management platform VSP; the test request is used to test the new vehicle version, and the new vehicle version is created by the VSP based on the parts information of each business part developed according to the version function; the version function is determined by the parts function management system according to the business update goals of each business module; the business update goals are determined by the VSP according to the vehicle update goals of the vehicle; S202: according to the vehicle version, the business parts in each business module are tested separately to obtain the business test reports of each business module; and S203: sending the business test report to the VSP; the VSP is used to generate an update release report for the vehicle based on the version function, vehicle update goals, business update goals, business test reports and parts information obtained from the parts function management system.

[0161] The above-mentioned memory 502 includes a memory 5021 and an external memory 5022; the memory 5021 here is also called an internal memory, which is used to temporarily store the calculation data in the processor 501, as well as the data exchanged with the external memory 5022 such as a hard disk. The processor 501 exchanges data with the external memory 5022 through the memory 5021. When the computer device is running, the processor 501 communicates with the memory 502 through the bus 503, so that the processor 501 executes the execution instructions mentioned in the above method embodiment.

[0162] The embodiment of the present disclosure also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the update release report generation method described in the above method embodiment are executed. The storage medium can be a volatile or non-volatile computer-readable storage medium.

[0163] The computer program product of the update release report generation method provided in the embodiment of the present disclosure includes a computer-readable storage medium storing program code, and the instructions included in the program code can be used to execute the steps of the update release report generation method described in the above method embodiment. For details, please refer to the above method embodiment, which will not be repeated here.

[0164] The computer program product may be implemented in hardware, software or a combination thereof. In one optional embodiment, the computer program product is embodied as a computer storage medium, and in another optional embodiment, the computer program product is embodied as a software product, such as a software development kit (SDK) and the like.

[0165] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, the specific working process of the system and device described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here. In the several embodiments provided in the present disclosure, it should be understood that the disclosed system, device and method can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of the device or unit can be electrical, mechanical or other forms.

[0166] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0167] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0168] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present disclosure, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0169] If the technical solution of this application involves personal information, the product using the technical solution of this application has clearly informed the personal information processing rules and obtained the individual's voluntary consent before processing the personal information. If the technical solution of this application involves sensitive personal information, the product using the technical solution of this application has obtained the individual's separate consent before processing the sensitive personal information, and at the same time meets the "explicit consent" requirement. For example, on personal information collection devices such as cameras, clear and prominent signs are set to inform that the personal information collection scope has been entered and personal information will be collected. If the individual voluntarily enters the collection scope, it is deemed that he or she agrees to the collection of his or her personal information; or on the device that processes personal information, the personal information processing rules are notified by obvious signs / information, and the individual's authorization is obtained through pop-up information or by asking the individual to upload his or her personal information; among them, the personal information processing rules may include information such as the personal information processor, the purpose of personal information processing, the processing method, and the type of personal information processed.

[0170] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present disclosure, which are used to illustrate the technical solutions of the present disclosure, rather than to limit them. The protection scope of the present disclosure is not limited thereto. Although the present disclosure is described in detail with reference to the aforementioned embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the aforementioned embodiments within the technical scope disclosed in the present disclosure, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present disclosure, and should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be based on the protection scope of the claims.

Claims

1. A method for generating an update release report, characterized in that: Applied to the automotive software management platform VSP, including: According to the vehicle's complete vehicle update target, the business update targets corresponding to each business module of the vehicle are determined and synchronized to the parts function management system; the parts function management system is used to determine the version function corresponding to each business module according to the business update target; Obtaining the version function of each of the business modules from the part function management system, and obtaining the part information of each business part developed according to the version function, and creating a new vehicle version according to the part information and initiating a test request to the test system; Obtaining a business test report obtained after the test system tests the business parts in each of the business modules according to the vehicle version; An update release report for the vehicle is generated based on the version function, the whole vehicle update target, the business update target, the business test report and the parts information; the update release report is used to indicate whether the whole vehicle version can be released to the production stage, as well as test details in multiple dimensions.

2. The method according to claim 1, characterized in that Generate an update release report for the vehicle according to the version function, the vehicle update target, the business update target, the business test report and the parts information, including: Generate vehicle software information according to the parts information, the version information and version usage information of the vehicle version, and the vehicle system version on which the vehicle version depends; Generate vehicle update information according to the version function, the vehicle update target, the business test report and the multiple dimensions, and generate business update information according to the business update target and the business test report; the multiple dimensions at least include version delivery dimension, version production dimension, and version compatibility dimension; The update release report is generated according to the whole vehicle software information, the whole vehicle update information, and the business update information.

3. The method according to claim 2, characterized in that The business test report includes the business completion status of the business module and the priority distribution of the faults corresponding to the failed test cases in each test case used to test the business parts; the faults corresponding to each failed test case are stored in the part function management system; The generating the vehicle update information according to the version function, the vehicle update target, the business test report and the multiple dimensions includes: Determining the completion status of the vehicle version according to the completion status of each of the businesses and the multiple dimensions; Obtaining the stored faults corresponding to the respective failed test cases from the part function management system, and generating a fault distribution diagram according to the priority distribution and the faults; According to the priority of each of the faults, select risk faults whose risk levels meet the requirements from the faults; According to the function priority of the version function, from the obtained version functions, filter each version function whose function priority meets the target priority; The whole vehicle update information is generated according to the completion status of the whole vehicle version, the fault distribution map, the risk faults and each version function that meets the target priority.

4. The method according to claim 1, characterized in that After generating the update release report, the method further includes: An editing operation for the update release report is received, and the update release report is updated according to the editing operation to obtain an updated update release report.

5. The method according to claim 1, characterized in that After determining the business update targets corresponding to each business module of the vehicle, it also includes: The business update target is synchronized to the test system, so that the tester can create a test case for testing the business component according to the business update target and test the business component.

6. A method for generating an update release report, characterized in that: Applied to test systems, including: Receive a test request initiated by a vehicle software management platform VSP; the test request is used to test a new vehicle version, the new vehicle version is created by the VSP according to the parts information of each business part developed according to the version function; the version function is determined by the parts function management system according to the business update target of each business module; the business update target is determined by the VSP according to the vehicle update target of the vehicle; According to the vehicle version, the business parts in each business module are tested respectively to obtain a business test report for each business module; The service test report is sent to the VSP; the VSP is used to generate an update release report for the vehicle based on the version function, the vehicle update target, the service update target, the service test report and the parts information obtained from the parts function management system.

7. The method according to claim 6, characterized in that According to the vehicle version, the business parts in each business module are tested respectively to obtain a business test report for each business module, including: Obtain the service update target synchronized by the VSP, and write multiple test cases according to the service update target and the vehicle version; Using the test cases, the business parts in each of the business modules are tested respectively, the test cases that pass the test and the test cases that fail the test are determined, and faults corresponding to the test cases that fail the test are created in the part function management system; Determine the service completion status of each service module according to the test cases that have passed the test and the test cases that have not passed the test, and determine the priority distribution according to the priority of the faults corresponding to each of the test cases that have not passed the test; The service test report is generated according to the service completion status and the priority distribution status.

8. An update release report generation system, characterized in that: It includes the automotive software management platform VSP, parts function management system and testing system, including: The VSP is configured to determine the business update targets corresponding to each business module of the vehicle according to the vehicle update target and synchronize them to the part function management system; obtain the version function of each business module from the part function management system, and obtain the part information of each business part developed according to the version function determined by the part function management system, and create a new vehicle version according to the part information and initiate a test request to the test system; and generate an update release report for the vehicle according to the version function, the vehicle update target, the business update target, the business test report fed back by the test system and the part information; the update release report is used to indicate whether the vehicle version can be released to the production stage, as well as test details in multiple dimensions; The part function management system is configured to determine the version function corresponding to each business module according to the business update target; The testing system is configured to test the business parts in each of the business modules separately according to the vehicle version, obtain a business test report and synchronize it to the VSP.

9. A computer device, characterized in that: include: A processor and a memory, wherein the memory stores machine-readable instructions executable by the processor, and the processor is used to execute the machine-readable instructions stored in the memory. When the machine-readable instructions are executed by the processor, the processor executes the steps of the update release report generation method as described in any one of claims 1 to 7.

10. A computer program product, which, when executed by a computer device, executes the steps of the update release report generation method according to any one of claims 1 to 7.

Images