A method and system for measuring the complexity of online transaction processing system

Abstract

The present invention provides a method and system for measuring the complexity of an online transaction processing system, which belongs to the field of financial information technology, and specifically comprises: based on the analysis results of transaction links of cross-system transactions, determining the transaction links between different application systems of different cross-system transactions, and determining the complex system transactions in the cross-system transactions in combination with the operation data of the application systems involved in the transaction links, determining the transaction processing complexity coefficients of different complex system transactions based on the call data of the transaction links between different application systems of different complex system transactions, acquiring the historical execution data of different complex system transactions, and combining the transaction processing complexity coefficients of different complex system transactions to measure the complexity of the online transaction processing system, and determining whether the complexity of the online transaction processing system meets the requirements through the measurement results, thereby improving the accuracy of the measurement results of the complexity of the online transaction processing system.

Description

Technical Field

[0001] The present invention belongs to the field of financial information technology, and in particular relates to a method and system for measuring the complexity of an online transaction processing system. Background Art

[0002] Enterprise-level OLTP (On-Line Transaction Processing, a data processing system tailored for real-time transaction operations and daily operational tasks) systems are inherently complex. Especially as the scale of the enterprise expands, the business scale expands, and the duration of existence is prolonged, the continuous accumulation of various system iterations makes the disorder of enterprise-level IT architecture continue to expand and the cost continues to increase.

[0003] In order to reduce the complexity of the business system, in the invention patent application CN202111551414.X "A system architecture with multiplexing function", the upstream system is connected through an adapter, the access implementation logic of the upstream system is independently and isolated, and the plug-and-play target effect is effectively achieved, avoiding the upstream system technology framework and logic from being deeply embedded in the system. However, there are the following technical problems:

[0004] The existing technical solutions ignore the evaluation of the complexity of the online transaction system based on the analysis results of the transaction data of different atomic business transactions, making it difficult to generate differentiated complexity processing strategies for different atomic business transactions in a targeted manner, and to improve the processing efficiency and reliability of atomic business transactions without changing the system architecture on a large scale.

[0005] In view of the above technical problems, the present invention provides a method and system for measuring the complexity of an online transaction processing system. Summary of the invention

[0006] To achieve the purpose of the present invention, the present invention adopts the following technical solutions:

[0007] According to one aspect of the present invention, a method for measuring the complexity of an online transaction processing system is provided.

[0008] A method for measuring the complexity of an online transaction processing system, specifically comprising:

[0009] S1: Decomposing the business architecture of the online transaction processing system to obtain multiple business transactions, determining the cross-application system business transactions according to the decomposition results of the application architecture of the business transactions, treating them as cross-system transactions, and determining through the call data of the cross-system transactions that the processing complexity of the online transaction processing system meets the requirements, then proceeding to the next step;

[0010] S2 determines the transaction links of different cross-system transactions between different application systems based on the analysis results of the transaction links of the cross-system transactions, and determines the complex system transactions in the cross-system transactions in combination with the operation data of the application systems involved in the transaction links;

[0011] S3 determines the transaction processing complexity coefficients of different complex system transactions based on the call data of the transaction links between different application systems;

[0012] S4 obtains historical execution data of different complex system transactions, and combines the transaction processing complexity coefficients of different complex system transactions to measure the complexity of the online transaction processing system, and determines whether the complexity of the online transaction processing system meets the requirements through the measurement results.

[0013] A further technical solution is that the application system includes a credit information acquisition system, a credit information analysis system, a credit risk analysis system, a lending system and a credit monitoring system.

[0014] A further technical solution is that the call data includes the number of calls and the call times corresponding to different number of calls.

[0015] A further technical solution is to determine whether the processing complexity of the online transaction processing system meets the requirements, specifically including:

[0016] Based on the call data of the cross-system transaction of the online transaction processing system, determining the call times of different cross-system transactions and the call times corresponding to the different call times;

[0017] Determine the average daily call times of different cross-system transactions based on the call times corresponding to the different call times, and determine the call busy coefficient of the cross-system transaction using the average daily call times;

[0018] The busy system transactions are determined based on the calling busy coefficients of different cross-system transactions, and the number of the busy system transactions is used to determine whether the processing complexity of the online transaction processing system meets the requirements.

[0019] A further technical solution is that when the number of the busy system transactions is greater than a preset number of transactions, it is determined that the processing complexity of the online transaction processing system does not meet the requirements.

[0020] A further technical solution is to determine whether the complexity of the online transaction processing system meets the requirements through the measurement results, which specifically includes:

[0021] When the measurement result is not within the preset complexity range, it is determined that the complexity of the online transaction processing system meets the requirement.

[0022] In a second aspect, the present invention provides a computer system comprising: a memory and a processor that are communicatively connected, and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the above-mentioned method for measuring the complexity of an online transaction processing system when running the computer program.

[0023] The beneficial effects of the present invention are:

[0024] 1. In the present invention, complex system transactions in cross-system transactions are determined through transaction links between different application systems and operation data of application systems involved in the transaction links, thereby avoiding the technical problem of high complexity of measurement processing caused by complexity measurement based on all system transactions in cross-system transactions, realizing the screening of cross-system transactions with high complexity in online transaction systems, and laying a foundation for improving the reliability of complexity identification processing on the basis of ensuring the efficiency of identification processing of complexity measurement results of online transaction processing systems.

[0025] 2. In the present invention, the complexity of the online transaction processing system is measured by using the historical execution data of different complex system transactions and combining the transaction processing complexity coefficients of different complex system transactions. This not only takes into account the differences in the complexity of transaction processing of different complex system transactions due to the number of links and the number of application systems involved, but also takes into account the differences in the historical number of executions of complex system transactions and the frequency of executions. This achieves accurate measurement of the complexity of the online transaction processing system from multiple angles, and also lays a foundation for judging whether the complexity of the online transaction system meets the requirements.

[0026] Other features and advantages will be described in the following description. The objects and other advantages of the present invention are realized and obtained by the structures particularly pointed out in the description and drawings.

[0027] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] The above and other features and advantages of the present invention will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings.

[0029] Figure 1 is a flow chart of a method for measuring the complexity of an online transaction processing system;

[0030] Figure 2 is a flow chart of a method for determining that the processing complexity of an online transaction processing system meets requirements;

[0031] Figure 3 It is a flowchart of the method of determining complex system transactions in cross-system transactions;

[0032] Figure 4 It is a flow chart of a method for determining a transaction processing complexity coefficient of a complex system transaction;

[0033] Figure 5 The invention is a flow chart of a method for determining a measurement result of complexity of an online transaction processing system. DETAILED DESCRIPTION

[0034] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this specification.

[0035] Enterprise-level OLAP systems are characterized by large scale, high complexity, large data volume, and high cost. With the development of enterprise business and the extension of duration, disorder and cost will increase significantly. The present invention proposes a model, method and system for measuring the complexity of the overall enterprise-level online analytical processing system. By modeling, measuring and observing the complexity of the enterprise and OLAP system, accurate and rapid adjustment of disorder can be achieved, thereby continuously reducing the overall scientific and technological costs of the enterprise.

[0036] Determine whether the processing complexity of the online transaction processing system meets the requirements: the cross-system transactions with an average daily call frequency of more than 1,000 times are regarded as busy system transactions, and the number of busy system transactions is used to determine whether the processing complexity of the online transaction processing system meets the requirements. Specifically, when the number of busy system transactions is less than 3, it is determined that the processing complexity of the online transaction processing system meets the requirements.

[0037] Complex system transactions: The application systems involved in cross-system transactions are regarded as associated application systems. The busy application systems of cross-system transactions are determined according to the idle time ratio of the associated application systems. Specifically, the idle time ratio less than 0.3 is regarded as the busy application coefficient. When the number of busy application systems is more than 4, the system transaction is determined to be a complex system transaction.

[0038] Transaction processing complexity coefficient of complex system transactions: The frequently called links in the associated transaction links are determined by the number of calls. Specifically, the links with more than 500 calls are regarded as frequently called links, and the transaction processing complexity coefficient of complex system transactions is determined by the number of frequently called links.

[0039] The measurement results of the complexity of online transaction processing systems:

[0040] The measurement of system complexity mainly includes the following steps:

[0041] 1. Disassemble the enterprise data architecture to determine the transaction system data model;

[0042] 2. Determine the source model and derived processing model of the analysis system;

[0043] 3. Classify the data flow from one model to another to form a standard processing classification table;

[0044] 4. Adjust the coefficient of standard processing according to the actual environment of the enterprise architecture;

[0045] 5. Collect the flow information of the enterprise-level system data persistence layer during the window period, and map it into standard processing according to classification;

[0046] 6. Measure variables such as data volume, standard processing time, and model size.

[0047] Embodiment 1 To solve the above problem, according to one aspect of the present invention, Figure 1 As shown, a method for measuring the complexity of an online transaction processing system is provided, which specifically includes:

[0048] S1: Decomposing the business architecture of the online transaction processing system to obtain multiple business transactions, determining the cross-application system business transactions according to the decomposition results of the application architecture of the business transactions, treating them as cross-system transactions, and determining through the call data of the cross-system transactions that the processing complexity of the online transaction processing system meets the requirements, then proceeding to the next step;

[0049] S2 determines the transaction links of different cross-system transactions between different application systems based on the analysis results of the transaction links of the cross-system transactions, and determines the complex system transactions in the cross-system transactions in combination with the operation data of the application systems involved in the transaction links;

[0050] S3 determines the transaction processing complexity coefficients of different complex system transactions based on the call data of the transaction links between different application systems;

[0051] S4 obtains historical execution data of different complex system transactions, and combines the transaction processing complexity coefficients of different complex system transactions to measure the complexity of the online transaction processing system, and determines whether the complexity of the online transaction processing system meets the requirements through the measurement results.

[0052] Furthermore, the application system includes a credit information acquisition system, a credit information analysis system, a credit risk analysis system, a lending system and a credit monitoring system.

[0053] Optionally, the call data includes the number of calls and the call times corresponding to different number of calls.

[0054] Specifically, Figure 2 As shown, determining that the processing complexity of the online transaction processing system meets the requirements specifically includes:

[0055] Based on the call data of the cross-system transaction of the online transaction processing system, determining the call times of different cross-system transactions and the call times corresponding to the different call times;

[0056] Determine the average daily call times of different cross-system transactions based on the call times corresponding to the different call times, and determine the call busy coefficient of the cross-system transaction using the average daily call times;

[0057] The busy system transactions are determined based on the calling busy coefficients of different cross-system transactions, and the number of the busy system transactions is used to determine whether the processing complexity of the online transaction processing system meets the requirements.

[0058] Further, when the number of the busy system transactions is greater than a preset number of transactions, it is determined that the processing complexity of the online transaction processing system does not meet the requirement.

[0059] It should also be noted that determining that the processing complexity of the online transaction processing system meets the requirements specifically includes:

[0060] Based on the call data of the cross-system transaction of the online transaction processing system, determining the call times of different cross-system transactions and the call times corresponding to the different call times;

[0061] Determine the call times of different cross-system transactions on different dates based on the call times corresponding to the different call times, and determine the busy call dates among the dates using the call times on the different dates;

[0062] Whether the processing complexity of the online transaction processing system meets the requirements is determined based on the date quantity ratio of the busy call dates.

[0063] It is understandable that when the proportion of the number of busy call dates is not within the preset range of the number of dates, it is determined that the processing complexity of the online transaction processing system does not meet the requirements.

[0064] Optionally, determining whether the processing complexity of the online transaction processing system meets the requirements includes steps S11-S14, specifically:

[0065] S11 determines the calling times of different cross-system transactions and the calling times corresponding to the different calling times based on the calling data of the cross-system transactions of the online transaction processing system;

[0066] S12 determines the average daily call times of different cross-system transactions based on the call times corresponding to the different call times, and determines the call busy coefficients of the cross-system transactions using the average daily call times, and determines the busy system transactions based on the call busy coefficients of the different cross-system transactions;

[0067] S13 determines the call times of different cross-system transactions on different dates based on the call times corresponding to the different call times, and determines the busy call dates among the dates by using the call times on the different dates;

[0068] S14 determines the processing complexity coefficient of the online transaction processing system by using the number of busy system transactions and the number of busy call dates, and determines whether the processing complexity of the online transaction processing system meets the requirements according to the processing load coefficient.

[0069] Furthermore, the transaction link between the application systems is determined according to the data transmission status of the application systems in the cross-system transaction.

[0070] It should be noted that if Figure 3 As shown, the method for determining the complex system transaction in the cross-system transaction is:

[0071] Based on the transaction links between different application systems of the cross-system transaction, the application systems involved in the cross-system transaction are determined and used as associated application systems;

[0072] Based on the operation data of the application systems involved in the transaction link, determining the idle time proportions of different associated application systems, and determining the idle coefficients of different associated application systems according to the idle time proportions;

[0073] The busy application systems of the cross-system transaction are determined by the idle coefficients of different associated application systems, and whether the cross-system transaction is a complex system transaction is determined based on the number of the busy application systems.

[0074] It should be noted that when the number of busy application systems of the cross-system transaction is greater than the preset number of systems, the cross-system transaction is determined to be a complex system transaction.

[0075] Furthermore, the busy application system is an associated application system whose idle coefficient is less than a preset idle coefficient.

[0076] It should also be noted that the method for determining the complex system transaction in the cross-system transaction is:

[0077] Based on the transaction links between different application systems of the cross-system transaction, the application systems involved in the cross-system transaction are determined and used as associated application systems;

[0078] Based on the operation data of the application systems involved in the transaction link, determining the idle time proportions of different associated application systems, and determining the idle coefficients of different associated application systems according to the idle time proportions;

[0079] The system idle coefficient of the cross-system transaction is determined by the idle coefficients of different associated application systems and the number of associated application systems, and whether the cross-system transaction is a complex system transaction is determined based on the system idle coefficient.

[0080] Optionally, the method for determining the complex system transaction in the cross-system transaction includes steps S21-S23, specifically:

[0081] Optionally, before entering step S21, it is also necessary to determine whether the number of transaction links of the cross-system transaction and the number of associated application systems are both within the preset system quantity range. When the number of transaction links of the cross-system transaction and the number of associated application systems are both within the preset system quantity range, it is determined that the cross-system transaction does not belong to a complex system transaction.

[0082] S21 determines the number of transaction links between different application systems of the cross-system transaction based on the transaction links, and determines the link complexity coefficient in the cross-system transaction according to the number of transaction links and the application systems corresponding to different transaction links;

[0083] Optionally, the above step S21 includes steps S211-S213, which are specifically:

[0084] S211 determines the number of transaction links of the cross-system transaction between different application systems based on the transaction links of the cross-system transaction. When the number of transaction links of the cross-system transaction is not within a preset number range, the cross-system transaction is determined to be a complex system transaction. When the number of transaction links of the cross-system transaction is within the preset number range, the process proceeds to step S212.

[0085] S212 determines the number of transaction links of different application systems based on the transaction links between different application systems. When the number of transaction links is greater than the preset number of links and the number of application systems is greater than the preset number of application systems, it is determined that the cross-system transaction is a complex system transaction. When the number of transaction links is greater than the preset number of links and the number of application systems is not greater than the preset number of application systems, the process proceeds to step S213.

[0086] S213 determines the link complexity coefficient in the cross-system transaction through the number of transaction links and the application systems corresponding to different transaction links. When the link complexity coefficient of the cross-system transaction does not meet the requirements, the cross-system transaction is determined to be a complex system transaction. When the link complexity coefficient of the cross-system transaction meets the requirements, proceed to step S22.

[0087] S22 determines the application systems involved in the cross-system transaction and uses them as associated application systems, and determines the application system complexity coefficient of the cross-system transaction in combination with the idle time ratios of different associated application systems;

[0088] Optionally, the above step S22 includes steps S221-S223, specifically:

[0089] S221 determines the application systems involved in the cross-system transaction and uses them as associated application systems. When the number of associated application systems is greater than a preset threshold of the number of associated systems, the cross-system transaction is determined to be a complex system transaction. When the number of associated application systems is not greater than the preset threshold of the number of associated systems, the process proceeds to step S222;

[0090] S222 determines the idle time proportions of different associated application systems based on the operation data of different associated application systems. When the number of associated application systems whose idle time proportions are less than the preset proportions does not meet the requirement, the cross-system transaction is determined to be a complex system transaction. When the number of associated application systems whose idle time proportions are less than the preset proportions meets the requirement, the process proceeds to step S223.

[0091] S223 determines the application system complexity coefficient of the cross-system transaction based on the number of associated application systems and the proportion of idle time of different associated application systems. When the application system complexity coefficient of the cross-system transaction does not meet the requirements, the cross-system transaction is determined to be a complex system transaction. When the application system complexity coefficient of the cross-system transaction meets the requirements, proceed to step S23.

[0092] S23 determines the system complexity coefficient of the cross-system transaction based on the application system complexity coefficient and the link complexity coefficient, and determines whether the cross-system transaction is a complex system transaction based on the system complexity coefficient.

[0093] Further, such as Figure 4 As shown, the method for determining the transaction processing complexity coefficient of the complex system transaction is:

[0094] Using the transaction links between different application systems of the complex system transaction as associated transaction links;

[0095] Based on the call data of different associated transaction links, the call times of different associated transaction links are determined, and the frequently called links in the associated transaction links are determined according to the call times;

[0096] The transaction processing complexity coefficient of the complex system transaction is determined by the number of the frequently called links.

[0097] It should be noted that the transaction processing complexity coefficient of the complex system transaction is determined by the number of the frequently called links, specifically including:

[0098] Based on the number of the frequently called links and the preset proportional factor, the transaction processing complexity coefficient of the complex system transaction is determined.

[0099] It can be understood that the frequently called link is an associated transaction link whose number of calls is greater than the limit value of the number of calls.

[0100] It should also be noted that the historical execution data includes the historical execution times of complex system transactions and the execution frequencies in different time periods.

[0101] Specifically, Figure 5 As shown, the method for determining the measurement result of the complexity of the online transaction processing system is:

[0102] Based on the historical execution data of different complex system transactions, determine the historical execution times of different complex system transactions and the execution frequencies in different time periods;

[0103] The execution frequency in different time periods is used to determine the time period with an execution frequency greater than the preset execution frequency, and the time period is used as the frequent execution time period. The preset frequency coefficients of different complex system transactions are determined by the proportion of the number of frequent execution time periods.

[0104] Determine preset weight coefficients of different complex system transactions corresponding to the historical execution times according to the historical execution times of different complex system transactions, and determine system weight coefficients of different complex transaction systems based on the average value of the preset weight coefficients and the preset frequency coefficients;

[0105] The measurement result of the complexity of the online transaction processing system is determined by using system weight coefficients and transaction processing complexity coefficients of different complex system transactions.

[0106] Furthermore, the complexity measurement result of the online transaction processing system is determined by using the system weight coefficients and transaction processing complexity coefficients of different complex system transactions, specifically including:

[0107] The sum of the products of system weight coefficients of transactions of different complex systems and transaction processing complexity coefficients is used as the measurement result of the complexity of the online transaction processing system.

[0108] It can be understood that determining whether the complexity of the online transaction processing system meets the requirements through the measurement results specifically includes:

[0109] When the measurement result is not within the preset complexity range, it is determined that the complexity of the online transaction processing system meets the requirement.

[0110] In another specific embodiment:

[0111] Optionally, the above step S12 includes steps S121-S123, specifically:

[0112] S121 obtains the number of cross-system transactions. When the number of cross-system transactions is greater than the preset cross-system transaction number threshold, the process proceeds to step S122. When the number of cross-system transactions is not greater than the preset cross-system transaction number threshold, the process proceeds to step S123.

[0113] S122 determines the average daily call times of different cross-system transactions based on the call times corresponding to the different call times. When the average daily call times of different cross-system transactions are all greater than the preset number threshold, it is determined that the processing complexity of the online transaction processing system does not meet the requirements. When there is a cross-system transaction with an average daily call time not greater than the preset number threshold, the process proceeds to step S123.

[0114] S123 uses the average daily number of calls to determine the call busy coefficient of the cross-system transaction, and determines the busy system transaction based on different call busy coefficients of cross-system transactions. When the number of busy system transactions does not meet the requirements, it is determined that the processing complexity of the online transaction processing system does not meet the requirements. When the number of busy system transactions meets the requirements, it proceeds to step S13.

[0115] Optionally, the above step S13 includes steps S131-S133, specifically:

[0116] S131 determines the call times of different cross-system transactions on different dates based on the call times corresponding to the different call times. When the total call times on different dates are greater than the preset call times threshold, it is determined that the processing complexity of the online transaction processing system does not meet the requirements. When there is a date with a total call times not greater than the preset call times threshold, it proceeds to step S132.

[0117] S132 determines the busy call date among the dates by using the number of calls on different dates. When the number of busy call dates does not meet the requirement, it is determined that the processing complexity of the online transaction processing system does not meet the requirement. When the number of busy call dates does meet the requirement, the process proceeds to step S133.

[0118] S133 determines the comprehensive call busy coefficient based on the proportion of the number of different busy call dates and the number of calls of different cross-system transactions corresponding to different busy call dates. When the comprehensive call busy coefficient does not meet the requirements, it is determined that the processing complexity of the online transaction processing system does not meet the requirements. When the comprehensive call busy coefficient meets the requirements, it proceeds to step S14.

[0119] Embodiment 2 In a second aspect, the present invention provides a computer system, comprising: a memory and a processor that are communicatively connected, and a computer program stored in the memory and executable on the processor, wherein the processor executes the above-mentioned method for measuring the complexity of an online transaction processing system when executing the computer program.

[0120] Optionally, the method for determining the transaction processing complexity coefficient of the complex system transaction includes steps S31-S33, specifically:

[0121] S31: taking the transaction link of the complex system transaction between different application systems as an associated transaction link;

[0122] S32: determining the call times of different associated transaction links based on the call data of different associated transaction links, and determining the link call frequency coefficient of the associated transaction link through the call times and the call processing time of different call times;

[0123] S33 determines the transaction processing complexity coefficient of the complex system transaction through the link call frequency coefficients of different associated transaction links.

[0124] Optionally, before entering step S32, it is also necessary to determine whether the number of associated transaction links of the complex system transaction is greater than the preset number of associated links. When the number of associated transaction links of the complex system transaction is not greater than the preset number of associated links, the preset processing complexity coefficient is used to determine the transaction processing complexity coefficient of the complex system transaction. When the number of associated transaction links of the complex system transaction is greater than the preset number of associated links, proceed to step S32.

[0125] Optionally, the above step S32 includes steps S321-S323, specifically:

[0126] S321 determines the call times of different associated transaction links based on the call data of different associated transaction links, and determines the total call times based on the call times of different associated transaction links. When the total call times is less than the minimum call times limit value, the process proceeds to step S322; when the total call times is not less than the minimum call times limit value, the process proceeds to step S323;

[0127] S322: when it is determined based on the call times of different associated transaction links that there is no associated transaction link whose call times are greater than the preset link call times, the transaction processing complexity coefficient of the complex system transaction is determined using the preset processing complexity coefficient; when there is an associated transaction link whose call times are greater than the preset link call times, the process proceeds to step S323;

[0128] S323 determines the link call frequency coefficient of the associated transaction link through the number of calls and the call processing time of different call numbers. When there is no associated transaction link whose link call frequency coefficient is greater than the preset call frequency coefficient threshold, the preset processing complexity coefficient is used to determine the transaction processing complexity coefficient of the complex system transaction. When there is an associated transaction link whose link call frequency coefficient is greater than the preset call frequency coefficient threshold, proceed to step S33.

[0129] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, equipment, and non-volatile computer storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0130] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0131] The above description is only one or more embodiments of this specification and is not intended to limit this specification. For those skilled in the art, one or more embodiments of this specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of this specification shall be included in the scope of the claims of this specification.

Claims

1. A method for measuring the complexity of an online transaction processing system, characterized in that: Specifically include: The business architecture of the online transaction processing system is disassembled to obtain multiple business transactions, and the cross-application system business transactions are determined according to the disassembly results of the application architecture of the business transactions, and the cross-system transactions are regarded as cross-system transactions. When it is determined through the call data of the cross-system transactions that the processing complexity of the online transaction processing system meets the requirements, the next step is entered; Based on the analysis results of the transaction links of the cross-system transactions, the transaction links of different cross-system transactions between different application systems are determined, and the complex system transactions in the cross-system transactions are determined in combination with the operation data of the application systems involved in the transaction links; Determine the transaction processing complexity coefficients of different complex system transactions by using the call data of the transaction links between different application systems; Acquire historical execution data of different complex system transactions, and determine the measurement results of the processing complexity of the online transaction processing system in combination with the transaction processing complexity coefficients of the different complex system transactions, and determine whether the processing complexity of the online transaction processing system meets the requirements through the measurement results; The method for determining the transaction processing complexity coefficient of the complex system transaction is: Using the transaction links between different application systems of the complex system transaction as associated transaction links; Based on the call data of different associated transaction links, the call times of different associated transaction links are determined, and the frequently called links in the associated transaction links are determined according to the call times; The transaction processing complexity coefficient of the complex system transaction is determined by the number of the frequently called links.

2. The method for measuring the complexity of an online transaction processing system according to claim 1, characterized in that: The application system includes a credit information acquisition system, a credit information analysis system, a credit risk analysis system, a lending system and a credit monitoring system.

3. The method for measuring the complexity of an online transaction processing system according to claim 1, characterized in that: The call data includes the number of calls and the call times corresponding to different call numbers.

4. The method for measuring the complexity of an online transaction processing system according to claim 1, characterized in that: Determining that the processing complexity of the online transaction processing system meets the requirements, specifically including: Based on the call data of the cross-system transaction of the online transaction processing system, determining the call times of different cross-system transactions and the call times corresponding to the different call times; Determine the call times of different cross-system transactions on different dates based on the call times corresponding to the different call times, and determine the busy call dates among the dates using the call times on the different dates; Whether the processing complexity of the online transaction processing system meets the requirements is determined based on the date quantity ratio of the busy call dates.

5. The method for measuring the complexity of an online transaction processing system according to claim 4, characterized in that: When the proportion of the number of busy call dates is not within a preset range of the number of date proportions, it is determined that the processing complexity of the online transaction processing system does not meet the requirements.

6. The method for measuring the complexity of an online transaction processing system according to claim 1, characterized in that: The transaction link between the application systems is determined according to the data transmission status of the application systems in the cross-system transaction.

7. The method for measuring the complexity of an online transaction processing system according to claim 1, characterized in that: The method for determining the complex system transaction in the cross-system transaction is: Based on the transaction links between different application systems of the cross-system transaction, the application systems involved in the cross-system transaction are determined and used as associated application systems; Based on the operation data of the application systems involved in the transaction link, determining the idle time proportions of different associated application systems, and determining the idle coefficients of different associated application systems according to the idle time proportions; The busy application systems of the cross-system transaction are determined by the idle coefficients of different associated application systems, and whether the cross-system transaction is a complex system transaction is determined based on the number of the busy application systems.

8. The method for measuring the complexity of an online transaction processing system according to claim 7, characterized in that: The busy application system is an associated application system whose idle coefficient is less than a preset idle coefficient.

9. The method for measuring the complexity of an online transaction processing system according to claim 1, characterized in that: Determining whether the processing complexity of the online transaction processing system meets the requirements through the measurement results specifically includes: When the measurement result is not within the preset complexity range, it is determined that the processing complexity of the online transaction processing system meets the requirements.

10. A computer system comprising: A memory and a processor in communication connection, and a computer program stored in the memory and capable of running on the processor, characterized in that: when the processor runs the computer program, a method for measuring the complexity of an online transaction processing system as described in any one of claims 1 to 9 is executed.

Images