A ship information system MBSE metamodel design method
By designing the hierarchical framework of the MBSE metamodel for ship information systems and constructing the corresponding relationship with the SysML language, the problem of inconsistent modeling in SysML in specific domains was solved, and efficient and standardized modeling and model integration of ship information systems were achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CHINA SHIP DEV & DESIGN CENT
- Filing Date
- 2024-11-26
- Publication Date
- 2026-06-05
AI Technical Summary
The existing SysML language lacks a unified modeling expression when facing specific domains, which leads to inconsistent descriptions of specific concepts by different design teams, resulting in difficulties in design understanding and model integration.
Design a hierarchical framework for the MBSE metamodel of a ship information system, establish the correspondence between specific design elements of the ship information system and the SysML language, and construct it layer by layer through conceptual data model, logical data model and physical data model to form a standard document of the system MBSE metamodel, and standardize the granularity and interaction relationship of model elements at each level.
The standardized definition of the MBSE metamodel for ship information systems has been achieved, which improves design efficiency, supports the modeling needs of multiple projects and teams, and ensures the consistency of model integration and the clarity of semantic relationships.
Smart Images
Figure CN122154055A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to ship information systems, and more particularly to a method for designing a ship information system's MBSE metamodel. Background Technology
[0002] The digital transformation of ship information system development leverages digital technologies, relies on digital models to standardize the transfer of design status at different stages, and enables early model-based verification, thereby improving R&D efficiency and quality. In the process of designing and verifying ship information systems using digital technologies, MBSE (Model-based System Engineering) techniques are required for system architecture model construction and model-based architecture integration verification. The MBSE metamodel, as the underlying data foundation for modeling, plays a crucial supporting role in the modeling process.
[0003] Currently, the common approach to system architecture design and modeling based on MBSE technology is to use a unified modeling language such as SysML (Systems Modeling Language) for modeling representation of system designs. However, since SysML is essentially a unified modeling expression for various domains, its universality needs to be further defined for specific domains. In this process, relying on designer customization often leads to inconsistencies in the description of specific concepts across different projects and design teams. For example, the "Block" in SysML can be used to describe all "elements" during modeling; it can represent the entire system, a subsystem, a piece of software, a type of matter, etc. However, at different stages of product development, it may be necessary to describe different types and levels of elements, such as material elements and energy elements, separately from the conceptual logic layer and the physical entity layer. If all elements are modeled using the same meta-concept, it can easily cause difficulties in understanding for designers and make it difficult to classify element models at different levels during model integration.
[0004] The MBSE metamodel refers to a model obtained by abstracting and modeling based on the MBSE model. In other words, the MBSE metamodel itself is highly abstract, representing a higher level of abstraction than the system's MBSE model, and is expressed as an abstract set of common and fundamental elements. Establishing a MBSE metamodel specific to the ship information system domain involves creating a set of MBSE metamodels representing common and fundamental elements of the ship information system domain through standardized definitions tailored to the professional domain and business characteristics. This simplifies the process of designers defining modeling languages, allowing system designers to focus more on system design rather than defining the model language. When modeling the MBSE architecture of a ship information system, the standard metamodel file can be loaded each time a new project is created, enabling rapid access to the system metamodel, saving on the standardized definition process of fundamental elements, avoiding redundant definitions, improving development efficiency, and meeting the needs of multiple projects and teams for large-scale modeling. Summary of the Invention
[0005] The technical problem to be solved by the present invention is to provide a method for designing a meta-model of a ship information system (MBSE) to address the deficiencies in the prior art.
[0006] The technical solution adopted by this invention to solve its technical problem is: a method for designing a ship information system MBSE metamodel, comprising the following steps: 1) Design the hierarchical framework of the MBSE metamodel for ship information systems; The ship information system MBSE meta-model hierarchical framework is a three-level ship information system MBSE meta-model, ship information system basic model, and ship information system engineering model. The ship information system MBSE metamodel includes the elements contained in the system architecture and their internal relationships. The ship information system MBSE metamodel does not represent specific model information. The ship information system basic model is a reusable and reusable basic model for information systems of various ship types. The ship information system basic model represents the common information of various ship types. The basic model of a ship information system is obtained by instantiating the ship information system MBSE metamodel, or by combining multiple ship information system MBSE metamodels after instantiation. Ship information system engineering models are design requirement models, functional models, performance models, and physical models developed to meet the needs of ship development and production, representing specific information for each ship model. Standardize the granularity and interaction relationships of model elements at each level; 2) Establish the correspondence between specific design elements of the ship information system and the SysML language specification, and form a standard document of the system MBSE metamodel; Among these, specific design elements represent high-level concepts in the field of ship information systems; the process is as follows: 2.1) Abstractly describe specific elements in the field of ship information systems, and clarify the basic elements, attributes, and relationships within the field; 2.2) Using a method that constructs the data model layer by layer, consisting of a conceptual data model, a logical data model, and a physical data model, the identification of specific design elements in the field of ship information systems is completed; During the conceptual data model construction process, identify and abstract high-level concepts in the field of ship information systems and the relationships between these concepts; The high-level concepts of ship information systems include: ship information system design requirements, ship information system design functions, ship information system design performance, and physical configuration. Conceptual data models can be represented in various forms, including natural language, taxonomy, tables, and graphical modeling languages. The process of constructing a conceptual data model includes: The inputs to the conceptual data model are design documents, databases, knowledge bases, and dictionaries; The input is preprocessed to generate a preprocessed result set; Concept extraction and domain identification are performed on the input to generate conceptual terms. Extract concepts and relationships from the input to generate a set of concepts and relationships; The generated process results, including the preprocessed result set, conceptual terms, and concept and relation set, are fused together to finally output a conceptual data model. In the process of constructing the logical data model, the data elements in the conceptual data model are used as inputs, and conceptual data analysis, element type and attribute definition, and element feature parameter configuration are performed in sequence. The final output is the logical data model. In the process of constructing the logical data model, the element type and attribute definition use a lightweight extension method. Based on three core extension mechanisms: category templates (Stereotype), tag values (tags), and constraints (constraints), the corresponding SysML metamodel is constructed on the SysML software tool. The process of constructing a logical data model is as follows: The design input is a conceptual data model, which is then processed sequentially through conceptual data analysis, element type and attribute definition, and element feature parameter configuration. The final output is a logical data model. In the construction of physical data models, the MBSE metamodel of the ship information system is managed through database construction. The construction process of the physical data model is as follows: based on the selected database, define physical exchange specifications for various logical elements in the logical data model, and provide database management and execution support; 3) Design of ship information systems based on the MBSE meta-model; During the data analysis phase, based on the purpose and requirements of the system architecture design, and with the support of the meta-model, the models to be developed are selected. The models to be developed include: design requirement model, functional architecture model, logical architecture model, and physical architecture model. In the data generation phase, based on the determined model and modeling method to be developed, system architecture elements are collected, including the design or reuse of system architecture elements. In the data presentation phase, the system architecture design results are organized and presented according to the application scenarios and the users of the system.
[0007] The beneficial effects of this invention are: This invention proposes a metamodel design method for ship information systems (MBSE). By abstracting the common and variable features in ship information system design to the metamodel layer, the MBSE metamodel definition of the ship information system is implemented based on the SysML extensibility mechanism, forming a standard document of the system MBSE metamodel. This enables the effective use of the metamodel in the ship information system modeling process, and ultimately achieves standardization and consistency of the underlying models of each view at the element and semantic relationship levels. Attached Figure Description
[0008] The present invention will be further described below with reference to the accompanying drawings and embodiments. In the accompanying drawings: Figure 1 This is a flowchart of a method according to an embodiment of the present invention; Figure 2 This is a design principle diagram of an embodiment of the present invention; Figure 3 This is a flowchart of the method for constructing a conceptual data model according to an embodiment of the present invention; Figure 4 This is a flowchart of the method for constructing a logical data model according to an embodiment of the present invention; Figure 5 This is a high-level conceptual diagram of a ship information system according to an embodiment of the present invention; Figure 6 This is a schematic diagram showing the correspondence between specific design elements of the ship information system and SysML modeling elements in an embodiment of the present invention. Detailed Implementation
[0009] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.
[0010] like Figure 1 and Figure 2 As shown, a method for designing a meta-model of a ship information system (MBSE) includes the following steps: 1) Design the hierarchical framework of the MBSE metamodel for ship information systems, and standardize the granularity and interaction relationships of model elements at each level of the “MBSE metamodel for ship information systems”, “basic model for ship information systems”, and “engineering model for ship information systems”. The ship information system MBSE metamodel hierarchical framework consists of three levels: the ship information system MBSE metamodel, the ship information system basic model, and the ship information system engineering model. The MBSE metamodel specification for ship information systems includes the elements and their internal relationships within the system architecture, but does not represent specific model information. Taking the system architecture element of "system components" as an example, the domain metamodel can define five metamodels based on the needs of the ship's information system: "System," "Subsystem," "Equipment," "Hardware," and "Software." Each metamodel can be set with standardized basic attributes such as "ID," "Description," "Name," "Quantity," "Dimensions," and "Weight," as well as relationships such as "Inclusion" and "Deployment." The process of modeling various view models describing the system architecture is the process of instantiating the above metamodels. Depending on the degree of instantiation, a basic system model or a specific model engineering model can be formed.
[0011] The basic model of a ship information system is a basic model that can be reused in various ship information systems, representing common information of the ship type.
[0012] Taking the "system component module" as an example of system architecture, the basic system model, based on the common needs of information systems for various ship platforms, can define basic models such as "inertial navigation equipment" and "maneuvering decision-making and command software," representing the basic information and relationships of the corresponding hardware and software devices. The basic system model consists of highly versatile, repetitive, technologically mature, and relatively unchanging components in various ship information systems. Rapid migration and reuse of this type of basic model can significantly improve development efficiency.
[0013] The basic system model can be obtained by instantiating the ship information system MBSE meta-model, or by combining the instantiation of multiple ship information system MBSE meta-models. In most cases, it is not necessary to develop a separate basic system model. In the system architecture design of various models, a basic system model library / set can be gradually built by accumulating and refining common elements.
[0014] For example, a model engineering model is a design requirement model, functional model, performance model, and physical model developed to meet the development needs of a specific model, representing model-specific information. Similarly, taking the system architecture element of "system component modules" as an example, a model engineering model, based on the development needs of the ship's information system for that model, can establish a standardized configuration component model by instantiating the domain meta-model. Alternatively, it can quickly model some "used" hardware and software equipment by reusing the system's basic model. Since both the newly created model and the reused basic model are based on the instantiation of the ship's information system's MBSE meta-model, model integration and information sharing can be carried out more effectively based on the same semantic definitions and relational descriptions. Furthermore, during the modeling process for specific models, common elements should be continuously extracted to form corresponding system basic models, constantly expanding the system basic model library / set.
[0015] Granularity and interaction relationships of model elements at each level 2) Establish the correspondence between specific design elements of ship information systems and SysML language specifications; Among these, specific design elements represent high-level concepts in the field of ship information systems; the process is as follows: 2.1) Abstractly describe specific elements in the field of ship information systems, and clarify the basic elements, attributes, and relationships within the field; 2.2) Using a method that constructs the data model layer by layer, consisting of a conceptual data model, a logical data model, and a physical data model, the identification of specific design elements in the field of ship information systems is completed; During the conceptual data model construction process, high-level concepts in the field of ship information systems and the relationships between these concepts are identified and abstracted. High-level concepts of ship information systems include: ship information system design requirements, ship information system design functions, ship information system design performance, and physical configuration. The construction of a conceptual data model should comprehensively consider all data sources related to the field of ship information systems, thoroughly sort out the data elements in these data sources, extract common concepts and the relationships between concepts, and the conceptual data model can be presented in any form according to the preferences of different modelers, such as natural language, taxonomy, tables and graphical modeling languages.
[0016] The process of constructing a conceptual data model is as follows: Figure 3 As shown, it includes: The inputs to the conceptual data model are design documents, databases, knowledge bases, and dictionaries; The input is preprocessed to generate a preprocessed result set; Concept extraction and domain identification are performed on the input to generate conceptual terms. Extract concepts and relationships from the input to generate a set of concepts and relationships; The generated process results, including the preprocessed result set, conceptual terms, and concept and relation set, are fused together to finally output a conceptual data model. In the process of constructing the logical data model, the data elements in the conceptual data model are used as inputs, and conceptual data analysis, element type and attribute definition, and element feature parameter configuration are performed in sequence. The final output is the logical data model. In the process of constructing the logical data model, the element type and attribute definition use a lightweight extension method. Based on three core extension mechanisms: category templates (Stereotype), tag values (tags), and constraints (constraints), the corresponding SysML metamodel is constructed on the SysML software tool. A logical data model is the explicit and formalized representation of a conceptual data model. It takes data elements from the conceptual data model as input and uses effective data analysis methods and tools to map these data elements to concepts in the upper-level ontology in a semantically clear form. Then, it organizes and stores the meta-model data using a specific modeling language. The construction process of a logical data model is as follows: Figure 4 As shown, the design input is the conceptual data model output from the previous stage. The design process is as follows: conceptual data analysis, element type and attribute definition, element feature parameter configuration, and the final output is the logical data model. In the construction of physical data models, the MBSE metamodel of the ship information system is managed through database construction. The physical data model defines physical exchange specifications for various logical elements and provides data management and execution support such as databases. The construction method and process of the physical data model can be defined according to the selected database. Since database technology is relatively mature, this intellectual property does not impose mandatory constraints on the method and process of constructing the physical data model.
[0017] 3) Design of ship information systems based on the MBSE meta-model; During the data analysis phase, based on the purpose (background demonstration, model design, concept demonstration, etc.) and requirements (system function analysis, comparison and optimization of multiple schemes for system configuration, etc.), with the support of the meta-model, the model to be developed (design requirement model, functional architecture model, logical architecture model, physical architecture model) can be quickly selected. Furthermore, as needed, new modeling methods can be customized with the support of the ship information system MBSE meta-model. During the data generation phase, based on the determined model and modeling method to be developed, system architecture elements are collected, including the design or reuse of system architecture elements. In this process, priority should be given to reusing models or model elements in the ship information system basic model library, followed by instantiation based on meta-models, and finally customized development based on general modeling languages to ensure that the model expression and underlying data semantics in the system architecture model are standardized. During the data presentation phase, the system architecture design results are organized and presented in a targeted manner according to different application scenarios and personnel. For example, when reporting the system architecture design scheme to the headquarters, the main focus is on presenting the block definition views representing the decomposition of system functions, as well as the activity diagrams and sequence diagrams representing the logical relationships of the system's operation at each stage. When issuing design requirements to subsystem / equipment units, the target audience is the technical personnel of the subsystem / equipment units, and the main focus is on presenting the internal module relationship diagrams and sequence diagrams related to that subsystem / equipment in the system architecture design results.
[0018] An application example: Ship information system design; (1) Review of specific design elements of ship information systems; Ship information system design involves four levels: design requirements, functionality, performance, and physical aspects. Each level contains some basic concepts, and these concepts are interconnected. By abstracting a series of concepts, we can summarize the high-level conceptual categories and intuitive meanings of ship information systems, such as... Figure 5 As shown.
[0019] (2) The correspondence between specific design elements of the ship information system and SysML modeling elements; Based on the identification and analysis of specific design elements of ship information systems, taking design requirements and configuration components as examples, and drawing upon the learning and understanding of the SysML modeling language, a correspondence between specific design elements and SysML language specifications is established, such as... Figure 6 As shown, it supports the construction of logical data models.
[0020] (3) Example of MBSE metamodel construction for ship information systems; Category 1: Design Requirements; Expanded to 9 categories: mission and tasks, functional requirements, performance requirements, integration interface requirements, general quality characteristics requirements, testing and verification requirements, usage constraints, independent controllability requirements, and economic requirements.
[0021] There are 12 attributes that can be set: ID, description, validity (valid / invalid), basis for the existence of the requirement (reason, assumption, design constraints, relationship), expected time to meet the requirement, requirement priority, requirement confirmation status, owner (proposer, writer, manager, change controller), verification method, verification leader, verification level (system level, subsystem level, unit level), and verification status. Supported relationship settings: Traceability (parent requirement, child requirement, sibling requirement, verification result (referring to verified items, documents, etc.); Category Two: Component Modules; It has been expanded to five categories: system, subsystem, device, hardware, and software.
[0022] Five attributes can be set: ID, description, name, quantity, dimensions, and weight.
[0023] Supported relationships to be set: Include, Deploy.
[0024] Category 3: Interfaces (Ports) It has been expanded to five categories: network, analog, electricity, water, and gas.
[0025] There are two attributes that can be set: ID and bandwidth.
[0026] Category 4: Interactive Items It can be expanded into three categories: matter, energy, and signal.
[0027] There are two attributes that can be set: ID and content description.
[0028] (4) Construct a ship information system.
[0029] It should be understood that those skilled in the art can make improvements or modifications based on the above description, and all such improvements and modifications should fall within the protection scope of the appended claims.
Claims
1. A method for designing a meta-model (MBSE) for a ship information system, characterized in that, Includes the following steps: 1) Design the hierarchical framework of the MBSE metamodel for ship information systems; The ship information system MBSE meta-model hierarchical framework is a three-level ship information system MBSE meta-model, ship information system basic model, and ship information system engineering model. The ship information system MBSE metamodel includes the elements contained in the system architecture and their internal relationships. The ship information system MBSE metamodel does not represent specific model information. The ship information system basic model is a reusable and reusable basic model for information systems of various ship types. The ship information system basic model represents the common information of various ship types. The basic model of a ship information system is obtained by instantiating the ship information system MBSE metamodel, or by combining multiple ship information system MBSE metamodels after instantiation. Ship information system engineering models are design requirement models, functional models, performance models, and physical models developed to meet the needs of ship development and production, representing specific information for each ship model. Standardize the granularity and interaction relationships of model elements at each level; 2) Establish the correspondence between specific design elements of the ship information system and the SysML language specification, and form a standard document of the system MBSE metamodel; Among them, specific design elements are high-level concepts in the field of ship information systems; 3) Design of ship information systems based on MBSE metamodel.
2. The MBSE metamodel design method for ship information systems according to claim 1, characterized in that, The process of establishing the correspondence between specific design elements of the ship information system and the SysML language specification is as follows: 2.1) Abstractly describe specific elements in the field of ship information systems, and determine the basic elements, attributes, and relationships within the field; 2.2) By constructing the data model layer by layer according to the three levels of conceptual data model, logical data model and physical data model, the identification of specific design elements in the field of ship information system is completed; During the conceptual data model construction process, identify and abstract high-level concepts in the field of ship information systems and the relationships between these concepts; The high-level concepts of ship information systems include: ship information system design requirements, ship information system design functions, ship information system design performance, and physical configuration. In the process of constructing the logical data model, the data elements in the conceptual data model are used as inputs, and conceptual data analysis, element type and attribute definition, and element feature parameter configuration are performed in sequence. The final output is the logical data model. During the construction of the logical data model, the element type and attribute definition use a lightweight extension method. Based on three extension mechanisms: category templates, label values, and constraints, the corresponding SysML metamodel is constructed on the SysML software tool. In the construction of the physical data model, the MBSE metamodel of the ship information system is managed through database construction.
3. The MBSE metamodel design method for ship information systems according to claim 2, characterized in that, In step 2.2), the method for constructing the conceptual data model includes: Obtain inputs for the conceptual data model, including design documents, databases, knowledge bases, and dictionaries; The input is preprocessed to generate a preprocessed result set; Concept extraction and domain identification are performed on the input to generate conceptual terms. Extract concepts and relationships from the input to generate a set of concepts and relationships; The generated process results, including the preprocessed result set, conceptual terms, and concept and relation sets, are fused together to finally output a conceptual data model.
4. The MBSE metamodel design method for ship information systems according to claim 2, characterized in that, In step 2.2), the method flow for constructing the logical data model is as follows: The design takes a conceptual data model as input, performs conceptual data analysis, defines element types and attributes, configures element feature parameters, and finally outputs a logical data model.
5. The MBSE metamodel design method for ship information systems according to claim 2 or 4, characterized in that, In step 2.2), the conceptual data model can be represented in the form of natural language, taxonomy, tables, and graphical modeling languages.
6. The MBSE metamodel design method for ship information systems according to claim 2, characterized in that, In step 2.2), the physical data model construction method is as follows: based on the selected database, define physical exchange specifications for various logical elements in the logical data model, and provide database management and execution support.
7. The MBSE metamodel design method for ship information systems according to claim 1, characterized in that, In step 3), the ship information system is designed based on the MBSE metamodel; including: During the data analysis phase, based on the purpose and requirements of the system architecture design, and with the support of the meta-model, the models to be developed are selected. The models to be developed include: design requirement model, functional architecture model, logical architecture model, and physical architecture model. In the data generation phase, based on the determined model and modeling method to be developed, system architecture elements are collected, including the design or reuse of system architecture elements. In the data presentation phase, the system architecture design results are organized and presented according to the application scenarios and the users of the system.
8. An electronic device, characterized in that, include: One or more processors; as well as Storage device for storing one or more programs. Wherein, when the one or more programs are executed by the one or more processors, the one or more processors perform the method according to any one of claims 1 to 7.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method described in any one of claims 1 to 7.