Method for automatically identifying and defining domain service and internal component according to business entity

Abstract

The invention relates to a method for automatically identifying and defining domain services and internal components according to business entities. The method comprises the following steps of: in an operation step, defining a BOC of a BCC type according to a service entity which an operation aims at; defining an association relationship needing to be queried by multiple service entities together in the operation step as a BOC of a BQC type; identifying the step of executing the business rule or the partial identification class in the operation step as a BOC of a PBB type; the method comprises the following steps: defining BOCs of one or more PBS types under a service function; for the BOC of the PBS type, the code is implemented as a domain service; for BOCs of the BCC, BQC, PBB type, the code is implemented as an internal component within the domain service. According to the method, the domain service needing to be realized is quickly identified and defined in a visual, simple and operable mode, the defect caused by the fact that domain service definition needs to be carried out by means of experience of designers in the past is overcome, the method can be checked and automatically executed, the working efficiency is improved, and the task completion quality is guaranteed.

Description

Technical Field

[0001] The present invention relates to the technical field of domain service identification and definition methods, and in particular to a method for automatically identifying and defining domain services and internal components according to business entities. Background Art

[0002] The bank's enterprise-level architecture includes two major parts: business architecture and IT architecture (IT architecture can be divided into application architecture, data architecture, technical architecture and security architecture).

[0003] Business architecture generally includes narrow business architecture and business model:

[0004] (1) Business architecture (in a narrow sense) includes: business domain, business components, and business objects.

[0005] (2) Business models include: process model, product model, and entity model.

[0006] How is the relationship between business architecture (narrow sense), business model, IT architecture, and IT design Figure 1 shown.

[0007] To carry out IT design based on the business model and to fully undertake the business model, an end-to-end IT implementation process is needed to ensure it.

[0008] Implementation technology refers to a set of processes, methods, templates, and guidelines for structured design based on the enterprise architecture model to obtain project implementation delivery results based on business modeling results.

[0009] The complete implementation process covers the entire life cycle of software engineering, from requirements, analysis, design, development, testing, deployment to switching, forming an iterative project implementation process. The overall process of the implementation process is as follows: Figure 2 shown.

[0010] The implementation process uses a structured software engineering method to guide the transformation of business modeling results into system delivery results, thereby ensuring that the IT system fully and correctly undertakes the business modeling results and is implemented as microservice components.

[0011] As business modeling becomes the main trend in the transformation of the bank's enterprise-level architecture, the implementation process based on the results of business modeling has also become the focus of various banks in application research and development. A complete, reasonable and efficient implementation process is an important means to ensure the quality and quantity of project delivery. At present, the research and development focus of the implementation process includes:

[0012] (1) Improve quality: During the implementation process, the entry, exit, and quality standards of each process step are strictly defined to ensure the lower limit of quality of the developed application;

[0013] (2) Improve efficiency: With the support of supporting tools and under the premise of ensuring quality, the R&D work that was previously only carried out by a few "craftsmen" can be reduced to an engineering development model that can be performed by ordinary R&D personnel, thereby improving the overall efficiency of R&D work;

[0014] (3) Improve response speed: Componentized banking applications often require a lot of time and effort to conduct impact analysis on iterative requirements to clarify the scope of changes, resulting in longer and longer response times to requirements. The source of the implementation process is structured requirements ("business modeling results"), and the process emphasizes complete and faithful acceptance. In this process, an end-to-end requirement tracking matrix will be established, thereby ensuring that when iterating future requirements, impact analysis can be completed quickly and the scope of application modification and testing can be determined.

[0015] We know that in the general R&D process, during the design phase, designers mainly define functions based on business needs through a series of analysis work based on experience. When designing through Domain-Driven Design (Domain-Driven Design, a software development methodology that aims to design software systems by defining the core concepts of the business domain in detail, this method emphasizes starting from the perspective of business domain experts and guiding software development by establishing business domain models to ensure that the software system can accurately reflect the logic and complexity of the business domain), first identify domain objects such as entities, commands, and events through event storming, and then cluster these domain objects from different dimensions to form boundaries such as aggregation and bounded contexts, establish domain models, and then design domain services based on the domain models. For composite services that need to coordinate multiple domain services, they are implemented by defining application services. The entire process is essentially designed based on business needs. In terms of the phase division of the R&D model, it belongs to the design phase and is a process of deconstructing and reconstructing requirements.

[0016] During the design phase, when designing domain services and internal components based on domain models, we mainly rely on the experience of designers. This results in:

[0017] (1) Low efficiency: Due to the scarcity of experienced designers, especially those with relevant backgrounds, and limited resources, staff shortage has become a bottleneck in the entire project implementation process;

[0018] (2) Quality cannot be controlled: Since the design work is based on experience, it is difficult to have a relatively scientific evaluation method for the output of the design phase, and the quality cannot be well guaranteed.

[0019] When the requirements are provided through business models, the method of identifying and defining domain services in the design phase has undergone a fundamental change, from identifying and defining services based on experience based on domain models to identifying and defining services based on business entities in business models. While fully inheriting the results of business modeling, correctness is guaranteed. Summary of the invention

[0020] In order to solve the above problems existing in the current process of implementing process research and development, the present invention proposes a new method for automatically identifying and defining domain services and internal components according to business entities.

[0021] Explanation of terms

[0022] The concepts and terms involved in the present invention are shown in the following table:

[0023]

[0024]

[0025]

[0026] The relationship between the above concepts is as follows Figure 3 shown.

[0027] As we all know, both the traditional waterfall R&D model and the currently popular agile R&D model mainly emphasize the management of the R&D process, but do not provide specific guidance on the specific methods, guidelines, templates, etc. of the actions that need to be performed in each link of the R&D process. The reason is that the different architectural styles (centralized architecture, component architecture, microservice component architecture, etc.), requirement specifications, development specifications, etc. adopted by the application have different requirements for each link of the R&D model.

[0028] The present invention aims to use a structured software engineering method to guide the conversion of business modeling results into system delivery results, thereby ensuring that the IT system completely and correctly undertakes the business modeling results and is implemented as a microservice component.

[0029] Specifically, the present invention provides a method for automatically identifying and defining domain services and internal components according to business entities, such as Figure 4 As shown, the method comprises the following steps:

[0030] S1. In the operation steps, according to the business entity for which the operation is performed, define the BCC (basic command component) type BOC (business object component);

[0031] S2. The association relationship that requires multiple business entities to be queried together in the operation steps is defined as a BQC (basic query component) type BOC;

[0032] S3. The steps or partial identification classes in the operation steps for executing business rules are identified as a PBB (functional element) type BOC;

[0033] S4. Under a business function, define one or more PBS (basic service) types of BOC;

[0034] S5. For PBS type BOC, the code is implemented as a domain service; for BCC, BQC, and PBB type BOC, the code is implemented as an internal component within the domain service.

[0035] Furthermore, the operation steps described in step S1 of the method for automatically identifying and defining domain services and internal components according to business entities of the present invention are derived from the steps, and each operation step specifies which business entities will be operated on.

[0036] Furthermore, the method step S1 of the present invention for automatically identifying and defining domain services and internal components according to business entities also includes: distinguishing operations for different operation types for the same business entity and defining corresponding BCC type BOCs respectively.

[0037] Furthermore, the operation types described in the method for automatically identifying and defining domain services and internal components according to business entities of the present invention include creation, update, deletion, and reading.

[0038] Furthermore, step S4 of the method for automatically identifying and defining domain services and internal components according to business entities of the present invention also includes: improving the cohesion of PBS type BOCs and reducing the coupling between PBS type BOCs by adjusting PBS type BOCs.

[0039] Furthermore, in the method for automatically identifying and defining domain services and internal components according to business entities of the present invention: aggregation originates from business objects, business entities belong to business objects, and based on this mapping relationship, the aggregation to which the business entity belongs is clarified.

[0040] Furthermore, in the method of automatically identifying and defining domain services and internal components according to business entities of the present invention:

[0041] If there is a modified business entity, call other BOCs with the BOC of the PBS type to which this business entity belongs;

[0042] If they are all read-only business entities, the PBS-type BOC of the aggregation at both ends of the link (the initial aggregation or the aggregation that finally produces the step result) calls other BOCs.

[0043] Furthermore, in the method of automatically identifying and defining domain services and internal components according to business entities of the present invention:

[0044] When the data processed by two BOCs have a dependency relationship, the PBS type BOC is defined according to the aggregation of the dependent party, and the BOC of the dependent party is called;

[0045] When the data processed by two BOCs have no dependency, two PBS-type BOCs are defined to perform collaboration according to the aggregation to which the data belongs.

[0046] On the other hand, the present invention also provides a system for automatically identifying and defining domain services and internal components according to business entities. When the system is running, the steps of the method for automatically identifying and defining domain services and internal components according to business entities are implemented.

[0047] In addition, the present invention also provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the steps of the method for automatically identifying and defining domain services and internal components according to business entities are implemented.

[0048] In summary, the method of automatically identifying and defining domain services and internal components according to business entities of the present invention identifies and defines various types of business object components through the business entities involved in the operation steps and the aggregation to which the business entities belong, and then develops through the business object components to realize domain services and internal components. This method is based on the full inheritance of the business model results, and uses an intuitive, concise and operational way to quickly identify and define the domain services that need to be implemented, overcoming the drawbacks of relying on the experience of designers to define domain services in the past. In addition, the method of the present invention can be checked and can be automatically executed by analysis tools, thereby improving work efficiency and ensuring the quality of task completion. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to more clearly illustrate the prior art and the technical solutions of the present invention, the following briefly introduces the drawings required for use in the description of the present invention. Obviously, the following drawings are only some embodiments recorded in the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0050] Figure 1 A diagram showing the relationship between business architecture (in a narrow sense), business model, IT architecture, and IT design.

[0051] Figure 2 An overall flow chart for the (end-to-end) implementation of the process.

[0052] Figure 3 A relationship diagram between related concepts involved in the present invention.

[0053] Figure 4 It is a schematic diagram of the implementation process of the method of the present invention. DETAILED DESCRIPTION

[0054] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. The present invention can also be implemented or applied through other different specific implementation methods. The details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention.

[0055] At the same time, it should be understood that the protection scope of the present invention is not limited to the specific embodiments described below; it should also be understood that the terms used in the embodiments of the present invention are for describing specific embodiments rather than for limiting the protection scope of the present invention.

[0056] Embodiment: A method for automatically identifying and defining domain services and internal components based on business entities

[0057] Step 1: Define a business object component of the BCC (Basic Command Component) type according to the business entity operated in the operation steps.

[0058] Business functions are derived from tasks, are based on specific business scenarios, and include some or all of the steps in the corresponding tasks.

[0059] The steps describe which attributes of which business entities will be operated on. Operation steps are derived from steps, so each operation step also clarifies which business entities will be operated on.

[0060] In the operation steps, the operation of a specific business entity is defined as a BCC type BOC (Business Object Component). For different operations of the same entity, it is necessary to distinguish the operations to define multiple BCCs. The operation types include create, update, delete, and read.

[0061] For example, the entity [xx contract] (C) creation operation on the entity can be identified as BCC type BOC "create [xx contract]", and the naming convention is as follows:

[0062] Read operation (R): "Get [entity name] according to xx" or "Get [entity name]";

[0063] Update operation (U): "Update [entity name]";

[0064] Create operation (C): "Create [entity name]".

[0065] Step 2: Define the association relationship that requires multiple entities to be queried together in the operation steps as a business object component of the BQC (basic query component) type.

[0066] Step 3: Identify the step or part of the identification class that executes the business rule in the operation step as a PBB (functional element) type business object component.

[0067] Step 4: Under a business function, one or more PBS (basic service) type business object components need to be defined. Since the combination of PBB, BCC, and BQC type BOCs is also business logic, by adjusting the PBS type BOCs, the cohesion of PBS type BOCs can be improved and the coupling between PBS type BOCs can be reduced.

[0068] Aggregates originate from business objects, and business entities belong to business objects. Based on this mapping relationship, it is possible to clearly identify the aggregation to which a business entity belongs.

[0069] If there is an entity to be modified, you can consider calling other BOCs with the PBS type BOC of the aggregate to which this entity belongs (according to the agreement of the business model, a step is allowed to modify at most one business entity, and the modification of the entity is often the ultimate business goal of this step).

[0070] If they are all read-only entities, consider selecting the PBS type BOC of the aggregation at both ends of the link (the initial aggregation or the aggregation that finally produces the step result) to call other BOCs.

[0071] When the data processed by two BOCs have a dependency relationship, a PBS type BOC can be defined according to the aggregation of the relying party to call the BOC of the dependent party.

[0072] When the data processed by two BOCs have no dependency, it is necessary to define two PBS type BOCs to perform collaboration according to the aggregation to which the data belongs.

[0073] Step 5: For PBS type BOC, the code is implemented as a domain service. For BCC, BQC, and PBB type BOC, the code is implemented as an internal component within the domain service.

[0074] Example 1: Different types of BOC can be identified according to the operation steps listed in the following table:

[0075]

[0076] Example 2: The following table shows the definition of PBS type BOC under business function

[0077]

[0078] The above description is only a preferred embodiment of the present invention and does not limit the present invention in any form. Any technician familiar with the profession can make some changes or modifications to the technical contents disclosed above without departing from the scope of the technical solution of the present invention to obtain equivalent embodiments of equivalent changes. However, any simple modification, equivalent changes and modifications made to the above embodiments based on the technical essence of the present invention without departing from the content of the technical solution of the present invention should be included in the scope of protection of the claims of the present invention.

Claims

1. A method for automatically identifying and defining domain services and internal components based on business entities, characterized in that: The method comprises: S1. In the operation steps, define the BCC type BOC according to the business entity targeted by the operation; S2. Define the association relationship that requires multiple business entities to be queried together in the operation steps as a BQC type BOC; S3. Identify the steps or partial identification classes in the operation steps for executing business rules as a BOC of PBB type; S4. Under a business function, define one or more PBS type BOC; S5. For PBS type BOC, the code is implemented as a domain service; for BCC, BQC, and PBB type BOC, the code is implemented as an internal component within the domain service.

2. The method for automatically identifying and defining domain services and internal components according to business entities according to claim 1, characterized in that: The operation steps described in step S1 are derived from the steps, and each operation step specifies which business entities will be operated on.

3. The method for automatically identifying and defining domain services and internal components according to business entities according to claim 1, characterized in that: Step S1 also includes: distinguishing operations for different operation types for the same business entity and defining corresponding BCC type BOCs respectively.

4. The method for automatically identifying and defining domain services and internal components according to business entities according to claim 3, characterized in that: The operation types include create, update, delete, and read.

5. The method for automatically identifying and defining domain services and internal components according to business entities according to claim 1, characterized in that: Step S4 also includes: improving the cohesion of the PBS type BOCs and reducing the coupling between the PBS type BOCs by adjusting the PBS type BOCs.

6. The method for automatically identifying and defining domain services and internal components according to business entities according to claim 1, characterized in that: In the method, the aggregation originates from the business object, the business entity belongs to the business object, and the aggregation to which the business entity belongs is clarified based on this mapping relationship.

7. The method for automatically identifying and defining domain services and internal components according to business entities according to claim 6, characterized in that: In the method: If there is a modified business entity, call other BOCs with the BOC of the PBS type to which this business entity belongs; If they are all read-only service entities, the aggregated PBS type BOCs at both ends of the link call other BOCs.

8. The method for automatically identifying and defining domain services and internal components according to business entities according to claim 6, characterized in that: In the method: When the data processed by two BOCs have a dependency relationship, the PBS type BOC is defined according to the aggregation of the dependent party, and the BOC of the dependent party is called; When the data processed by two BOCs have no dependency, two PBS-type BOCs are defined to perform collaboration according to the aggregation to which the data belongs.

9. A system for automatically identifying and defining domain services and internal components based on business entities, characterized in that: When the system is running, the steps of the method for automatically identifying and defining domain services and internal components according to business entities described in any one of claims 1 to 8 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the steps of the method for automatically identifying and defining domain services and internal components according to business entities as described in any one of claims 1 to 8 are implemented.

Images