Tree data dictionary maintenance system and method

Abstract

The invention discloses a tree data dictionary maintenance system and method, and belongs to the field of data dictionary maintenance, aiming to solve the technical problem of how to flexibly and efficiently manage basic data. The tree data dictionary maintenance system comprises a data dictionary category definition module used for creating a data dictionary and configuring category information,authorization information and maintenance rules of the data dictionary, a data dictionary definition module which is used for acquiring service data and calling the data dictionary category definitionmodule to maintain the data, and a data interface which is used for providing the maintained data to a service system. According to the tree data dictionary maintenance method, the service data is maintained through the maintenance system, and the maintained service data is provided for each service system.

Description

technical field [0001] The invention relates to the field of data dictionary maintenance, in particular to a tree-like data dictionary maintenance system and method. Background technique [0002] With the continuous development of enterprises, the requirements for information technology in enterprise management continue to increase. In the informatization projects of modern enterprises, some requirements for flexible expansion of system data attributes and synchronization of master data during multi-system integration are often encountered. However, most of the management software on the market mainly adopt solutions to develop forms or functions for different individual requirements when facing these requirements. This solution brings the following problems to the information construction of enterprises: [0003] 1. Repeated development wastes limited development resources [0004] The form styles or functional characteristics in this type of requirements are almost the sa...

AI Technical Summary

Problems solved by technology

[0003] 1. Repeated development wastes limited development resources

[0004] The form styles or functional characteristics in this type of requirements are almost the same, but the business data operated is different, so the form or function developed separately for each requirement is actually a kind of repeated development, which violates the reusable principle of software engineering , which increases the research and development investment of software manufacturers, and the consumption of limited development resources on repetitive work will undoubtedly prolong the research and development cycle and increase the enterprise's information investment

[0005] 2. Poor expandability, need to re-invest funds for development when subsequent business changes

[0006] The operating environment of today's enterprises is changing all the time, and the corresponding demand for information systems is also changing all the time. Forms or functions developed separately for each business are bound to be unable to adapt to changing needs due to their special limitations. Therefore, when When the demand changes, modify and re-invest development resources to modify the original function, which will lead to an increase in the cost of enterprise information construction and increase the burden on the enterprise

[0007] 3. Scattered forms or functions are not convenient for unified management by classification

[0008] Independently developed forms or functions are generally scattered among the functional modules of the information system in the form of independent menus, which requires business personnel to remember the location of each menu accurately, which is not conducive to the unified management of business personnel, and often occurs Problems affecting business operations due to inability to find a certain menu

[0009] 4. Lack of integration interface with heterogeneous systems, which increases the cost of enterprise cross-system business integration

[0010] If there is no special requirement for independent development of forms or functions, data access interfaces are often not provided, which creates obstacles for possible cross-system business integration in the subsequent process of enterprise informatization. When there is a need for system integration, the enterprise needs to re-invest funds for development Relevant data access interfaces will not only increase the cost of enterprises, but also delay the cycle of enterprise business system integration

Images