CN117389601A

CN117389601A - Financial software influence traceability analysis method, device, equipment and storage medium

Info

Publication number: CN117389601A
Application number: CN202311099332.5A
Authority: CN
Inventors: 金洋旭
Original assignee: Bank of China Ltd
Current assignee: Bank of China Ltd
Priority date: 2023-08-29
Filing date: 2023-08-29
Publication date: 2024-01-12

Abstract

The application relates to a financial software influence traceability analysis method, a financial software influence traceability analysis device, financial software influence traceability analysis equipment and a financial software influence traceability storage medium. And outputting software influence content and corresponding software composition influence objects after recursively analyzing the target software maintenance information based on the data flow relation between the target software composition object and a plurality of other software composition objects and the associated software maintenance information with the association relation in the target software maintenance information and a plurality of other software maintenance information by the influence traceability analysis model, and determining influence traceability analysis results of the target software composition object according to the target software composition object, the software composition influence objects and the software operation influence information. Compared with the traditional influence tracing method through manually analyzing the financial software, the influence tracing method and the influence tracing device have the advantages that the influence tracing method and the influence tracing device conduct recursion the influence relationship among the software composition objects, influence tracing is conducted on the software composition objects in the financial software, and complexity of influence tracing of the financial software is reduced.

Description

Financial software influence traceability analysis method, device, equipment and storage medium

Technical Field

The present invention relates to the technical field of financial software, and in particular, to a method, an apparatus, a computer device, a storage medium and a computer program product for traceability analysis of financial software influence.

Background

With the development of computer technology, banking software is introduced at present, and portable financial business handling modes are provided for users. When the financial software is developed, the influence among all functional modules in the software system needs to be considered, namely, the influence traceability analysis needs to be carried out on various objects in the financial software so as to improve the development stability of the financial software. At present, the tracing analysis of the financial software is usually performed by a manual investigation mode, however, the influence of each object in the financial software is traced by manual analysis, and the analysis complexity is high.

Therefore, the existing influence traceability analysis method of the financial software has the defect of high complexity.

Disclosure of Invention

In view of the foregoing, it is desirable to provide a financial software influence traceability analysis method, apparatus, computer device, computer readable storage medium and computer program product that can reduce analysis complexity.

In a first aspect, the present application provides a method for analyzing financial software influence tracing, where the method includes:

responding to an influence traceability analysis request aiming at a target software component object in financial software, and acquiring pre-input target software maintenance information corresponding to the target software component object and a plurality of pre-input other software maintenance information corresponding to a plurality of other software component objects; the other software component objects represent software component objects except the target software component object in the software component objects corresponding to the financial software;

Inputting the target software maintenance information and the plurality of other software maintenance information into an influence traceability analysis model, and acquiring software operation influence information corresponding to the target software composition object and software composition influence objects corresponding to the software operation influence information output by the influence traceability analysis model; the influence traceability analysis model is used for carrying out recursion analysis on the target software maintenance information according to the data flow relation between the target software component object and the plurality of other software component objects and the associated software maintenance information with the association relation in the target software maintenance information and the plurality of other software maintenance information;

and determining an influence traceability analysis result of the target software composition object in the financial software according to the target software composition object, the software composition influence object and the software operation influence information.

In one embodiment, the method further comprises:

responding to a maintenance instruction aiming at the financial software, and displaying a software maintenance page corresponding to the financial software; the software maintenance page comprises a plurality of software component objects and a plurality of pre-recorded software maintenance information corresponding to the plurality of software component objects;

Responding to trigger information of the influence traceability analysis instruction in the software maintenance page, and displaying the plurality of software composition objects on the influence traceability analysis page;

and responding to the trigger information of the object formed by the target software in the influence traceability analysis page, and determining to trigger the influence traceability analysis request.

In one embodiment, the method further comprises:

responding to trigger information aiming at a target software composition object in the software maintenance page, and displaying a software maintenance information inquiry page corresponding to the target software composition object; the software maintenance information inquiry page comprises a plurality of software maintenance information inquiry fields corresponding to the target software composition object;

when software maintenance query information input for the plurality of software maintenance information query fields is detected, acquiring a software maintenance information input page corresponding to the software maintenance query information and displaying the software maintenance information input page;

and acquiring target software maintenance information corresponding to the target software composition object input in the software maintenance information input page, and acquiring the target software maintenance information input in advance.

In one embodiment, the software composition object includes at least two of: module objects, function objects, interface objects, data table objects and file objects;

The obtaining the target software maintenance information corresponding to the target software composition object input in the software maintenance information input page includes:

if the object formed by the target software is a module object, acquiring the module name, the module type and the module content description information input in the software maintenance information input page as target software maintenance information;

and/or the number of the groups of groups,

if the target software composition object is a functional object, acquiring the function name, the function type and the function action description information input in the software maintenance information input page, and taking the function name, the function type and the function action description information as target software maintenance information;

and/or the number of the groups of groups,

if the object formed by the target software is an interface object, acquiring the interface name, the interface type and the interface function description information input in the software maintenance information input page as target software maintenance information;

and/or the number of the groups of groups,

if the object formed by the target software is a data table object, acquiring a data table name, data table function description information and a data table and interface relation which are input in the software maintenance information input page, and taking the data table name, the data table function description information and the data table and interface relation as target software maintenance information;

and/or the number of the groups of groups,

and if the object formed by the target software is a file object, acquiring the file name, the file type, the relation between the file and the data table, the file function description information and the object to which the file belongs, which are input in the software maintenance information input page, and taking the file name, the file type, the file and the data table relation, the file function description information and the object to which the file belongs as the target software maintenance information.

In one embodiment, the inputting the target software maintenance information and the plurality of other software maintenance information into the influence traceability analysis model includes:

inputting the target software maintenance information and the plurality of other software maintenance information into an influence traceability analysis model, taking the target software component object as a software component object to be analyzed by the influence traceability analysis model, and determining an upstream object and a downstream object of the software component object to be analyzed based on a data flow relation between the software component object to be analyzed and the plurality of other software component objects; the upstream object characterizes an object of which the software component object to be analyzed receives data, and the downstream object characterizes an object of which the software component object to be analyzed sends data;

if the software maintenance information of the upstream object and/or the software maintenance information of the downstream object is detected according to the target software maintenance information, the associated software maintenance information which has an association relation with the target software maintenance information exists, and the software operation influence information of the associated software maintenance information on the target software maintenance information is obtained;

And returning the upstream object and/or the downstream object corresponding to the associated software maintenance information as a new software composition object to be analyzed, determining the upstream object and the downstream object of the software composition object to be analyzed based on the data flow relation between the software composition object to be analyzed and the plurality of other software composition objects, recursively analyzing the plurality of other software composition objects, and outputting software operation influence information corresponding to the target software composition object and software composition influence objects corresponding to the software operation influence information.

In one embodiment, the determining the result of the traceability analysis of the influence of the target software component object in the financial software according to the target software component object, the software component influence object and the software operation influence information includes:

acquiring a target data flow relation between the target software composition object and the software composition influence object;

generating a traceability relationship tree diagram according to a plurality of nodes, node contents of the nodes and the target data stream relationship; a plurality of nodes in the traceability relationship tree diagram are determined according to the target software composition object and the software composition influence object, and the nodes are determined according to the software operation influence information corresponding to the nodes of each software composition influence object;

And determining an influence traceability analysis result based on the traceability relation tree diagram.

In a second aspect, the present application provides a financial software influence traceability analysis device, the device comprising:

the acquisition module is used for responding to an influence traceability analysis request aiming at a target software composition object in the financial software, and acquiring pre-input target software maintenance information corresponding to the target software composition object and a plurality of pre-input other software maintenance information corresponding to a plurality of other software composition objects; the other software component objects represent software component objects except the target software component object in the software component objects corresponding to the financial software;

the input module is used for inputting the target software maintenance information and the plurality of other software maintenance information into an influence traceability analysis model, and acquiring software operation influence information corresponding to the target software composition object and software composition influence objects corresponding to the software operation influence information output by the influence traceability analysis model; the influence traceability analysis model is used for carrying out recursion analysis on the target software maintenance information according to the data flow relation between the target software component object and the plurality of other software component objects and the associated software maintenance information with the association relation in the target software maintenance information and the plurality of other software maintenance information;

And the analysis module is used for determining an influence traceability analysis result of the target software composition object in the financial software according to the target software composition object, the software composition influence object and the software operation influence information.

In a third aspect, the present application provides a computer device comprising a memory storing a computer program and a processor implementing the steps of the method described above when the processor executes the computer program.

In a fourth aspect, the present application provides a computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of the method described above.

In a fifth aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements the steps of the method described above.

According to the financial software influence traceability analysis method, the financial software influence traceability analysis device, the financial software influence traceability analysis computer device, the financial software storage medium and the financial software program product, the target software maintenance information and the plurality of other software maintenance information are input into the influence traceability analysis model, the model is used for determining the influence traceability analysis result of the target software composition object based on the data flow relation between the target software composition object and the plurality of other software composition objects and the associated software maintenance information with the association relation in the target software maintenance information and the plurality of other software maintenance information, the software influence content and the corresponding software composition influence object are output after the target software maintenance information is subjected to recursive analysis, and the influence traceability analysis result of the target software composition object is determined according to the target software composition object, the software composition influence object and the software operation influence information. Compared with the traditional influence tracing method through manually analyzing the financial software, the influence tracing method and the influence tracing device have the advantages that the influence tracing method and the influence tracing device conduct recursion the influence relationship among the software composition objects, influence tracing is conducted on the software composition objects in the financial software, and complexity of influence tracing of the financial software is reduced.

Drawings

FIG. 1 is a flow chart of a method for tracing analysis of financial software effects in one embodiment;

FIG. 2 is an interface diagram of a module maintenance step in one embodiment;

FIG. 3 is an interface diagram of a function maintenance step in one embodiment;

FIG. 4 is an interface diagram of an interface maintenance step in one embodiment;

FIG. 5 is an interface diagram of a file maintenance step in one embodiment;

FIG. 6 is a block diagram of a financial software impact traceability analysis device according to one embodiment;

fig. 7 is an internal structural diagram of a computer device in one embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.

In one embodiment, as shown in fig. 1, a method for analyzing financial software influence tracing is provided, and the embodiment is applied to a terminal for illustration by the method, it can be understood that the method can also be applied to a server, and can also be applied to a system including the terminal and the server, and implemented through interaction between the terminal and the server, and includes the following steps:

Step S202, in response to an influence traceability analysis request for a target software component object in financial software, acquiring pre-input target software maintenance information corresponding to the target software component object and a plurality of other pre-input software maintenance information corresponding to a plurality of other software component objects; the other software component objects represent software component objects except the target software component object in the software component objects corresponding to the financial software.

The financial software may be a banking software, and the financial software may be composed of a plurality of software constituent objects, which may be program components of the financial software, such as modules, functions, interfaces, data tables, files, and the like of the financial software. Wherein, a plurality of software component objects of the financial software have an interactive relation, for example, when one software component object is abnormal, the operation of other software component objects in the financial software can be influenced. Therefore, in order to ensure the normal operation of the financial software, the mutual influence relationship among the software constituent objects in the financial software needs to be traced and analyzed.

The manager of the financial software can trigger an influence traceability analysis request to the financial software at the system management interface. For example, the terminal displays each software component object of the financial software on the system management page, and after detecting the triggering information of the manager on the target software component object, the terminal can determine that the influence traceability analysis request aiming at the target software component object in the financial software is detected. The terminal may acquire the target software maintenance information input in advance corresponding to the target software component object and the plurality of other software maintenance information input in advance corresponding to the plurality of other software component objects. The other software component objects represent software component objects outside the target software component object among a plurality of software component objects corresponding to the financial software. The target software maintenance information and the plurality of other software maintenance information may each be information entered by a manager at a system interface. The target software maintenance information and the plurality of other software maintenance information may include maintenance information such as attribute information and operation information of the corresponding software component object.

Step S204, inputting the target software maintenance information and a plurality of other software maintenance information into an influence traceability analysis model, and obtaining software operation influence information corresponding to the target software composition object output by the influence traceability analysis model and software composition influence objects corresponding to the software operation influence information; the influence traceability analysis model is used for recursively analyzing the target software maintenance information according to the data flow relation between the target software component object and the plurality of other software component objects and the associated software maintenance information with the association relation in the target software maintenance information and the plurality of other software maintenance information.

The target software component object may be any one of a plurality of software component objects of the financial software terminal. The target software component object has a data flow relation with a plurality of other software component objects, and the data flow relation can be a direct relation or an indirect relation. For example, the target software component object may be referred to as a direct relationship if it directly performs data transmission with other software component objects; the target software component object performs data transmission with other software component objects through a certain software component object, and may be referred to as an indirect relationship. The direct relationship and the indirect relationship may have influence on the operation of the target software component object, and the terminal may identify the influence relationship of other software component objects on the target software component object by training the influence traceability analysis model.

The software maintenance information corresponds to each software composition object, and the terminal can train the influence traceability analysis model to be trained in advance. For example, the terminal inputs software maintenance sample information of a software component object into an influence traceability analysis model to be trained, the influence traceability analysis model carries out recursion analysis on the software maintenance sample information based on associated software maintenance information with association relations among the software maintenance sample information and a plurality of other software component objects and data flow relations among a target software component object and a plurality of other software component objects, the terminal carries out comparison with corresponding software operation influence sample information based on software operation influence prediction information output by the model and software component influence objects corresponding to the software operation influence prediction information, and model parameters of the influence traceability analysis model to be trained are adjusted according to comparison results until preset training end conditions are met, so that the trained influence traceability analysis model is obtained. The preset training ending condition includes, but is not limited to, that the similarity is greater than or equal to a preset threshold value within preset training times; or the training times reach the preset times.

The influence relation between the target software component object and other software component objects can be determined through the association relation between the software maintenance information corresponding to the software component object, the terminal can input the target software maintenance information and a plurality of other software maintenance information into the influence tracing analysis model, the influence tracing analysis model can carry out recursion analysis on the target software maintenance information according to the data flow relation between the target software component object and the plurality of other software component objects and the association software maintenance information with the association relation in the target software maintenance information and the plurality of other software maintenance information, so that other software maintenance information which directly and indirectly affects the target software maintenance information is identified, and the influence tracing analysis model can output the software operation influence information corresponding to the target software component object and the software operation influence object corresponding to the software operation influence information. The software operation influence information indicates that the content of the target software maintenance information is directly or indirectly influenced in other software maintenance information of other software component objects, and the software component influence object indicates other software component objects which directly or indirectly influence the operation of the target software component objects.

Step S206, determining the influence traceability analysis result of the target software composition object in the financial software according to the target software composition object, the software composition influence object and the software operation influence information.

After determining the target software composition object, the software composition influence object and the corresponding software operation influence information, the terminal can determine an influence traceability analysis result aiming at the target software composition object in the financial software based on the target software composition object, the software composition influence object and the corresponding software operation influence information. The terminal can determine a direct influence relation and an indirect influence relation corresponding to the object formed by the target software according to the data flow relation. The terminal can display the influence traceability analysis result aiming at the object formed by the target software in a tree diagram construction mode.

For example, in one embodiment, the terminal may obtain a target software composition object and a target data flow relationship between software composition influencing objects, determine a plurality of nodes in a traceability relationship tree according to the target software composition object and the software composition influencing object, determine node contents of each node according to software operation influencing information corresponding to the nodes of each software composition influencing object, and generate the traceability relationship tree according to the plurality of nodes, the node contents of each node and the target data flow relationship. Therefore, the terminal can determine the influence tracing analysis result based on the tracing relation tree diagram. Specifically, the terminal may take the target software component object as a root node, and generate a corresponding leaf node according to the target data flow relationship, by using the software component influence object as an influence relationship on the target software component object. The adjacent two nodes in the traceable relation tree graph can represent that a direct influence relation exists between the two nodes, so that influence content of a software composition influence object corresponding to the target software composition object on the target software composition object can be determined according to software operation influence information of the software composition object. Therefore, the terminal can effectively organize software composition objects in financial software, help developers and other related roles to rapidly evaluate requirements and transformation schemes, check data circulation lines, rapidly analyze and respond internal and external transformation, and rapidly position production problems.

In the financial software influence traceability analysis method, the target software maintenance information and the plurality of other software maintenance information are input into the influence traceability analysis model, the model is used for determining the influence traceability analysis result of the target software composition object based on the data flow relation between the target software composition object and the plurality of other software composition objects and the associated software maintenance information with the association relation in the target software maintenance information and the plurality of other software maintenance information, the software influence content and the corresponding software composition influence object are output after the target software maintenance information is subjected to recursion analysis, and the target software composition object, the software composition influence object and the software operation influence information are determined. Compared with the traditional influence tracing method through manually analyzing the financial software, the influence tracing method and the influence tracing device have the advantages that the influence tracing method and the influence tracing device conduct recursion the influence relationship among the software composition objects, influence tracing is conducted on the software composition objects in the financial software, and complexity of influence tracing of the financial software is reduced.

In one embodiment, further comprising: responding to a maintenance instruction for financial software, and displaying a software maintenance page corresponding to the financial software; the software maintenance page comprises a plurality of software composition objects and a plurality of pre-recorded software maintenance information corresponding to the plurality of software composition objects; responding to trigger information aiming at an influence tracing analysis instruction in a software maintenance page, and displaying a plurality of software composition objects on the influence tracing analysis page; and determining a trigger influence traceability analysis request in response to the trigger information aiming at the target software composition object in the influence traceability analysis page.

In this embodiment, the terminal may display a software maintenance page corresponding to the financial software in advance, for example, the terminal responds to a maintenance instruction of a system administrator for the financial software to display the software maintenance page corresponding to the financial software. The software maintenance page may include a plurality of software component objects, and a plurality of pre-recorded software maintenance information corresponding to the plurality of software component objects. Each software component object may correspond to a plurality of software maintenance information.

The software maintenance page is also provided with an influence traceability analysis instruction, the terminal responds to the triggering information of the influence traceability analysis instruction in the software maintenance page by a system manager, the influence traceability analysis page can be displayed, and a plurality of software composition objects corresponding to the financial software are displayed in the page. The system person may select the target software component object from a plurality of software component objects. The terminal responds to the trigger information aiming at the object formed by the target software in the influence traceability analysis page, and can determine the trigger influence traceability analysis request. The target software component object may be one of a plurality of software component objects corresponding to the financial software.

According to the embodiment, the terminal can display the software maintenance page and the influence traceability analysis page in advance, so that the terminal determines the influence traceability analysis on the target software component object by detecting the trigger information of the system manager on the target software component object on the influence traceability analysis page, and the complexity of the influence traceability analysis is reduced.

In one embodiment, further comprising: responding to trigger information aiming at a target software component object in a software maintenance page, and displaying a software maintenance information inquiry page corresponding to the target software component object; the software maintenance information inquiry page comprises a plurality of software maintenance information inquiry fields corresponding to the target software composition object; when software maintenance query information input for a plurality of software maintenance information query fields is detected, acquiring a software maintenance information input page corresponding to the software maintenance query information and displaying the software maintenance information input page; and acquiring target software maintenance information corresponding to the target software composition object input in the software maintenance information input page, and acquiring the target software maintenance information input in advance.

In this embodiment, the terminal may acquire software maintenance information that is entered in advance by a system administrator for a software component object. Taking the example that the terminal acquires the software maintenance information of the object formed by the target software. The target software component object may correspond to a plurality of software maintenance information. The terminal responds to the trigger information aiming at the target software component object in the software maintenance page, and can display the software maintenance information inquiry page corresponding to the target software component object.

The software maintenance information query page may include a plurality of software maintenance information query fields corresponding to the target software component object, where each software maintenance information query field may be used to input different types of software maintenance information. When the terminal detects the software maintenance query information input by the system manager aiming at a plurality of software maintenance information query fields, the terminal can acquire and display a software maintenance information input page corresponding to the software maintenance query information. The system manager can input the target software maintenance information corresponding to the target software composition object in the software maintenance information input page, so that the terminal obtains the target software maintenance information corresponding to the target software composition object input by the system manager in the software maintenance information input page, and obtains the target software maintenance information input in advance. The target software component object may be any one of a plurality of software component objects corresponding to the financial software. Different software component objects may correspond to the same software maintenance information or may contain the same software maintenance information.

According to the embodiment, the terminal can acquire the software maintenance information input by the system manager in the software maintenance information input page of the corresponding software component object, so that the terminal performs influence tracing analysis on the software component object according to the software maintenance information, and the complexity of influence tracing analysis is reduced.

In one embodiment, obtaining the target software maintenance information corresponding to the target software composition object input in the software maintenance information input page includes: if the object formed by the target software is a module object, the module name, the module type and the module content description information input in the software maintenance information input page are obtained and used as the target software maintenance information.

In this embodiment, the plurality of software component objects corresponding to the financial software include at least two of the following: module objects, function objects, interface objects, data table objects, and file objects. The terminal may determine the target software component object and other software component objects from the plurality of software component objects. The corresponding target software maintenance information may be different for different target software composition objects. For example, if the terminal determines that the target software component object is a module object, the terminal may acquire the module name, the module type, and the module content description information input in the software maintenance information entry page as the target software maintenance information.

Specifically, as shown in fig. 2, fig. 2 is an interface schematic diagram of a module maintenance step in one embodiment. The respective software component modules include common information and software maintenance information specific to the software component modules. Wherein the common information represents software maintenance information that each software component module has. For the module object, the specific software maintenance information can be information such as a module name, a module main function description, a module category, a module responsible person, a module high availability level, a module disaster recovery level and the like. The module content description information may include the above-mentioned information such as the module main function description, the module responsible person, the module high availability level, and the module disaster recovery level. The module categories include, but are not limited to, online, batch, receive, send, download, sign-up, etc. the module loaders include, but are not limited to, name, job number, etc. the module high availability levels include, but are not limited to, A5, A4, A3, A2, etc. the module disaster recovery levels include, but are not limited to, T1-A, T1-B, T2, T3, etc. There is also an internal relation between the software component objects, for example, for a module object, the software object associated with it may be a functional object, i.e. the module corresponds to a corresponding function.

The terminal may further obtain target software maintenance information corresponding to the function object when determining that the function object is a target software component object. For example, in one embodiment, if the target software component object is a functional object, the terminal may acquire, as the target software maintenance information, the function name, the function type, and the function action description information input by the system administrator on the software maintenance information entry page.

Specifically, as shown in fig. 3, fig. 3 is an interface schematic diagram of a function maintenance step in one embodiment. When the terminal maintains the function object, the terminal maintains information such as a module, a function name, a function main function description, a function category, a function responsible person, a function online time, a function latest modification time, a function service scene, a function effectiveness requirement and the like. The function action description information may include information such as a function main action description, a function category, a function responsible person, a function online time, a function latest modification time, a function service scene, a function validity requirement, and the like. The function category includes, but is not limited to, online, batch, receive, send, download, sign-up, etc.; the functional responsible person includes but is not limited to information such as name, job number, etc.; the functional service scene comprises, but is not limited to, information such as external supervision, internal service users, public clients, private clients and the like; functional availability requirements include, but are not limited to, month, week, day, time, second, millisecond, etc. information.

And, for the function object, the terminal may determine, according to the software maintenance information, a software component object, such as an interface object and a module object, corresponding to the function object, where the software component object has a direct influence relationship. Specifically, the module object and the function object can be directly influenced by the function category, and the function object and the interface object can be directly influenced by the internal connection. An indirect influence relationship can exist between the module object and the interface object, and specific software influences the content and needs to be analyzed and identified through an influence traceability analysis model.

The terminal can also acquire the target software maintenance information corresponding to the interface object when determining that the interface object is used as the target software component object. For example, in one embodiment, if the target software component object is an interface object, the terminal may obtain, as the target software maintenance information, the interface name, the interface type, and the interface function description information that are input by the system administrator on the software maintenance information input page.

Specifically, as shown in fig. 4, fig. 4 is an interface schematic diagram of an interface maintenance step in one embodiment. Maintenance of the interface object by the terminal includes, but is not limited to, operations such as add-drop-check. The terminal obtains software maintenance information of the interface object, including but not limited to an interface upstream and downstream type, an interface technology type, an interface name, an interface function description, an interface specific definition, a system list of an interface service, an interface importance degree, interface responsible person information, an interface and upstream external data table relation, an interface and internal data table relation and the like. The interface type comprises information such as an interface upstream type, an interface downstream type, an interface technology type and the like; the interface function description information comprises interface function description, interface concrete definition, a system list of interface service, interface importance degree, interface responsible person information, interface and upstream external data table relation, interface and internal data table association and other information. The upstream and downstream types of the interface include, but are not limited to, upstream, downstream, internal, etc. information; interface specific definition includes, but is not limited to json format, file format, etc.; the list of systems of the interface service includes, but is not limited to, a plurality of systems; interface importance includes, but is not limited to, high, medium, low, etc. The functional object and the interface object may be directly associated based on the interface to which the function is associated, i.e. the functional object and the interface object may directly influence each other.

And the terminal can also acquire the target software maintenance information corresponding to the data table object when determining the data table object as the target software composition object. For example, in one embodiment, if the target software component object is a data table object, the terminal may obtain, as the target software maintenance information, the data table name, the data table function description information, and the data table-to-interface relationship input by the system administrator on the software maintenance information entry page.

Specifically, the data table may be a system database corresponding to financial software. Software maintenance information for data table objects includes, but is not limited to, table names, field definitions, table function descriptions, inter-table relationships, data table and interface relationships. The data table function description information comprises the table function description and the table relation; the relationships between tables include, but are not limited to, up-down processing dependencies, associations, and the like. According to the embodiment, the data table object and the interface object have a direct association relationship, namely the data table object and the interface object can directly mutually influence each other to operate.

In addition, the terminal can also acquire the target software maintenance information corresponding to the file object when determining that the file object is used as the target software composition object. For example, in one embodiment, if the object formed by the target software is a file object, the terminal may obtain, as the target software maintenance information, a file name, a file type, a file-to-data table relationship, file function description information, and an object to which the file belongs, which are input by the system administrator on the software maintenance information entry page.

Specifically, as shown in fig. 5, fig. 5 is an interface schematic diagram of a file maintenance step in one embodiment. The software maintenance information of the file object is recorded in the page, and the contained information can be file name, file action category, file and table relationship, file data volume, file increment type, file function description, system to which the file belongs, and the like. The file function description information comprises the file data volume, the file increment type, the file function description and the like. File delta types include, but are not limited to, delta and delta. The file action category comprises a receiving upstream category, a service downstream category and the like; the file system includes a corresponding upstream system, etc. As can be seen from FIG. 5, the file object may have a direct influence relationship with the data table object through the file-table relationship; the file object is described by the file function, and a direct influence relation exists between the file object and the function object. Therefore, the influence traceability model can carry out influence traceability analysis on the object formed by the target software based on the direct or indirect influence relation.

Through the embodiment, the terminal acquires different software maintenance information aiming at different software component objects, determines the data flow relation among a plurality of software component objects through the specific software maintenance information, and performs influence traceability analysis on the target software component objects based on the software maintenance information and the data flow relation, thereby reducing the complexity of analysis.

In one embodiment, entering the target software maintenance information and the plurality of other software maintenance information into the impact traceability analysis model includes: inputting the target software maintenance information and a plurality of other software maintenance information into an influence traceability analysis model, taking a target software component object as a software component object to be analyzed by the influence traceability analysis model, and determining an upstream object and a downstream object of the software component object to be analyzed based on a data flow relation between the software component object to be analyzed and the plurality of other software component objects; the upstream object characterizes an object of which the software component object to be analyzed receives data, and the downstream object characterizes an object of which the software component object to be analyzed sends data; if the software maintenance information of the upstream object and/or the software maintenance information of the downstream object is detected according to the target software maintenance information, the associated software maintenance information which has an association relation with the target software maintenance information exists, and the software operation influence information of the associated software maintenance information on the target software maintenance information is obtained; and returning the upstream object and the downstream object corresponding to the associated software maintenance information as new software composition objects to be analyzed, determining the upstream object and the downstream object of the software composition objects to be analyzed based on the data flow relation between the software composition objects to be analyzed and a plurality of other software composition objects, recursively analyzing the plurality of other software composition objects, and outputting software operation influence information corresponding to the target software composition objects and software composition influence objects corresponding to the software operation influence information.

In this embodiment, the terminal may perform the influence tracing analysis on the object formed by the target software by using the influence tracing analysis model. The terminal can input the target software maintenance information and a plurality of other software maintenance information into the influence traceability analysis model, and the influence traceability analysis model performs repeated iterative analysis. The influence traceability analysis model takes the input target software component object as the current software component object to be analyzed, and can determine an upstream object and a downstream object of the software component object to be analyzed based on the data flow relation between the software component object to be analyzed and a plurality of other software component objects.

The upstream object characterizes an object of receiving data by the software component object to be analyzed, namely, the upstream object can send data to the target software component object; the downstream object characterizes the object of the data transmitted by the software component object to be analyzed, i.e. the downstream object can receive the data transmitted by the target software component object.

The influence traceability analysis model can detect whether associated software maintenance information with an association relation with target software maintenance information exists in the software maintenance information of the upstream object and the software maintenance information of the downstream object. If the influence traceability analysis model detects that the associated software maintenance information with the association relation with the target software maintenance information exists in the software maintenance information of the upstream object and/or the software maintenance information of the downstream object according to the target software maintenance information, the software operation influence information aiming at the target software maintenance information in the associated software maintenance information, such as the associated software maintenance information with direct influence or indirect influence on the target software maintenance information, can be obtained. The terminal uses at least one of the upstream object and the downstream object corresponding to the associated software maintenance information as a new software composition object to be analyzed by influencing the traceability analysis model, and returns to the step of determining the upstream object and the downstream object of the software composition object to be analyzed based on the data flow relation between the software composition object to be analyzed and a plurality of other software composition objects, so that the terminal can recursively analyze a plurality of other software composition objects in the financial software by influencing the traceability analysis model and taking the target software composition object as a starting point.

After recursion analysis is performed on the terminal through the influence traceability analysis model, software operation influence information corresponding to the target software composition object and software composition influence objects corresponding to the software operation influence information can be output. The software running influence information includes information that directly influences the target software component object, and may also include information that indirectly influences the target software component object.

The terminal recursively analyzes the software composition influence objects of all the software composition objects by taking the target software composition objects as starting points through the influence tracing analysis model, and continuously probes the influence scope of all the software composition objects on other software composition objects in a blood relationship mode through the influence tracing analysis model by circularly analyzing until all the objects which are corresponding to the financial software and need to be maintained are identified. And the terminal can also carry out recursion analysis in a depth and breadth mode by influencing the traceability analysis model, and continuously carry out forward and backward exploration analysis in a forward data stream and reverse data stream mode to determine a software composition influence object which directly influences a target software composition object and a software composition influence object which indirectly influences the target software composition object, and the terminal can display the analysis result in a tree diagram mode. Wherein the forward data flow indicates that the analysis of the data flow is followed, for example, detecting the influence of a receiver object corresponding to the sender object on the sender object, etc.; the reverse data flow indicates an analysis of the reverse data flow, for example, detection of an influence of a sender object corresponding to a receiver object on the receiver object, or the like.

The tree diagram displayed by the terminal can comprise all nodes formed by the target software forming object and the software forming influence object and software operation influence information of all the nodes. For example, for a software composition influence object that has a direct influence relationship with a target software composition object, it may be directly connected with the target software composition object; and, the software operation influence information corresponding to the software composition influence object may include what kind of influence is caused to the target software composition object by what kind of information.

According to the embodiment, the terminal can carry out recursion analysis on the influence relation among the plurality of software component objects in the financial software based on the influence traceability analysis model, so that the influence traceability analysis result aiming at the target software component object is obtained, and the complexity of the influence traceability analysis is reduced. In addition, the terminal maintains the context information of the software system interface and the data in a visual mode, displays the blood-cause relationship of the data in a chart form, supports the influence tracing from the software module to the interface to the data file, and improves the data management efficiency of the financial software.

It should be understood that, although the steps in the flowcharts related to the above embodiments are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.

Based on the same inventive concept, the embodiment of the application also provides a financial software influence traceability analysis device for realizing the financial software influence traceability analysis method. The implementation scheme of the solution provided by the device is similar to the implementation scheme recorded in the method, so the specific limitation in the embodiment of the device for tracing the influence of the financial software provided below can be referred to the limitation of the method for tracing the influence of the financial software, which is not repeated here.

In one embodiment, as shown in fig. 6, there is provided a financial software influence traceability analysis device, including: an acquisition module 500, an input module 502, and an analysis module 504, wherein:

the acquiring module 500 is configured to respond to an influence traceability analysis request for a target software component object in financial software, and acquire pre-input target software maintenance information corresponding to the target software component object and a plurality of other pre-input software maintenance information corresponding to a plurality of other software component objects; the other software component objects represent software component objects except the target software component object in the software component objects corresponding to the financial software.

The input module 502 is configured to input the target software maintenance information and the plurality of other software maintenance information into the influence tracing analysis model, obtain software operation influence information corresponding to the target software composition object output by the influence tracing analysis model, and obtain software composition influence objects corresponding to the software operation influence information; the influence traceability analysis model is used for recursively analyzing the target software maintenance information according to the data flow relation between the target software component object and the plurality of other software component objects and the associated software maintenance information with the association relation in the target software maintenance information and the plurality of other software maintenance information.

And the analysis module 504 is configured to determine an influence traceability analysis result of the target software component object in the financial software according to the target software component object, the software component influence object and the software operation influence information.

In one embodiment, the apparatus further comprises: the response module is used for responding to the maintenance instruction for the financial software and displaying a software maintenance page corresponding to the financial software; the software maintenance page comprises a plurality of software composition objects and a plurality of pre-recorded software maintenance information corresponding to the plurality of software composition objects; responding to trigger information aiming at an influence tracing analysis instruction in a software maintenance page, and displaying a plurality of software composition objects on the influence tracing analysis page; and determining a trigger influence traceability analysis request in response to the trigger information aiming at the target software composition object in the influence traceability analysis page.

In one embodiment, the apparatus further comprises: the input module is used for responding to the trigger information aiming at the target software composition object in the software maintenance page and displaying the software maintenance information inquiry page corresponding to the target software composition object; the software maintenance information inquiry page comprises a plurality of software maintenance information inquiry fields corresponding to the target software composition object; when software maintenance query information input for a plurality of software maintenance information query fields is detected, acquiring a software maintenance information input page corresponding to the software maintenance query information and displaying the software maintenance information input page; and acquiring target software maintenance information corresponding to the target software composition object input in the software maintenance information input page, and acquiring the target software maintenance information input in advance.

In one embodiment, the input module is configured to obtain, as the target software maintenance information, the module name, the module type, and the module content description information input in the software maintenance information input page if the target software component object is a module object.

In one embodiment, the input module is configured to obtain, as the target software maintenance information, the function name, the function type, and the function action description information input in the software maintenance information input page if the target software component object is a function object;

In one embodiment, the input module is configured to obtain, as the target software maintenance information, an interface name, an interface type, and interface function description information input in the software maintenance information input page if the target software component object is an interface object;

in one embodiment, the input module is configured to obtain, as the target software maintenance information, a data table name, data table function description information, and a data table-to-interface relationship input in the software maintenance information input page if the target software component object is a data table object;

in one embodiment, the input module is configured to obtain, as the target software maintenance information, a file name, a file type, a file-to-data table relationship, file function description information, and an object to which the file belongs, which are input in the software maintenance information input page, if the target software component object is a file object.

In one embodiment, the input module 502 is configured to input the target software maintenance information and the plurality of other software maintenance information into the influence traceability analysis model, and determine an upstream object and a downstream object of the software component object to be analyzed based on a data flow relationship between the software component object to be analyzed and the plurality of other software component objects by using the target software component object as the software component object to be analyzed by the influence traceability analysis model; the upstream object characterizes an object of which the software component object to be analyzed receives data, and the downstream object characterizes an object of which the software component object to be analyzed sends data; if the software maintenance information of the upstream object and/or the software maintenance information of the downstream object is detected according to the target software maintenance information, the associated software maintenance information which has an association relation with the target software maintenance information exists, and the software operation influence information of the associated software maintenance information on the target software maintenance information is obtained; and returning the upstream object and the downstream object corresponding to the associated software maintenance information as new software composition objects to be analyzed, determining the upstream object and the downstream object of the software composition objects to be analyzed based on the data flow relation between the software composition objects to be analyzed and a plurality of other software composition objects, recursively analyzing the plurality of other software composition objects, and outputting software operation influence information corresponding to the target software composition objects and software composition influence objects corresponding to the software operation influence information.

In one embodiment, the analysis module 504 is configured to obtain a target data flow relationship between a target software component object and a software component influencing object; generating a traceability relationship tree diagram according to the plurality of nodes, the node contents of the plurality of nodes and the target data stream relationship; a plurality of nodes in the traceability relationship tree diagram are determined according to the target software composition object and the software composition influence object, and the nodes are determined according to the software operation influence information corresponding to the nodes of each software composition influence object; and determining an influence traceability analysis result based on the traceability relation tree diagram.

The above-mentioned financial software influence traceability analysis device may be implemented by all or part of each module by software, hardware and a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In one embodiment, a computer device is provided, which may be a terminal, and the internal structure of which may be as shown in fig. 7. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program, when executed by the processor, implements a financial software impact traceability analysis method. The display unit of the computer device is used for forming a visual picture, and can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, can also be a key, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.

It will be appreciated by those skilled in the art that the structure shown in fig. 7 is merely a block diagram of some of the structures associated with the present application and is not limiting of the computer device to which the present application may be applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is provided, including a memory and a processor, where the memory stores a computer program, and the processor implements the financial software impact traceability analysis method described above when executing the computer program.

In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, which when executed by a processor implements the financial software impact traceability analysis method described above.

In one embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the financial software impact traceability analysis method described above.

It should be noted that, user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party.

Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the various embodiments provided herein may include at least two of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magnetic random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (Phase Change Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like. The databases referred to in the various embodiments provided herein may include at least two of a relational database and a non-relational database. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic units, quantum computing-based data processing logic units, etc., without being limited thereto.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The above examples only represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the present application. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application shall be subject to the appended claims.

Claims

1. A financial software influence traceability analysis method, the method comprising:

2. The method according to claim 1, wherein the method further comprises:

3. The method according to claim 2, wherein the method further comprises:

4. A method according to claim 3, wherein the software composition object comprises at least two of: module objects, function objects, interface objects, data table objects and file objects;

and/or the number of the groups of groups,

5. The method of claim 1, wherein said entering the target software maintenance information and the plurality of other software maintenance information into an impact traceability analysis model comprises:

6. The method according to claim 1, wherein determining the result of the traceability analysis of the influence of the target software component object in the financial software according to the target software component object, the software component influence object and the software running influence information comprises:

7. A financial software influence traceability analysis device, the device comprising:

8. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 6 when the computer program is executed.

9. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.

10. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.