A method for modeling and analyzing development requirements of a mechatronic complex system

Abstract

The application provides a development demand modeling analysis method of a mechatronic hydraulic complex system, comprising the following steps: S1, performing stakeholder analysis to identify stakeholders and stakeholder demands, and generating a tracking matrix between the stakeholders and the stakeholder demands; S2, performing use case analysis to determine system function demands of a system to be developed based on the tracking matrix; S3, performing system environment analysis to determine system interface demands of the system to be developed; S4, performing index analysis to determine system performance demands of the system to be developed; and S5, determining system development demands according to the system function demands, the system external interface demands and the system performance demands. The technical scheme of the application can improve the system development demand obtaining speed and reduce the product research and development cycle.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of system engineering, and in particular to a development requirement modeling analysis method for mechatronic complex systems. BACKGROUND

[0002] System development requirements, as the basis for system development and design, have a decisive role in the functions, performance and other characteristics of the final system. Mechatronic complex system design includes innovative design based on new requirements and modification design based on existing systems. Traditional mechatronic complex system development requirements are mostly structured decomposition based on documents. This decomposition method is mainly used for modification design of existing mature systems, and has problems such as text ambiguity, difficulty or incompleteness of requirement tracing. For mechatronic complex system innovation design oriented to new user requirements, there are problems such as instability of stakeholders, frequent iteration of stakeholder requirements, etc. in the early stage of system development, which further leads to frequent changes of system development requirements, and affects the speed of obtaining system development requirements due to frequent changes of system development requirements, and increases the product development cycle. SUMMARY

[0003] In order to solve at least one of the technical problems in the prior art, the present application provides a development requirement modeling analysis method for mechatronic complex systems.

[0004] The present application provides a development requirement modeling analysis method for mechatronic complex systems, comprising:

[0005] S1, performing stakeholder analysis to identify stakeholders and stakeholder requirements, and generating a tracking matrix between the stakeholders and the stakeholder requirements;

[0006] S2, performing use case analysis to determine the system function requirements of the system to be developed based on the tracking matrix;

[0007] S3, performing system environment analysis to determine the system interface requirements of the system to be developed;

[0008] S4, performing index analysis to determine the system performance requirements of the system to be developed;

[0009] S5, determining the system development requirements according to the system function requirements, the system external interface requirements and the system performance requirements.

[0010] Optionally, the S1 comprises:

[0011] Based on the characteristics of the system to be developed, a state machine diagram is used to define the system full life cycle;

[0012] According to the system full life cycle, the participants related to the system to be developed are identified as stakeholders.

[0013] Identify stakeholder needs according to stakeholders.

[0014] Optionally, the S1 comprises:

[0015] Classify the stakeholders in the form of package diagram;

[0016] Model the needs of the stakeholders according to the needs diagram, and associate the needs with the corresponding stakeholders.

[0017] Optionally, the S1 comprises: constructing a needs tracking tree representing the traceability relationship between the stakeholders and the corresponding needs;

[0018] Optionally, the S2 comprises:

[0019] According to the tracking matrix, filter the functional needs by using the functional needs table;

[0020] Create use cases based on the functional needs by using the use case diagram to describe the use scenarios of the system in the form of verb-object phrases;

[0021] Draw the system boundary by using the use case diagram, and establish the association relationship between the stakeholders outside the boundary and the use cases inside the boundary;

[0022] Create use case activities by using the activity diagram;

[0023] Determine the functional needs of the system based on the functional needs table, the activity diagram and each of the use case diagrams.

[0024] Optionally, the S2 comprises: performing functional needs traceability to construct a functional needs tracking tree and an activity allocation table.

[0025] Optionally, the S2 comprises: constructing a functional needs tracking tree representing the traceability relationship between the stakeholders and the corresponding needs.

[0026] Optionally, the S3 comprises:

[0027] Define the system environment composition elements by using the block definition diagram;

[0028] Establish the system composition relationship by using the internal block diagram to describe the interfaces and the data transmitted between the composition elements;

[0029] Obtain the system interface needs according to the block definition diagram and the internal block diagram.

[0030] Optionally, the S4 comprises:

[0031] Define the system validity measure by using the block definition diagram, and carry out index analysis to create the decomposed constraint information;

[0032] The constraint information decomposed is counted by using a constraint statistics table;

[0033] The participating element composition of index solving is established by using a block definition diagram, and the binding relationship between input and output parameters and constraints is established by using a parameter diagram, and the parameter combination satisfying the system validity measure is calculated as the performance requirement of the system to be developed.

[0034] Optionally, the method comprises:

[0035] A transformation relationship model between the stakeholder requirements and the system function requirements, the system performance requirements and the system interface requirements is constructed, and a traceability relationship model between the system development requirements is further constructed;

[0036] Based on the transformation relationship model and the traceability relationship model, the change response of the system development requirements to the stakeholder requirements is determined.

[0037] One or more technical solutions provided in the embodiments of the application are obtained from the stakeholder analysis definition, and the analysis is carried out from various angles such as use function, interface, performance index, and the system development requirements are obtained, and the system development requirement obtaining efficiency is improved. Based on the requirement matrix, the system function requirements of the system to be developed are determined, so that when part of the stakeholder requirements changes, the corresponding requirement matrix can be adjusted to realize the adjustment of the system function requirements. As can be known, the numerous steps in the application can be realized based on a computer, and therefore the system function requirement confirmation efficiency can be greatly improved. By using a system modeling language, a normalized modeling representation method is used to give the model view used in each analysis stage, and a modeling analysis process for traceable, visualized and multi-angle analysis of complex system development requirements is formed. The identification of the stakeholders, the acquisition of the stakeholder requirements and the comprehensive definition and traceability of the system use scenarios, functions, performances, interfaces and other system development requirements are realized, and the system development requirements can be fully covered and changed in response to the stakeholder requirements. The patent uses a more agile model-based method to solve the problem that frequent changes are caused by unclear requirements in the early stage of system development, and further increases the workload in the whole life cycle. The system development requirement analysis iteration efficiency is improved, and the product development cycle is shortened. BRIEF DESCRIPTION OF DRAWINGS

[0038] The accompanying drawings illustrate exemplary embodiments of the present application and together with the description, explain the principles of the application, in which:

[0039] Figure 1 A flowchart of a development requirement modeling analysis method of a mechatronic complex system according to an exemplary embodiment of the application is shown;

[0040] Figure 2Another flow chart of the development requirement modeling analysis method of the mechatronic complex system according to the exemplary embodiments of the present application is shown.

[0041] Figure 3 A schematic diagram of the model type of each stage of the system development requirement analysis flow according to the exemplary embodiments of the present application is shown. DETAILED DESCRIPTION

[0042] Embodiments of the present application will be described in more detail with reference to the drawings. While certain embodiments of the present application will be shown and described below, it is to be understood that the present application can be embodied in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and fully convey the scope of the present application to those skilled in the art.

[0043] It should be understood that each of the steps in the method embodiments of the present application can be performed in a different order and / or in parallel. In addition, the method embodiments can include additional steps and / or omit performing the steps shown. The scope of the present application is not limited in this respect.

[0044] The term "comprising" and variations thereof as used herein are used inclusively, i.e., "comprising but not limited to." The term "based on" is "based at least in part on." The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments." Related terms are defined in the description that follows. It should be noted that reference to a "first," "second," etc. concept does not limit the scope of these concepts in any way, but is simply used to differentiate one concept from another.

[0045] It should be noted that the terms "a" and "an" and "the" and "at least one" and "one or more" are used interchangeably herein with the context in mind. It should be noted that the terms "first," "second," and the like, refer only to different instances of a same item and do not connote any order, precedence, or the like, in the absence of such context.

[0046] The names of the messages or information exchanged between the plurality of devices in the embodiments of the present application are used only for illustrative purposes, and are not intended to limit the scope of the messages or information.

[0047] The solution of the present application will be described below with reference to the accompanying drawings.

[0048] Referring to Figure 1 A development requirement modeling analysis method of a mechatronic complex system includes:

[0049] S1, performing stakeholder analysis to identify stakeholders and stakeholder needs, and generating a tracking matrix between the stakeholders and the stakeholder needs.

[0050] In this step, the stakeholder analysis is performed, the stakeholders related to the system to be developed are identified, the stakeholders are classified and summarized, and the stakeholder needs are obtained as the input source of the system development demand analysis.

[0051] Specifically, S1 includes: defining the system full life cycle based on the characteristics of the system to be developed using a state machine diagram; identifying the participants related to the system to be developed as stakeholders according to the system full life cycle; and identifying the stakeholder needs according to the stakeholders.

[0052] Specifically, S1 includes: classifying the stakeholders in the form of a package diagram; and modeling the stakeholder needs using a requirement diagram to associate the requirements with the corresponding stakeholders.

[0053] Specifically, S1 includes: constructing a requirement tracking tree representing the traceability relationship between the stakeholders and the corresponding needs

[0054] More specifically, step S1 defines the system full life cycle using a state machine diagram (stm) based on the characteristics of the mechatronic complex system, and describes each stage (State) of the full life cycle. For each stage of the full life cycle, the participants that may be related to the system to be developed are analyzed as stakeholders, and are classified in the form of a package diagram (pkg). For the characteristics of the mechatronic complex system, the stakeholders can be divided into users, IPT (Integrated Product Team) teams, usage sites, and related regulations. A life cycle and stakeholder tracking matrix is established to perform a stakeholder coverage check. All stakeholder needs are collected through demand acquisition methods such as investigation and interview, and are modeled using a requirement diagram (req) to divide the requirements into three types of function, performance, and constraint, and to associate the requirements with the corresponding stakeholders. After the analysis is completed, all stakeholder needs are summarized using a requirement table, the traceability relationship between the stakeholders and the corresponding needs can be viewed through the establishment of a requirement tracking tree, and finally a tracking matrix between the stakeholders and the stakeholder needs is established to perform a coverage check on the stakeholder needs, to ensure that all stakeholders have needs, and to ensure that all stakeholder needs have corresponding stakeholders.

[0055] S2, performing use case analysis to determine the system function requirements of the system to be developed based on the tracking matrix.

[0056] Use case analysis is the process from use case model to analysis model, which is the bridge between requirement and design. Use case analysis allocates system behavior to analysis class, and makes analysis class interact to complete system behavior. In this step, the use scenarios expected by stakeholders are identified, the core functions that the system should have are determined, and the value of the system is embodied.

[0057] Specifically, S2 includes: filtering functional requirements according to the tracking matrix using the functional requirement table; creating use cases based on functional requirements using use case diagrams to describe the use scenarios of the system in the form of verb-object phrases; using use case diagrams to delineate system boundaries and establish the association between stakeholders outside the boundary and use cases inside the boundary; creating use case activities using activity diagrams; determining system functional requirements based on the functional requirement table, activity diagrams, and various use case diagrams.

[0058] Specifically, S2 includes: performing functional requirement traceability to build a functional requirement tracking tree and an activity allocation table.

[0059] Specifically, S2 includes: building a functional requirement tracking tree representing the functional requirement traceability relationship of stakeholders and corresponding requirements.

[0060] More specifically: Step S2 uses the functional requirement table to filter out all stakeholder functional requirements. Based on the functional requirements, use case diagrams (uc) are used to create use cases to describe the use scenarios of the system in the form of verb-object phrases, and to embody the core value of the system. The system boundary is delineated, and the association between stakeholders outside the boundary and use cases inside the boundary is established. Activity diagrams (act) are used to refine each use case, refining the use scenario into a series of activity action sequences, creating a swim lane representing the activity execution object, and assigning activity actions to the corresponding swim lane to complete the activity allocation. The requirement tracking tree is used to establish the traceability relationship of stakeholder functional requirements, and an activity allocation table is established to analyze the activities contained in each execution object.

[0061] S3, performing system environment analysis to determine the system interface requirements of the system to be developed.

[0062] Define the external environment in which the system runs, analyze the external participants related to the system, and capture the external interface information of the system.

[0063] Specifically, S3 includes: using block definition diagrams to define system environment composition elements; using internal block diagrams to establish system composition relationships and describe interfaces and data transmitted between composition elements; obtaining system interface requirements based on block definition diagrams and internal block diagrams.

[0064] More specifically: S3 adopts block definition diagram (bdd) to define system environment elements, including the system to be developed and other related elements. Internal block diagram (ibd) is adopted to establish the relationship between system elements, describe the interface between elements and the data transmitted. The external interface information of the system to be developed is obtained.

[0065] S4, performing index analysis to determine the system performance requirements of the system to be developed.

[0066] In this step, the effectiveness measure (MOE) of the system to be developed is defined, which is used to evaluate and verify whether the system can meet the needs of stakeholders, and to decompose the key performance indicators related to the system.

[0067] Specifically: S4 includes: defining system effectiveness measure using block definition diagram, and carrying out index analysis to create decomposed constraint information; using constraint statistics table to count all decomposed constraint information; using block definition diagram to establish the participating element composition of index solving, and establishing the binding relationship between input, output parameters and constraints through parameter diagram, calculating the parameter combination satisfying the system effectiveness measure as the performance requirement of the system to be developed.

[0068] More specifically: S4 adopts block definition diagram to define system effectiveness measure and carry out index analysis to create decomposed constraint information. All decomposed constraint information is counted by constraint statistics table. Block definition diagram (bdd) is used to establish the participating element composition of index solving, and the binding relationship between input, output parameters and constraints is established through parameter diagram (par), and the parameter combination satisfying MOE is calculated as the performance requirement of the system to be developed, and all performance requirements are summarized by performance requirement statistics table.

[0069] S5, obtaining system development requirements according to system function requirements, system external interface requirements and system performance requirements.

[0070] In this step, the requirements obtained from the above different angle analysis can be classified and summarized, and passed down to the downstream as the requirement input of system layer deep analysis. Specifically: the function requirements of the system to be developed obtained from step S2 can be passed to the system layer for white box stage refinement through function inheritance, as shown in the attached Figure 3 The external interface requirements of the system to be developed are obtained from step S3. The key performance requirements of the system to be developed are obtained from step S4. The requirements captured in the above three steps are collected and organized in the form of package diagram (pkg), and exported as system development requirements.

[0071] The application can include a transformation relationship model between stakeholder needs and system function needs, system performance needs and system interface needs, and a traceability relationship model between system development needs; based on the transformation relationship model and the traceability relationship model, the system development needs are determined to change the response of the stakeholder needs.

[0072] For example, referring to Figure 3 , a system development requirement analysis process model type schematic diagram is shown, which includes black box function traceability and white box function traceability, and the stakeholders have elements users, IPT teams, use places, and related regulations, and the users have elements XX members, XX members are detailed as user44 start, user44 start is improved as start engine, start engine has elements start engine, starter power off, starter power on, start engine, starter power off, and starter power on are generalized as corresponding start engine xt, starter power off xt, and starter power on xt. Start engine xt has elements power system ignition, oil monitoring, fuel injection acceleration, start oil supply, start, separation, monitoring, supercharging, oil supply, and monitoring; power system ignition is assigned to start ignition system; oil monitoring has elements monitoring connection and abnormal handling, both of which are assigned to the system; fuel injection acceleration is assigned to the fuel system; start oil supply is assigned to the start ignition system; start is assigned to the start ignition system; separation has elements contact surface separation and receiving contact surface position signal, both of which are assigned to the start ignition system; monitoring has elements supercharging control system connection and supercharging abnormal handling, both of which are assigned to the fuel system; supercharging is assigned to the fuel system; oil supply is assigned to the lubrication system; and detection is assigned to the start ignition system.

[0073] The application can form a set of modeling analysis processes that can trace, visualize, analyze complex system development requirements from multiple angles, realize the identification of stakeholders, the acquisition of stakeholder needs, and the comprehensive definition and traceability of system development requirements such as system use scenarios, functions, performance, and interfaces, and solve the problems of system development requirement integrity, consistency, traceability, etc. in the forward design process. In addition, the application can effectively solve the frequent iteration problem of mechanical, electrical and hydraulic coupled complex system development requirements for new user needs, realize comprehensive coverage of system development requirements for stakeholder needs and response to changes, and improve the efficiency of system development requirement analysis iteration.

Claims

1. A method for modeling and analyzing development requirements of complex electromechanical-hydraulic systems, characterized in that, include: S1, Perform stakeholder analysis to identify stakeholders and stakeholder needs, and generate a tracking matrix between the stakeholders and the stakeholder needs; S2, Perform use case analysis to determine the system functional requirements of the system to be developed based on the trace matrix; S3, Perform system environment analysis to determine the external interface requirements of the system to be developed; S4, Perform indicator analysis to determine the system performance requirements of the system to be developed; S5. Determine the system development requirements based on the system functional requirements, the system external interface requirements, and the system performance requirements; S2 includes: Based on the tracking matrix, functional requirements are filtered using a functional requirements table. Based on the aforementioned functional requirements, use case diagrams are used to create use cases, which describe the system's usage scenarios in the form of verb-object phrases. Use case diagrams are used to delineate system boundaries and establish relationships between stakeholders outside the boundaries and use cases inside the boundaries; Use activity diagrams to create use case activities; Based on the functional requirements table, activity diagram, and each of the use case diagrams, the system functional requirements are determined. Perform functional requirements tracing to build a functional requirements tracking tree and activity assignment table; Construct a functional requirement tracking tree that represents the functional requirement tracing relationship between stakeholders and their corresponding needs; S3 includes: The system environment components are defined using a block definition diagram. The system composition relationship is established using internal block diagrams, which describe the interfaces between each component element and the data transmitted. Based on the block definition diagram and the internal block diagram, the external interface requirements of the system are obtained; S4 includes: The system effectiveness measure is defined using a block definition diagram, and index analysis is carried out to create the decomposed constraint information; Use a constraint statistics table to collect all decomposed constraint information; A block definition graph is used to establish the components of the index solution, and a parametric graph is used to establish the binding relationship between input and output parameters and constraints. The parameter combination that satisfies the system effectiveness measure is calculated as the performance requirements of the system to be developed.

2. The method according to claim 1, characterized in that, S1 includes: Based on the characteristics of the system to be developed, the entire lifecycle of the system is defined using a state machine diagram. Based on the entire lifecycle of the system, identify the participants related to the system to be developed as stakeholders; Identify stakeholder needs based on stakeholder information.

3. The method according to claim 1, characterized in that, S1 includes: The stakeholders are categorized in the form of a package diagram; Demand graphs are used to model the needs of the stakeholders and associate the needs with the corresponding stakeholders.

4. The method according to claim 1, characterized in that, S1 includes: constructing a demand tracking tree that represents the traceability relationship between stakeholders and their corresponding needs.

5. The method according to claim 1, characterized in that, The method includes: Construct a model of the transformation relationship between stakeholder needs and system functional requirements, system performance requirements, and system external interface requirements, as well as a model of the traceability relationship between these requirements and system development requirements; Based on the aforementioned transformation relationship model and traceability relationship model, the system development requirements are determined in response to changes in stakeholder requirements.

Images