Physical model processing method, device, electronic equipment and computer storage medium

Abstract

The embodiment of the present application relates to the field of data processing technology, and discloses a physical model processing method, device, electronic device and computer storage medium, wherein the physical model processing method includes: designing a physical model through a physical model design module according to English roots, data items and option codes included in a data dictionary module, wherein English roots are abbreviations of English words, data items are obtained by splicing English roots, and option codes are description information of the data value of a data item; then, branch management and / or version management of the designed physical model are performed through a basic function management module, and the update of the designed physical model is reviewed. This allows the use of a uniformly formulated data dictionary to achieve uniform entry and standardized management, thereby standardizing the definition of the physical model, facilitating unified implementation of standards, and allowing the physical model to be flexibly branched and versioned, and the change of the physical model to be subject to authority control.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of data processing technology. Specifically, the present application relates to a physical model processing method, device, electronic device and computer storage medium. Background Art

[0002] At present, in the physical model design process of enterprise information systems, physical model design is mainly carried out through database management tools or database command line mode. In the physical model design process, since multiple batches of tasks are developed in parallel or one after another, each task maintains its own physical model during the development process.

[0003] However, during the specific implementation process, the inventors of this application discovered that the current development model of physical models has led to a lack of unified data standards for various physical models and inconsistent definitions of physical models in different systems, making it impossible to implement standards. In addition, it is impossible to flexibly perform branch management and version management on the physical models according to different schedules and development tasks, nor is it possible to perform corresponding authority control on changes to the designed physical models. Summary of the invention

[0004] The purpose of the embodiments of the present application is to solve at least one of the above technical defects, and the following technical solutions are proposed:

[0005] In one aspect, a physical model processing method is provided, comprising:

[0006] According to the English root words, data items and option codes included in the data dictionary module, the physical model is designed through the physical model design module, wherein the English root words are abbreviations of English words, the data items are obtained by splicing the English root words, and the option codes are description information of the data values ​​of the data items;

[0007] The basic function management module is used to perform branch management and / or version management on the designed physical model, and to review updates to the designed physical model.

[0008] In a possible implementation, before designing the physical model through the physical model design module according to the English word roots, data items and option codes included in the data dictionary module, the following is also included:

[0009] Create a root word library and a data item information library. The root word library is a database storing multiple English root words, and the data item information library is a database maintaining data information of multiple data items.

[0010] The data information of each English root in the root database includes at least one of the following:

[0011] Root name, root type, full English name of the root, Chinese description of the root, creator of the root and creation time of the root;

[0012] The data information of each data item in the data item information library includes at least one of the following:

[0013] Data item type, data item name, English name, Chinese name, data item status, encoding rule, data type, data length, maximum data value, minimum data value, amount unit, business definition, business rule, number of associated option code, creator of the data item and creation time of the data item.

[0014] In a possible implementation, before designing the physical model through the physical model design module according to the English word roots, data items and option codes included in the data dictionary module, the following is also included:

[0015] The data item is associated with the option code, and the option code is used to represent the value range of the data item;

[0016] The data information of each option code includes at least one of the following:

[0017] The option code’s name, Chinese code, English name, usage status, option value, description of the option value, creator of the option code, and creation time of the option code.

[0018] In a possible implementation, the physical model is designed by the physical model design module according to the English root words, data items and option codes included in the data dictionary module, including:

[0019] Design the physical model by designing the physical table through the physical model design module according to the English root, data item and option code;

[0020] The data information of the physical table at least includes basic information, field information, primary key information and index information, and the basic information at least includes the table name and the corresponding database type.

[0021] In a possible implementation, the design of the physical table includes a new creation process of the physical table or a change process of the physical table;

[0022] Among them, the physical table is designed through the physical model design module according to the English root, data item and option code, including:

[0023] When the design of the physical table is a new creation of the physical table, a new physical table is created according to the English root, data item and option code, basic information and field information are added to the new physical table, and version information of the new physical table is saved;

[0024] When the design of the physical table is a change process of the physical table, the basic information and field information of the physical table to be changed are changed according to the English root, data item and option code, and the version information of the changed physical table is saved.

[0025] In a possible implementation, after adding basic information and field information to the newly created physical table, the method further includes: adding at least one of primary key information or index information to the newly created physical table;

[0026] After the basic information and field information of the physical table to be changed are changed, the method further includes: changing at least one of the primary key information or the index information of the physical table to be changed.

[0027] In one possible implementation, the update of the physical model of the design is reviewed, including:

[0028] Review the newly created physical table or the changed physical table to determine whether the newly created physical table or the changed physical table meets the requirements.

[0029] In one aspect, a physical model processing device is provided, comprising:

[0030] A first processing module is used to design the physical model through a physical model design module according to English roots, data items and option codes included in the data dictionary module, wherein the English roots are abbreviations of English words, the data items are obtained by splicing the English roots, and the option codes are description information of data values ​​of the data items;

[0031] The second processing module is used to perform branch management and / or version management on the designed physical model through the basic function management module, and to review the update of the designed physical model.

[0032] In a possible implementation, the device further includes a creation module;

[0033] A creation module is used to create a root word library and a data item information library. The root word library is a database storing multiple English root words, and the data item information library is a database maintaining data information of multiple data items.

[0034] The data information of each English root in the root database includes at least one of the following:

[0035] Root name, root type, full English name of the root, Chinese description of the root, creator of the root and creation time of the root;

[0036] The data information of each data item in the data item information library includes at least one of the following:

[0037] Data item type, data item name, English name, Chinese name, data item status, encoding rule, data type, data length, maximum data value, minimum data value, amount unit, business definition, business rule, number of associated option code, creator of the data item and creation time of the data item.

[0038] In a possible implementation, the device further includes a third processing module;

[0039] A third processing module is used to associate the data item with the option code, where the option code is used to represent the value range of the data value of the data item;

[0040] The data information of each option code includes at least one of the following:

[0041] The option code’s name, Chinese code, English name, usage status, option value, description of the option value, creator of the option code, and creation time of the option code.

[0042] In a possible implementation manner, the first processing module is specifically configured to:

[0043] Design the physical model by designing the physical table through the physical model design module according to the English root, data item and option code;

[0044] The data information of the physical table at least includes basic information, field information, primary key information and index information, and the basic information at least includes the table name and the corresponding database type.

[0045] In a possible implementation, the design of the physical table includes a new creation process of the physical table or a change process of the physical table;

[0046] Wherein, the first processing module is specifically used for:

[0047] When the design of the physical table is a new creation of the physical table, a new physical table is created according to the English root, data item and option code, basic information and field information are added to the new physical table, and version information of the new physical table is saved;

[0048] When the design of the physical table is a change process of the physical table, the basic information and field information of the physical table to be changed are changed according to the English root, data item and option code, and the version information of the changed physical table is saved.

[0049] In a possible implementation, after adding basic information and field information to the newly created physical table, the first processing module is further configured to: add at least one of primary key information or index information to the newly created physical table;

[0050] After performing change processing on basic information and field information of the physical table to be changed, the first processing module is further used to: perform change processing on at least one of primary key information or index information of the physical table to be changed.

[0051] In a possible implementation, when reviewing the update of the designed physical model, the second processing module is used to:

[0052] Review the newly created physical table or the changed physical table to determine whether the newly created physical table or the changed physical table meets the requirements.

[0053] On the one hand, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the above-mentioned physical model processing method is implemented when the processor executes the program.

[0054] On the one hand, a computer-readable storage medium is provided, on which a computer program is stored, and when the program is executed by a processor, the above-mentioned physical model processing method is implemented.

[0055] The physical model processing method provided in the embodiment of the present application designs the physical model according to the English roots, data items and option codes included in the data dictionary module, so that the design of the physical model of each system can adopt the data dictionary uniformly formulated by the enterprise to achieve unified entry and standardized management, thereby standardizing the definition of the physical model and facilitating unified implementation of standards; by performing branch management and / or version management on the designed physical model, flexible branch management and version management of the physical model according to different schedules and development tasks is achieved, and by reviewing the update of the designed physical model, the review of the changes to the designed physical model is achieved, so that corresponding authority control can be performed on the changes to the designed physical model.

[0056] Additional aspects and advantages of the embodiments of the present application will be partially given in the description below, which will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] The above and / or additional aspects and advantages of the embodiments of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0058] Figure 1 A schematic diagram of a physical model processing method according to an embodiment of the present application;

[0059] Figure 2 A schematic diagram of a physical model processing architecture according to an embodiment of the present application;

[0060] Figure 3A schematic diagram of the process of constructing a data dictionary according to an embodiment of the present application;

[0061] Figure 4 A schematic diagram of the physical model design process of an embodiment of the present application;

[0062] Figure 5 A schematic diagram of the basic structure of a physical model processing device according to an embodiment of the present application;

[0063] Figure 6 A schematic diagram of the structure of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0064] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be interpreted as limiting the present application.

[0065] It will be understood by those skilled in the art that, unless expressly stated, the singular forms "one", "said", and "the" used herein may also include plural forms. It should be further understood that the term "comprising" used in the specification of the present application refers to the presence of the features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof. It should be understood that when we refer to an element as being "connected" or "coupled" to another element, it may be directly connected or coupled to the other element, or there may be an intermediate element. In addition, the "connection" or "coupling" used herein may include wireless connection or wireless coupling. The term "and / or" used herein includes all or any unit and all combinations of one or more associated listed items.

[0066] In order to make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the implementation methods of the present application will be further described in detail below in conjunction with the accompanying drawings.

[0067] The following specific embodiments are used to describe in detail the technical solutions of the embodiments of the present application and how the technical solutions of the embodiments of the present application solve the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0068] An embodiment of the present application provides a physical model processing method, which is executed by a computer device, which may be a terminal or a server. The terminal may be a desktop device or a mobile terminal. The server may be an independent physical server, a physical server cluster, or a virtual server. Figure 1 As shown, the method includes:

[0069] Step S110, designing a physical model through the physical model design module according to the English roots, data items and option codes included in the data dictionary module, wherein the English roots are abbreviations of English words, the data items are obtained by concatenating the English roots, and the option codes are description information of the data values ​​of the data items; Step S120, performing branch management and / or version management on the designed physical model and reviewing the update of the designed physical model through the basic function management module.

[0070] The overall architecture of the embodiment of the present application is mainly divided into three parts: data dictionary module, physical model design module, and basic function module. Among them, the data dictionary module includes English roots, data items and option codes, that is, the data dictionary of the data dictionary module is a general term for English roots, option codes and data items. According to the scope of application, the data dictionary can be subdivided into enterprise-level data dictionary and system-level data dictionary.

[0071] English root words, also known as abbreviations, are the abbreviations of English words. English root words use important letters in English words / phrases to represent the meaning of the entire word / phrase, and are generally represented by 3 to 4 capital letters. The English root word library is uniformly formulated by the company's data standards or relevant departments that formulate specifications. It is the basis of the entire data dictionary. Enterprise-level data items and system-level data items are based on the same set of English root word libraries.

[0072] Data items are composed of English root words and are used to describe the detailed definition of business elements. In the logical model, they correspond to the attributes in the entity and in the physical model, they correspond to the fields in the physical table. They can be subdivided into enterprise-level data items and system-level data items. Among them, enterprise-level data items are uniformly formulated by the company's data standards or relevant departments that formulate specifications. The collection of enterprise-level data items is collectively referred to as the enterprise-level data dictionary; system-level data items are data items unique to each business system, maintained by each system itself, and only visible and available to each system itself. The collection of system-level data items is collectively referred to as the system-level data dictionary.

[0073] In actual applications, when designing physical models, each system should give priority to the use of enterprise-level data dictionaries. If the existing enterprise-level data dictionary does not meet the needs, an application process can be initiated in the system to increase the content of the data dictionary after approval by the company's data standards or relevant departments that formulate specifications.

[0074] The option code is a description of the data value information of the data item, that is, the option code is the description information of the data value of the data item. The data item can be associated with the option code to define the value range of the data item. For example, the value of the option code gender includes male|female, and male|female is the code value information of the option code. Among them, the option code can be subdivided into enterprise-level option code and system-level option code according to the scope of application.

[0075] The physical model design module provides online design functions for physical models. In practical applications, physical models can be designed through the physical model design module based on English roots, data items and option codes.

[0076] The basic function module can perform branch management and / or version management on the designed physical model, as well as audit the update of the designed physical model. In other words, the basic function module can provide branch management and version management functions, and can also provide design audit functions, among which the branch management function mainly provides the management function of production branches and development branches for physical tables. The development branch can manage multiple development branches according to different schedules and development tasks. Different branches correspond to different versions, and provide version comparison functions to analyze the differences between different versions. The design audit function mainly refers to the permission audit function. The permission audit function provides permission control and online audit functions for changes to the designed physical model. Changes to the designed physical model can only take effect after approval by the authorized reviewers of each system.

[0077] The physical model processing method provided in the embodiment of the present application designs the physical model according to the English roots, data items and option codes included in the data dictionary module, so that the design of the physical model of each system can adopt the data dictionary uniformly formulated by the enterprise to achieve unified entry and standardized management, thereby standardizing the definition of the physical model and facilitating unified implementation of standards; by performing branch management and / or version management on the designed physical model, flexible branch management and version management of the physical model according to different schedules and development tasks is achieved, and by reviewing the update of the designed physical model, the review of the changes to the designed physical model is achieved, so that corresponding authority control can be performed on the changes to the designed physical model.

[0078] The physical model processing method of the embodiment of the present application is specifically introduced below:

[0079] Figure 2 The overall architecture of the embodiment of the present application is given. Figure 2 The data dictionary module includes English roots, data items and option codes; the physical model design module includes model design and model import; the basic function management module includes design review, branch management and version management.

[0080] Model design is a forward online design function of the physical model provided by the physical model design module, including basic information of the physical table, field information, primary key, index, etc.; among them, the basic information includes the physical table name, corresponding database type, etc. The physical table fields can be generated by referencing the enterprise-level data dictionary or system-level data dictionary, and specific fields can be selected as primary keys or index fields.

[0081] Model import is a reverse import function of the existing physical model provided by the physical model design module. By configuring specific database information, the corresponding physical table information in the database can be directly extracted. Among them, the fields of the physical table will automatically generate system-level data items and automatically associate with the fields of the generated physical model. The export function can export the basic information, field information, primary key, index, etc. of the physical table in Excel. Different information is stored in different tabs.

[0082] In a possible implementation, before designing the physical model through the physical model design module according to the English roots, data items and option codes included in the data dictionary module, it also includes: creating a root library and a data item information library, the root library is a database storing multiple English roots, and the data item information library is a database maintaining data information of multiple data items; wherein the data information of each English root in the root library includes at least one of the following: root name, root type, full English name of the root, Chinese description of the root, root creator and root creation time; the data information of each data item in the data item information library includes at least one of the following: data item type, data item name, English name, Chinese name, data item status, encoding rule, data type, data length, maximum data value, minimum data value, amount unit, business definition, business rule, number of associated option code, creator of the data item and creation time of the data item.

[0083] In addition, before designing the physical model through the physical model design module based on the English roots, data items and option codes included in the data dictionary module, the data items and option codes can also be associated with each other. The option code is used to represent the value range of the data value of the data item; wherein the data information of each option code includes at least one of the following: the name of the option code, Chinese code, English name, usage status, option value, description information of the option value, the creator of the option code and the creation time of the option code.

[0084] In actual applications, data dictionaries can be divided into enterprise-level data dictionaries and system-level data dictionaries according to their scope of use. The creation principle of system-level data dictionaries is the same as that of enterprise-level data dictionaries, but the creators are different. Enterprise-level data dictionaries are uniformly formulated by the company's data standards or relevant departments that formulate specifications, while system-level data dictionaries are formulated by each system model manager. The following takes the creation of an enterprise-level data dictionary as an example for specific explanation. Among them, the creation process of an enterprise-level data dictionary is as follows: Figure 3 As shown, the specific steps may be:

[0085] Step 1: Create a root library for English roots

[0086] The root word library stores multiple English root words, which are uniformly formulated by the company's data standards or relevant departments that formulate specifications. English root word maintenance information (i.e., the data information of each English root word in the English root word library) includes root word name, root word type, root word English full name, root word Chinese description, root word creator, creation time, etc. A single English root word is represented by 3 to 5 uppercase letters, such as the English root word CNTR, the root word type is word, the root word English full name is country, the root word Chinese description is country, the root word creator is Zhang San, etc. Another example is the English root word CITIC, the root word type is phrase, the root word Chinese description is China CITIC Bank, and so on.

[0087] Step 2: Develop a data item information library for enterprise-level data items

[0088] The data item information library maintains multiple data items, which are uniformly formulated by the company's data standards or relevant departments that formulate specifications, and are formed based on the company's business scenarios. Data item maintenance information (i.e., data information of each data item) includes: data item type, data item name, English name, Chinese name, data item status, encoding rules, data type, data length, data maximum value, data minimum value, amount unit, business definition, business rules, number of associated option codes, creator, creation time, etc. Different fields need to be maintained according to different data item types. For example, when the data type is amount, maintain the amount unit.

[0089] The data item name is composed of English root words, such as the data item CNTY_RGON_COD, the Chinese name is country and region, the English name is Country / Region Code, the data item type is code, the data item status is enabled, the data length is 5, the associated option code number is OptionCode001, the business definition refers to the unified code of countries and regions in the world, and the business rules use three-digit alphabetic codes.

[0090] Step 3: Data item associated option code

[0091] It is not necessary to associate option codes with data items. For example, if the country and region fields have a certain range of values, then an option code should be developed and associated. For another example, if the creation time is random, then such data items do not need to be associated with option codes. When associating data items with enterprise-level option codes, you need to develop enterprise-level option codes first, and then associate the data items with the enterprise-level option codes. Specifically, it can be:

[0092] Step 3.1: Create an enterprise-level option code

[0093] Option codes are used to specify the range of data values ​​for the number of data items. The maintenance information of option codes (i.e., the data information of each option code) includes option code name, Chinese number, English name, status, option value, option value description, creator, creation time, etc. For example, option code OPTIONCODE0001, Chinese name country and region, English name Country / Region Code, status enabled, option value 001, option value description Afghanistan, option value 002, option value description Albania, etc.

[0094] Step 3.2: Associate data items with enterprise-level option codes

[0095] Select the associated option code on the data item maintenance page. After association, the value range of the data item is the option value range of the option code. If a field in the physical table is associated with the data item, the value range of this field in the physical table is also the option value range of the option code. If it exceeds this value range, the data is judged to be incorrect in order to achieve unified implementation of standards.

[0096] In a possible implementation, a physical model is designed through a physical model design module according to English roots, data items and option codes included in a data dictionary module. Specifically, the physical model is designed by designing a physical table through a physical model design module according to English roots, data items and option codes; wherein the data information of the physical table includes at least basic information, field information, primary key information and index information, and the basic information includes at least a table name and a corresponding database type.

[0097] In one case, the design of the physical table includes the creation of a new physical table or the modification of the physical table; wherein, the design of the physical table is performed through a physical model design module according to English roots, data items and option codes, and specifically can be: when the design of the physical table is the creation of a new physical table, a new physical table is created according to English roots, data items and option codes, basic information and field information are added to the new physical table, and version information of the new physical table is saved; when the design of the physical table is the modification of the physical table, basic information and field information of the physical table to be modified are modified according to English roots, data items and option codes, and version information of the modified physical table is saved.

[0098] Among them, after adding basic information and field information to the newly created physical table, at least one of primary key information or index information can also be added to the newly created physical table; after changing the basic information and field information of the physical table to be changed, at least one of primary key information or index information can also be changed for the physical table to be changed.

[0099] Reviewing the update of the designed physical model, specifically, reviewing the newly created physical table or the changed physical table to determine whether the newly created physical table or the changed physical table meets the requirements.

[0100] Physical model design refers to the design of physical tables. The maintenance information of physical tables includes: basic information, table fields, table primary keys, table indexes, etc. Physical model design is carried out in the development branch, which is specifically divided into two types: creation of physical tables and changes to physical tables. New physical tables are not available in the production branch. They are added for this launch, also known as tables added to this schedule. There can be multiple development tasks under one schedule, and each development task can create a new physical table. Changes to physical tables are made through checkout operations to the corresponding schedule and development branch, and then modifications are made based on the production branch. Users can only maintain the creation or change of physical models under authorized systems. Among them, Figure 4 The overall process of creating a new physical table or changing a physical table is given below. Figure 4 Taking a scheduled maintenance process as an example, the following describes the creation or modification of a physical table:

[0101] The specific steps can be:

[0102] Step 1: Determine whether this physical table design is a new physical table addition or a physical table change. If it is a new physical table addition, proceed to step 2; if it is a physical table change, proceed to step 3.

[0103] Step 2: Create a new physical table operation

[0104] Step 2.1, add basic table information, that is, add basic information of the physical table, including: system, table name, table Chinese name, database type, table space name, index space name, remarks, etc.

[0105] Step 2.2, add table field information, that is, add field information of the physical table, where table fields are generated by associating data items. Depending on the specific situation, enterprise-level data items or system-level data items can be associated. The basic information of the table fields is directly generated from the basic information of the data items, including field name, English name, Chinese name, data type, length, encoding rule, maximum value, minimum value, etc. The option code information associated with the data item will also be automatically associated with the field to limit the value range of the field.

[0106] Step 2.3, add table primary key information (that is, add physical table primary key information): Select individual table fields in step 2.2 as table primary key fields. This step is not necessary.

[0107] Step 2.4, add table index information (i.e. add physical table index information): select individual table fields in step 2.2 as table index fields. This step is not necessary.

[0108] Step 2.5: The version number of the newly created physical table is automatically generated, and the default is 1.00.00.

[0109] 3. Change physical table operation

[0110] Step 3.1. Query the table that is already in the production branch and check it out to the development branch. The version number of the physical table to be changed is automatically generated according to the production branch version number. If the version of the production branch is 1.00, the version checked out to the development branch is 1.00.01. It can be checked out once per schedule.

[0111] Step 3.2: Modify the basic information of the table, that is, modify the basic information of the physical table;

[0112] Step 3.3, modify the table field information, that is, modify the field information of the physical table;

[0113] Step 3.4: Modify the primary key information of the table, that is, modify the primary key information of the physical table;

[0114] Step 3.5: Modify the table index information, that is, modify the index information of the physical table;

[0115] Step 4: Save the addition or change of the physical table to obtain the newly created physical table or the changed physical table.

[0116] Step 5, Design Review: If the review fails, the addition or change of the physical table will not take effect and needs to be modified and re-initiated for review. If the review passes, it will be automatically checked in to the production branch when it is scheduled to go online. After the newly created physical table 1.00.00 is checked in, the corresponding production branch version of the table is 1.00. After the changed physical table 1.00.01 is checked in to production, the corresponding production branch version of the table is 1.01.

[0117] The physical model processing method of the embodiment of the present application is specifically introduced below through specific examples:

[0118] Assume that system A starts a new scheduling task with the scheduling number 00001. During this scheduling period, the customer income situation collection must be completed and customer grade type information must be added to the customer basic information page.

[0119] 1. Determine the scope of physical model design

[0120] First, based on the requirements of this schedule, confirm the design scope of the physical model involved in this schedule:

[0121] ① Newly added customer income status table: customer number, personal monthly salary income amount, personal monthly salary income currency, family annual income amount, family annual income currency.

[0122] ②Change the customer basic information table: add a new customer level type field.

[0123] 2. Determine the data item information corresponding to the physical model field

[0124] Query the enterprise-level data items corresponding to the designed table fields. If they are unique to the system, query the system-level data items. There is a lot of data item information. Some key information is listed here, as shown in Table 1 below.

[0125]

[0126] Table 1 Examples of some key information

[0127] The option code information corresponding to the data item takes OPTIONCODE0001 as an example, as shown in Table 2 below:

[0128]

[0129] Table 2 Option codes corresponding to data items

[0130] 3. Physical model design

[0131] ①New customer income status table

[0132] The maintenance information of the physical table includes: basic information, table fields, table primary keys, table indexes, etc. The new table operation is Add, and the version number is automatically generated by the system as 1.00.01.

[0133] Maintain table basic information: including system name, table name, table Chinese, database type, etc., as shown in Table 3 below.

[0134] Maintain table field information: Newly added fields generate field names, field Chinese, data types, data length, etc. by associating data items, and add other relevant information, such as whether to allow blanks, etc., as shown in Table 4 below.

[0135]

[0136] Table 3 Basic information of physical table

[0137]

[0138] Table 4 Field information of physical table

[0139] Maintain table primary key and table index information: Determine the table primary key and index information based on the table fields. This is optional. The table primary key information is shown in Table 5 below, and the table index information is shown in Table 6 below.

[0140]

[0141] Table 5 Primary key information of physical table

[0142]

[0143] Table 6 Index information of physical table

[0144] ②Change customer basic information form

[0145] The change of physical table is based on the existing production branch. The checkout operation is to copy a copy of table information to a specific schedule based on the production branch, such as version 1.00, and automatically define the copied version as 1.00.01, as shown in Table 7. The processing of other information, such as the modification of physical primary key and index of physical table, is no different from that of the physical table in the addition of physical table, and will not be repeated here.

[0146]

[0147] Table 7 Modify the basic information of the physical table

[0148] 4. Design review

[0149] After the physical table design is completed, the review process can be initiated. The person in charge of the system model design review will receive relevant to-do information. If the review fails, the addition or change of the physical table will not take effect. The review will be re-initiated after modification. If the review passes, it will be automatically checked in to the production branch when it is scheduled to go online. The version number of the newly created table CUST_INCM_INFO development branch is 1.00.00. After checking in, the corresponding version of the production branch is 1.00. The version number of the physical table CUST_INFO after checking out of the development branch is changed to 1.00.01. After checking in to production, the corresponding version of the production branch is 1.01.

[0150] Figure 5 A structural diagram of a physical model processing device provided in another embodiment of the present application is shown in FIG. Figure 5 As shown, the device 500 may include a first processing module 501 and a second processing module 502, wherein:

[0151] The first processing module 501 is used to design the physical model through the physical model design module according to the English root, data item and option code included in the data dictionary module, wherein the English root is the abbreviation of the English word, the data item is obtained by splicing the English root, and the option code is the description information of the data value of the data item;

[0152] The second processing module 502 is used to perform branch management and / or version management on the designed physical model through the basic function management module, and to review the update of the designed physical model.

[0153] In a possible implementation, the device further includes a creation module;

[0154] A creation module is used to create a root word library and a data item information library. The root word library is a database storing multiple English root words, and the data item information library is a database maintaining data information of multiple data items.

[0155] The data information of each English root in the root database includes at least one of the following:

[0156] Root name, root type, full English name of the root, Chinese description of the root, creator of the root and creation time of the root;

[0157] The data information of each data item in the data item information library includes at least one of the following:

[0158] Data item type, data item name, English name, Chinese name, data item status, encoding rule, data type, data length, maximum data value, minimum data value, amount unit, business definition, business rule, number of associated option code, creator of the data item and creation time of the data item.

[0159] In a possible implementation, the device further includes a third processing module;

[0160] A third processing module is used to associate the data item with the option code, where the option code is used to represent the value range of the data value of the data item;

[0161] The data information of each option code includes at least one of the following:

[0162] The option code’s name, Chinese code, English name, usage status, option value, description of the option value, creator of the option code, and creation time of the option code.

[0163] In a possible implementation manner, the first processing module is specifically configured to:

[0164] Design the physical model by designing the physical table through the physical model design module according to the English root, data item and option code;

[0165] The data information of the physical table at least includes basic information, field information, primary key information and index information, and the basic information at least includes the table name and the corresponding database type.

[0166] In a possible implementation, the design of the physical table includes a new creation process of the physical table or a change process of the physical table;

[0167] Wherein, the first processing module is specifically used for:

[0168] When the design of the physical table is a new creation of the physical table, a new physical table is created according to the English root, data item and option code, basic information and field information are added to the new physical table, and version information of the new physical table is saved;

[0169] When the design of the physical table is a change process of the physical table, the basic information and field information of the physical table to be changed are changed according to the English root, data item and option code, and the version information of the changed physical table is saved.

[0170] In a possible implementation, after adding basic information and field information to the newly created physical table, the first processing module is further configured to: add at least one of primary key information or index information to the newly created physical table;

[0171] After performing change processing on basic information and field information of the physical table to be changed, the first processing module is further used to: perform change processing on at least one of primary key information or index information of the physical table to be changed.

[0172] In a possible implementation, when reviewing the update of the designed physical model, the second processing module is used to:

[0173] Review the newly created physical table or the changed physical table to determine whether the newly created physical table or the changed physical table meets the requirements.

[0174] The device provided in the embodiment of the present application designs a physical model according to the English roots, data items and option codes included in the data dictionary module, so that the design of the physical model of each system can adopt the data dictionary uniformly formulated by the enterprise to achieve unified entry and standardized management, thereby standardizing the definition of the physical model and facilitating unified implementation of standards; by performing branch management and / or version management on the designed physical model, flexible branch management and version management of the physical model according to different schedules and development tasks is achieved, and by reviewing the update of the designed physical model, the review of the changes to the designed physical model is achieved, so that corresponding authority control can be performed on the changes to the designed physical model.

[0175] It should be noted that this embodiment is an apparatus embodiment corresponding to the above-mentioned method embodiment, and this embodiment can be implemented in conjunction with the above-mentioned method embodiment. The relevant technical details mentioned in the above-mentioned method embodiment are still valid in this embodiment, and in order to reduce repetition, they are not repeated here. Accordingly, the relevant technical details mentioned in this embodiment can also be applied in the above-mentioned method embodiment.

[0176] Another embodiment of the present application provides an electronic device, such as Figure 6 As shown, Figure 6 The electronic device 600 shown includes: a processor 601 and a memory 603. The processor 601 and the memory 603 are connected, such as through a bus 602. Further, the electronic device 600 may also include a transceiver 604. It should be noted that in actual applications, the transceiver 604 is not limited to one, and the structure of the electronic device 600 does not constitute a limitation on the embodiments of the present application.

[0177] The processor 601 is used in the embodiment of the present application to implement Figure 5 The functions of the first processing module and the second processing module are shown. The transceiver 604 includes a receiver and a transmitter.

[0178] Processor 601 may be a CPU, a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. Processor 601 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0179] The bus 602 may include a path to transmit information between the above components. The bus 602 may be a PCI bus or an EISA bus, etc. The bus 602 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0180] The memory 603 may be a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, or an EEPROM, a CD-ROM or other optical disk storage, an optical disk storage (including a compressed optical disk, a laser disk, an optical disk, a digital versatile disk, a Blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to these.

[0181] The memory 603 is used to store the application code for executing the solution of the present application, and the execution is controlled by the processor 601. The processor 601 is used to execute the application code stored in the memory 603 to implement Figure 5 The illustrated embodiment provides actions of the physical model processing device.

[0182] The electronic device provided in the embodiment of the present application includes a memory, a processor and a computer program stored in the memory and executable on the processor. When the processor executes the program, it can achieve: designing a physical model through a physical model design module according to English roots, data items and option codes included in a data dictionary module, wherein the English roots are abbreviations of English words, the data items are obtained by concatenating the English roots, and the option codes are description information of the data values ​​of the data items; then, performing branch management and / or version management on the designed physical model through a basic function management module, and auditing updates to the designed physical model.

[0183] The embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the method shown in the above embodiment is implemented. Among them: the physical model is designed according to the English root words, data items and option codes included in the data dictionary module, so that the design of the physical model of each system can adopt the data dictionary uniformly formulated by the enterprise, realize unified entry and standardized management, so that the definition of the physical model can be standardized, which is conducive to unified implementation of standards; by performing branch management and / or version management on the designed physical model, flexible branch management and version management of the physical model according to different schedules and development tasks is realized, and by reviewing the update of the designed physical model, the review of the change of the designed physical model is realized, so that the change of the designed physical model can be controlled accordingly.

[0184] The computer-readable storage medium provided in the embodiments of the present application is applicable to any embodiment of the above method.

[0185] It should be understood that, although the steps in the flowchart of the accompanying drawings are displayed in sequence as indicated by the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps.

[0186] The above is only a partial implementation method of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A physical model processing method, characterized in that: include: According to the English word roots, data items and option codes included in the data dictionary module, the physical model is designed by the physical model design module, wherein the English word roots are abbreviations of English words, the data items are obtained by splicing the English word roots, and the option codes are description information of the data values ​​of the data items; Wherein, designing the physical model through the physical model design module according to the English root words, data items and option codes included in the data dictionary module comprises: designing the physical model by designing a physical table through the physical model design module according to the English root words, the data items and the option codes; wherein the data information of the physical table at least comprises basic information, field information, primary key information and index information, and the basic information at least comprises a table name and a corresponding database type; Wherein, the design of the physical table includes the creation of the physical table or the modification of the physical table; wherein, the design of the physical table through the physical model design module according to the English root, the data item and the option code includes: when the design of the physical table is the creation of the physical table, according to the English root, the data item and the option code, the physical table is created and basic information and field information are added to the newly created physical table, and the version information of the newly created physical table is saved; when the design of the physical table is the modification of the physical table, according to the English root, the data item and the option code, the basic information and field information of the physical table to be modified are modified, and the version information of the modified physical table is saved; After adding basic information and field information to the newly created physical table, the method further includes: adding at least one of primary key information or index information to the newly created physical table; after performing a change process on the basic information and field information of the physical table to be changed, the method further includes: performing a change process on at least one of primary key information or index information of the physical table to be changed; The basic function management module is used to perform branch management and / or version management on the designed physical model, and to review the update of the designed physical model, wherein: The update of the physical model of the design is reviewed, that is, the design review function is provided. The design review function refers to the authority review function. The authority review function provides authority control and online review functions for changes to the physical model of the design. Changes to the physical model of the design will take effect only after approval by the authorized reviewers of each system.

2. The method according to claim 1, characterized in that: Before designing the physical model through the physical model design module according to the English word roots, data items and option codes included in the data dictionary module, the following is also included: Creating a root word library and a data item information library, wherein the root word library is a database storing a plurality of English root words, and the data item information library is a database maintaining data information of a plurality of data items; The data information of each English word root in the word root library includes at least one of the following: Root name, root type, full English name of the root, Chinese description of the root, creator of the root and creation time of the root; The data information of each data item in the data item information library includes at least one of the following: Data item type, data item name, English name, Chinese name, data item status, encoding rule, data type, data length, maximum data value, minimum data value, amount unit, business definition, business rule, number of associated option code, creator of the data item and creation time of the data item.

3. The method according to claim 1 or 2, characterized in that: Before designing the physical model through the physical model design module according to the English word roots, data items and option codes included in the data dictionary module, the method further includes: Associating the data item with the option code, wherein the option code is used to represent a value range of a data value of the data item; The data information of each option code includes at least one of the following: The option code’s name, Chinese code, English name, usage status, option value, description of the option value, creator of the option code, and creation time of the option code.

4. The method according to claim 1, characterized in that: The review of the update of the physical model of the design includes: The newly created physical table or the changed physical table is reviewed to determine whether the newly created physical table or the changed physical table meets the requirements.

5. A physical model processing device, characterized in that: include: a first processing module, configured to design the physical model through a physical model design module according to English word roots, data items and option codes included in the data dictionary module, wherein the English word roots are abbreviations of English words, the data items are obtained by concatenating the English word roots, and the option codes are description information of data values ​​of the data items; Wherein, designing the physical model through the physical model design module according to the English root words, data items and option codes included in the data dictionary module comprises: designing the physical model by designing a physical table through the physical model design module according to the English root words, the data items and the option codes; wherein the data information of the physical table at least comprises basic information, field information, primary key information and index information, and the basic information at least comprises a table name and a corresponding database type; Wherein, the design of the physical table includes the creation of the physical table or the modification of the physical table; wherein, the design of the physical table through the physical model design module according to the English root, the data item and the option code includes: when the design of the physical table is the creation of the physical table, according to the English root, the data item and the option code, the physical table is created and basic information and field information are added to the newly created physical table, and the version information of the newly created physical table is saved; when the design of the physical table is the modification of the physical table, according to the English root, the data item and the option code, the basic information and field information of the physical table to be modified are modified, and the version information of the modified physical table is saved; After adding basic information and field information to the newly created physical table, the method further includes: adding at least one of primary key information or index information to the newly created physical table; after performing a change process on the basic information and field information of the physical table to be changed, the method further includes: performing a change process on at least one of primary key information or index information of the physical table to be changed; The second processing module is used to perform branch management and / or version management on the designed physical model through the basic function management module, and to review the update of the designed physical model, wherein: The update of the physical model of the design is reviewed, that is, the design review function is provided. The design review function refers to the authority review function. The authority review function provides authority control and online review functions for changes to the physical model of the design. Changes to the physical model of the design will take effect only after approval by the authorized reviewers of each system.

6. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the method according to any one of claims 1 to 4 is implemented.

7. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 4.

Images