Demand management method, system, equipment and medium based on unified data source model

Abstract

This invention discloses a requirement management method, system, device, and medium based on a unified data source model, relating to the field of model-based systems engineering technology. The steps include: designing a requirement information carrier and constructing a requirement management model based on the Model-Based Systems Engineering (MBSE) methodology and the SysML system modeling language specification; designing a data structure for the requirement management model and organizing requirement data through the data structure; adding attributes to all requirement data domains; recursively tracing back the requirement data after adding attributes and using a stack to store the current backtracking path; storing the requirement change attributes in the current backtracking path; filling out a requirement change form when requesting a requirement change; and performing requirement baseline control and version traceability. This invention redesigns the requirement traceability method based on requirement traceability and requirement verification mechanisms, solving the problem of the lack of a complete requirement traceability chain in the traceability matrix, and realizing requirement change control and change traceability, requirement baseline control, and version traceability.

Description

Technical Field

[0001] The present invention relates to the technical field of model system engineering, and in particular to a demand management method, system, equipment and medium based on a unified data source model. Background Art

[0002] Liquid rocket engine is the abbreviation of rocket engine using liquid propellant. In the process of developing new spacecraft models, it is usually necessary to decompose the capabilities and map the indicators of liquid rocket engine systems, establish an indicator system and calculate qualitative and quantitative indicators.

[0003] In order to meet the requirements of further power capability, life and reliability of liquid rocket engines, the demonstration and development of rocket engine models cannot be limited to design indicators, but should be designed according to the space launch requirements under the new situation. Based on the above background, the aerospace science and technology field has gradually introduced MBSE methodology and DOORS requirement management tools, and applied them in the development process of multiple liquid rocket engine models to achieve the purpose of demand analysis and demand management.

[0004] Traditional liquid rocket engine design platforms generally integrate simulation programs and evaluation programs for indicator calculation. Due to the lack of process management and unified data source storage, such platforms cannot realize data traceability, and demand traceability and demand verification also lose their digital foundation. Summary of the invention

[0005] The purpose of the present invention is to address the deficiencies of the above-mentioned prior art and provide a demand management method, system, device and medium based on a unified data source model, so as to solve the problem that the prior art lacks process management and unified data source storage, so such platforms cannot realize data traceability functions, and demand tracing and demand verification also lose their digital foundation.

[0006] The present invention specifically provides the following technical solution: a demand management method based on a unified data source model, comprising the following steps:

[0007] Model-based systems engineering MBSE methodology and system modeling language SysML specification design a demand information carrier based on a unified data source model, and build a demand management model through the demand information carrier; wherein the demand information carrier is the design indicator data of a liquid rocket engine;

[0008] Designing a data structure for the demand management model and organizing demand data through the data structure;

[0009] Add attributes to all required data fields , recursively add attributes Backtrack the demand data and use a stack Save the current backtracking path; the properties Indicates whether the requirement has been searched;

[0010] The requirement change attributes in the current backtracking path are stored as a whole in a set in the requirement data domain. When applying for a requirement change, a requirement change form is filled out, and requirement baseline control and requirement version tracing are performed.

[0011] Preferably, constructing a demand management model through the demand information carrier includes the following steps:

[0012] The requirement management model RMM is defined as:

[0013] .

[0014] in, The demand set composed of requirements, Constitutes model element sets for other SysML elements, E is the edge set consisting of demand relations, is the correlation function consisting of the mapping between demand and demand relationship, Demand weight consisting of demand priority or demand decomposition ratio;

[0015] Assume that the demand management model exists m requirements, the requirement vertex set V = { v 1, v 2,⋯, v m}, v 1. v 2. And v m They are the first demand vertex, the second demand vertex and the m demand vertices, then the adjacency matrix of the demand management model is m×m The matrix a ij , recorded as A =[ a ij ] m×m ,in, a ij The value expression of is:

[0016] .

[0017] in, For existence i Demand Vertex As the starting point, j Demand Vertex The edge of the end point;

[0018] Adjacency matrix corresponding to the demand management model A for:

[0019] .

[0020] When the requirements management model association relationship meets the requirements management model element e > m log( m ), that is, when there are a large number of correlations between the requirements, it is converted into an adjacency matrix.

[0021] Preferably, designing a data structure for the demand management model and organizing demand data through the data structure comprises the following steps:

[0022] Set up IRequirementManage interface, ITrace interface and ISysmlElement interface for the requirement management model, and use the ISysmlElement interface to operate various elements in SysML;

[0023] Organizing the demand data through all the interfaces and exchanging data with the system modeling language SysML; specifically comprising the following steps:

[0024] Reorganize the itemized requirement information according to the attribute form of the requirement management model, and re-render the front-end requirement management diagram to complete the data conversion;

[0025] When the demand management model reads XMI, the extensible markup language XML deserializer Deserializer is used to import data, and then the specified XMI data is mapped to the object entity, and the demand management model structure is rebuilt according to the object entity to complete the data exchange; the XMI is an XML-based metadata exchange;

[0026] JSON is used for data exchange between the front-end and back-end of the demand management model, and JSON serializer / deserializer is used to exchange JSON data and demand management model data.

[0027] Preferably, the adding of attributes to all required data fields , including the following steps:

[0028] Use queue Q to manage the requirements to be searched. The queue is a first-in-first-out data set. When a requirement enters the queue, it is added to the end of the queue. When it leaves the queue, the requirement at the head of the queue is deleted.

[0029] For the non-connected demand management model, all strongly connected components are identified through the BFS algorithm, and each strongly connected component is traversed.

[0030] Preferably, the recursive addition of attributes The subsequent demand data is backtracked and a stack is used to save the current backtracking path, including the following steps:

[0031] Perform matching search on the required vertices;

[0032] When traversing the BFS algorithm, specify the required demand relationships and store the qualified demand relationships into a collection;

[0033] Analyze the relationship between several requirements and obtain all the requirement vertices and requirement relationships between the requirements.

[0034] Preferably, the step of filling out a requirement change form when applying for a requirement change, and performing requirement baseline control and requirement version tracing includes the following steps:

[0035] Maintain a set of version numbers for each requirement through the requirements management model, and perform updates whenever the requirements change;

[0036] A baseline identifier set baselines is maintained for each requirement through the requirement management model. The baseline identifier records the corresponding relationship corVersion between the requirement version and the requirement baseline name.

[0037] The requirements management model stores the corVersion attribute for each requirement. After that, traverse The requirements contained in the requirements, through the requirement history set history, switch the current requirement version to the version number Version corresponding to the baseline identifier Baseline to complete the baseline switch;

[0038] When the requirements change, fill in the change control form, save the attributes to the requirement change set ReqChange, copy the current requirements to the requirement history set changes, execute the requirement change, and modify the current requirements;

[0039] View and specify the requirement version in the requirement history collection history of the requirement, save the current requirement to the requirement history collection history and then switch the current requirement.

[0040] Preferably, the requirement baseline control and requirement version tracing further include the following steps:

[0041] Specify filtering rules to limit the traceability scope, use the requirement search algorithm to traverse the selected requirements, and search for the requirement set;

[0042] Traverse the demand association relationship of the adjacency list and reverse adjacency list of the demand, match the corresponding elements, and filter according to the direction and type of the association relationship;

[0043] If the specified element exists in the adjacency list or the reverse adjacency list, there is an association relationship, and filtering is performed according to whether the rows and columns selected by the user are associated;

[0044] Store the filtering results into a two-dimensional array to generate a demand traceability matrix.

[0045] The present invention provides a demand management system based on a unified data source model, comprising:

[0046] A model building module is used to design a model requirement information carrier based on a unified data source model based on the model-based systems engineering MBSE methodology and the system modeling language SysML specification, and to build a requirement management model through the requirement information carrier; wherein the requirement information carrier is the design indicator data of a liquid rocket engine;

[0047] A data exchange module, used to design a data structure for the demand management model and organize demand data through the data structure;

[0048] Search module, used to add attributes to all required data fields , recursively add attributes The subsequent demand data is backtracked, and a stack is used to save the current backtracking path; the attribute Indicates whether the requirement has been searched;

[0049] The backtracking module is used to store the demand change attributes in the current backtracking path as a whole in a set in the demand data domain, fill in the demand change form when applying for demand change, and perform demand baseline control and demand version tracing.

[0050] The present invention provides a computer device, including a memory and a processor, wherein a program is stored in the memory, and when the program is executed by the processor, the processor executes the steps of the above-mentioned demand management method based on a unified data source model.

[0051] The present invention provides a storage medium having a computer program stored thereon, characterized in that when the computer program is executed by a processor, the steps of the above-mentioned demand management method based on a unified data source model are implemented.

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

[0053] The invention designs the demand information carrier based on the unified data source model based on the model-based system engineering MBSE methodology and the system modeling language SysML specification, and constructs the demand management model and its data structure and data exchange scheme through the demand information carrier, and adds attributes to all demand data domains. , recursively add attributes The subsequent demand data is backtracked, and a stack is used to save the current backtracking path, which is stored in a collection in the demand data domain. When applying for a demand change, a demand change form is filled out, and demand baseline control and demand version traceability are performed. The demand management model traversal and demand traceability designed by the present invention support complex demand management, and according to the SysML demand traceability and demand verification mechanism, the demand traceability method is redesigned, which solves the problem of the traceability matrix lacking a complete demand traceability chain. It can realize demand change control and change traceability, demand baseline control and version traceability based on the demand management model, and trace the indicator calculation of the liquid rocket engine and verify the demand, thereby improving the power capacity, life and reliability of the liquid rocket engine. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] Figure 1 A method for constructing a demand management model according to the present invention:

[0055] Figure 2 It is a partial component of a certain demand management model according to the present invention;

[0056] Figure 3 These are two methods of expressing the demand management model according to the present invention; wherein, Figure 3 (a) is the first method, Figure 3 (b) is the second method;

[0057] Figure 4 is a class inheritance structure of a demand management model according to the present invention;

[0058] Figure 5 The relationship between different input and output forms of the demand information according to the present invention;

[0059] Figure 6 To change the process according to the requirements of the present invention;

[0060] Figure 7 There are four forms of demand tracing according to the present invention;

[0061] Figure 8 is a white box activity diagram of a turbo pump according to the present invention;

[0062] Fig. 9 A partial requirements management model for the construction according to the present invention;

[0063] Fig.10 For the forward tracking of weight requirements according to the present invention;

[0064] Fig.11 For the backward tracing of the weight requirement according to the present invention;

[0065] Fig.12 The tracing result of the specified requirement pair according to the present invention;

[0066] Fig.13 This is an overall flow chart of a demand management method based on a unified data source model of the present invention. DETAILED DESCRIPTION

[0067] The following is a clear and complete description of the technical solutions of the embodiments of the present invention in conjunction with the drawings in the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0068] Based on models and graph theory, the requirements management model and its data structure and data exchange scheme are designed. The designed requirements management model traversal and search algorithms can support the high-performance operation of the requirements management process. The key requirements capture algorithm and the requirements management model measurement indicators can effectively perform requirements analysis. According to the SysML requirements traceability mechanism, the requirements traceability method is redesigned to solve the problem of the lack of a complete requirements traceability chain in the traceability matrix, and it can realize requirements change control and change traceability, requirements baseline control and version traceability based on the requirements management model. Model-based transmission system modeling and requirements management are realized, providing a reference for the requirements management of complex systems. Requirements management methods, systems, equipment and media based on a unified data source model are proposed. The overall Figure 1 to Figure 13 As shown, the problem of the prior art is solved.

[0069] like Figure 1 and Fig.13 As shown, an embodiment of the present invention provides a demand management method based on a unified data source model, comprising the following steps:

[0070] Step S1: Based on the MBSE methodology of model-based systems engineering and the SysML specification of system modeling language, the requirement information carrier is designed, and the requirement management model is constructed through the requirement information carrier. The metamodel extension mechanism is also studied. The requirement information carrier is the liquid rocket engine design index data.

[0071] Based on the model, demand types and demand relationships are established, and demand scenarios and processes are modeled based on the model to obtain a demand management model combined with graph theory.

[0072] The specific steps of this step are:

[0073] The requirement management model RMM is defined as:

[0074] .

[0075] in, The demand set composed of requirements, Constitutes model element sets for other SysML elements, E is the edge set consisting of demand relations, is the correlation function consisting of the mapping between demand and demand relationship, The demand weight is composed of demand priority or demand decomposition ratio.

[0076] Assume that the demand management model exists m requirements, the requirement vertex set V = { v 1, v 2,⋯, v m}, v 1. v 2. And v m They are the first demand vertex, the second demand vertex and the m demand vertices, then the adjacency matrix of the demand management model is m×m The matrix a ij , recorded as A =[ a ij ] m×m ,in, a ij The value expression of is:

[0077] .

[0078] in, For existence i Demand Vertex As the starting point, j Demand Vertex The end edge.

[0079] Adjacency matrix corresponding to the demand management model A for:

[0080] .

[0081] When the requirements management model association relationship meets the requirements management model element e > m log( m ), that is, when there are a large number of correlations between the requirements, it is converted into an adjacency matrix.

[0082] like Figure 2 As shown, in one embodiment, five vertices are determined , , , and ,in, and , The correlations between them are and , and The relationships between , and , and The relationship between , and The interconnections between and , and The interconnection relationship between .like Figure 3 (a) and Figure 3 As shown in (b), two methods are used to represent the demand management model, and the linked list results obtained are also different.

[0083] The requirement management model traversal and search algorithm is as follows, and the requirement change, version control and baseline control based on the requirement management model are obtained, and the requirement tracing method based on the requirement management model is obtained.

[0084] Step S2: Design a data structure for the requirement management model, organize the requirement data through the data structure, and exchange data with the system modeling language SysML.

[0085] The specific steps of this step are:

[0086] Set the requirement management IRequirementManage interface, event tracking ITrace interface and unified modeling language modeling ISysmlElement interface for the requirement management model, and operate various elements in SysML through the ISysmlElement interface.

[0087] Organize the demand data through all interfaces and exchange data with the system modeling language SysML; the specific steps include:

[0088] Reorganize the item-based requirement information according to the attribute form of the requirement management model, and re-render the front-end requirement management diagram to complete the data conversion.

[0089] When the demand management model reads XMI, it uses the extensible markup language XML deserializer to import data, then maps the specified XMI data to the object entity, and rebuilds the demand management model structure based on the object entity to complete the data exchange. XMI is an XML-based metadata exchange.

[0090] An open standard file format and data exchange format JSON (JavaScript Object Notation) is used between the front-end and back-end of the demand management model for data exchange. The storage format of JSON files is similar to the aforementioned adjacency list. The JSON serializer / deserializer is used to exchange the above JSON data and the demand management model data. The relationship between different input and output forms of demand information is as follows: Figure 5 As shown, the front end of the requirement management model converts XML into SysML diagrams and displays them on the front end. The front end display includes requirement management diagrams and requirement attributes. Other output files are output through the front end display. Other output files include PNG, JPG, BMP, GIF, SVG, PDF and requirement analysis reports. Other output files can also be output through the back end. The itemized requirements displayed on the front end include CSV and Excel.

[0091] The class inheritance structure of the demand management model is as follows Figure 4 As shown, the SysML elements include requirements, common elements and requirement relationships, wherein requirements include functional requirements, non-functional requirements and constraints, and requirement relationships include traceability, satisfaction and verification. At the same time, system simulation verification and process simulation verification are performed through requirements, and the judgment confirmation Iverify interface is used. The SysML elements use the ISysmlElement interface for data exchange; the requirement management model uses the ITrace interface for requirement tracing, and uses the IRequirementManage interface for data exchange between directed multi-graph operation classes and graph operation basic classes.

[0092] Step S3: Add attributes for all required data fields , recursively add attributes Backtrack the demand data and use a stack Save the current backtracking path; properties Indicates whether the requirement has been searched.

[0093] In this step, add an attribute for all required data fields. , indicating whether the requirement has been searched, including the following steps:

[0094] A queue Q is used to manage the requirements for preparing searches. A queue is a first-in-first-out data set. When a requirement enters the queue, it is added to the end of the queue. When a requirement exits the queue, the requirement at the head of the queue is deleted.

[0095] For the non-connected demand management model, all strongly connected components are identified through the breadth-first traversal BFS (Breath First Search) algorithm, and then each strongly connected component is traversed.

[0096] In this step, a search algorithm is used to use a stack to save the current backtracking path, and recursion is used to backtrack, including the following steps:

[0097] Simply perform a matching search on the required vertices; directly use the adjacency list to look up the table.

[0098] When traversing the BFS algorithm, specify the required demand relationships and store the demand relationships that meet the conditions into a collection.

[0099] To analyze the relationship between several requirements, it is necessary to obtain all the requirement vertices and requirement relationships between the requirements.

[0100] The present invention proposes four forms of demand tracing, as follows: Figure 7 As shown, it includes the traceability forms of requirements between stakeholder requirements and system requirements, and the traceability forms of requirements between system requirements and SysML elements. The traceability forms of requirements between stakeholder requirements and system requirements include: 1. Tracing forward to requirements, 4. Tracing backward from requirements; the traceability forms of requirements between system requirements and SysML elements include: 2. Tracing forward from requirements, 3. Tracing backward to requirements.

[0101] Step S4: Store the requirement change attributes in the current backtracking path as a whole in a set in the requirement data domain, fill out the requirement change form when applying for a requirement change, and perform requirement baseline control and requirement version tracing.

[0102] Specifically:

[0103] The requirement management model maintains a set of version numbers for each requirement, and updates are performed whenever the requirement changes.

[0104] By default, the requirement management model maintains a baseline identifier set baselines for each requirement. The baseline identifier records the corresponding relationship corVersion between the requirement version and the requirement baseline name.

[0105] The corVersion attribute is stored for each requirement through the requirement management model. After that, traverse The requirements contained in requirements switch the current requirement version to the version number Version corresponding to the baseline identifier Baseline through the requirement history record set history to complete the baseline switch.

[0106] When the requirements change, first fill out the change control form, save the attributes to the requirement change set ReqChange, then copy the current requirements to the requirement history set changes, and finally execute the requirement change to modify the current requirements.

[0107] View and specify the requirement version in the requirement history collection history of the requirement, save the current requirement to the requirement history collection history and then switch the current requirement.

[0108] Requirements change process Figure 6 As shown, specifically: by making a change application, performing an impact analysis, obtaining the change assessment result, storing the change result after the change is rejected, obtaining the change execution result after specifying the change executor, re-evaluating the change execution result, canceling the change, re-verifying, or ending the change without verification, storing the change result after the change is ended, obtaining the requirement verification result after re-verifying, confirming or canceling the change based on the requirement verification result, ending the change after the change is confirmed, and storing the change result after the change is canceled.

[0109] The requirements baseline control and requirements version traceability also include the following steps:

[0110] Specify filtering rules to limit the traceability scope, use the requirement search algorithm to traverse the selected requirements, search for the requirement set, traverse the requirement association relationship on the adjacency list and reverse adjacency list of the requirements, match the corresponding elements, and filter according to the direction and type of the association relationship.

[0111] In this step, if the specified element exists in the adjacency list or the reverse adjacency list, there is an association relationship, and filtering is performed according to whether the rows and columns selected by the user are associated.

[0112] Store the filtering results into a two-dimensional array A=( a ij ), generate the demand traceability matrix, where a ij Indicates i elements and j The association relationship between the elements, the two-dimensional array is the two-dimensional array form of the adjacency matrix.

[0113] A practical implementation is as follows:

[0114] Step (1): Under the guidance of the MBSE Harmony-SE methodology (MBSE stands for Model based System Engineering), SysML is used to complete the modeling of the model-based liquid rocket engine turbine pump transmission system in the requirements analysis, functional analysis and design synthesis stages. Generate turbine pump system requirements items based on system requirements and stakeholders, and then combine the spacecraft attitude correction and control scenarios. Table 1 shows some requirements items for the liquid rocket engine turbine pump. After generating the requirements diagram for the liquid rocket engine turbine pump, the system requirements are allocated to use cases and scenarios, and the black box and white box models of the turbine pump are constructed. From how the turbine pump responds to external stimuli and its role in the entire liquid rocket engine system to allocating its functions to various subsystems, the internal structure and working mechanism of the turbine pump are revealed in detail, including the interaction and collaboration between components such as the turbine, impeller, shaft, pipeline and pump body. According to the system context analysis of the function usage logic, a system white box activity diagram can be generated as follows: Figure 8 As shown in the figure, we design from demand analysis to underlying parameters, build demand management models based on the parameters generated in the demand and process, and realize demand traceability and demand verification.

[0115] Step (2): The established SysML model can generate an XMI file, which contains all the information of the SysML model. The XMI file is imported into the requirements management software, and the requirements management model can be automatically constructed by parsing the elements and their relationships. Fig. 9 The following figure shows part of the requirements management model built in the requirements management software. Due to the large number of model elements, the software hides some elements and their relationships. Each element in the figure shows the SysML name and stereotype name, which correspond to the SysML modeling elements.

[0116] Step (3): The requirements management software provides a series of requirements change functions in the upper toolbar. After clicking the change application, you need to check the requirements that need to be changed in the requirements list and fill in the source of the requirement change, the reason for the change, the priority, the change content and the change summary. The applicant, the application submission date and the change date are automatically filled in by the software. After that, a person with relevant authority needs to conduct a change impact analysis. After completing the change assessment, the change executor needs to be designated. After that, click Change Execution to jump to the requirements model construction interface. The requirements checked in the change application are open for modification. After completing the change execution, you can choose to execute the requirements verification process, or you can directly notify stakeholders to confirm the change and finally end the change. In the above process, changes can be rejected or canceled.

[0117] Table 1 Partial requirements for liquid rocket engine turbo pumps

[0118]

[0119] Requirement baselines and requirement version control are closely related to requirement changes. In the requirement management software, users can use the requirement version control function independently, and users can directly change requirement attributes. When a user creates a requirement baseline, the requirement management software will maintain a requirement baseline for the current requirement version as a whole, and any subsequent requirement modifications must go through a strict change control process. The version control function of the requirement management software requires that after switching the baseline, you need to select the requirement from the requirement list under the corresponding baseline, and then select the requirement version corresponding to the requirement to view the requirement version information, version change information, original requirement information, and control requirement information.

[0120] Step (4): Based on the demand management model, demand tracing related functions can also be implemented. Taking weight demand as an example, first search for weight demand, then perform forward tracing on weight demand, the result is as follows: Fig.10 As shown. Backtracking is performed on the weight requirement, and the result is as follows Fig.11 shown.

[0121] In addition, it may be necessary to analyze the traceability relationship based on other conditions, and filtering can be performed based on the traceability relationship found, such as Fig.12 As shown. For example, the weight requirement is used as the source requirement and the turbine pump housing output port is used as the target element to analyze the traceability path. Since the branch from the turbine pump system module to the turbine pump total weight constraint module is not connected to the pump housing output port, it will be filtered out, and only the paths connected according to the selected requirements and elements will be retained in the results.

[0122] Based on the above method, the present invention provides a demand management system based on a unified data source model, including: a model building module, a data exchange module, a search module and a backtracking module.

[0123] Among them, the model construction module is used to design the demand information carrier of the unified data source model based on the model-based systems engineering MBSE methodology and the system modeling language SysML specification, and to build the demand management model through the demand information carrier; the demand information carrier is the design indicator data of the liquid rocket engine; the data exchange module is used to design the data structure for the demand management model, and to organize the demand data through the data structure; the search module is used to add the attribute Visited to all demand data domains, and to use recursion to backtrack the demand data after adding the attribute Visited, and use a stack to save the current backtracking path; the attribute Visited indicates whether the demand has been searched; the backtracking module is used to store the demand change attributes in the current backtracking path as a whole in a set in the demand data domain, fill in the demand change form when applying for demand changes, and perform demand baseline control and demand version traceability.

[0124] The present invention also provides a computer device, including a memory and a processor, wherein a program is stored in the memory, and when the program is executed by the processor, the processor executes the steps of a demand management method based on a unified data source model.

[0125] According to the disclosed embodiments, a computing device may communicate with one or more external devices (e.g., keyboards, pointing devices, Bluetooth communications, etc.), or with any device (e.g., routers, modems, etc.) that enables a computing device to communicate with one or more other computing devices.

[0126] The present invention also provides a storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of a demand management method based on a unified data source model are implemented.

[0127] According to the disclosed embodiments, the storage medium may be a non-volatile computer-readable storage medium, such as but not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present invention, the storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0128] The above content is a further detailed description of the present invention in combination with a specific preferred embodiment. For technicians in the technical field to which the present invention belongs, several simple deductions or substitutions can be made without departing from the concept of the present invention, which should be regarded as belonging to the protection scope of the present invention.

Claims

1. A demand management method based on a unified data source model, characterized in that: The steps include: Model-based systems engineering MBSE methodology and system modeling language SysML specification design a demand information carrier based on a unified data source model, and build a demand management model through the demand information carrier; wherein the demand information carrier is the design indicator data of a liquid rocket engine; Designing a data structure for the demand management model and organizing demand data through the data structure; Add the attribute Visited to all demand data fields, recursively trace back the demand data after adding the attribute Visited, and use a stack to save the current backtracking path; the attribute Visited indicates whether the demand has been searched; The requirement change attributes in the current backtracking path are stored as a whole in a set in the requirement data domain, and a requirement change form is filled in when applying for a requirement change, and requirement baseline control and requirement version tracing are performed; Constructing a demand management model through the demand information carrier includes the following steps: The requirement management model RMM is defined as: Among them, V r is the demand set composed of demand, V e The model element set is composed of other SysML elements, E is the edge set composed of requirement relationships, is the correlation function formed by mapping the demand and the demand relationship, and f is the demand weight formed by the demand priority or the demand decomposition ratio; Assume that there are m requirements in the demand management model, and the demand vertex set V = {v1, v2, …, v m }, v1, v2, and v m are the first demand vertex, the second demand vertex, and the mth demand vertex respectively, then the adjacency matrix A of the demand management model is an m×m matrix a ij , denoted as A=[a ij ] m×m , where a ij The value expression of is: Among them, v i →v j For there to be a demand vertex v i As the starting point, take the jth demand vertex v j The edge of the end point; The adjacency matrix A corresponding to the demand management model is: When the demand management model association relationship satisfies the demand management model element e>mlog(m), that is, when there are a large number of association relationships between the requirements, it is converted into an adjacency matrix.

2. A demand management method based on a unified data source model as claimed in claim 1, characterized in that: Designing a data structure for the demand management model and organizing demand data through the data structure includes the following steps: Set up the requirement management IRequirementManage interface, event tracking ITrace interface and unified modeling language modeling ISysmlElement interface for the requirement management model, and operate various elements in SysML through the ISysmlElement interface; Organizing the demand data through all the interfaces and exchanging data with the system modeling language SysML; specifically comprising the following steps: Reorganize the itemized requirement information according to the attribute form of the requirement management model, and re-render the front-end requirement management diagram to complete the data conversion; When the demand management model reads XMI, the extensible markup language XML deserializer Deserializer is used to import data, and then the specified XMI data is mapped to the object entity, and the demand management model structure is rebuilt according to the object entity to complete the data exchange; the XMI is an XML-based metadata exchange; JSON is used for data exchange between the front-end and back-end of the demand management model, and JSON serializer / deserializer is used to exchange JSON data and demand management model data.

3. A demand management method based on a unified data source model as claimed in claim 1, characterized in that: Adding the attribute Visited to all required data fields includes the following steps: Use queue Q to manage the requirements to be searched. The queue is a first-in-first-out data set. When a requirement enters the queue, it is added to the end of the queue. When it leaves the queue, the requirement at the head of the queue is deleted. For the non-connected demand management model, all strongly connected components are identified through the BFS algorithm, and each strongly connected component is traversed.

4. A demand management method based on a unified data source model as claimed in claim 1, characterized in that: The method of recursively backtracking the demand data after adding the attribute Visited, and using a stack to save the current backtracking path, includes the following steps: Perform matching search on the required vertices; When traversing the BFS algorithm, specify the required demand relationships and store the qualified demand relationships into a collection; Analyze the relationship between several requirements and obtain all the requirement vertices and requirement relationships between the requirements.

5. A demand management method based on a unified data source model as claimed in claim 1, characterized in that: When applying for a requirement change, fill out a requirement change form, and perform requirement baseline control and requirement version tracing, including the following steps: Maintain a set of version numbers for each requirement through the requirements management model, and perform updates whenever the requirements change; A baseline identifier set baselines is maintained for each requirement through the requirement management model. The baseline identifier records the corresponding relationship corVersion between the requirement version and the requirement baseline name. The requirements management model stores the corVersion attribute for each requirement. i After that, traverse the baseline i The requirements contained in the requirements, through the requirement history set history, switch the current requirement version to the version number Version corresponding to the baseline identifier Baseline to complete the baseline switch; When the requirements change, fill in the change control form, save the attributes to the requirement change set ReqChange, copy the current requirements to the requirement history set changes, execute the requirement change, and modify the current requirements; View and specify the requirement version in the requirement history collection history of the requirement, save the current requirement to the requirement history collection history and then switch the current requirement.

6. A demand management method based on a unified data source model as claimed in claim 1, characterized in that: The requirement baseline control and requirement version tracing include the following steps: Specify filtering rules to limit the traceability scope, use the requirement search algorithm to traverse the selected requirements, and search for the requirement set; Traverse the demand association relationship of the adjacency list and reverse adjacency list of the demand, match the corresponding elements, and filter according to the direction and type of the association relationship; If the specified element exists in the adjacency list or the reverse adjacency list, there is an association relationship, and filtering is performed according to whether the rows and columns selected by the user are associated; Store the filtering results into a two-dimensional array to generate a demand traceability matrix.

7. A demand management system based on a unified data source model, characterized in that: include: A model building module is used to design a model requirement information carrier based on a unified data source model based on the model-based systems engineering MBSE methodology and the system modeling language SysML specification, and to build a requirement management model through the requirement information carrier; wherein the requirement information carrier is the design indicator data of a liquid rocket engine; A data exchange module, used to design a data structure for the demand management model and organize demand data through the data structure; The search module is used to add the attribute Visited to all demand data domains, recursively trace the demand data after adding the attribute Visited, and use a stack to save the current traceback path; the attribute Visited indicates whether the demand has been searched; A backtracking module is used to store the demand change attributes in the current backtracking path as a whole in a set in the demand data domain, fill in a demand change form when applying for a demand change, and perform demand baseline control and demand version tracing; Constructing a demand management model through the demand information carrier includes the following steps: The requirement management model RMM is defined as: Among them, V r is the demand set composed of demand, V e The model element set is composed of other SysML elements, E is the edge set composed of requirement relationships, is the correlation function formed by mapping the demand and the demand relationship, and f is the demand weight formed by the demand priority or the demand decomposition ratio; Assume that there are m requirements in the demand management model, and the demand vertex set V = {v1, v2, …, v m }, v1, v2, and v m are the first demand vertex, the second demand vertex, and the mth demand vertex respectively. Then the adjacency matrix A of the demand management model is an m×m matrix a ij , denoted as A=[a ij ] m×m , where a ij The value expression of is: Among them, v i →v j For there to be a demand vertex v i As the starting point, take the jth demand vertex v j The edge of the end point; The adjacency matrix A corresponding to the demand management model is: When the demand management model association relationship satisfies the demand management model element e>mlog(m), that is, when there are a large number of association relationships between the requirements, it is converted into an adjacency matrix.

8. A computer device, characterized in that: It includes a memory and a processor, wherein a program is stored in the memory, and when the program is executed by the processor, the processor executes the steps of a demand management method based on a unified data source model as described in any one of claims 1 to 6.

9. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of a demand management method based on a unified data source model as described in any one of claims 1 to 6 are implemented.

Images