Method for researching, developing and maintaining bank application system based on process arrangement tool

By adopting the first orchestration and then coding method based on process orchestration tools in the research and development of bank application systems, the high cost and maintenance problems of bank application systems are solved, and the system is efficiently maintained and the ability to respond quickly to business needs is achieved.

CN119556887APending Publication Date: 2025-03-04BEIJING ZHONGGUANCUN BANK CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411654508.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-11-19
Publication Date
2025-03-04

AI Technical Summary

Technical Problem

The research and development and maintenance of bank application systems are inefficient and error risks caused by high costs, high maintenance difficulty, and inefficiency and error risks caused by the incorrect correspondence between documents and system updates during system optimization.

Method used

The system development method based on process orchestration and then coding is adopted. The process lane, module code lane and public service lane are designed through graphical process orchestration development tools to realize process orchestration and code generation, reducing code complexity and maintenance difficulty.

Benefits of technology

It improves the research and development and maintenance efficiency of bank application systems, reduces the system error rate, improves the system maintainability, and enables the bank application system to respond to business needs more quickly.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119556887A_ABST
    Figure CN119556887A_ABST
Patent Text Reader

Abstract

The invention provides a method for researching, developing and maintaining a bank application system based on a process arrangement tool, and the method comprises the following steps: selecting a graphical process arrangement development tool according to the field to which the application system belongs; carrying out process design by using a graphical process arrangement development tool; drawing an application system research and development flow chart by using a graphical flow arrangement development tool, and archiving the application system research and development flow chart; according to an application system research and development flow chart, a function module is newly built for each flow node. According to the method for researching, developing and maintaining the bank application system based on the process arrangement tool, after the corresponding process arrangement development tool is selected, when the function module which completes the process is optimized and upgraded, a design document and obscure and difficult-to-understand codes do not need to be browsed, and the process is simplified. And the design thought of the previous development or maintenance personnel can be quickly understood only by browsing the graphical arrangement flow chart.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a software development and maintenance method, and in particular to a method for developing and maintaining a banking application system based on a process orchestration tool, so as to improve the software development process and maintainability and reduce the error rate of the system software. Background Art

[0002] At present, the research and development of banking application systems in my country is generally divided into two construction modes: outsourcing and independent research and development. Among them, although independent research and development has the advantages of high demand matching and timely technological response, it also has the problems of requiring a large amount of manpower during the construction period to complete the system as planned, and the need to reduce personnel during the maintenance period to reduce maintenance costs, which leads to the introduction of system defects when optimizing needs, as well as the disadvantages that it takes a long time to solve problems. These problems are the chronic diseases of banking application system research and development and maintenance.

[0003] This problem becomes more prominent especially for small and medium-sized banks, which are under pressure from both low overall demand and cost assessments and often significantly reduce the number of maintenance personnel for the corresponding systems before the systems are fully stable.

[0004] The industry usually solves this problem by increasing the frequency of project document updates and improving document quality. However, in actual implementation, there have always been problems such as the lack of accurate measurement standards for document quality, and the lack of clear correspondence and accurate description between document updates and system updates. Faced with the above difficulties, R&D personnel often fail to update documents in a timely manner, and even if there are updates, most of them are incremental updates. Especially for system outline design and detailed design documents, as the number of modified versions and times increases, the correlation between the incremental modified files and the original documents is difficult for readers to understand. After two or three versions, the documents are basically unusable.

[0005] In addition, in order to increase module reuse and improve R&D efficiency in single system construction, the industry introduced process orchestration tools, but the effect was not ideal in actual construction. Except for the initial application architects, it was difficult for other R&D personnel to achieve reuse, and process orchestration became a formality. The most common orchestration nodes only included the start, processing, and end nodes. All business processing processes were completed in the processing nodes in a coded manner.

[0006] After the introduction of the process orchestration tool, the goal of increasing module reuse and improving R&D efficiency was indeed achieved during the system construction period. However, when there are subsequent optimization needs, there are still problems caused by the lack of clear correspondence and accurate description between the aforementioned documents and system updates. System maintenance personnel need to read through all the codes of the processing nodes and re-understand the meaning of the codes, which is inefficient and easy to make mistakes.

[0007] Bank application systems cannot be easily restructured like application systems in other industries. However, the maintainability of application systems is crucial to bank application systems, and an improved method for developing and maintaining bank application systems is urgently needed. Summary of the invention

[0008] The present invention proposes a system development and quality inspection method based on a process orchestration system development tool, establishes a system development method of first orchestration and then coding, and achieves the goal of improving the development and maintainability of the bank application system at a low cost.

[0009] In order to achieve the above objectives, the present invention provides a method for developing and maintaining a banking application system based on a process orchestration tool, comprising the following steps:

[0010] 1) Select a graphical process orchestration development tool based on the application system's field;

[0011] 2) Use graphical process orchestration development tools to design processes:

[0012] Place each process node in the process lane, module code lane, and public service lane respectively;

[0013] The nodes in the process lane are process orchestration nodes, which are used to complete process orchestration, including: business process judgment nodes, business process branch nodes, and business process combination nodes;

[0014] The business process judgment node is used to connect the business process branch node and / or the business process combination node;

[0015] Business process branch nodes and business process combination nodes have corresponding nodes in the module code lane or public service lane;

[0016] Each node in the module code lane has a corresponding node in the process lane; each node in the module code lane is an internal interface, corresponding to a development subtask;

[0017] Each node in the public service lane has a corresponding node in the module code lane or process lane;

[0018] 3) Use graphical process orchestration development tools to draw application system development flow charts and archive them;

[0019] 4) Create new functional modules for each process node according to the application system development flowchart.

[0020] The method for developing and maintaining a banking application system based on a process orchestration tool described in the present invention has mature process orchestration development tools for commonly used core systems and credit systems in the banking industry. After selecting the corresponding process orchestration development tool, when optimizing and upgrading the functional modules that have completed the process of the present invention, there is no need to read the design documents and obscure codes. Instead, one only needs to browse the graphical orchestration flowchart to quickly understand the design ideas of the previous developer or maintainer.

[0021] Preferably, when a business process is adjusted, the process nodes involved in this business process adjustment are found from the process lane according to the system development process diagram, and then the process nodes corresponding to the process nodes involved in this business process adjustment are found from the module code lane and the public service lane;

[0022] Use graphical process orchestration development tools to redraw the application system development process diagram and archive it;

[0023] Reconstruct the functional modules for the process nodes and corresponding module code lanes and / or public service lane process nodes involved in this business process adjustment.

[0024] When the business process is adjusted, each optimization and upgrade will involve the adjustment and development of the graphical process orchestration. This method makes it easy to find the process nodes that need to be adjusted and developed, to evaluate the workload and modification difficulty of this optimization, and to maintain the process level of the optimization work.

[0025] Preferably, the method further includes grading the developers according to their business capabilities, and only assigning developers with high business capabilities to participate in the development of functional modules corresponding to the process nodes of the process lane. This method improves the reliability of the system.

[0026] Preferably, for the process nodes placed in the module code swim lane, the workload of the development subtasks corresponding to the process nodes is further evaluated, and the development subtasks are graded according to the evaluation results.

[0027] More preferably, the development subtasks are divided into the following levels: the first level, the development self-test workload of the development subtask is less than or equal to 2 working days; the second level, the development self-test workload of the development subtask exceeds 2 working days. In principle, it is forbidden to assign development subtasks that take more than 2 working days, which can reduce the system error rate.

[0028] Preferably, for the process node placed in the module code swimlane, the workload of the development subtask corresponding to the process node is further evaluated, and when the workload is greater than a preset value, the process node is adjusted to the process swimlane.

[0029] Preferably, for the process nodes placed in the module code swim lane, the importance of the development subtasks corresponding to the process nodes is further evaluated, and the development subtasks are graded according to the evaluation results.

[0030] The method for developing and maintaining a banking application system based on a process orchestration tool described in the present invention can greatly improve the maintainability of application system development because the process node splitting granularity is fine enough, the scale of each internal interface code in the module code lane is relatively small, and the code function is single and easy to read.

[0031] More preferably, the development subtasks are assigned to junior and intermediate developers according to the classification. Because each internal interface code in the module code lane is relatively small in size and has a single code function, junior and intermediate developers can be fully utilized, reducing the impact of junior and intermediate developers' business capabilities on the overall system.

[0032] Preferably, each node in the public service swim lane is graded according to the total number of process nodes to which it corresponds to, in order to assess its importance.

[0033] More preferably, the functional modules corresponding to each node in the public service lane are assigned to developers of different levels according to the classification. This allocation method can make full use of the business capabilities of developers and reduce the impact of the business capabilities of junior and intermediate developers on the overall system.

[0034] By using the method of the present invention to regularly adjust the process planners and subtask developers of the functional modules, the system reliability can be effectively improved. If the project management specifications are adjusted and the review of the process outline design is added when the functional modules are newly built or reconstructed, the system reliability and ease of improvement can be significantly improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 This is a schematic diagram of the process arrangement of a bank application system during its development;

[0036] Figure 2 for Figure 1 The bank application system shown in the figure is a flow chart of the process of developing and maintaining a bank application system using a method for developing and maintaining a bank application system based on a process arrangement tool according to the present invention.

[0037] Figure 3 for Figure 1 The bank application system shown in the figure is a flowchart of the maintenance process when the method for developing and maintaining a bank application system based on a process arrangement tool according to the present invention is applied. DETAILED DESCRIPTION

[0038] In order to clearly describe the present invention, it is further described with reference to the accompanying drawings.

[0039] like Figure 1 The figure shows a schematic diagram of the process arrangement of a banking application system during development. The process nodes include, in sequence: start, process 1, branch 2 judgment condition preparation, branch 2, branch 2 process 2.1 or branch 2 process 2.2, process 3, process 4, and end.

[0040] Figure 2 for Figure 1 The bank application system shown applies the method for developing and maintaining a bank application system based on a process orchestration tool described in the present invention. According to the field to which the application system belongs, a graphical process orchestration development tool is selected to draw an application system development flowchart.

[0041] According to the application system's field, select a graphical process orchestration development tool and use it to design the process:

[0042] Each process node is placed in the process lane, module code lane, and public service lane respectively.

[0043] like Figure 2 As shown in the figure, the nodes in the process lane are process orchestration nodes, which are used to complete process orchestration, including:

[0044] Business process judgment nodes (start, end), business process branch nodes (branch 2), business process combination nodes (process 1, branch 2 judgment condition preparation, branch 2 process 2.1, branch 2 process 2.2, process 3, process 4);

[0045] The business process judgment node is used to connect the business process branch node and / or the business process combination node;

[0046] Business process branch nodes and business process combination nodes have nodes of the module code lane or the public service lane corresponding to them: Process 1 corresponds to the Process 1 module code of the module code lane, Branch 2 judgment condition preparation corresponds to the Branch 2 judgment condition calculation module code of the module code lane, Branch 2 Process 2.1 corresponds to the Process 2.1 module code of the module code lane, Branch 2 Process 2.2 corresponds to the Process 2.2 module code of the module code lane, Process 4 corresponds to the Process 4 module code of the module code lane; Process 3 corresponds to Public Service 3 of the Public Service lane.

[0047] Each node in the module code lane has a corresponding node in the process lane (see above); each node in the module code lane is an internal interface, corresponding to a development subtask.

[0048] Each node in the public service lane has a corresponding node in the module code lane or process lane. The process 1 module code in the module code lane corresponds to public service 1 in the public service lane, and the process 2.1 module code and process 2.2 module code in the module code lane correspond to public service 2 in the public service lane.

[0049] According to the above method, a graphical process orchestration development tool is used to draw an application system development flow chart and archive it; then, based on the application system development flow chart, a new functional module is created for each process node.

[0050] The method for developing and maintaining a banking application system based on a process orchestration tool described in the present invention has mature process orchestration development tools for commonly used core systems and credit systems in the banking industry. After selecting the corresponding process orchestration development tool, when optimizing and upgrading the functional modules that have completed the process of the present invention, there is no need to read the design documents and obscure codes. Instead, one only needs to browse the graphical orchestration flowchart to quickly understand the design ideas of the previous developer or maintainer.

[0051] Compared with existing flowcharts, this method places each process node in the process lane, module code lane, and public service lane respectively, and graphically indicates the role of the process node in the entire process and its functional impact in the project.

[0052] Figure 3 for Figure 2 The flowchart shown is when the banking application system is maintained due to business process adjustments.

[0053] First, find the process nodes involved in this business process adjustment from the process lane according to the system development flowchart, and then find the process nodes corresponding to the process nodes involved in this business process adjustment from the module code lane and the public service lane (process 3 and public service 3 in the process lane);

[0054] Use the graphical process arrangement development tool, add the process 3 module code, redraw the application system development flow chart, and archive it;

[0055] Reconstruct the functional modules for the process nodes and corresponding module code lanes and / or public service lane process nodes involved in this business process adjustment.

[0056] When the business process is adjusted, each optimization and upgrade will involve the adjustment and development of the graphical process orchestration. This method makes it easy to find the process nodes that need to be adjusted and developed, to evaluate the workload and modification difficulty of this optimization, and to maintain the process level of the optimization work.

[0057] When the above-mentioned bank application system is developed and maintained, the method for developing and maintaining the bank application system based on the process orchestration tool described in the present invention can be used to classify developers according to their business capabilities, and only developers with high business capabilities can be assigned to participate in the development of functional modules corresponding to the process nodes of the process lane. Furthermore, the method essentially uses a graphical method to mark the importance level of each process node, and can classify developers according to the level of confidentiality agreements they sign and their business capabilities, and only developers with high business capabilities can be assigned to participate in the development of functional modules corresponding to the process nodes of the process lane, and feedback is given to the human resources department to supplement the signing of high-level confidentiality agreements by personnel who participate in the development of process nodes in the process lane. This method improves the reliability of the system and promotes the implementation of enterprise management standards.

[0058] When the above-mentioned banking application system is being developed and maintained, for the process nodes placed in the module code swimlane, the workload of the development subtasks corresponding to the process nodes is further evaluated, and the development subtasks are graded according to the evaluation results.

[0059] The development subtasks are divided into the following categories: the first category, the development subtasks have a development self-test workload of less than or equal to 2 working days; the second category, the development subtasks have a development self-test workload of more than 2 working days. In principle, it is prohibited to assign development subtasks that take more than 2 working days, which can reduce the system error rate.

[0060] When the above-mentioned banking application system is developed and maintained, for the process nodes placed in the module code lane, the workload of the development subtasks corresponding to the process nodes is further evaluated. When the workload is greater than the preset value, the process node is adjusted to the process lane.

[0061] When the above-mentioned banking application system is developed and maintained, for the process nodes placed in the module code swimlane, the importance of the development subtasks corresponding to the process nodes is further evaluated, and the development subtasks are graded according to the evaluation results.

[0062] When developing and maintaining the above banking application system, the development subtasks can be assigned to junior and intermediate developers according to the level. Because the scale of each internal interface code in the module code lane is relatively small and the code function is single, junior and intermediate developers can be fully utilized, reducing the impact of junior and intermediate developers' business capabilities on the overall system.

[0063] When developing and maintaining the above-mentioned banking application system, each node in the public service lane is graded according to the total number of corresponding process nodes to assess its importance.

[0064] When the above-mentioned banking application system is being developed and maintained, the functional modules corresponding to each node in the public service lane are assigned to developers of different levels according to the classification. This allocation method can make full use of the business capabilities of developers and reduce the impact of the business capabilities of junior and intermediate developers on the overall system.

[0065] By using the method of the present invention to regularly adjust the process planners and subtask developers of the functional modules, the system reliability can be effectively improved. If the project management specifications are adjusted and the review of the process outline design is added when the functional modules are newly built or reconstructed, the system reliability and ease of improvement can be significantly improved.

[0066] The method for developing and maintaining a banking application system based on a process orchestration tool described in the present invention can greatly improve the maintainability of application system development because the process node splitting granularity is fine enough, the scale of each internal interface code in the module code lane is relatively small, and the code function is single and easy to read.

[0067] It can be seen in the outline design diagram that if complex business branch judgments are involved and the process orchestration tool cannot support them and need to be implemented through coding, a branch judgment preparation node needs to be added to the process lane. The purpose of this process detail is to allow all business processes to be reflected in the process lane, to avoid the situation where some business process orchestrations are not reflected in the process lane due to tool limitations, which would pose a hidden danger to subsequent maintenance (this requirement can quickly determine whether the design complies with this plan, "Each node in the public service lane has a corresponding node in the module code lane or the process lane. Each node in the module code lane has a corresponding node in the process lane").

[0068] The present invention mainly relates to the correspondence between the outline design diagram and the process arrangement tool, as well as a simple method for checking whether the outline design diagram meets the requirements through the number of nodes.

Claims

1. A method for developing and maintaining a banking application system based on a process orchestration tool, characterized in that: The steps include: 1) Select a graphical process orchestration development tool based on the application system's field; 2) Use graphical process orchestration development tools to design processes: Place each process node in the process lane, module code lane, and public service lane respectively; The nodes in the process lane are process orchestration nodes, which are used to complete process orchestration, including: business process judgment nodes, business process branch nodes, and business process combination nodes; The business process judgment node is used to connect the business process branch node and / or the business process combination node; Business process branch nodes and business process combination nodes have corresponding nodes in the module code lane or public service lane; Each node in the module code lane has a corresponding node in the process lane; each node in the module code lane is an internal interface, corresponding to a development subtask; Each node in the public service lane has a corresponding node in the module code lane or process lane; 3) Use graphical process orchestration development tools to draw application system development flow charts and archive them; 4) Create new functional modules for each process node according to the application system development flowchart.

2. A method for developing and maintaining a banking application system based on a process orchestration tool as claimed in claim 1, characterized in that: When the business process is adjusted, find the process nodes involved in this business process adjustment from the process lane according to the system development process diagram, and then find the process nodes corresponding to the process nodes involved in this business process adjustment from the module code lane and the public service lane; Use graphical process orchestration development tools to redraw the application system development process diagram and archive it; Reconstruct the functional modules for the process nodes and corresponding module code lanes and / or public service lane process nodes involved in this business process adjustment.

3. A method for developing and maintaining a banking application system based on a process orchestration tool as claimed in claim 1, characterized in that: The method also includes grading developers according to their business capabilities and assigning only developers with high business capabilities to participate in the development of functional modules corresponding to process nodes in the process lane.

4. A method for developing and maintaining a banking application system based on a process orchestration tool as claimed in claim 1, characterized in that: For the process nodes placed in the module code swimlane, the workload of the development subtasks corresponding to the process nodes is further evaluated, and the development subtasks are graded based on the evaluation results.

5. A method for developing and maintaining a banking application system based on a process orchestration tool as claimed in claim 4, characterized in that: The grading of the development subtasks includes: the first level, the development self-test workload of the development subtask is less than or equal to 2 working days; the second level, the development self-test workload of the development subtask exceeds 2 working days.

6. A method for developing and maintaining a banking application system based on a process orchestration tool as claimed in claim 1, characterized in that: For the process nodes placed in the module code swimlane, the workload of the development subtasks corresponding to the process nodes is further evaluated. When the workload is greater than the preset value, the process node is adjusted to the process swimlane.

7. A method for developing and maintaining a banking application system based on a process orchestration tool as claimed in claim 1, characterized in that: For the process nodes placed in the module code swimlane, the importance of the development subtasks corresponding to the process nodes is further evaluated, and the development subtasks are graded based on the evaluation results.

8. A method for developing and maintaining a banking application system based on a process orchestration tool as described in claim 6 or 7, characterized in that: The development subtasks are assigned to junior and intermediate level developers based on their grades.

9. A method for developing and maintaining a banking application system based on a process orchestration tool as claimed in claim 1, characterized in that: Each node in the public service swim lane is graded according to the total number of corresponding process nodes to assess its importance.

10. A method for developing and maintaining a banking application system based on a process orchestration tool as claimed in claim 9, characterized in that: The functional modules corresponding to each node in the public service lane are assigned to developers of different levels for processing according to the classification.