Business domain model management method and device, computer equipment and storage medium

Abstract

The invention belongs to the field of data analysis, and relates to a business domain model management method and related equipment. According to the application, the acquired service data set is divided into a plurality of service sub-domains according to the acquired service rule, and aggregation is carried out to obtain the aggregation relationship, so that the association relationship between different service entities can be clearly sorted out, and generation of a subsequent service process can be conveniently determined; secondly, modeling the service data set according to the plurality of service sub-domains and the aggregation relationship to obtain a plurality of service domain models, so that the service domain models with high accuracy can be generated; and finally, receiving a service change request sent by a client, changing the service domain model corresponding to the service change request when the service change request is reasonable to obtain a target service domain model, and refusing the change of the service domain model corresponding to the service change request when the service change request is unreasonable to obtain the target service domain model. The condition that the business domain model is randomly and unreasonably changed can be avoided, and effective management of the business domain model is realized.

Description

Technical Field

[0001] The present application relates to the field of data analysis technology, and in particular to a management method, apparatus, computer equipment and storage medium for a business domain model. Background Art

[0002] Business domain modeling is the process of summarizing and analyzing the needs of various business problems in reality. It is a visual display of business entities and a communication tool that converts the needs of business personnel into technical-oriented object design to establish a unified language that can be understood by both developers and businesses. With the development of microservices in the software development industry, domain modeling technology is also widely used in several business scenarios. For example, in the financial field, by combing the business logic of insurance product business, policy business, preservation business and underwriting business, an insurance domain model including insurance policy, preservation and underwriting business can be obtained.

[0003] Traditional business domain modeling is to obtain a corresponding business domain model by associating at least two entity models of business data.

[0004] However, the business domain model generated by this method still has the problem of unclear business processes. As the business domain is constantly iteratively modified, the business domain model needs to be updated and upgraded. During the update and upgrade process, the business domain model is arbitrarily and irrationally changed, which damages the business domain model and makes it unusable, making it difficult to effectively manage the business domain model. Summary of the invention

[0005] The purpose of the embodiments of the present application is to propose a management method, apparatus, computer equipment and storage medium for a business domain model, the main purpose of which is to improve the accuracy of business domain model generation and to achieve effective management of business domain models.

[0006] In order to solve the above technical problems, the present application embodiment provides a management method for a business domain model, which adopts the following technical solution:

[0007] Acquire a business data set to be modeled and business rules in the business data set, and divide the business data set into a plurality of business subdomains according to the business rules;

[0008] Extracting a business entity set and a business value object from the business data set;

[0009] Aggregating the business entity set and the business value object to obtain an aggregation relationship;

[0010] Modeling the business data set according to the several business subdomains and the aggregation relationship to obtain several business domain models;

[0011] Receive a service change request from a client and determine whether the service change request is reasonable;

[0012] If the business change request is reasonable, modify the business domain model corresponding to the business change request to obtain a target business domain model;

[0013] If the business change request is unreasonable, the change of the business domain model corresponding to the business change request is rejected.

[0014] Furthermore, the step of dividing the business data set into a plurality of business subdomains according to the business rules specifically includes the following steps:

[0015] Obtain several domain objects corresponding to the business rules;

[0016] Dividing the business data set into a plurality of bounded contexts according to the plurality of domain objects;

[0017] Identifying domain priorities corresponding to the plurality of domain objects;

[0018] According to the domain priorities, the plurality of bounded contexts are divided into the plurality of business subdomains including a core domain, a general domain and a supporting domain.

[0019] Furthermore, the step of aggregating the business entity set and the business value object to obtain an aggregation relationship specifically includes the following steps:

[0020] Obtain the root entity and common entity of the business entity set;

[0021] Identify a first dependency relationship between the root entity and the common entity and a second dependency relationship between the common entity and the business value object;

[0022] The root entity, the common entity and the business value object are aggregated according to the first dependency relationship and the second dependency relationship to obtain the aggregation relationship.

[0023] Furthermore, the step of determining whether the service change request is reasonable specifically includes the following steps:

[0024] Obtaining the business domain model corresponding to the business change request, and extracting the business logic corresponding to the business domain model;

[0025] Identify whether the business change request complies with the business logic;

[0026] If the business change request is reasonable, then the business domain model corresponding to the business change request is changed to obtain the target business domain model, and the step specifically includes:

[0027] When the business change request conforms to the business logic, the business change request is determined to be reasonable, and the business domain model corresponding to the business change request is changed to obtain a target business domain model;

[0028] If the business change request is unreasonable, the step of rejecting the change of the business domain model corresponding to the business change request specifically includes:

[0029] When the business change request does not conform to the business logic, it is determined that the business change request is unreasonable, and the change of the business domain model corresponding to the business change request is rejected.

[0030] Furthermore, the step of modifying the business domain model corresponding to the business change request to obtain the target business domain model specifically includes the following steps:

[0031] Obtaining the business field to be changed and the request type carried in the business change request;

[0032] The business field to be changed is changed in the business domain model according to the request type to obtain the target business domain model.

[0033] Furthermore, the step of modeling the business data set according to the several business subdomains and the aggregation relationship to obtain several business domain models specifically includes the following steps:

[0034] Acquire a plurality of domain objects in the business data set, and identify the business processes corresponding to the domain objects according to the plurality of business subdomains and the aggregation relationship;

[0035] Performing conceptual annotation on the plurality of domain objects to obtain domain annotation data;

[0036] The annotation data is visually mapped according to the business process to obtain a plurality of business domain models corresponding to the plurality of domain objects.

[0037] Furthermore, after the step of modeling the business data set according to the several business subdomains and the aggregation relationship to obtain several business domain models, the following steps are also included:

[0038] Obtain model fields corresponding to the several business models;

[0039] Performing application extension annotation on the model field to obtain an application field;

[0040] The target business process corresponding to the application field is obtained, and the application field is added to the target business process to obtain a final business domain model.

[0041] In order to solve the above technical problems, the embodiment of the present application also provides a management device for a business domain model, which adopts the following technical solution:

[0042] A partitioning module, used to obtain a business data set to be modeled and business rules in the business data set, and to partition the business data set into a plurality of business subdomains according to the business rules;

[0043] An extraction module, used to extract a business entity set and a business value object from the business data set;

[0044] An aggregation module, used for aggregating the business entity set and the business value object to obtain an aggregation relationship;

[0045] A modeling module, used to model the business data set according to the several business subdomains and the aggregation relationship to obtain several business domain models;

[0046] A judgment module, used to receive a service change request from a client and judge whether the service change request is reasonable;

[0047] A change execution module, used for changing the business domain model corresponding to the business change request to obtain a target business domain model if the business change request is reasonable;

[0048] The change rejection module is used to reject the change of the business domain model corresponding to the business change request if the business change request is unreasonable.

[0049] In order to solve the above technical problems, the embodiment of the present application further provides a computer device, which adopts the following technical solution:

[0050] The system comprises a memory and a processor, wherein the memory stores computer-readable instructions, and the processor implements the steps of the business domain model management method as described above when executing the computer-readable instructions.

[0051] In order to solve the above technical problems, the embodiment of the present application further provides a computer-readable storage medium, which adopts the following technical solution:

[0052] The computer-readable storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the steps of the business domain model management method described above are implemented.

[0053] The present application provides a management method for a business domain model, comprising: obtaining a business data set to be modeled and business rules in the business data set, and dividing the business data set into a plurality of business subdomains according to the business rules; extracting a business entity set and a business value object in the business data set; aggregating the business entity set and the business value object to obtain an aggregation relationship; modeling the business data set according to the plurality of business subdomains and the aggregation relationship to obtain a plurality of business domain models; receiving a business change request issued by a client, and determining whether the business change request is reasonable; if the business change request is reasonable, changing the business domain model corresponding to the business change request to obtain a target business domain model; if the business change request is unreasonable, rejecting the change of the business domain model corresponding to the business change request. Compared with the prior art, the present application first divides the acquired business data set into several business subdomains according to the acquired business rules, can determine the business domains to which different businesses belong, and aggregates the business entity set and the business value object to obtain the aggregation relationship, can clearly sort out the association relationship between different business entities, and is convenient for determining the generation of subsequent business processes; secondly, the business data set is modeled according to several business subdomains and the aggregation relationship to obtain several business domain models, which can generate a business domain model with high accuracy; finally, by receiving the business change request issued by the client and judging whether the business change request is reasonable, if it is reasonable, the business domain model corresponding to the business change request is changed to obtain the target business domain model, and if it is unreasonable, the change of the business domain model corresponding to the business change request is rejected, which can avoid the situation of making unreasonable changes to the business domain model at will, and realize the effective management of the business domain model. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] In order to more clearly illustrate the scheme in the present application, a brief introduction is given below to the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0055] Figure 1 is an exemplary system architecture diagram to which the present application may be applied;

[0056] Figure 2 It is a flowchart for implementing the management method of the business domain model provided in Example 1 of the present application;

[0057] Figure 3 It is a structural diagram of a management device for a business domain model provided in Example 2 of the present application;

[0058] Figure 4It is a structural diagram of an embodiment of a computer device according to the present application. DETAILED DESCRIPTION

[0059] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by technicians in the technical field of the present application; the terms used in the specification of the application herein are only for the purpose of describing specific embodiments and are not intended to limit the present application; the terms "including" and "having" and any variations thereof in the specification and claims of the present application and the above-mentioned drawings are intended to cover non-exclusive inclusions. The terms "first", "second", etc. in the specification and claims of the present application or the above-mentioned drawings are used to distinguish different objects, not to describe a specific order.

[0060] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0061] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings.

[0062] like Figure 1 As shown, the system architecture 100 may include a terminal device 101, a network 102 and a server 103. The terminal device 101 may be a laptop 1011, a tablet computer 1012 or a mobile phone 1013. The network 102 is used to provide a medium for a communication link between the terminal device 101 and the server 103. The network 102 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0063] The user can use the terminal device 101 to interact with the server 103 through the network 102 to receive or send messages, etc. Various communication client applications can be installed on the terminal device 101, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0064] The terminal device 101 can be various electronic devices with a display screen and supporting web browsing. In addition to the laptop computer 1011, the tablet computer 1012 or the mobile phone 1013, the terminal device 101 can also be an e-book reader, an MP3 player (Moving Picture Experts Group Audio Layer III), an MP4 (Moving Picture Experts Group Audio Layer IV) player, a laptop computer, a desktop computer, etc.

[0065] The server 103 may be a server that provides various services, such as a background server that provides support for a web page displayed on the terminal device 101 .

[0066] It should be noted that the management method of the business domain model provided in the embodiment of the present application is generally executed by a server / terminal device, and accordingly, the management device of the business domain model is generally set in the server / terminal device.

[0067] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to the implementation requirements.

[0068] Embodiment 1

[0069] Continue to refer Figure 2 , shows a flow chart of an embodiment of a method for managing a business domain model according to the present application. The method for managing a business domain model comprises: step S201, step S202, step S203, step S204, step S205, step S206 and step S207.

[0070] In step S201, a business data set to be modeled and business rules in the business data set are obtained, and the business data set is divided into a plurality of business subdomains according to the business rules.

[0071] In an embodiment of the present application, obtaining the business data set to be modeled can be to first determine the source of the business data set, including the enterprise's internal database, files, API interfaces, or external data providers, public data sets, etc.; then, based on the determined data source, data collection work is performed according to various technical means such as ETL (Extract, Transform, Load) tools, API calls, file reading, etc.; finally, after collecting the data, a preliminary quality assessment is performed to check the data's completeness, accuracy, consistency, and whether there are missing values, outliers, and other problems.

[0072] In the embodiment of the present application, the business data set is divided into several business subdomains according to the business rules, which can be:

[0073] (1) Identify key business elements: Based on business rules, identify the key elements or dimensions that affect business objectives. These elements or dimensions will serve as the basis for dividing business subdomains;

[0074] (2) Define business subdomains: Divide the business data set into several business subdomains based on key business elements. Each subdomain should focus on a specific business scenario or problem and contain the relevant data required to solve the scenario or problem;

[0075] (3) Data allocation and integration: The data in the original data set is allocated and integrated according to the defined subdomains. This may require data screening, conversion, aggregation and other operations to ensure that the data in each subdomain is accurate, complete and complies with business rules;

[0076] (4) Subdomain assessment: Conduct an independent assessment of each business subdomain to check the integrity, consistency, and relevance of the data to ensure that the subdomain division is reasonable and effective.

[0077] In some optional implementations of the embodiments of the present application, after the business data set is divided, more in-depth data analysis, feature engineering, model building and evaluation can be performed for each business subdomain. Since each subdomain focuses on a specific business scenario or problem, the model can be designed and optimized more accurately to improve the performance and interpretability of the model.

[0078] In step S202, a business entity set and a business value object in the business data set are extracted.

[0079] In the embodiment of the present application, the business entity set extracted from the business data set may be:

[0080] (1) Identify unique identifiers: First, it is necessary to identify which business objects have unique identifiers. These objects are often key participants or resources in the business process.

[0081] (2) Analyze business logic: Next, analyze the business logic of these objects, including their state changes, interactions with other objects, etc.

[0082] (3) Define entity classes: Based on the above analysis, define the corresponding entity classes and implement the properties and methods related to the business logic in the classes.

[0083] In the embodiment of the present application, the business value object extracted from the business data set may be:

[0084] (1) Identify attribute sets: First, identify which attribute sets are meaningful in business terms and do not depend on specific contexts or instances;

[0085] (2) Evaluate uniqueness requirements: Then, evaluate whether these attribute sets need to be unique. If not, they are likely value objects;

[0086] (3) Define the value object class: Finally, define the corresponding value object class and implement these properties in the class. The value object class usually does not contain behaviors (ie methods) unless these behaviors are related to the creation, comparison, or serialization of the value object.

[0087] In step S203, the business entity set and the business value object are aggregated to obtain an aggregation relationship.

[0088] In step S204, the business data set is modeled according to a plurality of business subdomains and aggregation relationships to obtain a plurality of business domain models.

[0089] In step S205, a service change request sent by the client is received, and it is determined whether the service change request is reasonable.

[0090] In step S206, if the business change request is reasonable, the business domain model corresponding to the business change request is changed to obtain a target business domain model.

[0091] In step S207, if the business change request is unreasonable, the change of the business domain model corresponding to the business change request is rejected.

[0092] In an embodiment of the present application, a management method for a business domain model is provided, including: obtaining a business data set to be modeled and business rules in the business data set, and dividing the business data set into a number of business subdomains according to the business rules; extracting a business entity set and a business value object in the business data set; aggregating the business entity set and the business value object to obtain an aggregation relationship; modeling the business data set according to the number of business subdomains and the aggregation relationship to obtain a number of business domain models; receiving a business change request issued by a client, and determining whether the business change request is reasonable; if the business change request is reasonable, changing the business domain model corresponding to the business change request to obtain a target business domain model; if the business change request is unreasonable, rejecting the change of the business domain model corresponding to the business change request. Compared with the prior art, the present application first divides the acquired business data set into several business subdomains according to the acquired business rules, can determine the business domains to which different businesses belong, and aggregates the business entity set and the business value object to obtain the aggregation relationship, can clearly sort out the association relationship between different business entities, and is convenient for determining the generation of subsequent business processes; secondly, the business data set is modeled according to several business subdomains and the aggregation relationship to obtain several business domain models, which can generate a business domain model with high accuracy; finally, by receiving the business change request issued by the client and judging whether the business change request is reasonable, if it is reasonable, the business domain model corresponding to the business change request is changed to obtain the target business domain model, and if it is unreasonable, the change of the business domain model corresponding to the business change request is rejected, which can avoid the situation of making unreasonable changes to the business domain model at will, and realize the effective management of the business domain model.

[0093] In some optional implementations of the embodiments of the present application, the above step S201 specifically includes the following steps:

[0094] Get several domain objects corresponding to business rules;

[0095] Divide the business data set into several bounded contexts based on several domain objects;

[0096] Identify domain priorities corresponding to several domain objects;

[0097] According to domain priorities, several bounded contexts are divided into several business subdomains including core domains, general domains and supporting domains.

[0098] In the embodiment of the present application, a domain object is a software representation of a concept or thing in a business domain.

[0099] In an embodiment of the present application, the business data set is divided into several bounded contexts according to several domain objects. The relationship between the domain objects can be analyzed first, and the dependency, aggregation, association and other relationships between the domain objects can be identified; then the context boundary is determined: based on the relationship between the objects, the boundaries of each bounded context are determined. These boundaries should be able to clearly divide different business domains or subdomains, while ensuring the consistency and integrity of the business logic and rules within the context; finally, the bounded context is defined, each bounded context is named, and the domain objects, business rules and business logic contained therein are clearly defined.

[0100] In an embodiment of the present application, to identify the domain priorities corresponding to several domain objects, the contribution of each domain object to the business objectives can be analyzed first to evaluate its business value; then the technical complexity and resource investment required to implement or modify the domain object can be considered; finally, based on the business value and technical complexity, the priority of each domain object can be determined.

[0101] In an embodiment of the present application, the bounded context may be divided into different business subdomains, including a core domain, a general domain, and a support domain, wherein:

[0102] Core domain: Contains domain objects and rules that are critical to business success. These subdomains should receive the highest priority and resources.

[0103] Common domain: contains domain objects and rules shared across several business subdomains. These subdomains may not be critical to business success, but their commonality and reusability make them important.

[0104] Support domain: Contains the infrastructure, tools, and technologies that support the operation of the core domain and the common domain. Although these subdomains do not directly contribute to business value, they are indispensable for business operations.

[0105] In some optional implementations of the embodiments of the present application, the above step S203 specifically includes the following steps:

[0106] Get the root entity and common entity of the business entity set;

[0107] Identify a first dependency relationship between a root entity and a common entity and a second dependency relationship between the common entity and a business value object;

[0108] The root entity, the common entity and the business value object are aggregated according to the first dependency relationship and the second dependency relationship to obtain an aggregation relationship.

[0109] In the embodiments of the present application, there are dependencies between entities and between entities and value objects within the aggregate. These dependencies are crucial to understanding the structure and behavior of the aggregate, including:

[0110] First dependency: This refers to the dependency between the root entity and the common entity. Usually, the common entity depends on the root entity to maintain its existence and consistency. In other words, the common entity is usually created, updated or deleted through the root entity;

[0111] Second dependency: This refers to the dependency between ordinary entities and business value objects. Value objects are usually used to describe a certain aspect or attribute set of an entity. They may be shared by several entities, but they do not contain any business logic or behavior.

[0112] In the embodiments of the present application, by identifying these dependencies, you can better understand the internal structure and interaction mode of the aggregate.

[0113] In the embodiment of this application, after identifying the root entity, common entity, value object and the dependencies between them, you can organize these elements into an aggregate. An aggregate is a highly cohesive and low-coupling unit that encapsulates domain knowledge by defining boundaries to ensure data consistency and integrity, where:

[0114] Constructing an aggregate: With the root entity as the center, organize the common entities and value objects that have dependencies with it to form an aggregate. The boundaries of the aggregate should clearly define which elements belong to the aggregate and which elements do not;

[0115] Maintaining aggregate consistency: The internal consistency of the aggregate should be maintained by the root entity. External objects should access the aggregate through the root entity, and the root entity should be responsible for ensuring that any operations performed within the aggregate do not destroy its consistency.

[0116] In the embodiment of the present application, aggregation can be constructed according to entities and value objects in the business domain and the dependencies between them, so as to obtain a domain model with a clear structure, which is easy to understand and maintain.

[0117] In some optional implementations of the embodiments of the present application, the above step S205 specifically includes the following steps:

[0118] Obtain the business domain model corresponding to the business change request, and extract the business logic corresponding to the business domain model;

[0119] Identify whether the business change request complies with business logic;

[0120] The above step S206 specifically includes the following steps:

[0121] When the business change request conforms to the business logic, the business change request is determined to be reasonable, and the business domain model corresponding to the business change request is changed to obtain the target business domain model;

[0122] The above step S207 specifically includes the following steps:

[0123] When a business change request does not conform to the business logic, the business change request is determined to be unreasonable, and the change of the business domain model corresponding to the business change request is rejected.

[0124] In some optional implementations of the embodiments of the present application, the above step S206 specifically includes the following steps:

[0125] Get the business fields to be changed and the request type carried in the business change request;

[0126] According to the request type, the business fields to be changed are modified in the business domain model to obtain the target business domain model.

[0127] In the embodiment of the present application, for a data update request, it is necessary to locate the corresponding entity or value object in the business domain model and modify its attributes. This involves database query, data validation and update operations. During the update process, it is necessary to ensure the integrity and consistency of the data and consider whether the relevant cache or index needs to be updated.

[0128] In the embodiment of the present application, by obtaining the business fields to be changed and the request type in the business change request, and making corresponding changes in the business domain model according to the request type, it is possible to ensure that the system can accurately respond to changes in business requirements. This process requires close cooperation with the business department to ensure accurate understanding and effective implementation of the changes. At the same time, it is also necessary to pay attention to the impact of the changes on system performance, security and stability, and take appropriate measures to reduce risks.

[0129] In some optional implementations of the embodiments of the present application, the above step S204 specifically includes the following steps:

[0130] Obtain several domain objects in the business data set, and identify the business processes corresponding to the domain objects based on several business subdomains and aggregation relationships;

[0131] Conduct conceptual annotations on several domain objects to obtain domain annotation data;

[0132] The annotation data is visualized and mapped according to the business process to obtain several business domain models corresponding to several domain objects.

[0133] In the embodiments of the present application, by acquiring domain objects in the business data set, identifying business processes, performing concept annotations and visual mapping, a clear and accurate business domain model can be constructed, laying a solid foundation for the success of software development.

[0134] In some optional implementations of the embodiments of the present application, after the step of modeling the business data set according to the business subdomains and the aggregation relationship to obtain the business domain models, the following steps are also included:

[0135] Get the model fields corresponding to several business models;

[0136] Apply extension annotation to the model fields to obtain application fields;

[0137] Get the target business process corresponding to the application field, and add the application field to the target business process to obtain the final business domain model.

[0138] In an embodiment of the present application, by applying extension annotations to model fields, additional functions or constraints can be added to the fields without changing the original business model structure. This non-invasive extension method makes the model more flexible and easy to adapt to changes in future business needs.

[0139] In an embodiment of the present application, accurately mapping application fields to target business processes can ensure that the business processes can accurately use these fields when processing data, which helps reduce data errors and redundant processing and improve the accuracy and efficiency of business processes.

[0140] In the embodiments of the present application, by analyzing the business model and business process, the enterprise can better understand the key links and potential risks in its business operation process. This helps the enterprise optimize resource allocation, invest more resources in key links, and formulate corresponding risk management strategies to reduce potential risks.

[0141] The embodiments of the present application can acquire and process relevant data based on artificial intelligence technology. Artificial Intelligence (AI) is the theory, method, technology and application system that uses digital computers or machines controlled by digital computers to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results.

[0142] AI basic technologies generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing technology, operation / interaction systems, mechatronics, etc. AI software technologies mainly include computer vision technology, robotics technology, biometrics technology, speech processing technology, natural language processing technology, and machine learning / deep learning.

[0143] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through computer-readable instructions, and the computer-readable instructions can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the aforementioned storage medium can be a non-volatile storage medium such as a disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

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

[0145] Embodiment 2

[0146] Further references Figure 3 , as a response to the above Figure 2 The present application provides an embodiment of a management device for a business domain model. Figure 2 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0147] like Figure 3 As shown, the management device 200 of the business domain model of the embodiment of the present application includes:

[0148] A partitioning module 210 is used to obtain a business data set to be modeled and business rules in the business data set, and to partition the business data set into a plurality of business subdomains according to the business rules;

[0149] An extraction module 220 is used to extract a business entity set and a business value object from a business data set;

[0150] Aggregation module 230, used to aggregate business entity sets and business value objects to obtain aggregation relationships;

[0151] A modeling module 240 is used to model a business data set according to a plurality of business subdomains and aggregation relationships to obtain a plurality of business domain models;

[0152] The judging module 250 is used to receive a service change request from a client and judge whether the service change request is reasonable;

[0153] A change execution module 260 is used to change the business domain model corresponding to the business change request to obtain a target business domain model if the business change request is reasonable;

[0154] The change rejection module 270 is used to reject the change of the business domain model corresponding to the business change request if the business change request is unreasonable.

[0155] In an embodiment of the present application, a management device 200 for a business domain model is provided, including: a division module 210, used to obtain a business data set to be modeled and business rules in the business data set, and divide the business data set into a number of business subdomains according to the business rules; an extraction module 220, used to extract a business entity set and a business value object in the business data set; an aggregation module 230, used to aggregate the business entity set and the business value object to obtain an aggregation relationship; a modeling module 240, used to model the business data set according to a number of business subdomains and the aggregation relationship to obtain a number of business domain models; a judgment module 250, used to receive a business change request issued by a client, and judge whether the business change request is reasonable; a change execution module 260, used to change the business domain model corresponding to the business change request if the business change request is reasonable, to obtain a target business domain model; a change rejection module 270, used to reject the change of the business domain model corresponding to the business change request if the business change request is unreasonable. Compared with the prior art, the present application first divides the acquired business data set into several business subdomains according to the acquired business rules, can determine the business domains to which different businesses belong, and aggregates the business entity set and the business value object to obtain the aggregation relationship, can clearly sort out the association relationship between different business entities, and is convenient for determining the generation of subsequent business processes; secondly, the business data set is modeled according to several business subdomains and the aggregation relationship to obtain several business domain models, which can generate a business domain model with high accuracy; finally, by receiving the business change request issued by the client and judging whether the business change request is reasonable, if it is reasonable, the business domain model corresponding to the business change request is changed to obtain the target business domain model, and if it is unreasonable, the change of the business domain model corresponding to the business change request is rejected, which can avoid the situation of making unreasonable changes to the business domain model at will, and realize the effective management of the business domain model.

[0156] To solve the above technical problems, the present application also provides a computer device. Figure 4 , Figure 4 This is a basic structural block diagram of a computer device according to an embodiment of the present application.

[0157] The computer device 300 includes a memory 310, a processor 320, and a network interface 330 that are interconnected and communicated through a system bus. It should be noted that the figure only shows a computer device 300 having components 310-330, but it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital processors (DSPs), embedded devices, etc.

[0158] The computer device may be a computing device such as a desktop computer, a notebook, a PDA, a cloud server, etc. The computer device may interact with a user through a keyboard, a mouse, a remote controller, a touch pad, or a voice control device.

[0159] The memory 310 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 310 can be an internal storage unit of the computer device 300, such as a hard disk or memory of the computer device 300. In other embodiments, the memory 310 can also be an external storage device of the computer device 300, such as a plug-in hard disk equipped on the computer device 300, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card, etc. Of course, the memory 310 can also include both the internal storage unit of the computer device 300 and its external storage device. In the embodiment of the present application, the memory 310 is generally used to store the operating system and various application software installed on the computer device 300, such as computer-readable instructions of the management method of the business domain model. In addition, the memory 310 can also be used to temporarily store various data that have been output or are to be output.

[0160] The processor 320 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip in some embodiments. The processor 320 is generally used to control the overall operation of the computer device 300. In the embodiment of the present application, the processor 320 is used to run the computer-readable instructions stored in the memory 310 or process data, such as computer-readable instructions for running the management method of the business domain model.

[0161] The network interface 330 may include a wireless network interface or a wired network interface. The network interface 330 is generally used to establish a communication connection between the computer device 300 and other electronic devices.

[0162] The computer device provided by the present application first divides the acquired business data set into several business subdomains according to the acquired business rules, can determine the business fields to which different businesses belong, and aggregates the business entity set and the business value object to obtain the aggregation relationship, can clearly sort out the association relationship between different business entities, and is convenient for determining the generation of subsequent business processes; secondly, the business data set is modeled according to several business subdomains and the aggregation relationship to obtain several business domain models, and a business domain model with high accuracy can be generated; finally, by receiving the business change request issued by the client and judging whether the business change request is reasonable, if it is reasonable, the business domain model corresponding to the business change request is changed to obtain the target business domain model, and if it is unreasonable, the change of the business domain model corresponding to the business change request is rejected, which can avoid the situation of making unreasonable changes to the business domain model at will, and realize the effective management of the business domain model.

[0163] The present application also provides another implementation, namely, providing a computer-readable storage medium, wherein the computer-readable storage medium stores computer-readable instructions, and the computer-readable instructions can be executed by at least one processor to enable the at least one processor to perform the steps of the business domain model management method as described above.

[0164] The computer-readable storage medium provided by the present application first divides the acquired business data set into several business subdomains according to the acquired business rules, can determine the business domains to which different businesses belong, and aggregates the business entity set and the business value object to obtain the aggregation relationship, can clearly sort out the association relationship between different business entities, and is convenient for determining the generation of subsequent business processes; secondly, the business data set is modeled according to several business subdomains and the aggregation relationship to obtain several business domain models, and a business domain model with high accuracy can be generated; finally, by receiving a business change request issued by a client and judging whether the business change request is reasonable, if it is reasonable, the business domain model corresponding to the business change request is changed to obtain the target business domain model, and if it is unreasonable, the change of the business domain model corresponding to the business change request is rejected, which can avoid the situation where unreasonable changes are made to the business domain model at will, and realize the effective management of the business domain model.

[0165] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0166] Obviously, the embodiments described above are only some embodiments of the present application, rather than all embodiments. The preferred embodiments of the present application are given in the accompanying drawings, but they do not limit the patent scope of the present application. The present application can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of the present application more thorough and comprehensive. Although the present application is described in detail with reference to the aforementioned embodiments, for those skilled in the art, it is still possible to modify the technical solutions recorded in the aforementioned specific implementation methods, or to perform equivalent replacement of some of the technical features therein. Any equivalent structure made using the contents of the specification and drawings of this application, directly or indirectly used in other related technical fields, is similarly within the scope of patent protection of this application.

Claims

1. A method for managing a business domain model, characterized in that: The steps include: Acquire a business data set to be modeled and business rules in the business data set, and divide the business data set into a plurality of business subdomains according to the business rules; Extracting a business entity set and a business value object from the business data set; Aggregating the business entity set and the business value object to obtain an aggregation relationship; Modeling the business data set according to the several business subdomains and the aggregation relationship to obtain several business domain models; Receive a service change request from a client and determine whether the service change request is reasonable; If the business change request is reasonable, modify the business domain model corresponding to the business change request to obtain a target business domain model; If the business change request is unreasonable, the change of the business domain model corresponding to the business change request is rejected.

2. The method for managing a business domain model according to claim 1, characterized in that: The step of dividing the business data set into a plurality of business subdomains according to the business rules specifically includes the following steps: Obtain several domain objects corresponding to the business rules; Dividing the business data set into a plurality of bounded contexts according to the plurality of domain objects; Identifying domain priorities corresponding to the plurality of domain objects; According to the domain priorities, the plurality of bounded contexts are divided into the plurality of business subdomains including a core domain, a general domain and a supporting domain.

3. The method for managing a business domain model according to claim 1, characterized in that: The step of aggregating the business entity set and the business value object to obtain an aggregation relationship specifically includes the following steps: Obtain the root entity and common entity of the business entity set; Identify a first dependency relationship between the root entity and the common entity and a second dependency relationship between the common entity and the business value object; The root entity, the common entity and the business value object are aggregated according to the first dependency relationship and the second dependency relationship to obtain the aggregation relationship.

4. The method for managing a business domain model according to claim 1, characterized in that: The step of determining whether the service change request is reasonable specifically includes the following steps: Obtaining the business domain model corresponding to the business change request, and extracting the business logic corresponding to the business domain model; Identify whether the business change request complies with the business logic; If the business change request is reasonable, then the business domain model corresponding to the business change request is changed to obtain the target business domain model, and the step specifically includes: When the business change request conforms to the business logic, the business change request is determined to be reasonable, and the business domain model corresponding to the business change request is changed to obtain a target business domain model; If the business change request is unreasonable, the step of rejecting the change of the business domain model corresponding to the business change request specifically includes: When the business change request does not conform to the business logic, it is determined that the business change request is unreasonable, and the change of the business domain model corresponding to the business change request is rejected.

5. The method for managing a business domain model according to any one of claims 1 to 4, characterized in that: The step of changing the business domain model corresponding to the business change request to obtain the target business domain model specifically includes the following steps: Obtaining the business field to be changed and the request type carried in the business change request; The business field to be changed is changed in the business domain model according to the request type to obtain the target business domain model.

6. The method for managing a business domain model according to claim 1, characterized in that: The step of modeling the business data set according to the several business subdomains and the aggregation relationship to obtain several business domain models specifically includes the following steps: Acquire a plurality of domain objects in the business data set, and identify the business processes corresponding to the domain objects according to the plurality of business subdomains and the aggregation relationship; Performing conceptual annotation on the plurality of domain objects to obtain domain annotation data; The annotation data is visually mapped according to the business process to obtain a plurality of business domain models corresponding to the plurality of domain objects.

7. The method for managing a business domain model according to claim 6, characterized in that: After the step of modeling the business data set according to the several business subdomains and the aggregation relationship to obtain several business domain models, the following steps are also included: Obtain model fields corresponding to the several business domain models; Performing application extension annotation on the model field to obtain an application field; The target business process corresponding to the application field is obtained, and the application field is added to the target business process to obtain a final business domain model.

8. A management device for a business domain model, characterized in that: include: A partitioning module, used to obtain a business data set to be modeled and business rules in the business data set, and to partition the business data set into a plurality of business subdomains according to the business rules; An extraction module, used to extract a business entity set and a business value object from the business data set; An aggregation module, used for aggregating the business entity set and the business value object to obtain an aggregation relationship; A modeling module, used to model the business data set according to the several business subdomains and the aggregation relationship to obtain several business domain models; A judgment module, used to receive a service change request from a client and judge whether the service change request is reasonable; A change execution module, used for changing the business domain model corresponding to the business change request to obtain a target business domain model if the business change request is reasonable; The change rejection module is used to reject the change of the business domain model corresponding to the business change request if the business change request is unreasonable.

9. A computer device comprising a memory and a processor, characterized in that: The memory stores computer-readable instructions, and when the processor executes the computer-readable instructions, the steps of the method for managing a business domain model according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by a processor, the steps of the method for managing a business domain model according to any one of claims 1 to 7 are implemented.

Images