A method and apparatus for identifying a service object

Abstract

The application provides a method and device for identifying a business object, wherein the method for identifying the business object comprises the following steps: extracting business nouns from a pre-acquired business modeling database; performing business entity identification on the extracted business nouns according to a pre-set business entity identification strategy, clustering the identified business entities, and constructing a classification hierarchical structure based on the clustering result; acquiring a transverse correlation relationship between the business entities, marking the business entities corresponding to the transverse correlation relationship in the classification hierarchical structure based on the acquired transverse correlation relationship; acquiring a candidate business object based on the marked classification hierarchical structure; and verifying and adjusting the candidate business object according to a pre-set business object verification strategy to obtain the business object. The complexity of the business model can be reduced, and the business modeling accuracy can be improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of business modeling, in particular to a method and device for identifying business objects. BACKGROUND

[0002] Business modeling is a bridge for converting business architecture to IT architecture (system) and is used to drive IT architecture design through standardized business modeling. In the business modeling, a business component is an enterprise capability and is a basic, unique and non-repeated building block in an enterprise, which is composed of one or a group of business objects with high cohesion and loose coupling and all operations on the business objects, and is used to design business microservices of an IT architecture business middle platform. Therefore, the accuracy of identifying business objects directly affects the precision of business modeling.

[0003] In the business modeling, business objects are mainly identified by human experience, and the relationship between the identified business objects and the relationship between the business entities in the business objects are relatively complex, which does not meet the requirements of the principles of high cohesion and loose coupling, and is not suitable for quickly training business modeling related technical personnel, resulting in a complex business model based on business objects and low precision, so that after the business model is converted to the IT architecture, the boundaries between the microservices of the IT architecture are not clear, the coupling degree is high, the maintenance of the IT architecture is not convenient, the IT side cannot play a greater value, and the overall benefit is reduced. SUMMARY

[0004] Therefore, the purpose of the present application is to provide a method and device for identifying business objects to reduce the complexity of the business model and improve the precision of business modeling.

[0005] In a first aspect, the embodiments of the present application provide a method for identifying business objects, comprising:

[0006] extracting business nouns from a pre-acquired business modeling database;

[0007] performing business entity identification on the extracted business nouns according to a pre-set business entity identification strategy, clustering the identified business entities, and constructing a classification hierarchical structure based on the clustering results;

[0008] obtaining a horizontal association relationship between the business entities, and marking the business entities corresponding to the horizontal association relationship in the classification hierarchical structure based on the obtained horizontal association relationship;

[0009] obtaining a candidate business object based on the marked classification hierarchical structure;

[0010] performing verification and adjustment on the candidate business object according to a pre-set business object verification strategy, and obtaining a business object.

[0011] With reference to the first aspect, in a first possible implementation form of the first aspect, the candidate business object is obtained based on the identified root entity and the business entities contained in the root entity.

[0012] In the hierarchical structure of the labels, the last obtained clustering result is extracted to obtain a topic, and a business entity relationship model is constructed based on the topic and the business entities contained in the topic.

[0013] The root entity is identified based on the topic, the business entities contained in the topic, and the transverse correlation relationship between the business entities in the business entity relationship model, and the candidate business object is obtained based on the identified root entity and the business entities contained in the root entity.

[0014] With reference to the first possible implementation form of the first aspect, in a second possible implementation form of the first aspect, the root entity is identified based on the topic, the business entities contained in the topic, and the transverse correlation relationship between the business entities in the business entity relationship model, and the candidate business object is obtained based on the identified root entity and the business entities contained in the root entity.

[0015] For each topic, the topic is extracted to obtain an initial root entity.

[0016] For each classification level in the classification hierarchy structure corresponding to the topic, the business entities contained in the classification level are obtained, the business entities having the transverse correlation relationship label in the classification level are obtained to obtain a new root entity, the business entities between the initial root entity and the new root entity in the classification level without the correlation relationship label are obtained to obtain the business entities contained in the initial root entity, and the business entities between the new root entity and a next new root entity in the classification level without the correlation relationship label are obtained to obtain the business entities contained in the new root entity.

[0017] The root entity is obtained based on the initial root entity, the business entities contained in the initial root entity, the new root entity, and the business entities contained in the new root entity.

[0018] With reference to the first possible implementation form of the first aspect, in a third possible implementation form of the first aspect, the candidate business object is obtained based on the identified root entity and the business entities contained in the root entity.

[0019] For each root entity, the root entity and all subordinate business entities contained in the root entity are obtained to obtain a candidate business object, and each root entity corresponds to a candidate business object.

[0020] With reference to any one of the first aspect, the first possible implementation to the third possible implementation of the first aspect, embodiments of the present application provide a fourth possible implementation of the first aspect, wherein the verifying and adjusting the candidate business object according to the pre-set business object verification strategy comprises:

[0021] determining whether the number of business entities contained in the candidate business object is greater than or equal to a pre-set number threshold;

[0022] if yes, checking whether the types of business entities contained in the candidate business object include at least one root entity and one attribute entity of the root entity;

[0023] if yes, confirming whether each business entity in the marked classification hierarchy structure is included in the candidate business object, and whether each business entity is only attributed to one candidate business object;

[0024] if yes, confirming that the candidate business object is the business object.

[0025] With reference to the fourth possible implementation of the first aspect, embodiments of the present application provide a fifth possible implementation of the first aspect, wherein the method further comprises:

[0026] if the number of business entities contained in the candidate business object is less than the number threshold, or the types of business entities contained in the candidate business object do not include at least one root entity and one attribute entity of the root entity, or each business entity in the marked classification hierarchy structure is not included in the candidate business object, or the business entity is attributed to two or more candidate business objects, performing the step of identifying the extracted business noun as a business entity according to the pre-set business entity identification strategy.

[0027] With reference to any one of the first aspect, the first possible implementation to the third possible implementation of the first aspect, embodiments of the present application provide a sixth possible implementation of the first aspect, wherein the clustering the identified business entities and constructing a classification hierarchy structure based on the clustering result comprises:

[0028] performing hierarchical clustering on the identified business entities by using a pre-set clustering algorithm;

[0029] for each clustering result obtained last time, obtaining a classification hierarchy structure of the clustering result based on the clustering result and each hierarchical clustering result corresponding to the clustering result.

[0030] In the second aspect, embodiments of the present application provide a device for identifying a business object, comprising: a business noun extraction module, configured to extract business nouns from a pre-obtained business modeling database;

[0031] The hierarchical structure construction module is configured to perform business entity recognition on the extracted business nouns according to a preset business entity recognition strategy, cluster the recognized business entities, and construct a classification hierarchical structure based on the clustering result.

[0032] The association relationship marking module is configured to obtain a transverse association relationship between the business entities, and mark the business entities corresponding to the transverse association relationship in the classification hierarchical structure based on the obtained transverse association relationship.

[0033] The preliminary screening module is configured to obtain a candidate business object based on the marked classification hierarchical structure.

[0034] The business object acquisition module is configured to verify and adjust the candidate business object according to a preset business object verification strategy, and obtain the business object.

[0035] In a third aspect, an embodiment of the present application provides a computer device, which comprises a processor, a memory and a bus, the memory stores machine readable instructions executable by the processor, when the computer device is running, the processor and the memory communicate through the bus, and the machine readable instructions are executed by the processor to perform the steps of the method for identifying a business object.

[0036] In a fourth aspect, an embodiment of the present application provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to perform the steps of the method for identifying a business object.

[0037] The method and device for identifying a business object provided by the embodiment of the present application extract business nouns from a pre-acquired business modeling database; perform business entity identification on the extracted business nouns according to a pre-set business entity identification strategy, cluster the identified business entities, and construct a classification hierarchical structure based on the clustering result; acquire a horizontal association relationship between the business entities, mark the business entities corresponding to the horizontal association relationship in the classification hierarchical structure based on the acquired horizontal association relationship; acquire a candidate business object based on the marked classification hierarchical structure; and verify and adjust the candidate business object according to a pre-set business object verification strategy to obtain a business object. In this way, the business nouns are subjected to entity identification, the classification hierarchical structure is constructed based on the clustering result of the identified business entities, the horizontal association relationship between the business entities is acquired, two business entities with the horizontal association relationship in the classification hierarchical structure are separated, and the business object is constructed based on the vertical classification relationship of the business entities and the business entities without the horizontal association relationship. The business object constructed based on the vertical classification relationship of the business entities has high cohesion, and the business object contains the business entities without the horizontal association relationship, so that the business entities in the business object have mutual independence and the business entities in the same business object are loosely coupled, thereby realizing high cohesion and loose coupling of the business entities in the business object, effectively reducing the complexity of the business model constructed based on the business object, and improving the business modeling precision.

[0038] In order to make the above objectives, characteristics and advantages of the present application more apparent, the following will describe a preferred embodiment in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF DRAWINGS

[0039] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments. It should be understood that the following drawings only show some of the embodiments of the present application, and therefore should not be considered as a limitation to the scope. For those skilled in the art, other related drawings can also be obtained without creative labor.

[0040] Figure 1 Fig. 1 shows a flowchart of a method for identifying a business object provided by the embodiment of the present application;

[0041] Figure 2 Fig. 2 shows a schematic diagram of a classification hierarchical structure provided by the embodiment of the present application;

[0042] Figure 3 Fig. 3 shows a schematic diagram of a marked classification hierarchical structure provided by the embodiment of the present application;

[0043] Figure 4 Fig. 4 shows a schematic diagram of a business entity relationship model provided by the embodiment of the present application;

[0044] Figure 5 The embodiment of the present application is based on Figure 4 The obtained root entity schematic diagram is shown in the figure.

[0045] Figure 6 The embodiment of the present application is based on Figure 5 The obtained candidate business object schematic diagram is shown in the figure.

[0046] Figure 7 The device structure schematic diagram for identifying a business object provided by the embodiment of the present application is shown in the figure.

[0047] Figure 8 The structure schematic diagram of a computer device 800 provided by the embodiment of the present application is shown in the figure. DETAILED DESCRIPTION

[0048] In order to make the purpose, technical scheme and advantages of the embodiment of the present application clearer, the technical scheme of the embodiment of the present application will be described clearly and completely in combination with the drawings in the embodiment of the present application. Obviously, the described embodiment is only a part of the embodiment of the present application, but not all the embodiments. The components of the embodiment of the present application described and shown in the drawings can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiment of the present application provided in the drawings is not intended to limit the scope of the claimed present application, but only represents selected embodiments of the present application. Based on the embodiment of the present application, all other embodiments obtained by those skilled in the art without creative work belong to the scope of protection of the present application.

[0049] The embodiment of the present application provides a method and device for identifying a business object, which will be described below by an embodiment.

[0050] Figure 1 The method flow schematic diagram for identifying a business object provided by the embodiment of the present application is shown in the figure.

[0051] As Figure 1 shown, the method comprises:

[0052] Step 101, extracting a business noun from a pre-acquired business modeling database;

[0053] In the embodiment of the present application, as an optional embodiment, the business modeling data in the business modeling database includes but is not limited to business system data, operation manual data, transaction list data, business process modeling data, and product modeling result data. The business terms related to the key business resources are identified and extracted from the business modeling data by using the pre-set business term identification rules. The business term identification rules can be set by the business experts and experienced business practitioners after discussion, and as an optional embodiment, the business term identification rules can not need to pay attention to the granularity of the business terms to be identified, and as many business resources as possible are extracted from the business modeling data as the business terms, so that the extracted business terms can comprehensively reflect the business.

[0054] In the embodiment of the present application, as an optional embodiment, the business modeling data is preferably various business resources related to the business process modeling data.

[0055] In step 102, the extracted business terms are subjected to business entity identification according to the pre-set business entity identification strategy, the identified business entities are clustered, and the classification hierarchical structure is constructed based on the clustering results.

[0056] In the embodiment of the present application, the business entity is a collection of specific things obtained by abstraction according to business demand management and maintenance.

[0057] In the embodiment of the present application, the business entity identification strategy is a business entity identification rule, and the business terms meeting the business entity identification rule are extracted from the business terms and placed in the business entity library according to the pre-set business entity identification rule.

[0058] In the embodiment of the present application, as an optional embodiment, the business entity identification rule is set by the domain experts or experienced business practitioners in the field to which the business belongs.

[0059] In the embodiment of the present application, as an optional embodiment, the identified business entities are clustered, and the classification hierarchical structure is constructed based on the clustering results, including:

[0060] A11, the identified business entities are hierarchically clustered by using the pre-set clustering algorithm;

[0061] A12, for each clustering result obtained last time, the classification hierarchical structure of the clustering result is obtained based on the clustering result and each hierarchical clustering result corresponding to the clustering result.

[0062] In this embodiment of the invention, as an optional implementation, the clustering algorithm includes, but is not limited to: K-MEANS clustering algorithm, Mean shift clustering algorithm, Density Based Spatial Clustering of Applications with Noise (DBSCAN), and hierarchical clustering algorithm. The clustering algorithm is used to cluster business entities, obtaining multi-level clustering results. The top-level clustering results (the last obtained clustering results) constitute the upper-level classification hierarchy, and the multi-level business entities contained in this clustering result are the lower-level classification hierarchies, thus forming a hierarchical classification structure for business entities.

[0063] Figure 2 A schematic diagram of the classification hierarchy structure provided by an embodiment of the present invention is shown. For example... Figure 2 As shown, by clustering each business entity, a hierarchical clustering result is obtained. Assuming that the last obtained clustering result includes: participants and contracts, for participants (first-level classification level), the corresponding lower-level classification level (second-level classification level) includes: individual customers, corporate customers, interbank customers, etc. For contracts (first-level classification level), the corresponding lower-level classification level (second-level classification level) includes: product contracts, resource item contracts, etc.; for product contracts, the corresponding lower-level classification level (third-level classification level) includes: deposit contracts, loan contracts, etc.

[0064] In this embodiment of the invention, as an optional embodiment, business entities are subjected to hierarchical clustering analysis based on common data model themes to obtain hierarchical clustering results. The common clustering results corresponding to the first-level classification level include themes such as participants and contracts.

[0065] In this embodiment of the invention, as another optional embodiment, taking financial business as an example, the existing assets of the financial institution corresponding to the financial business can also be referenced. For example, the classification hierarchy set in the financial data standard can be used as the hierarchical clustering result. Based on the set hierarchical clustering result, the business entity is classified into corresponding hierarchical categories to obtain business entities with a classification hierarchy structure.

[0066] Step 103: Obtain the horizontal relationships between business entities; based on the obtained horizontal relationships, mark the business entities corresponding to the horizontal relationships in the classification hierarchy.

[0067] In this embodiment of the invention, the inherent relationship between one business entity and another is described using the term "Business Entity Relationship." As an optional embodiment, the relationship entity includes: vertical classification relationships and horizontal association relationships.

[0068] Vertical Classification Relationship, used to represent the classification structure and content system refined layer by layer in the information contained by the business entity.

[0069] Horizontal Association Relationship, used to represent the connection between business entities. The Horizontal Association Relationship establishes a stable and directly callable connection between one business entity and another business entity.

[0070] In the embodiment of the application, the hierarchical structure in the classification hierarchy is a vertical classification relationship. For the horizontal association relationship, any two business entities are selected, relationship data is extracted from the business modeling data corresponding to the two business entities according to the pre-set relationship extraction rules, and it is determined whether the two business entities have a horizontal association according to the relationship data and the pre-set association algorithm, so as to construct the horizontal association relationship between the business entities by identifying the horizontal association relationship between the business entities, merge the obtained horizontal association relationship into one of the business entities, and label the two business entities according to the obtained horizontal association relationship. For example, by analyzing and abstracting the business modeling data corresponding to the business entities, relationship data is obtained, and a horizontal association relationship of signing information is obtained based on the relationship data and the association algorithm. The signing information can be classified into the "relationship between customer and contract" business entity. As an optional embodiment, the association relationship information of the product conditions used by the product components is classified into the "product component and product condition relationship" business entity.

[0071] In the embodiment of the application, the classification hierarchy structure that is labeled contains horizontal association relationship and vertical classification relationship. The business entities of the upper and lower levels of the classification hierarchy structure have vertical classification relationship, and the business entities at the same level have or do not have horizontal association relationship.

[0072] Figure 3 A labeled classification hierarchy structure provided by an embodiment of the application is shown. As shown in FIG. 1, the classification hierarchy structure is composed of a plurality of business entities, and the business entities are arranged in a hierarchical structure. The business entities at the same level have horizontal association relationship, and the business entities of the upper and lower levels have vertical classification relationship. Figure 3As shown, for example, in the marked classification hierarchy, the business entity (clustering result) is a participant, and under the corresponding first-level hierarchy, a plurality of second-level hierarchies can be included, which are respectively: participant name information, individual, organization, organization unit, for the case that the second-level hierarchy is participant name information, a third-level hierarchy: individual name information can be included, for the last obtained clustering result is a participant role, under the corresponding first-level hierarchy, two second-level hierarchies: customer and employee are included. Among them, the first-level hierarchy, the second-level hierarchy and the third-level hierarchy are vertical classification relationships of the business entity, if the first-level hierarchy participant role has a horizontal association relationship with the first-level hierarchy participant, the horizontal association relationship is the participant and participant role relationship.

[0073] In step 104, the candidate business object is obtained based on the marked classification hierarchy.

[0074] In the embodiment of the application, as an optional embodiment, the candidate business object is obtained based on the marked classification hierarchy, and the method comprises the following steps:

[0075] B11, in the marked classification hierarchy, the last obtained clustering result is extracted to obtain a theme, and a business entity relationship model is constructed based on the theme and the business entity contained in the theme;

[0076] In the embodiment of the application, the clustering result is taken as a theme, and the business entity corresponding to the classification hierarchy below the classification hierarchy where the clustering result is located in the classification hierarchy structure is the business entity contained in the theme.

[0077] In the embodiment of the application, as an optional embodiment, the theme includes but is not limited to: participant, contract, etc.

[0078] In the embodiment of the application, as an optional embodiment, the constructed business entity relationship model is shown in Table 1.

[0079] Table 1

[0080]

[0081]

[0082] B12, based on the theme, the business entity contained in the theme and the horizontal association relationship between the business entities in the business entity relationship model, a root entity is identified, and a candidate business object is obtained based on the identified root entity and the business entity contained in the root entity.

[0083] In the embodiment of the application, as an optional embodiment, the root entity is identified based on the theme, the business entity contained in the theme and the horizontal association relationship between the business entities in the business entity relationship model, and the method comprises the following steps:

[0084] B121, for each subject, extract the subject to obtain an initial root entity;

[0085] In the embodiment of the present application, the business entity contained in the subject is a classification level business entity of the initial root entity.

[0086] B122, for each classification level in the classification level structure corresponding to the subject, obtain each business entity contained in the classification level, obtain the business entity with a horizontal association relationship mark in the classification level, obtain a new root entity, obtain the business entity without an association relationship mark between the initial root entity and the new root entity in the classification level, obtain the business entity contained in the initial root entity, and obtain the business entity contained in the new root entity according to the business entity without an association relationship mark between the new root entity and the next new root entity in the classification level;

[0087] B123, based on the initial root entity, the business entity contained in the initial root entity, the new root entity, and the business entity contained in the new root entity, obtain a root entity.

[0088] In the embodiment of the present application, for the marked classification level structure, each business entity contained in the classification level is analyzed to determine whether the business entity is a root entity, until the business entity contained in the classification level of the last level is analyzed to obtain the mapping relationship between the root entity and the business entity, wherein the root entity includes the initial root entity and the new root entity. That is, if the business entity has a relationship entity (horizontal association relationship) with other business entities, the two business entities are taken as new root entities, until the business entity of the lowest level is analyzed and the identification of the root entity is confirmed to be completed. For example, for the subject: participant, the participant corresponding to the subject is a root entity. Based on the subject, the relationship entity existing between all business entities is analyzed layer by layer from the upper level to the lower level using the vertical classification relationship of the business entity corresponding to the subject, and the business entity with the relationship entity is taken as a new root entity. For example, the business entity "customer" has a horizontal association relationship with the business entity "product contract", so the business entity "customer" and the business entity "product contract" are respectively identified as new root entities.

[0089] In the embodiment of the present application, as an optional embodiment, an entity relationship view can also be generated according to the vertical classification relationship of the business entity and the horizontal association relationship of the business entity to display the relationship between the business entities, wherein the fields displayed include but are not limited to: entity type, root entity ID, subordinate upper entity ID, and relationship entity ID. For example, if the business entity C is a root entity, the corresponding entity type is 0, the business entity A belongs to the business entity B, and the business entity C is taken as a root entity, then the fields (entity type, root entity ID, subordinate entity ID, relationship entity ID) in the business entity A data are (1, C_ID, B_ID, NULL).

[0090] In this embodiment of the invention, after marking the root entity, a root entity identification check can be performed. This checks all business entities whose relational entity IDs are not null and whose entity type is not 0. For example, if the fields in the data of business entity A are (1, C_ID, B_ID, D_ID), then they are updated to (0, NULL, NULL, D_ID). Simultaneously, the root entity IDs of all subordinate entities of business entity A are updated to A_ID. For example, if the fields in the data of business entity E are (1, C_ID, A_ID, D_ID), then they are updated to (1, A_ID, A_ID, NULL).

[0091] In this embodiment of the invention, since each topic is related to at least one other topic, each topic is the default initial root entity.

[0092] Figure 4 This is a schematic diagram of a business entity relationship model provided for an embodiment of the present invention. Figure 4 As shown, there are two topics, both of which have three-level classification levels. Topics 1 and 2 are the first-level classification levels. The second-level classification levels corresponding to topic 1 include: business entity A, business entity B, and business entity C. The second-level classification levels corresponding to topic 2 include: business entity D, business entity E, and business entity F. Business entity D and business entity E have a horizontal relationship (relationship entities).

[0093] The three-level classification hierarchy corresponding to business entity A includes: business entity A1, business entity A2, and business entity A3;

[0094] The three-level classification hierarchy corresponding to business entity B includes: business entity B1, business entity B2 and business entity B3;

[0095] The three-level classification hierarchy corresponding to business entity C includes: business entity C1, business entity C2, and business entity C3;

[0096] The three-level classification hierarchy corresponding to business entity D includes: business entity D1, business entity D2, and business entity D3;

[0097] The three-level classification hierarchy corresponding to business entity E includes: business entity E1, business entity E2 and business entity E3;

[0098] The three-level classification hierarchy corresponding to business entity F includes: business entity F1.

[0099] Figure 5 The embodiments of the present invention are based on Figure 4 A schematic diagram of the resulting root entity. (See diagram below.) Figure 5 As shown, root entity 1 corresponds to topic 1, root entity D corresponds to business entity D, and root entity E corresponds to business entity E.

[0100] In an embodiment of the present application, as an optional embodiment, candidate business objects are acquired based on the identified root entity and the business entities contained in the root entity, including:

[0101] For each root entity, the root entity and all subordinate business entities contained in the root entity are acquired to obtain a candidate business object, and each root entity corresponds to a candidate business object.

[0102] Figure 6 In an embodiment of the present application, based on the root entity and the business entities contained in the root entity, candidate business objects are acquired, including: Figure 5 A schematic diagram of the obtained candidate business objects is shown in FIG. 1. As shown in FIG. 1, three candidate business objects are obtained, which are candidate business object 1, candidate business object 2 and candidate business object 3. Figure 6

[0103] In an embodiment of the present application, for each root entity, each business entity under the root entity is analyzed layer by layer according to the classification hierarchy, and all business entities in the lower layer of the root entity are taken as a whole as a business object. Based on each candidate business object, an initial model of a business object is established.

[0104] In an embodiment of the present application, business entities can be classified according to business entity types (Business Entity Type). As an optional embodiment, the business entity types include: root entity, attribute entity and relationship entity, wherein,

[0105] The root entity (Root Entity) is a basic business entity, which is the basic structure of the business entity;

[0106] The attribute entity (Attribute Entity) is used to expand the information of the root entity, which is the information describing the root entity, including business entities in each classification hierarchy. Taking a theme as an example, for the theme as a root entity, the attribute entity of the theme needs to be classified into a business object, for example, the business entities in the subordinate classification hierarchy of the “participant name information” and the “participant permission information” under the “participant” root entity are classified into the participant business object.

[0107] The relationship entity (Relationship Entity) is used to connect the root entities, and describes the horizontal association relationship between the root entities.

[0108] In an embodiment of the present application, the horizontal association relationship (Horizontal Association Relationship) between the root entities can also be checked and confirmed, and only the horizontal association relationship between the root entities is allowed to abstractly represent the relationship between the subordinate business entities.

[0109] ​In the embodiment of the present application, as an optional embodiment, the subordinate business entity under the root entity is established after the root entity is established, and the root entity is finally eliminated after the subordinate business entity is eliminated.

[0110] In the embodiment of the present application, the business objects are divided from the business logic and the business flow, the cohesion of the business and the complexity of the subsequent IT implementation are comprehensively considered, so that the present situation of the IT system can be avoided to interfere. The division granularity of the business objects.

[0111] In the embodiment of the present application, as an optional embodiment, the business object table is used to store the business objects and the association relationship between the business objects and the business entities after the business objects and the association relationship between the business objects and the business entities are established, wherein the business objects and the association relationship between the business objects and the business entities are saved in the field mode in the business object table, and the field includes but is not limited to the business object ID, the business object name and the root entity ID. For example, the business object DEMO corresponds to the root entity C, and the field (business object ID, business object name, root entity ID) stored in the business object table is (DEMO_ID, DEMO, C_ID). As another optional embodiment, when the business object and the association relationship between the business object and the business entity need to be added, the field (entity type, root entity ID, subordinate entity ID, business object ID) is set to (0, NULL, NULL, NEW_Object_ID) in the business object table, and the set field is updated based on the root entity and all subordinate entities under the root entity after the root entity serving as the business object is obtained.

[0112] In the embodiment of the present application, all subordinate business entities of the root entity are completely identified to form the business object, so that the creation sequence of the business entity is perfected, the business entity created after the root entity is created is regarded as the subordinate business entity of the root entity, and the root entity and the subordinate business entity of the root entity are classified into the same business object.

[0113] In step 105, the candidate business object is verified and adjusted according to the pre-set business object verification strategy to obtain the business object.

[0114] In the embodiment of the present application, as an optional embodiment, the business object verification strategy includes but is not limited to the number of business entities contained in the business object, the type of business entity contained in the business object and the range of business entity contained in the business object.

[0115] In the embodiment of the present application, as an optional embodiment, the candidate business object is verified and adjusted according to the pre-set business object verification strategy, including:

[0116] For each candidate business object, it is judged whether the number of business entities contained in the candidate business object is greater than or equal to a pre-set number threshold value;

[0117] If yes, it is checked whether the types of business entities contained in the candidate business object include at least one root entity and one attribute entity of the root entity;

[0118] If yes, it is confirmed whether each business entity in the marked classification hierarchy structure is included in the candidate business object, and each business entity is only attributed to one candidate business object;

[0119] If yes, the candidate business object is confirmed as a business object.

[0120] In the embodiment of the present application, as another optional embodiment, the method further comprises:

[0121] If the number of business entities contained in the candidate business object is less than the number threshold value, or the types of business entities contained in the candidate business object do not include at least one root entity and one attribute entity of the root entity, or each business entity in the marked classification hierarchy structure is not included in the candidate business object, or the business entity is attributed to two or more candidate business objects, the step of performing business entity recognition on the extracted business nouns according to the pre-set business entity recognition strategy is executed.

[0122] In the embodiment of the present application, as long as any rule in the business object verification strategy is not met, the business entity recognition is re-performed. As an optional embodiment, the business entity recognition is performed on the business modeling data corresponding to the candidate business object which does not meet the business object verification strategy, so as to adjust the classification hierarchy structure of the business entities contained in the business object, until the business object verification strategy is met. The candidate business object which meets the business object verification strategy is the business object.

[0123] In the embodiment of the present application, as an optional embodiment, the number threshold value is 2. Of course, in actual application, the number threshold value can also be set to other numerical values.

[0124] In the embodiment of the present application, for each candidate business object, the number of business entities contained in the candidate business object is obtained, it is confirmed that each candidate business object contains one root entity and more than one attribute entity of the root entity; at the same time, the attribution of each business entity is confirmed, so as to ensure that each business entity, whether a root entity, an attribute entity or a relationship entity, is included in the candidate business object, and each business entity is not repeated or missed.

[0125] Table 2 is a business object initial model or a business object model template and a field description.

[0126] Table 2

[0127]

[0128]

[0129] In the embodiment of the present application, as an optional embodiment, when verifying the candidate business object, the business object ID of the business data in the initial model of the business object (business object table) is taken as the retrieval object to retrieve the number of business entities contained in the candidate business object, and if the number is greater than 2 and at least the business entity type is 0 and 1; then, it is determined that the case where the candidate business object ID is NULL does not exist in the table, or the business entity cannot be found in the table according to the candidate business object ID, and then the check is successful. Further, the business entity relationship diagram, the business object and the business entity relationship diagram can also be displayed.

[0130] In the embodiment of the present application, if the check fails, as an optional embodiment, it can also prompt that the verification of the business object fails, and notify the relevant personnel (input personnel) to recheck the input business modeling data.

[0131] In the embodiment of the present application, by verifying and checking the candidate business object, the scope and relationship of each candidate business object are confirmed, and if the candidate business object does not meet the business object verification strategy, the vertical classification relationship and the horizontal association relationship of the business entities in the candidate business object are adjusted until the candidate business object identification work is completed. Compared with the existing business object identification method, the structure of the business entities in the business object and the number relationship of the contained business entities are ignored, and in the embodiment of the present application, the obtained business object includes at least two business entities: a root entity and an attribute entity of the root entity, and it is confirmed that each business entity belongs to a business object, and each business entity only belongs to one business object, so that according to the obtained business object, the design of the IT to the data object or aggregation can be better guided.

[0132] The method of the embodiment of the present application can effectively reduce the error caused by the artificial division of the business object, and reduce the complexity of the business entity relationship of the later business object identification result. Further, by improving and confirming the relationship between the root entities, the relationship between the subordinate business entities under the root entities is abstractly represented by using the horizontal association relationship between the root entities.

[0133] In the embodiment of the present application, based on the pre-constructed vertical classification relationship model, for example, B model, the acquired business entities are vertically classified, and based on the horizontal association relationship model, for example, C model, the horizontal association relationship between the entities is acquired, and based on the vertical classification relationship and the horizontal association relationship of the business entities, the business objects are identified, so that the business objects are high cohesion and loose coupling, the business object model constructed based on the business objects is located at the first layer of the data model system, records the business information, embodies the business behavior state, and defines the relationship between the root entities.

[0134] In the embodiment of the present application, when the business object identification is performed, the vertical classification relationship of the business entities and the horizontal association relationship of the business entities are used as the identification basis, so that a simplified business object identification and definition method of business entity relationship is brought, qualified data modeling or counterpart technology personnel can be trained in a short period of time, so that large-scale data modeling asset construction and understanding work can be carried out. Further, the business object constructed by using the vertical classification relationship of the business entities has high cohesion, and the two business entities with horizontal association relationship in the classification hierarchical structure are separated and used as the business entities of two business objects respectively, the high cohesion and loose coupling of the business entities in the business object are realized, the granularity of the business object is appropriate, the boundary between the formed micro services is clearer, the granularity of the aggregation in the DDD concept can be better provided as a reference, so as to guide the granularity of the aggregation of the IT system micro services. Moreover, by defining the identification standardization method of the business object, the process model and the product model of the enterprise-level business modeling are further docked, and the achievement standardization of the enterprise-level business modeling is facilitated. In addition, the data concept analysis can be carried out without being based on the traditional whole-line level, flexible field-level modeling can be supported, the business object can form a logical knowledge graph of business data, and the information such as the containing relationship, the inheritance relationship, the generation sequence of data and the like of each concept is clearly presented.

[0135] In the embodiment of the present application, as an optional embodiment, the method further comprises:

[0136] The business micro service is created based on the business object, and the data model is obtained.

[0137] In the embodiment of the present application, the micro service (Microservice) is a small service composed of a single application interface (API), has its own process and light processing, is deployed in a fully automatic manner, can communicate with other micro services by using the HTTP API, and can be edited by using different programming languages and databases, and is convenient to implement.

[0138] In the embodiment of the present application, the business microservice is created based on the business object, and the business microservice contains the business object and the process of processing the business object. The business microservice in the embodiment of the present application is a cluster of business entities under a business object, and is essentially a collection of business capabilities. The same business microservice can support the same business target in terms of business capabilities, and the business entities created or maintained by the same business microservice are closely related.

[0139] In the embodiment of the present application, the business microservice is constructed based on the clustered business entities, so that the boundaries between the business microservices are clear, and the dependency and correlation are small. Meanwhile, the input and output of each business microservice and the processing object are clear and complete, and the business capability can be independently provided.

[0140] In the embodiment of the present application, the business microservice can be used to design the business middle platform service of the IT architecture, and corresponds to the IT application microservice. The steps associated with the business microservice can be used to design the API or function exposed by the business middle platform service, and correspond to the IT application API / functional interface. In the embodiment of the present application, the microservice design of the IT architecture is based on two main models of process modeling and data modeling. The business microservice is constructed based on the identified business object. The business microservice (business side) corresponds to the IT application microservice (IT side), the business object (business side) corresponds to the IT application aggregation (IT side), and the step (business side) corresponds to the IT application API / functional interface. The business object comes from the business process, is the internal execution capability defined from the perspective of enterprise internal, the responsibility division of the business process and information, is the structured embodiment of resources, and realizes the integration of business resources. The business object in the embodiment of the present application is a meaningful minimum entity set used in the enterprise, which can effectively improve the efficiency of entity use in the business, reflects the business behavior state, defines the relationship between each business data, establishes a unified business common terminology, and assists the IT design to produce an assemblyable aggregation in the technical end, so as to support the system design with good integration effect.

[0141] Figure 7 The device structure schematic diagram for identifying the business object provided by the embodiment of the present application is shown.

[0142] As shown in Figure 7 The device includes:

[0143] The business noun extraction module 701 is configured to extract business nouns from a pre-acquired business modeling database.

[0144] In the embodiment of the present application, as an optional embodiment, the business modeling data in the business modeling database includes but is not limited to: business system data, operation manual data, transaction list data, business process modeling data, product modeling result data.

[0145] The hierarchical structure construction module 702 is configured to perform business entity recognition on the extracted business nouns according to a preset business entity recognition strategy, cluster the recognized business entities, and construct a classification hierarchical structure based on the clustering results.

[0146] In the embodiment of the present application, as an optional embodiment, the hierarchical structure construction module 702 includes:

[0147] The entity recognition unit (not shown in the figure) is configured to perform business entity recognition on the extracted business nouns according to a preset business entity recognition strategy.

[0148] The clustering unit is configured to perform hierarchical clustering on the recognized business entities by using a preset clustering algorithm.

[0149] In the embodiment of the present application, as an optional embodiment, the clustering algorithm includes but is not limited to: K-MEANS clustering algorithm, mean shift clustering algorithm, DBSCAN, and hierarchical clustering algorithm.

[0150] The hierarchical construction unit is configured to, for each clustering result obtained last time, obtain a classification hierarchical structure of the clustering result based on the clustering result and each hierarchical clustering result corresponding to the clustering result.

[0151] The association relationship marking module 703 is configured to obtain a horizontal association relationship between business entities, and mark the business entities corresponding to the horizontal association relationship in the classification hierarchical structure based on the obtained horizontal association relationship.

[0152] In the embodiment of the present application, the classification hierarchical structure that is marked contains the horizontal association relationship and the vertical classification relationship. The business entities of the upper and lower levels of the classification hierarchical structure have the vertical classification relationship, and the business entities of the same level have or do not have the horizontal association relationship.

[0153] The preliminary screening module 704 is configured to obtain a candidate business object based on the marked classification hierarchical structure.

[0154] In the embodiment of the present application, as an optional embodiment, the preliminary screening module 704 includes:

[0155] The theme construction unit (not shown in the figure) is configured to extract the clustering result obtained last time in the marked classification hierarchical structure to obtain a theme, and construct a business entity relationship model based on the theme and the business entities contained in the theme.

[0156] In the embodiments of the present application, as an optional embodiment, the subject matter includes but is not limited to the participants, the contract, etc.

[0157] The preliminary screening unit is configured to identify a root entity based on the subject matter in the business entity relationship model, the business entities contained in the subject matter, and the transverse association relationship between the business entities, and obtain a candidate business object based on the identified root entity and the business entities contained in the root entity.

[0158] In the embodiments of the present application, as an optional embodiment, the preliminary screening unit is specifically configured to:

[0159] For each subject matter, the subject matter is extracted to obtain an initial root entity;

[0160] For each classification level in the classification hierarchy corresponding to the subject matter, the business entities contained in the classification level are obtained, the business entities with the transverse association relationship mark in the classification level are obtained, a new root entity is obtained, the business entities without the association relationship mark between the initial root entity and the new root entity in the classification level are obtained, the business entities contained in the initial root entity are obtained, and the business entities contained in the new root entity are obtained according to the business entities without the association relationship mark between the new root entity and a next new root entity in the classification level;

[0161] The root entity is obtained based on the initial root entity, the business entities contained in the initial root entity, the new root entity, and the business entities contained in the new root entity.

[0162] In the embodiments of the present application, as another optional embodiment, the preliminary screening unit is specifically further configured to:

[0163] For each root entity, the root entity and all subordinate business entities contained in the root entity are obtained to obtain a candidate business object, and each root entity corresponds to a candidate business object.

[0164] The business object obtaining module 705 is configured to verify and adjust the candidate business object according to a pre-set business object verification strategy to obtain a business object.

[0165] In the embodiments of the present application, as an optional embodiment, the business object obtaining module 705 is specifically configured to:

[0166] For each candidate business object, it is judged whether the number of business entities contained in the candidate business object is greater than or equal to a pre-set number threshold;

[0167] If yes, it is checked whether the types of the business entities contained in the candidate business object at least include one root entity and one attribute entity of the root entity;

[0168] If yes, it is confirmed whether each business entity in the marked classification hierarchy is included in the candidate business object, and each business entity is only included in one candidate business object.

[0169] If yes, it is confirmed that the candidate business object is the business object.

[0170] In the embodiment of the present application, as another optional embodiment, the business object acquisition module 705 is specifically further used for:

[0171] If the number of business entities included in the candidate business object is less than the number threshold, or the types of business entities included in the candidate business object include one root entity and one attribute entity of the root entity, or each business entity in the marked classification hierarchy is not included in the candidate business object, or the business entity is included in two or more candidate business objects, the step of performing business entity recognition on the extracted business nouns according to the pre-set business entity recognition strategy is executed.

[0172] In the embodiment of the present application, as an optional embodiment, the device further includes:

[0173] The data model construction module (not shown in the figure) is used for creating a business microservice based on the business object, and obtaining a data model.

[0174] In the embodiment of the present application, the business microservice is created based on the business object, and the business microservice includes the business object and a process for processing the business object.

[0175] As shown in Figure 8 , an embodiment of the present application provides a computer device 800 for executing the method for identifying a business object in Figure 1 , and the device includes a memory 801, a processor 802 connected to the memory 801 through a bus, and a computer program stored in the memory 801 and executable on the processor 802, wherein the processor 802 executes the computer program to realize the steps of the method for identifying a business object.

[0176] Specifically, the memory 801 and the processor 802 can be a general memory and processor, which are not specifically limited here, and when the processor 802 runs the computer program stored in the memory 801, the method for identifying a business object can be executed.

[0177] Corresponding to the method for identifying a business object in Figure 1 , an embodiment of the present application further provides a computer readable storage medium, and the computer readable storage medium stores a computer program, and the computer program is executed by a processor to execute the steps of the method for identifying a business object.

[0178] Specifically, the storage medium can be a general storage medium such as a mobile disk, a hard disk, etc., and the computer program on the storage medium can execute the method of identifying the business object when the computer program is run.

[0179] In the embodiments provided by the present application, it should be understood that the disclosed system and method can be implemented in other manners. The embodiments described above are merely exemplary, for example, the division of the units is only a logical function division, and there can be another division manner in actual implementation; for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections between different units, can be indirect couplings or communication connections through some interfaces, and electrical, mechanical or other forms.

[0180] The units described as separate components can or can not be physically separate, and the components displayed as units can or can not be physical units, i.e., can be located in one place, or can be distributed on a plurality of network units. In actual implementation, some or all of the units can be selected according to the actual needs to achieve the purposes of the embodiments.

[0181] In addition, each functional unit in the embodiments provided by the present application can be integrated into one processing unit, or each unit can exist physically as a separate unit, or two or more units can be integrated into one unit.

[0182] The functions described above can be implemented in the form of software function units and sold or used as an independent product, which can be stored in a computer readable storage medium. Based on such an understanding, the technical solutions of the present application essentially, or part of the technical solutions that make contributions to the prior art, or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The foregoing storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, and various media that can store program codes.

[0183] It should be noted that: similar reference numerals and letters in the following drawings represent similar items, and therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. In addition, the terms "first", "second", "third", etc. are only used to distinguish descriptions, and cannot be understood as indicating or implying relative importance.

[0184] Finally, it should be noted that the above-described embodiments are merely specific implementations of the present application, and are not intended to limit the technical solutions of the present application. The protection scope of the present application is not limited thereto. Although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can make modifications or easily think of changes to the technical solutions described in the foregoing embodiments, or make equivalent replacements to some of the technical features, within the technical scope disclosed by the present application. Such modifications, changes or replacements do not cause the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application. All should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method of identifying a business object, characterized by, The method comprises the following steps: extracting business nouns from a pre-acquired business modeling database; performing business entity recognition on the extracted business nouns according to a pre-set business entity recognition strategy, clustering the recognized business entities, and constructing a classification hierarchy based on the clustering results; obtaining a transverse association relationship between the business entities, and marking the business entities corresponding to the transverse association relationship in the classification hierarchy based on the obtained transverse association relationship; obtaining a candidate business object based on the marked classification hierarchy; wherein, the last obtained clustering result is extracted in the marked classification hierarchy to obtain a theme, a business entity relationship model is constructed based on the theme and the business entities contained in the theme, a root entity is identified based on the theme, the business entities contained in the theme and the transverse association relationship between the business entities in the business entity relationship model, and a candidate business object is obtained based on the identified root entity and the business entities contained in the root entity; wherein, the root entity is identified based on the theme, the business entities contained in the theme and the transverse association relationship between the business entities in the business entity relationship model, and comprises the following steps: for each theme, the theme is extracted to obtain an initial root entity; for each classification hierarchy in the classification hierarchy corresponding to the theme, the business entities contained in the classification hierarchy are obtained, the business entities with transverse association relationship marks in the classification hierarchy are obtained to obtain new root entities, the business entities between the initial root entity and the new root entities in the classification hierarchy without association relationship marks are obtained to obtain the business entities contained in the initial root entity, and the business entities between the new root entity and the next new root entity in the classification hierarchy without association relationship marks are obtained to obtain the business entities contained in the new root entity; the root entity is obtained based on the initial root entity, the business entities contained in the initial root entity, the new root entity and the business entities contained in the new root entity; verifying and adjusting the candidate business object according to a pre-set business object verification strategy to obtain a business object.

2. The method of claim 1, wherein, The method of obtaining a candidate business object based on the identified root entity and the business entities contained in the root entity comprises the following steps: for each root entity, the root entity and all subordinate business entities contained in the root entity are obtained to obtain a candidate business object, and each root entity corresponds to a candidate business object.

3. The method according to any one of claims 1 to 2, characterized in that, The method of verifying and adjusting the candidate business object according to a pre-set business object verification strategy comprises the following steps: for each candidate business object, it is judged whether the number of business entities contained in the candidate business object is greater than or equal to a pre-set number threshold; if yes, it is checked whether the types of the business entities contained in the candidate business object at least include one root entity and one attribute entity of the root entity; if yes, it is confirmed whether each business entity in the marked classification hierarchy is included in the candidate business object, and whether each business entity only belongs to one candidate business object; if yes, the candidate business object is confirmed as a business object.

4. The method of claim 3, wherein, The method further comprises the following steps: If the number of business entities contained in the candidate business object is less than the number threshold, or the business entity types contained in the candidate business object do not include at least one root entity and one attribute entity of the root entity, or each business entity in the marked classification hierarchy structure does not belong to the candidate business object, or the business entity belongs to two or more candidate business objects, the step of performing business entity recognition on the extracted business nouns according to the pre-set business entity recognition strategy is executed.

5. The method according to any one of claims 1 to 2, characterized in that, The clustering of the recognized business entities and the construction of the classification hierarchy structure based on the clustering results include: The pre-set clustering algorithm is used to perform hierarchical clustering on the recognized business entities. For each clustering result obtained last time, the classification hierarchy structure of the clustering result is obtained based on the clustering result and each hierarchical clustering result corresponding to the clustering result.

6. An apparatus for identifying a business object, the apparatus comprising: It includes: The business noun extraction module is used to extract business nouns from the pre-obtained business modeling database. The hierarchy structure construction module is used to perform business entity recognition on the extracted business nouns according to the pre-set business entity recognition strategy, cluster the recognized business entities, and construct a classification hierarchy structure based on the clustering results. The association relationship marking module is used to obtain the horizontal association relationship between business entities, and mark the business entities corresponding to the horizontal association relationship in the classification hierarchy structure based on the obtained horizontal association relationship. The preliminary screening module is used to obtain candidate business objects based on the marked classification hierarchy structure. In the marked classification hierarchy structure, the last obtained clustering result is extracted to obtain a theme, and a business entity relationship model is constructed based on the theme and the business entities contained in the theme. The root entity is identified based on the theme, the business entities contained in the theme, and the horizontal association relationship between the business entities in the business entity relationship model. The candidate business objects are obtained based on the identified root entity and the business entities contained in the root entity. Based on the theme, the business entities contained in the theme, and the horizontal association relationship between the business entities in the business entity relationship model, the root entity is identified, which includes: for each theme, the theme is extracted to obtain an initial root entity; for each classification level in the classification hierarchy structure corresponding to the theme, the business entities contained in the classification level are obtained, the business entities with horizontal association relationship marking in the classification level are obtained to obtain new root entities, the business entities without association relationship marking between the initial root entity and the new root entity in the classification level are obtained to obtain the business entities contained in the initial root entity, and the business entities without association relationship marking between the new root entity and the next new root entity in the classification level are obtained to obtain the business entities contained in the new root entity; the root entity is obtained based on the initial root entity, the business entities contained in the initial root entity, the new root entity, and the business entities contained in the new root entity. The business object acquisition module is used to verify and adjust the candidate business objects according to the pre-set business object verification strategy to obtain business objects.

7. A computer device, comprising: It includes: A processor, a memory storing machine readable instructions executable by the processor, and a bus for communication between the processor and the memory when the computer device is running, the machine readable instructions, when executed by the processor, performing the steps of the method of claim 1 to 5.

8. A computer-readable storage medium, characterized in that, A computer readable storage medium storing a computer program, the computer program, when executed by a processor, performing the steps of the method of claim 1 to 5.

Images