CN113076086A - Metadata management system and method for modeling model object using the same - Google Patents
Metadata management system and method for modeling model object using the same Download PDFInfo
- Publication number
- CN113076086A CN113076086A CN202110388611.8A CN202110388611A CN113076086A CN 113076086 A CN113076086 A CN 113076086A CN 202110388611 A CN202110388611 A CN 202110388611A CN 113076086 A CN113076086 A CN 113076086A
- Authority
- CN
- China
- Prior art keywords
- model object
- model
- information
- attribute information
- management system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/24—Object-oriented
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
A method and a metadata management system for modeling a model object using a metadata management system are provided. The method comprises the following steps: receiving input basic information and attribute information about at least one model object in a metadata management system, defining the at least one model object according to the input basic information and attribute information to model the at least one model object, determining inheritance relationships or association relationships between the at least one model object and other model objects based on the input basic information and attribute information in a modeling process, and generating a corresponding data access interface for the model object using a corresponding data access interface name and a data access interface attribute code when modeling of the at least one model object is completed, so that an external application program can access the corresponding modeled model object. The scheme of the invention can improve the management method of the metadata and realize a uniform data access interface for different systems.
Description
Technical Field
The present invention relates to the field of metadata modeling, and more particularly, to a metadata management system and a method, a computer device, and a storage medium for modeling a model object using the metadata management system.
Background
With the rapid development of computer technology and software engineering, software modeling becomes indispensable as a bridge for communicating the real world with the computer world. In the prior art, there are various software modeling methods, which have advantages and disadvantages: some methods can only be used in partial scenes, cannot be widely applied, have strong theoretical performance and poor practicability, and have weak expansibility, so that the long-term development of a software system is not facilitated. Different modeling methods can have a huge impact on software engineering.
Disclosure of Invention
It is an object of the present invention to provide a method of modeling a model object using a metadata management system and a metadata management system to solve or at least alleviate at least one of the above-mentioned problems of the prior art.
Specifically, according to a first aspect of the present invention, there is provided a method of modeling a model object using a metadata management system, wherein the metadata includes basic information and attribute information on at least one model object, the method comprising:
receiving, in the metadata management system, inputted basic information and attribute information about at least one model object, wherein the basic information about at least one model object includes at least a name of the at least one model object, information defining an inheritance relationship between the at least one model object and other model objects, and a corresponding data access interface name for accessing the at least one model object, wherein the attribute information about at least one model object includes at least information defining an association relationship between the at least one model object and other model objects and an attribute encoding of a corresponding data access interface for accessing the at least one model object; and
defining the at least one model object according to the input basic information and attribute information about the at least one model object to model the at least one model object, determining inheritance relationships or association relationships between the at least one model object and other model objects based on the input basic information and attribute information about the at least one model object in a modeling process, and generating a corresponding data access interface for the at least one model object using a corresponding data access interface name and a data access interface attribute code when modeling of the at least one model object is completed, so that an external application program can access the at least one model object formed by corresponding modeling.
According to one embodiment, the method further comprises: after inputting the basic information and the attribute information about at least one model object, storing the basic information of the at least one model object into a first database table of the metadata management system, storing the attribute information of the at least one model object into a second database table of the metadata management system, and generating at least one additional database table for storing business data corresponding to each model object according to the basic information and the attribute information of the model object for each model object.
According to one embodiment, the generating of the additional at least one database table for storing business data corresponding to each model object from the basic information and the attribute information of the model object comprises: and generating at least one additional database table for storing business data corresponding to each model object according to the name of the additional database table in the basic information of the model object and the name of the field for generating the additional database table in the attribute information of the model object aiming at each model object.
According to one embodiment, the method further comprises determining a level at which the at least one model object is located in the built model from the information defining inheritance relationships between the at least one model object and other model objects and the information defining association relationships between the at least one model object and other model objects by:
defining a first model object by inputting basic information and attribute information on the first model object in the metadata management system, the defined first model object being a first hierarchy of a model to be built; and
defining a second model object by inputting basic information and attribute information about the second model object in the metadata management system, and determining a relationship between the second model object and the first model object based on the inputted basic information and attribute information about the second model object, building the second model object to a second level below a first level at which the first model object is located if there is an inheritance relationship between the second model object and the first model object, and building the second model object to a first level at which the first model object is located if there is an association relationship between the second model object and the first model object.
According to a second aspect of the present invention, there is provided a metadata management system comprising:
an input unit configured to receive input basic information and attribute information about at least one model object, wherein the basic information about the at least one model object at least comprises a name of the at least one model object, information defining an inheritance relationship between the at least one model object and other model objects, and a corresponding data access interface name for accessing the at least one model object, wherein the attribute information about the at least one model object at least comprises information defining an association relationship between the at least one model object and other model objects and an attribute encoding of a corresponding data access interface for accessing the at least one model object;
a processing unit configured to define the at least one model object according to the inputted basic information and attribute information about the at least one model object to model the at least one model object, determine inheritance relationships or association relationships between the at least one model object and other model objects based on the basic information and attribute information about the at least one model object inputted into the metadata management system during modeling, and generate a corresponding data access interface for the at least one model object using a corresponding data access interface name and a data access interface attribute code when modeling of the at least one model object is completed, so that an external application can access the at least one model object formed by corresponding modeling.
According to one embodiment, wherein the metadata management system comprises a storage unit comprising:
a first database table configured to store basic information about the at least one model object input to the metadata management system,
a second database table configured to store attribute information about the at least one model object entered into the metadata management system,
and the additional at least one database table is configured to be generated according to the basic information and the attribute information of each model object aiming at each model object and used for storing the business data corresponding to each model object.
According to one embodiment, the basic information on at least one model object further comprises a name of the additional at least one database table for storing business data corresponding to the at least one model object, the attribute information on at least one model object further comprises a name of a field for generating the additional at least one database table, and wherein the additional at least one database table is further configured to be generated for each model object according to the name of the additional database table in the basic information of the model object and the name of the field for generating the additional database table in the attribute information of the model object.
According to one embodiment, wherein the processing unit is further configured to: determining the level of the at least one model object in the established model according to the information for defining the inheritance relationship between the at least one model object and other model objects and the information for defining the association relationship between the at least one model object and other model objects by:
defining a first model object by inputting basic information and attribute information on the first model object in the metadata management system, the defined first model object being a first hierarchy of a model to be built; and
defining a second model object by inputting basic information and attribute information about the second model object in the metadata management system, and determining a relationship between the second model object and the first model object based on the inputted basic information and attribute information about the second model object, building the second model object to a second level below a first level at which the first model object is located if there is an inheritance relationship between the second model object and the first model object, and building the second model object to a first level at which the first model object is located if there is an association relationship between the second model object and the first model object.
According to a third aspect of the present invention, there is provided a computer apparatus comprising a memory and a processor, the memory having stored thereon a computer program which, when executed by the processor, causes the method of modelling a model object using a metadata management system as described above to be performed.
According to a fourth aspect of the present invention, there is provided a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, causes the method of modeling a model object using a metadata management system as described above to be performed.
The scheme of the invention provides a novel metadata management system and a method for modeling a model object by using the metadata management system. By using the scheme of the invention, the model object is defined by inputting the basic information and the attribute information about the model object in the metadata management system, and the hierarchy of the model object in the model is determined according to the basic information and the attribute information, so that the metadata model can be established, and further, the stable, efficient and extensible software model can be helped to be constructed. The model object established by the invention can be widely applied to various software systems, in particular to enterprise application systems. The scheme of the invention can also standardize the model interface, so that the constructed model can follow the unified interface specification and design principle, and the stability and the expansibility of the system are ensured.
Drawings
Non-limiting and non-exhaustive embodiments of the present invention are described by way of example with reference to the following drawings, in which:
FIG. 1 is a flow diagram that schematically illustrates a method for modeling model objects using a metadata management system, in accordance with an embodiment of the present invention;
FIG. 2 is a block diagram that schematically illustrates a metadata management system, in accordance with an embodiment of the present invention;
FIG. 3 is a diagram schematically illustrating basic information of a model object according to an embodiment of the present invention;
FIG. 4 is a diagram that schematically illustrates attribute information for a model object, in accordance with an embodiment of the present invention;
FIG. 5 is a diagram schematically illustrating attribute information of a model object according to another embodiment of the present invention;
fig. 6 is a diagram schematically illustrating a metadata model according to an embodiment of the present invention.
Detailed Description
In order to make the above and other features and advantages of the present invention more apparent, the present invention is further described below with reference to the accompanying drawings. It is understood that the specific embodiments described herein are for purposes of illustration only and are not intended to be limiting.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to one of ordinary skill in the art that the specific details need not be employed to practice the present invention. In other instances, well-known steps or operations are not described in detail to avoid obscuring the invention.
The term "model object" herein refers to an object (e.g., a claim object) in a computer system corresponding to an element (e.g., a claim) in the real world for which modeling processing is required. Specifically, the model object may include a system object and a business object, wherein the system object refers to a model object built in the system or a model object capable of supporting system operation (such as a person, an organization, a menu (such as a system navigation menu), or system configuration in the system), and the business object refers to an object related to normal business of the system (such as a general ledger, a receipt, or an invoice in a financial system). In addition, the model objects may each be inherited to one or more common model objects, the base meta-object (which may be considered in the form of a "root object"). Metadata may refer to all data used to describe the model object, e.g., all basic information and attribute information about the model object.
The term "data access interface" herein refers to an external function interface, such as a "RESTful API" interface, that allows external applications to access model objects. The RESTful API technology is a popular inter-system access mode at present, the RESTful API is used as conveniently as url accessing a website, and different platforms can be crossed, for example, programs developed in different languages can use the RESTful API to call each other. The RESTful API is a relatively mature technology, but the interface address patterns are not uniform. The RESTful API provided by the metadata management system can provide a uniform access mode, and can access the corresponding RESTful API address according to the API name defined by the model object, so that the purpose of accessing and operating data is achieved. For example, the data access interface may allow external applications to perform some standard data manipulation functions (e.g., add, delete, modify, find, etc.) and custom manipulation functions (e.g., copy, cut, etc.) on model objects. For example, the data access interface may be automatically generated after modeling is complete, which may allow other systems to access the data in the model object (system-automated actions) without requiring a developer to write a program to call the data out of the database back to the other systems as before. In addition, other systems can be allowed to access various related data of the model object through the data access interface, such as customer information of a company can be conveniently inquired through the automatically generated data access interface in a software system for modeling the client, and the client can be added or deleted.
FIG. 1 illustrates a method 100 for modeling model objects using a metadata management system, in accordance with an embodiment of the present invention. The method 100 comprises:
s101, receiving input basic information and attribute information about at least one model object in the metadata management system, wherein the basic information about the at least one model object at least comprises a name of the at least one model object, information defining inheritance relationships between the at least one model object and other model objects and corresponding data access interface names for accessing the at least one model object, and the attribute information about the at least one model object at least comprises information defining association relationships between the at least one model object and other model objects and attribute codes of corresponding data access interfaces for accessing the at least one model object.
S102, defining the at least one model object according to the input basic information and attribute information about the at least one model object to model the at least one model object, determining inheritance relationships or incidence relationships between the at least one model object and other model objects based on the input basic information and attribute information about the at least one model object in the modeling process, and generating a corresponding data access interface for the at least one model object by using a corresponding data access interface name and a corresponding attribute code of the data access interface when the modeling of the at least one model object is completed, so that an external application program can access the at least one model object formed by the corresponding modeling.
Specifically, in step S101, as shown in fig. 3, the received basic information about at least one model object may include, for example, a name of the model object, a module to which the model object belongs (which may indicate a group to which the model object belongs), a type (which may be used to indicate a type to which the model object belongs), an API name (i.e., a corresponding data access interface name for accessing the at least one model object), a physical table name (which will be further explained below), a source, a hint, an underlying meta-object (which may specify inheriting an existing model object), a tree structure, a logical deletion, and/or the like. In the embodiment shown in FIG. 3, model objects to be defined for a reimbursement order are grouped into a "documents" module and classified into the type of "transaction object". Such grouping and classification may be set according to actual needs to facilitate management of model objects in the metadata management system, e.g., model objects may be grouped according to business to determine the module to which the model object belongs; the model object may also be classified according to its usage to determine the type to which the model object belongs. In addition, the module and type to which the model object belongs can be viewed as an attribute of the model object itself.
As shown in fig. 4, the received attribute information about at least one model object may include, for example, a code of an attribute of a data access interface of the model object (i.e., an attribute code of a corresponding data access interface accessing the model object), a field name (explained further below), a name of the attribute, a hint, a data type, a field length, a decimal point position, a default value, and/or the like. In another embodiment, as shown in fig. 5, a model object having an association relationship with the model object may be set by setting a data type in the attribute information as an association relationship and inputting a relationship ID of the model object. All the attribute fields of a model object can also be displayed for the model object so as to carry out query preview on the attribute fields of the model object. For example, the attribute field of the model object may include a unique ID, a line number, a key (primary key), a business object definition ID, an attribute type, a business object type definition version ID, an attribute number, and/or an attribute name, and the like.
In step S102, in one embodiment, the process of defining the model object is the process of modeling it. The process of defining a model object includes: after inputting the basic information and the attribute information about at least one model object, storing the basic information of the at least one model object into a first database table of the metadata management system, and storing the attribute information of the at least one model object into a second database table of the metadata management system.
In one embodiment, the basic information about at least one model object further includes a name of the additional at least one database table for storing business data corresponding to the at least one model object, the attribute information about at least one model object further includes a name of a field used for generating the additional at least one database table, and the generating, for each model object, the additional at least one database table for storing business data corresponding to each model object according to the basic information and the attribute information of the model object includes: and generating at least one additional database table for storing business data corresponding to each model object according to the name of the additional database table in the basic information of the model object and the name of the field for generating the additional database table in the attribute information of the model object aiming at each model object. The generated database physical table may include some system preset fields, such as a unique ID, a creator, etc., in addition to the service data input by the user.
In one embodiment, the basic information of the model object may be saved to a Metadataform database table (i.e., a first database table), where the necessary basic information includes at least an "API name" and a "physical table name" (indicating the name of the database table that holds the actual business data of the model object). In one embodiment, the attribute information of the model object may be saved to a MetadataField database table (i.e., a second database table), where the necessary basic information includes at least a "code (indicating API interface attribute encoding)" and a "field name (indicating the name of the field of the database table that generated the actual business data of the model object)".
And generating at least one additional database table for storing business data corresponding to each model object according to the basic information and the attribute information of the model object. The term "additional" is with respect to the first database table and the second database table. In one embodiment, for example, the metadata management system may generate an additional database table for each model object. It should be understood that a database table herein may also be referred to as a "database physical table" or "physical table".
In step S102, after generating the database physical table, the metadata management system may automatically generate an API interface for the model object according to a preset RESTful API access pattern by using the API name in the basic information and the corresponding field name encoded by the API interface attribute in the attribute information about at least one model object.
In one embodiment, the generated API interface address pattern may be of the form: http:// server/app/{ version }/{ resource }/[ { id } ] [? { urlParameter } ]. Wherein server is an IP address or domain name, app is an application root path, version is a release version of a RESTful API, resource is an API name of a model object, ID is a data ID (e.g., a keyword ID) of the model object, and urlParameter is a query parameter. Wherein server, app, version are deployed according to actual situation, resource and id are determined according to defined model object and actual business data, urlParameter is fixed parameter, such as query parameter: query, paging parameter limit, etc.
The metadata management system can provide a uniform access mode by accessing a corresponding RESTful API address according to an API name, when the RESTful API of a model object is accessed, the corresponding model object can be found according to an input parameter such as resource, and a keyword of data of the model object can be found through id, so that a database table of the model object is queried, actual business data is found, and a request is returned. In the above manner, functions such as adding, querying, deleting, modifying, exporting, importing and the like to the model object can be realized. For example, the API interface may provide functionality for external systems to query model object data, add model object data, modify model object data, delete model object data, import model object data, or export model object data in the metadata management system. In addition, for example, the API interface can also generate page content and configuration structures according to the metadata of the model object so as to complete the building of system functions.
When the model object is defined, the current model object can be appointed or selected to inherit to which existing model object, the basic information and attribute of the existing object can be inherited to the new model object, and the inheritance hierarchy is not limited, so that the layered modeling can be completed according to the requirement of actual service.
In one embodiment, the metadata model built for the model object may include a plurality of different levels, and the level at which the at least one model object is located in the built model may be determined from the information defining the inheritance relationship and the information defining the association relationship between the at least one model object and the other model objects by:
defining a first model object by inputting basic information and attribute information on the first model object in the metadata management system, the defined first model object being a first hierarchy of a model to be built; and defining a second model object by inputting basic information and attribute information on the second model object in the metadata management system, and determining a relationship between the second model object and the first model object based on the inputted basic information and attribute information on the second model object, building the second model object to a second level below a first level where the first model object is located if there is an inheritance relationship between the second model object and the first model object, and building the second model object to a first level where the first model object is located if there is an association relationship between the second model object and the first model object.
FIG. 2 illustrates a metadata management system 200 according to an embodiment of the present invention. The metadata management system 200 includes an input unit 210 and a processing unit 220.
The input unit 210 is configured to receive input basic information and attribute information about at least one model object, wherein the basic information about at least one model object comprises at least a name of the at least one model object, information defining an inheritance relationship between the at least one model object and other model objects, and a corresponding data access interface name for accessing the at least one model object, wherein the attribute information about at least one model object comprises at least information defining an association relationship between the at least one model object and other model objects and an attribute encoding of a corresponding data access interface for accessing the at least one model object.
The processing unit 220 is configured to define the at least one model object according to the inputted basic information and attribute information about the at least one model object to model the at least one model object, determine an inheritance relationship or an association relationship between the at least one model object and other model objects based on the basic information and attribute information about the at least one model object inputted into the metadata management system during the modeling process, and generate a corresponding data access interface for the at least one model object using a corresponding data access interface name and a data access interface attribute code when the modeling of the at least one model object is completed, so that an external application can access the at least one model object formed by the corresponding modeling.
The metadata management system 200 further comprises a storage unit 230, said storage unit 230 containing a first database table 231, a second database table 232 and additionally at least one database table 233.
The first database table 231 is configured for storing basic information about the at least one model object input to the metadata management system. The second database table 232 is configured to store attribute information entered into the metadata management system regarding the at least one model object. An additional at least one database table 233 is configured to be generated for each model object from the basic information and attribute information of the model object for storing business data corresponding to each model object.
The metadata management system 200 herein may be applied in a variety of scenarios, and in particular may be applied in enterprise management systems, e.g., in enterprise applications such as financial sharing, management accounting, etc. In different application scenarios, the standard interface can be modified or expanded according to a predetermined rule.
FIG. 3 shows a diagram 300 of basic information of a model object, according to an embodiment of the invention. FIG. 4 shows a diagram 400 of attribute information for a model object, according to an embodiment of the invention. As shown in fig. 3 and 4, the chinese name of the model object is "reimbursement form", the name of the corresponding API interface is "expenseBill", and the attribute of the API interface is encoded as "expenseAmount"; the name of the database physical table generated by the metadata management system for the model object is "T _ EXPENSE _ BILL", and the name of the field of the database physical table is "EXPENSE _ AMOUNT"; the model object is inherited from the model object of businessObject and is located at the next level of the businessObject model object. Fig. 5 illustrates a schematic diagram of attribute information of a model object according to another embodiment of the present invention. It can be seen that fig. 5 also shows a model object having an association relationship with the model object, specifically, the "data type" is set as "association relationship", and the "examination and approval record area" is input in the "relationship ID" so that the "examination and approval record area" model object has an association relationship with the model object.
FIG. 6 illustrates a metadata model 600 according to an embodiment of the invention. In one embodiment, the model objects in the metadata model may be inherited to a common model object (shown in FIG. 6 as a base meta-object). As shown in fig. 6, the "base meta-object" is located at a first level of the model, the "a-object" is inherited to the "base meta-object", is located at a second level of the model, the "B-object" is inherited to the "a-object" (which is indirectly inherited to the "base meta-object"), is located at a third level of the model, and the "C-object" and the "B-object" have an association relationship therebetween, are located at the same third level as the "B-object", and are also inherited to the "base meta-object".
The inheritance relationship means that the existing basic information and attribute information of the model object are inherited, for example, the B object inherits the A object, that is, the B object has all the basic information and attribute information of the A object, and the user does not need to fill in the basic information and attribute information of the A object when creating/defining the B object, so that the labor cost can be saved, and the metadata in the system can be better managed. It will be appreciated that the number of levels of the metadata model may be unlimited, and that the user may modify the structure of the model at any time as desired.
It will be appreciated by those of ordinary skill in the art that the schematic diagram of the metadata management system shown in fig. 2 is merely an illustrative block diagram of portions of the structure associated with aspects of the present invention and does not constitute a limitation of the computer device, processor or computer program embodying aspects of the present invention. A particular computer device, processor or computer program may include more or fewer components or modules than shown in the figures, or may combine or split certain components or modules, or may have a different arrangement of components or modules.
In addition, it should be understood that the various elements of the metadata management system described above may be implemented in whole or in part by software, hardware, and combinations thereof. The units can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the units.
In one embodiment, a computer device is provided comprising a memory and a processor, the memory having stored thereon computer instructions executable by the processor, the computer instructions, when executed by the processor, instructing the processor to perform the steps of the method of the invention. The computer device may broadly be a server, or any other electronic device having the necessary computing and/or processing capabilities. In one embodiment, the computer device may include a processor, memory, a network interface, a communication interface, etc., connected by a system bus. The processor of the computer device may be used to provide the necessary computing, processing and/or control capabilities. The memory of the computer device may include non-volatile storage media and internal memory. An operating system, a computer program, and the like may be stored in or on the non-volatile storage medium. The internal memory may provide an environment for the operating system and the computer programs in the non-volatile storage medium to run. The network interface and the communication interface of the computer device may be used to connect and communicate with an external device through a network. Which when executed by a processor performs the steps of the method of the invention.
The invention may be implemented as a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, causes the steps of the method of the invention to be performed. In one embodiment, the computer program is distributed across a plurality of computer devices or processors coupled by a network such that the computer program is stored, accessed, and executed by one or more computer devices or processors in a distributed fashion. A single method step/operation, or two or more method steps/operations, may be performed by a single computer device or processor or by two or more computer devices or processors. One or more method steps/operations may be performed by one or more computer devices or processors, and one or more other method steps/operations may be performed by one or more other computer devices or processors. One or more computer devices or processors may perform a single method step/operation, or perform two or more method steps/operations.
It will be understood by those of ordinary skill in the art that all or part of the steps of the method of the present invention may be directed to associated hardware, such as a computer device or a processor, for performing the steps of the method of the present invention by a computer program, which may be stored in a non-transitory computer readable storage medium and executed to cause the steps of the method of the present invention to be performed. Any reference herein to memory, storage, databases, or other media may include non-volatile and/or volatile memory, as appropriate. Examples of non-volatile memory include read-only memory (ROM), programmable ROM (prom), electrically programmable ROM (eprom), electrically erasable programmable ROM (eeprom), flash memory, magnetic tape, floppy disk, magneto-optical data storage device, hard disk, solid state disk, and the like. Examples of volatile memory include Random Access Memory (RAM), external cache memory, and the like.
The respective technical features described above may be arbitrarily combined. Although not all possible combinations of features are described, any combination of features should be considered to be covered by the present specification as long as there is no contradiction between such combinations.
While the present invention has been described in connection with the embodiments, it is to be understood by those skilled in the art that the foregoing description and drawings are merely illustrative and not restrictive of the broad invention, and that this invention not be limited to the disclosed embodiments. Various modifications and variations are possible without departing from the spirit of the invention.
Claims (10)
1. A method for modeling a model object using a metadata management system, wherein the metadata includes basic information and attribute information about at least one model object, the method comprising:
receiving, in the metadata management system, inputted basic information and attribute information about at least one model object, wherein the basic information about at least one model object includes at least a name of the at least one model object, information defining an inheritance relationship between the at least one model object and other model objects, and a corresponding data access interface name for accessing the at least one model object, wherein the attribute information about at least one model object includes at least information defining an association relationship between the at least one model object and other model objects and an attribute encoding of a corresponding data access interface for accessing the at least one model object; and
defining the at least one model object according to the input basic information and attribute information about the at least one model object to model the at least one model object, determining inheritance relationships or association relationships between the at least one model object and other model objects based on the input basic information and attribute information about the at least one model object in a modeling process, and generating a corresponding data access interface for the at least one model object using a corresponding data access interface name and a data access interface attribute code when modeling of the at least one model object is completed, so that an external application program can access the at least one model object formed by corresponding modeling.
2. The method of claim 1, further comprising: after inputting the basic information and the attribute information about at least one model object, storing the basic information of the at least one model object into a first database table of the metadata management system, storing the attribute information of the at least one model object into a second database table of the metadata management system, and generating at least one additional database table for storing business data corresponding to each model object according to the basic information and the attribute information of the model object for each model object.
3. The method of claim 2, wherein the basic information about at least one model object further comprises a name of the additional at least one database table for storing business data corresponding to the at least one model object, the attribute information about at least one model object further comprises a name of a field used to generate the additional at least one database table, and wherein the generating, for each model object, the additional at least one database table for storing business data corresponding to each model object from the basic information and the attribute information of the model object comprises: and generating at least one additional database table for storing business data corresponding to each model object according to the name of the additional database table in the basic information of the model object and the name of the field for generating the additional database table in the attribute information of the model object aiming at each model object.
4. The method according to any one of claims 1 to 3, further comprising determining a level at which the at least one model object is located in the built model from the information defining inheritance relationships between the at least one model object and other model objects and the information defining association relationships between the at least one model object and other model objects by:
defining a first model object by inputting basic information and attribute information on the first model object in the metadata management system, the defined first model object being a first hierarchy of a model to be built; and
defining a second model object by inputting basic information and attribute information about the second model object in the metadata management system, and determining a relationship between the second model object and the first model object based on the inputted basic information and attribute information about the second model object, building the second model object to a second level below a first level at which the first model object is located if there is an inheritance relationship between the second model object and the first model object, and building the second model object to a first level at which the first model object is located if there is an association relationship between the second model object and the first model object.
5. A metadata management system, comprising:
an input unit configured to receive input basic information and attribute information about at least one model object, wherein the basic information about the at least one model object at least comprises a name of the at least one model object, information defining an inheritance relationship between the at least one model object and other model objects, and a corresponding data access interface name for accessing the at least one model object, wherein the attribute information about the at least one model object at least comprises information defining an association relationship between the at least one model object and other model objects and an attribute encoding of a corresponding data access interface for accessing the at least one model object;
a processing unit configured to define the at least one model object according to the inputted basic information and attribute information about the at least one model object to model the at least one model object, determine inheritance relationships or association relationships between the at least one model object and other model objects based on the basic information and attribute information about the at least one model object inputted into the metadata management system during modeling, and generate a corresponding data access interface for the at least one model object using a corresponding data access interface name and a data access interface attribute code when modeling of the at least one model object is completed, so that an external application can access the at least one model object formed by corresponding modeling.
6. The metadata management system of claim 5 wherein the metadata management system comprises a storage unit, the storage unit including:
a first database table configured to store basic information about the at least one model object input to the metadata management system,
a second database table configured to store attribute information about the at least one model object entered into the metadata management system,
and the additional at least one database table is configured to be generated according to the basic information and the attribute information of each model object aiming at each model object and used for storing the business data corresponding to each model object.
7. The system of claim 6, wherein the base information about at least one model object further includes a name of the additional at least one database table for storing business data corresponding to the at least one model object, the attribute information about at least one model object further includes a name of a field used to generate the additional at least one database table, and wherein the additional at least one database table is further configured to be generated for each model object according to the name of the additional database table in the base information of the model object and the name of the field used to generate the additional database table in the attribute information of the model object.
8. The system of any of claims 5 to 7, wherein the processing unit is further configured to: determining the level of the at least one model object in the established model according to the information for defining the inheritance relationship between the at least one model object and other model objects and the information for defining the association relationship between the at least one model object and other model objects by:
defining a first model object by inputting basic information and attribute information on the first model object in the metadata management system, the defined first model object being a first hierarchy of a model to be built; and
defining a second model object by inputting basic information and attribute information about the second model object in the metadata management system, and determining a relationship between the second model object and the first model object based on the inputted basic information and attribute information about the second model object, building the second model object to a second level below a first level at which the first model object is located if there is an inheritance relationship between the second model object and the first model object, and building the second model object to a first level at which the first model object is located if there is an association relationship between the second model object and the first model object.
9. A computer device comprising a memory and a processor, the memory having stored thereon a computer program which, when executed by the processor, causes the method of modeling a model object using a metadata management system of any of claims 1 to 4 to be performed.
10. A non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, causes the method of modeling a model object using a metadata management system of any of claims 1 to 4 to be performed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110388611.8A CN113076086B (en) | 2021-04-12 | 2021-04-12 | Metadata management system and method for modeling model object using the same |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110388611.8A CN113076086B (en) | 2021-04-12 | 2021-04-12 | Metadata management system and method for modeling model object using the same |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113076086A true CN113076086A (en) | 2021-07-06 |
| CN113076086B CN113076086B (en) | 2022-02-11 |
Family
ID=76617306
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110388611.8A Active CN113076086B (en) | 2021-04-12 | 2021-04-12 | Metadata management system and method for modeling model object using the same |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113076086B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114048193A (en) * | 2022-01-12 | 2022-02-15 | 树根互联股份有限公司 | Data management and control method, device and computer readable storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040049766A1 (en) * | 2002-09-09 | 2004-03-11 | Bloch Joshua J. | Method and apparatus for associating metadata attributes with program elements |
| CN102567932A (en) * | 2010-12-30 | 2012-07-11 | 北京亿阳信通软件研究院有限公司 | Method, device and system for managing comprehensive resources |
| CN103729460A (en) * | 2014-01-10 | 2014-04-16 | 中国南方电网有限责任公司 | Graphical data model managing method and system based on metadata |
| CN106355439A (en) * | 2016-08-29 | 2017-01-25 | 南京茂毓通软件科技有限公司 | Knowledge base modeling method for association relation analysis |
| CN108038222A (en) * | 2017-12-22 | 2018-05-15 | 冶金自动化研究设计院 | System for Information System Modeling and entity-property frame of data access |
| CN109753492A (en) * | 2019-01-02 | 2019-05-14 | 陕西西部资信股份有限公司 | A kind of system constituting method and device based on metadata configurations |
| CN110196852A (en) * | 2019-05-16 | 2019-09-03 | 北京科东电力控制系统有限责任公司 | Regulation cloud grid model data management method and system based on metadata management |
-
2021
- 2021-04-12 CN CN202110388611.8A patent/CN113076086B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040049766A1 (en) * | 2002-09-09 | 2004-03-11 | Bloch Joshua J. | Method and apparatus for associating metadata attributes with program elements |
| CN102567932A (en) * | 2010-12-30 | 2012-07-11 | 北京亿阳信通软件研究院有限公司 | Method, device and system for managing comprehensive resources |
| CN103729460A (en) * | 2014-01-10 | 2014-04-16 | 中国南方电网有限责任公司 | Graphical data model managing method and system based on metadata |
| CN106355439A (en) * | 2016-08-29 | 2017-01-25 | 南京茂毓通软件科技有限公司 | Knowledge base modeling method for association relation analysis |
| CN108038222A (en) * | 2017-12-22 | 2018-05-15 | 冶金自动化研究设计院 | System for Information System Modeling and entity-property frame of data access |
| CN109753492A (en) * | 2019-01-02 | 2019-05-14 | 陕西西部资信股份有限公司 | A kind of system constituting method and device based on metadata configurations |
| CN110196852A (en) * | 2019-05-16 | 2019-09-03 | 北京科东电力控制系统有限责任公司 | Regulation cloud grid model data management method and system based on metadata management |
Non-Patent Citations (1)
| Title |
|---|
| 江伟光: ""产品集成建模关键技术及应用研究"", 《中国优秀博士学位论文全文数据库》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114048193A (en) * | 2022-01-12 | 2022-02-15 | 树根互联股份有限公司 | Data management and control method, device and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113076086B (en) | 2022-02-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10037341B1 (en) | Nesting tree quotas within a filesystem | |
| CN108388622B (en) | API interface dynamic generation method and device, computer equipment and storage medium | |
| US10628381B2 (en) | Optimized content object storage service for large scale content | |
| US20130238557A1 (en) | Managing tenant-specific data sets in a multi-tenant environment | |
| US10089371B2 (en) | Extensible extract, transform and load (ETL) framework | |
| US10740286B1 (en) | Migration task validation before data migration | |
| CN103425468A (en) | Method and device for integrating plug-in type software | |
| CN103064957B (en) | Realize method and the client of ACL | |
| CN115993966B (en) | Application development system and method | |
| US20220067180A1 (en) | Security policy management for database | |
| TW202030658A (en) | Data structure reading method and apparatus, data structure updating method and apparatus, and electronic device | |
| CN102054041B (en) | Method and system for upgrading metadata | |
| CN113946837A (en) | Data access and data access authority configuration method, device and storage medium | |
| CN112416710A (en) | User operation recording method and device, electronic equipment and storage medium | |
| CN112464625A (en) | Receipt generation method and device, computer equipment and storage medium | |
| CN113076086B (en) | Metadata management system and method for modeling model object using the same | |
| JP4719212B2 (en) | Method and apparatus for constructing representations of objects and entities | |
| US11620353B2 (en) | Hyperlink visual indicator | |
| CN113918149A (en) | Interface development method and device, computer equipment and storage medium | |
| CN112000971B (en) | File permission recording method, system and related device | |
| CN115543428A (en) | Simulated data generation method and device based on strategy template | |
| CN116167882A (en) | Conditional expression dynamic configuration method, accounting condition calculation method and accounting condition calculation device | |
| US9009731B2 (en) | Conversion of lightweight object to a heavyweight object | |
| US11366658B1 (en) | Seamless lifecycle stability for extensible software features | |
| CN111221817B (en) | Service information data storage method, device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |