A system based on metadata model to realize a design with thousands of faces

Abstract

The present invention provides a system based on a metadata model to realize one-time design and display of thousands of faces, including: a metadata model design module, which is used to generate a standard interactive interface metadata model by using a preset development interface designer in the development stage of the interactive interface The custom model generation module is used to generate at least one custom interactive interface metadata model based on a standard interactive interface metadata model using a preset custom interface designer during the running phase of the interactive interface; the interface information distribution module is used for Assign the custom interactive interface metadata model to the pre-configured operation object to establish the association relationship between the custom interactive interface metadata model and the operation object; the interactive interface display module is used to obtain the corresponding custom interface according to the operation object matching The metadata model of the interactive interface, and display the interactive interface formed by customizing the metadata model of the interactive interface. The beneficial effect is that standard products only need to maintain a set of codes to display different interfaces.

Description

Technical field [0001] The present invention relates to the field of software development, and in particular, to a system based on a metadata model to achieve a set of thousands of faces. Background technique [0002] The existing software interactive interface implementation is generally written directly by fixed writing source code, and the disadvantage of this implementation is: [0003] 1) When the business changes, the interface needs to be adjusted, and the source code must be modified, then re-released, deploy software; [0004] 2) When using this set of software, many customers are inconsistent with the requirements of the interactive interface layout of different services, the development team must divide many different source code branches for these customers, resulting in simultaneous maintenance of large source code, Added development, test costs; [0005] 3) When customers are multi-group, multi-organizational architecture large enterprises, each business unit, organ...

AI Technical Summary

Problems solved by technology

[0003] 1) When the business changes and the interface needs to be adjusted, the source code must be modified, and then the software must be republished and deployed;

[0004] 2) When there are many customers using this set of software, and many customers have inconsistent requirements for the layout of the interactive interface of different businesses, the development team must separate many different source code branches for these customers, resulting in the need to maintain a large number of source codes at the same time. Increased development and testing costs;

[0005] 3) When the customer is a large enterprise with multi-group and multi-organizational structure, and each business unit and organization has inconsistent requirements for the interactive interface of the same business point, the way of fixedly writing source code to deploy a set of codes only has one set of interactive interface, which cannot satisfy This business scenario;

[0006] 4) The Saas software system deploys a set of codes. In the multi-tenant mode, different tenants require to display business scenarios with different interfaces, which cannot be satisfied by this implementation;

[0007] In order to meet the individual needs of different business units and organizations of large-scale enterprises with multi-organizational structures on the interactive interface, some existing enterprise-level application development platforms have transformed the interactive interface into metadata, which can support the readjustment of the interactive interface during the operation phase, and the allocation Personalized interactive interface; however, there is also a common problem in this development platform: the standard product development stage and the secondary development stage use the same interface designer and the same interactive interface metadata model, and the design-time interactive interface metadata is not included. The model is decoupled from the metadata model of the interactive interface at runtime, which requires that the metadata model of the interactive interface that the interface designer relies on during the development phase cannot be reconstructed at will, otherwise it is easier to upgrade the metadata model of the interactive interface when the version is upgraded Encountered the problem of incompatibility of the metadata model format of the interactive interface, which made it difficult to upgrade

Furthermore, the metadata model of the interactive interface that the interface designer relies on in the development stage has a complex data format and contains too much attribute information at design time. A large amount of attribute information at design time is useless in the running stage

[0008] In the actual enterprise-level application software development process, in the standard product development stage, the development activities are mainly interface design, metadata design, and computer program code writing. The whole process is relatively complicated and requires relatively high development skills for developers. At this stage The functions of the interface designer used by most developers are often more complex; and in the secondary development stage, the development activities become relatively simple interface adjustments and script writing, and the skill requirements for secondary developers are relatively low. At this time, The interface designer in the standard product development stage is too complicated and unfriendly for secondary developers. It is expensive to learn and difficult to control, and it is easy to introduce errors during secondary development.

Images