Architecture multi-view modeling method based on meta-model and ontology

Abstract

The invention discloses an architecture multi-view modeling method based on a meta-model and an ontology. The method comprises the following steps: 1) describing an information system architecture meta-model by using a knowledge graph ontology description language (OWL); 2) establishing a mapping relationship between the DoDAF meta-meta model and the OWL element, and constructing all meta-model types of the DoDAF-based information system architecture and ontology representation of a relationship tuple according to the mapping relationship, thereby establishing an ontology framework of the meta-model of the information system architecture; 3) according to the meta-model ontology framework, constructing an information system domain ontology based on meta-model ontology traction, namely an instance of the meta-model ontology, and providing a reusable domain ontology library for construction of an information system architecture model; and 4) constructing an information system architecture multi-view model with data consistency by utilizing the meta-model ontology framework and the domain ontology library through conversion of domain ontology and architecture model data.

Description

Technical Field

[0001] The present invention relates to information system design technology, and in particular to a metamodel and ontology-based architecture multi-view modeling method. 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] According to the requirements of large-scale platform information system architecture modeling, structured modeling methods and object-oriented modeling methods can be applied. However, the modeling process of both methods requires a lot of expert business experience and modeling experience. With the rapid development of information technology, the system composed of a large number of information systems has the characteristics of scale, networking, and complexity. Modeling using structured and object-oriented methods has the limitations of heavy workload, multiple architecture perspectives, and large data volume, making it difficult to efficiently support system modeling. This method aims to propose a method that uses the architecture metamodel as a normative framework, uses the information system knowledge ontology and its knowledge graph to support the construction of a multi-view model of the architecture of a large-scale platform information system. 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 method for multi-view modeling of an architecture based on a metamodel and an ontology, 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 property Property of the class to express the relationship between classes, and finally describe the characteristics of the object property 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, so as to establish the ontology framework of information system architecture metamodel;

[0009] Among them, the elements of 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 corresponds to the concept of Class in OWL, which includes individual type and power type. Tuple type is a set of tuples, which is a set of descriptions of the relationship between types. Tuple type does not correspond.

[0014] OWL's description of all classes in a domain is based on a tree structure, where owl:Thing is set as the parent node of all classes, and other classes are established as child nodes of this node. When creating a new class in OWL, it only needs to be declared as a named class. The definition of a class consists of a reference and a restriction list.

[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 class instances and non-relational data. Object properties refer to the relationship between two class instances. For example, the information exchange relationship between two radars is the radar's object property.

[0018] 2.3) Attributes of classes in OWL;

[0019] Complete the feature description and attribute restrictions of the tuple type Tuple according to 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 the attribute to enhance the reasoning of the attribute; the characteristic description of the attribute includes transitive attributes, symmetric attributes, functional attributes, inverse function attributes and inverse attributes;

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

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

[0023] 4) Utilize the metamodel ontology framework and domain ontology library to build a multi-view model of information system architecture with data consistency 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 architecture view model of the metamodel based on the domain ontology of the metamodel and using the metamodel ontology.

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

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

[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 method flow chart of an embodiment of the present invention;

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

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

[0032] In order to make the purpose, technical solution 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 used 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, so as to establish the information system architecture metamodel ontology framework;

[0037] Among them, the elements of 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 a collection of concepts in the field; 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 by the DoDAF meta-metamodel corresponds to the concept of class in OWL, except for the tuple type, because the tuple type, as a collection of tuples, is actually a collection of descriptions of the relationships between types. OWL's description of all classes in the domain is based on a tree structure, in which owl:Thing is set as the parent node of all classes, and other classes are established as child nodes of this node. When creating a new class in OWL, it only needs to be declared as a named class. The definition of a class consists of a reference and a restriction list.

[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 class instances and non-relational data, such as the model name of a missile is the data property of the missile. Object properties refer to the relationship between two class instances, such as the information exchange relationship between two radars is the object property of the radar.

[0046] 2.3) Define attribute characteristics;

[0047] Complete the feature description and attribute restrictions of the tuple type Tuple according to 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 DoDAF information system architecture 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) According to the metamodel ontology framework, construct the information system domain ontology (i.e., the instance of the metamodel ontology) based on the metamodel ontology, and provide a reusable domain ontology library for the information system architecture model construction;

[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 focus of the large-scale platform information system architecture, including capabilities, executors, activities, information, resources, rules, results, etc., for each meta-model, a corresponding domain ontology is constructed. For example, the capability class includes detection capability, command and control capability, and firepower strike capability; the activity class includes search activity, tracking activity, decision-making activity, and strike activity. On this basis, according to the ontology object attributes, the relationship between the meta-model ontology classes such as capabilities, activities, and resources is constructed. For example, if the executor is a radar and the activity is a search activity, then the relationship between the radar and the search activity is the object attribute IsCapableToPerform.

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

[0056] 4) Utilize the metamodel ontology framework and domain ontology library to build a multi-view model of information system architecture with data consistency through the conversion of domain ontology and architecture model data.

[0057] Using the metamodel 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 capabilities (Capability), executors (OperationalPerformer), operational activities (OperationalActivity), information / data (InformationElement / DataE-

[0059] The domain instances of meta-models such as Element are used to construct 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 the instances of meta-models such as Resource / System, Function, and InformationElement / DataElement, the system interface description (SV-1), system functional description (SV-4) model, system resource flow description (SV-2), and data information (DIV-3) model for interaction between resources are constructed. At the same time, traceability matrices such as Capability-Combat Activity Traceability Matrix (CV-6) and Combat Activity-Function Traceability Matrix (SV-5b) are established to form a core supporting architecture view model.

[0061] For example, based on the domain ontology of the 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, the dynamic behavior analysis of the system can be further carried out as needed. For various activities, interactions and decision-making processes in the combat system structure, the combat rule model (OV-6a) (based on the instance of the rule metamodel), the combat state transition model (OV-6b), the combat event trajectory description (OV-6c), as well as the system rule model (SV-10a), the system state transition model (SV-10b) and the system trajectory description (SV-10c) can be established. Among them, the OV-6a model is established on the basis of the combat activity model (OV-5b) and the data information (DIV-1 / DIV-2) model, the OV-6b model is constructed for each combat node one by one, and the OV-6c model establishes the event trajectory description between combat nodes. The SV-10a is established on the basis of the system function flow model and the data information (DIV-3) model, the SV-10b model is constructed for each combat resource one by one, and the SV-10c establishes the event trajectory description between combat resources.

[0063] The present invention utilizes the architecture framework metamodel theory and ontology construction method, and proposes 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 these improvements and changes should fall within the scope of protection of the appended claims of the present invention.

Claims

1. A method for multi-view modeling of architecture based on metamodel and ontology, characterized in that: 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 their 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 DoDAF meta-metamodel include: Type, Tuple, Individual; The mapping relationship 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 in 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 interest to the large platform information system is constructed, thereby establishing the ontology framework of the information system architecture metamodel; 3) According to the metamodel ontology framework, construct the information system domain ontology based on the metamodel ontology, that is, the instance of the metamodel ontology, to provide a reusable domain ontology library for the information system architecture model construction; 4) Utilize the metamodel ontology framework and domain ontology library to build a multi-view model of information system architecture with data consistency 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 corresponds to the concept of Class in OWL, which includes individual type and power type. Tuple type is a set of tuples, which is a set of descriptions of the relationship between types. Tuple type does not correspond. OWL's description of all classes in a domain is based on a tree structure, where owl:Thing is set as the parent node of all classes, and other classes are established as child nodes of this node. When creating a new class in OWL, it only needs to be declared as a named class. The definition of a class consists of a reference and a restriction list. 2.2) Mapping of properties in OWL; The concept of tuple type Tuple in DoDAF meta-metamodel corresponds to the attribute in OWL; There are two types of properties in OWL: data properties and object properties. Data properties refer to the relationship between class instances and non-relational data; object properties refer to the relationship between instances of two classes. 2.3) Attributes of classes in OWL; Complete the feature description and attribute restrictions of the tuple type Tuple according to the feature description of the class attributes in OWL; Among them, the characteristic description of the attributes of a class in OWL is a detailed description of the characteristics of the attributes, and its purpose is to provide a powerful mechanism for the attributes to enhance the reasoning about the attributes; the characteristic description of the 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