CN116149673A

CN116149673A - Application program data model issuing system, application program data model expanding method and electronic equipment

Info

Publication number: CN116149673A
Application number: CN202310099192.5A
Authority: CN
Inventors: 王学文; 黄玮
Original assignee: Alibaba Cloud Computing Ltd
Current assignee: Alibaba Cloud Computing Ltd
Priority date: 2023-01-21
Filing date: 2023-01-21
Publication date: 2023-05-23

Abstract

The application provides a release system of a data model of an application program, which comprises a first user platform, a second user platform and an application release platform; the method comprises the steps that a first user platform generates baseline data model metadata of a first application program and issues the baseline data model metadata through an application issuing platform, wherein the baseline data model metadata is in a read-only state; a second user arranges a metadata engine on an operation platform for operating a second application program, downloads the baseline data model metadata of the first application program, and generates extended part data model metadata for expanding the first application program; and when the computer application is running, the metadata engine is used for combining the baseline data model metadata with the extended part data model metadata to generate second application program data model metadata. The application also provides an extension method of the data model of the application program. According to the technical scheme, the baseline data model and the extended data model can be ensured to be independent relatively, and can be updated and updated respectively.

Description

Application program data model issuing system, application program data model expanding method and electronic equipment

Technical Field

The application relates to the technical field of computers, in particular to a release system of a data model of an application program; the application also relates to an extension method of the data model of the application program, electronic equipment and a storage medium.

Background

With the development of the internet, more enterprises begin to select application programs which fit application scenes required by themselves, but the development process of the application programs is quite complex, and more enterprises can also select to purchase and rent application programs developed by other enterprises so as to meet the demands of themselves.

However, the application scenario of the enterprise is very complex, and the application program developed by the first user often needs to be modified in a targeted manner at the second user; in particular, in the data model part, almost every manufacturer needs to modify the data model in the original application program to reflect the specific requirements of the application scene.

In the prior art, an application program released at the release end of the application program often causes modification of an original data model in the process of modifying the data model of the application program; thus, after the first user further upgrades the data model of the application program, the second user is difficult to continuously use the upgraded data model on the original basis; the above situation causes that it is difficult for the second user at the user end to track the upgrade of the distribution end in time.

Therefore, how to extend the data model of the application program, so that the extending process does not prevent the updated version of the original data model from being adopted in time, becomes a technical problem to be solved by those skilled in the art.

Disclosure of Invention

The application program data model publishing system can enable a second user to conveniently combine a baseline data model from a first user with an extended data model provided by the second user, and facilitate the second user to upgrade the baseline data model in time; the application also provides an extension method of the data model of the application program, electronic equipment and a computer storage medium.

The application provides a release system of a data model of an application program, which comprises a first user platform, a second user platform and an application release platform;

the first user platform generates baseline data model metadata of a first application program and issues the baseline data model metadata through the application issuing platform, wherein the baseline data model metadata is in a read-only state;

the second user arranges a metadata engine on an operation platform for operating a second application program, downloads the baseline data model metadata of the first application program through the application release platform, and generates extended part data model metadata for expanding the first application program; when the computer application is operated, reading the baseline data model metadata through the metadata engine, reading the extended part data model metadata, combining the baseline data model metadata and the extended part data model metadata to generate second application program data model metadata, and using the second application program data model metadata in a process of establishing a second application program;

The application publishing platform is used for receiving and publishing the baseline data model metadata;

the data model is a description of data objects and interaction relations related to the application program; the data model metadata is data for describing a data model.

Optionally, the method further comprises: the first user platform issues an upgrade version of the baseline data model metadata through the application issuing platform, and the upgrade version is in a read-only state;

and the second user platform downloads the updated version of the baseline data model metadata through the application release platform on an operation platform for operating the second application program, and the data engine reads the updated version of the baseline data model metadata and combines the updated version of the baseline data model metadata with the extended part data model metadata to generate second application program data model metadata after the baseline data model metadata is updated and is used in the process of establishing the second application program.

Optionally, the method further comprises:

the second user platform updates the metadata of the extended part data model to obtain updated metadata of the extended part data model; and the metadata engine combines the updated extended part data model metadata with the baseline data model metadata to generate updated second application program data model metadata of the extended part data model metadata, and the updated second application program data model metadata is used in the process of establishing a second application program.

Optionally, the method further comprises:

the second user platform combines the baseline data model metadata and the extended part data model metadata, takes the formed extended second application program data model metadata as an extended and upgraded version of the baseline data model metadata, and issues the baseline data model metadata in a mode of issuing the baseline data model metadata through the application platform; and the third user can obtain the extended upgrade version of the baseline data model metadata through the application platform and use the extended upgrade version as baseline data model metadata.

The application also provides an extension method of the data model of the application program, which is used for a second application program operation platform of a second user platform for operating the application program, and comprises the following steps:

obtaining baseline data model metadata, wherein the baseline data model metadata is in a read-only state;

acquiring extended part data model metadata for extending the baseline data model according to the requirements of an application scene of a second application program;

and the preset metadata engine reads the baseline data model metadata and the extended part data model metadata, combines the baseline data model metadata and the extended part data model metadata to form extended data model metadata, and uses the extended data model metadata in a process established for the second application program.

Preferably, the baseline data model metadata and the extended portion data model metadata each include: domain object model metadata, data object model metadata, structure object model metadata.

Preferably, the metadata engine reads the baseline data model metadata and the extended portion data model metadata, combines the extended portion data model metadata with the baseline data model metadata to form second application data model metadata, and includes:

combining the corresponding domain object model metadata, the corresponding data object model metadata and the corresponding structure object model metadata in the baseline data model metadata and the corresponding extended part data model metadata into extended second application domain object model metadata, second application data object model metadata and second application structure object model metadata;

determining the mapping relation among the structural object model metadata, the domain object model metadata and the data object model metadata;

and according to the mapping relation among the object model metadata, combining the second application program structure object model metadata, the second application program field object model metadata and the second application program structure object model metadata to obtain the second application program data model metadata.

Preferably, the obtaining, for the requirement of the target application scenario, metadata of an extended portion data model for extending the baseline data model includes:

obtaining an expansion request for application expansion based on the baseline data model metadata;

and acquiring the metadata of the extended part data model constructed according to the target application scene from a metadata warehouse according to the extended request.

Preferably, the obtaining baseline data model metadata includes:

the baseline data model metadata is published along with the first application program through an application publishing platform;

the baseline data model metadata is obtained by downloading the first application.

Preferably, said obtaining said baseline data model metadata by downloading said first application program includes:

and downloading the first application program to a visual designer of the application program, and displaying a visual model corresponding to the baseline data model metadata according to the baseline data model metadata by the visual designer.

Preferably, the method further comprises:

obtaining incremental data model metadata for upgrading the baseline data model;

Upgrading the baseline data model metadata according to the incremental data model metadata to obtain upgraded baseline data model metadata;

and the metadata engine reads the updated baseline data model metadata and the extended part data model metadata, combines the updated baseline data model metadata with the extended part data model metadata, and obtains extended data model metadata with the updated baseline data model metadata.

Preferably, the method further comprises:

obtaining update-purpose extension-use data model metadata for updating the extension-use data model metadata;

updating the original extended part data model metadata through the extended part data model metadata for updating to obtain updated extended part data model metadata;

and the metadata engine reads the updated extended part data model metadata and the baseline data model metadata to obtain updated extended data model metadata.

The application provides an electronic device, comprising:

a processor;

a memory for storing a program of a method, which when read by a processor is executed performs the method of any of the above.

The present application also provides a computer storage medium storing a computer program which when executed performs a method according to any one of the above.

According to the expansion method of the data model, on the premise that the baseline data model metadata is in a read-only state, the baseline data model metadata and the expansion part data model metadata corresponding to a target application scene are read through a metadata engine, the expansion part data model metadata and the baseline data model metadata are combined to form expansion data model metadata, and a process is established according to the expansion data model metadata; the extended data model metadata can be combined with extended part data model metadata designed for a specific application scene on the basis of baseline data model metadata to obtain a complete data model suitable for the specific scene, and finally an application program process tightly combined with the specific scene is obtained. According to the method, when the metadata of the baseline data model are expanded, the original metadata of the baseline data model are not changed, so that the baseline data model and the metadata of the expanded data model can be independent relatively, and upgrading and updating can be performed respectively.

Drawings

Fig. 1 is a schematic diagram of an expansion method of a data model according to an embodiment of the present application;

FIG. 2 is a flowchart of an expanding method of a data model according to a first embodiment of the present application;

FIG. 3 is a schematic diagram of a structural object model according to a first embodiment of the present application;

fig. 4 is a schematic diagram of a domain object model according to a first embodiment of the present application;

FIG. 5 is a schematic diagram of a data object model according to a first embodiment of the present application;

FIG. 6 is a flowchart of a method for updating a data model according to a second embodiment of the present application;

fig. 7 is a schematic structural diagram of an expansion device of a data model according to a third embodiment of the present application;

FIG. 8 is a schematic diagram of a data model updating device according to a fourth embodiment of the present application;

fig. 9 is a schematic structural diagram of an electronic device according to a fifth embodiment of the present application.

Detailed Description

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application, however, may be embodied in many other forms than described herein and similarly generalized by those skilled in the art without departing from the spirit of the application and, therefore, the application is not to be limited to the specific embodiments disclosed below.

The embodiments of the present application provide a method, an apparatus, an electronic device, and a computer storage medium for expanding a data model, which will be described in detail in the following embodiments.

Firstly, in order to facilitate understanding of the data model extension method provided by the embodiment of the present application, the method is first described in connection with an application scenario of the method.

Referring to fig. 1, fig. 1 is a schematic diagram of a publishing system of a data model of an application program according to a first embodiment of the present application.

As shown in fig. 1, the publishing system of the data model of the application program includes: a first application 101, a first user platform 102, an application distribution platform 103, a second application 104, a second user platform 105.

Wherein the first application 101 is created by the first user platform 102 of the first user 1, the second application 104 is obtained by expanding an application architecture of the second user 2 on the basis of the first application 101, and the expansion of the application architecture comprises expansion of a baseline data model of the first application 101, and the expansion part is called an expansion data model; the baseline data model and the extended data model are described and transmitted in a metadata form, metadata corresponding to the baseline data model is called baseline data model metadata, and metadata corresponding to the extended data model is called extended data model metadata.

The baseline data model metadata is used for describing data of a baseline data model; in order to facilitate the user to design the baseline data model by himself, a convenient design interface can be provided through a graphical user interface of the platform, and the user can input relevant contents by combining elements such as graphics, charts and the like to realize the design of the baseline data model; for a user desiring to construct a specific application, the graphic, chart presentation involved with the application represented by the baseline data model can be seen from the platform provided for the user, including the block diagrams or fields representing the specific data object model, the data input page, and the association relationship with other data object models, etc.; the baseline data model metadata is a computer language description of the baseline data models, and is used for the data of the graphic chart presentation.

The baseline data model reflected by the baseline data model metadata may be understood as a description of the application logic and the data objects involved in the application of the first user program 101 and the interrelationships, for example, assuming that the first application program 101 may be used in the field of online teaching, the first application program 101 may be created by using the baseline data model, which includes a structural object model representing the presentation content of a presentation interface of a student, teacher, course, etc. for describing the target application; a domain object model for describing data objects such as students, teachers, courses, etc. contained in the target application scene; and a data object model describing the data structure of the data objects contained in the application scenario, such as descriptions of students, teachers, and curriculum specific data objects containing data content (e.g., fields represented as data tables). The baseline data model reflects the general and basic model architecture of the application, and is generally developed by application developers in a targeted manner according to the field and general problems faced by the application; by means of the baseline data model, a basic architecture of one of the application domains, such as the online teaching domain in the above example, can be obtained, which basic architecture can be provided for use by users of other of the domains. In many cases, the baseline data model is a model architecture designed directly for a typical client (i.e. the first user 1), typically an enterprise middle-stage, but in terms of architecture, a certain commonality is considered, and can be directly migrated to be used by other clients (e.g. the second user 2); of course, these clients using the migration application need to make some adjustments according to their own situation, in this embodiment of the present application, the baseline data model is set to be read-only, so that it cannot be changed, but the baseline data model is provided with an interface that can be extended to it or a manner of extending it, and the second user 2 can design the extension portion by itself according to its own situation.

The baseline data model is built through the first user platform 102, the specific building process can be performed in a visualized programming environment provided by the first user platform 102 by a programmer to obtain the baseline data model, and metadata corresponding to the baseline data model is generated through a program of the background of the first user platform 102, so that baseline data model metadata is obtained; after the creation of the first application 101 is completed, the release of the first application 101 is completed by the application release platform 103 in communication with the first user platform 102, where the application version of the first application 101 released by the application release platform 103 may be set to v1.0.

Specifically, after the first user platform 102 completes creation of the first application 101, the application publishing platform 103 is used to publish the first application 101, so that the second user 2 can purchase or rent the first application 101 through the application publishing platform 103 according to the requirement, and further obtain the use right of the first application 101. The second user 2 refers to any enterprise or person other than the first user 1 who is likely to use the first application 101.

After the second user 2 obtains the right of use of the first application 101 from the release platform 103, the main relation is, for the present application, the obtained metadata of the baseline data model, that is, the data objects used in the baseline model, which characterize the characteristics of people, objects, etc. that need to be processed by the application; while this baseline data model metadata has data objects and frameworks for the general case of the field, in general, it is difficult to fully meet all of the requirements of the second user 2. For a user who specifically wants to reference to use the first application program 101, such as the second user 2, the user is, for example, a professional training school or an extracurricular training class of a preschool child, and the situations specifically faced by the user are greatly different, and the user needs to combine with the specific situations of the user and appropriately expand the situations so as to adapt to the specific situations that the user needs to face; for the second user 2, the description itself requires the use of extended part data model metadata; specifically, the second user platform 105 may set related objects or data fields, even specific parameters and data, through an intuitive interface such as graphics and icons based on the baseline data model described by the baseline data model metadata, so as to finally obtain an extended part model, and further generate extended data model metadata in the background by the second user platform 105. The extended data model metadata can be combined with the baseline model metadata via an extended interface or other combination provided by the baseline data model.

Of course, the extended portion data model metadata may be obtained by extending the first application program 101 based on the obtained baseline model metadata according to a specific usage scenario of the application, and the specific obtaining manner does not affect the independence of the extended portion data model metadata as the extended portion data model metadata itself, that is, the extended portion data model metadata and the baseline model metadata belong to different mutually independent portions; the expansion method of the data model refers to that the metadata of the baseline data model is expanded by using metadata of an expansion part data model, so as to obtain metadata of the expansion data model meeting the requirements of specific scenes; in the embodiment of the present application, the baseline data model metadata of the second user 2 is obtained by downloading from an application platform, and the extended data model metadata is obtained by adding extended data model metadata to the baseline data model metadata in combination with the self situation, and whether a specific design interface and a specific design method need to be based on a baseline data model or not is only that an interface provided in a design process is different, however, in essence, the baseline data model metadata and the extended data model metadata exist independently from each other, and only when the application is running, the metadata are kneaded together by a metadata engine to form the extended data model metadata used in the actual running.

Because the baseline model metadata and the extended part data model metadata are mutually isolated, the baseline model metadata and the extended part data model metadata can be respectively and independently upgraded or updated, so that the method and the device have more convenient upgrading capability.

From the application level, in the embodiment of the application scenario, the expansion of the data model refers to the expansion of the baseline data model of the first application program 101 in combination with a more specific and more practical application scenario, and the expansion mode is realized by designing the data model of the expansion part and forming metadata of the data model of the expansion part.

In a specific aspect, the baseline data model further comprises three specific models, namely a domain object model, a structure object model and a data object model according to the requirements of a model architecture. For example, assuming that the first application 101 is an online teaching APP specifically applied to an online teaching field, the field object model may specifically include three field objects including a teacher, a student, and a course, where the field objects include relevant data of the teacher, the student, and the course, and further include behaviors related to the objects; for example, the student object may include data content composed of fields such as name, age, gender, grade, learning course, etc., and further includes actions related to the student object such as creating and deleting the student object, or a data processing manner of the student object. The data object model is a model related to definition and expansion of data for a certain class of objects, for example, a student, and the data object comprises data contents comprising fields of name, age, gender, grade, learning course and the like. The structure object model is a data structure of display content when the display is carried out according to the interface requirement, one structure object model can call a plurality of data object models, for example, the structure object model corresponding to an order display page can call two data object models of an order and order details. The field object model, the data object model and the structure object model have a mapping relation with each other, and the complete construction of the baseline data model can be realized through the mapping relation; for example, for a field object model "student", the mapping relationship between the data object model "student" and the data object model "student", that is, the modification of the data field of the data object model student, is reflected in the field object model student, because the data field of the student used by the field object model is from the data object model student; the interface for course management is used for displaying a certain structural object model, wherein the interface is mapped with a field object model 'student', a field object model 'teacher' and a field object model 'course', and relevant fields in the field object models are combined to form a display object.

Further, if the second user 2 desires to further create an object of "parent" after obtaining the first application 101 in a downloaded manner, a new domain object model describing the parent, and a data object model may be further created through the extended part data model metadata.

It should be noted that, the above embodiment of the scenario provided in the present application is only for facilitating understanding of the extension method of the data model provided in the present application, and is not used to limit the application scenario of the extension method of the computer application.

The following describes, with reference to fig. 2, an extension method of a data model according to a first embodiment of the present application, which is characterized in that, under the precondition that a baseline data model is guaranteed to be in a protected state that cannot be changed, baseline data model metadata and extension part data model metadata for extending the baseline data model are read by a metadata engine, the extension part data model metadata and the baseline data model metadata are combined to form extension data model metadata, and a process is established according to the extension data model metadata. The above procedure can also be understood as follows: the baseline data model metadata and the extended baseline data model metadata are static program description data, and the metadata engine is used as a process to read the program description data and assemble and run the two in a running process, so as to establish the running first application program 101 comprising the extended part. In the running state, the metadata engine is a process for combining two parts of metadata and driving the metadata to run; statically, the metadata engine is a specially designed computer program for implementing the above-described process. The metadata engine operates in a mirror image environment, namely, the metadata engine is read from a storage space storing metadata engine program codes into the mirror image space, and then a process related to the metadata engine is established according to the metadata engine codes in the mirror image space, so that the program operation in the data space is realized.

From the above description, it can be appreciated that the first embodiment of the present application provides a publishing system of a data model of an application program, including a first user platform 102, a second user platform 105, and an application publishing platform 103; the first user platform 102 generates a first application program 101, wherein the first application program comprises generated baseline data model metadata, and the baseline data model metadata is released through the application release platform 103 and is in a read-only state; the second user 2 arranges a metadata engine on a second user platform 105 on which a second application 104 is running, downloads baseline data model metadata of the first application 101 through the application publishing platform 103, and generates extended part data model metadata for extending the first application 101; when the computer application is operated, reading the baseline data model metadata through the metadata engine, reading the extended part data model metadata, combining the baseline data model metadata and the extended part data model metadata to generate second application program data model metadata, and using the second application program data model metadata in a process of establishing a second application program; the application publishing platform 103 is configured to receive and publish the baseline data model metadata; the data model is a description of data objects and interaction relations related to the application program; the data model metadata is data for describing a data model.

In actual operation, the first user 1 is likely to need to modify the baseline data model metadata, and the second user 2 is likely to need to modify the extended portion data model metadata, and for distinction, the modification of the baseline data model metadata by the first user 1 is referred to as an upgrade and the modification of the extended portion data model metadata by the second user 2 is referred to as an update in the present application.

In the publishing system provided in this embodiment, the step of implementing the upgrade of the baseline data model metadata by the first user 1 includes: the first user platform 102 issues an upgrade version of the baseline data model metadata through the application issue platform 103, the upgrade version being in a read-only state;

on the second user platform 105 on which the second application 104 is running, the updated version of the baseline data model metadata is downloaded through the application publishing platform 103, and the data engine reads the updated version of the baseline data model metadata and combines it with the extended portion data model metadata to generate second application data model metadata with updated baseline data model metadata, and uses the second application data model metadata in the process of building the second application 104.

In the publishing system provided in this embodiment, the step of implementing the update of the metadata of the extended portion data model by the second user 1 includes: the second user platform 105 updates the metadata of the extended part data model to obtain updated metadata of the extended part data model; and the metadata engine combines the updated extended part data model metadata with the baseline data model metadata to generate updated second application program data model metadata of the extended part data model metadata, and the updated second application program data model metadata is used in the process of establishing a second application program.

In the publishing system of the data model of the application program provided in this embodiment, the second user 2 may also use the extended metadata of the second application program data model as the baseline data model metadata provided to other people, and publish the baseline data model metadata for other people to use. The second application data model metadata as baseline data model metadata is referred to as baseline data model metadata extended upgrade version in order to distinguish it from the original baseline data model metadata.

The process for releasing the metadata extension upgrade version of the baseline data model by the second user comprises the following steps: the second user platform 105 combines the baseline data model metadata and the extended part data model metadata, takes the formed extended second application program data model metadata as an extended and upgraded version of the baseline data model metadata, and issues the baseline data model metadata in a manner of issuing the baseline data model metadata through the application platform; the third user can obtain the extended upgraded version of the baseline data model metadata through the application distribution platform 103 and use it as baseline data model metadata.

Referring to fig. 2, fig. 2 is a flowchart of a method for expanding a data model provided in a second embodiment of the present application, where the method is applied to an application running platform of a second user 2; the method includes the following steps S201 to S203.

Step S201, baseline data model metadata is obtained, and the baseline data model metadata is in a read-only state.

First, to facilitate understanding of the baseline data model metadata, a description will be given of "baseline" in the form of a specific scene embodiment.

Here, it is assumed that the first user 1 creates a first application 101 through an application build platform according to its own needs, and further distributes the first application 101 through an application distribution module or a dedicated application distribution platform 103 in the application build platform, including baseline data model metadata; the second user 2 obtains the rights of the use and the function expansion of the first application 101 through purchase or lease after considering own enterprise environment, and obtains the data describing the first application 101, namely, baseline model metadata, distributed by the first user 1 through the application distribution platform 103. Here, the "baseline" is the relevant content of the first application 101 which is the most initial basic part published by the first user 1 through the publication platform 103 and can be further used as a basis for improvement. The baseline data model metadata refers to a part of the baseline model related to the data object, and comprises a structural object model, a field object model and a data object model, which have a mutual correspondence (mapping) and a mutual construction relation.

In the process of a specific application, the baseline data model can be expressed as various data tables forming the target application, or functional unit block diagrams, wherein the data tables can be used for recording the data structure of the data object related in the target application, so as to express the attribute of the specific data object, thus forming a data object model, if the data object is a student, the data structure table for recording the attribute fields of the student such as age, sex, name, class and the like, and the data object of the student can be expressed, thus forming a data object model.

In an alternative embodiment of the present application, the baseline data model includes a structural object model for describing the presentation content in the presentation interface of the first application 101.

Referring to fig. 3, fig. 3 is a schematic diagram of a structural object model according to a first embodiment of the present application.

The content shown in fig. 3 is specifically a display editing interface of a structural object model applied to online teaching, including: a structure object model display interface 301 and a structure object model editing interface 302.

The structure object model display interface 301 displays a student structure object model 301-1, a course structure object model 301-2 and a teacher structure object model 301-3; these structural object models express what needs to be presented at the presentation interface of the target application.

The structure object editing interface 302 is specifically configured to edit contents such as basic information and fields of the model, and preview the edited model, as shown in fig. 3, the structure object editing interface 302 is configured to edit coding information and data type information of attributes such as name and age of the student structure object model 301-1. Of course, if the course structure object is selected in the structure object model display interface 301, editing settings may be performed on the course structure object.

The following description will be made with reference to fig. 4 and fig. 5, where first, please refer to fig. 4, and fig. 4 is a schematic diagram of a domain object model according to a first embodiment of the present application;

the content shown in fig. 4 is specifically a domain object model display editing interface applied to online teaching, including: a domain object model presentation interface 401, a domain object model editing interface 402.

The field object model display interface 401 displays a student field object model 401-1, a course field object model 401-2 and a teacher field object model 401-3; the domain object model is used for describing the data objects contained in the target application scene.

The domain object model editing interface 402 is specifically configured to edit the code and data type of the attribute of the name and the code and data type of the attribute of the age in the student domain object model 401-1, and further, may encode the code and data type of the attribute of the mobile phone number and the code and data type of other attributes as required, so as to complete the creation of the student domain object model 401-1. Of course, if the domain object is selected as a course in the domain object model display interface 401, editing setting may be performed on the course data object. The domain object model also carries the behavior of the data, i.e. the processing mode of the data, such as adding, deleting, checking, etc.

Further, referring to fig. 5, fig. 5 is a schematic diagram of a data object model according to a first embodiment of the present application;

the content shown in fig. 5 is specifically a data object model presentation editing interface applied to an online teaching model, including: a data object model presentation interface 501, a data object model editing interface 502. The data object model is used to describe the data structure of the data objects contained in the target application scenario.

Wherein, the data object model display interface 501 displays a student data object model 501-1, a course data object model 501-2 and a teacher data object model 501-3;

The data object model editing page 502 is specifically configured to edit attribute information such as field names and codes of attributes such as names and ages in the student data object model 501-1, so as to complete creation of the student data object model 501-1. Of course, if the course data object is selected in the data object model presentation interface 501, editing settings may also be made for the course data object. The data object model only relates to data definition and extension.

For the baseline data model, the content of the editing setting is set before the editing setting is issued by the user through the metadata of the baseline data model, and the editing setting is in a read-only state and can only be used for inquiring by the user to know the content of the baseline data model; since these contents are in a read-only state, they cannot be changed.

The baseline data model metadata may be understood as a transport carrier for the baseline data model, i.e. the baseline data model is distributed in the form of metadata; the expressed contents are expressed as the structural object model, the domain object model and the data object model which are expressed through the interface.

During the process of a specific application, the first application program 101 is generally constructed by the first user platform 102 of the first user 1 and distributed by uploading to the application publishing platform 103, wherein the published content includes the baseline data model. Further, the user of the target application, that is, the second user 2, may purchase or rent the usage rights of the first application 101 according to the needs, and download the first application 101 through the publishing platform to obtain the metadata of the baseline data model.

In a specific publishing mode, the metadata of the baseline data model is generally published along with the first application program 101 through the application publishing platform 103; the potential user, i.e. the second user 2, obtains the baseline data model metadata by downloading the first application 101. In general, the second user 2 downloads the first application 101 to the second user platform 105, and exposes the data model in a visual manner through a visual designer of the second user platform 105.

In this embodiment, the baseline data model metadata is set to a read-only form, so as to ensure that the baseline data model metadata is in a protected state that cannot be changed, and at the same time ensure that the original baseline data model metadata is functionally implemented in the second application 104 of the user. After obtaining the baseline data model metadata, the following step S202 is further performed.

Step S202, acquiring metadata of an extended part data model for extending the baseline data model according to the requirements of the application scenario of the second application program.

The target application scenario requirement refers to the original target application determined after the target application is combined with the requirement of the target application, namely, the second user 2 in the embodiment, namely, the content not related in the first application 101 in the embodiment. For example, assume that the first application program is an application issued by the first user 1 for online purchasing of goods by consumers, wherein the domain object model metadata of the first application program is used for describing price information and category information of the goods; after the second user 2 obtains the target application through the distribution platform of the first user 1, it is expected that the target application will be used to sell clothing commodities, but the clothing commodities need to describe the sizes of the commodities in addition to price information and type information of the commodities, and at this time, the metadata of the expansion part data model for expanding the baseline data model needs to include an expansion part for describing the size information.

In the specific application process, the metadata of the extended part data model can be designed according to the requirements of the user of the target application, and the specific design method can also intuitively edit the metadata in an interface similar to the baseline data model and then generate the metadata of the corresponding extended part data model; after generating metadata, the metadata may be stored in a metadata repository of the second user 2, and the acquiring extended portion data model metadata for extending the baseline data model includes: obtaining an expansion request for expanding the baseline data model; and acquiring the metadata of the extended part data model for extending the baseline data model from the metadata warehouse according to the extension request.

In this step, aiming at the requirement of the target application scene, the metadata of the extended part data model corresponding to the target application scene and used for extending the baseline data model is obtained. That is, considering the situation of the target application scenario specifically, the extended part data model metadata is selected, where the extended part data model metadata may be designed by the second user 2 as the user, or may be designed by other relevant clients and placed in the metadata repository, and the second user 2 selects to obtain according to the application scenario.

The extended part data model metadata also comprises a structural object model, a field object model and a data object model; and each kind of object model is correspondingly connected with the corresponding object model of the metadata of the baseline data model respectively.

In actual use, the metadata of the extended data model is often already enabled, but some update of the metadata of the extended data model is needed under the condition that the metadata of the baseline data model is unchanged; thus, the step and conditions for starting step S202 may be set, for example, starting in the following manner:

obtaining an expansion request for application expansion based on the baseline data model; the expansion request can be initiated by a user according to the requirement, or the user has updated the metadata of the expansion part data model and stored in a metadata warehouse, and the expansion request needs to be actually used in the application;

Another way of starting updating the metadata of the extended part data model may be a way characterized by automatically detecting and judging whether the metadata of the extended part data model meets the current requirement, and if not, starting the step of acquiring the metadata of the extended part data model for extending the baseline data model. The method comprises the following steps:

Judging whether original extended part data model metadata in original extended data model metadata accords with the requirement of a current target application scene or not;

and if not, deleting the original metadata of the expansion part data model, and executing the requirement aiming at the target application scene to acquire the metadata of the expansion part data model for expanding the baseline data model.

The above-mentioned determination of whether to meet the requirements of the current target application scenario may be implemented in various manners, for example, after the target application is actually run, user feedback is received.

In step S203, the preset metadata engine reads the baseline data model metadata and the extended portion data model metadata, combines them to form extended data model metadata, and uses them in the process established for the second application program.

In a specific application process, combining the extended part data model metadata with the baseline data model metadata means that new extended part data model metadata is added on the basis of original baseline data model metadata, for example, assuming that the baseline data model metadata can be used for constructing three field objects of students, courses and teachers, and corresponding structural objects and data objects of the three field objects, new fields can be added for the three field objects according to the extended part data model metadata on the basis, and the associated structural objects and data objects can be correspondingly modified.

The metadata engine can be understood as a computer program or a functional unit special for processing metadata, and is embodied as a running thread in actual running; the thread is used for respectively reading the baseline model metadata and the extended part data model metadata, combining and running the baseline model metadata and the extended part data model metadata to form extended data model metadata according to the content of the baseline model metadata and the extended part data model metadata, and using the extended data model metadata in a process established for a second application program to realize the actual running of the application. It should be noted that the baseline model metadata and the extended portion data model metadata stored separately can be combined with each other to form extended data model metadata only by driving of the metadata engine, and run in an actual running environment. As previously described, the metadata engine may operate in a mirrored environment.

Further, the step S103 is implemented by the following steps S1 to S3:

and S1, combining the corresponding domain object model metadata, the corresponding data object model metadata and the corresponding structure object model metadata in the baseline data model metadata and the extended part data model metadata into extended domain object model metadata, data object model metadata and structure object model metadata.

The correspondence relation can be seen from the name of the object model, for example.

And S2, determining the mapping relation among the structural object model metadata, the domain object model metadata and the data object model metadata.

The above-described mapping relationship may be recorded in each object model by linking with each other or the like.

And step S3, according to the mapping relation among the object model metadata, the extended structural object model metadata, the domain object model metadata and the data object model metadata are combined with each other to obtain the extended data model metadata.

By expanding the data model metadata as described above, data objects used in the actual running process can be created.

The mapping relationship between the structural object model metadata, the domain object model metadata and the data object model metadata may be understood as an association relationship between different models, for example, as shown in fig. 3, 4 and 5, when the addition of the model fields needs to be completed in the structural object model, the data object model and the domain object model, after the addition of the model fields of the structural object model is completed according to the extended part model metadata, the model fields may be synchronized to other models according to the association relationship between the three models, so that the model metadata of the other models and the extended part data model metadata are combined. Alternatively, the structural object model part of the baseline data model and the structural object model part of the extended part model are combined with each other, the domain object model part of the baseline data model and the domain object model part of the extended part model are combined with each other, and the data object model part of the baseline data model and the data object model part of the extended part model are combined with each other.

After the expansion is completed, the expansion of the target application is completed, further, the baseline data model metadata and the expansion part data model metadata can be loaded through the metadata engine, the expanded target application is further obtained, and the process of the actual running of the application is established.

Further, in the first embodiment of the present application, the baseline data model is extended, and meanwhile, the updating and upgrading of the extended data model are also related, specifically, in the present application, the updating refers to updating of an extended part data model in the extended data model, and the upgrading refers to upgrading of a baseline data model part of the extended data model.

The upgrading of the extended data model comprises the following steps S4 to S6:

step S4, incremental data model metadata for upgrading the baseline data model is obtained;

step S5, upgrading the baseline data model metadata according to the incremental data model metadata to obtain upgraded baseline data model metadata;

and S6, the metadata engine reads the updated baseline data model metadata and the extended part data model metadata, combines the updated baseline data model metadata with the extended part data model metadata, and obtains extended data model metadata of which the baseline data model metadata is partially updated.

The incremental data model metadata of the updated baseline data model is generally provided by a provider of the target application (i.e. the first user 1 in the embodiment), but is not excluded from being provided by other third-party users, so that the original baseline data model is updated based on the incremental data model metadata to obtain updated baseline data model metadata, and then the updated baseline data model is combined with the extended part data model metadata through a metadata engine to obtain updated extended data model metadata.

The updating of the extended data model means updating of metadata of the extended data model, and includes the following steps S7 to S9:

step S7, obtaining the metadata of the expansion part data model for updating the metadata of the expansion part data model;

step S8, updating the original extended part data model metadata by using the extended data model metadata for updating to obtain updated extended part data model metadata;

and step S9, the metadata engine reads the updated extended part data model metadata and the baseline data model metadata to obtain updated extended data model metadata.

The updating extension data model metadata for updating the extension data model metadata can be obtained from a metadata warehouse of a target application user (namely, a second user 2), and the updating of the original extension data model metadata is achieved through combining with the original extension data model metadata or directly using a method for replacing the updating extension data model metadata, and then a metadata engine reads the updated extension data model metadata and the baseline data model metadata to obtain updated extension data model metadata for use in a process of the second application program.

According to the data model expansion method, on the premise that the baseline data model metadata are in a protected state which cannot be changed, the baseline data model metadata and the expansion part data model metadata corresponding to the target application scene are read through the metadata engine, and the expansion part data model metadata and the baseline data model metadata are combined to complete expansion of the baseline data model metadata. The method ensures that the original baseline data model metadata is not changed while expanding the baseline data model metadata.

Corresponding to the second embodiment of the present application, a third embodiment of the present application provides a method for updating a data model, where the method for updating is that the extended data model is already established on the application platform of the second user 2, and an extended portion of the extended data model needs to be updated, and the method for updating is adopted at this time; in actual use, the updating method is suitable for updating processes in which the target application is already established and used by the second user 2, and may exist at any time during the use according to the need or the target environment adjustment. Since the basic content of this method embodiment is already provided in the method for expanding the data model provided in the second embodiment of the present application, the description herein is relatively simple, and reference should be made to the description related to the second embodiment of the present application for relevant points.

Referring to fig. 6, fig. 6 is a flowchart of a method for updating a data model according to a third embodiment of the present application, and the method includes steps S601 to S603 as follows:

step S601, obtaining the metadata of the expansion part data model for updating the metadata of the expansion part data model;

step S602, updating original extended part data model metadata through the updated extended part data model metadata to obtain updated extended part data model metadata;

Step S603, the metadata engine reads the updated extended portion data model metadata and the baseline data model metadata, and combines them to obtain updated extended data model metadata; and using the updated extended data model metadata in the established application program process.

Optionally, the baseline data model metadata and the extended portion data model metadata each include: domain object model, data object model, structure object model.

In correspondence to the second embodiment of the present application, a fourth embodiment of the present application provides an expansion device for a data model, please refer to fig. 7, fig. 7 is a schematic structural diagram of the expansion device for a data model provided in the fourth embodiment of the present application. Because the embodiment of the device is basically similar to the extension method of the data model provided by the first embodiment of the application, the description is simpler, and the relevant parts only need to refer to the description of the first embodiment of the application, and the description is omitted here.

As shown in fig. 7, the expanding device of the data model includes:

a first obtaining unit 701, configured to obtain baseline data model metadata, where the baseline data model metadata is in a read-only state;

An obtaining unit 702, configured to obtain, for a requirement of a target application scenario, metadata of an extended portion data model for extending the baseline data model;

and the expansion unit 703 is configured to read the baseline data model metadata and the expansion part data model metadata through a preset metadata engine, combine the baseline data model metadata and the expansion part data model metadata to form expanded data model metadata, and use the expanded data model metadata in a process established for the second application program.

The metadata engine reading the baseline data model metadata and the extended portion data model metadata, combining the extended portion data model metadata with the baseline data model metadata to form extended data model metadata, comprising:

the baseline data model metadata and the corresponding field object model metadata, the data object model metadata and the structure object model metadata in the extended part data model metadata are correspondingly combined into extended field object model metadata, data object model metadata and structure object model metadata;

and according to the mapping relation among the object model metadata, the extended structural object model metadata, the domain object model metadata and the data object model metadata are combined with each other to obtain the extended data model metadata.

Optionally, the obtaining, for the requirement of the target application scenario, metadata of an extended portion data model for extending the baseline data model includes:

obtaining an expansion request for application expansion based on the baseline data model;

Optionally, the obtaining baseline data model metadata includes:

the baseline data model metadata is published along with the target application through a publishing platform;

and downloading the target application, thereby obtaining the baseline data model metadata.

Optionally, the obtaining the baseline data model metadata by downloading the target application includes:

And downloading the target application to a visual designer of the target application, and displaying a corresponding visual model through the visual designer according to the baseline data model metadata.

Optionally, the device is further configured to:

Optionally, in the apparatus, the metadata engine operates in a mirrored environment.

In correspondence to the third embodiment of the present application, the fifth embodiment of the present application provides a device for updating a data model at the same time, please refer to fig. 8, fig. 8 is a schematic structural diagram of the device for updating a data model provided in the fifth embodiment of the present application. Since the embodiment of the device is substantially similar to the third embodiment, the description is relatively simple, and the relevant parts in the third embodiment and the second embodiment of the present application need only be referred to for description, which is not repeated herein.

As shown in fig. 8, the updating device of the data model includes:

a second obtaining unit 801 for obtaining extended part data model metadata for updating the extended part data model metadata;

a third obtaining unit 802, configured to obtain updated extended part data model metadata by updating the original extended part data model metadata with the extended part data model metadata for updating;

and an updating unit 803, configured to read, by the metadata engine, the updated extended portion data model metadata and the baseline data model metadata, combine the two to obtain updated extended data model metadata, and use the updated extended data model metadata in the established application program process.

Optionally, the metadata engine reads the baseline data model metadata and the updated extended portion data model metadata, and combines them to form extended data model metadata, including:

Optionally, the baseline data model metadata is obtained by:

The baseline data model metadata is published along with the first application program through a publishing platform;

Referring to fig. 9, fig. 9 is a schematic structural diagram of an electronic device according to a sixth embodiment of the present application.

The electronic device includes: at least one processor 901, at least one memory 902, at least one communication interface 903, and at least one communication bus 904;

alternatively, the communication interface 904 may be an interface of a communication module, such as an interface of a GSM module;

the processor 901 may be a CPU or a specific integrated circuit ASIC (APPlicationSpecific IntegratedCircuit) or one or more integrated circuits configured to implement embodiments of the present application;

the memory 902 may comprise high-speed RAM memory or may further comprise non-volatile memory (non-volatile memory), such as at least one disk memory.

The memory 902 is a program for storing a method, where the program, when read and executed by a processor, performs a method provided by an embodiment of a method of the present application.

Another embodiment of the present application provides a computer storage medium storing a computer program that when executed performs a method according to an embodiment of the present application.

It should be noted that, the detailed descriptions of the apparatuses and the computer storage medium provided in the embodiments of the present application may refer to the related descriptions of the first embodiment and the second embodiment provided in the present application, which are not repeated herein.

While the preferred embodiment has been described, it is not intended to limit the invention thereto, and any person skilled in the art may make variations and modifications without departing from the spirit and scope of the present invention, so that the scope of the present invention shall be defined by the claims of the present application.

In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

1. Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer readable media, as defined herein, does not include non-transitory computer readable media (transmission media), such as modulated data signals and carrier waves.

2. Those skilled in the art will appreciate that embodiments of the present application may be provided as a system or an electronic device. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Claims

1. The system for publishing the data model of the application program is characterized by comprising a first user platform, a second user platform and an application publishing platform;

2. The system for publishing a data model of an application of claim 1, further comprising: the first user platform issues an upgrade version of the baseline data model metadata through the application issuing platform, and the upgrade version is in a read-only state;

3. The system for publishing a data model of an application of claim 1, further comprising:

4. The system for publishing a data model of an application of claim 1, further comprising:

5. A method for extending a data model of an application, wherein a second application running platform for running a second user platform of the application comprises:

6. The method of claim 5, wherein the baseline data model metadata, the extended portion data model metadata, each respectively comprise: domain object model metadata, data object model metadata, structure object model metadata.

7. The method of claim 6, wherein the metadata engine reading the baseline data model metadata and the extended portion data model metadata, combining the extended portion data model metadata with the baseline data model metadata to form second application data model metadata, comprises:

8. The method of claim 5, wherein the obtaining extended portion data model metadata for extending the baseline data model for the requirements of the target application scenario comprises:

9. The method of claim 5, wherein the obtaining baseline data model metadata comprises:

10. The method of claim 9, wherein obtaining the baseline data model metadata by downloading the first application program comprises:

11. The method of claim 5, wherein the method further comprises:

12. The method of claim 5, wherein the method further comprises:

13. An electronic device, comprising:

a processor;

a memory for storing a program of methods, which when read and executed by a processor performs the method of any of claims 5-12.

14. A computer storage medium, characterized in that the computer storage medium stores a computer program which, when executed, performs the method of any of claims 5-12.