MBSE and product information management system integration method and system

Abstract

The invention relates to the technical field of data processing, and further relates to an MBSE and product information management system integration method and system. The method comprises the steps of obtaining to-be-processed data from project file extraction information according to user requirements; based on the ID of the to-be-processed data, determining whether the to-be-processed data exists in the product information management system; if the to-be-processed data does not exist, executing a first operation through the product information management system, the first operation being used for adding the to-be-processed data in the product information management system; and if yes, executing a second operation through the product information management system, the second operation being used for updating the to-be-processed data in the product information management system. According to the method, through an intelligent comparison mechanism based on the ID, the system can automatically identify whether to-be-processed data exists in the product information management system or not and intelligently trigger the newly-added or updated operation, and fine-grained management of model elements is achieved.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and further to an integration method and system for MBSE and product information management system. Background Technology

[0002] Model-Based Systems Engineering (MBSE), as an advanced systems engineering methodology, has been widely applied in the development of complex products in recent years. MBSE supports activities such as requirements, design, analysis, verification, and validation by establishing system models, spanning the entire system development lifecycle. Currently, the integration of MBSE with Product Information Management Systems (PLM / PDM) typically involves uploading project files (such as SysML model files) generated by MBSE tools to the PLM / PDM system as independent documents, which then manages the entire file centrally. However, this integration method has significant limitations; for example, it can only achieve coarse-grained management of project files and cannot provide fine-grained control over model elements within the files (such as requirements, functions, components, and interfaces). Summary of the Invention

[0003] To address the aforementioned technical issues, this application provides an integration method and system for MBSE and a product information management system, enabling fine-grained management of model elements.

[0004] In a first aspect, this application provides an integration method for MBSE and a product information management system, comprising: obtaining data to be processed from information extracted from engineering documents according to user requirements; determining whether the data to be processed exists in the product information management system based on the ID of the data to be processed; if it does not exist, performing a first operation through the product information management system, the first operation being used to add the data to be processed in the product information management system; if it exists, performing a second operation through the product information management system, the second operation being used to update the data to be processed in the product information management system; the data to be processed includes first element data or non-first element data, wherein the first element data includes at least one of requirement element data, functional element data, logical element data, and physical element data.

[0005] The above method, through an ID-based intelligent comparison mechanism, enables the system to automatically identify whether there is already data to be processed (including first element data and non-first element data) in the product information management system, and intelligently triggers new or update operations, thus realizing fine-grained management of model elements; especially precise control over first element data such as requirement element data, functional element data, logical element data and physical element data.

[0006] In one implementation, when the data to be processed includes the first element data, if it does not exist, the first operation is performed through the product information management system, specifically including: obtaining all root node data and creating the data to be processed in the product information management system; creating a relationship between all root node data and system model data based on all root node data and preset system model data; and creating a relationship between parent node data and the data to be processed based on the ID of the data to be processed and the ID of the parent node data of the data to be processed.

[0007] The above method establishes a complete model architecture foundation by acquiring all root node data and creating pending data in the product information management system; it creates associations between root nodes and system model data based on preset system model data to ensure the integrity of the model hierarchy; and in particular, it establishes precise parent-child relationships by using the ID of pending data and the ID of parent node data, enabling fine-grained management of model elements such as requirement element data, functional element data, logical element data, and physical element data.

[0008] In one implementation, when the data to be processed includes the first element data, if it does not exist, a first operation is performed through the product information management system. This operation specifically includes: determining whether the data to be processed is root node data based on the parent node data ID; if the data to be processed is root node data, creating an association between the data to be processed and preset system model data; if the data to be processed is not root node data, determining whether parent node data exists in the product information management system; if parent node data exists, creating an association between the parent node data and the data to be processed; if parent node data does not exist, using the parent node data as a new parent node data and creating an association between the new parent node data and the data to be processed.

[0009] The above method achieves automatic identification of model element hierarchy by intelligently determining whether the data to be processed is root node data based on the parent node data ID. For root node data, the association relationship between it and the system model data is directly established to ensure the integrity of the top-level architecture. For non-root node data, the existence of parent node data is dynamically checked and the corresponding association relationship is intelligently created (including treating parent node data as newly added parent node data when necessary), which improves the efficiency and accuracy of building association relationships between model elements, while realizing version control of individual model elements.

[0010] In one implementation, when the second operation is a modification operation and the data to be processed includes the first element data, if it exists, the second operation is performed through the product information management system, specifically including: detecting the data to be processed from the product information management system and modifying the attributes of the detected data to be processed; and / or, when the parent node data of the detected data to be processed has changed, creating an association between the detected data to be processed and the changed parent node data, and deleting the association between the detected data to be processed and the parent node data before the change; when the detected data to be processed changes from root node data to child node data, deleting the association between the data to be processed before the change and the preset system model data, and creating an association between the changed data to be processed and its parent node data; when the detected data to be processed changes from child node data to root node data, deleting the association between the data to be processed before the change and its parent node data, and creating an association between the changed data to be processed and the system model data.

[0011] The above methods ensure the controllability and traceability of data changes by retrieving the data to be processed from the product information management system and modifying its attributes. When the parent node data changes, the system automatically updates the association relationship (including creating new associations and deleting old associations) to maintain the accuracy of the model topology. In particular, for the state transition between the root node and child nodes (such as the root node becoming a child node or a child node becoming a root node), the system intelligently handles the changes in the association relationship with the system model data or parent node data, further improving the ability to perform fine-grained control over the model elements within the file and avoiding problems such as fragmentation of the integration solution.

[0012] In one implementation, when the second operation is a deletion operation and the data to be processed includes the first element data, if it exists, the second operation is performed through the product information management system, specifically including: querying the data to be deleted in the product information management system and determining the parent node data of the data to be deleted; when the data to be deleted has parent node data, deleting the association between the data to be deleted and its parent node data; when the data to be deleted does not have parent node data, deleting the association between the data to be deleted and the preset system model data.

[0013] In one implementation, when the data to be processed includes non-first element data, if it does not exist, a first operation is performed through the product information management system. Specifically, this includes: when the non-first element data is parameter element data, storing the ID of the data to be processed in the product information management system, creating an association between the data to be processed and preset system model data, and creating associations between the data to be processed and requirement element data, functional element data, logical element data, and physical element data respectively; when the non-first element data is interface element data, creating an association between the data to be processed and system model data, creating source-end associations between the data to be processed and functional element data, logical element data, and physical element data respectively, and creating target-end associations between the data to be processed and functional element data, logical element data, and physical element data respectively; when the non-first element data is view element data, storing the ID of the data to be processed in the product information management system, creating an attachment relationship between the data to be processed and an image, creating an association between the data to be processed and system model data, and creating associations between the data to be processed and requirement element data, functional element data, logical element data, and physical element data respectively.

[0014] In one implementation, if such an operation exists, a second operation is performed through the product information management system, specifically including: when the second operation is a modification operation, retrieving the data to be processed from the product information management system and modifying the attributes of the retrieved data to be processed; and / or, when the second operation is a deletion operation, deleting and / or creating the relevant associations of the retrieved data to be processed.

[0015] In one implementation, when the data to be processed includes non-first element data, if it does not exist, the first operation is performed through the product information management system, specifically including: when the non-first element data is traceable element data, determining the associated requirement element data, functional element data, logical element data, and physical element data based on the data source end information and target end information extracted from the project file; and creating traceable association relationships for the associated requirement element data, functional element data, logical element data, and physical element data respectively.

[0016] In one implementation, when the data to be processed includes non-first element data, if it does not exist, a first operation is performed through the product information management system, specifically including: when the non-first element data is file data, creating system model data based on the tool name, tool version, project name, and ID of the data to be processed, and associating the system model data with the data to be processed; if it exists, a second operation is performed through the product information management system, specifically including: when the non-first element data is file data, updating the association between the system model data and the data to be processed.

[0017] Secondly, this application provides an integrated system of MBSE and a product information management system, comprising: an acquisition module for acquiring data to be processed from information extracted from engineering documents according to user requirements; a judgment module for determining whether the data to be processed exists in the product information management system based on the ID of the data to be processed; an execution module for performing a first operation through the product information management system if the data does not exist; the execution module is further configured to perform a second operation through the product information management system if the data exists; the data to be processed includes first element data or non-first element data, wherein the first element data includes at least one of requirement element data, functional element data, logical element data, and physical element data.

[0018] Compared with the prior art, the present invention has at least one of the following beneficial effects:

[0019] 1. Through an ID-based intelligent comparison mechanism, the system can automatically identify whether there is already data to be processed in the product information management system (including first element data and non-first element data), and intelligently trigger new or update operations, realizing fine-grained management of model elements; especially the precise control of first element data such as requirement element data, functional element data, logical element data and physical element data.

[0020] 2. By acquiring all root node data and creating pending data in the product information management system, a complete model architecture foundation is established; based on the preset system model data, the relationship between root nodes and system model data is created to ensure the integrity of the model hierarchy; in particular, by establishing precise parent-child relationships through the ID of pending data and the ID of parent node data, fine-grained management of model elements such as requirement element data, functional element data, logical element data, and physical element data is realized.

[0021] 3. By intelligently determining whether a data is a root node based on the parent node data ID of the data to be processed, automatic identification of model element hierarchy is achieved. For root node data, the association relationship between it and the system model data is directly established to ensure the integrity of the top-level architecture. For non-root node data, the existence of parent node data is dynamically checked and the corresponding association relationship is intelligently created (including treating parent node data as newly added parent node data when necessary), which improves the efficiency and accuracy of building association relationships between model elements, and at the same time realizes version control of individual model elements.

[0022] 4. By retrieving data to be processed from the product information management system and modifying its attributes, the system ensures the controllability and traceability of data changes; when the parent node data changes, the system automatically updates the association relationship (including creating new associations and deleting old associations) to maintain the accuracy of the model topology; in particular, for the state transition between the root node and child nodes (such as the root node becoming a child node or a child node becoming a root node), the system intelligently handles the changes in the association relationship with the system model data or parent node data, further improving the ability to perform fine-grained control over the model elements within the file and avoiding problems such as fragmentation of the integration solution. Attached Figure Description

[0023] The preferred embodiments will now be described in a clear and easy-to-understand manner, in conjunction with the accompanying drawings, to further explain the above-mentioned characteristics, technical features, advantages, and implementation methods of the present invention.

[0024] Figure 1 This illustration shows a UML design diagram of an RflpStanard object provided in an embodiment of this application;

[0025] Figure 2 This paper illustrates an RFLP data model architecture diagram in a product information management system provided in an embodiment of this application.

[0026] Figure 3 This document illustrates a flowchart of the submission and updating of engineering files according to an embodiment of this application.

[0027] Figure 4 A flowchart illustrating an integration method for an MBSE and a product information management system provided in an embodiment of this application is shown.

[0028] Figure 5 A flowchart illustrating the execution of a first operation according to an embodiment of this application is shown;

[0029] Figure 6 This document illustrates a flowchart illustrating the execution of a first operation by functional element data according to an embodiment of this application.

[0030] Figure 7 This application provides an embodiment of another flowchart for performing the first operation;

[0031] Figure 8 This invention illustrates a flowchart of another functional element data performing a first operation, as provided in an embodiment of this application.

[0032] Figure 9 A flowchart illustrating the execution of a second operation, as provided in an embodiment of this application, is shown.

[0033] Figure 10 A flowchart illustrating another method for performing the second operation, as provided in an embodiment of this application, is shown.

[0034] Figure 11 This invention provides a flowchart illustrating the execution of a second operation by functional element data according to an embodiment of the present application.

[0035] Figure 12 This document illustrates a flowchart of performing a first operation on non-first element data, as provided in an embodiment of this application.

[0036] Figure 13 This document illustrates a flowchart illustrating the execution of a second operation using parameter element data, as provided in an embodiment of this application.

[0037] Figure 14 This document illustrates a flowchart illustrating the execution of a second operation on interface element data according to an embodiment of this application.

[0038] Figure 15 A flowchart illustrating the second operation performed on view element data according to an embodiment of this application is shown. Detailed Implementation

[0039] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the specific implementation methods of the present invention will be described below with reference to the accompanying drawings. Obviously, the drawings described below are merely some embodiments of the present invention. For those skilled in the art, other drawings and other implementation methods can be obtained based on these drawings without any creative effort.

[0040] To keep the drawings concise, each figure only schematically shows the parts relevant to the invention, and these do not represent the actual structure of the product. Furthermore, to facilitate understanding, in some figures, only one of components with the same structure or function is schematically depicted, or only one is labeled. In this document, "one" not only means "only one," but can also mean "more than one."

[0041] It should also be further understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0042] In this document, it should be noted that, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to fixed connections, detachable connections, or integral connections; they can refer to mechanical connections or electrical connections; they can refer to direct connections or indirect connections through an intermediate medium; and they can refer to the internal communication between two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0043] Furthermore, in the description of this application, the terms "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0044] It should be noted that the above embodiments can be freely combined as needed. The above are merely preferred embodiments of the present invention. It should be pointed out that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

[0045] Model-Based Systems Engineering (MBSE), as an advanced systems engineering methodology, has been widely applied in the field of complex product development in recent years. MBSE supports activities such as requirements, design, analysis, verification, and validation by establishing system models, spanning the entire system development lifecycle.

[0046] Currently, existing integration solutions between MBSE and product information management systems mainly fall into three categories: For example, file-level integration solutions import engineering files generated by MBSE tools (such as Rhapsody and Enterprise Architect) into a Product Data Management (PDM) / Product Lifecycle Management (PLM) system, utilizing the system's native document management functions for version control and access control. This solution is convenient to implement and highly compatible, but suffers from insufficient granularity of model information. Another example is API interface integration solutions: by calling the open interfaces of MBSE tools (such as Rhapsody API and Capella SDK), model elements are exported in a structured manner to intermediate formats such as XML / JSON, and then interact with enterprise-level platforms (such as IBM Jazz and Teamcenter) for data exchange. Yet another example is model transformation integration solutions: using transformation languages ​​such as ATL / QVT to establish cross-system semantic mapping, and using a rule engine to achieve accurate RFLP (Requirement-Function-Logic-Physical) views between MBSE models and business systems. However, these integration solutions all suffer from problems such as the inability to perform fine-grained control over model elements within files and fragmented integration solutions.

[0047] This application provides an integrated design for MBSE and a product information management system to address the problems existing in the prior art.

[0048] The following explanation is based on the accompanying diagram:

[0049] Reference Appendix Figure 1It shows a UML design diagram of an RflpStanard object provided in an embodiment of this application. Figure 1 This document primarily demonstrates a method for converting core elements in MBSE project files into standardized RFLP data types. For example, there are various types of MBSE tools, and the format and structure of core elements in project files generated by each type may differ. The same core element may be represented differently in project files generated by different MBSE tools. Therefore, it is necessary to convert the original non-standardized core elements in the MBSE project file into standardized RFLP data types. Figure 1 Standardized RFLP data or extended data. RFLP data includes requirement element data (see appendix for details). Figure 1 (Requirement element information), Function element data (see appendix) Figure 1 (Functional element information), logical element data (see appendix) Figure 1 Logical element information and physical element data (see appendix) Figure 1 (Physical element information in the text). Also, attached... Figure 1 The extended data may include extended parameter element data (see appendix). Figure 1 Parameter element information), interface element data (refer to the appendix) Figure 1 (Interface element information), view element data (refer to the appendix) Figure 1 (View information in the image) and trace element data (see appendix) Figure 1 (Including traceability information, etc.) Appendix Figure 1 The general element information in BaseDatalnfo refers to... Figure 1 This illustrates the common attribute information possessed by standardized RFLP data and extended data. This application embodiment converts the original non-standardized core elements in the MBSE project file into... Figure 1 Standardized RFLP data or extended data, specifically embodied in the appendix. Figure 1 The data shown in the RflpStanard project file extraction information is from the appendix. In other words, the actual data source for this embodiment is the appendix. Figure 1 Extract information from the RflpStanard project file.

[0050] Appendix Figure 1 The extracted information for the RfptStandard project file includes +toolName:String "tool name", +toolVersion:String "tool version", and +projectId:String "unique identifier of the project file".

[0051] +projectName:String "Project Name", +systemModelId:String "System Model Version ID", +functions:List <functioninfo>"Functional element information", +logics:List <logicinfo>"Logical element information", +physicals:List <physicalinfo>"Physical element information", +params:List <paraminfo>"Parameter element information", +interfaces:List <interfaceport>"Interface element information", +traces:List <traceinfo>"Tracing relationship information", +diagrams:List <diagraminfo>"View Information"

[0052] +updateType:String "Update type", +visualNavigator:VisualNavigatorDto "Project file visualization information".

[0053] Appendix Figure 1 The RequirementInfo element information includes +linkedParamsIds:List <string>"The parameter element ID associated with the requirement project" and "+reqSpecId:String" "The requirement specification element ID to which the requirement project belongs". FunctionInfo function element information includes "+linkedParamsIds:List". <string>"The ID of the parameter element associated with the function." LogicInfo logical element information includes +linkedParamsIds:List <string>"Logically related parameter element IDs". PhysicalInfo physical element information includes +linkedParamsIds:List <string>"Physically associated parameter element ID". The ParamInfo parameter element information includes +unit:String "parameter unit", +max:String "parameter maximum value", +min:String "parameter minimum value", +type:String "parameter type", and +defaultValue:String "parameter default value". The InterfacePort interface element information includes +type:String "interface type", +sourceDateId:String "interface source element ID", +sourceDateType:String "interface source element type", +targetDateId:String "interface target element ID", and +targetDateType:List <string>"Target element type", +sourcePortName:String "Source port name",

[0054] +targetPortName:String "Target Port Name", +linkedParamsIds:List <string>"The parameter ID associated with the interface". BaseDataInfo general element information includes +id:String "element ID", +parentId:String "parent element ID", +name:String "element name", +content:String "element description information", and +ownedDiagramIds:List <string>"The view ID where the element is located".

[0055] Appendix Figure 1 The TraceInfo section contains trace relationship information including +type:String "trace type", +sourceId:String "trace source element ID", +sourceDataType:String "trace source element type", +targetId:String "trace target element ID", and +targetDataType:String "trace target element type". The DiagramInfo view information includes +id:String "view ID", +name:String "view name", +typeName:String "view type", +typeShortName:String "view type abbreviation", and +contentElementIds:List. <string>"The ID of the element contained in the view", +oid:String "The unique identifier of the view in the data management system".

[0056] VisualNavigatorDto project file visualization information includes +pathMode:List <visualelementdto>"Navigation mode according to path", +classificationMode:List <visualelementdto>"Navigation modes categorized by view".

[0057] VisualElementDto visualization element information includes: +id:String "element ID corresponding to the tree node", +name:String "tree node name", +typeName:String "tree node type name", +pid:String "parent node ID", +path:String "local storage path of the image exported from the view", +field:Long "ID assigned by the file server after the image is uploaded to the file server", +parent:VisualElementDto "parent visualization element", +children:List <visualelementdto>"Tree node name", +icon:String "icon information to be displayed before the node", +nodeId:String "tree node id".

[0058] After converting the original non-standardized core elements in the MBSE tool's project files into RFLP data or extended data, the converted data needs to be managed and presented in a product information management system. Therefore, an RFLP data model architecture diagram for a product information management system is proposed, which can be found in the appendix. Figure 2 .like Figure 2 As shown, Link association: represents a normal association relationship, which is reflected in the database as a relational intermediate table; UsageLink association: represents a parent-child association relationship, indicating that RFLP data can form a tree structure through this association relationship, which is also reflected in the database as a relational intermediate table; TraceLink association: is essentially also a type of association relationship, used to represent the traceability relationship between RFLP data.

[0059] Reference Appendix Figure 3 This illustrates a flowchart of the submission and updating of engineering documents provided in an embodiment of this application. For example... Figure 3 As shown, it includes:

[0060] First, convert the core elements in the MBSE project file into appendices. Figure 1 The standardized RFLP data type shown means that the converted data yields the extracted project file information (see attached document). Figure 1 The RflpStanard project file extraction information is used to extract the project file ID (or projectId). This ID is then used to search the product information management system's database. The system checks if the project file ID already exists in the product information management system. If it does, the existing system model data is checked out, the association between the system model data and the project file attachments is updated, and then the updated system model data is checked in. If the project file ID does not exist, the system model data is created, and the system model data's ID is recorded in its attributes. Then, the association between the system model data and the project file attachments is established.

[0061] This application's embodiments can avoid repeatedly uploading the same data, ensuring that multiple modifications to the same project file will not generate multiple sets of model data. Furthermore, if the integration system supports version management, and the data undergoes a checkout → update → check-in process to upgrade the data, each modified project file can be saved in the data's historical versions. When creating model data, the tool name and version can be stored in the model attributes, thus distinguishing project files generated by different tools or different tool software versions. The project file name can be used as the default name attribute value for the model data.

[0062] Appendix Figure 3 The illustrated solution is essentially a file-level integration solution. This application's embodiments can extend the file-level integration solution by allowing the submission and updating of data extracted from project files. For example, please refer to the appendix... Figure 4 This illustrates a flowchart of an integration method for an MBSE and a product information management system provided in an embodiment of this application. Figure 4 As shown, it includes:

[0063] The S400 extracts data to be processed from information extracted from project files according to user needs.

[0064] S410 determines whether there is data to be processed in the product information management system based on the ID of the data to be processed.

[0065] S420, if not present, then the first operation is performed through the product information management system. The first operation is used to add data to be processed in the product information management system.

[0066] S430, if present, then the second operation is performed through the product information management system, which updates the data to be processed in the product information management system.

[0067] The data to be processed includes first-element data or non-first-element data, wherein the first-element data includes at least one of requirement element data, functional element data, logical element data, and physical element data. Non-first-element data may include parameter element data (see appendix). Figure 1 Parameter element information), interface element data (refer to the appendix) Figure 1 (Interface element information), view element data (refer to the appendix) Figure 1 View information in the middle), trace element data (see appendix) Figure 1 (Information on the traceability relationship in the document) and document data (see attached document) Figure 1 At least one of the following: tool name, tool version, unique identifier of project file, and project name.

[0068] Product information management systems typically include multiple specialized systems, such as, but not limited to, demand management systems, product data management systems, product lifecycle management systems, simulation data management systems, and experimental data management systems.

[0069] There are two possible scenarios for the first operation. One scenario is that the data to be processed is being submitted to the product information management system for the first time. In this case, the system does not yet contain the corresponding data, allowing the first operation to be performed on the acquired data. The other scenario is that the data to be processed is not being submitted to the product information management system for the first time, but its ID confirms that it does not exist in the system. Similarly, the first operation can still be performed on the acquired data.

[0070] The second step includes modifying the attributes of the data to be processed and deleting data from the product information management system. For example, some data may not exist in the data to be processed but does exist in the product information management system; this data is the data that needs to be deleted.

[0071] This application embodiment uses an ID-based intelligent comparison mechanism to automatically identify whether there is already data to be processed (including first element data and non-first element data) in the product information management system, and intelligently triggers new or update operations, realizing fine-grained management of model elements; especially precise control over first element data such as requirement element data, functional element data, logical element data and physical element data.

[0072] Continue to refer to the appendix Figure 1 The data types mapped by RFLP data are all composed of parent and child structures. Based on the ID of the RFLP data and the ID of the parent node data (or parentId, or parent element ID), the parent-child relationship between the RFLP data and its parent node data can be represented, which is the UsageLink association.

[0073] RFLP data referenced by views can be represented by the `BaseDataInfo.ownedDiagramIds` property. By analyzing the `ownedDiagramIds` property, the product information management system can maintain the association between RFLP data and view element data. The association between RFLP data and parameter element data can be represented by the `LinkedParamIds` property. The ID of the RFLP data is uniformly stored in the `toolModelId` property within the product information management system.

[0074] Modifying RFLP data attributes on the tool side will not change the RFLP data ID. Therefore, based on the RFLP data ID, it can be determined whether it is an added (or newly added) RFLP data or an updated RFLP data when entering the product information management system, that is, whether the product information management system performs the first or second operation. RFLP data is usually a tree structure, so updating it is relatively complex. If you want to update the related relationships of an RFLP data (such as a UsageLink relationship), in order to preserve the version modification history, you must first check out the parent node data of the RFLP data, so that the parent node data generates a new version record, then create a UsageLink relationship between the modified RFLP data and the new version of the parent node data, and finally check in the new version of the parent data. The first and second operations of RFLP data will be explained in detail below:

[0075] Reference Appendix Figure 5 This illustrates a flowchart of performing a first operation according to an embodiment of this application. Figure 5 As shown, it includes:

[0076] S500 retrieves all root node data and creates pending data in the product information management system.

[0077] S510 creates the relationships between all root node data and system model data based on all root node data and preset system model data.

[0078] S520 creates a relationship between the parent node data and the data to be processed based on the ID of the data to be processed and the ID of the parent node data of the data to be processed.

[0079] When the first operation corresponds to the data to be processed being submitted to the product information management system for the first time, it is necessary to first obtain all root node data. Root node data refers to node data whose parent node data ID is empty. That is, by identifying all node data in the data to be processed whose parent node data ID is empty, all root node data can be obtained. All the data to be processed is then created in the product information management system. Next, the association relationship between all root node data and system model data is created; this relationship can be called the Link association between all root node data and system model data. The association relationship between parent node data and the data to be processed is also created; this relationship can be called the UsageLink association. Finally, the ID of the data to be processed is stored in the toolModelId in the product information management system.

[0080] Regardless of whether the data to be processed is requirement element data, functional element data, logical element data, or physical element data, the process of performing the first and second operations is the same. The following example uses functional element data as the data to be processed; please refer to the appendix. Figure 6 This illustrates a flowchart of a functional element data performing a first operation, as provided in an embodiment of this application. Figure 6 As shown, it includes:

[0081] Collect all root node function data, and then in the product information management system (which can be attached) Figure 6 In the data management system, create all functional element data. Create Link relationships between all root node functional data and system model data. Based on the ID of each functional element data and its parent node data ID, create UasgeLink relationships between each functional element data and its parent node data. Finally, store the ID of each functional element data in the attribute of each functional element data, that is, store it in toolModelId.

[0082] This application embodiment establishes a complete model architecture foundation by acquiring all root node data and creating pending data in the product information management system; it creates the association relationship between root nodes and system model data based on preset system model data to ensure the integrity of the model hierarchy structure; in particular, it establishes a precise parent-child association relationship through the ID of pending data and the ID of parent node data, realizing fine-grained management of model elements such as requirement element data, functional element data, logical element data and physical element data.

[0083] Reference Appendix Figure 7 This illustrates another flowchart of performing the first operation provided in an embodiment of this application. For example... Figure 7 As shown, it includes:

[0084] S700 determines whether the data to be processed is root node data based on the parent node data ID of the data to be processed.

[0085] S710: When the data to be processed is root node data, create a relationship between the data to be processed and the preset system model data.

[0086] S720: When the data to be processed is not root node data, determine whether there is parent node data for the data to be processed in the product information management system.

[0087] S730: If there is parent node data for the data to be processed, then create an association between the parent node data and the data to be processed.

[0088] S740, if there is no parent node data for the data to be processed, the parent node data is used as the new parent node data, and an association relationship is created between the new parent node data and the data to be processed.

[0089] When the first operation corresponds to a situation where the data to be processed is not submitted to the product information management system for the first time, but the ID of the data to be processed confirms that the corresponding data does not exist in the product information management system, batch creation and relationship maintenance are performed on the data to be processed. Then, based on the parent node data ID of the data to be processed, it is determined whether the data to be processed is root node data. Specifically, if the parent node data ID of the data to be processed is empty, the data to be processed is root node data. Alternatively, if no data with an ID equal to the parent node data ID of the data to be processed currently performing the first operation is found in the data to be processed extracted from the project file, then the data to be processed is root node data. When the data to be processed is root node data, the association relationship between the data to be processed and the preset system model data is created.

[0090] When the data to be processed is not root node data, determine whether parent node data exists in the product information management system. The specific determination process is as follows: based on the parent node data ID of the data to be processed, query the product information management system (excluding the currently created data to be processed) to see if there is data to be processed with `toolModelId = parent node data ID`. If parent node data exists, query the version of that parent node and check out the parent node, then create the association between the parent node data and the data to be processed, and finally check in the parent node. If parent node data does not exist, the parent node data is added as a new parent node, and the association between the new parent node data and the data to be processed is created.

[0091] Similarly, for a specific example using the data to be processed as the functional element data, please refer to the appendix. Figure 8 This illustrates a flowchart of another functional element data performing a first operation, provided in an embodiment of this application. For example... Figure 8 As shown, it includes:

[0092] This function performs batch creation of functional element data and maintains relationships for each newly added functional element. It determines whether a functional element is a root node functional element. The criteria are: if the parentld value of the functional element is empty, then the functional element is a root node functional element; if no functional element with id=parentld is found in functions, then that functional element is a root node functional element.

[0093] When the functional element data is root node functional data, a Link association is created between the system model data and the root node functional data. When the functional element data is not root node functional data, it is determined whether the parent node data of the current functional element data exists in the product information management system. Specifically, the determination is based on a query in the product information management system (excluding the currently created pending data) to see if there is functional element data with toolModelId = parentld. If the parent node data of the current functional element data already exists in the product information management system, the latest version of that parent node is retrieved and the parent node is checked out. Then, the parent node data and the corresponding functional element data (or appendix) are created. Figure 8 The `UsageLink` association between sub-functions in the product information management system is established, and finally, the parent node is checked in. If the parent node data for the current functional element data does not exist in the product information management system, the parent node data for the current functional element data is searched, and the parent node data and the corresponding functional element data (or appendix data) are created. Figure 8 The UaageLink association between sub-functions in the process.

[0094] This application embodiment intelligently determines whether a data is a root node based on the parent node data ID of the data to be processed, thereby achieving automatic identification of the model element hierarchy. For root node data, the association relationship between it and the system model data is directly established to ensure the integrity of the top-level architecture. For non-root node data, the existence of parent node data is dynamically checked and corresponding association relationships are intelligently created (including treating parent node data as newly added parent node data when necessary), which improves the efficiency and accuracy of constructing association relationships between model elements, while also realizing version control of individual model elements.

[0095] Reference Appendix Figure 9 This illustrates a flowchart of performing a second operation according to an embodiment of this application. Figure 9 As shown, it includes:

[0096] S900 retrieves data to be processed from the product information management system and modifies the attributes of the retrieved data.

[0097] S910, and / or, when the parent node data of the detected data to be processed has changed, create an association between the detected data to be processed and the changed parent node data, and delete the association between the detected data to be processed and the parent node data before the change.

[0098] S920, when the detected data to be processed changes from root node data to child node data, delete the association between the data to be processed before the change and the preset system model data, and create the association between the data to be processed after the change and its parent node data.

[0099] S930, when the detected data to be processed changes from child node data to root node data, delete the association between the data to be processed before the change and its parent node data, and create the association between the data to be processed after the change and the system model data.

[0100] The second operation can be modifying the attributes of the data to be processed, or deleting data from the product information management system. Deletion here refers to changing the position of the data to be processed in the tree structure, that is, changing the position of the parent node data of the data to be processed.

[0101] When the second operation is to modify the attributes of the data to be processed, the data to be processed can be retrieved from the product information management system, and the attributes of the retrieved data to be processed can be modified. The specific modification process is to synchronize the name and content attributes of the data to be processed according to the corresponding data in RflpStandard.functions.

[0102] When the second operation involves deleting data in the product information management system, the system identifies pending data whose parent node data location has changed, and then creates (or deletes) or modifies their related relationships. For example, if the parent node data of the detected pending data has changed, the system creates a relationship between the detected pending data and the changed parent node data, and deletes the relationship between the detected pending data and the parent node data before the change. Similarly, if the detected pending data changes from root node data to child node data, the system deletes the relationship between the pending data before the change and the preset system model data, and creates a relationship between the changed pending data and its parent node data. Likewise, if the detected pending data changes from child node data to root node data, the system deletes the relationship between the pending data before the change and its parent node data, and creates a relationship between the changed pending data and the system model data. Finally, the modified parent node data of the pending data is checked in.

[0103] This application embodiment ensures the controllability and traceability of data changes by detecting data to be processed from the product information management system and modifying its attributes; when the parent node data changes, the association relationship is automatically updated (including creating new associations and deleting old associations) to maintain the accuracy of the model topology; in particular, for the state transition between the root node and child nodes (such as the root node becoming a child node or a child node becoming a root node), the system intelligently processes the changes in the association relationship with the system model data or parent node data, further improving the ability to perform fine-grained control over the model elements inside the file and avoiding problems such as fragmentation of the integration solution.

[0104] Reference Appendix Figure 10 This illustrates another flowchart of performing the second operation provided in an embodiment of this application. For example... Figure 10 As shown, it includes:

[0105] S1000 queries the data to be deleted in the product information management system and determines the parent node data of the data to be deleted.

[0106] S1010: When the data to be deleted has parent node data, delete the association between the data to be deleted and its parent node data.

[0107] S1020: When the data to be deleted does not have parent node data, delete the association between the data to be deleted and the preset system model data.

[0108] The system queries the product information management system for data to be deleted and identifies its parent nodes. If a parent node exists, it retrieves the parent node, removes the association between the data to be deleted and its parent node, and finally retrieves the parent node. If no parent node exists, it removes the association between the data to be deleted and the preset system model data.

[0109] Similarly, for a specific example using the data to be processed as the functional element data, please refer to the appendix. Figure 11 This illustrates a flowchart of a functional element data performing a second operation, as provided in an embodiment of this application. Figure 11 As shown, it includes:

[0110] One possible approach is to process the data of the functional element to be deleted by querying its parent node. If the parent node is found, it is retrieved, the parent-child relationship (UageLink) is deleted, and then the parent node is retrieved. If the parent node is not found, the Link relationship between the functional element data and the system model data is deleted.

[0111] One possible approach is to modify the attributes of the functional element data. Each functional element data entry is retrieved, and then its name and content attributes are synchronized based on the corresponding functional data in RflpStandard.functions.

[0112] Another possible scenario is querying functional element data where the parent node data has changed. This could include: 1. The parent node data has changed; collect the UsageLinks that need to be deleted and the UsageLinks that need to be created (when the parent node data of the detected functional element data has changed, this refers to creating a UsageLink association between the detected functional element data and the changed parent node data, and deleting the UsageLink association between the detected functional element data and the parent node data before the change); 2. The functional element data has changed from a root node to a child node; collect the Links that need to be deleted and the UsageLinks that need to be created (this refers to creating a UsageLink association between the detected functional element data and the changed parent node data, and deleting the UsageLink association between the detected functional element data and the parent node data before the change); 3. The functional element data has changed from a root node to a child node; collect the Links that need to be deleted and the UsageLinks that need to be created (this refers to creating a UsageLink association between the detected functional element data and the changed parent node data, and deleting the UsageLink association between the detected functional element data and the parent node data before the change); 4. The functional element data has changed from a root node to a child node; collect the Links that need to be deleted and the UsageLinks that need to be created (this refers to creating a UsageLink association between the detected functional element data and the changed parent node data, and deleting the UsageLink association between the detected functional element data and the parent node data before the change); 5. The functional element data has changed from a root node to a child node; collect the Links that need to be deleted and the UsageLinks that need to be created (this refers to creating a UsageLink association between the detected functional element data and the parent node data before the change); 6. The functional element data has changed from a root node to a child node; collect the Links that need to be deleted and the UsageLinks that need to be created (this refers to creating a UsageLink association between the detected functional element data and the parent node data before the When functional element data changes from root node data to child node data, delete the Link association between the functional element data and the system model data before the change, and create the UsageLink association between the functional element data and its parent node data after the change; 3. When functional element data changes from a child node to a root node, collect the UsageLinks that need to be deleted and the system model Link data that need to be newly created (referring to deleting the UsageLink association between the functional element data and its parent node data before the change and creating the Link association between the functional element data and the system model data after the change when the detected functional element data changes from a child node data to a root node data).

[0113] Reference Appendix Figure 12 This illustrates a flowchart of performing a first operation on non-first element data, as provided in an embodiment of this application. Figure 12 As shown, it includes:

[0114] S1200: When the non-first element data is parameter element data, store the ID of the data to be processed in the product information management system, create the association between the data to be processed and the preset system model data, and create the association between the data to be processed and the requirement element data, functional element data, logical element data and physical element data respectively.

[0115] S1210, when the non-first element data is interface element data, create the association relationship between the data to be processed and the system model data, create the source-end association relationship between the data to be processed and the functional element data, logical element data and physical element data respectively, and create the target-end association relationship between the data to be processed and the functional element data, logical element data and physical element data respectively.

[0116] S1220, when the non-first element data is view element data, store the ID of the data to be processed in the product information management system, create an attachment relationship between the data to be processed and the image, create an association relationship between the data to be processed and the system model data, and create association relationships between the data to be processed and the requirement element data, functional element data, logical element data and physical element data respectively.

[0117] Parameter element data is stored as a list, without a tree structure, and parent-child relationships do not need to be handled. However, requirement element data, functional element data, logical element data, and physical element data all have Link relationships with parameter element data, expressed using the LinkedParamIds attribute. After parameter element data is created and updated, it is also necessary to handle the Link relationships between parameter element data and requirement element data, functional element data, logical element data, and physical element data respectively.

[0118] When non-first element data is parameter element data, the ID of the data to be processed is stored in toolModelId in the product information management system. Link relationships are created between the data to be processed and the preset system model data, as well as separate link relationships are created between the data to be processed and the requirement element data, functional element data, logical element data, and physical element data.

[0119] Interface element data can be divided into three categories: functional interfaces, logical interfaces, and physical interfaces. Therefore, the `type` attribute (interface type) of interface element data can take three values: "function", "logic", and "physical". A functional interface means that both the source and target data of the interface are associated with functional data. A logical interface means that both the source and target data of the interface are associated with logical data. A physical interface means that both the source and target data of the interface are associated with physical data.

[0120] When non-first element data is interface element data, add interface element data in batches. Create Link associations between the data to be processed and the system model data. Create source Link associations between the data to be processed and functional element data, logical element data, and physical element data, respectively. Create target Link associations between the data to be processed and functional element data, logical element data, and physical element data, respectively.

[0121] When creating view element data, after the project file is submitted, all views in the project file are extracted as images, and these images are managed using view object data in the product information management system. Batch addition of view element data stores the IDs of the view element data in the contentElementIds property of the product information management system. This collection contains the IDs of requirement element data, functional element data, logical element data, physical element data, parameter element data, and interface element data. After the view element data is created, it is necessary to create links between the view element data and the requirement element data, functional element data, logical element data, physical element data, parameter element data, and interface element data, and these links must also be maintained during updates.

[0122] When a non-first element is view element data, the image is uploaded to the file server and the field is recorded. View element data is added in batches, and the IDs of these view element data are stored in the `toolModelID` property. Attachment relationships are created between view element data and images; Link relationships are created between system model data and view element data; and Link relationships are created between view element data and requirement element data, functional element data, logical element data, physical element data, parameter element data, and interface element data.

[0123] In some embodiments of this application, if present, a second operation is performed through the product information management system, specifically including: when the second operation is a modification operation, retrieving the data to be processed from the product information management system and modifying the attributes of the retrieved data to be processed; and / or, when the second operation is a deletion operation, deleting and / or creating the relevant associations of the retrieved data to be processed.

[0124] For details, please refer to the appendix. Figure 13 This illustrates a flowchart of a second operation performed on parameter element data provided in this application in real time. For example... Figure 13 As shown, it includes:

[0125] Based on the mapping relationship between the parameter element data's ID and toolModelId, locate the parameter element data that needs updating. Detect the parameter element data, update its attribute information, and then check it in. Using the linkedParamIds attribute of the RFLP data, compare it with the current RFLP data and parameter element data's Link associations in the system to collect Link associations that need to be deleted and Link associations that need to be created. Batch process Link associations, finding RFLP data based on the Link associations. Detect the RFLP data (skip this step if it has already been detected), and then delete or create Link associations. Finally, check in all detected RFLP data.

[0126] Reference Appendix Figure 14 The diagram illustrates a flowchart of an interface element data performing a second operation, provided in real time according to this application.

[0127] like Figure 14 As shown, it includes:

[0128] Based on the relationship between the ID of the interface element data and toolModelId, the system searches for interface data in the current product information management system to identify the interface element data that needs to be added, updated, or deleted. When interface element data needs to be added, the first operation performed on the interface element data in the aforementioned embodiment can be used to add the interface data.

[0129] When performing modification operations on interface element data, the interface element data can be checked out, the interface element data attributes can be updated, and finally the interface element data can be checked in.

[0130] When performing a deletion operation on interface element data, in one possible scenario, the interface element data to be deleted is processed in batches, and the link associations between the system model data and the interface element data to be deleted are deleted. In another possible scenario, the following are collected separately: 1. The source link associations between the functional element data, logical element data, and physical element data to be deleted and the interface element data; 2. The source link associations between the functional element data, logical element data, and physical element data to be added and the interface element data; 3. The target link associations between the functional element data, logical element data, and physical element data to be deleted and the interface element data; 4. The target link associations between the functional element data, logical element data, and physical element data to be added and the interface element data. Then, the relevant associations are added or deleted, and finally, all the detected functional element data, logical element data, and physical element data are checked in.

[0131] Reference Appendix Figure 15 This illustrates a flowchart of a second operation performed on view element data provided in real-time according to this application. For example... Figure 15 As shown, the specific operation process is similar to the process of the interface element data performing the second operation, so it will not be described in detail here.

[0132] In some embodiments of this application, when the data to be processed includes non-first element data, if it does not exist, a first operation is performed through the product information management system, specifically including: when the non-first element data is traceable element data, determining the associated demand element data, functional element data, logical element data, and physical element data based on the data source end information and target end information extracted from the engineering file; and creating traceable association relationships for the associated demand element data, functional element data, logical element data, and physical element data respectively.

[0133] Traceability element data is used to represent relationships between elements recorded in the project file, other than parent-child relationships. This application primarily focuses on the traceability relationships between requirement element data, functional element data, logical element data, and physical element data; therefore, it only provides solutions for extracting various types of relationships between requirement element data, functional element data, logical element data, and physical element data from the project file. Traceability relationships are represented using the TraceLink object model in the data management system.

[0134] When the non-first element data is a traceable element data, the List is extracted from the information in the project file. <traceinfo>The traces record source and destination information of the trace element data, and the associated RFLP data is queried. Then, TraceLink associations are created for these queried RFLP data.

[0135] When the data to be processed includes non-first element data, and the non-first element data is traceable element data, the second operation flow corresponding to the traceable element data can be: collect the List submitted this time. <tracelnfo>The traces record source and destination information of the trace element data, involving RFLP data. Query the TraceLink associations associated with this RFLP data. Delete these TraceLink associations in batches. Then, according to the list submitted this time... <tracelnfo>TraceLink associations are recreated for these RFLP data traces.

[0136] In some embodiments of this application, when the data to be processed includes non-first element data, if it does not exist, a first operation is performed through the product information management system, specifically including: when the non-first element data is file data, creating system model data based on the tool name, tool version, project name, and ID of the data to be processed in the data to be processed, and associating the system model data and the data to be processed; if it exists, a second operation is performed through the product information management system, specifically including: when the non-first element data is file data, updating the association between the system model data and the data to be processed.

[0137] The detailed content of the embodiments of this application has been described in the foregoing embodiments, and will not be repeated here.

[0138] This application provides an integrated system of MBSE and a product information management system, including: an acquisition module for acquiring data to be processed from information extracted from engineering files according to user requirements; a judgment module for determining whether the data to be processed exists in the product information management system based on the ID of the data to be processed; an execution module for performing a first operation through the product information management system if the data does not exist; the execution module is further configured to perform a second operation through the product information management system if the data exists; the data to be processed includes first element data or non-first element data, wherein the first element data includes at least one of requirement element data, functional element data, logical element data, and physical element data.

[0139] The detailed contents of the embodiments of this application have been described in the foregoing embodiments, and will not be repeated here.

[0140] It should be noted that the above embodiments can be freely combined as needed. The above are merely preferred embodiments of the present invention. It should be pointed out that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.< / tracelnfo> < / tracelnfo> < / traceinfo> < / visualelementdto> < / visualelementdto> < / visualelementdto> < / string> < / string> < / string> < / string> < / string> < / string> < / string> < / string> < / diagraminfo> < / traceinfo> < / interfaceport> < / paraminfo> < / physicalinfo> < / logicinfo> < / functioninfo>

Claims

1. A method of integration of MBSE and product information management system, characterized in that, The method comprises the following steps: extracting the to-be-processed data from the information extracted from the engineering file according to the user demand; determining whether the to-be-processed data exists in the product information management system based on the ID of the to-be-processed data; if not, performing a first operation on the product information management system, the first operation being used for adding the to-be-processed data in the product information management system; if yes, performing a second operation on the product information management system, the second operation being used for updating the to-be-processed data in the product information management system; the to-be-processed data comprises first element data or non-first element data, wherein the first element data comprises at least one of demand element data, function element data, logic element data and physical element data.

2. The integration method of MBSE and product information management system according to claim 1, characterized in that, when the to-be-processed data comprises first element data, the if not, performing a first operation on the product information management system specifically comprises: obtaining all root node data and creating the to-be-processed data in the product information management system; based on the all root node data and the preset system model data, creating an association relationship between the all root node data and the system model data; based on the ID of the to-be-processed data and the parent node data ID of the to-be-processed data, creating an association relationship between the parent node data and the to-be-processed data.

3. The integration method of MBSE and product information management system according to claim 1, characterized in that, when the to-be-processed data comprises first element data, the if not, performing a first operation on the product information management system specifically comprises: based on the parent node data ID of the to-be-processed data, determining whether the to-be-processed data is root node data; when the to-be-processed data is root node data, creating an association relationship between the to-be-processed data and the preset system model data; when the to-be-processed data is not root node data, determining whether the parent node data of the to-be-processed data exists in the product information management system; if the parent node data of the to-be-processed data exists, creating an association relationship between the parent node data and the to-be-processed data; if the parent node data of the to-be-processed data does not exist, taking the parent node data as new parent node data and creating an association relationship between the new parent node data and the to-be-processed data.

4. The integration method of MBSE and product information management system according to claim 1, characterized in that, when the second operation is a modification operation and the to-be-processed data comprises first element data, the if yes, performing a second operation on the product information management system specifically comprises: checking out the to-be-processed data from the product information management system, modifying the attribute of the checked-out to-be-processed data; and / or, when the parent node data of the checked-out to-be-processed data changes, creating an association relationship between the checked-out to-be-processed data and the changed parent node data and deleting the association relationship between the checked-out to-be-processed data and the changed parent node data; when the checked-out to-be-processed data changes from root node data to child node data, deleting the association relationship between the changed to-be-processed data and the preset system model data and creating an association relationship between the changed to-be-processed data and its parent node data; When the detected to-be-processed data changes from sub-node data to root node data, deleting the association relationship between the to-be-processed data before the change and the parent node data, and creating an association relationship between the to-be-processed data after the change and the system model data.

5. The integration method of MBSE and product information management system according to claim 1, characterized in that, When the second operation is a deletion operation and the to-be-processed data includes first element data, the second operation is executed through the product information management system if the to-be-processed data exists, and specifically includes: Querying to-be-deleted data in the product information management system, and determining parent node data of the to-be-deleted data; When the to-be-deleted data has parent node data, deleting the association relationship between the to-be-deleted data and the parent node data; When the to-be-deleted data has no parent node data, deleting the association relationship between the to-be-deleted data and preset system model data.

6. The integration method of MBSE and product information management system according to any one of claims 1-5, characterized in that, When the to-be-processed data includes non-first element data, the first operation is executed through the product information management system if the to-be-processed data does not exist, and specifically includes: When the non-first element data is parameter element data, storing the ID of the to-be-processed data in the product information management system, creating an association relationship between the to-be-processed data and preset system model data, and respectively creating association relationships between the to-be-processed data and the requirement element data, the function element data, the logic element data and the physical element data; When the non-first element data is interface element data, creating an association relationship between the to-be-processed data and the system model data, respectively creating source end association relationships between the to-be-processed data and the function element data, the logic element data and the physical element data, and respectively creating target end association relationships between the to-be-processed data and the function element data, the logic element data and the physical element data; When the non-first element data is view element data, storing the ID of the to-be-processed data in the product information management system, creating an attachment relationship between the to-be-processed data and a picture, creating an association relationship between the to-be-processed data and the system model data, and respectively creating association relationships between the to-be-processed data and the requirement element data, the function element data, the logic element data and the physical element data.

7. The integration method of MBSE and product information management system according to claim 6, characterized in that, The second operation is executed through the product information management system if the to-be-processed data exists, and specifically includes: When the second operation is a modification operation, the to-be-processed data is checked out from the product information management system, and the attribute of the checked-out to-be-processed data is modified; And / or, When the second operation is a deletion operation, related association relationships of the checked-out to-be-processed data are deleted and created.

8. The integration method of MBSE and product information management system according to any one of claims 1-5, characterized in that, When the to-be-processed data includes non-first element data, the first operation is executed through the product information management system if the to-be-processed data does not exist, and specifically includes: When the non-first element data is trace element data, the associated requirement element data, the function element data, the logic element data and the physical element data are determined according to the to-be-processed data source end information and the target end information in the engineering file extraction information; Trace association relationships are respectively created for the associated requirement element data, the function element data, the logic element data and the physical element data.

9. The integration method of MBSE and product information management system of claim 1, wherein, When the to-be-processed data includes non-first element data, if the non-first element data is file data, system model data is created according to the tool name, the tool version, the engineering name and the ID of the to-be-processed data in the to-be-processed data, and the system model data and the to-be-processed data are associated. When the non-first element data is file data, the associated relationship between the system model data and the to-be-processed data is updated. The method comprises the steps of: An acquisition module is configured to acquire to-be-processed data from engineering file extraction information according to user requirements; 10. An integrated system of MBSE and product information management system, characterized in that, A judgment module is configured to determine whether the to-be-processed data exists in a product information management system based on the ID of the to-be-processed data; An execution module is configured to perform a first operation through the product information management system if the to-be-processed data does not exist in the product information management system. The execution module is further configured to perform a second operation through the product information management system if the to-be-processed data exists in the product information management system. The to-be-processed data includes first element data or non-first element data, wherein the first element data includes at least one of requirement element data, function element data, logic element data and physical element data. ​ ​

Images