CN116185357A - Meta-model construction method, device and system based on multi-architecture modeling language - Google Patents

Abstract

A method for constructing a metamodel based on a multi-architecture modeling language, comprising: obtaining a set metamodel ID and a metamodel type; according to the metamodel ID and metamodel type, calling a corresponding metamodel template to generate a corresponding initial metamodel Model file; obtain the set meta-model information; identify the meta-model information, generate a corresponding specification based on the multi-architecture modeling language specification, and add it to the initial meta-model file; call and compile the initial meta-model file, and integrate and generate Graphical metamodel. Based on the multi-architecture modeling language, the present invention uniformly describes and expresses all constructed meta-model elements to realize efficient modeling of specific domain meta-models. The semantic mapping relationship between the model and the multi-architecture modeling language improves the compatibility and standardization of the meta-model.

Description

Metamodel construction method, device and system based on multi-architecture modeling language

Technical Field

The present invention belongs to the field of computer technology, and in particular, relates to a metamodel construction method, device and system based on a multi-architecture modeling language.

Background Art

Metamodel is a model about models. It is a model defined for a specific domain or its specific problem and constructed by a modeling language. There are three main existing methods for constructing domain-specific metamodels. Two of them are extended from existing modeling languages. (1) Refinement based on the existing metamodel in the same domain, thereby refining general concepts into specific concepts; (2) Extension based on a general, domain-independent modeling language to define domain-specific related concepts; (3) Define a new modeling language to construct a metamodel. Among these three methods, the third method is to express domain-specific concepts in the most direct and simple way, but it is particularly difficult to define a modeling language from scratch, as it contains very complex semantics. The first method is relatively the most practical and economical modeling method, but the semantics of the basic language will reduce the expressive power of the Directory Service Markup (DSML). Therefore, in general, most of the existing technologies adopt the second method, such as extension based on the existing general modeling language SysML to define a domain-specific metamodel for complex equipment. The model construction process mainly includes the following four steps:

(1) Extract relevant domain knowledge of complex equipment, such as the mission environment involved, and identify the semantic content such as concepts, relationships, interfaces, etc. involved;

(2) Define abstract syntax and use the model-driven architecture (MOF) to formally define the abstract syntax and semantics of the above concepts.

(3) Define specific syntax and semantics, expand on the general system modeling language SysML, and define corresponding representation methods and symbols for each metamodel element as its specific syntax based on the abstract syntax, so that it can be used in the modeling process;

The purpose of semantically describing the constructed metamodel is to explain the semantics and usage of the relevant elements in the metamodel and form a graphical language specification.

The above-mentioned prior art defines a new metamodel for new fields and needs through the definition of MOF. Although it can adapt well to the target field, the newly defined metamodel has poor compatibility and can only be expanded through the existing UM L/SysML platform, with high resource costs. Moreover, the newly defined metamodel is not standardized and is not conducive to data exchange with models in other fields.

Summary of the invention

In view of the problems existing in the above-mentioned prior art, the present invention provides a meta-model construction method, device and system based on a multi-architecture modeling language.

The present invention adopts the following technical solution:

In a first aspect, a metamodel construction method based on a multi-architecture modeling language includes:

Get the set metamodel ID and metamodel type;

According to the metamodel ID and metamodel type, the corresponding metamodel template is called to generate the corresponding initial metamodel file;

Get the set metamodel information;

Identify the metamodel information, generate corresponding specifications based on the multi-architecture modeling language specification, and add the specifications to the initial metamodel file;

The initial metamodel file is called and compiled to integrate and generate a graphical metamodel.

Furthermore, the metamodel ID and metamodel type that are set are obtained by inputting them through an interactive interface, or by providing optional options through the interactive interface.

Furthermore, a model template library is set to store preset meta-model templates.

Furthermore, the preset model templates include at least six types of meta-model templates of GOPPRR, namely, graph meta-model template, object meta-model template, point meta-model template, attribute meta-model template, relationship meta-model template, and role meta-model template.

Further, the metamodel information is identified, and corresponding specifications are generated based on the multi-architecture modeling language specification, including: according to the graph metamodel template, based on the identified metamodel information, a corresponding graph metamodel specification file is generated, and added to the initial metamodel file; according to the object metamodel template, based on the identified metamodel information, a corresponding object metamodel specification file is generated, and added to the initial metamodel file; according to the point metamodel template, based on the identified metamodel information, a corresponding point metamodel specification file is generated, and added to the initial metamodel file; according to the attribute metamodel template, based on the identified metamodel information, a corresponding attribute metamodel specification file is generated, and added to the initial metamodel file; according to the relationship metamodel template, based on the identified metamodel information, a corresponding relationship metamodel specification file is generated, and added to the initial metamodel file; according to the role metamodel template, based on the identified metamodel information, a corresponding role metamodel specification file is generated, and added to the initial metamodel file.

Further, the initial metamodel file is called and compiled to integrate and generate a graphical metamodel, including: compiling the graphic metamodel specification file, and based on the information therein, calling and compiling the object metamodel specification file, the point metamodel specification file, the attribute metamodel specification file, the relationship metamodel specification file, and the role metamodel specification file, integrating all the compiled model specification files to generate the graphical metamodel of the specific field.

Furthermore, the graph metamodel template includes metamodel type, metamodel ID, binding, name and description; the object metamodel template includes metamodel ID, name, description and fixed syntax; the point metamodel template includes model ID, name, description and fixed syntax; the attribute metamodel template includes data type, model ID, name, unit and description; the relationship metamodel template includes model ID, name, description and fixed syntax; the role metamodel template includes direction, model ID, name, description and fixed syntax.

In a second aspect, a metamodel construction device based on a multi-architecture modeling language includes:

The acquisition module is used to obtain the set metamodel ID and metamodel type;

A calling module, used to call the corresponding metamodel template according to the metamodel ID and metamodel type, and generate the corresponding initial metamodel file;

The acquisition module is also used to acquire the set metamodel information;

A generation module, used for identifying the metamodel information, generating corresponding specifications based on the multi-architecture modeling language specification, and adding the specifications to the initial metamodel file;

The generation module is also used to call and compile the initial meta-model file, and integrate and generate the graphical meta-model.

In a third aspect, a metamodel construction system based on a multi-architecture modeling language is provided, the system comprising:

one or more processors;

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 implement the above-mentioned metamodel construction method based on a multi-architecture modeling language.

In a fourth aspect, a computer-readable storage medium stores a computer program, which, when executed by a processor, implements the above-mentioned metamodel construction method based on a multi-architecture modeling language.

Beneficial Effects

Compared with the prior art, the beneficial effects of the present invention are: providing a metamodel construction method based on a multi-architecture modeling language, including: obtaining a set metamodel ID and metamodel type; calling a corresponding metamodel template according to the metamodel ID and metamodel type, and generating a corresponding initial metamodel file; obtaining set metamodel information; identifying the metamodel information, generating a corresponding specification based on a multi-architecture modeling language specification, and adding it to the initial metamodel file; calling and compiling the initial metamodel file, and integrating to generate a graphical metamodel. In order to solve the problems of unclear hierarchical description, fuzzy decomposition and unclear data flow interaction of equipment functions caused by multi-disciplinary, multi-physical quantity, multi-behavior and multi-morphological evolution in the process of complex equipment analysis to architecture design, this metamodel construction method based on multi-architecture modeling language is used to analyze the complex product problem domain, and construct a specific domain metamodel of the full cycle, all elements and all-field R&D information of complex equipment. All the constructed metamodel elements are uniformly described and expressed based on the multi-architecture modeling language to achieve efficient modeling of specific domain metamodels. On the basis of the GOPPRR metamodel construction method, the semantic mapping relationship between the metamodel of graphical modeling method and the multi-architecture modeling language is established to improve the compatibility and standardization of metamodels.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a flow chart of building a metamodel based on a multi-architecture modeling language according to the present invention;

FIG2 is a structural diagram of a metamodel building device based on a multi-architecture modeling language according to the present invention;

FIG3 is a structural diagram of an electronic device system provided by an embodiment of an operating environment of a meta-model building method based on a multi-architecture modeling language in the present invention;

FIG4 is a structural diagram of a computer-readable storage medium provided by an embodiment of an operating environment of a meta-model building method based on a multi-architecture modeling language in the present invention;

FIG5 is an example diagram of a model library in a metamodel construction based on a multi-architecture modeling language according to the present invention;

FIG6 is a specific step of calling and compiling in constructing a metamodel based on a multi-architecture modeling language according to the present invention;

FIG. 7 illustrates an example of compiling a graph model and setting objects and relationships in one embodiment;

FIG8 illustrates, in one embodiment, obtaining attribute IDs, etc. from the metaObject object metamodel file on the left side of the screen from the right side of the screen;

FIG9 illustrates a specific interface of step S56 in one embodiment;

FIG. 10 illustrates a schematic interface for setting the decomposition of an object in step S57 in one embodiment;

FIG. 11 illustrates information of an integrated generated primitive model file in one embodiment.

DETAILED DESCRIPTION

The present invention is further described below in conjunction with specific embodiments.

The terms "include" and "comprising" used herein should be understood as inclusive and open-ended, rather than exclusive. Specifically, when the terms "include" and "comprising" and their synonyms are used in the specification and claims, they mean including the specified features, steps or components. These terms cannot be understood to exclude the existence of other features, steps or components.

On the one hand, in one embodiment, the present invention provides a metamodel construction method based on a multi-architecture modeling language, as shown in FIG1 , the method comprising:

S1: Obtaining the set metamodel ID and metamodel type. In one embodiment, a graphical operation interface is provided, through which the metamodel ID and metamodel type are input.

In one embodiment, a graphical operation interface is provided, through which optional options are provided to select and obtain the metamodel ID and the metamodel type, such as a drop-down menu item.

In one embodiment, the metamodel ID and metamodel type are automatically identified and obtained by inputting text. The specific method of setting the metamodel ID and metamodel type is not limited.

S2: According to the metamodel ID and metamodel type, the corresponding metamodel template is called to generate a corresponding initial metamodel file.

In one embodiment, a model template library is set to store preset meta-model templates. The preset model templates include at least six types of meta-model templates of GOPPRR, namely, graph meta-model template, object meta-model template, point meta-model template, attribute meta-model template, relationship meta-model template, and role meta-model template.

Among them, GOPPRR is a meta-metamodel concept. The GOPPRR meta-metamodel is divided into 6 types, including graph, object, attribute, node, relationship, and role. Specifically: Graph: The graph is composed of the other 5 elements and describes the system in a box; Object: The basic element in the model, which can exist alone or be linked to other objects; Property: It cannot exist alone and is attached to other meta-metamodels to represent its characteristics; Port: Usually attached to an object, indicating the port where the object is connected; Role: At both ends of the relationship, it connects objects and indicates how or who the objects are connected; Relationship: The relationship is connected to the object through the role, indicating the interaction between objects. According to the above meta-metamodel, the above six types of metamodel templates are created, namely, graph metamodel template, object metamodel template, node metamodel template, attribute metamodel template, relationship metamodel template, and role metamodel template.

In one embodiment, (1) the metamodel template includes the metamodel type, ID, binding, name and description, where the ID is the name of the metamodel file obtained, and the other values are empty. The metamodel template is detailed as follows:

(2) The object metamodel template contains ID, name, description and fixed syntax, where ID is the name of the object metamodel file obtained, the default value of the fixed syntax is rectangle, and other values are empty. The object metamodel template is as follows:

(3) The point metamodel template contains ID, name, description and fixed syntax, where ID is the name of the point metamodel file obtained, the default value of the fixed syntax is circle, and other values are empty. The point metamodel template is as follows:

(4) The attribute metamodel template contains data type, ID, name, unit and description. The default value of data type is string. Only integer and real number can be set as unit, so the default value is "null". Other values are empty. The attribute metamodel template is as follows:

StringPropertyIDannotation(localLabel="",unit="null",description="");

(5) The relational metamodel template contains ID, name, description and fixed syntax, where the default value of the fixed syntax is a bold solid line and other values are empty. The relational metamodel template is as follows:

(6) The role metamodel template contains direction, ID, name, description and fixed syntax, where the default value of the fixed syntax is a circle, the direction is input, and other values are empty. The role metamodel template is as follows:

In one embodiment, the metamodel ID and type defined by relevant personnel are obtained, different types of metamodel templates are called, and corresponding metamodel files are generated, so that relevant personnel can further set other information of the metamodel based on the metamodel template.

S3: Get the set metamodel information.

In one embodiment, a graphical operation interface is provided, through which the meta-model information required for setting is obtained.

In one embodiment, a same graphical operation interface is provided to obtain the metamodel ID and type data and the required metamodel information.

In one embodiment, the metamodel ID and type data and the required metamodel information are acquired through different acquisition methods.

S4: Identify the metamodel information, generate corresponding specifications based on the multi-architecture modeling language specification, and add them to the initial metamodel file.

In one embodiment, it specifically includes:

According to the graphic meta-model template, based on the identified meta-model information, a corresponding graphic meta-model specification file is generated and added to the initial meta-model file;

According to the object metamodel template, based on the identified metamodel information, generating a corresponding object metamodel specification file, and adding it to the initial metamodel file;

According to the point metamodel template, based on the identified metamodel information, generating a corresponding point metamodel specification file, and adding it to the initial metamodel file;

According to the attribute metamodel template, based on the identified metamodel information, a corresponding attribute metamodel specification file is generated and added to the initial metamodel file;

According to the relational metamodel template, based on the identified metamodel information, generating a corresponding relational metamodel specification file, and adding it to the initial metamodel file;

According to the role metamodel template, based on the identified metamodel information, a corresponding role metamodel specification file is generated and added to the initial metamodel file.

FIG5 is an example diagram of a model library in a metamodel construction based on a multi-architecture modeling language according to the present invention.

In one embodiment, as shown in Figure 5, the graph metamodel template includes metamodel type, metamodel ID, binding, name and description; the object metamodel template includes metamodel ID, name, description and fixed syntax; the point metamodel template includes model ID, name, description and fixed syntax; the attribute metamodel template includes data type, model ID, name, unit and description; the relationship metamodel template includes model ID, name, description and fixed syntax; the role metamodel template includes direction, model ID, name, description and fixed syntax.

1) Based on the attribute metamodel template, identify the information required for establishing the attribute metamodel from the acquired metamodel information, generate a corresponding specification file, and save it to the initial metamodel file. The main steps are as follows:

(1) Identify the name of the attribute metamodel;

(2) Identify the data types of the attribute metamodel, such as integer, Boolean, real number, and enumeration;

(3) Identify the unit of the attribute;

(4) Descriptive text of the identification attribute.

2) Based on the role metamodel template, identify the information required to establish the role metamodel from the acquired metamodel information, generate a corresponding specification file, and save it to the initial metamodel file. The construction steps are as follows:

(1) Identify the name of the role metamodel;

(2) Identify the descriptive text of the role metamodel;

(3) Identify the direction of the role metamodel, which is relative to the relationship and includes the beginning and the end;

(4) Identify the fixed syntax of the role metamodel

(5) Identify the attributes of the role metamodel.

3) Based on the point metamodel template, identify the information required for establishing the point metamodel from the acquired metamodel information, generate a corresponding specification file, and save it to the initial metamodel file. The main steps are as follows;

(1) Identify the name of the point metamodel;

(2) Description text of the identification point metamodel;

(3) a fixed grammar for the identification point metamodel;

(4) Identify the attributes of the point meta-model.

4) Based on the object metamodel template, identify the information required for establishing the object metamodel from the acquired metamodel information, generate a corresponding specification file, and save it to the initial metamodel file. The main steps are as follows:

(1) Identify the name of the object metamodel;

(2) Identify the descriptive text of the object metamodel;

(3) Identify the fixed syntax of the object metamodel;

(4) Identify the points of the object metamodel. When setting the defined point metamodel on the object metamodel, it is necessary to select the direction of the point. Unlike the direction of the role, the direction of the point is relative to the object. There are three types of directions: input, output, and undirected.

(5) Identify the attributes of the object metamodel.

5) Based on the relational metamodel template, identify the required information for establishing the attribute relational model from the acquired metamodel information, generate a corresponding specification file, and save it to the initial metamodel file. The main steps are as follows:

(1) Identify the name of the relational metamodel;

(2) Identify the descriptive text of the relational metamodel;

(3) Identify the fixed syntax of the relational metamodel;

(4) Identify the attributes of the relational metamodel;

(5) Identify the roles of the relational metamodel. This step sets the role metamodel to the relational metamodel. If a relational metamodel is to be instantiated, it must contain at least one start role and one end role. Multiple start and end roles can be defined here, but the roles at both ends of the relationship are unique after instantiation.

6) Based on the meta-model template, identify the information required for establishing the meta-model from the acquired meta-model information, generate a corresponding specification file, and save it to the initial meta-model file. The construction steps are as follows:

(1) Identify the name of the graphic element model;

(2) Identify the description text of the primitive model;

(3) Identifying the attributes of the graph meta-model. This step can set the defined attribute meta-model to the graph meta-model;

(4) Identify objects in the graph model;

(5) Identify relationships between graph primitives;

(6) Identify the binding of the graph model. Its function is to define which objects and relationships can be connected to the beginning and end of the relationship in the graphical modeling language. In the definition process, for the points on the object, the output point of the object can only be bound to the beginning of the relationship, and the input point can only be bound to the end of the relationship. After the binding relationship is defined in the graph model, it can be connected in the instantiated model;

(7) Identify the decomposition of objects in the primitive model;

(8) Identify the cross-section of objects in the graphic model.

S5: calling and compiling the initial metamodel file, integrating and generating a graphical metamodel.

In one embodiment, the initial metamodel file is called and compiled to integrate and generate a graphical metamodel, including: compiling the graphic metamodel specification file, calling and compiling the object metamodel specification file, the point metamodel specification file, the attribute metamodel specification file, the relationship metamodel specification file, and the role metamodel specification file based on the information therein, integrating all the compiled model specification files to generate the graphical metamodel of the specific field.

FIG6 shows the specific steps of calling and compiling in constructing a metamodel based on a multi-architecture modeling language according to the present invention.

In one embodiment, as shown in FIG6 , S5 calls and compiles the initial metamodel file, and integrates and generates a graphical metamodel, specifically including:

S51: compile a graph primitive model, and obtain an attribute ID, an object ID, and a relationship ID in the compiled graph primitive model;

As shown in FIG. 7 , an example of compiling a graph primitive model and setting objects and relationships is illustrated in one embodiment.

S52: compile the object metamodel according to the acquired object ID, and acquire the attribute ID and the point ID in the object metamodel;

As shown in FIG. 8 , it is illustrated that in one embodiment, in the metaObject object metamodel file on the left side of the screen, the point ID and the like are obtained from the right side of the screen.

S53: compile a point meta-model according to the obtained point ID, and obtain an attribute ID in the point meta-model;

S54: compile a relational metamodel based on the acquired relational ID, and simultaneously acquire an attribute ID and a role ID in the relational metamodel;

S55: compile the role meta-model according to the obtained role ID, and obtain the attribute ID in the role meta-model;

S56: generating binding rules of a graphical modeling language according to the binding settings in the graphic element model;

As shown in FIG. 9 , it is illustrated that in one embodiment, in the “element model” file on the left side of the screen, the binding rule “bindconnector” (also called connection rule) is obtained from the right side of the screen.

S57: generating object decomposition and sectioning rules according to the decomposition and sectioning settings of the object in the graphic element model;

FIG. 10 shows the decomposition of setting objects in one embodiment.

S58: compile an attribute metamodel based on the attribute IDs obtained from the compiled five metamodels, namely, the graph metamodel, the object metamodel, the relationship metamodel, the node metamodel, and the role metamodel;

S59: Integrate and generate a graphical modeling language based on all the information compiled in the above steps S51 to S58.

As shown in FIG. 11 , it illustrates information of an integrated generated primitive model file in one embodiment.

Please refer to the flowchart in Figure 6 for the logical relationship of the execution sequence of the above steps.

On the other hand, in one embodiment, the present invention provides a meta-model construction device based on a multi-architecture modeling language.

As shown in FIG2 , the metamodel construction device based on the multi-architecture modeling language of the present invention includes:

The first acquisition module is used to acquire the set metamodel ID and metamodel type;

A calling generation module is used to call a corresponding metamodel template according to the metamodel ID and metamodel type to generate a corresponding initial metamodel file;

A first generation module is used to identify the metamodel information, generate a corresponding specification based on a multi-architecture modeling language specification, and add the specification to the initial metamodel file;

The second acquisition module is used to acquire the set metamodel information;

The integration generation module is used to call and compile the initial meta-model file and integrate and generate a graphical meta-model.

The functions of the above-mentioned device can be implemented by the functional modules corresponding to the meta-model construction method based on the multi-architecture modeling language described above, which will not be repeated here.

On the other hand, in one embodiment, please refer to Figure 3, which is a structural diagram of an electronic device provided in one embodiment of the present application. As shown in Figure 3, the electronic device includes a processor, a memory, and a bus.

The memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the memory through a bus. When the machine-readable instructions are executed by the processor, the steps of the metamodel construction method based on the multi-architecture modeling language in the method embodiment shown in Figure 1 above can be executed. The specific implementation method can be found in the method embodiment, which will not be repeated here.

On the other hand, in one embodiment, the embodiment of the present application also provides a computer-readable storage medium, as shown in Figure 4, on which a computer program is stored. When the computer program is executed by the processor, it can execute the steps of the metamodel construction method based on the multi-architecture modeling language in the method embodiment shown in Figure 1 above. The specific implementation method can be found in the method embodiment, which will not be repeated here.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application can essentially be embodied in the form of a software product, or in other words, the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The protection scope of the present application is not limited thereto. Although the present application is described in detail with reference to the above-described embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-described embodiments within the technical scope disclosed in the present application, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (10)

1. A meta-model construction method based on a multi-architecture modeling language, comprising:

s1: acquiring a set meta model ID and a meta model type;

s2: calling a corresponding meta model template according to the meta model ID and the meta model type to generate a corresponding initial meta model file;

s3: acquiring set meta-model information;

s4: identifying the meta-model information according to the meta-model template, generating a corresponding specification based on a multi-architecture modeling language specification, and adding the corresponding specification into the initial meta-model file;

s5: and calling and compiling the initial meta-model file, and integrating to generate a graphical meta-model.

2. The meta model construction method based on multi-architecture modeling language according to claim 1, wherein the meta model ID and the meta model type are obtained through the input of the interactive interface, or the selectable option selection is provided through the interactive interface.

3. The meta-model construction method based on multi-architecture modeling language according to claim 1, wherein the set model template library stores preset meta-model templates.

4. A meta-model construction method based on multi-architecture modeling language according to claim 3, wherein the preset meta-model templates at least comprise a graphic primitive model template, an object meta-model template, a point meta-model template, an attribute meta-model template, a relationship meta-model template and a role meta-model template.

5. The meta model construction method based on multi-architecture modeling language according to claim 1, wherein the meta model templates called in step S2 include primitive model templates, object meta model templates, point meta model templates, attribute meta model templates and relationship meta model templates;

step S4: identifying the meta-model information, generating a corresponding specification based on a multi-architecture modeling language specification, and adding the corresponding specification to the initial meta-model file, wherein the method specifically comprises the following steps of:

generating a corresponding primitive model specification file based on the identified primitive model information according to the primitive model template, and adding the primitive model specification file to the initial primitive model file;

generating a corresponding object meta-model specification file based on the identified meta-model information according to the object meta-model template, and adding the corresponding object meta-model specification file to the initial meta-model file;

generating a corresponding point meta-model specification file based on the identified meta-model information according to the point meta-model template, and adding the point meta-model specification file to the initial meta-model file;

generating a corresponding attribute meta-model specification file based on the identified meta-model information according to the attribute meta-model template, and adding the attribute meta-model specification file to the initial meta-model file;

generating a corresponding relation meta-model specification file based on the identified meta-model information according to the relation meta-model template, and adding the corresponding relation meta-model specification file to the initial meta-model file;

and generating a corresponding character meta-model specification file based on the identified meta-model information according to the character meta-model template, and adding the character meta-model specification file to the initial meta-model file.

6. The meta-model construction method based on multi-architecture modeling language according to claim 5, wherein the calling and compiling the initial meta-model file, integrating and generating a graphical meta-model, comprises: compiling the primitive model specification file, calling and compiling the object primitive model specification file, the point primitive model specification file, the attribute primitive model specification file, the relation primitive model specification file and the role primitive model specification file according to the information in the primitive model specification file, and integrating all the compiled model specification files to generate the graphical primitive model in a specific field.

7. A meta-model construction method based on a multi-architecture modeling language according to claim 3, wherein the primitive model template includes a meta-model type, a meta-model ID, a binding, a name, and a description; the object meta-model template comprises meta-model ID, name, description and fixed grammar; the point meta model template comprises a model ID, a name, a description and a fixed grammar; the attribute meta-model template comprises a data type, a model ID, a name, a unit and a description; the relational meta-model template comprises a model ID, a name, a description and a fixed grammar; the character meta-model template contains directions, model IDs, names, descriptions, and fixed grammars.

8. A meta-model building apparatus based on a multi-architecture modeling language, comprising:

the first acquisition module is used for acquiring the set meta model ID and the set meta model type;

the calling generation module is used for calling a corresponding meta model template according to the meta model ID and the meta model type to generate a corresponding initial meta model file;

the first generation module is used for identifying the meta-model information, generating corresponding specifications based on multi-architecture modeling language specifications and adding the corresponding specifications to the initial meta-model file;

the second acquisition module is used for acquiring the set meta-model information;

and the integration generation module is used for calling and compiling the initial meta-model file and integrating to generate a graphical meta-model.

9. A metamodel construction system based on a multi-architecture modeling language, the system comprising:

one or more processors;

a storage means for storing one or more programs;

the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the multi-architecture modeling language based metamodel construction method of any one of claims 1-7.

10. A computer-readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements a meta model construction method based on a multi-architecture modeling language as claimed in any one of claims 1-7.

Images