CN111145011B - Banking system building method and device - Google Patents
Banking system building method and device Download PDFInfo
- Publication number
- CN111145011B CN111145011B CN201911378177.4A CN201911378177A CN111145011B CN 111145011 B CN111145011 B CN 111145011B CN 201911378177 A CN201911378177 A CN 201911378177A CN 111145011 B CN111145011 B CN 111145011B
- Authority
- CN
- China
- Prior art keywords
- metadata
- model
- meta
- physical object
- mobile banking
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title description 37
- 238000010276 construction Methods 0.000 claims abstract description 29
- 238000004458 analytical method Methods 0.000 claims description 29
- 230000006870 function Effects 0.000 claims description 28
- 230000006399 behavior Effects 0.000 claims description 20
- 238000004590 computer program Methods 0.000 claims description 20
- 238000012098 association analyses Methods 0.000 claims description 4
- 239000000047 product Substances 0.000 description 29
- 238000007726 management method Methods 0.000 description 24
- 238000010586 diagram Methods 0.000 description 15
- 230000008569 process Effects 0.000 description 12
- 238000012545 processing Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 6
- 238000011161 development Methods 0.000 description 6
- 238000013523 data management Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000005192 partition Methods 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 238000013499 data model Methods 0.000 description 2
- VJYFKVYYMZPMAB-UHFFFAOYSA-N ethoprophos Chemical compound CCCSP(=O)(OCC)SCCC VJYFKVYYMZPMAB-UHFFFAOYSA-N 0.000 description 2
- 238000000605 extraction Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000000750 progressive effect Effects 0.000 description 2
- 238000012356 Product development Methods 0.000 description 1
- 108010001267 Protein Subunits Proteins 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 239000008280 blood Substances 0.000 description 1
- 210000004369 blood Anatomy 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 239000007795 chemical reaction product Substances 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 239000012467 final product Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 238000005065 mining Methods 0.000 description 1
- 239000003607 modifier Substances 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/10—Requirements analysis; Specification techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- Finance (AREA)
- Accounting & Taxation (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- General Business, Economics & Management (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a banking system construction method and device, comprising the following steps: creating public metadata according to a pre-established meta-model system range; and constructing a service system according to the public metadata, wherein the service system consists of a physical object model. The application provides a banking system based on the metadata standard, which at least solves the problems that model objects with the same meaning are defined into a plurality of objects and data among products are inconvenient to be commonly used because modeling objects of various product parts of various departments are not uniform in the prior art by establishing a business system by establishing a metadata management system.
Description
Technical Field
The application belongs to the technical field of financial business systems, and particularly relates to a banking business system building method and device.
Background
In banking industry, in order to solve the problem that model objects with the same meaning are defined into a plurality of objects (such as core client numbers in banks have a plurality of names, for example, CUSTOMER_NO\CUST_NO\CIF\ BANCS _CUST_NO\ … …, and the respective data types and lengths are different) due to non-uniform modeling standards of the products of multiple development departments, the data influence analysis between the products is inconvenient for developers and service analyzers when the products need to borrow data from each other in the past. Especially in the information age, the lack of unified data management is difficult to truly mine mass data.
Disclosure of Invention
The application provides a banking system building method and device, which at least solve the problems that model objects with the same meaning are defined into a plurality of objects and data among products are inconvenient to use because modeling objects among products of departments are not uniform in the prior art.
According to one aspect of the present application, there is provided a banking system construction method including:
Creating public metadata according to a pre-established meta-model system range;
and constructing a service system according to the public metadata, wherein the service system consists of a physical object model.
In one embodiment, establishing common metadata according to a predefined meta-model hierarchy scope includes:
building a meta model according to the meta model system range, wherein the meta model comprises corresponding attributes;
common metadata is created from the metamodel.
In one embodiment, constructing a business system from common metadata includes:
Generating each physical object model according to the public metadata;
and calling a physical object model to construct a service system.
In one embodiment, generating physical object models from common metadata includes:
Calling a corresponding metadata object from the public metadata according to the service requirement;
The metadata objects are combined into a physical object model.
In one embodiment, the step of pre-establishing the meta-model hierarchy range includes:
and determining the attribute of each meta-model to be established according to the service requirement, and obtaining a meta-model system range according to the attribute of each meta-model to be established.
According to another aspect of the present application, there is provided a banking system construction apparatus comprising:
A common metadata creation unit for creating common metadata according to a pre-established meta model system range;
and the business system construction unit is used for constructing a business system according to the public metadata, wherein the business system consists of a physical object model.
In an embodiment, the common metadata creation unit includes:
The meta model building module is used for building a meta model according to the meta model system range, wherein the meta model comprises corresponding attributes;
And the creation module is used for creating the public metadata according to the meta model.
In one embodiment, the service system construction unit includes:
the physical object model generation module is used for generating each physical object model according to the common metadata;
And the construction module is used for calling the physical object model by the service system to construct the service system.
In one embodiment, the physical object model generation module includes:
the object calling module is used for calling the corresponding metadata object from the public metadata according to the service requirement;
and the combination module is used for combining the metadata objects into a physical object model.
In an embodiment, the apparatus further comprises:
And the meta-model system range creation module is used for determining the attribute of each meta-model to be built according to the service requirement and obtaining the meta-model system range according to the attribute of each meta-model to be built.
The application establishes the banking system by constructing the metadata management system, namely, establishes the unified physical object model, and then establishes the banking system according to the physical object models, thereby realizing the functions of describable and traceable data in the banking system, and blood margin analysis and influence analysis.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flowchart of a banking system construction method provided by the application.
FIG. 2 is a flow chart of establishing common metadata according to a predefined meta-model hierarchy scope in an embodiment of the present application.
Fig. 3 is a flowchart of constructing a business system according to common metadata in an embodiment of the present application.
FIG. 4 is a flow chart of generating physical object models from common metadata in an embodiment of the application.
Fig. 5 is a block diagram of a banking system construction device according to the present application.
Fig. 6 is a block diagram showing the structure of a common metadata creation unit in the embodiment of the present application.
Fig. 7 is a block diagram of a service system construction unit in an embodiment of the present application.
FIG. 8 is a block diagram of the physical object model generation module in an embodiment of the application.
Fig. 9 is a key node diagram of a banking system construction method in the present application.
Fig. 10 is a specific implementation of an electronic device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Before describing the scheme of the application, several concepts are described:
1. Meta-model: is a model related to the model. For a model in a particular domain, a meta-model is a building element that defines concepts and provides for creating the model in that domain. Such as meta-models that define topics, products, interfaces, tables, relationships, dimensions, fields, etc. and their corresponding attributes as a particular domain.
2. Metadata: is data describing the data. The attributes mainly used for describing data are used for supporting resource searching, indicating storage locations and the like, and are generally classified into business metadata, technical metadata and process metadata.
In existing data management, model objects with the same meaning due to non-uniformity of respective modeling standards in multiple development departments and multiple products are often defined as multiple objects, for example, core client numbers in banks, and have a plurality of names, such as: the various definitions of CUSTOMER_NO\CUST_NO\CIF\ BANCS _CUST_NO\ … … and the like are different in data type and length, so that when the mutual use of data is needed between products, the data is inconvenient for developers or business analysts to understand and the analysis of the data influence between the products is inconvenient. At present, the field lacks unified data management, and the mining work is difficult to really realize when facing mass data.
Based on this, the present application provides a banking system building method, that is, a banking system is built by building a metadata management system, and specific steps are as shown in fig. 1, including:
S101: common metadata is created from a pre-established meta-model hierarchy scope.
Firstly, a pre-set banking metadata management standard (namely, defining a range of a meta-model system) is used for establishing a meta-model management system which comprises all meta-models in the field, and then common metadata is maintained through the management system.
In a particular embodiment, common metadata is created by a meta-model management system, and from the perspective of the type of common metadata, the population is divided into business metadata (e.g., topics, products, report indicators, etc.) and technical metadata (e.g., interfaces, tables, fields, process relationships, etc.).
S102: and constructing a service system according to the public metadata, wherein the service system consists of a physical object model.
And selecting metadata objects required by the service according to the service requirements, requesting to acquire the required metadata objects from a metadata management system, forming a physical object model by the acquired metadata objects, and then forming a service system by combining the physical object models.
The method shown in fig. 1, which can be implemented by a server, a PC, and a mobile terminal, implements the function of building a service system by building a common metadata management system and then using a meta model and metadata.
In a specific embodiment, the common metadata referenced in the service system can be changed, deleted, replaced and added along with the change of the service requirement, and when the common metadata is selected, the relationship is established with the service system, and the relationships can also be changed.
In one embodiment, as shown in FIG. 2, establishing common metadata according to a predefined meta-model hierarchy scope includes:
s201: and building a meta model according to the meta model system range, wherein the meta model comprises corresponding attributes.
Building a meta-model according to the system range of the meta-model (which can be also understood as banking meta-data management standard), wherein the built meta-model comprises corresponding attributes, and in the process of building the meta-model: firstly, the types of metamodels are divided, which types of metamodels need to be established definitely, for example, metamodels of topics, products, report indexes, interfaces, tables, fields and process relations need to be established definitely, and then various types of metamodels need to have attributes according to the system scope of the metamodels, for example, in a specific embodiment, the field metamodels need to be established, the attributes comprise an ID (identification) of a field, an belonged table ID, a field English name, a field Chinese name, a field type, a field length, a partition type, a field mode type (discrete or continuous), decimal point number, whether the metamodels are empty, serial numbers, default values, whether a primary key, a field description, states, a creator, creation time, an updater, update time and remarks.
S202: common metadata is created from the metamodel.
In a specific embodiment, taking the common metadata of the fields as an example, based on the above meta model, the common metadata is established as follows:
{ "662e2d1c168911eab7bc125056a00cd8", "662e2d1c168911eab7bc125056a00cd9", "CUST_NO", "bank core customer number", "VARCHAR", "16", "day", "1", NULL, "0", 1"," Y "," bank core customer number ","1","662e2d1c168911eab7bc015056a00cd8","2019-10-02 12:45:00","662e2d1c168911eab7bc025056a00cd8","2019-10-02 12:45:00"," bank core customer number "}
The above is a specific example of common metadata of fields.
In one embodiment, as shown in FIG. 3, constructing a business system from common metadata includes:
S301: each physical object model is generated from the common metadata.
And selecting the required public metadata from the metadata management system according to the service requirements to build a physical object model.
In a specific embodiment, to build the physical object model of the client information table, public metadata such as CUST_NO (core client number), CUST_EMAIL (EMAIL), CUST_MOBILE (MOBILE phone number), CUST_ID_TYPE (certificate TYPE), CUST_ID_NO (certificate number), CUST_NAME (NAME) and the like are selected from the metadata management system to build the physical object model of the client information table. These field metadata can be applied from a metadata management system and can be selectively used by multiple business systems.
S302: and calling a physical object model to construct a service system.
In one embodiment, taking a mobile banking behavior analysis system (a type of banking system) as an example, to analyze and count a report index, the mobile banking behavior analysis system is formed by using a constructed physical object model as follows:
cdm_cus_cut_info: mobile phone bank client information table (physical object model)
Cdm_cus_menu_clip_num: mobile phone bank function click list (physical object model)
The two physical object models form a mobile banking behavior analysis system.
And counting the ranking of the function use condition of each client in a certain period of time through the association analysis of the mobile banking client information table and the mobile banking function click list.
In one embodiment, as shown in FIG. 4, generating each physical object model from common metadata includes:
S401: and calling the corresponding metadata object from the public metadata according to the service requirement.
In a specific embodiment, for example, a client information table is needed in a mobile banking behavior analysis service system, and a core client number field applies for calling a metadata object from public metadata as follows:
① Field metamodel: ID identification, belonging table ID, field English name, field Chinese name, field type, field length, partition type, field mode type (discrete-0 or continuous-1), decimal place number, null, sequence number, default value, main key, field description, state, creator, creation time, updater, update time, remarks.
② One physical object instance of field common metadata:
{ "662e2d1c168911eab7bc125056a00cd8", "662e2d1c168911eab7bc125056a00cd9", "CUST_NO", "bank core customer number", "VARCHAR", "16", "day", "1", NULL, "0", 1"," Y "," bank core customer number ","1","662e2d1c168911eab7bc015056a00cd8","2019-10-02 12:45:00","662e2d1c168911eab7bc025056a00cd8","2019-10-02 12:45:00"," bank core customer number "}.
S402: the metadata objects are combined into a physical object model.
In a specific embodiment, after the metadata management system applies for using metadata objects, the metadata management system establishes a relationship with the metadata "core client number" and generates field metadata (i.e. core client number) of the mobile banking client information table of the service system, as follows:
An object (physical object model) instance of mobile banking behavior analysis business system field metadata:
{ "662e2d1c168911eab7bc125056a00cd8", "662e2d1c168911eab7bc125056a00cd9", "CUST_NO", "cell phone bank core customer number", "VARCHAR", "16", "day", "1", NULL, "0", 1"," Y "," cell phone bank core customer number ","1","662e2d1c168911eab7bc015056a00cd8","2019-10-0212:45:00","662e2d1c168911eab7bc025056a00cd8","2019-10-02 12:45:00"," bank core customer number "}.
In one embodiment, the step of pre-establishing the meta-model hierarchy range includes:
and determining the attribute of each meta-model to be established according to the service requirement, and obtaining a meta-model system range according to the attribute of each meta-model to be established.
The application establishes a banking system by establishing a metadata management system in the vertical field in a bank, namely, establishes a banking uniform data model, which can contain metadata such as topics, products, interfaces, tables, processes, relations, dimensions, fields, indexes, reports and the like, and establishes the banking system by the data model, wherein certain metadata can be referenced by a plurality of business systems so as to realize the targets of describable, traceable, blood-margin analysis and analysis of data objects in the business systems.
Based on the same inventive concept, the embodiment of the present application also provides a device for constructing a banking system, which can be used to implement the method described in the above embodiment, as described in the following embodiment. The principle of the banking system construction device for solving the problems is similar to that of the banking system construction method, so that the implementation of the banking system construction device can be referred to the implementation of the banking system construction method, and repeated parts are not repeated. As used below, the term "unit" or "module" may be a combination of software and/or hardware that implements the intended function. While the system described in the following embodiments is preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.
According to another aspect of the present application, as shown in fig. 5, there is provided a banking system construction apparatus including:
a common metadata creation unit 501 for creating common metadata from a pre-established meta model hierarchy range;
a service system construction unit 502, configured to construct a service system according to the common metadata, where the service system is composed of a physical object model.
In an embodiment, as shown in fig. 6, the common metadata creation unit 501 includes:
the meta model building module 601 is configured to build a meta model according to a meta model system range, where the meta model includes a corresponding attribute;
a creation module 602, configured to create common metadata according to the meta model.
In one embodiment, as shown in fig. 7, the service system construction unit 502 includes:
a physical object model generating module 701, configured to generate each physical object model according to the common metadata;
The construction module 702 is configured to construct a service system by using the service system call physical object model.
In one embodiment, as shown in fig. 8, the physical object model generating module 701 includes:
an object calling module 801, configured to call a corresponding metadata object from the common metadata according to a service requirement;
A combination module 802 for combining the metadata objects into a physical object model.
In an embodiment, the apparatus further comprises:
And the meta-model system range creation module is used for determining the attribute of each meta-model to be built according to the service requirement and obtaining the meta-model system range according to the attribute of each meta-model to be built.
The scheme of the application will be specifically illustrated by way of example, as shown in fig. 9:
Firstly, banking metadata management standards are designed, namely, a meta-model system range (comprising a theme, a product, an interface, a table, a process, a relation, a dimension, a field, an index, a report and the like) is defined, then a specific meta-model of the standard is established, and meta-model attribute definition of the meta-model system is as follows:
Theme meta-model: ID, topic category, topic type, topic English name, topic Chinese name, status, creator, creation time, updater, update time, update description, remarks;
Product meta-model: ID identification, product type, product identification, product name, function profile, business classification, development style, product remark, sub-product identification, sub-product name, corresponding product, architecture classification, version case, sub-product development style, disaster recovery grading, availability grading, system deployment mode, vendor related case description, whether an Internet product is involved, whether a mobile application is involved, whether a dedicated line connection exists, internet finance, data class, current intellectual property status brief description, product technology transfer implementation status, product technology transfer objective, product technology transfer case description, home location, development/management department, development/management team, maintenance project code, maintenance department, test team, business director, department management team, architect A corner, architect B corner, business artist B corner, business professional domain, field of interest, field senior expert, date, creator, creation time, updater, update time;
Interface unit metamodel: ID identification, operation, path, name, new name, alias, serial number, interface unit code, interface unit name, interface unit description, data file type, data file path, data source system, opposite end system, transmission direction, interface host identification, interface type, interface data file name, check file name, column separator, row separator, whether to perform non-empty check, upper limit of number of data files, extraction mode, extraction period, expected running time, file arrival time limit, responsible party, current state, expiration date, whether to fail, creation time, creator, modification time, modifier, remark;
Interface field metamodel: ID identity, operation type, path, name, new name, alias, sequence number, field name, field type, field description, field encoding, remark, field length, error detection criteria JsonString, modified flag, revision ID, null, primary key, status, source system entity, target system entity, pseudo ID, attribute description backup, dimension constraint;
And (3) a table element model: ID identification, belonging library ID, table English name, table Chinese name, table belonging layer, column split separator, file start separator, file end separator, table service function description, primary type, secondary type, record number, occupied space, number of times of being referenced, table storage format, state, creator, creation time, updater, update time, remark.
Then, public metadata such as topics, products, interfaces, tables, processes, relations, dimensions, fields, indexes, reports and the like are established based on the meta model; for example, the common metadata for creating a theme based on a theme meta-model is as follows:
Theme meta-model: ID identification, topic category, topic type, topic english name, topic chinese name, creator, creation time, updater, update time, remarks.
Based on the instantiation metadata of this meta-model, the lending topic metadata is as follows:
“662e2d1c168911eab7bc005056a00cd8”、
Financial service "
Loan service "
“Vehicle loan”
Vehicle credit "
“662e2d1c168911eab7bc015056a00cd8”
“2019-10-02 12:45:00”
“662e2d1c168911eab7bc025056a00cd8”
“2019-10-02 12:45:00”
'Vehicle credit theme-buying vehicle carefree'
Then abstracting the metadata objects which can be used from the service requirements (if the metadata management system can not be expanded, the metadata objects can be used after the system audit is needed);
For example, in a mobile banking behavior analysis service system, a client information table is required, wherein a core client number field is applied from public metadata, as follows:
① Field metamodel: ID identification, belonging table ID, field English name, field Chinese name, field type, field length, partition type, field mode type (discrete-0 or continuous-1), decimal place number, null, sequence number, default value, primary key, field description, state, creator, creation time, updater, update time, remark
② One object instance of field common metadata:
{ "662e2d1c168911eab7bc125056a00cd8", "662e2d1c168911eab7bc125056a00cd9", "CUST_NO", "bank core customer number", "VARCHAR", "16", "day", "1", NULL, "0", 1"," Y "," bank core customer number ","1","662e2d1c168911eab7bc015056a00cd8","2019-10-02 12:45:00","662e2d1c168911eab7bc025056a00cd8","2019-10-02 12:45:00"," bank core customer number "}
Then applying for using metadata in the metadata management system (the corresponding relation between the public metadata and the service system metadata can be automatically generated by the system after the application passes through); applying for using the common field metadata of the 'bank core client number' from the field common metadata; organically combining the metadata passing through the application into a data physical object model of the service system, and uniformly managing the data physical object model in a service system management module; after the application was used successfully, the following was applied for:
The mobile banking behavior system establishes a relation with the public field metadata 'core client number' and generates field metadata (mobile banking core client number) of the mobile banking client information table of the business system as follows:
An object (physical object model) instance of mobile banking behavior analysis business system field metadata:
{ "662e2d1c168911eab7bc125056a00cd8", "662e2d1c168911eab7bc125056a00cd9", "CUST_NO", "cell phone bank core customer number", "VARCHAR", "16", "day", "1", NULL, "0", 1"," Y "," cell phone bank core customer number ","1","662e2d1c168911eab7bc015056a00cd8","2019-10-0212:45:00","662e2d1c168911eab7bc025056a00cd8","2019-10-02 12:45:00"," bank core customer number "}
The development of the business system is completed based on the physical object model of the final product; such as:
The physical object model of the table established by the fields of the above is used for analyzing and counting a report index (ranking of the use condition of the mobile banking function) for a mobile banking behavior analysis system (business system)
Cdm_cus_cut_info: mobile phone bank client information table (physical object model)
Cdm_cus_menu_clip_num: mobile phone bank function click list (physical object model)
Through the association analysis of the two tables, the ranking of the function use condition of each client in a certain period of time can be counted.
Repeating the process of establishing the service system when the service system is changed;
Each business system and product is checked, analyzed and operated in the business system management system, including blood-margin analysis, influence analysis and the like of data in and between the business systems.
The application builds the business system by building the management method of the metadata in the vertical field, can perform blood-margin influence and analysis on the data, and avoids inconvenient understanding and inconvenient analysis on the data influence between the products when the data are used between the products. The method realizes the functions of constructing a physical model of a business system by supporting the metadata management in the vertical field and describing and tracing the data.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention 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.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The principles and embodiments of the present invention have been described in detail with reference to specific examples, which are provided to facilitate understanding of the method and core ideas of the present invention; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present invention, the present description should not be construed as limiting the present invention in view of the above.
The embodiment of the present application further provides a specific implementation manner of an electronic device capable of implementing all the steps in the method in the foregoing embodiment, and referring to fig. 10, the electronic device specifically includes the following:
A processor 1001, a memory 1002, a communication interface (Communications Interface) 1003, a bus 1004, and a nonvolatile memory 1005;
wherein, the processor 1001, the memory 1002, and the communication interface 1003 complete communication with each other through the bus 1004;
The processor 1001 is configured to invoke the computer program in the memory 1002 and the nonvolatile memory 1005, where the processor executes the computer program to implement all the steps in the method in the foregoing embodiment, for example, the processor executes the computer program to implement the following steps:
S101: common metadata is created from a pre-established meta-model hierarchy scope.
S102: and constructing a service system according to the public metadata, wherein the service system consists of a physical object model.
An embodiment of the present application also provides a computer-readable storage medium capable of implementing all the steps of the method in the above embodiment, the computer-readable storage medium storing thereon a computer program that, when executed by a processor, implements all the steps of the method in the above embodiment, for example, the processor implements the following steps when executing the computer program:
S101: common metadata is created from a pre-established meta-model hierarchy scope.
S102: and constructing a service system according to the public metadata, wherein the service system consists of a physical object model.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for a hardware+program class embodiment, the description is relatively simple, as it is substantially similar to the method embodiment, as relevant see the partial description of the method embodiment. Although the present description provides method operational steps as described in the examples or flowcharts, more or fewer operational steps may be included based on conventional or non-inventive means. The order of steps recited in the embodiments is merely one way of performing the order of steps and does not represent a unique order of execution. When implemented in an actual device or end product, the instructions may be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment, or even in a distributed data processing environment) as illustrated by the embodiments or by the figures. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, it is not excluded that additional identical or equivalent elements may be present in a process, method, article, or apparatus that comprises a described element. For convenience of description, the above devices are described as being functionally divided into various modules, respectively. Of course, when implementing the embodiments of the present disclosure, the functions of each module may be implemented in the same or multiple pieces of software and/or hardware, or a module that implements the same function may be implemented by multiple sub-modules or a combination of sub-units, or the like. The above-described apparatus embodiments are merely illustrative, for example, the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form. The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be appreciated by those skilled in the art that embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the present specification embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present description embodiments may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein. In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments. In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the embodiments of the present specification.
In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction. The foregoing is merely an example of an embodiment of the present disclosure and is not intended to limit the embodiment of the present disclosure. Various modifications and variations of the illustrative embodiments will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, or the like, which is within the spirit and principles of the embodiments of the present specification, should be included in the scope of the claims of the embodiments of the present specification.
Claims (8)
1. A banking system construction method, comprising:
Creating public metadata according to a pre-established meta-model system range;
Constructing a service system according to the public metadata, wherein the service system consists of a physical object model;
the construction of the business system according to the public metadata comprises the following steps:
generating each physical object model according to the public metadata;
calling the physical object model to construct the service system;
the generating each physical object model according to the common metadata comprises the following steps:
Calling a corresponding metadata object from the public metadata according to service requirements;
Combining the metadata objects into the physical object model;
when the service system is a mobile banking behavior analysis system, the calling the corresponding metadata object from the public metadata according to the service requirement comprises the following steps:
Applying for using the public metadata in a metadata management system, after the metadata management system passes, establishing a relation between a mobile banking behavior analysis system and the public metadata and generating field metadata of a mobile banking client information table of the mobile banking behavior analysis system; after the application passes, the system automatically generates the corresponding relation between the public metadata and the field metadata of the service system;
When the physical object model is a client information table, the combining the metadata objects into the physical object model includes:
Selecting common metadata from a metadata management system to build a physical object model of the client information table, wherein the field metadata can be applied from the metadata management system and can be selected and used by a plurality of business systems; the common metadata includes: core customer number, email, cell phone number, certificate type, certificate number, name;
when the mobile banking behavior analysis system is used for analyzing and counting a report index, the calling the physical object model to construct the business system comprises the following steps:
cdm_cus_cut_info: a mobile banking client information table;
cdm_cus_menu_clip_num: the mobile phone banking function clicks the detail list;
The mobile banking client information table and the mobile banking function click list are physical object models, and the two physical object models form a mobile banking behavior analysis system; and counting the ranking of the function use condition of each client in a certain period of time through the association analysis of the mobile banking client information table and the mobile banking function click list.
2. The business system construction method according to claim 1, wherein the establishing the common metadata according to the predefined meta-model hierarchy range includes:
Establishing a meta model according to the meta model system range, wherein the meta model comprises corresponding attributes;
And creating common metadata according to the meta-model.
3. The business system construction method according to claim 1, wherein the step of pre-establishing a meta-model hierarchy range includes:
and determining the attribute of each meta-model to be established according to the service requirement, and obtaining a meta-model system range according to the attribute of each meta-model to be established.
4. A banking system setting-up device, characterized by comprising:
A common metadata creation unit for creating common metadata according to a pre-established meta model system range;
a service system construction unit, configured to construct a service system according to the common metadata, where the service system is composed of a physical object model;
The business system construction unit includes:
the physical object model generation module is used for generating each physical object model according to the public metadata;
the construction module is used for calling the physical object model by a service system to construct the service system;
The physical object model generation module includes:
the object calling module is used for calling the corresponding metadata object from the public metadata according to the service requirement;
a combining module for combining the metadata objects into the physical object model;
when the service system is a mobile banking behavior analysis system, the object calling module is specifically configured to:
Applying for using the public metadata in a metadata management system, after the metadata management system passes, establishing a relation between a mobile banking behavior analysis system and the public metadata and generating field metadata of a mobile banking client information table of the mobile banking behavior analysis system; after the application passes, the system automatically generates the corresponding relation between the public metadata and the field metadata of the service system;
when the physical object model is a client information table, the combination module is specifically configured to:
Selecting common metadata from a metadata management system to build a physical object model of the client information table, wherein the field metadata can be applied from the metadata management system and can be selected and used by a plurality of business systems; the common metadata includes: core customer number, email, cell phone number, certificate type, certificate number, name;
When the mobile banking behavior analysis system is used for analyzing and counting a report index, the mobile banking behavior analysis system comprises:
cdm_cus_cut_info: a mobile banking client information table;
cdm_cus_menu_clip_num: the mobile phone banking function clicks the detail list;
The mobile banking client information table and the mobile banking function click list are physical object models, and the two physical object models form a mobile banking behavior analysis system; and counting the ranking of the function use condition of each client in a certain period of time through the association analysis of the mobile banking client information table and the mobile banking function click list.
5. The business system construction device according to claim 4, wherein the common metadata creation unit includes:
the meta model building module is used for building a meta model according to the meta model system range, wherein the meta model comprises corresponding attributes;
And the creation module is used for creating the public metadata according to the meta model.
6. The business system construction device according to claim 4, further comprising:
And the meta-model system range creation module is used for determining the attribute of each meta-model to be built according to the service requirement and obtaining the meta-model system range according to the attribute of each meta-model to be built.
7. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the banking system construction method of any one of claims 1 to 3 when executing the program.
8. A computer-readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the banking system construction method of any one of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911378177.4A CN111145011B (en) | 2019-12-27 | 2019-12-27 | Banking system building method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911378177.4A CN111145011B (en) | 2019-12-27 | 2019-12-27 | Banking system building method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111145011A CN111145011A (en) | 2020-05-12 |
| CN111145011B true CN111145011B (en) | 2024-04-23 |
Family
ID=70520953
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911378177.4A Active CN111145011B (en) | 2019-12-27 | 2019-12-27 | Banking system building method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111145011B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112286879B (en) * | 2020-07-15 | 2021-08-13 | 上海柯林布瑞信息技术有限公司 | Metadata-based data asset construction method and device |
| CN111858737B (en) * | 2020-07-29 | 2024-01-09 | 中国工商银行股份有限公司 | Data importing device and method, bank system constructing device and method, and storage medium |
| CN112037036B (en) * | 2020-09-02 | 2024-02-27 | 中国银行股份有限公司 | Banking information analysis method and device based on metadata |
| CN112905329A (en) * | 2021-03-24 | 2021-06-04 | 武汉众邦银行股份有限公司 | Full life cycle management and control method for improving standard falling rate of data |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102682357A (en) * | 2011-02-14 | 2012-09-19 | 微软公司 | Automatically creating business applications from description of business processes |
| CN103164221A (en) * | 2013-02-21 | 2013-06-19 | 用友软件股份有限公司 | Service modeling device and service modeling method |
| CN109254992A (en) * | 2018-10-12 | 2019-01-22 | 北京京东金融科技控股有限公司 | Project generation method and system, computer system and computer readable storage medium storing program for executing |
| CN109558393A (en) * | 2018-11-28 | 2019-04-02 | 中国海洋石油集团有限公司 | A kind of data model construction method, device, equipment and storage medium |
| CN109656912A (en) * | 2018-12-13 | 2019-04-19 | 成都四方伟业软件股份有限公司 | Data model management-control method, device and server |
| CN109753492A (en) * | 2019-01-02 | 2019-05-14 | 陕西西部资信股份有限公司 | A kind of system constituting method and device based on metadata configurations |
| CN110287223A (en) * | 2019-06-24 | 2019-09-27 | 北京明略软件系统有限公司 | Information storage means and device, electronic device and storage medium |
-
2019
- 2019-12-27 CN CN201911378177.4A patent/CN111145011B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102682357A (en) * | 2011-02-14 | 2012-09-19 | 微软公司 | Automatically creating business applications from description of business processes |
| CN103164221A (en) * | 2013-02-21 | 2013-06-19 | 用友软件股份有限公司 | Service modeling device and service modeling method |
| CN109254992A (en) * | 2018-10-12 | 2019-01-22 | 北京京东金融科技控股有限公司 | Project generation method and system, computer system and computer readable storage medium storing program for executing |
| CN109558393A (en) * | 2018-11-28 | 2019-04-02 | 中国海洋石油集团有限公司 | A kind of data model construction method, device, equipment and storage medium |
| CN109656912A (en) * | 2018-12-13 | 2019-04-19 | 成都四方伟业软件股份有限公司 | Data model management-control method, device and server |
| CN109753492A (en) * | 2019-01-02 | 2019-05-14 | 陕西西部资信股份有限公司 | A kind of system constituting method and device based on metadata configurations |
| CN110287223A (en) * | 2019-06-24 | 2019-09-27 | 北京明略软件系统有限公司 | Information storage means and device, electronic device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111145011A (en) | 2020-05-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111145011B (en) | Banking system building method and device | |
| Ivie et al. | Reproducibility in scientific computing | |
| CN110088749B (en) | Method, system and medium for automatic ontology generation | |
| US8234308B2 (en) | Deliver application services through business object views | |
| Washizaki et al. | Software-engineering design patterns for machine learning applications | |
| US8886590B2 (en) | Master data management in a data warehouse/data mart | |
| US11615076B2 (en) | Monolith database to distributed database transformation | |
| US20110145787A1 (en) | Business object change management using release status codes | |
| WO2007141068A1 (en) | A method for providing access to data stored in a database to an application | |
| CN116097247A (en) | Automated ETL workflow generation | |
| CN112463149B (en) | Software-defined satellite-oriented reusable code library construction method and device | |
| Zanoni et al. | Pattern detection for conceptual schema recovery in data‐intensive systems | |
| Gui et al. | IFC-based partial data model retrieval for distributed collaborative design | |
| EP2199905A1 (en) | Lifecycle management and consistency checking of object models using application platform tools | |
| CN107247581B (en) | Method for constructing system analysis and summary design delivery model | |
| CN115329011A (en) | Data model construction method, data query method, data model construction device and data query device, and storage medium | |
| CN106796598B (en) | Computation of management hierarchy entities | |
| CN116540980A (en) | Method and device for generating flow instance of business product and business system | |
| Thi et al. | A review of quality frameworks in information systems | |
| Karabey Aksakallı et al. | Micro‐IDE: A tool platform for generating efficient deployment alternatives based on microservices | |
| Guerra-García et al. | Developing web applications with awareness of data quality elements–DQAWA | |
| ElGamal et al. | An Architecture-Oriented Data Warehouse Testing Approach. | |
| El Beggar et al. | Towards an MDA-oriented UML profiles for data warehouses design and development | |
| Yang et al. | Single-state state machines in model-driven software engineering: an exploratory study | |
| TWI620134B (en) | Integration device and integration method thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |