Method for automatically identifying service function according to entity and affiliation system

Abstract

The invention relates to a method for automatically identifying a service function according to an entity and an affiliation system. The method comprises the following steps: analyzing all operation steps contained in a service function, and generating a set of service entities corresponding to the operation steps; splitting the service component into one or more application components according to an architecture design principle, and determining which application component the service entity contained in the service component belongs to; the method comprises the following steps: partially or completely combining one application component or a plurality of application components to form a system, and determining which system each business entity belongs to through layer-by-layer mapping; and determining the relationship between the service function and the system according to the relationship between the service entity and the system based on the service entity operated by the service function. According to the method, the system to which the business functions belong is rapidly and clearly defined in a visual, simple and operable mode, the defect caused by the fact that business function division needs to be carried out by means of experience of analysts in the past is overcome, the method can be checked and automatically executed, and the working efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of service function identification methods, and in particular to a method for automatically identifying service functions according to an entity and a belonging system. 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 entities.

[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 process 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, in the demand analysis phase, analysts mainly identify a series of business functions based on business needs through a series of analysis work based on experience, and then enter the design phase for designers to design. 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 analysis phase, the analyst's experience is the main reliance, which results in:

[0017] (1) Low efficiency: Due to the scarcity of experienced analysts, 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 analysis work is based on experience, it is difficult to have a relatively scientific evaluation method for the output of the analysis phase, and the quality cannot be well guaranteed.

[0019] When the requirements are provided in the form of business models, the method of identifying and defining business functions in the analysis phase has undergone a fundamental change, from identifying business functions based on experience to identifying business functions based on business entities in the business model. 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 business functions according to the belonging system based on the entity.

[0021] Explanation of terms

[0022] The concepts and terms involved in the present invention are shown in Table 1 below:

[0023] Table 1 Concepts and terms

[0024]

[0025]

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

[0027] As we all know, whether it is the traditional waterfall R&D model or the currently popular agile R&D model, the main emphasis is on the management of the R&D process, but no specific guidance is given for 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. The purpose of this invention is 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 fully and correctly undertakes the business modeling results and lands as microservice components.

[0028] Specifically, the present invention provides a method for automatically identifying service functions according to the entity and the belonging system, such as Figure 5 As shown, the method comprises the following steps:

[0029] S1. Analyze all the operation steps included in the business function and generate a collection of business entities that are clearly operated by these operation steps. The business entities in this collection are the business entities involved in the business function;

[0030] S2. Split the business component into one or more application components according to the architectural design principles. When split into multiple application components, clarify to which application component the business entity contained in the business component belongs after the split;

[0031] S3. Combine one or more application components, in part or in whole, to form a system, and make it clear which system each business entity belongs to by mapping layer by layer;

[0032] S4. Based on the business entities operated by the business functions, clarify the relationship between the business functions and the system in accordance with the relationship between the business entities and the system clarified in the previous step.

[0033] Furthermore, the business function described in step S1 of the method for automatically identifying business functions according to the belonging system based on the entity of the present invention is derived from the task based on the specific business scenario, and the business function includes part or all of the steps in the corresponding task, which steps explain which attributes of which business entities will be operated on.

[0034] Furthermore, the operation steps described in step S1 of the method for automatically identifying the service function according to the belonging system of the entity in the present invention are derived from the steps, and each operation step clarifies which service entities will be operated on;

[0035] The business function includes one or more operation steps, and the business entities involved in the business function are the collection of business entities clearly operated by all the operation steps belonging to this business function.

[0036] Furthermore, in the method of the present invention for automatically identifying service functions according to the belonging system based on the entity, the service components described in step S2, each service component includes one or more service entities, and each service entity belongs to only one service component.

[0037] Furthermore, according to the business components described in step S2 of the method for automatically identifying business functions according to the belonging system of the entity of the present invention, if there is a business entity that can be operated by multiple business components, it is necessary to clearly define the primary business component responsible for the creation and full life cycle management of the business entity, while the remaining business components can only access the business entity.

[0038] Furthermore, the present invention provides a business entity operated by the business function described in step S4 of the method for automatically identifying the business function according to the belonging system according to the entity, and the operation refers to the action of creating, maintaining or deleting the business entity.

[0039] Furthermore, if the business function described in step S4 of the method for automatically identifying business functions by belonging system according to entities of the present invention operates multiple business entities, they are split until a single business function only creates, maintains or deletes one business entity.

[0040] Furthermore, the split single business function described in step S4 of the method for automatically identifying business functions according to the belonging system according to the entity of the present invention only creates, maintains or deletes one business entity, but can access multiple business entities.

[0041] On the other hand, the present invention also provides a system for automatically identifying service functions according to the belonging system based on the entity, and when the system is running, the steps of the method for automatically identifying service functions according to the belonging system based on the entity are implemented.

[0042] 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 above-mentioned method of automatically identifying business functions according to the belonging system based on the entity are implemented.

[0043] In summary, the method of automatically identifying business functions according to the system to which they belong based on the entity of the present invention is a method for determining the system to which the business function belongs through the business entity. It is based on fully inheriting the results of the business model and uses an intuitive, concise and operational method to quickly clarify the system to which the business function belongs, overcoming the drawbacks of relying on the experience of analysts to divide business functions in the past. In addition, the division method adopted by 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

[0044] 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.

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

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

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

[0048] Figure 4 Schematic diagram of the mapping relationship between business entities and systems in an embodiment of the present invention.

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

[0050] 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.

[0051] 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.

[0052] Embodiment: A method for automatically identifying service functions according to the belonging system based on the entity

[0053] Step 1: Clarify the relationship between business functions and business entities:

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

[0055] (2) Steps describe which attributes of which business entities will be operated on. Operation steps are derived from steps, so each operation step also specifies which business entities will be operated on.

[0056] (3) A business function includes one or more operation steps, so the business entities involved in the business function are the collection of all business entities that are explicitly operated by the operation steps belonging to this business function.

[0057] For example, task TASK001 includes steps STEP001, STEP002 and STEP003. The business functions are BUSI001, BUSI002 and BUSI003, and the operation steps are OPER001, OPER002, OPER003, OPER004 and OPER005. The specific information of task TASK001 is shown in Table 2 below:

[0058] Table 2 Detailed information of TASK001

[0059]

[0060] It can be seen that for each business function, we can clearly know which business entities are operated, as shown in Table 3 below:

[0061] Table 3 Operational business entities corresponding to business functions

[0062] Business function number Business entity of operation BUSI001 Customer(R), Watchlist(R), Contract(C) BUSI002 Account (C), Contract (R) BUSI003 Limit(U)

[0063] Step 2: Clarify the relationship between business entities and systems:

[0064] (1) A business component contains one or more business entities, and a business entity belongs to only one business component (if a business entity can be operated by multiple business components, it is necessary to clearly define the primary business component responsible for the creation and full lifecycle management of the business entity, while other business components can only access this business entity);

[0065] (2) A business component can be split into one or more application components based on the architectural design principles. When split into multiple application components, it is necessary to clarify which application component the business entities contained in the business component belong to after the split;

[0066] (3) An application component or a combination of some or all of several application components to form a system;

[0067] (4) Through layer-by-layer mapping, it is possible to clearly identify which system a business entity belongs to.

[0068] The mapping relationship between business entities and systems is as follows Figure 4 shown.

[0069] Step 3: Clarify the relationship between business functions and systems:

[0070] (1) If a business function operates multiple business entities, it must be split until a single business function only creates, maintains, or deletes one business entity, but can access multiple business entities;

[0071] (2) Based on the business entities operated by the business functions (the operations here refer to the creation, maintenance or deletion of business entities), the relationship between the business functions and the system is clarified according to the relationship between the business entities and the system. The relationship between the business functions and the affiliated systems is shown in Table 4 below:

[0072] Table 4 Relationship between business functions and home systems

[0073]

[0074] 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 service functions according to the entity and the belonging system, characterized in that: The method comprises: S1. Analyze all the operation steps included in the business function and generate a collection of business entities that are clearly operated by these operation steps. The business entities in this collection are the business entities involved in the business function; S2. Split the business component into one or more application components according to the architectural design principles. When split into multiple application components, clarify to which application component the business entity contained in the business component belongs after the split; S3. Combine one or more application components, in part or in whole, to form a system, and make it clear which system each business entity belongs to by mapping layer by layer; S4. Based on the business entities operated by the business functions, clarify the relationship between the business functions and the system in accordance with the relationship between the business entities and the system clarified in the previous step.

2. The method for automatically identifying service functions according to the entity and the belonging system according to claim 1, characterized in that: The business function described in step S1 is derived from a task based on a specific business scenario. The business function includes part or all of the steps in the corresponding task. These steps describe which attributes of which business entities will be operated on.

3. The method for automatically identifying service functions according to the entity and the belonging system according to claim 2, 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; The business function includes one or more operation steps, and the business entities involved in the business function are the collection of business entities clearly operated by all the operation steps belonging to this business function.

4. The method for automatically identifying service functions according to the entity and the belonging system according to claim 1, characterized in that: The business components described in step S2, each business component includes one or more business entities, and each business entity belongs to only one business component.

5. The method for automatically identifying service functions according to the entity and the belonging system according to claim 4, characterized in that: For the business components described in step S2, if there is a business entity that can be operated by multiple business components, it is necessary to clearly define the primary business component as being responsible for the creation and full life cycle management of the business entity, while the remaining business components can only access the business entity.

6. The method for automatically identifying service functions according to the entity and the belonging system according to claim 1, characterized in that: The business entity operated by the business function described in step S4, wherein the operation refers to the action of creating, maintaining or deleting the business entity.

7. The method for automatically identifying service functions according to the entity and the belonging system according to claim 1, characterized in that: If the business function described in step S4 operates multiple business entities, they are split until a single business function only performs the action of creating, maintaining or deleting one business entity.

8. The method for automatically identifying service functions according to the entity and the belonging system according to claim 7, characterized in that: The split single business function described in step S4 only performs the action of creating, maintaining or deleting one business entity, but can access multiple business entities.

9. A system for automatically identifying business functions according to the entity and the belonging system, characterized in that: When the system is running, the steps of the method for automatically identifying business functions according to the belonging system according to any one of claims 1 to 8 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the steps of the method for automatically identifying a service function according to an entity and a belonging system as described in any one of claims 1 to 8.

Images