Changes to fields affect analysis methods, devices, and storage media.
By combining a cross-component tracker and a field semantic knowledge base, the cross-component dependencies of target fields in the financial system are identified and analyzed, solving the problem of low accuracy in change impact analysis in existing technologies and realizing full-link dependency analysis and risk quantification.
Patent Information
- Application Number
- CN202611371464.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-04
- Publication Date
- 2026-11-17
AI Technical Summary
In existing financial back-office operation systems, change impact analysis based on a single component cannot identify implicit dependencies across different technical components, resulting in low accuracy of field change impact analysis results.
By using a cross-component tracker to perform parallel cross-component scanning based on a field semantic knowledge base, the system identifies the physical usage points and logical dependencies of target fields in the business logic layer, view presentation layer, and data persistence layer. It generates a field mapping object containing full dependency information and performs multi-dimensional impact analysis, including compatibility checks for preset change types.
It enables end-to-end dependency analysis of the impact of field changes, improves the accuracy of change impact analysis results, quantifies the specific risks of change points, and generates detailed change impact analysis reports.
Smart Images

Figure CN123115681A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of financial technology, and more specifically, to a method, apparatus, and storage medium for analyzing the impact of field changes. Background Technology
[0002] In change management practices for financial back-office operations systems, the system architecture typically takes the form of a multi-component hybrid architecture, encompassing backend service modules as the business logic layer, page files as the frontend presentation layer, and database storage procedures as the data persistence layer. Existing change impact analysis methods are mainly limited to dependency checks within a single technology stack. For example, they may rely solely on static code scanning tools to analyze call relationships within backend services or solely on database tools to analyze table structure dependencies. This single-dimensional analysis approach cannot identify implicit dependencies across different technology components. Since the continuity of business logic in financial systems often depends on the flow of data between different components, when a target field changes, single-link analysis tools struggle to detect the corresponding reference of that field in another technology stack component. For instance, a change in database field length may require simultaneous modifications to the input validation rules of the frontend page or the data object definition in the backend service. The lack of end-to-end tracing capabilities across components in existing technologies leads to the omission of such cross-level dependencies, resulting in change impact analysis results that fail to cover all related points and consequently, low analysis accuracy.
[0003] There is currently no effective solution to the problem that change analysis based on a single component in related technologies results in low accuracy of the analysis results for the impact of changes on fields. Summary of the Invention
[0004] The main objective of this application is to provide a method, apparatus, and storage medium for analyzing the impact of field changes, in order to solve the problem that the accuracy of the analysis results for the impact of field changes is low due to the use of a single component in related technologies.
[0005] To achieve the above objectives, according to one aspect of this application, a method for analyzing the impact of field changes is provided. The method includes: obtaining change definition information of the target field to be analyzed; performing a cross-component parallel scan of the target field based on a field semantic knowledge base using a cross-component tracker to identify the physical usage points and logical dependencies of the target field in the business logic layer, view presentation layer, and data persistence layer; fusing the physical usage points and logical dependencies to generate a field mapping object containing full dependency information; and performing a multi-dimensional impact analysis on the changes to the target field based on the change definition information, the field mapping object, and the field semantic knowledge base to generate change impact analysis results. The multi-dimensional impact analysis includes a compatibility check for preset change types, which include at least one of field length change, data type change, null value constraint change, and dictionary enumeration value change.
[0006] Optionally, before performing cross-component parallel scanning of the target field based on the field semantic knowledge base using a cross-component tracker, the method further includes: parsing the syntax structure of the source code, front-end page files, database definition scripts, and stored procedure definitions of the target system using a semantic parsing engine to extract field definitions from the source code, front-end page files, database definition scripts, and stored procedure definitions; filtering candidate financial status fields from the field definitions; analyzing the value patterns of the candidate financial status fields and constructing a directed transition relationship graph between the state values of the candidate financial status fields based on the value patterns; and generating a field semantic knowledge base based on the field name, component, business semantic tag, state value enumeration set, and directed transition relationship graph of the candidate financial status fields.
[0007] Optionally, a cross-component tracker performs parallel cross-component scanning of the target field based on a field semantic knowledge base to identify the physical usage points and logical dependencies of the target field in the business logic layer, view presentation layer, and data persistence layer. This includes: parsing the business logic layer code of the target system to locate the physical usage points of the target field in class attribute definitions, method parameter declarations, and data access mappings; analyzing the control flow statements in the business logic layer code according to the state transition rules in the field semantic knowledge base to identify logical dependencies on the target field; parsing the view presentation layer page files of the target system to identify logical dependencies on the target field; and parsing the database definition files of the data persistence layer of the target system to identify the physical usage points of the target field in table column structure definitions and stored procedure parameters.
[0008] Optionally, the process of fusing physical usage points and logical dependency points to generate a field mapping object containing full dependency information includes: normalizing the names of the original field identifiers of physical usage points and logical dependency points to obtain normalized identifiers; calculating the semantic similarity score between the normalized identifiers and the standard identifiers of the target field based on the naming variant list in the field semantic knowledge base, and determining the identifiers with semantic similarity scores greater than a preset similarity threshold as the identifiers of the associated references of the target field, wherein the naming variant list includes a set of synonymous field names of the target field; calculating the relevance of a preset association point corresponding to each associated reference identifier, and determining the preset association points with relevance scores greater than a preset relevance threshold as target association points; determining the standard identifier of the target field as the primary key, determining the target association points as child nodes, and generating a field mapping object.
[0009] Optionally, based on the change definition information, field mapping objects, and field semantic knowledge base, a multidimensional impact analysis is performed on the change of the target field, generating the following change impact analysis results: When the change type of the target field is a field length change, check whether the current length of the target associated point in the field mapping object is less than the new length in the change definition information, and determine that the target associated point whose current length is less than the new length is an incompatible associated point; when the change type of the target field is a data type change, calculate the accuracy loss ratio of each target associated point after the data type change, and determine that the target associated point whose accuracy loss ratio is greater than a preset accuracy loss threshold is an incompatible associated point; when the change type of the target field is empty... When value constraints change, the code logic of the target association points in the scan field mapping object is used to identify incompatible association points that depend on non-null logic. When the change type of the target field is a dictionary enumeration value change, the field mapping coverage of each target association point is calculated, and target association points with a field mapping coverage of less than a preset threshold are identified as incompatible association points. Based on the proportion of incompatible association points to all target association points and the business impact coefficient of the target field, the change risk value is calculated, and the change risk level of the target field is determined based on the change risk value. Modification suggestions are determined for each incompatible association point, and change impact analysis results are generated based on the incompatible association points, change risk levels, and modification suggestions.
[0010] Optionally, calculating the relevance of a preset relevance point corresponding to the identifier of each associated reference includes: obtaining the call frequency of the preset relevance point within a preset time window; determining the business weight of the business module to which the preset relevance point belongs based on the business semantic tags in the field semantic knowledge base; and multiplying the call frequency by the business weight to calculate the relevance of the preset relevance point.
[0011] Optionally, after generating change impact analysis results based on incompatible related points, change risk levels, and modification suggestions, the method further includes: using a force-directed layout algorithm to generate a field topology diagram based on the dependency relationships between target fields and target related points; using a four-dimensional risk matrix model to calculate the related point risk value for each target related point based on four dimensions: technical impact, business impact, probability of occurrence, and repair cost, and mapping the related point risk value to the related point risk level; grouping and aggregating target related points according to component type, file path, and related point risk level, counting the number of risk points or average comprehensive risk score within each group, mapping the statistical results to a preset color gradient, and generating a risk heatmap; and generating a change impact analysis report based on the field topology diagram, risk heatmap, and change impact analysis results.
[0012] To achieve the above objectives, according to another aspect of this application, a field change impact analysis apparatus is provided. The apparatus includes: an identification unit, configured to acquire change definition information of the target field to be analyzed, and to perform cross-component parallel scanning of the target field based on a field semantic knowledge base using a cross-component tracker, identifying the physical usage points and logical dependency points of the target field in the business logic layer, view presentation layer, and data persistence layer; a first generation unit, configured to perform fusion processing on the physical usage points and logical dependency points to generate a field mapping object containing full dependency information; and an analysis unit, configured to perform multidimensional impact analysis on the change of the target field based on the change definition information, the field mapping object, and the field semantic knowledge base, generating change impact analysis results, wherein the multidimensional impact analysis includes a compatibility check for preset change types, the preset change types including at least one of field length change, data type change, null value constraint change, and dictionary enumeration value change.
[0013] According to another aspect of this application, a computer-readable storage medium is provided, the computer-readable storage medium including a stored program, wherein, when the program is executed, it controls the device where the computer-readable storage medium is located to perform a method for analyzing the impact of changes to any field.
[0014] According to another aspect of this application, an electronic device is provided, comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include a method for performing a change impact analysis of any one type of field.
[0015] According to another aspect of this application, a computer program product is provided, including computer instructions, which, when executed by a processor, implement the steps of the method for analyzing the impact of changes to any of the fields described above.
[0016] In this embodiment, by obtaining the change definition information of the target field to be analyzed, and by using a cross-component tracker to perform cross-component parallel scanning of the target field based on the field semantic knowledge base, the physical usage points and logical dependency points of the target field in the business logic layer, view presentation layer, and data persistence layer are identified; the physical usage points and logical dependency points are fused to generate a field mapping object containing full dependency information; based on the change definition information, the field mapping object, and the field semantic knowledge base, a multidimensional impact analysis is performed on the change of the target field to generate change impact analysis results. The multidimensional impact analysis includes a compatibility check for preset change types, which include at least one of field length change, data type change, null value constraint change, and dictionary enumeration value change. This solves the technical problem in related technologies where change analysis based on a single component leads to low accuracy of the change impact analysis results for fields.
[0017] In this application, by obtaining the change definition information of the target field to be analyzed, a cross-component tracker is used to perform a three-way parallel scan of the business logic layer, view presentation layer, and data persistence layer based on the field semantic knowledge base to conduct full-link dependency analysis, identify the physical usage points and logical dependency points of the target field, generate a field mapping object containing full dependency information, and perform compatibility checks on preset change types based on the change definition information, field mapping object, and field semantic knowledge base to quantify the specific risks of change points and generate change impact analysis results, thereby achieving the technical effect of improving the accuracy of change impact analysis results for fields. Attached Figure Description
[0018] The accompanying drawings, which form part of this application, are used to provide a further understanding of this application. The illustrative embodiments and descriptions of this application are used to explain this application and do not constitute an undue limitation of this application. In the drawings:
[0019] Figure 1 A hardware structure block diagram of a computer terminal for implementing a field change impact analysis method is shown.
[0020] Figure 2 This is a flowchart of the method for analyzing the impact of field changes according to the embodiments of this application;
[0021] Figure 3 This is a schematic diagram of the field change impact analysis method provided in the embodiments of this application;
[0022] Figure 4 This is a schematic diagram of a field change impact analysis device provided in the embodiments of this application;
[0023] Figure 5 This is a structural block diagram of an electronic device according to an embodiment of this application. Detailed Implementation
[0024] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.
[0025] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0026] It should be noted that all relevant information (including at least one of the following database information, component information, etc.) and data (including at least one of the following data used for display, data used for analysis, etc.) involved in this application are information and data authorized by the user or fully authorized by all parties. For example, this system has an interface with the relevant user or organization. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or organization through the interface, and obtain the relevant information after receiving consent information from the aforementioned user or organization.
[0027] Example 1
[0028] According to an embodiment of this application, a method embodiment for analyzing the impact of field changes is also provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.
[0029] The method embodiment provided in Embodiment 1 of this application can be executed on a mobile terminal, computer terminal, or similar computing device. Figure 1 A hardware block diagram of a computer terminal (or mobile device) for implementing a method for analyzing the impact of field changes is shown. Figure 1As shown, the computer terminal 10 (or mobile device) may include one or more processors 102 (shown as 102a, 102b, ..., 102n in the figure) 102 (processor 102 may include at least one of the following: a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a Universal Serial Bus (USB) port (which may be included as one of the ports of a BUS bus), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, computer terminal 10 may also include... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.
[0030] It should be noted that the aforementioned one or more processors 102 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be integrated, in whole or in part, into any other element within the computer terminal 10 (or mobile device). As involved in the embodiments of this application, the data processing circuits serve as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).
[0031] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the field change impact analysis method in this embodiment. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, thereby realizing the above-mentioned field change impact analysis method. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the computer terminal 10 via a network. Examples of the above-mentioned networks include at least one of the following: the Internet, corporate intranet, local area network, mobile communication network, and combinations thereof.
[0032] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the computer terminal 10. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.
[0033] The display can be, for example, a touchscreen liquid crystal display (LCD), which allows the user to interact with the user interface of the computer terminal 10 (or mobile device).
[0034] Under the aforementioned operating environment, this application provides the following: Figure 2 The method for analyzing the impact of changes to the fields shown. Figure 2 This is a flowchart of the field change impact analysis method according to Embodiment 1 of this application.
[0035] Step S201: Obtain the change definition information of the target field to be analyzed, and perform cross-component parallel scanning of the target field based on the field semantic knowledge base through the cross-component tracker to identify the physical usage points and logical dependencies of the target field in the business logic layer, view presentation layer and data persistence layer.
[0036] Optionally, the source code of the business logic layer can be parsed using an abstract syntax tree to locate entity class attribute definitions, field references in data access mapping files, and field assignment or read operations in service layer methods. This identifies the physical usage points of the target fields and analyzes the control flow statements in the business logic layer code based on state transition rules in the field semantic knowledge base to identify logical dependencies on the target fields. The page files of the view presentation layer can be parsed to identify form input element attributes, expression language references, and front-end script validation logic, thus identifying logical dependencies on the target fields. The database definition files and stored procedures of the data persistence layer can be parsed to identify table column definitions, stored procedure parameter declarations, and field references in triggers, thus identifying the physical usage points of the target fields.
[0037] Step S202: Merge the physical usage points and logical dependency points to generate a field mapping object containing full dependency information.
[0038] Optionally, firstly, the original field identifiers of physical usage points and logical dependency points are normalized; then, based on the list of named variants in the field semantic knowledge base, the semantic similarity score between the normalized identifier and the standard identifier of the target field is calculated; identifiers with semantic similarity scores greater than a preset similarity threshold are selected as candidate association points; the association degree of each candidate association point is calculated, and target association points with association degrees greater than a preset association threshold are retained to construct a field mapping object with the target field as the primary key and the target association points as child nodes.
[0039] Step S203: Based on the change definition information, field mapping object, and field semantic knowledge base, perform a multidimensional impact analysis on the change of the target field and generate the change impact analysis results. The multidimensional impact analysis includes a compatibility check on preset change types, which include at least one of field length change, data type change, null value constraint change, and dictionary enumeration value change.
[0040] Optionally, compatibility checks include: marking incompatible association points where the current length is less than the new length for field length changes; marking incompatible association points where precision loss exceeds a preset threshold for data type changes; marking incompatible association points that depend on non-null logic but do not handle null values for null value constraints changes; and marking incompatible association points where mapping coverage is insufficient or mapping inconsistency rate exceeds the standard for dictionary enumeration value changes. Change risk values can be calculated based on the proportion of incompatible association points and the business impact coefficient of the target field, generating change impact analysis results that include a list of incompatible points, change risk levels, and modification suggestions.
[0041] The field change impact analysis method provided in this application obtains the change definition information of the target field to be analyzed, performs a three-way parallel scan of the business logic layer, view presentation layer, and data persistence layer based on a field semantic knowledge base through a cross-component tracker, conducts full-link dependency analysis, identifies the physical usage points and logical dependency points of the target field, generates a field mapping object containing full dependency information, and performs compatibility checks on preset change types based on the change definition information, field mapping object, and field semantic knowledge base, quantifies the specific risks of change points, and generates change impact analysis results. This solves the technical problem in related technologies where change analysis based on a single component leads to low accuracy of field change impact analysis results, and achieves the technical effect of improving the accuracy of field change impact analysis results.
[0042] To construct an accurate field semantic knowledge base and provide a semantic foundation for the identification and risk quantification of cross-component dependencies, optionally, in the field change impact analysis method provided in this application embodiment, before performing cross-component parallel scanning of the target field based on the field semantic knowledge base using a cross-component tracker, the method further includes:
[0043] The first step is to use a semantic parsing engine to perform syntactic structure parsing on the source code, front-end page files, database definition scripts, and stored procedure definitions of the target system, and extract the field definitions from the source code, front-end page files, database definition scripts, and stored procedure definitions.
[0044] Optionally, the syntax structure parsing can utilize abstract syntax tree parsing technology to traverse the syntax tree nodes of the source code, front-end page files, database definition scripts, and stored procedure definitions, and extract the field definitions from the source code, front-end page files, database definition scripts, and stored procedure definitions.
[0045] The second step is to filter out candidate financial status fields from the field definitions.
[0046] Optionally, the field definitions can be matched based on preset keyword rules to identify fields containing status identifier keywords; alternatively, historical change records can be combined to count the change frequency of each field, exclude fields with a change frequency lower than a preset threshold, and use the excluded fields as candidate financial status fields.
[0047] The third step is to analyze the value patterns of the candidate financial status fields and construct a directed transition relationship graph between the status values of the candidate financial status fields based on the value patterns.
[0048] Optionally, the value patterns of candidate financial status fields can be analyzed by scanning the context in which they appear in conditional statements, flow control statements, and business logic methods. The state values of candidate financial status fields and the transition logic between them can also be analyzed. A directed transition graph representing the state flow relationship can be constructed with state values as nodes and transition logic as directed edges.
[0049] The fourth step is to generate a field semantic knowledge base based on the field name, component, business semantic tag, state value enumeration set, and directed transition relationship diagram of the candidate financial status field.
[0050] Optionally, the field name, its component, business semantic tag, state value enumeration set, and directed transition relationship diagram are associated and stored to form structured field semantic record information, generating a field semantic knowledge base containing field semantic record information of all candidate financial state fields.
[0051] In summary, by following the steps above, extracting all field definitions through structured parsing of multi-source data, filtering out candidate financial status fields, and generating a field semantic knowledge base by combining the state transition relationships of the candidate financial status fields, it is helpful to improve the accuracy of dependency identification in cross-component tracking.
[0052] To accurately identify the physical usage points and logical dependencies of the target field, optionally, in the field change impact analysis method provided in this application embodiment, a cross-component tracker performs a parallel cross-component scan of the target field based on a field semantic knowledge base to identify the physical usage points and logical dependencies of the target field in the business logic layer, view presentation layer, and data persistence layer, including:
[0053] The first step is to parse the business logic layer code of the target system, locate the physical usage points of the target field in class attribute definition, method parameter declaration and data access mapping, and analyze the control flow statements in the business logic layer code according to the state transition rules in the field semantic knowledge base to identify the logical dependency points that depend on the target field.
[0054] Optionally, static code analysis tools or abstract syntax tree parsing techniques can be used to traverse the business logic layer code files, match the variable names, attribute names, or database mapping aliases of the target fields, and record the physical usage points of the target fields in class attribute definitions, method parameter declarations, and data access mappings. At the same time, conditional statements and loop statements involving the target fields can be extracted, and combined with the state transition rules in the field semantic knowledge base, the logical dependency points of implicit business logic dependencies can be identified.
[0055] The second step is to parse the view presentation layer page files of the target system and identify the logical dependencies that depend on the target fields.
[0056] Optionally, the form element definitions in the view presentation layer page file can be scanned to extract the control attributes of input boxes and drop-down boxes and match them with the target field names; the expression language and front-end script code in the view presentation layer page file can be parsed to identify the front-end interaction's response to changes in the target field, i.e., the logical dependency points.
[0057] The third step is to parse the database definition file of the target system's data persistence layer to identify the physical usage points of the target fields in the table column structure definition and stored procedure parameters.
[0058] Optionally, the database structure definition script and stored procedure source code in the database definition file are parsed to extract column names, data types, and constraints in the table structure definition, and to confirm the physical definition of the target field in the database. At the same time, the stored procedure, trigger, and view definitions are scanned to identify column references in parameter declarations, local variable assignments, and data operation statements, and the code locations that directly manipulate the target field data are recorded as physical usage points.
[0059] In summary, by performing structured parallel parsing of the business logic layer, view presentation layer, and data persistence layer, and extracting direct references at the physical level and indirect dependencies at the logical level, the above steps achieve accurate identification of cross-component dependencies, providing an accurate data foundation for the subsequent generation of field mapping objects.
[0060] To generate accurate field mapping objects based on end-to-end dependencies, optionally, in the field change impact analysis method provided in this application embodiment, physical usage points and logical dependency points are fused to generate field mapping objects containing full dependency information, including:
[0061] The first step is to normalize the names of the original field identifiers of physical usage points and logical dependency points to obtain normalized identifiers.
[0062] Optionally, name normalization may include removing special characters, spaces, and case differences from the original field identifier, converting them into a standard format, and mapping common abbreviations to a unified standardized name to obtain a normalized identifier, thereby eliminating the surface differences in identifiers caused by different coding styles or naming habits.
[0063] The second step is to calculate the semantic similarity score between the normalized identifier and the standard identifier of the target field based on the naming variant list in the field semantic knowledge base, and determine the identifiers whose semantic similarity scores are greater than the preset similarity threshold as the identifiers associated with the target field. The naming variant list includes a set of synonym field names of the target field.
[0064] Optionally, based on the edit distance algorithm or cosine similarity algorithm, the similarity between the normalized identifier and the standard identifier of the target field in the character sequence can be quantified, and a semantic similarity score can be calculated; identifiers with a semantic similarity score greater than a preset similarity threshold (such as 0.85) can be identified as identifiers associated with the target field, thus filtering out fields that are accidentally hit or irrelevant.
[0065] The third step is to calculate the correlation degree of the preset correlation point corresponding to the identifier of each associated reference, and determine the preset correlation point with a correlation degree greater than the preset correlation degree threshold as the target correlation point.
[0066] Optionally, the correlation degree of preset association points can be calculated based on the product of call frequency and business weight. Call frequency can be obtained by statistically analyzing the frequency of occurrence of the identifier in historical logs or code call chains, and business weight can be determined based on the importance of the business module to which the identifier belongs. Determining preset association points with a correlation degree greater than a preset correlation degree threshold as target association points can exclude preset association points with low frequency or low importance.
[0067] The fourth step is to determine the standard identifier of the target field as the primary key, determine the target association point as the child node, and generate a field mapping object.
[0068] Optionally, a tree-like data structure can be constructed with the standard identifier of the target field as the root node, and the target association points can be mounted as child nodes under the root node. Metadata such as source component, file location, dependency type and association degree value can be added to each child node to form a structured field mapping object.
[0069] In summary, the above steps—name normalization to eliminate format interference, semantic similarity to filter irrelevant identifiers, relevance to determine target association points, and target field mapping objects to generate based on the standard identifiers and target association points of the target fields—improve the accuracy and completeness of the generated field mapping objects, providing reliable data support for subsequent quantification of change risks.
[0070] To accurately assess the risk of changes to the target variable, optionally, in the field change impact analysis method provided in this application embodiment, a multidimensional impact analysis is performed on the change of the target field based on the change definition information, the field mapping object, and the field semantic knowledge base, generating change impact analysis results including:
[0071] The first step is to check whether the current length of the target field is less than the new length in the change definition information when the target field is changed. If the target field is less than the new length, it is determined to be an incompatible field.
[0072] Optionally, all target association points in the field mapping object are traversed, the field length definition of each target association point is extracted, the current length of the extracted target association point is compared with the new length in the change definition information, and if the current length is less than the new length, it is determined to be an incompatible association point, and the specific length difference is recorded.
[0073] The second step is to calculate the accuracy loss ratio of each target association point after the data type change when the target field is changed, and determine the target association points whose accuracy loss ratio is greater than the preset accuracy loss threshold as incompatible association points.
[0074] Optionally, based on the precision definitions of the original data type and the new data type, the data conversion process can be simulated to calculate the data error magnitude caused by type truncation or rounding. The precision loss ratio can be obtained by calculating the ratio of the data error magnitude to the original value. Target association points with a precision loss ratio greater than a preset precision loss threshold (such as 0.001%) are identified as incompatible association points.
[0075] The third step is to scan the code logic of the target association point in the field mapping object when the change type of the target field is a null constraint change, and determine the target association point that depends on the non-null logic as an incompatible association point.
[0076] Optionally, the code logic of the target association point is analyzed, including conditional statements and data insertion / update logic. Code snippets that assume field values are not null but do not contain null value handling branches are identified. If it is found that the target association point depends on non-null logic, it means that a null pointer exception may be thrown or a logical omission may occur after the target variable is changed, and then it is determined to be an incompatible association point.
[0077] The fourth step is to calculate the field mapping coverage rate of each target association point when the change type of the target field is a dictionary enumeration value change. Target association points with a field mapping coverage rate less than a preset threshold are identified as incompatible association points.
[0078] Optionally, check whether each old state value of the target associated point has a corresponding valid new state value, calculate the ratio of the number of old state values that have been covered to the total number of old state values as the mapping coverage rate. If the field mapping coverage rate is lower than a preset threshold (such as 100%), or if there is a mapping conflict, it is determined to be an incompatible associated point.
[0079] The fifth step is to calculate the change risk value based on the proportion of incompatible related points to all target related points and the business impact coefficient of the target field, and then determine the change risk level of the target field based on the change risk value.
[0080] Optionally, firstly, divide the number of incompatible related points by the total number of all target related points to obtain the basic risk percentage; then, obtain the business impact coefficient corresponding to the business module to which the target field belongs from the field semantic knowledge base (e.g., the impact coefficient for clearing business is 1.0, and the impact coefficient for query business is 0.3); multiply the basic risk percentage by the business impact coefficient to obtain the change risk value. The change risk value can be compared with a preset risk level range to determine the change risk level.
[0081] The sixth step is to determine the modification recommendations for each incompatible related point, and generate the change impact analysis results based on the incompatible related points, the change risk level, and the modification recommendations.
[0082] Optionally, modification suggestions are generated based on the incompatibility type of each incompatible association point. For length incompatibility, the modification suggestion is to generate a code template for adjusting the length parameter; for type incompatibility, the modification suggestion is to generate a code template for compatibility conversion or precision preservation; for null value constraint incompatibility, the modification suggestion is to generate a code template for adding null value judgment logic; and for dictionary value incompatibility, the modification suggestion is to generate a code template for state mapping conversion.
[0083] In summary, by performing compatibility checks on changes in field length, data type, null constraint, and dictionary enumeration values, and by calculating change risk values based on risk percentage and business impact coefficient, a change impact analysis result containing modification suggestions is generated. This not only improves the accuracy of the change impact analysis result but also helps to improve the efficiency of subsequent change approval and execution.
[0084] To accurately quantify the relevance of each preset association point, optionally, in the field change impact analysis method provided in this application embodiment, calculating the relevance of the preset association point corresponding to each associated reference identifier includes:
[0085] The first step is to obtain the call frequency of the preset associated points within the preset time window.
[0086] Optionally, the call frequency of preset related points within a preset time window (e.g., the past 30 days or the most recent production version cycle) can be calculated from system operation logs, gateway access records, or code static analysis metadata.
[0087] The second step is to determine the business weight of the business module to which the preset association point belongs, based on the business semantic tags in the field semantic knowledge base.
[0088] Optionally, the semantic knowledge base of the field is queried to identify the business semantic tags (such as fund clearing, account freezing, information query, etc.) served by the preset association points, and the business semantic tags are mapped to the corresponding numerical business weights according to the preset business importance level mapping table.
[0089] The third step is to multiply the call frequency by the business weight to calculate the correlation degree of the preset association points.
[0090] Optionally, the call frequency value can be multiplied by the business weight value to obtain the correlation value. The correlation value can also be normalized and mapped to a standard range of 0 to 1. The normalized value can then be used as the final correlation degree of the preset correlation point.
[0091] In summary, by following the steps above and calculating the correlation degree of preset related points based on call frequency and business weight, the correlation degree of each preset related point is accurately quantified. This helps to filter out non-core related points and provides accurate data support for subsequent quantification of change risks.
[0092] To generate an accurate change impact analysis report, optionally, in the change impact analysis method for fields provided in this application embodiment, after generating the change impact analysis results based on incompatible association points, change risk levels, and modification suggestions, the method further includes:
[0093] The first step is to use a force-directed layout algorithm to generate a field topology graph based on the dependency relationships between the target field and the target associated points.
[0094] Optionally, the target field and all target associated points are treated as nodes in the field topology graph, and the dependencies between nodes are treated as edges. Each node is initialized with a random position on the two-dimensional plane. The energy minimization process of the physical system is simulated by iteratively calculating the repulsive force between nodes and the attractive force of edges until a stable state is reached. Finally, the coordinate layout of each node on the two-dimensional plane is output, and connecting lines are drawn to form a field topology graph that can reflect the field dependency structure.
[0095] The second step involves using a four-dimensional risk matrix model to calculate the associated risk value for each target associated point based on four dimensions: technological impact, business impact, probability of occurrence, and repair cost. This associated risk value is then mapped to the associated risk level.
[0096] Optionally, for each target associated point, the degree of technical impact, the degree of business impact, the probability of occurrence, and the repair cost are quantified separately. A weighted sum of these factors is then performed to calculate the associated point risk value for each target associated point. Based on a preset risk score range, the associated point risk value for each target associated point can be mapped to a corresponding risk level (e.g., low, medium, high, urgent).
[0097] The third step is to group and aggregate the target associated points according to component type, file path and associated point risk level, count the number of risk points or average comprehensive risk score in each group, and map the statistical results to a preset color gradient to generate a risk heat map.
[0098] Optionally, a two-dimensional matrix is constructed with component type as rows and file path as columns; all target association points are traversed, and the risk score or count of the target association points is accumulated according to their position in the matrix; the aggregated risk index is calculated for each matrix unit; a color gradient mapping rule from green (low risk) to red (high risk) is defined; according to the magnitude of the aggregated risk index, the corresponding color is selected to fill the matrix unit, generating a risk heatmap that can intuitively display the density of risk distribution.
[0099] The fourth step is to generate a change impact analysis report based on the field topology diagram, risk heat map, and change impact analysis results.
[0100] Optionally, the change impact analysis report can display field topology diagrams and risk heatmaps in the form of charts, and display the change impact analysis results in the form of lists. It can also realize the linkage and interaction between charts and list data. For example, clicking on a node in the field topology diagram can highlight the corresponding risk heatmap area and change impact analysis results.
[0101] In summary, by taking the steps described above, generating field topology diagrams and risk heatmaps, and combining these with the change impact analysis results to generate a change impact analysis report, topology dependencies and data risks are transformed into intuitive visual information. This helps improve the speed at which the operations and maintenance team perceives and makes decisions regarding complex change risks.
[0102] Optionally, such as Figure 3 The diagram illustrates the method for analyzing the impact of field changes. It involves receiving a change request for the target field, including change definition information; constructing a semantic knowledge base using an AI learning engine; performing a cross-component parallel scan of the target field based on the semantic knowledge base using a cross-component tracker to identify the physical usage points and logical dependencies of the target field in the business logic layer, view presentation layer, and data persistence layer, and generating a field mapping object; using a financial impact analyzer, performing a multi-dimensional impact analysis on the change of the target field based on the change definition information, field mapping object, and field semantic knowledge base, identifying incompatible correlation points, and generating a change impact analysis result including a list of incompatible correlation points, change risk level, and modification suggestions; and generating a visual analysis report including a field topology map, risk heatmap, and change impact analysis results using a visualization report generator.
[0103] It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases the steps shown or described may be executed in a different order than that shown here.
[0104] Example 2
[0105] This application also provides a field change impact analysis device. It should be noted that the field change impact analysis device of this application can be used to execute the field change impact analysis method provided in this application. The following describes the field change impact analysis device provided in this application.
[0106] According to embodiments of this application, an apparatus for implementing the above-described method for analyzing the impact of changes to fields is also provided, such as... Figure 4 As shown, the device includes: 401, a first generation unit 402, and an analysis unit 403.
[0107] The identification unit 401 is used to obtain the change definition information of the target field to be analyzed, and to perform cross-component parallel scanning of the target field based on the field semantic knowledge base through the cross-component tracker to identify the physical usage points and logical dependencies of the target field in the business logic layer, view presentation layer and data persistence layer.
[0108] The first generation unit 402 is used to merge physical usage points and logical dependency points to generate a field mapping object containing full dependency information.
[0109] Analysis unit 403 is used to perform multidimensional impact analysis on changes to the target field based on change definition information, field mapping objects, and field semantic knowledge base, and generate change impact analysis results. The multidimensional impact analysis includes a compatibility check for preset change types, which include at least one of field length change, data type change, null value constraint change, and dictionary enumeration value change.
[0110] The field change impact analysis device provided in this application embodiment obtains the change definition information of the target field to be analyzed through the identification unit 401, and performs cross-component parallel scanning of the target field based on the field semantic knowledge base through the cross-component tracker to identify the physical usage points and logical dependency points of the target field in the business logic layer, view display layer and data persistence layer; the first generation unit 402 performs fusion processing on the physical usage points and logical dependency points to generate a field mapping object containing full dependency information; the analysis unit 403 performs multi-dimensional impact analysis on the change of the target field according to the change definition information, the field mapping object and the field semantic knowledge base, and generates change impact analysis results. The multi-dimensional impact analysis includes a compatibility check for preset change types, which include at least one of field length change, data type change, null value constraint change and dictionary enumeration value change. This solves the problem of low accuracy of field change impact analysis results caused by change analysis based on a single component in related technologies, and achieves the technical effect of improving the accuracy of field change impact analysis results.
[0111] Optionally, in the field change impact analysis device provided in this application embodiment, the device further includes: an extraction unit, used to perform syntactic structure parsing on the source code, front-end page file, database definition script, and stored procedure definition of the target system through a semantic parsing engine before performing cross-component parallel scanning of the target field based on the field semantic knowledge base through a cross-component tracker, and extracting the field definitions from the source code, front-end page file, database definition script, and stored procedure definition; a filtering unit, used to filter out candidate financial status fields from the field definitions; a construction unit, used to analyze the value patterns of the candidate financial status fields and construct a directed transition relationship graph between the state values of the candidate financial status fields according to the value patterns; and a second generation unit, used to generate a field semantic knowledge base based on the field name, component, business semantic tag, state value enumeration set, and directed transition relationship graph of the candidate financial status fields.
[0112] Optionally, in the field change impact analysis device provided in this application embodiment, the identification unit 401 includes: a first identification module, used to parse the business logic layer code of the target system, locate the physical usage points of the target field in class attribute definition, method parameter declaration and data access mapping, and analyze the control flow statements in the business logic layer code according to the state transition rules in the field semantic knowledge base to identify the logical dependency points that depend on the target field; a second identification module, used to parse the view presentation layer page file of the target system to identify the logical dependency points that depend on the target field; and a third identification module, used to parse the data persistence layer database definition file of the target system to identify the physical usage points of the target field in table column structure definition and stored procedure parameters.
[0113] Optionally, in the field change impact analysis device provided in this application embodiment, the first generation unit 402 includes: a processing module, used to perform name normalization processing on the original field identifier of the physical usage point and the original field identifier of the logical dependency point to obtain a normalized identifier; a first calculation module, used to calculate the semantic similarity score between the normalized identifier and the standard identifier of the target field according to the naming variant list in the field semantic knowledge base, and determine the identifier with a semantic similarity score greater than a preset similarity threshold as the identifier of the associated reference of the target field, wherein the naming variant list includes a set of synonym field names of the target field; a first determination module, used to calculate the relevance of a preset association point corresponding to each associated reference identifier, and determine the preset association point with a relevance greater than a preset relevance threshold as the target association point; and a second determination module, used to determine the standard identifier of the target field as the primary key, determine the target association point as a child node, and generate a field mapping object.
[0114] Optionally, in the field change impact analysis device provided in this application embodiment, the analysis unit 403 includes: a checking module, used to check whether the current length of the target associated point in the field mapping object is less than the new length in the change definition information when the change type of the target field is a field length change, and to determine that the target associated point whose current length is less than the new length is an incompatible associated point; a second calculation module, used to calculate the accuracy loss ratio of each target associated point after the data type change when the change type of the target field is a data type change, and to determine that the target associated point whose accuracy loss ratio is greater than a preset accuracy loss threshold is an incompatible associated point; and a third determination module, used to scan when the change type of the target field is a null value constraint change. The code logic of the target association points in the field mapping object determines that target association points that depend on non-empty logic are incompatible association points; the fourth determination module is used to calculate the field mapping coverage of each target association point when the change type of the target field is a dictionary enumeration value change, and determines the target association points whose field mapping coverage is less than a preset threshold as incompatible association points; the third calculation module is used to calculate the change risk value based on the proportion of incompatible association points to all target association points and the business impact coefficient of the target field, and determine the change risk level of the target field based on the change risk value; the fifth determination module is used to determine the modification suggestion for each incompatible association point, and generate the change impact analysis result based on the incompatible association points, change risk level, and modification suggestion.
[0115] Optionally, in the field change impact analysis device provided in the embodiments of this application, the first determining module includes: an acquisition submodule, used to acquire the call frequency of a preset association point within a preset time window; a determining submodule, used to determine the business weight of the business module to which the preset association point belongs based on the business semantic tags in the field semantic knowledge base; and a calculation submodule, used to multiply the call frequency by the business weight to calculate the association degree of the preset association point.
[0116] Optionally, in the field change impact analysis device provided in this application embodiment, the device further includes: a third generation unit, used to generate a field topology map based on the dependency relationship between the target field and the target related points after generating change impact analysis results according to incompatible related points, change risk levels and modification suggestions; a calculation unit, used to calculate the related point risk value of each target related point according to four dimensions: technical impact, business impact, probability of occurrence and repair cost, using a four-dimensional risk matrix model, and mapping the related point risk value to the related point risk level; a fourth generation unit, used to group and aggregate the target related points according to component type, file path and related point risk level, count the number of risk points or average comprehensive risk score in each group, map the statistical results to a preset color gradient, and generate a risk heat map; and a fifth generation unit, used to generate a change impact analysis report based on the field topology map, risk heat map and change impact analysis results.
[0117] It should be noted that the identification unit 401, the first generation unit 402, and the analysis unit 403 mentioned above correspond to steps S201 to S203 in Embodiment 1. The three units and the corresponding steps implement the same instances and application scenarios, but are not limited to the content disclosed in Embodiment 1. It should be noted that the above modules or units can be hardware or software components stored in memory (e.g., memory 104) and processed by one or more processors (e.g., processors 102a, 102b, ..., 102n). The above modules can also be part of a device and run in the computer terminal 10 provided in Embodiment 1.
[0118] Example 3
[0119] Embodiments of this application may provide a computer terminal, which may be any computer terminal device in a group of computer terminals. Optionally, in this embodiment, the aforementioned computer terminal may also be replaced with a mobile terminal or an electronic device, etc.
[0120] Optionally, in this embodiment, the computer terminal may be located in at least one of a plurality of network devices in a computer network.
[0121] In this embodiment, the computer terminal described above can execute the program code for the following steps in the field change impact analysis method: obtaining the change definition information of the target field to be analyzed, and performing cross-component parallel scanning of the target field based on the field semantic knowledge base through a cross-component tracker to identify the physical usage points and logical dependency points of the target field in the business logic layer, view presentation layer, and data persistence layer; performing fusion processing on the physical usage points and logical dependency points to generate a field mapping object containing full dependency information; and performing multidimensional impact analysis on the change of the target field based on the change definition information, the field mapping object, and the field semantic knowledge base to generate change impact analysis results. The multidimensional impact analysis includes a compatibility check for preset change types, which include at least one of field length change, data type change, null value constraint change, and dictionary enumeration value change.
[0122] Optionally, the aforementioned computer terminal can execute the program code for the following steps in the field change impact analysis method: Before performing cross-component parallel scanning of the target field based on the field semantic knowledge base through the cross-component tracker, the method further includes: parsing the syntax structure of the source code, front-end page files, database definition scripts, and stored procedure definitions of the target system through a semantic parsing engine, and extracting field definitions from the source code, front-end page files, database definition scripts, and stored procedure definitions; filtering candidate financial status fields from the field definitions; analyzing the value patterns of the candidate financial status fields, and constructing a directed transition relationship graph between the state values of the candidate financial status fields based on the value patterns; and generating a field semantic knowledge base based on the field name, component, business semantic tag, state value enumeration set, and directed transition relationship graph of the candidate financial status fields.
[0123] Optionally, the aforementioned computer terminal can execute the program code for the following steps in the field change impact analysis method: Performing a cross-component parallel scan of the target field using a cross-component tracker based on a field semantic knowledge base, identifying the physical usage points and logical dependencies of the target field in the business logic layer, view presentation layer, and data persistence layer, including: parsing the business logic layer code of the target system, locating the physical usage points of the target field in class attribute definitions, method parameter declarations, and data access mappings, and analyzing the control flow statements in the business logic layer code according to the state transition rules in the field semantic knowledge base to identify logical dependencies on the target field; parsing the view presentation layer page files of the target system to identify logical dependencies on the target field; and parsing the database definition files of the data persistence layer of the target system to identify the physical usage points of the target field in table column structure definitions and stored procedure parameters.
[0124] Optionally, the aforementioned computer terminal can execute the program code for the following steps in the field change impact analysis method: merging physical usage points and logical dependency points to generate a field mapping object containing full dependency information, including: normalizing the names of the original field identifiers of physical usage points and logical dependency points to obtain normalized identifiers; calculating the semantic similarity score between the normalized identifier and the standard identifier of the target field based on the named variant list in the field semantic knowledge base, and determining identifiers with semantic similarity scores greater than a preset similarity threshold as identifiers of associated references to the target field, wherein the named variant list includes a set of synonymous field names of the target field; calculating the relevance of a preset associated point corresponding to each associated reference identifier, and determining preset associated points with relevance scores greater than a preset relevance threshold as target associated points; determining the standard identifier of the target field as the primary key, determining the target associated points as child nodes, and generating a field mapping object.
[0125] Optionally, the aforementioned computer terminal can execute the program code for the following steps in the field change impact analysis method: Based on the change definition information, field mapping objects, and field semantic knowledge base, perform a multi-dimensional impact analysis on the target field change, generating change impact analysis results including: If the target field change type is a field length change, check whether the current length of the target association point in the field mapping object is less than the new length in the change definition information, and determine that the target association point whose current length is less than the new length is an incompatible association point; if the target field change type is a data type change, calculate the accuracy loss ratio of each target association point after the data type change, and determine that the target association point whose accuracy loss ratio is greater than a preset accuracy loss threshold is incompatible. For each target field, when the change type is a null constraint change, the code logic of the target related points in the field mapping object is scanned to identify those that depend on non-null logic as incompatible related points. When the change type is a dictionary enumeration value change, the field mapping coverage of each target related point is calculated, and those with a field mapping coverage less than a preset threshold are identified as incompatible related points. Based on the proportion of incompatible related points to all target related points and the business impact coefficient of the target field, the change risk value is calculated, and the change risk level of the target field is determined based on the change risk value. Modification suggestions are determined for each incompatible related point, and change impact analysis results are generated based on the incompatible related points, change risk level, and modification suggestions.
[0126] Optionally, the computer terminal described above can execute the program code for the following steps in the field change impact analysis method: calculating the correlation degree of the preset correlation point corresponding to the identifier of each associated reference includes: obtaining the call frequency of the preset correlation point within a preset time window; determining the business weight of the business module to which the preset correlation point belongs based on the business semantic tags in the field semantic knowledge base; multiplying the call frequency by the business weight to calculate the correlation degree of the preset correlation point.
[0127] Optionally, the aforementioned computer terminal can execute the program code for the following steps in the field change impact analysis method: After generating change impact analysis results based on incompatible related points, change risk levels, and modification suggestions, the method further includes: using a force-directed layout algorithm to generate a field topology diagram based on the dependency relationships between target fields and target related points; using a four-dimensional risk matrix model to calculate the related point risk value for each target related point based on four dimensions: technical impact, business impact, probability of occurrence, and repair cost, and mapping the related point risk value to the related point risk level; grouping and aggregating target related points according to component type, file path, and related point risk level, counting the number of risk points or average comprehensive risk score within each group, mapping the statistical results to a preset color gradient, and generating a risk heatmap; and generating a change impact analysis report based on the field topology diagram, risk heatmap, and change impact analysis results.
[0128] Optionally, Figure 5 This is a structural block diagram of an electronic device according to an embodiment of this application. Figure 5 As shown, the electronic device may include: one or more ( Figure 5 (Only one is shown) processor 502, memory 504, memory controller, and peripheral interface, wherein the peripheral interface is connected to the radio frequency module, audio module and display.
[0129] The memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the field change impact analysis method and apparatus in this application embodiment. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, thereby realizing the aforementioned field change impact analysis method. The memory may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include memory remotely located relative to the processor, and these remote memories can be connected to the terminal via a network. Examples of the aforementioned networks include at least one of the following: the Internet, corporate intranet, local area network, mobile communication network, and combinations thereof.
[0130] The processor can access the information and application programs stored in the memory via the transmission device to perform the steps described above in the method for analyzing the impact of changes to the aforementioned fields.
[0131] This application provides a scheme for analyzing the impact of field changes. By acquiring the change definition information of the target field to be analyzed, and using a cross-component tracker to perform parallel cross-component scanning of the target field based on a field semantic knowledge base, the scheme identifies the physical usage points and logical dependencies of the target field in the business logic layer, view presentation layer, and data persistence layer. The physical usage points and logical dependencies are then fused to generate a field mapping object containing full dependency information. Based on the change definition information, the field mapping object, and the field semantic knowledge base, a multi-dimensional impact analysis is performed on the changes to the target field, generating change impact analysis results. The multi-dimensional impact analysis includes a compatibility check for preset change types, which include at least one of field length changes, data type changes, null value constraint changes, and dictionary enumeration value changes. This solves the technical problem in related technologies where change analysis based on a single component leads to low accuracy in the field change impact analysis results, thus improving the accuracy of the field change impact analysis results.
[0132] Those skilled in the art will understand that Figure 5 The structure shown is for illustrative purposes only. Electronic devices can also be smartphones, tablets, handheld computers, mobile internet devices (MIDs), PADs, and other terminal devices. Figure 5 This does not limit the structure of the aforementioned electronic device. For example, electronic devices may also include components that are more... Figure 5 The more or fewer components shown (such as network interfaces, display devices, etc.), or having the same Figure 5 The different configurations shown.
[0133] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing the hardware related to the terminal device. The program can be stored in a computer-readable storage medium, which may include: flash drive, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.
[0134] Example 4
[0135] Embodiments of this application also provide a storage medium. Optionally, in this embodiment, the storage medium can be used to store the program code executed by the field change impact analysis method provided in Embodiment 1.
[0136] Optionally, in this embodiment, the storage medium may be located in any computer terminal in a group of computer terminals in a computer network, or in any mobile terminal in a group of mobile terminals.
[0137] This application also provides a computer program product that, when executed on a data processing device, is suitable for performing steps of a method for analyzing the impact of field changes.
[0138] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.
[0139] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0140] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection of units or modules may be electrical or other forms.
[0141] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0142] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0143] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.
[0144] The above are merely preferred embodiments of this application. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of this application, and these improvements and modifications should also be considered within the scope of protection of this application.
Claims
1. A method of change impact analysis of a field, characterized by, include: Obtain the change definition information of the target field to be analyzed, and perform cross-component parallel scanning of the target field based on the field semantic knowledge base through the cross-component tracker to identify the physical usage points and logical dependencies of the target field in the business logic layer, view presentation layer and data persistence layer; The physical usage points and the logical dependency points are merged to generate a field mapping object containing full dependency information; Based on the change definition information, the field mapping object, and the field semantic knowledge base, a multidimensional impact analysis is performed on the change of the target field to generate change impact analysis results. The multidimensional impact analysis includes a compatibility check for preset change types, which include at least one of field length change, data type change, null value constraint change, and dictionary enumeration value change.
2. The method according to claim 1, characterized in that, Before performing cross-component parallel scanning of the target field based on a field semantic knowledge base using a cross-component tracker, the method further includes: The semantic parsing engine performs syntactic structure parsing on the source code, front-end page files, database definition scripts, and stored procedure definitions of the target system, and extracts the field definitions from the source code, front-end page files, database definition scripts, and stored procedure definitions; Candidate financial status fields are obtained by filtering from the field definitions; Analyze the value patterns of the candidate financial state fields, and construct a directed transition relationship graph between the state values of the candidate financial state fields based on the value patterns; The field semantic knowledge base is generated based on the field name, component, business semantic tag, state value enumeration set, and directed transition relationship graph of the candidate financial state field.
3. The method according to claim 1, characterized in that, By using a cross-component tracker to perform parallel cross-component scanning of the target field based on a field semantic knowledge base, the physical usage points and logical dependencies of the target field in the business logic layer, view presentation layer, and data persistence layer are identified, including: The business logic layer code of the target system is parsed to locate the physical usage points of the target field in class attribute definition, method parameter declaration and data access mapping. The control flow statements in the business logic layer code are analyzed according to the state transition rules in the field semantic knowledge base to identify the logical dependency points that depend on the target field. The view presentation layer page files of the target system are parsed to identify logical dependency points that depend on the target field; The database definition file of the data persistence layer of the target system is parsed to identify the physical usage points of the target field in the table column structure definition and stored procedure parameters.
4. The method according to claim 1, characterized in that, The physical usage points and logical dependency points are fused together to generate a field mapping object containing full dependency information, including: The original field identifiers of the physical usage points and the original field identifiers of the logical dependency points are normalized to obtain normalized identifiers. Based on the naming variant list in the field semantic knowledge base, the semantic similarity score between the normalized identifier and the standard identifier of the target field is calculated, and the identifier with a semantic similarity score greater than a preset similarity threshold is determined as the identifier of the associated reference of the target field, wherein the naming variant list includes a set of synonym field names of the target field; Calculate the correlation degree of the preset correlation point corresponding to the identifier of each associated reference, and determine the preset correlation point with the correlation degree greater than the preset correlation degree threshold as the target correlation point; The standard identifier of the target field is determined as the primary key, the target association point is determined as the child node, and the field mapping object is generated.
5. The method according to claim 4, characterized in that, Based on the change definition information, the field mapping object, and the field semantic knowledge base, a multidimensional impact analysis is performed on the change of the target field, generating change impact analysis results including: If the change type of the target field is a field length change, check whether the current length of the target associated point in the field mapping object is less than the new length in the change definition information, and determine that the target associated point whose current length is less than the new length is an incompatible associated point; When the change type of the target field is a data type change, calculate the accuracy loss ratio of each target association point after the data type change, and determine the target association points whose accuracy loss ratio is greater than the preset accuracy loss threshold as incompatible association points; When the change type of the target field is a null constraint change, scan the code logic of the target association point in the field mapping object to determine that the target association point that depends on the non-null logic is an incompatible association point; When the change type of the target field is a dictionary enumeration value change, calculate the field mapping coverage of each target association point, and determine the target association points with a field mapping coverage of less than a preset threshold as incompatible association points; Based on the proportion of incompatible related points to all target related points and the business impact coefficient of the target field, the change risk value is calculated, and the change risk level of the target field is determined based on the change risk value. Determine modification suggestions for each incompatible correlation point, and generate the change impact analysis results based on the incompatible correlation point, the change risk level, and the modification suggestions.
6. The method according to claim 4, characterized in that, The degree of association for each associated reference's identifier corresponding to a preset association point is calculated as follows: Obtain the call frequency of the preset associated point within a preset time window; Based on the business semantic tags in the field semantic knowledge base, determine the business weight of the business module to which the preset association point belongs; The relevance of the preset association point is calculated by multiplying the call frequency by the business weight.
7. The method according to claim 5, characterized in that, After generating the change impact analysis results based on the incompatible correlation points, the change risk level, and the modification suggestions, the method further includes: A force-directed layout algorithm is used to generate a field topology graph based on the dependency relationships between the target field and the target associated points. Using a four-dimensional risk matrix model, the associated risk value of each target associated point is calculated based on four dimensions: technological impact, business impact, probability of occurrence, and repair cost. The associated risk value is then mapped to the associated risk level. The target associated points are grouped and aggregated according to component type, file path and risk level of associated points. The number of risk points or average comprehensive risk score in each group is counted. The statistical results are mapped to a preset color gradient to generate a risk heat map. Based on the field topology diagram, the risk heatmap, and the change impact analysis results, a change impact analysis report is generated.
8. A device for analyzing the impact of field changes, characterized in that, include: The identification unit is used to obtain the change definition information of the target field to be analyzed, and to perform cross-component parallel scanning of the target field based on the field semantic knowledge base through the cross-component tracker to identify the physical usage points and logical dependencies of the target field in the business logic layer, view presentation layer and data persistence layer. The first generation unit is used to fuse the physical usage points and the logical dependency points to generate a field mapping object containing full dependency information. The analysis unit is used to perform multidimensional impact analysis on the change of the target field based on the change definition information, the field mapping object and the field semantic knowledge base, and generate change impact analysis results. The multidimensional impact analysis includes a compatibility check for preset change types, which include at least one of field length change, data type change, null value constraint change and dictionary enumeration value change.
9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored executable program, wherein, when the executable program is executed, it controls the device on which the computer-readable storage medium is located to perform the field change impact analysis method according to any one of claims 1 to 7.
10. An electronic device, characterized in that, include: Memory, which stores executable programs; A processor for running the program, wherein the program, when running, performs the method for analyzing the impact of field changes as described in any one of claims 1 to 7.
11. A computer program product comprising computer instructions, characterized in that, When the computer instructions are executed by the processor, they implement the steps of the method for analyzing the impact of field changes as described in any one of claims 1 to 7.
