Method for Automatically Identifying Business Functions According to Entities by Attribution System

Abstract

The present invention relates to a method for automatically identifying business functions according to the system to which they belong based on entities. The method includes: analyzing all the operation steps contained in the business function, generating a collection of business entities corresponding to the operation steps; splitting the business component into one or more application components according to the architectural design principles, and clarifying to which application component the business entities contained in the business component belong after the split; combining part or all of one application component or multiple application components to form a system, and clarifying to which system each business entity belongs through layer-by-layer mapping; based on the business entity operated by the business function, clarifying the relationship between the business function and the system according to the relationship between the business entity and the system. The present invention uses an intuitive, concise and operational way to quickly clarify the system to which the business function belongs, overcoming the drawbacks brought about by the need to rely on the experience of analysts to divide business functions in the past. The method can be verified and automatically executed, improving work efficiency.

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 its 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 models, product models, and entity models.

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

[0007] To design IT based on the business model and fully implement 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 that are used to carry out structured design based on the enterprise architecture model and obtain project implementation deliverables based on the 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 approach to guide the transformation of business modeling results into system deliverables, thereby ensuring that the IT system fully and correctly inherits the business modeling results and implements them as microservice components.

[0011] As business modeling becomes a major trend in banks' enterprise-level architecture transformation, implementation processes based on business modeling findings have become a key focus for banks in their application R&D. A complete, reasonable, and efficient implementation process is crucial for ensuring project delivery with guaranteed quality and quantity. Currently, R&D priorities for implementation processes include:

[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 originally 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) Improving Response Speed: Componentized banking applications often require a significant amount of time and effort to conduct impact analysis on iterative requirements to clarify the scope of changes, resulting in increasingly longer response times. The source of the implementation process is structured requirements ("business modeling results"). The process emphasizes complete and faithful implementation. During this process, an end-to-end requirements tracking matrix is established, ensuring that impact analysis can be quickly completed and the scope of application modifications and testing can be determined for future iterations.

[0015] As we know, in a typical R&D process, during the requirements analysis phase, analysts primarily rely on experience and conduct a series of analytical tasks to identify a series of business functions based on business requirements. This then leads to the design phase, where designers carry out the design. When using Domain-Driven Design (DDD), a software development methodology that aims to design software systems by defining core concepts within the business domain, this approach emphasizes starting from the perspective of domain experts and guiding software development by building a model of the business domain to ensure that the software system accurately reflects the logic and complexity of the business domain, the design process begins with event storming to identify domain objects such as entities, commands, and events. These domain objects are then clustered along different dimensions to form boundaries such as aggregates and bounded contexts. A domain model is then established, and domain services are designed based on the domain model. Composite services that require collaboration between multiple domain services are implemented through the definition of application services. The entire process is essentially a design based on business requirements. In the R&D model, this phase of work falls within the design phase, a process of deconstructing and reconstructing requirements.

[0016] During the analysis phase, we mainly rely on the experience of analysts, 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 stage, and the quality cannot be well guaranteed.

[0019] Once requirements are provided through a business model, the approach to identifying and defining business functions during the analysis phase undergoes a fundamental shift, from empirically identifying business functions to identifying business functions based on the business entities in the business model. This ensures correctness while fully inheriting the results of business modeling. 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 entity and the belonging system.

[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 there is no specific guidance on the specific methods, guidelines, templates, etc. for 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 is implemented as a microservice component.

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

[0029] S1. Analyze all the operation steps included in the business function and generate a collection of business entities that are explicitly 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 based on architectural design principles. When splitting into multiple application components, clearly identify to which application component the business entities contained in the business component belong.

[0031] S3. Combine one or more application components, in part or in full, to form a system. By mapping each layer, clearly identify which system each business entity belongs to.

[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 entity and the belonging system of the present invention is derived from a task based on a specific business scenario, and the business function includes part or all of the steps in the corresponding task, which steps describe which attributes of which business entities will be operated on.

[0034] Furthermore, the method of automatically identifying business functions by entity according to the belonging system according to the present invention is based on the operation steps described in step S1, and each operation step clearly defines which business 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 automatically identifying business functions according to the belonging system based on entities, the present invention provides 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.

[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 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 relates to 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, wherein the operation refers to an 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 entity according to the belonging system 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 by entity according to the belonging system of the present invention only performs actions of creating, maintaining or deleting 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 entity and the home system. When the system is running, the steps of the method for automatically identifying service functions according to the entity and the home system are implemented.

[0042] In addition, the present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-mentioned method for automatically identifying service functions according to the entity and the belonging system.

[0043] In summary, the method of the present invention for automatically identifying business functions according to the system to which they belong based on the entity 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. Moreover, the division method adopted by the present invention can be verified 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 Provides an overall flow chart for the (end-to-end) implementation of the process.

[0047] Figure 3 A diagram showing the relationships among the 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 Schematic diagram of the implementation process of the method of the present invention. DETAILED DESCRIPTION

[0050] To make the objectives, technical solutions, and advantages of the present invention more clearly apparent, the technical solutions 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 some, not all, of the embodiments of the present invention. The present invention may also be implemented or applied through different specific implementation methods, and the details in this specification may 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 scope of protection 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 scope of protection of the present invention.

[0052] Embodiment: A method for automatically identifying business functions based on the entity and the home system

[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 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 clarifies 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 broken down into BUSI001, BUSI002, and BUSI003, and the operation steps broken down into OPER001, OPER002, OPER003, OPER004, and OPER005, are shown in Table 2 below.

[0058] Table 2 Detailed information of TASK001

[0059]

[0060] As you can see, for each business function, you can clearly know which business entities are being 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.

[0066] (3) An application component or a combination of parts or all of multiple 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 on 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 content disclosed above without departing from the scope of the technical solution of the present invention to obtain equivalent embodiments with equivalent changes. However, any simple modifications, 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 business functions according to the entity and the home system, characterized in that: The method comprises: S1. Analyze all operational steps involved in the business function and generate a set of business entities identified by these operational steps. The business entities in this set are the business entities involved in the business function. S2. Split business components into one or more application components based on architectural design principles. When splitting into multiple application components, clearly define to which application component the business entities contained in the business component belong. If a business entity can be operated by multiple business components, the primary business component must be responsible for the creation and lifecycle management of the business entity, while other business components must only access the business entity. S3. Combine one or more application components, partially or completely, to form a system. Through layer-by-layer mapping, clearly identify which system each business entity belongs to. S4. Based on the business entities operated by the business function, clarify the relationship between the business function and the system, following the relationship between the business entities and the system defined in the previous step. If the business function operates on multiple business entities, split them up until a single business function only creates, maintains, or deletes a single business entity.

2. The method according to claim 1, wherein: The business function described in step S1 is derived from a task based on a specific business scenario. The business function includes some or all steps in the corresponding task. These steps describe which attributes of which business entities will be operated on.

3. The method according to claim 2, wherein: The operation steps described in step S1 are derived from the steps, and each operation step clearly 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 according to claim 1, wherein: The business components described in step S2 each include one or more business entities, and each business entity belongs to only one business component.

5. The method according to claim 1, wherein: 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.

6. The method according to claim 1, wherein: 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.

7. A system for automatically identifying business functions according to the entity and the system to which it belongs, characterized in that: When the system is running, the steps of the method for automatically identifying service functions according to the belonging system based on the entity as described in any one of claims 1 to 6 are implemented.

8. 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 a service function according to an entity and a home system according to any one of claims 1 to 6 are implemented.

Images