Management method and device of legacy system and storage medium

By generating code analysis diagrams and data correlation analysis diagrams, creating business living documents and dependency analysis diagrams, the problem of exception handling difficulties in legacy systems is solved, rapid positioning and processing is achieved, and user experience is improved.

CN119025317APending Publication Date: 2024-11-26PICC LIFE INSURANCE CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411109876.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-13
Publication Date
2024-11-26

Smart Images

  • Figure CN119025317A_ABST
    Figure CN119025317A_ABST
Patent Text Reader

Abstract

The invention discloses a legacy system management method and device and a storage medium, and the method comprises the steps: generating a code analysis chart and a data association analysis chart of a legacy system; based on the code analysis chart and the data association analysis chart, generating a service live document and a dependency analysis chart of the legacy system; obtaining abnormal information of the legacy system; and performing exception analysis on the exception information based on the business live document and the dependency analysis chart, and processing the exception information based on an obtained exception analysis result. Therefore, the target code module and the database information associated with the abnormal information are quickly positioned through the business live document and the dependency analysis chart, so that business personnel can process the abnormity of the legacy system in time, the legacy system continues to provide service for a user, and the user experience is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a management method, device and storage medium for a legacy system. Background Art

[0002] Legacy systems usually refer to computer systems or applications that are technically outdated but need to be maintained in the enterprise. When business personnel maintain legacy systems, the business functions are unclear and the relationship between code modules is unclear. When business personnel handle exceptions in legacy systems, they need to invest a lot of energy to sort out the relationships and logic in the legacy systems, which results in the inability to handle exceptions in the legacy systems in a timely manner, making it impossible for the legacy systems to provide services to users and resulting in poor user experience. Summary of the invention

[0003] The present invention provides a method and device for managing a legacy system, so as to at least solve the above technical problems in the prior art.

[0004] To this end, the present invention proposes a management method for legacy systems, which can quickly locate the target code modules and database information associated with the exception information through business live documents and dependency analysis diagrams, so that business personnel can handle the exceptions of the legacy system in a timely manner, thereby allowing the legacy system to continue to provide services to users, thereby improving the user experience.

[0005] Another object of the present invention is to provide a management device for a legacy system.

[0006] To achieve the above object, the present invention provides a method for managing a legacy system, the method comprising:

[0007] Generate a code analysis diagram and a data association analysis diagram of the legacy system;

[0008] Based on the code analysis diagram and the data association analysis diagram, generating a business living document and a dependency analysis diagram of the legacy system;

[0009] Obtaining abnormal information of the legacy system;

[0010] The exception information is analyzed based on the business activity document and the dependency analysis diagram, and the exception information is processed based on the obtained exception analysis result.

[0011] The legacy system management method of the embodiment of the present invention may also have the following additional technical features:

[0012] In one embodiment of the present invention, the generating of the code analysis graph and the data association analysis graph of the legacy system includes:

[0013] Performing syntax analysis on the source code of the legacy system and constructing a corresponding abstract syntax tree;

[0014] Based on the abstract syntax tree, generating an initial code structure diagram of the legacy system;

[0015] Generate a code analysis diagram of the legacy system based on the abstract syntax tree and the initial code structure diagram;

[0016] Obtaining a database configuration file of the legacy system;

[0017] Based on the database configuration file, a data association analysis diagram of the legacy system is generated.

[0018] In one embodiment of the present invention, generating the business living document and dependency analysis diagram of the legacy system based on the code analysis diagram and the data association analysis diagram includes:

[0019] Extracting entities in the code analysis graph;

[0020] Determine the association relationship of entities in the code analysis graph;

[0021] Based on the entities and association relationships in the code analysis diagram, and the data association analysis diagram, a business living document and a dependency analysis diagram of the legacy system are generated.

[0022] In one embodiment of the present invention, performing an exception analysis on the exception information based on the business activity document and the dependency analysis graph, and processing the exception information based on the obtained exception analysis result, includes:

[0023] Analyze the exception information based on the dependency analysis graph to obtain an associated target code module set;

[0024] Based on the business activity document, determine database information that interacts with the target code module set;

[0025] Reproducing the abnormal information based on the target code module set and the database information to obtain an abnormal analysis result;

[0026] The target code module set is modified based on the obtained exception analysis result to process the exception information.

[0027] In one embodiment of the present invention, the exception information includes an exception type, an error code, and a timestamp; the analyzing the exception information based on the dependency analysis graph to obtain an associated target code module set includes:

[0028] Based on the exception type, determining a first code module set of the exception information;

[0029] Based on the dependency analysis graph, determine the external modules associated with the first code module set to obtain a second code module set;

[0030] The second code module set is analyzed based on the error code and the timestamp to obtain an associated target code module set.

[0031] In one embodiment of the present invention, the target code module set is modified based on the obtained exception analysis result to process the exception information, including:

[0032] Modifying the target code module set based on the obtained abnormal analysis results, and performing regression testing on the modified code module set;

[0033] If the regression test is passed, the processing of the abnormal information is completed.

[0034] In one embodiment of the present invention, the method further comprises: updating the business living documents and dependency analysis diagram of the legacy system based on the modified code module set.

[0035] To achieve the above object, the present invention provides a management device for a legacy system, the device comprising:

[0036] A first generating module, used to generate a code analysis diagram and a data association analysis diagram of the legacy system;

[0037] A second generating module is used to generate a business living document and a dependency analysis diagram of the legacy system based on the code analysis diagram and the data association analysis diagram;

[0038] An acquisition module, used for acquiring abnormal information of the legacy system;

[0039] A processing module is used to perform an exception analysis on the exception information based on the business activity document and the dependency analysis diagram, and process the exception information based on the obtained exception analysis result.

[0040] Another object of the present invention is to provide an electronic device, comprising:

[0041] at least one processor; and

[0042] a memory communicatively connected to the at least one processor; wherein,

[0043] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform any one of the methods described in the above aspect.

[0044] Another object of the present invention is to provide a computer storage medium, wherein the computer storage medium stores computer executable instructions; after the computer executable instructions are executed by a processor, the computer executes any one of the methods described in the above aspect.

[0045] The management method, device and storage medium of the legacy system of the embodiment of the present invention generate a code analysis diagram and a data association analysis diagram of the legacy system; based on the code analysis diagram and the data association analysis diagram, generate a business active document and a dependency analysis diagram of the legacy system; obtain the abnormal information of the legacy system; perform an abnormal analysis on the abnormal information based on the business active document and the dependency analysis diagram, and process the abnormal information based on the obtained abnormal analysis result. Therefore, the present invention can quickly locate the target code module and database information associated with the abnormal information through the business active document and the dependency analysis diagram, so that the business personnel can promptly process the abnormalities of the legacy system, thereby allowing the legacy system to continue to provide services to users, thereby improving the user experience.

[0046] Additional aspects and advantages of the present invention will be given in part in the following description and in part will be obvious from the following description, or will be learned through practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] The above and / or additional aspects and advantages of the present invention will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0048] Figure 1 is a flow chart of a method for managing a legacy system according to an embodiment of the present invention;

[0049] Figure 2 4 is a structural diagram of a management device for a legacy system according to an embodiment of the present invention. DETAILED DESCRIPTION

[0050] It should be noted that, in the absence of conflict, the embodiments of the present invention and the features in the embodiments can be combined with each other. The present invention will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0051] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme 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 only 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 should fall within the scope of protection of the present invention.

[0052] The following describes a method and apparatus for managing a legacy system according to an embodiment of the present invention with reference to the accompanying drawings.

[0053] Figure 1 The figure is a flowchart of a method for managing a legacy system according to an embodiment of the present invention.

[0054] like Figure 1 As shown, the method includes:

[0055] S1, generate code analysis diagram and data association analysis diagram of the legacy system;

[0056] In one embodiment of the present invention, the execution subject of the above-mentioned legacy system management method is a legacy system management device, which can be implemented by software and / or hardware, and the legacy system management device in this embodiment can be configured in an electronic device. In this example embodiment, the electronic device can include devices such as terminal devices and servers, and this embodiment does not limit the electronic device.

[0057] In one embodiment of the present invention, the method for generating a code analysis diagram and a data association analysis diagram of a legacy system may include the following steps:

[0058] S11, perform syntax analysis on the source code of the legacy system and construct the corresponding abstract syntax tree;

[0059] S12, based on the abstract syntax tree, generates the initial code structure diagram of the legacy system;

[0060] S13, generating a code analysis diagram of the legacy system based on the abstract syntax tree and the initial code structure diagram;

[0061] S14, obtaining a database configuration file of the legacy system;

[0062] S15, generating a data association analysis diagram of the legacy system based on the database configuration file.

[0063] In one embodiment of the present invention, the source code of the legacy system can be parsed by a compiler to construct a corresponding abstract syntax tree (AST). The compiler can be ANTLR or Roslyn.

[0064] In one embodiment of the present invention, the AST may be a tree data structure for representing the syntax structure of the source code, such as classes, methods, variables, and expressions. Also, in one embodiment of the present invention, the entities and their relationships in the code may be extracted by traversing the AST to generate an initial code structure diagram of the legacy system.

[0065] Furthermore, in one embodiment of the present invention, a control flow graph (CFG) can be constructed based on the above AST to represent the execution path and conditional branches in the code. Also, in one embodiment of the present invention, code entities (such as classes, methods, variables, etc.) are extracted from the initial code structure diagram and CFG, and the association relationships between entities (such as inheritance, implementation, and call) are analyzed, and a code analysis diagram of the legacy system is generated based on the entities and the association relationships.

[0066] Furthermore, in one embodiment of the present invention, the method for generating a data association analysis diagram of a legacy system based on the database configuration file may include the following steps:

[0067] Step 1: Extract the database string from the database configuration file to obtain data information;

[0068] Step 2: Access the corresponding database based on the data information to obtain the first association relationship between the data tables in the database;

[0069] Step 3: Parse the SQL statements in the source code of the legacy system to obtain the second association relationship between the SQL statements;

[0070] Step 4: Generate a data association analysis diagram of the legacy system based on the first association relationship and the second association relationship.

[0071] In one embodiment of the present invention, the database string may include a database type, a host name, a port number, a user name and a password. Also, in one embodiment of the present invention, the second association relationship may include a joint table query relationship and a subquery relationship, as well as a code module that interacts with the database.

[0072] Furthermore, in one embodiment of the present invention, after the first association relationship and the second association relationship are obtained through the above steps, a data association analysis diagram of the legacy system can be generated based on the first association relationship and the second association relationship.

[0073] S2, based on the code analysis diagram and data association analysis diagram, generates the business living documents and dependency analysis diagram of the legacy system;

[0074] In one embodiment of the present invention, after the code analysis graph and the data association analysis graph are obtained through the above steps, the business living document and the dependency analysis graph of the legacy system can be generated based on the code analysis graph and the data association analysis graph. Among them, in one embodiment of the present invention, the method for generating the business living document and the dependency analysis graph of the legacy system based on the code analysis graph and the data association analysis graph may include the following steps:

[0075] S21, extracting entities in the code analysis diagram;

[0076] S22, determining the association relationship of entities in the code analysis diagram;

[0077] S23. Based on the entities and association relationships in the code analysis diagram, as well as the data association analysis diagram, generate the business living documents and dependency analysis diagram of the legacy system.

[0078] Among them, in one embodiment of the present invention, the above-mentioned business living documents and dependency analysis diagrams of the legacy system can be generated based on the entities and association relationships in the code analysis diagram, as well as the data association analysis diagram.

[0079] And, in one embodiment of the present invention, the above-mentioned business activity document may include a cover and a table of contents, an introduction and a business process description. In one embodiment of the present invention, the above-mentioned cover and the table of contents may include basic information of the document, wherein the basic information may include the document title, version number and directory structure of the document; the introduction may include the background, purpose and scope of the legacy system; the business process description may include the process number and name, step and logic information and database interaction information.

[0080] Furthermore, in one embodiment of the present invention, the process number and name may include a unique number and a clear name assigned to each business process; the step and logic information may include the processing logic of each step, including input parameters, processing rules, and output parameters; the database interaction information may include the specific process and interaction information for interacting with the database table, wherein the interaction information may include the table name, field name, and operation type of the interaction.

[0081] In one embodiment of the present invention, the dependency analysis diagram may include components and modules in the legacy system represented by rectangles and ovals, dependency relationships and database table reference information. The dependency relationship between components and / or modules may be represented by a line with an arrow, and the direction of the arrow represents the direction of the dependency. Also, a database table referenced by the module or component may be marked with a specific icon or color next to the graphic representing the module or component, and the module and the database table may be connected by a dotted line or a special arrow to clearly show the reference relationship.

[0082] S3, obtain abnormal information of the legacy system;

[0083] In one embodiment of the present invention, the exception information of the above-mentioned legacy system may include an exception type, an error code and a timestamp.

[0084] S4, performing exception analysis on the exception information based on the business activity document and the dependency analysis diagram, and processing the exception information based on the obtained exception analysis results.

[0085] In one embodiment of the present invention, after obtaining the exception information of the legacy system through the above steps, the exception information can be analyzed based on the business live document and the dependency analysis diagram, and the exception information can be processed based on the obtained exception analysis results. Specifically, in one embodiment of the present invention, the above method of analyzing the exception information based on the business live document and the dependency analysis diagram, and processing the exception information based on the obtained exception analysis results can include the following steps:

[0086] S41, analyzing the exception information based on the dependency analysis graph to obtain a set of associated target code modules;

[0087] S42, based on the business activity document, determining database information that interacts with the target code module set;

[0088] S43, reproducing the abnormal information based on the target code module set and the database information to obtain an abnormal analysis result;

[0089] S44, modifying the target code module set based on the obtained exception analysis result to process the exception information.

[0090] In one embodiment of the present invention, the method for analyzing the exception information based on the dependency analysis graph to obtain the associated target code module set may include the following steps:

[0091] Step a, based on the exception type, determining a first code module set of exception information;

[0092] Step b: based on the dependency analysis graph, determine the external modules associated with the first code module set to obtain a second code module set;

[0093] Step c: Analyze the second code module set based on the error code and the timestamp to obtain an associated target code module set.

[0094] In one embodiment of the present invention, the first code module set that the exception information may involve can be determined based on the exception type in the exception information. For example, in one embodiment of the present invention, assuming that the exception type is a database connection exception, the code module involved may be a database access module.

[0095] Furthermore, in one embodiment of the present invention, after the first code module set is determined through the above steps, the second code module set can be obtained by determining the external modules associated with the first code module set based on the dependency analysis graph.

[0096] Further, in one embodiment of the present invention, the second code module set can be analyzed based on the error code and timestamp in the exception information, the target code module related to the error code and timestamp can be determined, and the target code module can be determined as the target code module set.

[0097] Furthermore, in one embodiment of the present invention, after the target code module set is determined through the above steps, database information that interacts with the target code modules in the target code module set can be determined based on the business activity document.

[0098] Furthermore, in one embodiment of the present invention, the target code modules in the target code module set can be reproduced through the target code module set and database information interacting with the target code module set, and the abnormal analysis results can be obtained by analysts.

[0099] Furthermore, in one embodiment of the present invention, after obtaining the abnormal analysis result through the above steps, the target code module set can be modified based on the obtained abnormal analysis result to process the abnormal information.

[0100] Specifically, in one embodiment of the present invention, the above-mentioned method of modifying the target code module set based on the obtained exception analysis results to process the exception information may include: modifying the target code module set based on the obtained exception analysis results, and performing regression testing on the modified code module set; if the regression test passes, the processing of the exception information is completed.

[0101] Among them, in one embodiment of the present invention, if the above-mentioned regression test fails, the target code modules in the target code module set continue to be modified until the regression test is passed and the processing of the abnormal information is completed.

[0102] Furthermore, in one embodiment of the present invention, after the abnormal information is processed by the above method, the method may further include: updating the business living documents and dependency analysis diagram of the legacy system based on the modified code module set.

[0103] Furthermore, in one embodiment of the present invention, the legacy system is maintained and managed through the updated business documents and dependency analysis diagrams of the legacy system.

[0104] In the management method of the legacy system proposed by the present invention, a code analysis diagram and a data association analysis diagram of the legacy system are generated; based on the code analysis diagram and the data association analysis diagram, a business active document and a dependency analysis diagram of the legacy system are generated; abnormal information of the legacy system is obtained; based on the business active document and the dependency analysis diagram, an abnormal analysis is performed on the abnormal information, and the abnormal information is processed based on the obtained abnormal analysis results. Therefore, the present invention can quickly locate the target code module and database information associated with the abnormal information through the business active document and the dependency analysis diagram, so that the business personnel can process the abnormalities of the legacy system in time, and then the legacy system can continue to provide services to users, thereby improving the user experience.

[0105] In order to implement the above embodiment, Figure 2 As shown, this embodiment also provides a management device 10 for a legacy system, which includes a first generation module 201, a second generation module 202, an acquisition module 203 and a processing module 204;

[0106] The first generating module 201 is used to generate a code analysis diagram and a data association analysis diagram of a legacy system;

[0107] The second generating module 202 is used to generate a business living document and a dependency analysis diagram of the legacy system based on the code analysis diagram and the data association analysis diagram;

[0108] The acquisition module 203 is used to acquire the abnormal information of the legacy system;

[0109] The processing module 204 is used to perform an exception analysis on the exception information based on the business activity document and the dependency analysis diagram, and process the exception information based on the obtained exception analysis result.

[0110] In one embodiment of the present invention, the first generating module 201 is specifically used for:

[0111] Perform syntax analysis on the source code of the legacy system and construct the corresponding abstract syntax tree;

[0112] Generate the initial code structure diagram of the legacy system based on the abstract syntax tree;

[0113] Generate code analysis diagram of legacy system based on abstract syntax tree and initial code structure diagram;

[0114] Obtain database configuration files of the legacy system;

[0115] Generate data association analysis diagrams for legacy systems based on database configuration files.

[0116] Furthermore, in one embodiment of the present invention, the second generating module 202 is specifically configured to:

[0117] Extract entities from code analysis diagrams;

[0118] Determine the association relationship between entities in the code analysis diagram;

[0119] Based on the entities and association relationships in the code analysis diagram, as well as the data association analysis diagram, business living documents and dependency analysis diagrams of the legacy system are generated.

[0120] Further, in one embodiment of the present invention, the processing module 204 is specifically used to:

[0121] Analyze the exception information based on the dependency analysis graph to obtain the associated target code module set;

[0122] Based on the business live documents, determine the database information that interacts with the target code module set;

[0123] Reproduce the abnormal information based on the target code module set and database information to obtain the abnormal analysis results;

[0124] The target code module set is modified based on the obtained exception analysis results to process the exception information.

[0125] Furthermore, in one embodiment of the present invention, the processing module 204 is further configured to:

[0126] Based on the exception type, determine a first code module set of exception information;

[0127] Based on the dependency analysis graph, determine the external modules associated with the first code module set to obtain a second code module set;

[0128] The second code module set is analyzed based on the error code and the timestamp to obtain an associated target code module set.

[0129] Furthermore, in one embodiment of the present invention, the processing module 204 is further configured to:

[0130] Modify the target code module set based on the obtained abnormal analysis results, and perform regression testing on the modified code module set;

[0131] If the regression test passes, the processing of the exception information is completed.

[0132] Furthermore, in one embodiment of the present invention, the above-mentioned apparatus is also used to update the business living documents and dependency analysis diagram of the legacy system based on the modified code module set.

[0133] In the management device of the legacy system proposed by the present invention, a code analysis diagram and a data association analysis diagram of the legacy system are generated; based on the code analysis diagram and the data association analysis diagram, a business active document and a dependency analysis diagram of the legacy system are generated; abnormal information of the legacy system is obtained; based on the business active document and the dependency analysis diagram, an abnormal analysis is performed on the abnormal information, and the abnormal information is processed based on the obtained abnormal analysis result. Therefore, the present invention can quickly locate the target code module and database information associated with the abnormal information through the business active document and the dependency analysis diagram, so that the business personnel can process the abnormalities of the legacy system in time, and then the legacy system can continue to provide services to users, thereby improving the user experience.

[0134] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0135] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of the present invention, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

Claims

1. A method for managing a legacy system, characterized in that: The method comprises: Generate a code analysis diagram and a data association analysis diagram of the legacy system; Based on the code analysis diagram and the data association analysis diagram, generating a business living document and a dependency analysis diagram of the legacy system; Obtaining abnormal information of the legacy system; The exception information is analyzed based on the business activity document and the dependency analysis diagram, and the exception information is processed based on the obtained exception analysis result.

2. The method according to claim 1, characterized in that The generating of the code analysis diagram and the data association analysis diagram of the legacy system includes: Performing syntax analysis on the source code of the legacy system and constructing a corresponding abstract syntax tree; Based on the abstract syntax tree, generating an initial code structure diagram of the legacy system; Generate a code analysis diagram of the legacy system based on the abstract syntax tree and the initial code structure diagram; Obtaining a database configuration file of the legacy system; Based on the database configuration file, a data association analysis diagram of the legacy system is generated.

3. The method according to claim 1, characterized in that The generating of the business living document and the dependency analysis diagram of the legacy system based on the code analysis diagram and the data association analysis diagram includes: Extracting entities in the code analysis graph; Determine the association relationship of entities in the code analysis graph; Based on the entities and association relationships in the code analysis diagram, and the data association analysis diagram, a business living document and a dependency analysis diagram of the legacy system are generated.

4. The method according to claim 1, characterized in that: The performing an exception analysis on the exception information based on the business activity document and the dependency analysis diagram, and processing the exception information based on the obtained exception analysis result, includes: Analyze the exception information based on the dependency analysis graph to obtain an associated target code module set; Based on the business activity document, determine database information that interacts with the target code module set; Reproducing the abnormal information based on the target code module set and the database information to obtain an abnormal analysis result; The target code module set is modified based on the obtained exception analysis result to process the exception information.

5. The method according to claim 4, characterized in that The exception information includes an exception type, an error code and a timestamp; the exception information is analyzed based on the dependency analysis graph to obtain an associated target code module set, including: Based on the exception type, determining a first code module set of the exception information; Based on the dependency analysis graph, determine the external modules associated with the first code module set to obtain a second code module set; The second code module set is analyzed based on the error code and the timestamp to obtain an associated target code module set.

6. The method according to claim 4, characterized in that The modifying the target code module set based on the obtained exception analysis result to process the exception information includes: Modifying the target code module set based on the obtained abnormal analysis results, and performing regression testing on the modified code module set; If the regression test is passed, the processing of the abnormal information is completed.

7. The method according to claim 4, characterized in that The method further includes: updating the business living documents and dependency analysis diagram of the legacy system based on the modified code module set.

8. A management device for a legacy system, characterized in that: The device comprises: A first generating module, used to generate a code analysis diagram and a data association analysis diagram of the legacy system; A second generating module is used to generate a business living document and a dependency analysis diagram of the legacy system based on the code analysis diagram and the data association analysis diagram; An acquisition module, used for acquiring abnormal information of the legacy system; A processing module is used to perform an exception analysis on the exception information based on the business activity document and the dependency analysis diagram, and process the exception information based on the obtained exception analysis result.

9. An electronic device comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 7.

10. A computer storage medium, wherein: The computer storage medium stores computer executable instructions; after the computer executable instructions are executed by the processor, the method according to any one of claims 1 to 7 can be implemented.