MBSE collaborative research and development management system based on Web

Abstract

The invention provides a Web-based MBSE collaborative research and development management system, which belongs to the field of model-based system engineering and comprises a demand center used for managing demands generated in a system development process and supporting system models, simulation data and demand entries to trace; the model center is used for managing model data generated in a system development process taking a demand as an input; the simulation center is used for calling and executing each model and recording simulation configuration, simulation tasks and simulation result data; the document center is used for extracting data and automatically generating and managing various documents; the digital clue is used for managing digital clue data of the MBSE and displaying an association tracing relation of data in a forward design process based on a model; and the project management module is used for managing the information of the MBSE research and development project. According to the method, a model-based system digital research and development process is realized, team cooperation efficiency and product design quality are improved, and tool support is provided for complex product MBSE activities.

Description

Technical Field

[0001] The present invention belongs to the field of model-based systems engineering (MBSE), and in particular relates to a Web-based MBSE collaborative R&D management system. Background Art

[0002] With the development trend of intelligent and integrated complex products, and the extensive and in-depth application of model-based system engineering (MBSE) in various industries, more and more equipment manufacturing companies have realized that they must rely on forward R&D thinking to break through key technical barriers, design better products, and achieve high-quality development of enterprises. With the engineering application of MBSE-related software, various product design models have been accumulated, including demand models, functional logic models, physical architecture models, embedded models, geometric models, simulation models, etc. However, the following problems are still exposed in the model-based design process: poor compatibility between various tool systems, making it difficult to achieve effective transmission of model data; lack of sufficient decoupling of models generated in the design process, making it difficult to establish fine-grained traceability relationships between various models; unclear task management in the design process, making it difficult to achieve the association between tasks and deliverables. At present, there is no integrated platform that can effectively manage MBSE-related activities and data.

[0003] With the development of technologies such as big data, cloud computing, the Internet of Things, cyber-physical systems, large models, and artificial intelligence, how to effectively associate the large amount of model data generated in the process of model-based system engineering, establish digital clues for the entire life cycle of the product, and improve the agility and adaptability of the system engineering process and the effectiveness of the process element transmission link through intelligent means is the key bottleneck in the current development of MBSE technology. To solve the above problems, it is necessary to realize the full life cycle process activities and data management of RFLP in an integrated MBSE collaborative platform, while being compatible with various heterogeneous modeling tools, and being able to perform data mining and analysis on models of different tool manufacturers through machine learning, accelerating the development cycle of complex products. Summary of the invention

[0004] In order to solve the above technical problems, the present invention provides a Web-based MBSE collaborative R&D management system, which includes the following modules: Demand center, used to manage the requirements generated during system development and support traceability between system models, simulation data and requirement items; Model center, used to manage model data generated during the system development process with requirements as input, including SysML models, Modelica models, Cyphy models, and FMU models; The simulation center is used to call and execute SysML models, Modelica models, and FMU models, and record simulation configurations, simulation tasks, and data generated during the simulation process; Document center, which is used to extract data from the MBSE collaborative R&D management system, automatically generate and manage various documents that meet user standards and specifications, including requirement documents, design documents, and simulation verification documents; Digital clues, used to manage MBSE digital clue data and display the correlation and traceability of data in the model-based forward design process; The project management module is used to manage MBSE R&D project related information, including: project PBS structure, project plan, project tasks, project members, roles and permissions.

[0005] Beneficial effects: The present invention provides a Web-based MBSE collaborative R&D management system, which realizes the model-based system digital R&D process through a unified platform, solves the problems of poor compatibility between various tool systems and inability to effectively transfer model data; at the same time, it fully decouples the models generated in the design process and establishes a fine-grained traceability relationship between various models; it performs task management on the design process and realizes the association between tasks and deliverables, thereby realizing effective management of MBSE-related activities and data, improving team collaboration efficiency and product design quality, and providing tool support for complex product MBSE activities. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1 is a relationship diagram between modules of a Web-based MBSE collaborative R&D management system provided by an embodiment of the present invention; Figure 2 It is composed of a Web-based MBSE collaborative R&D management system provided by an embodiment of the present invention; Figure 3 It is an architecture diagram of a Web-based MBSE collaborative R&D management system provided by an embodiment of the present invention; Figure 4 It is a bottom-level data structure diagram of a Web-based MBSE collaborative R&D management system provided by an embodiment of the present invention; Figure 5 It is a schematic diagram of the implementation principle of digital clues provided by an embodiment of the present invention; Figure 6 is a schematic diagram of demand management provided by an embodiment of the present invention; Figure 7 is a schematic diagram of SysML model management provided by an embodiment of the present invention; Figure 8 is a schematic diagram of FMU model management provided by an embodiment of the present invention; Fig. 9is a schematic diagram of SysML simulation management provided by an embodiment of the present invention; Fig.10 Schematic diagram of FMU simulation management provided by an embodiment of the present invention; Fig.11 is a schematic diagram of a document center provided by an embodiment of the present invention; Fig.12 is a schematic diagram of digital clue association analysis provided by an embodiment of the present invention; Fig.13 It is a schematic diagram of project management provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0007] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. In addition, the technical features involved in the various embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0008] Embodiment 1 The embodiment of the present invention provides a Web-based MBSE collaborative R&D management system, which includes the following modules: Demand center, used to manage the requirements generated during system development and support traceability between system models, simulation data and requirement items; Model center, used to manage model data generated during the system development process with requirements as input, including SysML models, Modelica models, Cyphy models, and FMU models; The simulation center is used to call and execute SysML models, Modelica models, and FMU models, and record simulation configurations, simulation tasks, and data generated during the simulation process; Document center, which is used to extract data from the MBSE collaborative R&D management system, automatically generate and manage various documents that meet user standards and specifications, including requirement documents, design documents, and simulation verification documents; Digital clues, used to manage MBSE digital clue data and display the correlation and traceability of data in the model-based forward design process; The project management module is used to manage MBSE R&D project related information, including: project PBS structure, project plan, project tasks, project members, roles and permissions.

[0009] like Figure 1 As shown, it is a relationship diagram between various modules of the Web-based MBSE collaborative R&D management system in an embodiment of the present invention.

[0010] like Figure 2As shown in the figure, according to the business architecture, the MBSE collaborative R&D system is divided into six modules: demand center, model center, simulation center, document center, digital clues, and project management foundation. Finer-grained services are split by each module.

[0011] like Figure 3 As shown, the underlying architecture of the system of the present invention builds various microservice components based on micro-frontend technology to support the MBSE collaborative R&D system. The underlying architecture of the system adopts a distributed microservice framework as a whole to meet the traditional and cloud cluster deployment methods. The underlying framework provides microservice governance functions such as service discovery, load balancing, and elastic scaling, decoupling the platform technology level from the business level. The top-level business is integrated on the platform as an independent service module to achieve flexible expansion, high concurrency, and high availability of the business. Different business modules of the system are developed and deployed by different teams to give full play to the advantages of the microservice architecture. The system provides common business modules, such as users, roles, menu permissions, process engines, low-code development, standard UI controls, log monitoring and other basic functions.

[0012] like Figure 4 As shown, the data modeling of this system adopts ontology theory to abstract the system requirement model, SysML model, Modelica model, Cyphy model, FMU model, and metamodel of simulation data, and establish database entities and their relationships based on the created metamodel ontology and the relationship between ontologies.

[0013] Furthermore, the bottom layer of data modeling defines and maintains model data through a set of patterns to establish data tracking relationships. By analyzing the metamodel of each business domain model of MBSE, the database entity structure and the relationship between entities that store the model are designed based on the metamodel. Each entity can automatically generate a general interface based on data modeling, or generate a dedicated interface for a certain entity. Through service orchestration, the combination and call of different entity interfaces are realized to form microservice capabilities. The top layer displays the system model from different business perspectives.

[0014] like Figure 5As shown, the model data is output into a specific format file (such as JSON, XML, RDF, OWL, etc.) through the model center; the information integration and interoperability layer constructs the meta-model of model objects in various fields for information in different fields such as system design, system simulation, demand development, system design, assembly manufacturing, test identification, and operation assurance, focusing on model objects such as demand models, three-dimensional digital models, experimental test data, functional models, and behavioral models; after obtaining relevant model data from the model center, the data is transformed and integrated, and then through data analysis, data mapping, data acquisition and other steps, the data is published as an open API interface and interface services are provided to the outside world; digital clues manage the linked data and perform model consistency and integrity checks; data query functions are opened to the general tool layer data requirements so that other third-party tools can obtain the model data they need.

[0015] In one embodiment, the demand center is used to manage the requirements generated during the system development process and trace the system model, simulation data and requirement items, specifically including: Based on PBS, the project's requirement information architecture is automatically initialized. The requirement information architecture includes: the project's hierarchical directory, hierarchical name, file name, creator, creation time, description, and type. The requirement information architecture graphically displays the composition of the requirement document and the relationship between documents. The requirement document includes name, type, prefix, status, responsible person, historical information, module attributes, file traceability, and access rights; The requirement document consists of requirement items, which are displayed one by one in a tabular interface. Double-click any item with the mouse to open the right area of ​​the interface and edit the requirement item, while displaying the detailed content of the requirement item. There are three main ways to establish associations between requirement items. The first is to open two requirement documents on the same interface and establish links by dragging the mouse. The second is to establish links by checking the cells of the requirement tracking matrix in a table. The third is to establish links by graphically displaying the requirement tree on the Web interface. When there is a link between requirement items, it is indicated by a triangle symbol. The left side indicates an incoming link, the right side indicates an outgoing link, yellow indicates that the linked object has changed, and green indicates that the linked object has not changed. When multiple people open the same requirement document, the online editors are displayed in the upper right corner of the requirement document editing interface, and the requirement items currently being edited by other people are displayed in a frame line; The person in charge of the requirement document selects the requirement items in the requirement document and assigns them to other requirement documents. The persons in charge of other requirement documents can receive the message and view the contents of the assigned requirement items: The demand center of the embodiment of the present invention includes a demand management front-end component and a demand management back-end component, wherein the demand management front-end component is used for demand data management, page display and business interaction; the demand management back-end component provides demand management back-end business interface services.

[0016] like Figure 6 As shown, the demand center of the embodiment of the present invention is composed of modules such as demand definition, demand management, process management, document generation and three-member management. The demand center includes the management of system requirements and system requirements. In online collaboration or offline collaboration mode, the transfer of system requirements to system requirements can be realized; the demand center is used to efficiently manage model, system, subsystem and equipment-level requirements, covering functions such as demand definition, decomposition, tracking, publishing, change, partition import and export, to achieve demand definition, capture, and allocation in the early stage of product design; demand tracking analysis, change impact analysis, publishing, verification, and baseline management in the mid-term of product design; project demand data analysis, demand template generation, and demand data reuse in the late stage of product design, to establish the only source of truth for demand in the process of model-based forward development. In view of the multi-level and multi-dimensional characteristics of complex product demand information, and focusing on the consistency requirements of complex product demand definition and management processes, effective organization, capture definition, efficient collaboration, precise control, and rapid reuse of demand are achieved.

[0017] In one embodiment, the model center is used to manage model data generated during the system development process with requirements as input, including: SysML model, Modelica model, Cyphy model, FMU model, specifically including: By calling the API interface of the client system modeling and simulation tool, all local model data can be traversed and obtained; The model management server uses a relational database, an object storage database, and a graph database to manage and version model elements. The basic information of the model objects is stored in the relational database, including object ID, object name, object label, parent object, child object, and model tree structure; the attribute information of the model objects is stored in the object storage database; and the relationship between model elements is stored in the graph database.

[0018] SysML model management includes SysML model management front-end components and SysML model management back-end components, wherein the SysML model management front-end components are used to display SysML package structure diagrams, requirement diagrams, use case diagrams, activity diagrams, sequence diagrams, state diagrams, parameter diagrams, block definition diagrams, and internal block diagrams; the SysML model management back-end components are used to organize and store the underlying structured data of SysML package diagrams, requirement diagrams, use case diagrams, activity diagrams, sequence diagrams, state diagrams, parameter diagrams, block definition diagrams, and internal block diagrams; like Figure 7The figure shows the SysML model management component. SysML is a multi-purpose system modeling language used in the field of system engineering. This component strictly complies with the OMG SysML v. 1.6 [Dec 2019] specification. The model data structure description and expression follow the MOF specification. The SysML model front-end component displays SysML package diagrams, requirement diagrams, use case diagrams, activity diagrams, timing diagrams, state diagrams, parameter diagrams, block definition diagrams, and internal block diagrams. The drawing of each graphic is based on the following methods: Graphic elements are generally organized in a tree structure. There is a strict parent-child relationship between elements, and there is only one root node to ensure consistency with the logical level of model elements. By extending the definition of some graphic elements, the deletion logic problem involved in the parent-child relationship at the graphic element level is solved, and the "parent-child" relationship at the representation level is handled in two ways: parent-child reference and indirect reference. The properties of DiagramElement are extended, and the IsChild and ByDelete properties are added. When the model element is determined to be a parent-child relationship, the semantic consistency of the action behavior of the graphic element is achieved by synchronizing the parameters. Graphic element conversion starts from the root node of the model element through the interface, accesses the model diagram and the graphic information of the model element step by step, and recursively accesses the graphic information of the contained child elements. Model management adopts a set of graphic elements UML DI (Diagram Interchange) formulated by the OMG organization for controlling UML models. It provides a set of standard specifications for reference for UML graphic modeling. Graphic elements can be divided into two categories: Shape and Edge, and are mapped to instances of SysML DI model elements.

[0019] (1) guid As the identification code of the graphic element, the associated element can be retrieved through the DI model element factory to ensure consistency with the unique code of the model element.

[0020] (2) owningElement The parent element of the graphic element needs to map both IsChild and ByDelete attributes to ensure the semantic consistency of the graphic element.

[0021] (3) owneElement The child elements contained in the graphic element need to be mapped recursively in the same way as the owningElement element, and the IsChild and ByDelete attributes need to be mapped.

[0022] (4) Bounds The relative position and size of the graphic elements in the modeling tool will form a mapping rule and algorithm after being displayed on the platform, thereby ensuring consistency with the mapping parameters of the modeling tool.

[0023] (5) shareStyle When a graphic element contains sub-elements, this property affects the style display of all sub-elements. However, when the sub-elements are styled individually, this mapping is meaningless.

[0024] (6) localStyle As a special style of a child element, it is consistent with the parent element by default. When set separately, it is not affected by the parent element.

[0025] SysML model management can carry out hierarchical modeling according to the model granularity. By creating branches, multiple sub-branches are derived from the master branch, and the modeling requirements and interfaces are distributed to the designated system-level modeling team, which then carries out the modeling work of the corresponding system. Similarly, subsystem-level branches can be derived from system-level branches and handed over to designated subsystem-level modeling teams for modeling, and subsystem lower-level branches can also be derived from subsystem-level branches. Models submitted by all branch teams can be merged up to the master branch layer by layer according to branches, thus forming a unified system engineering model for the equipment system. Branches can specify development teams and personnel. Each branch has independent version control capabilities. Branch versions can be compared and merged. Users can view branch version records and compare the differences between different versions in a graphical way. The offline space definition of model collaboration can check and set permissions for the model tree on a branch according to the directory, expose the agreed interface to the outside, and encrypt and package it for export.

[0026] Modelica model management includes Modelica model management front-end components and Modelica model management back-end components. The Modelica model management front-end components are used to display the package hierarchy of the Modelica model, the input, output and result parameters of the model, and the type and initial value of the parameters on the page; the Modelica model management back-end components are used to organize and store the structured data of the Modelica model, parse the model data, and provide front-end rendering and display.

[0027] Cyphy model management includes Cyphy model management front-end components and Cyphy model management back-end components. The Cyphy model management front-end component is used to display the directory structure and hierarchical relationship of the cyber physics model project, and to display the basic information of the model, including name, type, responsible person, member, version, creator, creation time, and description. The version information includes the version name, and provides new versions and historical versions for download. The Cyphy model back-end component is used to organize and store the structured data of the cyber physics model, parse the model data, and provide front-end rendering and display; provide client modeling tool model upload, download, and update functions; and provide multi-version management of the same object.

[0028] FMU model management includes FMU model management front-end components and FMU model management back-end components. The FMU model management front-end components are used to display the input, output and common parameters of the FMU model, and establish port communication between two FMU models by dragging and dropping in the graphical interface; the FMU model management back-end components are used to organize and store the structured data of the FMU model, parse the model data, and provide front-end rendering and display.

[0029] like Figure 8 The following is the FMU model management component. The FMU model is managed in a tree structure on the left. Selecting a model will display the basic information and model parameters of the model. Model parameters include the input, output and common parameters of the model. Parameter information includes name, type, initial value, unit, quantity and description.

[0030] In one embodiment, the simulation center is used to call and execute SysML models, Modelica models, and FMU models, and record simulation configurations, simulation tasks, and data generated during the simulation process, specifically including: Create simulation configuration for the system model selected in the model center, configure input and output parameters and simulation process parameters in the simulation configuration, and the simulation task can call and execute SysML models, Modelica models, and FMU models; Multiple simulation tasks can be created for each simulation configuration, and the requirement items to be verified can be specified in the simulation tasks; Call the local or cloud simulation engine through simulation tasks, identify data based on the OWL network ontology language, provide an entry for automatically executing simulation tasks and analyzing simulation data, and store and manage simulation results; In a simulation task, you can view any historical simulation results.

[0031] The simulation center of the embodiment of the present invention comprises a simulation center front-end component and a simulation center back-end component, wherein the simulation center front-end component is used to establish simulation configuration, simulation tasks, simulation task execution, simulation execution result storage, and simulation execution result replay interface display; the simulation center back-end component is used for simulation configuration, simulation tasks, simulation task execution, simulation execution result storage, simulation execution result storage, data parsing and assembly, and providing a SysML model simulation engine; providing FMU model joint simulation; like Fig. 9 The figure shows a schematic diagram of SysML simulation management. The online simulation of the SysML model in the simulation center of the embodiment of the present invention has simulation configuration management, simulation node management, external resource management, simulation script management, simulation plan management, simulation task management, and simulation result management components. (1) Simulation configuration management: establish simulation name, description, and configuration-related parameters; (2) Simulation node management: manage the simulation engine client, including machine name, IP, port, modeling environment, current status, CPU, memory, and hard disk information; (3) External resource management: display model, interface list, signal list, and basic information; (4) Simulation script management: add commands to be executed during simulation execution and write code; (5) Simulation plan management: Add a simulation execution plan, which includes the plan name, associated simulation tasks, start time, end time, plan description, and responsible person; (6) Simulation task management: definition of simulation tasks, including task name, task status, associated simulation configuration, associated simulation script, task description, responsible person, assignment of task execution nodes, and task initialization; (7) Simulation result management: The information includes simulation task, batch number, module ID, simulation result after execution, validity, creation time, and last update time.

[0032] like Fig.10 The following is a schematic diagram of FMU simulation management. The simulation center provides FMU model joint simulation, including simulation configuration, simulation tasks, and simulation data. (1) Simulation configuration: Select a simulation model in the FMU model library and combine the simulation model port information by dragging and dropping; (2) Simulation task: including simulation name, simulation configuration, start time, end time, simulation step, result output interval, simulation method, related requirements, and simulation results; (3) Simulation data: store and manage process data generated during the execution of simulation tasks, and view and replay data.

[0033] In one embodiment, the document center is used to extract data from the MBSE collaborative R&D management system, automatically generate and manage various documents that meet user standards and specifications, including requirement documents, design documents, and simulation verification documents, specifically including: Multiple data source management: manage each type of business model in the form of data source. Based on the model data in the output target system, the data source can be abstracted into an operable target object, which covers all input contents of the target system. Document template management. Document templates are used to specify the composition of document content. Users design the document framework in a graphical way, create document templates based on abstract document standards, specify the document cover, directory, main text, headers and footers, express output content through graphic nested formats, specify output styles, set filtering conditions, and generate tables. It supports single data source and multiple data source combinations, and generates documents that meet user requirements through designed document templates.

[0034] Document generation engine, used to generate documents in word, PDF, json, and xml formats.

[0035] like Fig.11 The document center is shown, which includes the document center front-end component and the document center back-end component. The document center front-end component is used to maintain the style of the generated target document, generate the chapters and paragraphs of the target document, and design the query and filtering conditions of the document template; the document center back-end component is used to parse the document template, call the data source, process the original data, and post-process the document content and style; Data source structure definition: Based on the data model in the output target system, the data source is abstracted into an operable target object that covers all input content of the target system. The system has built-in demand-centered and model-centered data source templates to export system data. Provide data source template definition specifications. After other third-party tools define data source templates and interfaces according to this specification, they can import data from other third-party tools. Through data source attribute editing, users can edit data source template attributes as needed, and perform template attribute operations such as adding, modifying, and deleting. Through data source sharing, users can share newly added data sources with their team or other stakeholders.

[0036] Document template definition: define the extracted data content and data formatting method. Use graphic symbols to identify data objects, and define page elements such as cover, directory, header and footer, picture, table, table content, appendix, etc. Users can customize the font and style of the document after output. Users can iterate and improve the output content through the free combination of template elements. Users can set filtering conditions to output data that meets the requirements. Users can configure multiple data sources from the same or different tools in a template, and obtain data from multiple data sources to generate a document. When defining the associated data source in the document generation template, the inner control data source can choose to inherit the outer control data source. In the process of designing the document generation template, drag and drop the JS script control, and write the js script and correctness test in the control. When generating a document template, you can customize variables and assign values ​​to them, and the values ​​of the variables can be output in the final generated document.

[0037] Document generation engine: Access the data of the target system according to the data source format, parse and execute the graphic information expressed by the document template, dynamically output the data source content, and provide sequential output, recursive output, object attribute output, custom attribute output, linked object output, filter output, and can parse the attributes and styles set by the template. It can combine the data source data with the template data to generate documents in WORD, PDF, HTML, JSON and other 4 formats that meet the standards. In WORD and PDF, you can insert pictures, add headers and footers, create tables, add form fields and mail merge fields, add bookmarks, add text and picture watermarks, set background colors and background pictures, add footnotes and endnotes, add hyperlinks, digital signatures, encrypt and decrypt Word documents, add comments, add shapes, etc. HTML outputs the data source in the specified message format. When generating a document, you can choose whether to encrypt the document and set a password.

[0038] In one embodiment, the digital clues are used to manage the digital clue data of MBSE and display the correlation and traceability relationship of data in the model-based forward design process, specifically including: Display the relationship between requirement items on the same page; Display the relationship between requirement items and model elements on the same interface; Display the relationship between requirement items, model elements, simulation configurations, and simulation tasks on the same interface; Ability to analyze associated model elements based on any object, providing global change impact analysis.

[0039] The digital clues of the embodiment of the present invention include a digital clue front-end component and a digital clue back-end component, wherein the digital clue front-end component is used to display the traceability relationship between requirements; the traceability relationship between requirements and SysML model elements; the traceability relationship between requirements, SysML model elements, and simulation data; the traceability relationship between requirements, SysML model elements, FMU models, Modelica model elements, and simulation data; the digital clue back-end component is used to extract the data relationship between requirements; the data relationship between requirements and SysML model elements; the data relationship between requirements, SysML model elements, and simulation data; the data relationship between requirements, SysML model elements, FMU models, Modelica model elements, and simulation data.

[0040] like Fig.12 The figure shows a schematic diagram of the digital clue association analysis. The digital clues of the embodiment of the present invention automatically record the association relationship between the model elements and data of each stage of the life cycle and each professional field, and display them on the web page through Alibaba Ant Design G6X6 graphical technology. The system data layer uses OSLC (Open Services for LifecycleCollaboration) technology to generate a unique URL access address for each element. The return value complies with the RDF (Resource Description Framework) specification. Each element implements the addition, deletion, query, and modification of resources through the RestFul style interface. The specific implementation process is as follows: (1) Using the Springboot architecture, the OSLC core Jar package and Jena dependencies are introduced to read and write RDF format files. By adding oslcMessageConverter, the request format is matched to achieve RDF format output. When format=rdf, the corresponding results are processed and converted into RDF format data; (2) Refine the demand model to the item level, and generate a unique URL address for each demand item based on OSLC technology; (3) Model elements are refined to the atomic level, and each model element generates a unique URL address based on OSLC technology; (4) Refine the simulation data to the atomic level, and generate a unique URL address for each model element based on OSLC technology; (5) Use Neo4j graph database to record the relationship between elements; (6) Use the Cypher graph database query language to query the relationship between elements; (7) Use Alibaba Ant Design G6 X6 to draw graphics and show the relationship between elements.

[0041] In one embodiment, the project management module is used to manage MBSE R&D project related information, including: project PBS structure, project plan, project tasks, project members, roles and permissions, specifically including: The users in the system come from the custom users in the system, or users authenticated by the central authentication service or the unified user authentication of microservices; The project PBS structure in the system is derived from the customized PBS in the system or the PBS data integrated from the project management system; The system supports task creation and directly assigns task orders to any specified user. Task orders can be associated with requirement items and model data.

[0042] The project management module of the embodiment of the present invention includes a project management front-end component and a project management back-end component, wherein the project management front-end component is used to display the basic information of the project, including interfaces such as the project name, project responsible person, project members, project confidentiality, project engineering directory structure, and project directory file permission management; the project management back-end component is used to maintain the basic information of the project, including the project name, project responsible person, project members, project confidentiality, project engineering directory structure, and project directory file permission information. This system includes multiple domain models in the MBSE development process. In order to ensure the consistency of various domain models of complex products, the global management function of product configuration is implemented at the top level of the system. In the project management component, this function takes the product model as a management project. The model can be divided into different directories according to the profession and system. Multiple model projects can be mounted under each directory. The model project can create multiple development branches to realize the version control of the model. Users can set the branch permissions and specify the model developers of each branch. The model can also be split into multiple projects for management, and project PBS maintenance and task management can be performed.

[0043] like Fig.13As shown in the figure, a product model is decomposed into three projects, which are independent of each other and do not interact with each other during the development process. Within each project, management modes such as multi-person, multi-team, remote, offline, and version merging are carried out. A project is managed as an independent model project, and the R&D team can choose different modeling tools to implement the model design of the sub-directory. Taking a SysML model project as an example, the top-level project is decomposed into system A, system B, and system C. Each system corresponds to a different R&D team, and system A can be further divided into subsystem A, subsystem B, and subsystem C. Each system or subsystem contains multiple packages, each of which provides branch versions and member permission control functions, so as to realize parallel development of different teams at different levels, and all model elements can be centrally managed in one project, so as to realize the continuous integration of the entire project during the product design process, and finally form a SysML model of the entire complex product, and realize the construction of the entire product digital system.

[0044] As the basic organizational unit for managing data, a project provides the following functions: Provide basic information maintenance within the project, such as project name and background description; Provide project confidentiality definition to ensure data security and controllability; Provide project member management, role management, and maintain project personnel visibility; Provides project-level template, phase, view, and attribute management; Provide project-level branch management and version baseline management; Provides project-level statistics and displays various charts; Users can selectively follow project information; Organize model element information by project; Define each stage of the project and realize the status of project start, execution, archiving, etc. Provide project-level data reuse; Provide package-level member, permission, version, and branch management; Provide project-level PBS planning; Support project task management.

[0045] For example, after the administrator logs into the login interface of the Web-based MBSE collaborative R&D management system, he or she can view and maintain basic project information and model elements, perform branch management, version management, role management, and management of various models and digital clues.

[0046] (1) Branch management The project is decomposed into system A, system B, and system C. Each system corresponds to a different research unit, and system A can be further divided into subsystem A, subsystem B, and subsystem C. Each system or subsystem contains multiple packages, and each package provides branch management. Each package corresponds to a branch, and the administrator can set members, roles, and permissions based on the branch. The branch can be merged into other branches.

[0047] When an administrator creates a branch, he or she can select the branch creation source and version, and specify the branch responsible person and members. Each branch is a physical copy of the model data, and the development and submission processes between branches are isolated from each other and do not affect each other. Users can pull a certain version of the model from a branch to the local at any time. Since the development of all R&D teams is based on the same model project, each R&D team continuously changes and submits the model on their respective branches. The configuration administrator realizes the merging and synchronization between branches, and finally realizes the collaborative development of the entire product model.

[0048] (2) Version management The entire product model is managed as an independent project, and each layer of directory and each package is subject to user, team, permission and version control. This system adopts the branch management mode, each package can be used as a branch, and version control is implemented based on branches. Users can create versions and download specified versions. The configuration manager selects a directory and sets users and their permissions (R read-only, M modify, C create, D delete) through the MDK (Model Development Kits) plug-in, and implements version management of the product model through operations such as creation, execution, merging, and deletion of branch versions.

[0049] (3) Role Management The system has built-in administrators, developers, and approvers. Customize user roles and specify role permissions.

[0050] (4) Demand model management A requirement model usually refers to a description of the requirements of a system or product in the form of items, including functions, performance, appearance, etc., and can express the relationship between requirements. Requirements management solves which requirements have changed, when they changed, and by whom; which documents each requirement can be traced back to; and which components each requirement is assigned to. Performing requirements management can ensure that the requirements of the system and system elements are consistent with other expressions, analysis and output results of the system, and are consistent with project resources and progress.

[0051] The requirements model has the following basic entities and relationships.

[0052] 1) Entities include: database, project, folder, document, object, attribute, view, baseline, type, process, review, etc.; 2) Relationships include: association, inclusion, belonging to, reference, etc.

[0053] The entity relationship of the demand model uses a relational database to store the demand entities and an object storage database to store the associated files.

[0054] The database core table structure design includes: Requirement entry table, associated requirement update record table, attribute type table, item attribute table, attribute item mapping table, illegal vocabulary table, professional vocabulary table, etc.

[0055] (5) SysML model management Based on OMG's DD (Diagram Definition), a unified model data structure is provided for the system architecture model of the platform, and the model diagram of the collaborative design model of heterogeneous modeling tools is defined to make the data structure fully comply with the SysML language specification.

[0056] The DD specification ensures the consistency of the model mainly from the following two aspects: 1) Define the SysML-based diagram exchange metamodel as an extension of the DI (Diagram Interchange) package.

[0057] 2) Map the SysML-based DI metamodel instance to the model symbol DG (Diagram Graphics).

[0058] DI is called Diagram Information Exchange Consistency, which is used to ensure the consistency of diagram information when checking in / out models between different modeling tools. DG is called Diagram Graphics Consistency, and the system presents diagram information in a graphical way.

[0059] The DD architecture distinguishes graphical information, which consists of metamodel shapes and line styles defined by the SysML specification. DD does not exchange them and directly maps them to DG objects. Graphical information supported by tools or that can be operated by users, such as node positions, inflection points of connection lines, etc., is mapped to a unified model data structure DI object through conversion. When it is displayed in the view, it is first instantiated as a DG object, and then the next DI object operation is performed.

[0060] SysML models are divided into 9 types of graphics according to structure and behavior; each graphic supports a combination of multiple graphics elements; each graphic element carries a large amount of attribute information. In order to solve the problems of storage, query and multi-team collaboration of multi-model model information, the data storage mode is designed as follows: 1) Develop MDK on the modeling tool side, parse the model project into individual model elements, and parse the model element attribute information into JSON format data; 2) Create an index for each model element data and store the relationship between model elements through a relational database; 3) Use an object storage database to save JSON format data of a single model element; 4) Use the index, type, and document of the non-relational database to map models, branches, and model elements respectively.

[0061] (6) Simulation model management There are many types of simulation models, such as SysML models, Modelica models, FMU models, continuous models, discrete event models, hybrid models, etc. Taking the Modelica model as an example, this type of data is currently managed in the form of a local file library and driven by professional simulation software. This management method cannot uniformly manage model versions, and model files cannot be associated with requirements, test environments, simulation configurations, simulation tasks, simulation data, etc. Tracking. For this kind of highly cohesive and low-coupling data, it is necessary to design a general model object management mechanism to achieve the management and control of model data and the maintenance of the relationship between model data.

[0062] like Figure 4 As shown in the figure, each entity in the system is abstracted into an object, and the object properties are sorted out. Objects can inherit from each other and quickly instantiate specific business objects. Define the full life cycle model objects of forward R&D, such as simulation models, simulation data, file objects, etc. Since the amount of data is very large, and each type of data has its own unique or common attributes, the model data of each stage is uniformly defined and maintained, displayed, and the model is associated and traced, and a data object and type management configuration interface is provided for maintenance.

[0063] like Figure 5 As shown in the figure, to achieve model element-level storage, first, the model needs to be opened through the model parsing algorithm to obtain the basic information of the model elements, second, the model information needs to be persistently stored, and third, the model resource files need to be organized in RDF format and expressed in the network native language OWL, and finally human-machine readable. Due to the differences in model types and tools, different parsing algorithms need to be written for different types of models and tools, the model needs to be parsed into individual model elements, and their relationships need to be maintained in the relationship table, and finally the attributes and attribute values ​​of the model element objects need to be stored.

[0064] (6) Digital clues In view of the large amount of heterogeneous models and data generated during the R&D process of industrial products, the Open Services for Lifecycle Collaboration (OSLC) is used to solve the problem of integrating heterogeneous modeling tools and realize the association and traceability between model elements in different fields. The OSLC specification can solve the problems brought about by the integration of tools throughout the product lifecycle, realize the interaction between the underlying data of heterogeneous tools, and create large-scale and maintainable integration and links in a heterogeneous tool environment. Through the OSLC integration method, data tracking can be achieved across domains, applications, and organizations.

[0065] The core mechanism of OSLC is to treat the data generated in all tools as resources. Each resource is assigned a fixed and unique URL address, and it is stipulated that each tool must provide a unified service access entry rootService. After accessing the entry, you can see the service provider catalog serviceProviderCatalog, in which you can obtain the service provider, and then perform CRUD operations on each resource. In this way, you can establish the association between model data and make the model data interoperable. The following is the construction method of several key objects: 1. The construction of rootService includes two parts: authentication and catalog URI information. The authentication URL information can be set according to its actual request routing. The catalog URI information is set to the system parameters when the container is started, and then obtained from it when it is called; 2. The starting point for building serviceProviderCatalog is the ServiceProviderCatalogSingleton class. In addition to the static code block, the ServiceProvider is built through the initServiceProvidersFromProducts method. The built ServiceProvider will be added to the catalog. When viewing the catalog, all ServiceProvider information is displayed; 3. ServiceProvider is constructed in the initServiceProvidersFromProducts method when building the catalog in the second step. It is mainly constructed through the DigitalThreadServiceProviderFactory.createServiceProvider method, and then the oslc ServiceProviderFactory is called for construction. The main work here is annotation scanning. First, the @OslcService annotation is scanned, and then specific annotations such as @Path, @Get and @Post are scanned, and creationDialogs, creationFactories, queryCapabilities and selectionDialogs are assembled. 4. Use graph database to record the relationship between model elements; 5. Use graph database query language to quickly retrieve upstream and downstream relationships of model elements.

[0066] The specific implementation methods described above provide a detailed description of the technical solutions and beneficial effects of the present invention. It should be understood that the above is only the most preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, supplements and equivalent substitutions made within the scope of the principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A Web-based MBSE collaborative R&D management system, characterized in that: include: Demand center, used to manage the requirements generated during system development and support traceability between system models, simulation data and requirement items; Model center, used to manage model data generated during the system development process with requirements as input, including: SysML model, Modelica model, Cyphy model, FMU model; The simulation center is used to call and execute SysML models, Modelica models, and FMU models, and record simulation configurations, simulation tasks, and data generated during the simulation process; Document center, which is used to extract data from the MBSE collaborative R&D management system, automatically generate and manage various documents that meet user standards and specifications, including requirement documents, design documents, and simulation verification documents; Digital clues, used to manage MBSE digital clue data and display the correlation and traceability of data in the model-based forward design process; The project management module is used to manage MBSE R&D project related information, including: project PBS structure, project plan, project tasks, project members, roles and permissions.

2. The Web-based MBSE collaborative R&D management system according to claim 1, characterized in that: The demand center is used to manage the requirements generated during the system development process and trace the system model, simulation data and requirement items, including: Automatically initialize the project's requirement information architecture based on PBS, the requirement information architecture includes: the project's hierarchical directory, hierarchical name, file name, creator, creation time, description, and type; the requirement information architecture graphically displays the composition of the requirement document and the relationship between the documents; The requirement document includes name, type, prefix, status, responsible person, historical information, module attributes, file traceability, and access rights; The requirement document consists of requirement items, which are displayed one by one in a tabular interface. Double-click any item with the mouse to open the right area of ​​the interface and edit the requirement item, while displaying the detailed content of the requirement item. The requirement items are mainly associated in three ways: the first is to open two requirement documents in the same interface and establish a link by dragging the mouse; the second is to establish a link by checking the cells of the requirement tracking matrix in a table form; the third is to establish a link by graphically displaying the requirement tree in the Web interface; when the requirement item has a link, it is indicated by a triangle symbol, the left side indicates an incoming link, the right side indicates an outgoing link, yellow indicates that the link object has changed, and green indicates that the link object has not changed; When multiple people open the same requirement document, the online editors are displayed in the upper right corner of the requirement document editing interface, and the requirement items currently being edited by other people are displayed in a frame line; The person in charge of the requirement document selects the requirement items in the requirement document and assigns them to other requirement documents. The persons in charge of other requirement documents can receive the message and view the contents of the assigned requirement items.

3. The Web-based MBSE collaborative R&D management system according to claim 1, characterized in that: The model center is used to manage the model data generated during the system development process with requirements as input, including SysML models, Modelica models, Cyphy models, and FMU models, specifically including: By calling the API interface of the client system modeling and simulation tool, all local model data can be traversed and obtained; The model management server implements model element management and version control through a relational database, an object storage database, and a graph database. The basic information of the model object is stored in the relational database, including object ID, object name, object label, parent object, child object, and model tree structure; the attribute information of the model object is stored in the object storage database; and the relationship between model elements is stored in the graph database.

4. The Web-based MBSE collaborative R&D management system according to claim 1, characterized in that: The simulation center is used to call and execute SysML models, Modelica models, and FMU models, and record simulation configurations, simulation tasks, and data generated during the simulation process, including: Create simulation configuration for the system model selected in the model center, configure input and output parameters and simulation process parameters in the simulation configuration, and the simulation task can call and execute SysML models, Modelica models, and FMU models; A plurality of simulation tasks can be created for each of the simulation configurations, and requirement items to be verified are specified in the simulation tasks; The simulation task calls a local or cloud-based simulation engine, identifies data based on the OWL network ontology language, provides an entry for automatically executing the simulation task and analyzing simulation data, and stores and manages simulation results; Any historical simulation results can be viewed in the simulation task.

5. The Web-based MBSE collaborative R&D management system according to claim 1, characterized in that: The document center is used to extract data from the MBSE collaborative R&D management system, automatically generate and manage various documents that meet user standards and specifications, including requirement documents, design documents, and simulation verification documents, specifically including: Multiple data source management: manage each type of business model in the form of data source. Based on the model data in the output target system, the data source can be abstracted into an operable target object, which covers all input contents of the target system. Document template management: document templates are used to specify the composition of document content. Users can design document frameworks graphically, create document templates based on abstract document standards, specify document cover, directory, body, headers and footers, express output content through graphic nested formats, specify output styles, set filtering conditions, and generate tables. Users can call designed document templates to generate documents required by users through single data source and multiple data source combinations. Document generation engine, used to generate documents in word, PDF, json, and xml formats.

6. The Web-based MBSE collaborative R&D management system according to claim 1, characterized in that: The digital clue is used to manage the digital clue data of MBSE and to display the correlation and traceability relationship of data in the model-based forward design process, including: Display the relationship between requirement items on the same page; Display the relationship between requirement items and model elements on the same interface; Display the relationship between requirement items, model elements, simulation configurations, and simulation tasks on the same interface; Ability to analyze associated model elements based on any object, providing global change impact analysis.

7. The Web-based MBSE collaborative R&D management system according to claim 1, characterized in that: The project management module is used to manage MBSE R&D project related information, including: project PBS structure, project plan, project tasks, project members, roles and permissions, specifically including: The users in the system come from the custom users in the system, or users authenticated by the central authentication service or the unified user authentication of microservices; The project PBS structure in the system is derived from the customized PBS in the system or the PBS data integrated from the project management system; The system supports task creation and directly assigns task orders to any specified user. Task orders can be associated with requirement items and model data.

Images