A multi-view architecture modeling method based on metamodel and ontology

Abstract

The present invention discloses a metamodel and ontology-based architecture multi-view modeling method, comprising the following steps: 1) using the knowledge graph ontology description language OWL to describe the information system architecture metamodel; 2) establishing a mapping relationship between the DoDAF meta-metamodel and the OWL elements, and constructing an ontology representation of all metamodel types and relationship tuples of the information system architecture based on DoDAF according to the mapping relationship, thereby establishing an information system architecture metamodel ontology framework; 3) constructing an information system domain ontology based on the metamodel ontology traction, that is, an instance of the metamodel ontology, according to the metamodel ontology framework, to provide a reusable domain ontology library for information system architecture model construction; 4) utilizing the metamodel ontology framework and the domain ontology library, through the conversion of the domain ontology and architecture model data, to construct an information system architecture multi-view model with data consistency.

Description

Technical Field

[0001] The present invention relates to information system design technology, in particular to an architecture multi-view modeling method based on metamodel and ontology. Background Art

[0002] Architecture modeling is a method that uses multiple models from different perspectives to assist and standardize the design of information system architecture based on the multiple perspectives and data organization methods defined by the Architecture Framework.

[0003] Based on the requirements for modeling the architecture of large-scale platform information systems, both structured and object-oriented modeling methods can be applied. However, the modeling process of both methods requires extensive expert business and modeling experience. With the rapid development of information technology, systems composed of a large number of information systems have become large-scale, networked, and complex. Modeling using structured and object-oriented methods is limited by heavy workload, multiple architectural perspectives, and large data volumes, making it difficult to efficiently support system modeling. This method aims to propose a method that uses the architectural metamodel as a standard framework, utilizes the information system knowledge ontology and its constituent knowledge graphs through mapping and transformation, and supports the construction of multi-view models of large-scale platform information system architectures. Summary of the Invention

[0004] The technical problem to be solved by the present invention is to provide a metamodel and ontology-based architecture multi-view modeling method in view of the defects in the prior art.

[0005] The technical solution adopted by the present invention to solve the technical problem is: a metamodel and ontology-based architecture multi-view modeling method, comprising the following steps:

[0006] 1) Use the knowledge graph ontology description language (OWL) to describe the information system architecture metamodel;

[0007] First, define the class Class in the model, then define the object properties Property of the class to express the relationship between classes, and finally describe the characteristics of the object properties Property of the defined class;

[0008] 2) Establish the mapping relationship between DoDAF meta-metamodel and OWL elements, and construct the ontology representation of all metamodel types and their relationship tuples (i.e., object attributes) of DoDAF-based information system architecture based on the mapping relationship, thereby establishing the information system architecture metamodel ontology framework;

[0009] Among them, the elements of the DoDAF meta-metamodel include: type (Type), tuple (Tuple), individual (Individual);

[0010] The mapping relationship between the DoDAF meta-metamodel and the ontology description language OWL elements is as follows: the type Type in the DoDAF meta-metamodel corresponds to the class in the ontology, the individual Individual corresponds to the individual of the class, and the tuple Tuple corresponds to the attribute in the ontology;

[0011] The mapping relationship is as follows:

[0012] 2.1) Mapping of classes in OWL;

[0013] The concept of type in the DoDAF meta-metamodel is mapped to the concept of class in OWL, including individual type and power type. Tuple type is a set of tuples, which is a set of descriptions of relationships between types. Tuple type is not mapped.

[0014] OWL describes all classes in a domain based on a tree structure, where owl:Thing is set as the parent node of all classes, and other classes are established as children of this node. When creating a new class in OWL, it is simply declared as a named class. A class definition consists of a reference and a list of restrictions.

[0015] 2.2) Mapping of properties in OWL;

[0016] Describe the concept of tuple type Tuple in the DoDAF meta-metamodel as an attribute;

[0017] There are two types of properties in OWL: data properties and object properties. Data properties refer to the relationship between a class instance and non-relational data. Object properties refer to the relationship between two class instances. For example, the information exchange relationship between two radars is an object property of the radars.

[0018] 2.3) Attributes of classes in OWL;

[0019] Complete the feature description and attribute restrictions of the tuple type Tuple based on the feature description of the class attributes in OWL;

[0020] The characteristic description of an attribute is a detailed description of the characteristics of the attribute, and its purpose is to provide a powerful mechanism for enhancing the reasoning about the attribute. The characteristic description of an attribute includes transitive attributes, symmetric attributes, functional attributes, inverse function attributes, and inverse attributes.

[0021] 2.4) After the mapping is established, an ontology representation of the architecture metamodel types and their relationship tuples of interest to large-scale platform information systems is constructed, thereby establishing an ontology framework for the information system architecture metamodel, laying the foundation for data specification of the information system architecture;

[0022] 3) Based on the metamodel ontology framework, construct the information system domain ontology (i.e., the instance of the metamodel ontology) driven by the metamodel ontology, and provide a reusable domain ontology library for the construction of the information system architecture model;

[0023] 4) Using the metamodel ontology framework and domain ontology library, a multi-view model of the information system architecture with data consistency is constructed through the conversion of domain ontology and architecture model data.

[0024] Conduct static structural analysis of the system, build a high-level conceptual model, and build the metamodel's architecture view model based on the metamodel's domain ontology and using the metamodel ontology.

[0025] The beneficial effects produced by the present invention are:

[0026] By analyzing the underlying relationship between knowledge graphs and architecture view models, the present invention proposes an ontology representation technology for architecture metamodels and establishes an ontology framework for information system architecture metamodels. Then, through the construction of the metamodel ontology framework and domain ontology, it can be used to support the construction of multi-view models of large-scale platform information system architectures.

[0027] The present invention can improve the construction efficiency of the architecture model and reduce the data conflict of the architecture by constructing a domain ontology library. The authoritative knowledge graph data source composed of domain ontology can improve data reusability. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] The present invention will be further described below with reference to the accompanying drawings and embodiments, in which:

[0029] Figure 1 is a flow chart of a method according to an embodiment of the present invention;

[0030] Figure 2 This is a flowchart of the steps of the method for describing the architecture metamodel using OWL in an embodiment of the present invention;

[0031] Figure 3 It is a schematic diagram of an example of the multi-view modeling process of the architecture according to an embodiment of the present invention. DETAILED DESCRIPTION

[0032] 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 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.

[0033] like Figure 1 As shown, a metamodel and ontology-based architecture multi-view modeling method includes the following steps:

[0034] 1) Use the knowledge graph ontology description language OWL to describe the information system architecture metamodel; the steps of OWL describing the architecture metamodel are shown in Figure 2 ;

[0035] First, define the class Class in the model, then define the object property Property of the class to express the relationship between classes, and finally describe the characteristics of the defined object property Property;

[0036] 2) Establish the mapping relationship between the DoDAF meta-metamodel and the knowledge graph ontology description language OWL elements, and construct the ontology representation of all metamodel types and their relationship tuples (i.e., object attributes) of the information system architecture based on the mapping relationship, thereby establishing the information system architecture metamodel ontology framework;

[0037] Among them, the elements of the DoDAF meta-metamodel include: type (Type), tuple (Tuple), individual (Individual);

[0038] Among them, tuple refers to the relationship between things; type refers to the concept description in the ontology, which is the collection of concepts in the domain; individual refers to the instance of the class; attribute refers to the relationship between classes, classes and individuals, and individuals and individuals;

[0039] The mapping relationship between the DoDAF meta-metamodel and the ontology description language OWL elements is as follows: the type Type in the DoDAF meta-metamodel corresponds to the class in the ontology, the individual Individual corresponds to the individual of the class, and the tuple Tuple corresponds to the attribute in the ontology; the mapping relationship is as follows:

[0040] 2.1) Mapping of classes in OWL;

[0041] Describe the concept of Type in the DoDAF meta-metamodel as a class concept, which includes individual types and power types;

[0042] The concept of type expressed in the DoDAF meta-metamodel corresponds to the concept of class in OWL, with the exception of tuple types, which, as a collection of tuples, are actually a collection of descriptions of relationships between types. OWL describes all classes in a domain based on a tree structure, with owl:Thing as the parent node for all classes, and other classes as children of this node. When creating a new class in OWL, simply declare it as a named class. A class definition consists of a list of references and restrictions.

[0043] 2.2) Mapping of properties in OWL;

[0044] Describe the concept of tuple type Tuple in the DoDAF meta-metamodel as an attribute;

[0045] There are two types of properties in OWL: data properties and object properties. Data properties refer to the relationship between a class instance and non-relational data, for example, the model name of a missile is a data property of the missile; while object properties refer to the relationship between two class instances, for example, the information exchange relationship between two radars is an object property of the radars.

[0046] 2.3) Define attribute characteristics;

[0047] Complete the feature description and attribute restrictions of the tuple type Tuple based on the feature description of the class attributes in OWL;

[0048] Among them, the characteristic description of the attribute includes transitive attribute, symmetric attribute, functional attribute, inverse function attribute and inverse attribute;

[0049] The characteristic description of an attribute is a detailed description of the characteristics of the attribute, and its purpose is to provide a powerful mechanism for enhancing the reasoning about the attribute;

[0050] According to the mapping relationship between DoDAF meta-metamodel and OWL elements, the ontology representation of all metamodel types and their relationship tuples (i.e., object attributes) of the information system architecture based on DoDAF is constructed. The ontology classes formed are: Capability; OperationalPerformer; OperationalActivity; Resource; System; Function; InformationElement; DataElement; Rule; MeasurementSet;

[0051] Its object attributes are: IsCapableToPerform / From; MapsToCapability; OperationalControlFlow / From; OperationalObjectFlow / From; PartWholeType; WholePartType; ResourceExchange; OperationalExchange / From.

[0052] 3) Based on the metamodel ontology framework, construct the information system domain ontology (i.e., the instance of the metamodel ontology) driven by the metamodel ontology, and provide a reusable domain ontology library for the construction of the information system architecture model;

[0053] The ontology building platform is used to build the information system domain ontology and establish an instance of the metamodel ontology class, namely the information system domain ontology.

[0054] Focusing on the key areas of interest in large-scale platform information system architecture, including capabilities, actors, activities, information, resources, rules, and outcomes, a corresponding domain ontology is constructed for each metamodel. For example, capability classes include detection capabilities, command and control capabilities, and firepower strike capabilities; activity classes include search activities, tracking activities, decision-making activities, and strike activities. Based on this foundation, relationships between metamodel ontology classes such as capabilities, activities, and resources are constructed based on ontology object attributes. For example, if the actor is radar and the activity is search, then the relationship between radar and search is the object property IsCapableToPerform.

[0055] This can provide a reusable domain ontology library for the construction of large-scale platform information system architecture models.

[0056] 4) Using the metamodel ontology framework and domain ontology library, a multi-view model of the information system architecture with data consistency is constructed through the conversion of domain ontology and architecture model data.

[0057] Using the meta-model ontology framework and domain ontology library, we build an ontology-driven architecture multi-view model. Through the conversion of domain ontology in the form of knowledge graph and architecture model data, we build an information system architecture multi-view model with data consistency, such as Figure 3 shown.

[0058] First, we conduct a static structural analysis of the system and build a high-level conceptual model (OV-1). Based on the built capabilities (Capability), executors (OperationalPerformer), operational activities (OperationalActivity), information / data (InformationElement / DataE-

[0059] lement) and other meta-models to build the capability decomposition model (CV-2), operational resource flow description (OV-2), operational activity model (OV-5b), and data information (DIV-1, DIV-2) models for interaction between operational activities.

[0060] At the same time, based on instances of meta-models such as Resource (Resource / System), Function (Function), and Information / Data (InformationElement / DataElement), we construct models for the System Interface Description (SV-1), System Functionality Description (SV-4), System Resource Flow Description (SV-2), and Data Information for Inter-resource Interactions (DIV-3). Furthermore, traceability matrices such as the Capability-Operational Activity Traceability Matrix (CV-6) and the Operational Activity-Function Traceability Matrix (SV-5b) are established, forming a core supporting architecture view model.

[0061] For example, based on the domain ontology of combat capability, combat activity and combat resource of a large platform information system and its object attributes in the domain ontology library, architecture view models such as capability decomposition model (CV-2), combat activity model (OV-5b) and combat resource flow description (SV-2) can be constructed.

[0062] On this basis, further dynamic behavior analysis of the system can be conducted as needed. Focusing on various activities, interactions, and decision-making processes within the operational architecture, an operational rule model (OV-6a) (based on instances of the rule metamodel), an operational state transition model (OV-6b), and an operational event trajectory description (OV-6c) can be established. Furthermore, a system rule model (SV-10a), a system state transition model (SV-10b), and a system trajectory description (SV-10c) can be developed. The OV-6a model is built on the operational activity model (OV-5b) and the data and information (DIV-1 / DIV-2) models. The OV-6b model is constructed for each operational node, while the OV-6c model describes the event trajectories between operational nodes. The SV-10a model is built on the system function flow model and the data and information (DIV-3) model. The SV-10b model is constructed for each operational resource, while the SV-10c model describes the event trajectories between operational resources.

[0063] The present invention utilizes the architecture framework metamodel theory and ontology construction method to propose an information system architecture multi-view modeling method of "metamodel → metamodel ontology → domain ontology (knowledge graph) → architecture data → architecture model". By constructing a domain ontology library in the form of a knowledge graph, the construction efficiency of the architecture model is improved and the data conflict of the architecture is reduced.

[0064] It should be understood that those skilled in the art can make improvements or changes based on the above description, and all such improvements and changes should fall within the scope of protection of the appended claims of the present invention.

Claims

1. A metamodel and ontology-based architecture multi-view modeling method, characterized by: The following steps are involved: 1) Use the knowledge graph ontology description language OWL to describe the information system architecture metamodel; First, define the class Class in the information system architecture metamodel; Then define the object property Property of the class to represent the relationship between classes; Finally, describe the properties of the object properties of the defined class; 2) Establish the mapping relationship between DoDAF meta-metamodel and OWL elements, and construct the ontology representation of all metamodel types and relationship tuples of DoDAF-based information system architecture based on the mapping relationship, so as to establish the information system architecture metamodel ontology framework; Among them, the elements of the DoDAF meta-metamodel include: Type, Tuple, Individual; The mapping principle between the DoDAF meta-metamodel and the ontology description language OWL is as follows: the type in the DoDAF meta-metamodel corresponds to the class in the ontology, the individual corresponds to the individual of the class, and the tuple corresponds to the attribute in the ontology; After the mapping is established, the ontology representation of the architecture metamodel types and their relationship tuples of the large platform information system is constructed, thereby establishing the ontology framework of the information system architecture metamodel; 3) Based on the metamodel ontology framework, an information system domain ontology based on the metamodel ontology is constructed, i.e., an instance of the metamodel ontology, to provide a reusable domain ontology library for the construction of information system architecture models; 4) Using the metamodel ontology framework and domain ontology library, a multi-view model of the information system architecture with data consistency is constructed through the conversion of domain ontology and architecture model data.

2. The method for multi-view architecture modeling based on metamodel and ontology according to claim 1, characterized in that: In step 2), the mapping relationship between the DoDAF meta-metamodel and the ontology description language OWL elements is as follows: 2.1) Mapping of classes in OWL; The concept of type in the DoDAF meta-metamodel is mapped to the concept of class in OWL, including individual type and power type. Tuple type is a set of tuples, which is a set of descriptions of relationships between types. Tuple type is not mapped. OWL describes all classes in a domain based on a tree structure, where owl:Thing is set as the parent node of all classes, and other classes are established as children of this node. When creating a new class in OWL, it is simply declared as a named class. A class definition consists of a reference and a list of restrictions. 2.2) Mapping of properties in OWL; Map the concept of tuple type Tuple in DoDAF meta-metamodel to attributes in OWL; There are two types of properties in OWL: data properties and object properties. Data properties refer to the relationship between a class instance and non-relational data; object properties refer to the relationship between two class instances. 2.3) Attributes of classes in OWL; Complete the feature description and attribute restrictions of the tuple type Tuple based on the feature description of the class attributes in OWL; Among them, the characteristic description of class attributes in OWL is a detailed description of the characteristics of the attributes, and its purpose is to provide a powerful mechanism for enhancing the reasoning about the attributes; the characteristic description of attributes includes transitive attributes, symmetric attributes, functional attributes, inverse function attributes and inverse attributes.

3. An electronic device, characterized in that: include: one or more processors; as well as a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors are caused to perform the method according to claim 1 or 2.

4. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to claim 1 or 2 is implemented.

Images