CN117555655A - Method and device for creating business center - Google Patents
Method and device for creating business center Download PDFInfo
- Publication number
- CN117555655A CN117555655A CN202311467000.8A CN202311467000A CN117555655A CN 117555655 A CN117555655 A CN 117555655A CN 202311467000 A CN202311467000 A CN 202311467000A CN 117555655 A CN117555655 A CN 117555655A
- Authority
- CN
- China
- Prior art keywords
- sub
- loan
- business
- field
- domain
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 73
- 230000008569 process Effects 0.000 claims abstract description 26
- 230000002776 aggregation Effects 0.000 claims description 41
- 238000004220 aggregation Methods 0.000 claims description 41
- 238000012795 verification Methods 0.000 claims description 13
- 238000000605 extraction Methods 0.000 claims description 8
- 230000004931 aggregating effect Effects 0.000 claims description 4
- 238000012423 maintenance Methods 0.000 abstract description 9
- 238000007726 management method Methods 0.000 description 19
- 238000004590 computer program Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 238000005457 optimization Methods 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 238000011835 investigation Methods 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000007689 inspection Methods 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000009466 transformation Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000012098 association analyses Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006116 polymerization reaction Methods 0.000 description 1
- 238000004321 preservation Methods 0.000 description 1
- 230000006798 recombination Effects 0.000 description 1
- 238000005215 recombination Methods 0.000 description 1
- 230000008521 reorganization Effects 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 108020001568 subdomains Proteins 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/461—Saving or restoring of program or task context
-
- 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
- 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/03—Credit; Loans; Processing thereof
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Finance (AREA)
- Accounting & Taxation (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Software Systems (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- General Business, Economics & Management (AREA)
- General Engineering & Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The present disclosure provides a method and an apparatus for creating a service center, where the method includes: acquiring a to-be-processed loan business field associated with a target loan product from the loan business field; dividing the loan business field to be processed according to the process node associated with the target loan product to obtain a plurality of sub-loan business fields; determining a limit context of any sub-loan business field according to at least one field event in any sub-loan business field aiming at any sub-loan business field in the plurality of sub-loan business fields; the limit context is used for limiting the domain boundary of any sub-loan business domain; according to the limit context of any sub-loan business field, a business center of any sub-loan business field is created, so that the problem that the created business center has boundary conflict is avoided, and the complexity and maintenance cost of the business center are reduced.
Description
Technical Field
The disclosure relates to the field of computer technology, and in particular, to a method and a device for creating a service center.
Background
Currently, financial institutions (e.g., banks) employ a loan service center for loan service processing in order to better manage and process loan services. The loan service center can provide more efficient, more convenient and safer loan service.
In the related art, the creation mode of the loan service center is limited by manual experience, and the created service center may have a problem of boundary conflict, thereby increasing the complexity and maintenance cost of the service center.
Disclosure of Invention
The present disclosure provides a method and apparatus for creating a service center to solve at least one of the technical problems in the related art to some extent. The technical scheme of the present disclosure is as follows:
according to a first aspect of an embodiment of the present disclosure, there is provided a method for creating a service center, including: acquiring a to-be-processed loan business field associated with a target loan product from the loan business field; dividing the to-be-processed loan business field according to the process node associated with the target loan product to obtain a plurality of sub-loan business fields; determining a limit context of any sub-loan business field in the plurality of sub-loan business fields according to at least one field event in the any sub-loan business field; the limit context is used for limiting the domain boundary of any sub-loan business domain; and creating a business center of the any sub-loan business field according to the limit context of the any sub-loan business field.
According to a second aspect of the embodiments of the present disclosure, there is provided a creation apparatus of a service center, including: the acquisition module is used for acquiring the to-be-processed loan business field associated with the target loan product from the loan business field; the dividing module is used for dividing the to-be-processed loan business field according to the flow node associated with the target loan product so as to obtain a plurality of sub-loan business fields; a determining module, configured to determine, for any sub-loan business domain of the multiple sub-loan business domains, a limit context of the any sub-loan business domain according to at least one domain event in the any sub-loan business domain; the limit context is used for limiting the domain boundary of any sub-loan business domain; and the creation module is used for creating a business center of any sub-loan business field according to the limit context of the any sub-loan business field.
According to a third aspect of embodiments of the present disclosure, there is provided an electronic device, comprising: a processor; a memory for storing the processor-executable instructions; wherein the processor is configured to execute the instructions to implement a method for creating a service center according to an embodiment of the first aspect of the present disclosure.
According to a fourth aspect of embodiments of the present disclosure, there is provided a computer readable storage medium, which when executed by a processor of an electronic device, causes the electronic device to perform a method of creation of a mid-service platform according to an embodiment of the first aspect of the present disclosure.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product comprising: a computer program, when executed by a processor, implements a method of creation of a middlebox according to an embodiment of the first aspect of the disclosure.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
1. according to the process node associated with the target loan product, the to-be-processed loan service fields are divided to obtain a plurality of sub-loan service fields, the service fields are divided without manual mode, the accuracy of the service field division is improved, and the limit context of any sub-loan service field is determined according to at least one field event in any sub-loan service field, so that the service center of any sub-loan service field is created according to the limit context of any sub-loan service field, the creation of the service center is realized on the basis of determining the limit context of any sub-loan service field, the problem that the created service center has boundary conflict is avoided, and the complexity and maintenance cost of the service center are reduced;
2. Aiming at any field event in at least one field event in any sub-loan service field, acquiring a decision command for realizing the any field event; respectively extracting any domain event and an entity in a decision command of any domain event; according to the entity in each field event in any sub-loan service field and the entity in the decision command of each field event, the limit context of any sub-loan service field is generated, and the accuracy and the effectiveness of the limit context of any sub-loan service field are improved;
3. based on the general loan business flow, carrying out business verification on the domain model of any sub-loan business domain to obtain a verification result; responding to the difference between the verification result and the expected result being greater than the set difference, adjusting the domain model of any sub-loan service domain at least once until the adjusted domain model meets the expected result; according to the field model of any sub-loan service field obtained by the last adjustment, a service center of any sub-loan service field is created, iterative optimization of the field model of any sub-loan service field is realized, the service center of any sub-loan service field is created based on the optimized field model of any sub-loan service field, the accuracy of the creation of the service center is improved, the problem that boundary conflict exists in the service center is further avoided, and the complexity and maintenance cost of the service center are reduced.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.
Fig. 1 is a flowchart of a method for creating a service center shown in a first embodiment of the present disclosure;
fig. 2 is a flow chart illustrating a method for creating a service center according to a second embodiment of the present disclosure;
fig. 3 is a flowchart illustrating a method for creating a service center according to a third embodiment of the present disclosure;
fig. 4 is a flowchart illustrating a method for creating a service center according to a fourth embodiment of the present disclosure;
FIG. 5 is a schematic diagram of an implementation flow of creation of a middlebox shown in an embodiment of the disclosure;
FIG. 6 is a schematic flow diagram of modeling sub-loan business fields, as shown in an embodiment of the disclosure;
FIG. 7 is a flow diagram illustrating iterative optimization of a domain model according to an embodiment of the present disclosure;
fig. 8 is a schematic structural diagram of a creation device of a service center shown in a fifth embodiment of the present disclosure;
Fig. 9 is a schematic structural view of an electronic device according to an exemplary embodiment of the present disclosure.
Detailed Description
In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
It should be noted that, in the technical solution of the present disclosure, the related processes of collecting, storing, using, processing, transmitting, providing, disclosing, etc. of the personal information of the user are all performed on the premise of proving the consent of the user, and all conform to the rules of the related laws and regulations, and do not violate the popular regulations of the public order.
Under the large background of digital transformation of credit business, each financial institution restarts the construction of a credit system in a dispute. The credit system of the single-structure can not meet the change of market environment and the change of customer demands in time and high efficiency, and further the new-generation credit system is built by adopting the structure of a business center. On one hand, the service center system can be well adapted to a distributed architecture system in the technical aspect, and the performance can be greatly improved; on the other hand, on the aspect of service value, the service center can reflect the multiplexing of enterprise-level capability, reduce cost, quickly construct and support service scene innovation and trial-and-error. In the related art, the creation of a service center usually adopts a data-driven design manner to split micro services from a data topic level, or relies on experiences of a certain service expert, so that a capability center split is often unclear.
Accordingly, in view of the above-mentioned problems, the present disclosure proposes a method and apparatus for creating a service center.
The following describes a method and an apparatus for creating a service center in an embodiment of the present disclosure with reference to the accompanying drawings.
Fig. 1 is a flowchart illustrating a method for creating a service center according to a first embodiment of the present disclosure.
As shown in fig. 1, the method for creating the service center station may include the following steps:
step 101, obtaining the pending loan business field associated with the target loan product from the loan business field.
As one possible implementation manner of the embodiments of the present disclosure, the pending loan business field may be determined according to a business requirement, and as an example, the pending loan business field associated with the target loan product may be obtained from the loan business field, for example, the loan business field may include: the target loan product is a personal business loan, and the pending loan business field associated with the target loan product can comprise the marketing acquirer and the credit investigation, wherein the pending loan business field is a pending loan business field which can construct a business center.
Step 102, dividing the to-be-processed loan business fields according to the process nodes associated with the target loan products to obtain a plurality of sub-loan business fields.
In order to more accurately create a middle loan office, the to-be-processed loan office may be divided to obtain multiple sub-loan office domains, which may be divided, as an example, based on a process node associated with a target loan product, to obtain multiple sub-loan office domains. Wherein, the process node associated with the target loan product may comprise a loan 3 check process and a credit 6 major basic process, wherein, the loan 3 check process may comprise: pre-loan investigation, in-loan inspection and post-loan inspection; the large basic flow of trust 6 may include: credit investigation, credit rating, censoring approval, credit execution, post-loan management and property preservation, a number of sub-loan business areas may include: customer management, credit operation management, line management, deposit management, post-credit management, security management, and the like.
Step 103, determining the limit context of any sub-loan business field according to at least one field event in any sub-loan business field aiming at any sub-loan business field in a plurality of sub-loan business fields.
The bounding contexts are used for defining the domain boundaries of any sub-loan business domain, so as to ensure that each context meaning has a unique meaning within a specific boundary thereof, and the domain model exists within the boundary.
In order to avoid the problem of boundary collision of the service center, as a possible implementation manner, a limit context of any sub-loan service domain may be determined to define a domain boundary of any sub-loan service domain, so as to create the service center of any sub-loan service domain based on the limit context of any sub-loan service domain.
When determining the limit context of any sub-loan service domain, the service activities of any sub-loan service domain (such as new client, maintained client, issued loan, etc.) may be decomposed to obtain at least one decision command related to completing one domain event, and domain nouns (such as main body objects, accounts, etc.) and rules are extracted from the domain event and the at least one decision command, and aggregation is completed according to principles of semantic relevance, cohesion, orthogonality, etc., so as to obtain the limit context of any sub-loan service domain.
Step 104, creating a business center of any sub-loan business field according to the limit context of any sub-loan business field.
Furthermore, on the basis of determining the limit context of any sub-loan service field, the service center is created, so that the problem of boundary conflict of the created service center is avoided, and the coupling between the service center and the maintenance cost caused by the change of the requirements are reduced.
To sum up, the to-be-processed loan business field associated with the target loan product is obtained from the loan business field; dividing the loan business field to be processed according to the process node associated with the target loan product to obtain a plurality of sub-loan business fields; determining a limit context of any sub-loan business field according to at least one field event in any sub-loan business field aiming at any sub-loan business field in the plurality of sub-loan business fields; according to the limit context of any sub-loan business field, a business center of any sub-loan business field is created, therefore, the business center is divided according to the process node associated with the target loan product, so as to obtain a plurality of sub-loan business fields, the business field is divided without manual mode, the accuracy of the business field division is improved, and according to at least one field event in any sub-loan business field, the limit context of any sub-loan business field is determined, so that the business center of any sub-loan business field is created according to the limit context of any sub-loan business field, the creation of the business center is realized on the basis of determining the limit context of any sub-loan business field, the problem that the created business center has boundary conflict is avoided, and the complexity and maintenance cost of the business center are reduced.
To clearly illustrate how the above embodiment is directed to any sub-loan business domain of the plurality of sub-loan business domains, the present disclosure proposes another business center creation method that determines a bounding context of any sub-loan business domain according to at least one domain event in any sub-loan business domain.
Fig. 2 is a flowchart illustrating a method for creating a service center according to a second embodiment of the present disclosure.
As shown in fig. 2, the method for creating the service center station may include the following steps:
step 201, obtaining the pending loan business field associated with the target loan product from the loan business field.
Step 202, dividing the loan business field to be processed according to the process node associated with the target loan product to obtain a plurality of sub-loan business fields.
Step 203, for any domain event in at least one domain event in any sub-loan service domain, acquiring a decision command for implementing any domain event.
As a possible implementation manner of the embodiments of the present disclosure, for any sub-loan service domain, at least one domain event in the any sub-loan service domain may be acquired, for example, any sub-loan service domain is a client sub-domain, where the at least one domain event includes: the method comprises the steps that a company client is created, real person information is created, stockholder information is created, external investment is created and the like, and then, for any one of at least one domain event in any sub-loan service domain, a decision command for realizing the any one domain event can be obtained, for example, the any one domain event is created by the company client, the decision command for realizing the any one domain event is an input client profile, for example, the any one domain event is the real person information is created, and the decision command for realizing the any one domain event is an input real person.
Step 204, extracting the entity in the decision command of any domain event and any domain event respectively.
As an example, any domain event and a decision command of the any domain event may be input into the entity extraction model, respectively, to obtain an entity in the any domain event and the decision command of the any domain event. The entity extraction model learns to obtain the corresponding relation between the domain event and the entity and the corresponding relation between the decision command and the entity.
Step 205, generating a limit context of any sub-loan business domain according to the entity in each domain event and the entity in the decision command of each domain event in any sub-loan business domain.
In order to accurately determine the limit context of any sub-loan service field, a high-cohesive low-coupling aggregation can be constructed according to the entity in each field event in any sub-loan service field and the entity in the decision command of each field event, and then the aggregation is classified according to the context environment of any sub-loan service field so as to divide the limit context of any sub-loan service field.
Step 206, creating a service center of any sub-loan service field according to the limit context of any sub-loan service field.
It should be noted that, the execution process of steps 201 to 202 and step 206 may be implemented in any manner in each embodiment of the disclosure, which is not limited to this embodiment, and is not repeated.
In summary, a decision command for implementing any domain event is obtained by aiming at any domain event in at least one domain event in any sub-loan service domain; and respectively extracting the entity in the decision command of any field event and any field event, and generating the limit context of any sub-loan service field according to the entity in each field event in any sub-loan service field and the entity in the decision command of each field event, thereby generating the limit context of any sub-loan service field according to the entity in each field event in any sub-loan service field and the entity in the decision command of each field event, and improving the accuracy and the effectiveness of the limit context of any sub-loan service field.
To clearly illustrate how the above embodiments generate a bounding context for any sub-loan business segment based on entities in each segment event and entities in decision commands for each segment event in any sub-loan business segment, the present disclosure proposes another business segment creation method.
Fig. 3 is a flowchart illustrating a method for creating a service center according to a third embodiment of the present disclosure.
As shown in fig. 3, the method for creating the service center station may include the following steps:
step 301, obtaining a pending loan business field associated with a target loan product from the loan business field.
Step 302, dividing the to-be-processed loan business fields according to the process nodes associated with the target loan products to obtain a plurality of sub-loan business fields.
Step 303, for any domain event in at least one domain event in any sub-loan service domain, acquiring a decision command for implementing any domain event.
Step 304, the entities in the decision command of any domain event and any domain event are extracted respectively.
Step 305, determining at least one entity aggregation root corresponding to any sub-loan business domain from the entities in each domain event and the entities in the decision command of each domain event in any sub-loan business domain.
In order to facilitate understanding of business logic corresponding to sub-loan business domains, to construct a more reasonable and efficient business center, as an example, at least one entity aggregation root corresponding to any sub-loan business domain may be determined from entities in each domain event within any sub-loan business domain and entities in decision commands of each domain event.
As an example, association analysis is performed on the entities in the events of each domain and the entities in the decision commands of the events of each domain in the sub-loan service domain to determine association relationships and dependency relationships between the entities, and at least one entity aggregation root is determined according to the association relationships and the dependency relationships between the entities.
For example, a loan application event may involve multiple entities, such as an applicant, an application form, and a loan product, and there may be a certain association between these entities, for example, information in the application form corresponds to the entity, such as the applicant, the loan product, and in this process, it may be determined that the application form is one of the aggregation roots of the entities of the event in the field.
Step 306, aggregating the entities of the domain events and the decision commands of the domain events in any sub-loan service domain according to at least one entity aggregation root to obtain a plurality of aggregations.
As an example, the entities of the domain events and the decision commands of the domain events in any sub-loan service domain are aggregated according to the association relationship between at least one entity aggregation root and the entities of the domain events and the decision commands of the domain events in any sub-loan service domain, so as to obtain a plurality of aggregations.
Step 307, determining the limit context of any sub-loan business field according to the plurality of aggregations corresponding to any sub-loan business field.
In order to accurately determine the bounding context of any sub-loan business segment, in embodiments of the present disclosure, the bounding context of any sub-loan business segment may be determined based on a corresponding plurality of aggregations of any sub-loan business segment.
As an example, according to the context of any sub-loan business domain, classifying a plurality of aggregations to obtain at least one class cluster; the context environment is used for indicating a service scene and a service flow of any sub-loan service field; determining context boundaries of any type of clusters according to entities in any type of clusters for any type of clusters in at least one type of clusters; and determining the limit context of any sub-loan service field according to the context boundaries of various clusters.
That is, according to the context of any sub-loan business field, the relationship between the corresponding multiple aggregations of any sub-loan business field is determined, the multiple aggregations are categorized to obtain at least one cluster, the context boundary of any cluster is determined according to the entity in at least one cluster, and further, according to the business requirement, the bounding context of any sub-loan business field is determined from the context boundaries of various clusters, for example, the context boundary of any cluster is used as the bounding context of any sub-loan business field, and for example, the context boundary with the largest range and the context boundary with the largest range are determined from the context boundaries of various clusters, and the context boundary with the largest range and the largest range are used as the bounding context of any sub-loan business field.
Step 308, creating a service center of any sub-loan service field according to the limit context of any sub-loan service field.
It should be noted that, the execution process of steps 301 to 304 and step 308 may be implemented in any manner in each embodiment of the disclosure, which is not limited to this embodiment, and is not repeated herein.
In summary, determining at least one entity aggregation root corresponding to any sub-loan service domain from the entities in each domain event in any sub-loan service domain and the entities in the decision command of each domain event; according to at least one entity aggregation root, aggregating all domain events in any sub-loan business domain and entities of decision commands of all domain events to obtain a plurality of aggregations; according to the multiple aggregations corresponding to any sub-loan business field, the limit context of any sub-loan business field is determined, so that the limit context of any sub-loan business field can be accurately determined based on the multiple aggregations corresponding to any sub-loan business field, and the creation of the business center station is performed based on the limit context of any sub-loan business field, so that the problem that the created business center station has boundary conflict is avoided, and the complexity and maintenance cost of the business center station are reduced.
To clearly illustrate how any sub-loan business domain is modeled according to the bounding context of any sub-loan business domain in the above embodiments, the present disclosure proposes another business center creation method to obtain a domain model of any sub-loan business domain.
Fig. 4 is a flowchart illustrating a method for creating a service center according to a fourth embodiment of the present disclosure.
As shown in fig. 4, the method for creating the service center station may include the following steps:
step 401, obtaining a pending loan business field associated with a target loan product from the loan business field.
Step 402, dividing the to-be-processed loan business fields according to the process node associated with the target loan product to obtain a plurality of sub-loan business fields.
Step 403, determining, for any sub-loan business domain of the plurality of sub-loan business domains, a limit context of the any sub-loan business domain according to at least one domain event in the any sub-loan business domain.
The limit context is used for limiting the domain boundary of any sub-loan business domain.
Step 404, modeling any sub-loan business domain according to the limit context of any sub-loan business domain, so as to obtain a domain model of any sub-loan business domain.
It should be appreciated that, the domain model may perform abstract representation on the business flow, the data relationship and the interaction relationship between entities in any sub-loan business domain, so in order to improve the processing efficiency and accuracy of the loan business, in the embodiment of the disclosure, for any sub-loan business domain, any sub-loan business domain may be modeled, and a domain model of any sub-loan business domain is obtained.
As an example, a context service map of any sub-loan business field is obtained; acquiring the service flow of at least one loan service related to any sub-loan service field from a context service map of any sub-loan service field; determining the entity related to each service flow node of the service flow of at least one loan service in any sub-loan service field from the entities in the limit context of any sub-loan service field; a domain model of any sub-loan business domain is created based on the service flow of at least one loan service of any sub-loan business domain and the entities involved in each service flow node. It should be noted that, the context service map of each sub-loan service domain may be preset by a professional, and the context service map may include a service flow of at least one loan service related to the corresponding sub-loan service domain, and further, according to a limit context of any sub-loan service domain, an entity in the service flow of at least one loan service related to the any sub-loan service domain is limited, so that, according to the service flow of at least one loan service in any sub-loan service domain and an entity related to each service flow node, a domain model of any sub-loan service domain may be created.
Step 405, creating a service center of any sub-loan service domain according to the domain model of any sub-loan service domain.
In order to further improve the accuracy of creating the service center of any sub-loan service field, as a possible implementation manner, the field model of any sub-loan service field may be iteratively optimized, and based on the optimized field model, the service center of any sub-loan service field is created.
As an example, based on the general loan business process, business verification is performed on the domain model of any sub-loan business domain to obtain a verification result; responding to the difference between the verification result and the expected result being greater than the set difference, adjusting the domain model of any sub-loan service domain at least once until the adjusted domain model meets the expected result; and creating a business center of any sub-loan business field according to the field model of any sub-loan business field obtained by the last adjustment. For example, generating micro-services according to the domain model of any sub-loan business domain obtained by the last adjustment; according to the micro-service, a service center in any sub-loan service field is generated, namely, the service center in any sub-loan service field is generated by a micro-service architecture corresponding to any sub-loan service field.
It should be noted that the execution of steps 401 to 403 may be implemented in any manner in each embodiment of the disclosure, which is not limited to this embodiment, and is not repeated herein.
In summary, modeling any sub-loan business field according to the limit context of any sub-loan business field to obtain a field model of any sub-loan business field; according to the field model of any sub-loan service field, a service center of any sub-loan service field is created, so that the creation of the service center is realized on the basis of determining the limit context of any sub-loan service field, the problem that the created service center has boundary conflict is avoided, and the complexity and maintenance cost of the service center are reduced.
On the basis of any embodiment of the present disclosure, an implementation flow of the present disclosure may be as shown in fig. 5, and mainly includes the following steps:
1. to confirm the transformation scope of the project (the field of loan service to be processed), the construction of the project is always in a bottom-up mode, and local breakthrough is needed, which is generally the field for most urgent problem solving at present;
2. the method comprises the steps of carrying out preliminary subdomain division on the field of loan business to be processed, and suggesting to adopt six subdomains of customer management, credit operation management, credit management, deposit management, post-loan management, security management and the like by starting from business varieties and combining a loan 'three-check' basic flow and a credit 'six-major' core flow in a credit total flow:
3. Modeling operation is carried out for each sub-domain, business activities of the sub-domains (such as newly added clients, maintained clients and issued loans) are decomposed, a plurality of decision commands related to completing one domain event are obtained through analysis, domain nouns (such as main body objects, accounts and the like) and rules are extracted from the commands, aggregation is completed according to principles of semantic relevance, cohesiveness, orthogonality and the like, a limited context is obtained, and iterative optimization is carried out on the sub-domain model. After the bottom-up modeling is completed, viewing modeling results from the top-down angle by combining with real environments such as the actual running environment of the project and the input resources and completing reconstruction;
wherein, as shown in fig. 6, the modeling of each sub-domain (sub-loan service domain) may take the following steps:
(1) Identifying domain events, and listing all domain events in the subdomain by analyzing from the view of the flow and the business functions related to the flow;
(2) Identifying decision commands from the domain events, and marking commands which lead to the events for each event;
(3) Identifying domain nouns: extracting domain objects, namely entities, which generate the business behaviors from commands and domain events;
(4) Searching aggregation, finding out aggregation roots from the entities, finding out all entities and value objects related to the aggregation roots according to a business cohesion principle, and constructing 'high cohesion and low cohesion' aggregation;
(5) And identifying a limit context, classifying the aggregation according to a context semantic environment, defining a business domain limit context boundary and a context service map, and constructing a domain model.
As shown in fig. 7, the iterative optimization of the sub-domain model may take the following steps:
(1) Determining the identified loan service field to be processed and the division result of the subdomain;
(2) Developing implementation evaluation work, distinguishing the implementation requirements of business classes and technology classes from the view angle of credit project implementation, and forming a new range of business capability centers and a technical component implementation thought;
(3) Service verification, namely verifying the rationality of subdomain division by combining a general credit service flow and service activity analysis from an actual service scene, and evaluating the following aspects:
1) Whether traffic in the sub-domain is highly relevant;
2) Whether the domain model concept in the sub-domain is complete;
3) The coupling degree of different subfields on the technical level design;
(4) Problems are identified, for example, it is found that part of the subfields are less cohesive, and that highly traffic-dependent aggregations are split into different subfields. For example: the repayment plan is adjusted to a post-credit subdomain in advance of the repayment application aggregation; the loan exhibition period application, the non-repayment application and the like are aggregated and adjusted to a sub-field;
(5) And (5) optimizing and adjusting the identified problem subdomain. Three principles of adjustment. 1) And defining one or more aggregations into a limit context according to factors such as business and semantic boundaries to form a new domain model. 2) Recombination of polymerization: finding out the domain objects or functions which are aggregated in the same way but are dispersed in other domains, so that the domain model is incomplete or the business is not cohesive, the original model is broken, and new domain model reorganization or merging is completed. 3) Multiplexing: finding a domain or functional repetition occurs in multiple domain models, and can be considered refined into new domain models.
4. Forming a division of a final capability center (service center);
such as a product center, a customer center, a post-loan center, a line center, a cash center, a deposit center, a trust center, a process center, etc.
Corresponding to the method for creating a service center provided by the foregoing embodiment, the present disclosure further provides an apparatus for creating a service center, and since the apparatus for creating a service center provided by the embodiment of the present disclosure corresponds to the method for creating a service center provided by the foregoing embodiment, implementation of the method for creating a service center is also applicable to the apparatus for creating a service center provided by the embodiment of the present disclosure, which is not described in detail in the embodiment of the present disclosure.
Fig. 8 is a schematic structural diagram of a creation device of a service center shown in a fifth embodiment of the present disclosure.
As shown in fig. 8, the creation device 800 of the service center includes: the acquisition module 810, the partitioning module 820, the determination module 830, and the creation module 840.
The obtaining module 810 is configured to obtain, from a loan service field, a to-be-processed loan service field associated with a target loan product; the dividing module 820 is configured to divide the loan service domain to be processed according to the process node associated with the target loan product, so as to obtain a plurality of sub-loan service domains; a determining module 830, configured to determine, for any sub-loan business domain of the multiple sub-loan business domains, a bounding context of the any sub-loan business domain according to at least one domain event in the any sub-loan business domain; the limit context is used for limiting the domain boundary of any sub-loan business domain; the creating module 840 is configured to create a service center in any sub-loan service domain according to the limit context in any sub-loan service domain.
As a possible implementation manner of the embodiment of the present disclosure, the determining module 830 is configured to obtain, for any one of at least one domain event in any sub-loan service domain, a decision command for implementing the any one domain event; respectively extracting any domain event and an entity in a decision command of any domain event; and generating a limit context of any sub-loan business field according to the entity in each field event in any sub-loan business field and the entity in the decision command of each field event.
As a possible implementation manner of the embodiments of the present disclosure, the determining module 830 is further configured to determine at least one entity aggregation root corresponding to any sub-loan service domain from an entity in each domain event in any sub-loan service domain and an entity in a decision command of each domain event; according to at least one entity aggregation root, aggregating entities in each domain event and the entity of the decision command of each domain event in any sub-loan service domain to obtain a plurality of aggregations; and determining the limit context of any sub-loan business field according to the plurality of aggregations corresponding to any sub-loan business field.
As one possible implementation manner of the embodiment of the present disclosure, the determining module 830 is further configured to obtain an entity extraction model; and respectively inputting the decision command of any domain event and any domain event into the entity extraction model to obtain the entity of any domain event and the entity in the decision command of any domain event output by the entity extraction model.
As a possible implementation manner of the embodiment of the present disclosure, the determining module 830 is further configured to classify a plurality of aggregations according to a context of any sub-loan service field, to obtain at least one class cluster; the context environment is used for indicating the business scene and the business flow of any sub-loan business field; determining context boundaries of any type of clusters according to entities in any type of clusters for any type of clusters in at least one type of clusters; and determining the limit context of any sub-loan service field according to the context boundaries of various clusters.
As one possible implementation manner of the embodiments of the present disclosure, the creating module 840 is configured to model any sub-loan service field according to the limit context of any sub-loan service field, so as to obtain a field model of any sub-loan service field; and creating a business center of any sub-loan business field according to the field model of any sub-loan business field.
As a possible implementation manner of the embodiments of the present disclosure, the creating module 840 is further configured to obtain a context service map of any sub-loan service domain, and obtain a service flow of at least one loan service related to any sub-loan service domain from the context service map of any sub-loan service domain; determining the entity related to each service flow node of the service flow of at least one loan service in any sub-loan service field from the entities in the limit context of any sub-loan service field; a domain model of any sub-loan business domain is created based on the service flow of at least one loan service of any sub-loan business domain and the entities involved in each service flow node.
As one possible implementation manner of the embodiments of the present disclosure, the creating module 840 is further configured to perform service verification on the domain model of any sub-loan service domain based on the general loan service flow, so as to obtain a verification result; responding to the difference between the verification result and the expected result being greater than the set difference, adjusting the domain model of any sub-loan service domain at least once until the adjusted domain model meets the expected result; and creating a business center of any sub-loan business field according to the field model of any sub-loan business field obtained by the last adjustment.
As a possible implementation manner of the embodiment of the present disclosure, the creating module 840 is further configured to generate a micro service according to the domain model of any sub-loan service domain obtained by the last adjustment; and generating a business center in any sub-loan business field according to the micro-service.
As one possible implementation of the embodiments of the present disclosure, the multiple sub-loan service fields include: customer management, credit operation management, line management, deposit management, post-credit management and security management.
The creation device of the business center of the embodiment of the disclosure obtains the to-be-processed loan business field associated with the target loan product from the loan business field; dividing the loan business field to be processed according to the process node associated with the target loan product to obtain a plurality of sub-loan business fields; determining a limit context of any sub-loan business field according to at least one field event in any sub-loan business field aiming at any sub-loan business field in the plurality of sub-loan business fields; according to the limit context of any sub-loan business field, a business center of any sub-loan business field is created, therefore, the business center is divided according to the process node associated with the target loan product, so as to obtain a plurality of sub-loan business fields, the business field is divided without manual mode, the accuracy of the business field division is improved, and according to at least one field event in any sub-loan business field, the limit context of any sub-loan business field is determined, so that the business center of any sub-loan business field is created according to the limit context of any sub-loan business field, the creation of the business center is realized on the basis of determining the limit context of any sub-loan business field, the problem that the created business center has boundary conflict is avoided, and the complexity and maintenance cost of the business center are reduced.
In an exemplary embodiment, an electronic device is also presented.
Wherein, electronic equipment includes:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to execute instructions to implement a method of creation of a middlebox as set forth in any of the foregoing embodiments.
As an example, fig. 9 is a schematic structural diagram of an electronic device 900 according to an exemplary embodiment of the disclosure, where, as shown in fig. 9, the electronic device 900 may further include:
memory 910 and processor 920, bus 930 connecting different components (including memory 910 and processor 920), memory 910 stores a computer program, and when processor 920 executes the program, the method for creating a service center in accordance with the embodiments of the present disclosure is implemented.
Bus 930 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, micro channel architecture (MAC) bus, enhanced ISA bus, video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.
Electronic device 900 typically includes a variety of electronic device readable media. Such media can be any available media that is accessible by electronic device 900 and includes both volatile and nonvolatile media, removable and non-removable media.
Memory 910 may also include computer-system readable media in the form of volatile memory such as Random Access Memory (RAM) 940 and/or cache memory 950. The server 900 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 960 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 9, commonly referred to as a "hard disk drive"). Although not shown in fig. 9, a magnetic disk drive for reading from and writing to a removable non-volatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In such cases, each drive may be coupled to bus 930 via one or more data medium interfaces. Memory 910 may include at least one program product having a set (e.g., at least one) of program modules configured to carry out the functions of the various embodiments of the disclosure.
A program/utility 980 having a set (at least one) of program modules 970 may be stored, for example, in memory 910, such program modules 970 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules 970 generally perform the functions and/or methods in the embodiments described in this disclosure.
The electronic device 900 may also communicate with one or more external devices 990 (e.g., keyboard, pointing device, display 991, etc.), one or more devices that enable a user to interact with the electronic device 900, and/or any devices (e.g., network card, modem, etc.) that enable the electronic device 900 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 992. Also, the electronic device 900 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through a network adapter 993. As shown, the network adapter 993 communicates with other modules of the electronic device 900 over the bus 930. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 900, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
The processor 920 performs various functional applications and data processing by running programs stored in the memory 910.
It should be noted that, the implementation process and the technical principle of the electronic device in this embodiment refer to the foregoing explanation of the method for creating the service center in the embodiment of the disclosure, and are not repeated herein.
In an exemplary embodiment, a computer readable storage medium is also provided, e.g. a memory, comprising instructions executable by a processor of an electronic device to perform the method of creation of a service center proposed by any of the embodiments described above. Alternatively, the computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
In an exemplary embodiment, a computer program product is also provided, which comprises a computer program/instruction, characterized in that the computer program/instruction, when executed by a processor, implements the method for creating a service center according to any of the above embodiments.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (10)
1. A method for creating a service center, comprising:
acquiring a to-be-processed loan business field associated with a target loan product from the loan business field;
dividing the to-be-processed loan business field according to the process node associated with the target loan product to obtain a plurality of sub-loan business fields;
determining a limit context of any sub-loan business field in the plurality of sub-loan business fields according to at least one field event in the any sub-loan business field; the limit context is used for limiting the domain boundary of any sub-loan business domain;
and creating a business center of the any sub-loan business field according to the limit context of the any sub-loan business field.
2. The method of claim 1, wherein the determining, for any of the plurality of sub-loan business segments, a bounding context for the any sub-loan business segment based on at least one segment event within the any sub-loan business segment, comprises:
Acquiring a decision command for realizing any domain event in the at least one domain event in the any sub-loan service domain;
respectively extracting the entity in the decision command of any domain event and any domain event;
and generating a limit context of the sub-loan business field according to the entity in the event of each field in the sub-loan business field and the entity in the decision command of the event of each field.
3. The method of claim 2, wherein the generating the bounding context for the any sub-loan transaction domain based on the entities in the domain events and the entities in the decision commands for the domain events within the any sub-loan transaction domain comprises:
determining at least one entity aggregation root corresponding to the sub-loan business field from the entities in the events of each field and the entities in the decision commands of the events of each field in the sub-loan business field;
according to the at least one entity aggregation root, aggregating the entities in each domain event and the entities of the decision command of each domain event in any sub-loan service domain to obtain a plurality of aggregations;
And determining the limit context of any sub-loan service field according to the plurality of aggregations corresponding to the any sub-loan service field.
4. A method according to claim 3, wherein said determining a bounding context for said any sub-loan transaction field from a corresponding plurality of aggregations for said any sub-loan transaction field comprises:
classifying the plurality of aggregations according to the context of any sub-loan service field to obtain at least one class cluster; the context environment is used for indicating a business scene and a business flow of any sub-loan business field;
determining a context boundary of any cluster in the at least one cluster according to the entity in the any cluster;
and determining the limit context of any sub-loan service field according to the context boundaries of various clusters.
5. The method according to claim 2, wherein the extracting the entity in the decision command of the arbitrary domain event and the arbitrary domain event, respectively, comprises:
obtaining an entity extraction model;
and respectively inputting the decision command of any domain event and the decision command of any domain event into the entity extraction model to obtain the entity of the any domain event and the entity in the decision command of any domain event output by the entity extraction model.
6. The method of claim 1, wherein creating a business center for the any sub-loan business segment based on the bounding context for the any sub-loan business segment comprises:
and modeling any sub-loan business field according to the limit context of the any sub-loan business field to obtain a field model of the any sub-loan business field.
And creating a business center of the any sub-loan business field according to the field model of the any sub-loan business field.
7. The method of claim 6, wherein modeling the any sub-loan business segment based on the bounding context of the any sub-loan business segment to obtain a segment model of the any sub-loan business segment, comprises:
acquiring a context service map of any sub-loan service field, and acquiring a service flow of at least one loan service related to the any sub-loan service field from the context service map of the any sub-loan service field;
determining the entity related to each service flow node of the service flow of at least one loan service in any sub-loan service field from the entities in the limit context of the sub-loan service field;
And creating a domain model of the sub-loan business domain based on the service flow of at least one loan service of the sub-loan business domain and the entities related to each service flow node.
8. The method of claim 6, wherein creating a business center for the any sub-loan business segment based on the domain model for the any sub-loan business segment comprises:
based on the general loan business flow, carrying out business verification on the domain model of any sub-loan business domain to obtain a verification result;
responding to the difference between the verification result and the expected result being greater than the set difference, adjusting the domain model of any sub-loan service domain at least once until the adjusted domain model meets the expected result;
and creating a business center of the any sub-loan business field according to the field model of the any sub-loan business field obtained by the last adjustment.
9. The method according to claim 8, wherein creating the service center of the any sub-loan service field according to the last-time adjusted field model of the any sub-loan service field includes:
Generating micro-services according to the domain model of any sub-loan business domain obtained by the last adjustment;
and generating a business center in any sub-loan business field according to the micro-service.
10. A service center creation apparatus, comprising:
the acquisition module is used for acquiring the to-be-processed loan business field associated with the target loan product from the loan business field;
the dividing module is used for dividing the to-be-processed loan business field according to the flow node associated with the target loan product so as to obtain a plurality of sub-loan business fields;
a determining module, configured to determine, for any sub-loan business domain of the multiple sub-loan business domains, a limit context of the any sub-loan business domain according to at least one domain event in the any sub-loan business domain; the limit context is used for limiting the domain boundary of any sub-loan business domain;
and the creation module is used for creating a business center of any sub-loan business field according to the limit context of the any sub-loan business field.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311467000.8A CN117555655A (en) | 2023-11-06 | 2023-11-06 | Method and device for creating business center |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311467000.8A CN117555655A (en) | 2023-11-06 | 2023-11-06 | Method and device for creating business center |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117555655A true CN117555655A (en) | 2024-02-13 |
Family
ID=89817729
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311467000.8A Pending CN117555655A (en) | 2023-11-06 | 2023-11-06 | Method and device for creating business center |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117555655A (en) |
-
2023
- 2023-11-06 CN CN202311467000.8A patent/CN117555655A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107025509B (en) | Decision making system and method based on business model | |
| US8112340B2 (en) | Collateralized debt obligation evaluation system and method | |
| CN111340616B (en) | Method, device, equipment and medium for approving online loan | |
| US9031914B2 (en) | Tier-based data management | |
| US10083263B2 (en) | Automatic modeling farmer | |
| CN110992169A (en) | Risk assessment method, device, server and storage medium | |
| US20110153536A1 (en) | Computer-Implemented Systems And Methods For Dynamic Model Switching Simulation Of Risk Factors | |
| US20180253737A1 (en) | Dynamicall Evaluating Fraud Risk | |
| CN110930249A (en) | Large-scale enterprise credit risk prediction method and system, storage medium and electronic equipment | |
| US11037236B1 (en) | Algorithm and models for creditworthiness based on user entered data within financial management application | |
| CN109711849B (en) | Ether house address portrait generation method and device, electronic equipment and storage medium | |
| CN115545088B (en) | Model construction method, classification method, device and electronic equipment | |
| KR102434489B1 (en) | Self-evolving agent-based simulation system and method thereof | |
| CN117555655A (en) | Method and device for creating business center | |
| JP5156692B2 (en) | Pseudo data generation device, pseudo data generation method, and computer program | |
| CN114691882A (en) | Multi-source data real-time calculation method and device, storage medium and equipment | |
| CN112347102B (en) | Multi-table splicing method and multi-table splicing device | |
| US9529860B2 (en) | Keyword frequency analysis system | |
| EP2838065A1 (en) | Customer income estimator with confidence intervals | |
| US10877969B2 (en) | Augmenting structured data | |
| CN111639910A (en) | Standing book generation method, device, equipment and storage medium | |
| CN114565030B (en) | Feature screening method and device, electronic equipment and storage medium | |
| US20240144274A9 (en) | Transaction-risk evaluation by resource-limited devices | |
| Narendra et al. | TRENDS, OPPORTUNITIES AND CHALLENGES IN DIGITAL ECONOMY OF INDIA | |
| US20220342869A1 (en) | Identifying anomalous transformations using lineage data |
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 |