A model-based electric drive system requirement analysis and architecture design method

Abstract

The application discloses a kind of based on model electric drive system demand analysis and architecture design method, including using SysML demand model to capture stakeholder demand, and stakeholder demand is converted into modelled system demand;Based on modelled system demand, design is used to describe the system architecture model of electric drive system logic component and the interactive relationship between components, and one-dimensional simulation is used to virtually verify system architecture model, and the optimized system architecture model is obtained according to the verification result;The optimized system architecture model is recursively decomposed into subsystem architecture model layer by layer, and each subsystem architecture model is used as input with the current level of subsystem architecture model, and the same architecture design and virtual verification operation as described above is repeatedly executed until the optimal design scheme of electric drive architecture is obtained.The technical problems that traditional document-based system engineering exists in electric drive system development, such as inconsistent demand, poor traceability and inability to virtually verify and optimize the scheme in the early stage of the scheme are solved.

Description

Technical Field

[0001] This invention relates to the field of requirements analysis and architecture modeling, and in particular to a model-based method for requirements analysis and architecture design of electric drive systems. Background Technology

[0002] With the increasing integration and complexity of electric drive products in new energy vehicles, electric drive systems involve the cross-disciplinary integration of multiple disciplines such as mechanics, electrical engineering, and software, significantly increasing their development difficulty. Currently, the industry generally adopts document-based systems engineering methods for requirements analysis and architecture design, that is, describing the system through texts such as requirements specifications, interface documents, and design reports written in natural language. However, traditional systems engineering suffers from problems such as the dispersion and inconsistency of its documents and the difficulty in intuitively expressing the complex relationships of the system, resulting in long system development cycles, high costs, high risks, and difficulty in guaranteeing system quality and performance. By establishing a visual system model, the relationships between various elements of the system can be clearly expressed, effectively integrating multidisciplinary knowledge and improving the efficiency and quality of systems engineering design, becoming a key development direction in the field of complex product systems engineering design.

[0003] To address these issues, existing research has attempted to introduce Model-Based Systems Engineering (MBSE) development methodologies. MBSE emphasizes using formal models to describe systems throughout the entire systems engineering lifecycle, rather than relying solely on documentation. These models can comprehensively and accurately capture key information such as system requirements, functions, structure, and behavior, providing a consistent foundation for system design, analysis, verification, and validation. Compared to document-based systems engineering, it significantly improves communication efficiency and enables closer and more efficient cross-domain collaboration. However, existing MBSE solutions are mostly geared towards general systems in fields such as aerospace and nuclear energy, lacking a complete process specifically designed for electric drive systems in new energy vehicles, spanning from requirements analysis to architecture design and integrating early simulation verification. In particular, electric drive systems have unique quantitative requirements for performance indicators such as power, economy, and drivability. Existing methods have not yet provided a systematic solution for how to effectively decompose business indicators into system performance parameters during the requirements analysis phase and conduct virtual verification and solution optimization through one-dimensional simulation in the early stages of architecture design.

[0004] Therefore, existing technologies urgently need a new technical solution to address the above problems. Summary of the Invention

[0005] To address the aforementioned shortcomings of existing technologies, this invention provides a model-based method for requirements analysis and architecture design of electric drive systems. By using SysML for model-based requirements analysis and architecture design, and integrating one-dimensional simulation virtual verification, it solves the technical problems of inconsistent requirements, poor traceability, and inability to perform virtual verification and scheme optimization in the early stages of electric drive system development in traditional document-based systems engineering.

[0006] To solve the above-mentioned technical problems, the present invention adopts the following technical solution:

[0007] A model-based method for requirements analysis and architecture design of electric drive systems includes the following steps:

[0008] S1. Use the SysML requirements model to capture stakeholder requirements and transform the stakeholder requirements into modeled system requirements.

[0009] S2. Based on the modeled system requirements, design a system architecture model to describe the logical components of the electric drive system and the interaction relationships between the components, and use one-dimensional simulation to virtually verify the system architecture model. Optimize the system architecture model based on the verification results to obtain the optimized system architecture model.

[0010] S3. The optimized system architecture model is recursively decomposed into subsystem architecture models layer by layer. For each subsystem architecture model, the same system architecture model design and virtual verification operation as step S2 is repeatedly executed, taking the current level subsystem architecture model as input, until the optimal design scheme of the electric drive architecture is obtained.

[0011] Furthermore, step S1 specifically includes:

[0012] S101. Identify and classify stakeholders, and output a list of stakeholder needs as stakeholder requirements;

[0013] S102. Based on the aforementioned list of stakeholder requirements, use a SysML block definition diagram to depict the system context, define the system boundary, identify the information interaction, energy interaction, and matter interaction between the system and the external environment, and output the system's interface requirements.

[0014] S103. Based on the aforementioned list of stakeholder requirements, use SysML use case diagrams to describe the interaction between external participants and the system, use SysML activity diagrams to model and simulate the scenario behavior logic, and assign functions to the logical architecture through swimlanes. At the same time, use SysML requirement diagrams to establish functional requirement items, and output the modeled functional requirements after decoupling the functional requirements from the corresponding performance indicators.

[0015] S104. Quantify the total business indicators, define each business indicator, set thresholds and decompose units, and decompose the business indicators layer by layer through quantitative simulation analysis to output modeled performance requirements.

[0016] S105. Establish the traceability relationship between the functional requirements, performance requirements, and interface requirements and the upstream stakeholder requirements through the requirements model, and output the modeled system requirements.

[0017] Furthermore, step S2 specifically includes:

[0018] S201. Logical Architecture Construction: Based on the functional requirements in the modeled system requirements, identify the logical components of the system functions, decompose the logical components hierarchically, define the interfaces between logical components to form an interface control document, and output the logical architecture model of the system hierarchy.

[0019] S202, System Function Allocation: Based on the logical architecture model and the modeled functional requirements, the system functions are recursively refined into subsystem functions using SysML activity diagrams. The correctness of the system functions is verified through functional behavior simulation. The verified system functions are then allocated to each logical component through logical mapping, and the functional architecture model is output.

[0020] S203. System Performance Verification and Optimization: Based on the functional architecture model and the modeled performance requirements, use SysML to perform quantitative analysis and modeling of performance indicators, and perform virtual verification through one-dimensional mechanism simulation. Based on the verification results, optimize and reallocate the performance parameters, and output the optimized system architecture model.

[0021] Furthermore, the characteristic feature is that step S3 specifically includes:

[0022] S301. Using the optimized system architecture model as input, its logical components, system functions, and corresponding performance indicators are used as the initial input of the subsystem architecture model at the current level to derive the modeled system requirements at the subsystem level.

[0023] S302. Taking the modeled system requirements of the subsystem level as input, repeatedly execute the logical architecture construction, system function allocation and system performance verification and optimization operations in steps S201 to S203, and output the subsystem architecture model of the current level after virtual verification and optimization.

[0024] S303. Determine whether the subsystem architecture model of the current level has reached the preset physical implementation level of the electric drive system. If yes, terminate the recursion and output the optimal design scheme of the electric drive architecture. If no, use the subsystem architecture model of the current level as the input of the next level and return to step S301 to continue recursive decomposition and verification.

[0025] Furthermore, in step S104, parameter constraints are established through constraint block elements to perform quantitative simulation analysis on key business indicators of different dimensions.

[0026] Furthermore, in step S202, after allocating the verified system functions to the logic components, the system functions are also organized and optimized to remove redundant functions.

[0027] Furthermore, in step S203, the parameters of the one-dimensional simulation model are calibrated by combining historical experimental data, and the performance parameters are optimized through experimental design.

[0028] Furthermore, in the recursive decomposition process of step S3, the logical architecture construction, system function allocation, and system performance verification and optimization operations are carried out through continuous interactive iteration.

[0029] Compared with the prior art, the present invention has the following technical effects:

[0030] 1. This invention employs tools such as SysML requirement models, block definition diagrams, use case diagrams, and activity diagrams for requirement capture, contextual environment analysis, use case scenario analysis, and business indicator analysis. It transforms stakeholder requirements into structured and modeled system requirements, and decouples and aggregates functional requirements, performance requirements, and interface requirements. This eliminates ambiguity and comprehension biases caused by natural language descriptions. Through the traceability relationship of the requirement model, it achieves a complete closed-loop traceability from stakeholder requirements to system architecture and then to subsystems. When requirements change, the scope of impact can be quickly located, improving the efficiency of requirement management.

[0031] 2. The logical architecture of this invention is decomposed recursively layer by layer, with each layer only expanding to the next layer, thereby effectively controlling the complexity of a single analysis; secondly, the system functions are recursively refined through activity diagrams, ensuring that atomic-level basic functional units are consistently expressed and referenced in different functional scenarios, avoiding redundant definition of functions and improving the reusability of the model; at the same time, functions are assigned to each logical component through functional logic mapping, ensuring that each functional requirement has a corresponding logical component to carry it, realizing a closed loop of requirement-function-architecture.

[0032] 3. This invention provides an understanding and analysis of system performance by establishing a mechanistic model, and obtains the optimal solution for multi-parameter combinations through Design of Experiments (DOE). By combining historical experimental data, the model parameters are calibrated to correct simulation deviations, so that the simulation model gradually approximates the behavior of the real system.

[0033] 4. This invention recursively reuses the system architecture design and virtual verification method, namely logical architecture design, functional analysis, performance analysis, and one-dimensional simulation, at the subsystem level, ensuring design consistency from the system to the subsystem and reducing communication errors and tool conversion costs introduced by level switching; at the same time, SysML is used as the unified modeling language throughout the process, enabling different technical personnel to collaborate on the same model platform, thereby improving efficiency. Attached Figure Description

[0034] To make the objectives, technical solutions, and advantages of the invention clearer, the invention will now be described in further detail with reference to the accompanying drawings, wherein:

[0035] Figure 1 This is a flowchart of a model-based electric drive system requirements analysis and architecture design method disclosed in this invention;

[0036] Figure 2 This is a model building framework diagram for the model-based electric drive system requirements analysis and architecture design method of the present invention;

[0037] Figure 3 This is a stakeholder classification architecture diagram in an embodiment of the present invention;

[0038] Figure 4 This is a stakeholder view in an embodiment of the present invention;

[0039] Figure 5 This is a contextual analysis view in an embodiment of the present invention;

[0040] Figure 6 Analysis of use case scenarios in the embodiments of the present invention;

[0041] Figure 7 This is a business indicator analysis chart in an embodiment of the present invention;

[0042] Figure 8 This is a system requirements diagram in an embodiment of the present invention;

[0043] Figure 9 This is a logical architecture diagram in an embodiment of the present invention;

[0044] Figure 10 This is a functional activity diagram in an embodiment of the present invention. Detailed Implementation

[0045] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0046] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, not all of them. Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to represent selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0047] It should be noted that similar reference numerals and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. In the description of this invention, it should be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the figures, or the orientation or positional relationship commonly used when the product is in use. They are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the invention. Furthermore, the terms "first," "second," and "third," etc., are only used to distinguish descriptions and should not be construed as indicating or implying relative importance. In addition, the terms "horizontal," "vertical," etc., do not indicate that the component is required to be absolutely horizontal or suspended, but can be slightly tilted. For example, "horizontal" simply means that its direction is more horizontal than "vertical," and does not mean that the structure must be completely horizontal, but can be slightly tilted. In the description of this invention, it should also be noted that, unless otherwise explicitly specified and limited, the terms "set," "install," "connect," and "link" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0048] Example:

[0049] Against the backdrop of the rapid development of new energy vehicles and intelligent electric drive systems, traditional electric drive system design methods face severe challenges. Existing technologies typically employ a document-driven waterfall development model, where requirements analysis, architecture design, and simulation verification are fragmented, leading to long design cycles, high iteration costs, and difficulties in requirements traceability. Particularly when dealing with complex electric drive systems, the lack of a unified modeling approach results in low collaboration efficiency between different professional fields (such as mechanical, electrical, and control), easily leading to technical defects such as missing requirements, interface mismatches, and the inability to quantify and verify performance indicators.

[0050] Therefore, to address the aforementioned technical problems, this invention proposes a model-based method for requirements analysis and architecture design of electric drive systems. This method introduces a model-based requirements analysis approach using SysML (System Modeling Language), integrating previously scattered stakeholder requirements, functional requirements, performance requirements, and interface requirements into a unified model framework, achieving visualization, traceability, and verifiability of requirements. Simultaneously, this invention integrates one-dimensional mechanism simulation with architecture design, constructing a closed-loop iterative mechanism of "requirements-architecture-simulation-optimization," enabling early verification and rapid iteration of design solutions in a virtual environment, significantly reducing the cost and risk of physical prototype development. Furthermore, this invention proposes a recursive decomposition and continuous interactive iteration design strategy, effectively solving the technical challenges in the hierarchical design of complex electric drive systems. By decomposing the system architecture layer by layer into subsystems and performing the same architecture design and virtual verification operations at each level, the consistency and integrity of the design are ensured. At the same time, the continuous interactive iteration between logical architecture construction, system function allocation, and performance verification allows the design process to be dynamically adjusted based on simulation results, thereby obtaining the optimal design solution.

[0051] Specifically, the model-based electric drive system requirements analysis and architecture design method proposed in this invention, such as... Figure 1 The flowchart shown is Figure 2 The model framework shown in this invention divides the entire development process into five core dimensions: requirements, structure, behavior, parameters, and verification. These correspond to stakeholder needs, logical architecture, functional activity analysis, business indicator analysis, and virtual simulation verification, respectively, thereby achieving a complete business closed loop from requirements to verification. Specifically, the method includes the following steps:

[0052] S1. Capture stakeholder requirements using the SysML requirements model and transform these stakeholder requirements into modeled system requirements; this step specifically includes:

[0053] S101. Initial Requirements Analysis: Identify and classify stakeholders, and output a list of stakeholder requirements as stakeholder requirements;

[0054] In this embodiment, as Figure 3 and 4 As shown, the process begins with identifying stakeholders, listing all individuals, teams, or organizations related to the product, including customers, developers, maintainers, and suppliers, to obtain each stakeholder's expectations, goals, concerns, and the extent of their impact on the product. The obtained stakeholder information is then identified and categorized, and graphical tools are used to illustrate the relationships and mutual influences between different stakeholders, helping to identify potential problems and risks, and outputting a list of stakeholder needs as stakeholder requirements.

[0055] S102. Context Analysis: Based on the list of stakeholder requirements, use SysML block definition diagrams to depict the system context, define the system boundaries, identify information, energy, and matter interactions between the system and the external environment, and output the system's interface requirements.

[0056] In this embodiment, as Figure 5 As shown, SysML's block definition diagram is used to depict the system context, clarify the system's scope, and define the boundaries between the system and its external environment. The context should include the system itself and all external environmental factors that interact with it, including users, other systems, and the network environment. It identifies information, energy, and matter interactions between the system and external elements, and outputs the system interface requirements.

[0057] S103. Use Case Scenario Analysis: Based on the aforementioned list of stakeholder requirements, use SysML use case diagrams to describe the interaction between external participants and the system, use SysML activity diagrams to model and simulate the scenario behavior logic, and assign functions to the logical architecture through swimlanes. At the same time, use SysML requirement diagrams to establish functional requirement items, and output the modeled functional requirements after decoupling the functional requirements from the corresponding performance indicators.

[0058] In this embodiment, as Figure 6 As shown, SysML use case diagrams are used to analyze system behavior, analyze the value points provided by the system from a higher level perspective, and use activity diagrams to decompose system behavior into system functional requirements.

[0059] S104. Business Indicator Analysis: Quantify the total business indicators, define each business indicator, set thresholds and decompose units, and decompose the business indicators layer by layer through quantitative simulation analysis to output modeled performance requirements.

[0060] In this embodiment, as Figure 7As shown, indicators for quantifying the success of a product from a business perspective are defined, namely, quantified key overall business objectives. These business indicators include cost, weight, power, drivability, etc. Then, each business indicator is defined and its required threshold is given, and the indicators are analyzed and decomposed. The business indicators are then distributed to system indicators. The system indicators are mapped to system blocks layer by layer, which facilitates business management and modeling operations. At the same time, parameter constraints are established through constraint block elements, indicators of different dimensions are unitized, and the key business indicators are decomposed layer by layer after quantitative simulation analysis.

[0061] S105. System Requirements Output: Establish the traceability relationship between the functional requirements, performance requirements, and interface requirements and the upstream stakeholder requirements through the requirements model, and output the modeled system requirements.

[0062] In this embodiment, as Figure 8 As shown, the functional model, interface model, and performance model generated in the preceding steps are described in an itemized manner using the SysML requirement model, and a traceability relationship with upstream stakeholder requirements is established. Finally, these three types of requirements are aggregated and organized into a unified model package, which serves as the input for the subsystem architecture design.

[0063] S2. Based on the modeled system requirements, design a system architecture model to describe the logical components of the electric drive system and the interactions between them. Perform virtual verification of the system architecture model using one-dimensional simulation, and optimize it based on the verification results to obtain an optimized system architecture model. This step specifically includes:

[0064] S201. Logical Architecture Design: Based on the functional requirements in the modeled system requirements, identify the logical components of the system functions, decompose the logical components hierarchically, define the interfaces between logical components to form an interface control document, and output the logical architecture model of the system hierarchy.

[0065] In this embodiment, as Figure 9 As shown, the logical architecture definition is the starting point and cornerstone of the entire logical architecture design. Its core lies in identifying the logical components that can implement the functions based on the functional requirements input from the system requirements; this is the logical architecture. This process is called logical component decomposition. The system architecture design is decomposed and expanded layer by layer. Each layer of logical architecture definition only expands to the next level of its object. Subsequent layers are expanded recursively to reduce system complexity. After the logical architecture definition is completed, logical interfaces are defined, and an interface control document is created. This document details the functional characteristics, parameter configurations, and data structures of each interface, providing clear interface specifications for subsequent development and testing.

[0066] S202. System Function Analysis: Based on the logical architecture model and the modeled functional requirements, the system functions are recursively refined into subsystem functions using SysML activity diagrams. The correctness of the system functions is verified through functional behavior simulation. The verified system functions are then assigned to each logical component through logical mapping, and the functional architecture model is output.

[0067] In this embodiment, as Figure 10 As shown, by expanding through activity diagrams, the system functions are decomposed into subsystem functions to achieve recursive refinement of functions. Functional behavior analysis ensures a comprehensive understanding and breakdown of system functions, guaranteeing the correctness and completeness of function expression in the architecture, forming functional units that constitute the functional architecture. By drawing activity diagrams, the interaction relationships and control flows between various functional components within the system can be clearly displayed, which helps to understand the overall structure and working principle of the system and provides a foundation for subsequent functional behavior simulation and function-logic allocation. The activity diagrams also expand recursively downwards, focusing on the behavior of the current analysis level. Through functional behavior simulation, the correctness of the system functions and whether they meet the expectations of the scenario, as well as the performance under different conditions, can be verified. Through functional logic mapping, system functions are allocated to various logical components or modules of the system, ensuring that each logical component undertakes functions that match its capabilities, and that each functional requirement is carried out by the design, improving the reliability and economy of the system. Next, the system functions need to be organized and optimized to remove redundant functions, ensure the simplicity and efficiency of the system, and ensure that the atomic-level basic functional units are consistently expressed and referenced in different functional scenarios.

[0068] S203. System Performance Verification and Optimization: Based on the functional architecture model and the modeled performance requirements, use SysML to perform quantitative analysis and modeling of performance indicators, and perform virtual verification through one-dimensional mechanism simulation. Based on the verification results, optimize and reallocate the performance parameters, and output the optimized system architecture model.

[0069] In this embodiment, performance index analysis is performed using the SysML language, mainly including three stages: performance index definition, quantitative analysis and modeling of indicators, and performance index decomposition. The system performance analysis process involves decomposing the performance indicators analyzed upstream down to the subsystem level. The purpose is to clarify the performance targets of the subsystems in their design and production, while also constraining the verification and validation process to ensure that these decomposed indicators are tested and accepted. Furthermore, by establishing a mechanistic model, the design object is analyzed in the early stages of the solution, and parameters are optimized using DOE (Design of Engineering). Model parameters are calibrated using experimental data, and the model confidence level is iterated step-by-step to optimize the rationality of performance parameter allocation.

[0070] S3. Recursively decompose the optimized system architecture model into subsystem architecture models layer by layer. For each subsystem architecture model, using the current level's subsystem architecture model as input, repeat the same system architecture model design and virtual verification operation as in step S2 until the optimal design scheme of the electric drive architecture is obtained. This step specifically includes:

[0071] S301. Using the optimized system architecture model as input, its logical components, system functions, and corresponding performance indicators are used as the initial input of the subsystem architecture model at the current level to derive the modeled system requirements at the subsystem level.

[0072] S302. Taking the modeled system requirements of the subsystem level as input, repeat the same logical architecture construction, system function allocation and system performance verification and optimization operations as in step S2, and output the subsystem architecture model of the current level after virtual verification and optimization.

[0073] S303. Determine whether the subsystem architecture model of the current level has reached the preset physical implementation level of the electric drive system. If yes, terminate the recursion and output the optimal design scheme of the electric drive architecture. If no, use the subsystem architecture model of the current level as the input of the next level and return to step S301 to continue recursive decomposition and verification.

[0074] During the recursive decomposition process, the logical architecture construction, system function allocation, and system performance verification and optimization are carried out through continuous interactive iteration. Specifically, this manifests as iteration between logical component decomposition and functional model swimlanes, interactive iteration between logical interface definition and functional model object flow, and iteration between logical component decomposition and performance indicator allocation. This process continues until the subsystem architecture model reaches the preset physical implementation level, ultimately outputting the optimal design scheme for the electric drive architecture.

[0075] In summary, the model-based electric drive system requirements analysis and architecture design method proposed in this embodiment aims to address the problems faced by traditional document-based systems engineering in developing increasingly complex new energy vehicle electric drive systems, such as long development cycles, high costs, difficulties in cross-domain collaboration, and ambiguous and untraceable requirements. This embodiment starts from stakeholder needs and innovatively uses SysML to construct a formalized requirements and architecture model, transforming stakeholder requirements into structured system requirements, and then designing the logical architecture of the system and its subsystems based on this. Its core lies in deeply integrating virtual verification methods such as one-dimensional mechanism simulation into the design process, allowing for quantitative evaluation and optimization of the functional correctness and performance indicators of the architecture model early in the design process. The entire design process adopts a layer-by-layer recursive decomposition approach, ensuring consistency and integrity from system to subsystem design, and achieving closed-loop collaboration of requirements, functions, logic, and performance through continuous interactive iteration.

[0076] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit the technical solutions. Those skilled in the art should understand that any modifications or equivalent substitutions to the technical solutions of the present invention without departing from the spirit and scope of the present invention should be covered within the scope of the claims of the present invention.

Claims

1. A model-based method for requirements analysis and architecture design of electric drive systems, characterized in that, Includes the following steps: S1. Use the SysML requirements model to capture stakeholder requirements and transform the stakeholder requirements into modeled system requirements. S2. Based on the modeled system requirements, design a system architecture model to describe the logical components of the electric drive system and the interaction relationships between the components, and use one-dimensional simulation to virtually verify the system architecture model. Optimize the system architecture model based on the verification results to obtain the optimized system architecture model. S3. The optimized system architecture model is recursively decomposed into subsystem architecture models layer by layer. For each subsystem architecture model, the same system architecture model design and virtual verification operation as step S2 is repeatedly executed, taking the current level subsystem architecture model as input, until the optimal design scheme of the electric drive architecture is obtained.

2. The model-based electric drive system requirements analysis and architecture design method according to claim 1, characterized in that, Step S1 specifically includes: S101. Identify and classify stakeholders, and output a list of stakeholder needs as stakeholder requirements; S102. Based on the aforementioned list of stakeholder requirements, use a SysML block definition diagram to depict the system context, define the system boundary, identify the information interaction, energy interaction, and matter interaction between the system and the external environment, and output the system's interface requirements. S103. Based on the aforementioned list of stakeholder requirements, use SysML use case diagrams to describe the interaction between external participants and the system, use SysML activity diagrams to model and simulate the scenario behavior logic, and assign functions to the logical architecture through swimlanes. At the same time, use SysML requirement diagrams to establish functional requirement items, and output the modeled functional requirements after decoupling the functional requirements from the corresponding performance indicators. S104. Quantify the total business indicators, define each business indicator, set thresholds and decompose units, and decompose the business indicators layer by layer through quantitative simulation analysis to output modeled performance requirements. S105. Establish the traceability relationship between the functional requirements, performance requirements, and interface requirements and the upstream stakeholder requirements through the requirements model, and output the modeled system requirements.

3. The model-based electric drive system requirements analysis and architecture design method according to claim 1 or 2, characterized in that, Step S2 specifically includes: S201. Logical Architecture Construction: Based on the functional requirements in the modeled system requirements, identify the logical components of the system functions, decompose the logical components hierarchically, define the interfaces between logical components to form an interface control document, and output the logical architecture model of the system hierarchy. S202, System Function Allocation: Based on the logical architecture model and the modeled functional requirements, the system functions are recursively refined into subsystem functions using SysML activity diagrams. The correctness of the system functions is verified through functional behavior simulation. The verified system functions are then allocated to each logical component through logical mapping, and the functional architecture model is output. S203. System Performance Verification and Optimization: Based on the functional architecture model and the modeled performance requirements, use SysML to perform quantitative analysis and modeling of performance indicators, and perform virtual verification through one-dimensional mechanism simulation. Based on the verification results, optimize and reallocate the performance parameters, and output the optimized system architecture model.

4. The model-based electric drive system requirements analysis and architecture design method according to any one of claims 3, characterized in that, Step S3 specifically includes: S301. Using the optimized system architecture model as input, its logical components, system functions, and corresponding performance indicators are used as the initial input of the subsystem architecture model at the current level to derive the modeled system requirements at the subsystem level. S302. Taking the modeled system requirements of the subsystem level as input, repeatedly execute the logical architecture construction, system function allocation and system performance verification and optimization operations in steps S201 to S203, and output the subsystem architecture model of the current level after virtual verification and optimization. S303. Determine whether the subsystem architecture model of the current level has reached the preset physical implementation level of the electric drive system. If yes, terminate the recursion and output the optimal design scheme of the electric drive architecture. If no, use the subsystem architecture model of the current level as the input of the next level and return to step S301 to continue recursive decomposition and verification.

5. The model-based electric drive system requirements analysis and architecture design method according to claim 2, characterized in that, In step S104, parameter constraints are established through constraint block elements to perform quantitative simulation analysis on key business indicators of different dimensions.

6. The model-based electric drive system requirements analysis and architecture design method according to claim 3, characterized in that, In step S202, after assigning the verified system functions to the logic components, the system functions are further organized and optimized to remove redundant functions.

7. The model-based electric drive system requirements analysis and architecture design method according to claim 3, characterized in that, In step S203, the parameters of the one-dimensional simulation model are calibrated by combining historical test data, and the performance parameters are optimized through experimental design.

8. The model-based electric drive system requirements analysis and architecture design method according to claim 4, characterized in that, In the recursive decomposition process of step S3, the logical architecture construction, system function allocation, and system performance verification and optimization operations are carried out in a continuous interactive iteration.

Images