A design method for business rule analysis and component reuse

Abstract

The present invention discloses a design method for business rule analysis and component reuse, including: a business distribution method; wherein the business distribution method includes: a business distribution project receives a unified message sent by the front desk, generates a business execution code by parsing and analyzing the message; based on the generated business execution code, obtains a component business configuration table, generates a business execution process template; generates the order component execution process through a configuration relationship table corresponding to the current order message and the business execution code, and stores it in the order component process execution plan table; an asynchronous message notifies the component project to call the component execution. The present invention reduces the operation and maintenance cost by reusing the front and back code on the basis of ensuring that the user's business acceptance is independent and clear; through configuration, it solves the problem of large development workload and bug rate caused by the dynamic increase and decrease of business links.

Description

Technical Field

[0001] The present invention relates to the technical field, and in particular to a design method for business rule analysis and component reuse. Background Art

[0002] Before the transformation of project products, a separate function point needs to be developed for each business scenario to provide business support. The advantage is that each business scenario can be directly handled at the corresponding function point, the acceptance is relatively clear, and the occurrence of business acceptance errors is reduced. However, it still has the following defects:

[0003] 1. There are many functional points, which brings the main problem that when customers accept the application, they need to find the business of corresponding scenarios among many functional points to handle, which leads to low efficiency;

[0004] 2. The front-end and back-end codes cannot be reused, resulting in a lot of redundant code. When modifying a common problem, it may be necessary to modify the code of multiple functional points, making the maintenance cost relatively high.

[0005] 3. The business acceptance process cannot be unified. If a process is added to the business, such as a paperless process, this will cause many functional codes to need to add this process processing in the middle link. In this way, many functions require processing of the codes before and after the paperless link. The modification amount is relatively large, and there are many modified functions, which has a greater impact. Summary of the invention

[0006] In view of the above problems existing in the prior art, the present invention provides a design method for business rule analysis and component reuse.

[0007] The present invention discloses a design method for business rule analysis and component reuse, including: a business distribution method; wherein:

[0008] The service distribution method comprises:

[0009] The business distribution project receives the unified message sent by the front desk, and generates the business execution code by parsing and analyzing the message;

[0010] Based on the generated business execution code, obtain the component business configuration table and generate a business execution process template;

[0011] Generate the order component execution process through the configuration relationship table corresponding to the current order message and the business execution code, and store it in the order component process execution plan table;

[0012] Asynchronous message notification component project calls component execution.

[0013] As a further improvement of the present invention, the analysis method of the message includes:

[0014] Differentiate business types through product selection at the front desk;

[0015] By configuring commodity account opening and inventory business at the front desk, business actions are distinguished; wherein the business actions include account opening and change;

[0016] Obtain detailed classification of each product through product configuration;

[0017] Based on the sub-classification of business types, business actions and commodities, business execution codes are generated through code combinations.

[0018] As a further improvement of the present invention, the component service configuration table includes:

[0019] The component definition table is used to define the component instance name. When the component is executed, it obtains the service instance through this name to call the service execution;

[0020] Business definition table, used to define business execution code and name, business type;

[0021] Business component relationship table, used to define the components to be executed associated with the current business;

[0022] The business component execution sequence table is used to define the current business component execution process and define the component execution method.

[0023] As a further improvement of the present invention, the order component process execution plan table stores the order component execution process, including the execution sequence number, execution status, the previous execution component, the next execution component and component execution details.

[0024] As a further improvement of the present invention, the component execution is performed by reading data of the order component process execution schedule and calling them sequentially.

[0025] As a further improvement of the present invention, it also includes: a commodity display method;

[0026] The commodity display method comprises:

[0027] Add product screening conditions to the products in production to speed up the rapid positioning and acceptance in various scenarios during the user acceptance process; wherein, the screening conditions include fuzzy queries by business category, package range, specifications, sales volume and name.

[0028] As a further improvement of the present invention, it also includes: a component reuse method;

[0029] The component reuse method comprises:

[0030] The front-end adopts a component development model to develop the smallest atomic components; the front-end dynamically generates customized interfaces corresponding to products through component assembly; each link of the back-end business is also split into individual components, targeting different business scenarios, but all businesses with the same components can share components.

[0031] Compared with the prior art, the present invention has the following beneficial effects:

[0032] The present invention reduces operation and maintenance costs by reusing foreground and background codes while ensuring that user business acceptance is independent and clear; and solves the problem of large development workload and bug rate caused by dynamic increase and decrease of business links through configuration. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 The present invention is a flowchart of a service distribution method disclosed in an embodiment of the present invention. DETAILED DESCRIPTION

[0034] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0035] The present invention is further described in detail below in conjunction with the accompanying drawings:

[0036] The present invention provides a design method for business rule analysis and component reuse, which performs unified transformation and optimization on the basis of unified acceptance and transformation of production products; it includes:

[0037] In order to solve the problem of too many functional points in the foreground, the present invention designs a commodity display method, that is, after the commodity is transformed, the commodity display is unified in the foreground, and each commodity is equivalent to a business scenario or functional point of the foreground. In this way, the commodity screening conditions are increased in the production of commodities, such as by business category, package range, specification, sales volume and name fuzzy query and other different dimensions, so as to speed up the rapid positioning and acceptance of each scenario in the user acceptance process.

[0038] In order to solve the problem of code reuse, the present invention designs a component reuse method, that is, in the product process, a component development mode is adopted in the foreground and the backstage to develop the smallest atomic component, and the foreground dynamically generates a customized interface corresponding to the product through component assembly; each link of the backstage business is also split into components, so that for different business scenarios, all businesses with the same components can share components to achieve the purpose of code reuse; at the same time, if this component changes later, it only needs to change the component implementation, and all businesses using the component can change at the same time, reducing operation and maintenance costs and the probability of problems caused by modifications.

[0039] In order to solve the problem of large amount of development and modification caused by changes in business process links, the present invention provides a business distribution method, that is, dynamically generating business execution process solutions through configuration according to different business rules; in this way, dynamic processes are configured according to different business scenarios, and no matter whether corresponding process links are added or reduced in the middle, no code development and modification is required, but only configuration modification is required, which greatly improves the dynamic business support capability.

[0040] Specifically, Figure 1 As shown, the service distribution method of the present invention includes:

[0041] Step 1: The business distribution project receives the unified message sent by the front desk, and generates the business execution code by parsing and analyzing the message;

[0042] The analysis method of the analysis message includes: distinguishing the business type through the product selection at the front desk; wherein the business type includes mobile network, broadband, fixed-line or converged related business; distinguishing the business actions through the front desk configuration of the product account opening type and the stock type business; wherein the business actions include account opening and change; obtaining the sub-classification of each product through product configuration; based on the business type, business action and sub-classification of the product, generating the business execution code through the coding combination. For example, broadband speed-up category. L represents broadband business, broadband speed-up is a change type business represented by CHG, and the broadband speed-up product configuration has a subdivision type of 609, so the final business code is: L-CHG-609.

[0043] Step 2: Based on the generated business execution code, obtain the component business configuration table and generate a business execution process template; wherein the component business configuration table includes:

[0044] The component definition table is used to define the component instance name. When the component is executed, it obtains the service instance through this name to achieve the purpose of calling the service execution. In the component service, spring aop is used to realize the unified recording of component logs, the unified change of order status after the component execution is completed, and the automatic unified update of the component execution status of the component process execution plan table, so that developers only need to care about the implementation of business logic.

[0045] The business definition table is used to define the business execution code and name, business type and other descriptions. The business definition table can be used to know the current business status. At the same time, the business type is recorded in the generated order table, so that the order can show the accepted business status.

[0046] Business component relationship table, used to define the components to be executed associated with the current business;

[0047] The business component execution sequence table is used to define the current business component execution process and define the component execution mode, that is, synchronous or asynchronous; when executing synchronously, you need to wait for the execution result before continuing to execute the next component, while when executing asynchronously, you do not need to wait for the current component to complete execution before executing the next step of the process.

[0048] Step 3: Generate the order component execution process through the configuration relationship table corresponding to the current order message and the business execution code, and store it in the order component process execution plan table; wherein,

[0049] The order component process execution plan table stores the order component execution process, including the execution sequence number, execution status, the previous execution component, the next execution component and component execution details.

[0050] Step 4: asynchronous message notifies the component engineering to call the component execution; wherein,

[0051] Component execution is accomplished by reading data from the order component process execution schedule and calling it sequentially.

[0052] Furthermore, the premise of business distribution is that the front-end products are uniformly componentized and accepted, and the messages requested to the back-end services are in a unified format.

[0053] Example 1:

[0054] The front-end acceptance of Wojia Networking and Broadband Speed-up Services is different. Wojia Networking requires the entry of terminal-related information, while Broadband Speed-up does not have this content. The front-end product needs to configure different business categories for the two services, and add a terminal serial code entry component for the Wojia Networking service based on this category. Both services in the background use the same interface. In this way, you only need to configure business distribution-related configurations according to different business types, but the final calling component is implemented by the same component, achieving the purpose of code reuse.

[0055] Example 2:

[0056] Fixed network migration did not originally support paperless operation. After the unified transformation of products was launched, paperless operation can be dynamically added by adding paperless process components to the business distribution configuration without the need for related code transformation.

[0057] The advantages of the present invention are:

[0058] The present invention reduces operation and maintenance costs by reusing foreground and background codes while ensuring that user business acceptance is independent and clear; and solves the problem of large development workload and bug rate caused by dynamic increase and decrease of business links through configuration.

[0059] The preferred embodiments of the present invention disclosed above are only used to help illustrate the present invention. The optional embodiments do not describe all the details in detail, nor do they limit the invention to specific implementation methods. Obviously, many modifications and changes can be made according to the content of this specification. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the present invention, so that those skilled in the art can understand and use the present invention well. The present invention is limited only by the claims and their full scope and equivalents.

Claims

1. A design method for business rule analysis and component reuse, characterized in that: include: Business distribution method and component reuse method; wherein, The service distribution method comprises: The business distribution project receives the unified message sent by the front desk, and generates the business execution code by parsing and analyzing the message; wherein the analysis method of the message includes: distinguishing the business type through the commodity selection at the front desk; distinguishing the business actions through the front desk configuration of the commodity account opening and inventory type business; wherein the business actions include account opening and change; obtaining the sub-classification of each commodity through commodity configuration; generating the business execution code through code combination based on the business type, business action and commodity sub-classification; Based on the generated business execution code, obtain the component business configuration table and generate a business execution process template; wherein the component business configuration table includes: The component definition table is used to define the component instance name. When the component is executed, it obtains the service instance through this name to call the service execution. In the component service, spring aop is used to realize the unified recording of component logs, the unified change of order status after the component execution is completed, and the automatic unified update of component execution status in the component process execution plan table; The business definition table is used to define the business execution code, name, and business type. The business definition table is used to know the current business status. At the same time, the business type is recorded in the generated order table. Business component relationship table, used to define the components to be executed associated with the current business; The business component execution sequence table is used to define the current business component execution process and the component execution mode, that is, synchronous or asynchronous. In synchronous execution, you need to wait for the execution result before continuing to execute the next component, while in asynchronous execution, you can execute the next process without waiting for the current component to complete execution. Generate an order component execution process through the configuration relationship table corresponding to the current order message and the business execution code, and store it in the order component process execution plan table; Asynchronous message notification component engineering calls component execution; The component reuse method comprises: The front-end adopts a component development model to develop the smallest atomic components; the front-end dynamically generates customized interfaces corresponding to products through component assembly; each link of the back-end business is also split into individual components, targeting different business scenarios, but all businesses with the same components can share components.

2. The design method according to claim 1, characterized in that: The order component process execution plan table stores the order component execution process, including the execution sequence number, execution status, the last executed component, the next executed component and component execution details.

3. The design method according to claim 1, characterized in that: The component execution is performed by reading the data of the order component process execution plan table and calling them sequentially.

4. The design method according to claim 1, characterized in that: Also includes: Methods of displaying goods; The commodity display method comprises: Add product screening conditions to the products in production to speed up the rapid positioning and acceptance in various scenarios during the user acceptance process; wherein, the screening conditions include fuzzy queries by business category, package range, specifications, sales volume and name.

Images