A management method and device of a whole vehicle software development platform
By managing vehicle requirements and test cases in separate zones based on common reuse and vehicle model-specific projects, the problems of long development cycles and low efficiency in vehicle software development have been solved, achieving rapid and efficient optimization of the development process.
Patent Information
- Application Number
- CN202211248173.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-10-12
- Publication Date
- 2025-11-21
- Estimated Expiration
- 2042-10-12
AI Technical Summary
In existing technologies, the development cycle of in-vehicle software is long, the updates and iterations are slow, the costs are increased, the quality is difficult to control, and the development efficiency is low. This is because all vehicle requirements and test cases are stored in a public database, which requires each test case to be retrieved individually during each development process, wasting time.
Vehicle requirements and test cases are managed in separate zones, categorized as either common for reuse or specific to a vehicle model project. The target vehicle requirements and test cases are retrieved from a pre-defined common requirements document through a vehicle model project generation request. A vehicle model project document is then generated, and the document is stored in either a common or specific document based on the requirement type.
It improved the efficiency of vehicle software development, enabled the rapid retrieval of reusable vehicle requirements and test cases in public areas, reduced redundant development, and optimized the development process.
Smart Images
Figure CN115562637B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of data processing technology, and in particular to a management method and apparatus for a vehicle software development platform. Background Technology
[0002] With the explosive growth of in-vehicle software, each vehicle model project needs to develop its own in-vehicle software, which not only has a long development cycle and slow updates and iterations, but also increases costs and makes it difficult to control risks and quality.
[0003] Currently, in order to accelerate the development of vehicle software for vehicle models, the approach adopted is to store all kinds of vehicle requirements and corresponding test cases in a unified public database, which developers can then retrieve when developing vehicle software.
[0004] However, the above method stores all kinds of vehicle requirements and corresponding test cases in a public database. This means that developers will have to retrieve the required test cases one by one from the public database each time they develop vehicle software, which wastes time and reduces development efficiency. Summary of the Invention
[0005] In view of the above problems, the present invention provides a management method and device for a vehicle software development platform. The main purpose is to realize the partitioned management of vehicle requirements and corresponding test cases according to common reuse and vehicle model project specificity, thereby improving the development efficiency of vehicle software.
[0006] To solve the above-mentioned technical problems, the present invention proposes the following solution:
[0007] In a first aspect, the present invention provides a management method for a vehicle software development platform, the method comprising: obtaining, according to a vehicle model project generation request, a target vehicle requirement corresponding to the vehicle model project and test cases corresponding to the target vehicle requirement from a preset public requirement document, wherein the target vehicle requirement and the test cases corresponding to the target vehicle requirement are applicable to at least two types of vehicle model projects;
[0008] The vehicle model project document is generated based on the target vehicle requirements and the test cases corresponding to the target vehicle requirements.
[0009] Modify the target vehicle requirements and test cases corresponding to the target vehicle requirements in the vehicle model project document, or construct new vehicle requirements and test cases corresponding to the new vehicle requirements;
[0010] Determine whether the number of vehicle model types to which the target vehicle requirement and test cases corresponding to the modified vehicle model project are applicable, or the number of new vehicle requirements and test cases corresponding to the constructed vehicle model project, are applicable, is greater than a preset threshold.
[0011] If so, the target vehicle requirements and test cases corresponding to the modified vehicle model project or the new vehicle requirements and test cases corresponding to the constructed vehicle model project are stored in the preset common requirements document.
[0012] If not, then the target vehicle requirements and test cases corresponding to the modified vehicle model project, or the new vehicle requirements and test cases corresponding to the constructed vehicle model project, are stored in the vehicle model project document.
[0013] Preferably, before obtaining the target vehicle requirements and test cases corresponding to the target vehicle requirements from a preset common requirements document based on the vehicle model project generation request, the method includes:
[0014] Obtain the target vehicle requirements and the corresponding test cases;
[0015] The target vehicle requirements, the corresponding test cases, and the functional feature work items are associated to obtain associated data. The attributes of the functional feature work items include mandatory attributes and optional attributes.
[0016] The associated data is stored in the preset public requirements document.
[0017] Preferably, the method further includes:
[0018] Based on the attributes of the functional feature work item, the target functional feature work item corresponding to the vehicle model project is obtained using a preset functional feature selection page. The target functional feature work item includes functional feature work items with mandatory attributes and functional feature work items with selected optional attributes.
[0019] The vehicle model project generation request is generated based on the target functional characteristic work item corresponding to the vehicle model project.
[0020] Preferably, the functional feature work item includes a first-level functional feature work item and a second-level functional feature work item, wherein the first-level functional feature work item is higher than the second-level functional feature work item.
[0021] The process of associating the target vehicle requirements, the corresponding test cases, and the functional feature work items to obtain associated data includes:
[0022] The target vehicle requirements are associated with the test cases corresponding to the target vehicle requirements to obtain the associated target vehicle requirements;
[0023] The associated target vehicle requirements are associated with the corresponding second-level functional feature work items to obtain the associated second-level functional feature work items.
[0024] The associated second-level functional feature work item is associated with the corresponding first-level functional feature work item to obtain the associated data.
[0025] Preferably, the preset functional feature selection page includes a first-level functional feature work item and a second-level functional feature work item;
[0026] The method of obtaining the target functional characteristic work item corresponding to the vehicle model project based on the attributes of the functional characteristic work item using a preset functional characteristic selection page includes:
[0027] Based on the attributes of the first-level functional feature work item, the target first-level functional feature work item of the vehicle model project is determined from the first-level functional feature work items using the preset functional feature selection page. The target first-level functional feature work item includes first-level functional feature work items with mandatory attributes and first-level functional feature work items with selected optional attributes.
[0028] Based on the attributes of the second-level functional feature work item, the target second-level functional feature work item of the vehicle model project is determined from the second-level functional feature work items associated with the target first-level functional feature work item of the vehicle model project using the preset functional feature selection page. The target second-level functional feature work item includes second-level functional feature work items with mandatory attributes and second-level functional feature work items with selected optional attributes.
[0029] Preferably, generating the vehicle model project generation request based on the target functional characteristic work item corresponding to the vehicle model project includes:
[0030] The vehicle model project generation request is generated based on the target first-level functional characteristic work item and the target second-level functional characteristic work item of the vehicle model project.
[0031] Preferably, the step of obtaining the target vehicle requirements and test cases corresponding to the target vehicle requirements from a preset public requirements document based on the vehicle model project generation request includes:
[0032] Based on the target first-level functional feature work item and the target second-level functional feature work item carried in the vehicle model project generation request, the target vehicle requirements associated with the target second-level functional feature work item and the test cases associated with the target vehicle requirements are obtained from the preset public requirements document, thereby obtaining the target vehicle requirements corresponding to the vehicle model project and the test cases corresponding to the target vehicle requirements.
[0033] Secondly, the present invention provides a management device for a vehicle software development platform, the device comprising:
[0034] The first acquisition unit is used to acquire the target vehicle requirements and test cases corresponding to the target vehicle requirements from a preset public requirements document according to the vehicle model project generation request, wherein the target vehicle requirements and test cases corresponding to the target vehicle requirements are applicable to at least two types of vehicle model projects.
[0035] The first generation unit is used to generate the vehicle model project document based on the target vehicle requirements corresponding to the vehicle model project and the test cases corresponding to the target vehicle requirements.
[0036] The processing unit is used to modify the target vehicle requirements and test cases corresponding to the target vehicle requirements in the vehicle project document, or to construct new vehicle requirements and test cases corresponding to the new vehicle requirements in the vehicle project document.
[0037] The judgment unit is used to determine whether the number of vehicle types to which the target vehicle requirement and the test cases corresponding to the modified vehicle model project are applicable, or the new vehicle requirement and the test cases corresponding to the constructed vehicle model project are applicable, is greater than a preset threshold.
[0038] The first storage unit is configured to store the target vehicle requirements and test cases corresponding to the target vehicle requirements, or the new vehicle requirements and test cases corresponding to the new vehicle requirements, applicable to the modified vehicle model project and the new vehicle requirements, into the preset common requirements document if the number of vehicle model project types to which the modified vehicle model project and the target vehicle requirements and the test cases corresponding to the target vehicle requirements and the new vehicle requirements are applicable is greater than a preset threshold.
[0039] The second storage unit is configured to store the target vehicle requirements and test cases corresponding to the modified vehicle model project, or the new vehicle requirements and test cases corresponding to the constructed vehicle model project, into the vehicle model project document if the number of vehicle model project types to which the modified target vehicle requirements and test cases corresponding to the target vehicle requirements and test cases corresponding to the constructed vehicle model project are applicable is not greater than a preset threshold.
[0040] Preferably, the device further includes:
[0041] The second acquisition unit is used to acquire the target vehicle requirements and the test cases corresponding to the target vehicle requirements.
[0042] The association unit is used to associate the target vehicle requirements, the test cases corresponding to the target vehicle requirements, and the functional feature work items to obtain associated data. The attributes of the functional feature work items include mandatory attributes and optional attributes.
[0043] The third storage unit is used to store the associated data in the preset public requirement document.
[0044] Preferably, the device further includes:
[0045] The selection unit is used to obtain the target functional characteristic work item corresponding to the vehicle model project based on the attributes of the functional characteristic work item using a preset functional characteristic selection page, wherein the target functional characteristic work item includes a functional characteristic work item with mandatory attributes and a functional characteristic work item with selected optional attributes.
[0046] The second generation unit is used to generate a vehicle model project generation request based on the target functional characteristic work item corresponding to the vehicle model project.
[0047] Preferably, the functional characteristic work item includes a first-level functional characteristic work item and a second-level functional characteristic work item, wherein the first-level functional characteristic work item is higher than the second-level functional characteristic work item; the associating unit includes:
[0048] It is also used to associate the target vehicle requirements with the test cases corresponding to the target vehicle requirements to obtain the associated target vehicle requirements;
[0049] It is also used to associate the associated target vehicle requirements with the corresponding second-level functional feature work items to obtain the associated second-level functional feature work items;
[0050] It is also used to associate the associated second-level functional feature work item with the corresponding first-level functional feature work item to obtain the associated data.
[0051] Preferably, the preset functional feature selection page includes first-level functional feature work items and second-level functional feature work items; the selection unit includes:
[0052] The first selection module is used to determine the target first-level functional feature work item of the vehicle model project from the first-level functional feature work items based on the attributes of the first-level functional feature work items using the preset functional feature selection page, wherein the target first-level functional feature work item includes first-level functional feature work items with mandatory attributes and first-level functional feature work items with selected optional attributes.
[0053] The second selection module is used to determine the target second-level functional feature work item of the vehicle model project from the second-level functional feature work items associated with the target first-level functional feature work item of the vehicle model project using the preset functional feature selection page, based on the attributes of the second-level functional feature work item. The target second-level functional feature work item includes second-level functional feature work items with mandatory attributes and second-level functional feature work items with selected optional attributes.
[0054] Preferably, the second generating unit includes:
[0055] It is also used to generate a vehicle model project generation request based on the target first-level functional characteristic work item and the target second-level functional characteristic work item of the vehicle model project.
[0056] Preferably, the first acquisition unit includes:
[0057] It is also used to obtain the target vehicle requirements associated with the target second-level functional feature work item and the test cases associated with the target vehicle requirements from a preset public requirements document based on the target first-level functional feature work item and the target second-level functional feature work item carried in the vehicle model project generation request, so as to obtain the target vehicle requirements corresponding to the vehicle model project and the test cases corresponding to the target vehicle requirements.
[0058] To achieve the above objectives, according to a third aspect of the present invention, a storage medium is provided, the storage medium including a stored program, wherein, when the program is executed, the device where the storage medium is located is controlled to execute the management method of the vehicle software development platform described in the first aspect.
[0059] To achieve the above objectives, according to a fourth aspect of the present invention, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements all or part of the steps of the management device for a vehicle software development platform as described in the second aspect.
[0060] By means of the above technical solution, the management method and device of the whole vehicle software R&D platform provided by the present invention is to store all kinds of vehicle requirements and the corresponding use cases in a unified public database. This would cause R&D personnel to have to retrieve the required use cases one by one from the public database according to the R&D requirements each time they develop vehicle software, which would waste time and reduce R&D efficiency. To this end, the present invention obtains the target vehicle requirements and test cases corresponding to the vehicle model project from a preset public requirements document according to the vehicle model project generation request; generates the vehicle model project document based on the target vehicle requirements and test cases corresponding to the target vehicle requirements; modifies the target vehicle requirements and test cases corresponding to the target vehicle requirements or constructs new vehicle requirements and test cases corresponding to the new vehicle requirements in the vehicle model project document; determines whether the number of vehicle model project types to which the modified or constructed new vehicle requirements and test cases corresponding to the new vehicle requirements are applicable is greater than a preset threshold; if yes, the modified or constructed new vehicle requirements and test cases corresponding to the new vehicle requirements are stored in the preset public requirements document; if no, the modified or constructed new vehicle requirements and test cases corresponding to the new vehicle requirements are stored in the vehicle model project document. This invention enables the storage of reusable vehicle requirements and corresponding test cases in a public storage area, and the storage of non-reusable vehicle requirements and corresponding test cases suitable for a certain type of vehicle project in a dedicated storage area for that type of vehicle project. When R&D personnel need to develop a certain type of vehicle project, they can directly retrieve and use the entire set of test cases from the dedicated storage area for that type of vehicle project. If it is necessary to add reusable test cases to the type of vehicle project, they can retrieve them from the public storage area, thereby improving R&D efficiency.
[0061] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention and to implement it in accordance with the contents of the specification, and in order to make the above and other objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description
[0062] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:
[0063] Figure 1 A flowchart illustrating a management method for a vehicle software development platform provided by an embodiment of the present invention is shown.
[0064] Figure 2 A flowchart illustrating another management method for a vehicle software development platform provided by an embodiment of the present invention is shown;
[0065] Figure 3 This diagram illustrates the composition of a management device for a vehicle software development platform according to an embodiment of the present invention.
[0066] Figure 4 This invention provides a block diagram illustrating the composition of a management device for another vehicle software development platform according to an embodiment of the present invention.
[0067] Figure 5 This diagram illustrates the relationship between target vehicle requirements, test cases, first-level functional feature work items, and second-level functional feature work items provided in an embodiment of the present invention. Detailed Implementation
[0068] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
[0069] Currently, to accelerate the development of in-vehicle software for vehicle projects, all various vehicle requirements and their corresponding test cases are stored in a unified public database. However, this requires developers to retrieve these test cases from the database individually for each development task, wasting time and reducing efficiency. To address this issue, the inventors devised a method to manage vehicle requirements and their corresponding test cases by separating them into public, reusable categories and vehicle-specific categories, thereby improving the development efficiency of in-vehicle software.
[0070] Therefore, this invention provides a management method for a vehicle software development platform, which improves the development efficiency of in-vehicle software. The specific execution steps are as follows: Figure 1 As shown, it includes:
[0071] 101. Based on the vehicle model project generation request, obtain the target vehicle requirements and test cases corresponding to the target vehicle requirements from the preset common requirements document.
[0072] The target vehicle requirements and their corresponding test cases are applicable to at least two types of vehicle models. The preset common requirements document is used to store reusable target vehicle requirements and their corresponding test cases. The preset common requirements document can use functional characteristic work items to classify or associate the various target vehicle requirements and their corresponding test cases, such as "windshield wiper function" or "high voltage power-on / off," etc., which are not specifically limited in this embodiment. Alternatively, preset defined symbol rules can be used to classify or associate the various target vehicle requirements and their corresponding test cases, such as "A" representing the undercarriage system, "A-1" representing wheel components, etc., which are not specifically limited in this embodiment.
[0073] The vehicle model project generation request can lock the target vehicle requirements and corresponding test cases from the preset public requirements document by carrying functional feature work items or preset terminology symbols.
[0074] 102. Generate vehicle model project documentation based on the target vehicle requirements and test cases corresponding to the target vehicle requirements.
[0075] A vehicle software development platform is built within the Automotive Lifecycle Management (ALM) system. Data storage within this platform is divided into two parts: a first, a common storage area containing pre-defined common requirement documents, such as Product Requirements Documents (PRDs); and a second, a dedicated area for vehicle model projects, where each type of vehicle model project has its own independent storage area containing vehicle model project documents, such as a specific vehicle model's PRD document. These vehicle model project documents originate from the platform's documentation. When reused in a vehicle model project, the document title is modified, but the internal structure remains unchanged. The relationship between vehicle model project documents and platform documents within a vehicle model project is one of reference.
[0076] From step 101, the target vehicle requirements and test cases corresponding to the vehicle model project are obtained, and a vehicle model project document is generated. The vehicle model project document is then stored in the dedicated area for vehicle model projects of the vehicle software development platform, separately from the preset public requirement document in the public storage area.
[0077] 103. Modify the target vehicle requirements and test cases corresponding to the target vehicle requirements in the vehicle model project document, or build new vehicle requirements and test cases corresponding to the new vehicle requirements.
[0078] 104. Determine whether the number of vehicle types to which the target vehicle requirements and test cases corresponding to the modified vehicle model project are applicable, or the number of new vehicle requirements and test cases corresponding to the new vehicle requirements of the constructed vehicle model project, exceeds a preset threshold.
[0079] The preset threshold can be set to 1 or 2, and this embodiment does not specifically limit it; R&D personnel can analyze how many types of vehicles the target vehicle requirements and test cases corresponding to the modified vehicle model project and the new vehicle requirements and test cases corresponding to the new vehicle model project can be applied to. If the preset threshold is 1, the judgment can be made based on the applicability to 1 vehicle model.
[0080] 105. If the number of vehicle types to which the target vehicle requirements and test cases corresponding to the modified vehicle model project are applicable exceeds a preset threshold, then the target vehicle requirements and test cases corresponding to the modified vehicle model project or the new vehicle requirements and test cases corresponding to the constructed vehicle model project will be stored in a preset common requirements document.
[0081] For example:
[0082] Assuming a preset threshold of 1, if the number of vehicle types to which the modified intelligent vehicle project's target vehicle requirements and corresponding test cases, or the newly constructed intelligent vehicle project's new vehicle requirements and corresponding test cases, are applicable is 2, then 2 is greater than 1. Therefore, the modified intelligent vehicle project's target vehicle requirements and corresponding test cases, or the newly constructed intelligent vehicle project's new vehicle requirements and corresponding test cases, are stored in a preset common requirements document within the vehicle software development platform. This allows other applicable vehicle models to access the preset common requirements document, eliminating the need for developers to redesign and redevelop, thus improving development efficiency.
[0083] 106. If the number of vehicle types to which the modified vehicle project's target vehicle requirements and test cases corresponding to the target vehicle requirements, or the constructed vehicle project's new vehicle requirements and test cases corresponding to the new vehicle requirements, are applicable is not greater than a preset threshold, then the modified vehicle project's target vehicle requirements and test cases corresponding to the target vehicle requirements, or the constructed vehicle project's new vehicle requirements and test cases corresponding to the new vehicle requirements, will be stored in the vehicle project document.
[0084] For example:
[0085] Assuming a preset threshold of 1, if the number of vehicle type projects applicable to the modified intelligent vehicle model project's target vehicle requirements and corresponding test cases, or the newly constructed intelligent vehicle model project's new vehicle requirements and corresponding test cases, is 1, then 1 equals 1. The modified intelligent vehicle model project's target vehicle requirements and corresponding test cases, or the newly constructed intelligent vehicle model project's new vehicle requirements and corresponding test cases, are stored in the intelligent vehicle model project document within the vehicle software development platform. This allows developers to directly access the intelligent vehicle model project document during subsequent intelligent vehicle development, improving development efficiency and reducing the storage load of preset common requirement documents. Based on the above... Figure 1 As can be seen from the implementation of the embodiments, the present invention provides a management method for a vehicle software development platform. The present invention obtains the target vehicle requirements and test cases corresponding to the target vehicle requirements from a preset public requirements document based on a vehicle model project generation request; generates a vehicle model project document based on the target vehicle requirements and test cases corresponding to the target vehicle requirements; modifies the target vehicle requirements and test cases corresponding to the target vehicle requirements in the vehicle model project document, or constructs new vehicle requirements and test cases corresponding to the new vehicle requirements; determines whether the number of vehicle model project types to which the modified or constructed new vehicle requirements and test cases corresponding to the new vehicle requirements are applicable exceeds a preset threshold; if yes, the modified or constructed new vehicle requirements and test cases corresponding to the new vehicle requirements are stored in the preset public requirements document; if no, the modified or constructed new vehicle requirements and test cases corresponding to the new vehicle requirements are stored in the vehicle model project document. This invention enables the storage of reusable vehicle requirements and corresponding test cases in a public storage area, and the storage of non-reusable vehicle requirements and corresponding test cases suitable for a certain type of vehicle project in a dedicated storage area for that type of vehicle project. When R&D personnel need to develop a certain type of vehicle project, they can directly retrieve and use the entire set of test cases from the dedicated storage area for that type of vehicle project. If it is necessary to add reusable test cases to the type of vehicle project, they can retrieve them from the public storage area, thereby improving R&D efficiency.
[0086] Furthermore, as a response to Figure 1 Further refinement and extension of the illustrated embodiments, this invention also provides another management method for a vehicle software development platform, such as... Figure 2As shown, the specific steps are as follows:
[0087] 201. Obtain the target vehicle requirements and the corresponding test cases.
[0088] Although different vehicle manufacturers produce various types of vehicles that are not entirely the same, these vehicles all share common and indispensable parts, such as wheels and floor panels. This embodiment does not make specific limitations on these parts. Based on the technical specifications in the vehicle field, the required components and subsystems for various types of vehicles can be analyzed, such as subsystem technical specifications and component technical specifications. This embodiment does not make specific limitations on these parts. Furthermore, it is possible to analyze the vehicle requirements applicable to various types of vehicles and the corresponding test cases. The specific analysis method can be manual analysis, which is not specifically limited in this embodiment.
[0089] The target vehicle requirement refers to a vehicle requirement applicable to at least two types of vehicles. The test cases corresponding to the target vehicle requirement are test cases that can solve the target vehicle requirement and have passed verification. Verifying test cases ensures their accuracy; verification can be performed manually, which is a conventional technique and is not specifically limited in this embodiment.
[0090] 202. Associate the target vehicle requirements, the corresponding test cases, and the functional feature work items to obtain associated data.
[0091] The attributes of the functional feature work item include mandatory attributes and optional attributes; for example: Figure 5 As shown: Feature A is a mandatory attribute feature work item, and Feature D is an optional attribute feature work item.
[0092] The functional characteristic work items include first-level functional characteristic work items and second-level functional characteristic work items, where the first-level functional characteristic work items are higher than the second-level functional characteristic work items; for example: Figure 5 As shown: The first-level functional feature work items are feature A, feature B, feature C and feature D; the second-level functional feature work items are feature A1, feature A2, feature B1, feature B2, feature B3, feature B4, feature C1, feature D1 and feature D2. Feature A1 and feature A2 are the next-level feature work items of feature A; feature B1, feature B2, feature B3 and feature B4 are the next-level feature work items of feature B; feature C1 is the next-level feature work item of feature C; and feature D1 and feature D2 are the next-level feature work items of feature D.
[0093] First, the target vehicle requirements obtained in step 201 are associated with the test cases corresponding to the target vehicle requirements to obtain associated target vehicle requirements; then, the associated target vehicle requirements are associated with the corresponding second-level functional feature work items to obtain associated second-level functional feature work items; finally, the associated second-level functional feature work items are associated with the corresponding first-level functional feature work items to obtain the associated data.
[0094] For example:
[0095] like Figure 5 As shown: REQ represents the target vehicle requirement; Testcase represents the test case; taking the first-level functional feature work item "Feature B" as an example, the downstream of the first-level functional feature work item "Feature B" is associated with the second-level functional feature work items "Feature B1", "Feature B2", "Feature B3" and "Feature B4". The downstream of the second-level functional feature work item "Feature B1" is associated with REQ2, the downstream of the second-level functional feature work item "Feature B2" is associated with REQ2 and REQ3, the downstream of the second-level functional feature work item "Feature B3" is associated with REQ2, and the downstream of the second-level functional feature work item "Feature B4" is associated with REQ4. Each of the downstream of REQ2 to REQ4 is associated with a corresponding test case. Figure 5 The other parts will not be elaborated here.
[0096] 203. Store the associated data in the preset public requirements document.
[0097] The associated data obtained in step 202 is stored in the preset public requirement document, such as the PRD product requirement document.
[0098] 204. Based on the vehicle model project generation request, obtain the target vehicle requirements and test cases corresponding to the target vehicle requirements from the preset common requirements document.
[0099] This step combines the description of step 101 in the above method, and the same content will not be repeated here.
[0100] Before generating a certain type of vehicle model project document in the vehicle software development platform, a vehicle model project generation request needs to be created; the steps for creating the vehicle model project generation request are as follows.
[0101] First, functional feature work items are pre-set on the preset functional feature selection page. The functional feature work items include the first-level functional feature work items and the second-level functional feature work items associated with it. Then, the attributes of each functional feature work item are set. The attributes can be mandatory attributes and optional attributes. Functional feature work items set as mandatory attributes are selected by default. Functional feature work items set as optional attributes need to be manually selected by the R&D personnel to determine whether to use them as needed.
[0102] Based on the attributes of the first-level functional characteristic work items, the target first-level functional characteristic work items for the vehicle model project are determined from the first-level functional characteristic work items using the preset functional characteristic selection page. The target first-level functional characteristic work items include first-level functional characteristic work items with mandatory attributes and first-level functional characteristic work items with selected optional attributes. For example, the preset functional characteristic selection page includes the first-level functional characteristic work items "Characteristic A" (mandatory attribute), "Characteristic B" (mandatory attribute), and "Characteristic C" (optional attribute). If the R&D personnel manually select "Characteristic C," and since "Characteristic A" and "Characteristic B" are mandatory attributes, the final determined target first-level functional characteristic work items are "Characteristic A," "Characteristic B," and "Characteristic C."
[0103] Then, based on the attributes of the second-level functional feature work item, the target second-level functional feature work item of the vehicle model project is determined from the second-level functional feature work items associated with the target first-level functional feature work item of the vehicle model project using the preset functional feature selection page. The target second-level functional feature work item includes second-level functional feature work items with mandatory attributes and selected second-level functional feature work items with optional attributes. For example: it is known that the preset functional feature selection page has defaulted to selecting the first-level functional feature work item "Feature B" (mandatory attribute), and it is known that the second-level functional feature work items associated with the first-level functional feature work item "Feature B" (mandatory attribute) include "Feature B1" (mandatory attribute), "Feature B2" (optional attribute), "Feature B3" (optional attribute), and "Feature B4" (optional attribute). If the R&D personnel manually select "Feature B2," and since "Feature B1" is a mandatory attribute, the final determined target second-level functional feature work items are "Feature B1" and "Feature B2".
[0104] The vehicle model project generation request is generated based on the target first-level functional characteristic work item and the target second-level functional characteristic work item of the vehicle model project; for example: the target first-level functional characteristic work item is selected as "Characteristic A", "Characteristic B" and "Characteristic C" and the target second-level functional characteristic work item "Characteristic A1" associated with "Characteristic A", the target second-level functional characteristic work item "Characteristic B1" and "Characteristic B2" associated with "Characteristic B" and the target second-level functional characteristic work item "Characteristic C1" associated with "Characteristic A", "Characteristic A1", "Characteristic B", "Characteristic B1", "Characteristic B2", "Characteristic C" and "Characteristic C1" are used to generate the vehicle model project generation request;
[0105] Based on the target first-level functional feature work item and the target second-level functional feature work item carried in the vehicle model project generation request, the target vehicle requirements associated with the target second-level functional feature work item and the test cases associated with the target vehicle requirements are obtained from a preset common requirements document, thus obtaining the target vehicle requirements corresponding to the vehicle model project and the test cases corresponding to the target vehicle requirements; for example: Figure 5 The document shows the relationships between various functional feature work items, target vehicle requirements, and test cases in the preset common requirements document. Based on the vehicle model project, the document generates requests carrying functional feature work items "Feature A", "Feature A1", "Feature B", "Feature B1", "Feature B2", "Feature C", and "Feature C1" from... Figure 5 The associated data of the preset common requirements document shown can be obtained as follows:
[0106] "Feature A" → "Feature A1" → REQ1 → Testcase
[0107] "Feature B" → "Feature B1" → REQ2 → Testcase
[0108] "Feature B" → "Feature B2" → REQ2 → Testcase
[0109] "Feature B" → "Feature B2" → REQ3 → Testcase
[0110] "Feature C" → "Feature C1" → REQ5 → Testcase
[0111] REQ1, REQ2, REQ3, and REQ5 are the target vehicle requirements corresponding to the vehicle model project; the Testcases associated with REQ1, REQ2, REQ3, and REQ5 are the test cases corresponding to the vehicle model project.
[0112] 205. Generate vehicle model project documentation based on the target vehicle requirements and test cases corresponding to the target vehicle requirements.
[0113] This step combines the description of step 102 in the above method, and the same content will not be repeated here.
[0114] 206. Modify the target vehicle requirements and test cases corresponding to the target vehicle requirements in the vehicle model project document, or build new vehicle requirements and test cases corresponding to the new vehicle requirements.
[0115] This step combines the description of step 103 in the above method, and the same content will not be repeated here.
[0116] For example:
[0117] The R&D personnel modified the original target vehicle requirements and corresponding test cases in the intelligent vehicle project document that had been established in the vehicle software R&D platform, and added new vehicle requirements and corresponding test cases to the intelligent vehicle project document.
[0118] 207. Determine whether the number of vehicle types to which the target vehicle requirements and test cases corresponding to the modified vehicle model project are applicable, or the number of new vehicle requirements and test cases corresponding to the new vehicle requirements of the constructed vehicle model project, exceeds a preset threshold.
[0119] This step combines the description of step 104 in the above method, and the same content will not be repeated here.
[0120] 208. If the number of vehicle types to which the target vehicle requirements and test cases corresponding to the modified vehicle model project are applicable exceeds a preset threshold, then the target vehicle requirements and test cases corresponding to the modified vehicle model project or the new vehicle requirements and test cases corresponding to the constructed vehicle model project will be stored in a preset common requirements document.
[0121] This step combines the description of step 105 in the above method, and the same content will not be repeated here.
[0122] 209. If the number of vehicle types to which the target vehicle requirements and test cases corresponding to the modified vehicle project are applicable, or the number of new vehicle requirements and test cases corresponding to the constructed vehicle project, are applicable does not exceed a preset threshold, then the target vehicle requirements and test cases corresponding to the modified vehicle project, or the new vehicle requirements and test cases corresponding to the constructed vehicle project, will be stored in the vehicle project document.
[0123] This step combines the description of step 106 in the above method, and the same content will not be repeated here.
[0124] Based on the above Figure 2 As can be seen from the implementation method, this invention provides a management method for a vehicle software development platform. The vehicle software development platform constructed by this invention includes common software requirements and characteristic software requirements required by vehicle models, and stores the two separately. This avoids the problem of large public storage load caused by storing all vehicle requirements and test cases in a single public database. Moreover, this invention can select vehicle requirements and test cases from the vehicle software platform for vehicle models, achieving large-scale reuse. Therefore, for vehicle models to develop in-vehicle software, only the special requirements and test cases required by the vehicle model need to be developed. The vehicle requirements and test cases reused from the vehicle software development platform do not need to be redeveloped. This effectively reduces the workload of vehicle in-vehicle software development, accelerates the development process, shortens the product launch cycle, and improves development efficiency.
[0125] Furthermore, as a response to the above Figure 1 In addition to the implementation of the method shown, this embodiment of the invention also provides a management device for a vehicle software development platform, used for the above-mentioned... Figure 1 The method shown is implemented accordingly. This device embodiment corresponds to the foregoing method embodiment. For ease of reading, this device embodiment will not repeat the details of the foregoing method embodiment, but it should be clear that the device in this embodiment can implement all the contents of the foregoing method embodiment. Figure 3 As shown, the device includes:
[0126] The first acquisition unit 31 is used to acquire the target vehicle requirements and test cases corresponding to the target vehicle requirements from a preset public requirements document according to the vehicle model project generation request, wherein the target vehicle requirements and test cases corresponding to the target vehicle requirements are applicable to at least two types of vehicle model projects.
[0127] The first generation unit 32 is used to generate the vehicle model project document based on the target vehicle requirements and test cases corresponding to the target vehicle requirements obtained from the first acquisition unit 31.
[0128] Processing unit 33 is used to modify the target vehicle requirements and test cases corresponding to the target vehicle requirements in the vehicle model project document obtained from the first generation unit 32, or to construct new vehicle requirements and test cases corresponding to the new vehicle requirements in the vehicle model project.
[0129] Judgment unit 34 is used to determine whether the number of vehicle type projects to which the target vehicle requirement and test cases corresponding to the modified vehicle type project obtained from the processing unit 33 are applicable is greater than a preset threshold.
[0130] The first storage unit 35 is configured to store the target vehicle requirements and test cases corresponding to the modified vehicle model project and the new vehicle requirements and test cases corresponding to the new vehicle requirements obtained from the judgment unit 34 into the preset common requirements document if the number of vehicle model project types to which the modified vehicle model project and the target vehicle requirements and test cases corresponding to the target vehicle requirements are applicable is greater than a preset threshold.
[0131] The second storage unit 36 is configured to store the target vehicle requirements and test cases corresponding to the modified vehicle model project obtained from the judgment unit 34, or the new vehicle requirements and test cases corresponding to the constructed vehicle model project, into the vehicle model project document if the number of vehicle model project types to which the modified target vehicle requirements and test cases corresponding to the target vehicle requirements and test cases corresponding to the target vehicle requirements and test cases corresponding to the constructed vehicle model project are applicable is not greater than a preset threshold.
[0132] The second storage unit 36 is configured to store the target vehicle requirements and test cases corresponding to the modified vehicle model project and the new vehicle requirements and test cases corresponding to the new vehicle requirements obtained from the judgment unit 34 into the vehicle model project document if the number of vehicle model project types to which the modified vehicle model project and the new vehicle requirements and test cases corresponding to the new vehicle requirements are applicable is not greater than a preset threshold.
[0133] Furthermore, as a response to the above Figure 2 In addition to the implementation of the method shown, this embodiment of the invention also provides another management device for a vehicle software development platform, used for the above-mentioned... Figure 2The method shown is implemented accordingly. This device embodiment corresponds to the foregoing method embodiment. For ease of reading, this device embodiment will not repeat the details of the foregoing method embodiment, but it should be clear that the device in this embodiment can implement all the contents of the foregoing method embodiment. Figure 4 As shown, the device includes:
[0134] The second acquisition unit 37 is used to acquire the target vehicle requirements and the test cases corresponding to the target vehicle requirements.
[0135] The association unit 38 is used to associate the target vehicle requirements, the test cases and functional feature work items corresponding to the target vehicle requirements obtained from the second acquisition unit 37 to obtain association data, wherein the attributes of the functional feature work items include mandatory attributes and optional attributes.
[0136] The third storage unit 39 is used to store the associated data obtained from the associated unit 38 into the preset public demand document;
[0137] Selection unit 40 is used to obtain the target functional characteristic work item corresponding to the vehicle model project based on the attributes of the functional characteristic work item obtained from association unit 38 using a preset functional characteristic selection page, wherein the target functional characteristic work item includes a functional characteristic work item with mandatory attributes and a functional characteristic work item with selected optional attributes.
[0138] The second generation unit 41 is used to generate a vehicle model project generation request based on the target functional characteristic work item corresponding to the vehicle model project obtained from the selection unit 40.
[0139] The first acquisition unit 31 is used to acquire the target vehicle requirements and test cases corresponding to the target vehicle requirements from a preset public requirements document according to the vehicle model project generation request obtained from the second generation unit 41, wherein the target vehicle requirements and test cases corresponding to the target vehicle requirements are applicable to at least two types of vehicle model projects.
[0140] The first generation unit 32 is used to generate the vehicle model project document based on the target vehicle requirements and test cases corresponding to the target vehicle requirements obtained from the first acquisition unit 31.
[0141] Processing unit 33 is used to modify the target vehicle requirements and test cases corresponding to the target vehicle requirements in the vehicle model project document obtained from the first generation unit 32, or to construct new vehicle requirements and test cases corresponding to the new vehicle requirements in the vehicle model project.
[0142] Judgment unit 34 is used to determine whether the number of vehicle type projects to which the target vehicle requirement and test cases corresponding to the modified vehicle type project obtained from the processing unit 33 are applicable is greater than a preset threshold.
[0143] The first storage unit 35 is configured to store the target vehicle requirements and test cases corresponding to the modified vehicle model project and the new vehicle requirements and test cases corresponding to the new vehicle requirements obtained from the judgment unit 34 into the preset common requirements document if the number of vehicle model project types to which the modified vehicle model project and the target vehicle requirements and test cases corresponding to the target vehicle requirements are applicable is greater than a preset threshold.
[0144] The second storage unit 36 is configured to store the target vehicle requirements and test cases corresponding to the modified vehicle model project and the new vehicle requirements and test cases corresponding to the new vehicle requirements obtained from the judgment unit 34 into the vehicle model project document if the number of vehicle model project types to which the modified vehicle model project and the new vehicle requirements and test cases corresponding to the new vehicle requirements are applicable is not greater than a preset threshold.
[0145] Furthermore, the functional feature work item includes a first-level functional feature work item and a second-level functional feature work item, wherein the first-level functional feature work item is higher than the second-level functional feature work item; the association unit 38 includes:
[0146] It is also used to associate the target vehicle requirements with the test cases corresponding to the target vehicle requirements to obtain the associated target vehicle requirements;
[0147] It is also used to associate the associated target vehicle requirements with the corresponding second-level functional feature work items to obtain the associated second-level functional feature work items;
[0148] It is also used to associate the associated second-level functional feature work item with the corresponding first-level functional feature work item to obtain the associated data.
[0149] Furthermore, the preset functional feature selection page includes first-level functional feature work items and second-level functional feature work items; the selection unit 40 includes:
[0150] The first selection module 401 is used to determine the target first-level functional feature work item of the vehicle model project from the first-level functional feature work items based on the attributes of the first-level functional feature work items using the preset functional feature selection page, wherein the target first-level functional feature work item includes first-level functional feature work items with mandatory attributes and first-level functional feature work items with selected optional attributes.
[0151] The second selection module 402 is used to determine the target second-level functional characteristic work item of the vehicle model project from the second-level functional characteristic work items associated with the target first-level functional characteristic work item of the vehicle model project obtained by the first selection module 401, based on the attributes of the second-level functional characteristic work item, using the preset functional characteristic selection page. The target second-level functional characteristic work item includes a second-level functional characteristic work item with mandatory attributes and a second-level functional characteristic work item with selected optional attributes.
[0152] Furthermore, the second generating unit 41 includes:
[0153] It is also used to generate a vehicle model project generation request based on the target first-level functional characteristic work item and the target second-level functional characteristic work item of the vehicle model project.
[0154] Furthermore, the first acquisition unit 31 includes:
[0155] It is also used to obtain the target vehicle requirements associated with the target second-level functional feature work item and the test cases associated with the target vehicle requirements from a preset public requirements document based on the target first-level functional feature work item and the target second-level functional feature work item carried in the vehicle model project generation request, so as to obtain the target vehicle requirements corresponding to the vehicle model project and the test cases corresponding to the target vehicle requirements.
[0156] Furthermore, embodiments of the present invention also provide a processor for running a program, wherein the program executes the above-described... Figure 1-2 The management method of the whole vehicle software R&D platform described in the document.
[0157] Furthermore, embodiments of the present invention also provide a storage medium for storing a computer program, wherein the computer program, when running, controls the device where the storage medium is located to execute the above-described... Figure 1-2 The management method of the whole vehicle software R&D platform described in the document.
[0158] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.
[0159] It is understood that the relevant features in the above methods and apparatus can be referenced interchangeably. Furthermore, the terms "first," "second," etc., in the above embodiments are used to distinguish between embodiments and do not represent the superiority or inferiority of any particular embodiment.
[0160] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0161] The algorithms and displays provided herein are not inherently related to any particular computer, virtual system, or other device. Various general-purpose systems can also be used in conjunction with the teachings herein. The required structure for constructing such systems is apparent from the above description. Furthermore, this invention is not directed to any particular programming language. It should be understood that the contents of the invention described herein can be implemented using various programming languages, and the above description of specific languages is for the purpose of disclosing the best mode of implementation of the invention.
[0162] In addition, the memory may include non-permanent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.
[0163] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0164] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.
[0165] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0166] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.
[0167] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0168] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.
[0169] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.
[0170] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.
[0171] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0172] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.
Claims
1. A management method for a vehicle software development platform, characterized in that, The method includes: According to the vehicle model project generation request, the target vehicle requirements and test cases corresponding to the target vehicle requirements are obtained from the preset public requirements document. The target vehicle requirements and test cases corresponding to the target vehicle requirements are applicable to at least two types of vehicle model projects. The vehicle model project document is generated based on the target vehicle requirements and the test cases corresponding to the target vehicle requirements. Modify the target vehicle requirements and test cases corresponding to the target vehicle requirements in the vehicle model project document, or construct new vehicle requirements and test cases corresponding to the new vehicle requirements; Determine whether the number of vehicle model types to which the target vehicle requirement and test cases corresponding to the modified vehicle model project are applicable, or the number of new vehicle requirements and test cases corresponding to the constructed vehicle model project, are applicable, is greater than a preset threshold. If so, the target vehicle requirements and test cases corresponding to the modified vehicle model project or the new vehicle requirements and test cases corresponding to the constructed vehicle model project are stored in the preset common requirements document. If not, then the target vehicle requirements and test cases corresponding to the modified vehicle model project or the new vehicle requirements and test cases corresponding to the constructed vehicle model project are stored in the vehicle model project document. Before obtaining the target vehicle requirements and test cases corresponding to the target vehicle requirements from a preset common requirements document based on the vehicle model project generation request, the method includes: Obtain the target vehicle requirements and the corresponding test cases; The target vehicle requirements, the corresponding test cases, and the functional feature work items are associated to obtain associated data, wherein the attributes of the functional feature work items include mandatory attributes and optional attributes. Store the associated data in the preset public requirements document; The method further includes: Based on the attributes of the functional feature work item, the target functional feature work item corresponding to the vehicle model project is obtained using a preset functional feature selection page. The target functional feature work item includes functional feature work items with mandatory attributes and functional feature work items with selected optional attributes. The vehicle model project generation request is generated based on the target functional characteristic work item corresponding to the vehicle model project.
2. The method according to claim 1, characterized in that, The functional feature work items include first-level functional feature work items and second-level functional feature work items, with the first-level functional feature work items being higher than the second-level functional feature work items; The process of associating the target vehicle requirements, the corresponding test cases, and the functional feature work items to obtain associated data includes: The target vehicle requirements are associated with the test cases corresponding to the target vehicle requirements to obtain the associated target vehicle requirements; The associated target vehicle requirements are associated with the corresponding second-level functional feature work items to obtain the associated second-level functional feature work items. The associated second-level functional feature work item is associated with the corresponding first-level functional feature work item to obtain the associated data.
3. The method according to claim 2, characterized in that, The preset functional feature selection page includes first-level functional feature work items and second-level functional feature work items; The method of obtaining the target functional characteristic work item corresponding to the vehicle model project based on the attributes of the functional characteristic work item using a preset functional characteristic selection page includes: Based on the attributes of the first-level functional feature work item, the target first-level functional feature work item of the vehicle model project is determined from the first-level functional feature work items using the preset functional feature selection page. The target first-level functional feature work item includes first-level functional feature work items with mandatory attributes and first-level functional feature work items with selected optional attributes. Based on the attributes of the second-level functional feature work item, the target second-level functional feature work item of the vehicle model project is determined from the second-level functional feature work items associated with the target first-level functional feature work item of the vehicle model project using the preset functional feature selection page. The target second-level functional feature work item includes second-level functional feature work items with mandatory attributes and second-level functional feature work items with selected optional attributes.
4. The method according to claim 3, characterized in that, The step of generating the vehicle model project generation request based on the target functional characteristic work item corresponding to the vehicle model project includes: The vehicle model project generation request is generated based on the target first-level functional characteristic work item and the target second-level functional characteristic work item of the vehicle model project.
5. The method according to claim 4, characterized in that, The step of obtaining the target vehicle requirements and test cases corresponding to the target vehicle requirements from a preset common requirements document based on the vehicle model project generation request includes: Based on the target first-level functional feature work item and the target second-level functional feature work item carried in the vehicle model project generation request, the target vehicle requirements associated with the target second-level functional feature work item and the test cases associated with the target vehicle requirements are obtained from the preset public requirements document, thereby obtaining the target vehicle requirements corresponding to the vehicle model project and the test cases corresponding to the target vehicle requirements.
6. A management device for a vehicle software development platform, implementing the management method for the vehicle software development platform according to any one of claims 1 to 5, characterized in that, include: The first acquisition unit is used to acquire the target vehicle requirements and test cases corresponding to the target vehicle requirements from a preset public requirements document according to the vehicle model project generation request, wherein the target vehicle requirements and test cases corresponding to the target vehicle requirements are applicable to at least two types of vehicle model projects. The first generation unit is used to generate the vehicle model project document based on the target vehicle requirements corresponding to the vehicle model project and the test cases corresponding to the target vehicle requirements. The processing unit is used to modify the target vehicle requirements and test cases corresponding to the target vehicle requirements in the vehicle project document, or to construct new vehicle requirements and test cases corresponding to the new vehicle requirements in the vehicle project document. The judgment unit is used to determine whether the number of vehicle types to which the target vehicle requirement and the test cases corresponding to the modified vehicle model project are applicable, or the new vehicle requirement and the test cases corresponding to the constructed vehicle model project are applicable, is greater than a preset threshold. The first storage unit is configured to store the target vehicle requirements and test cases corresponding to the target vehicle requirements, or the new vehicle requirements and test cases corresponding to the new vehicle requirements, applicable to the modified vehicle model project and the new vehicle requirements, into the preset common requirements document if the number of vehicle model project types to which the modified vehicle model project and the target vehicle requirements and the test cases corresponding to the target vehicle requirements and the new vehicle requirements are applicable is greater than a preset threshold. The second storage unit is configured to store the target vehicle requirements and test cases corresponding to the modified vehicle model project, or the new vehicle requirements and test cases corresponding to the constructed vehicle model project, into the vehicle model project document if the number of vehicle model project types to which the modified target vehicle requirements and test cases corresponding to the target vehicle requirements and test cases corresponding to the constructed vehicle model project are applicable is not greater than a preset threshold.
7. A storage medium comprising a stored program, characterized in that, When the program is running, it controls the device where the storage medium is located to execute the management method of the whole vehicle software R&D platform according to any one of claims 1 to 5.
8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the management method of the vehicle software development platform as described in any one of claims 1 to 5.
Citation Information
Patent Citations
A network test management system and method for commercial vehicle based on distributed system
CN109086213A
Demand document processing method and device, computer equipment and storage medium
CN112580363A