CN116893846A

CN116893846A - Data flow processing method, device, equipment, medium and program product

Info

Publication number: CN116893846A
Application number: CN202310658557.3A
Authority: CN
Inventors: 李亚雄
Original assignee: Bank of China Ltd
Current assignee: Bank of China Ltd
Priority date: 2023-06-05
Filing date: 2023-06-05
Publication date: 2023-10-17

Abstract

The application relates to a data flow processing method, a device, equipment, a medium and a program product, and relates to the technical field of big data. The method comprises the following steps: responding to the flow query instruction, and acquiring a target function module corresponding to the flow query instruction; acquiring a data flow relation in the target function module from a relation storage table; the relation memory table stores the data flow relation of a plurality of functional modules in the software system; and displaying the data flow relation in the target functional module. The target functional module is any functional module in the software system. The method can rapidly acquire the complete data flow of the computer system, thereby accelerating the update progress of the software system.

Description

Data flow processing method, device, equipment, medium and program product

Technical Field

The present application relates to the field of big data technologies, and in particular, to a data flow processing method, apparatus, device, medium, and program product.

Background

With the rapid development of computer technology, there are more and more functional modules of various software systems.

In the related art, the development process of each functional module in the software system is relatively decoupled, so that the fault appears in the complete data flow of the software system, and in this regard, the complete data flow of the software system is usually linked in the software system updating process by means of turning over design documents or combing database scripts and the like.

However, the related art has the problems of high data flow connection cost and long time, which affects the update progress of the software system.

Disclosure of Invention

Based on this, it is necessary to provide a data flow processing method, device, equipment, medium and program product for the above technical problems, so as to quickly obtain the complete data flow of the computer system, and further accelerate the update progress of the software system.

In a first aspect, the present application provides a data flow processing method, including:

responding to the flow query instruction, and acquiring a target function module corresponding to the flow query instruction; the target functional module is any functional module in the software system;

acquiring a data flow relation in the target function module from a relation storage table; the relation memory table stores the data flow relation of a plurality of functional modules in the software system;

and displaying the data flow relation in the target functional module.

In one embodiment, the process of building the relational storage table includes:

acquiring the data layer characteristics of each functional module in the software system; the data layer features include data input layer features, data processing layer features, and data application layer features;

based on the data layer characteristics of each functional module, a relation storage table of the software system is constructed.

In one embodiment, based on the data layer characteristics of each functional module, a relational storage table of the software system is constructed, including:

acquiring attribute description information of each functional module from the data layer characteristics of each functional module;

integrating attribute description information of each functional module;

and generating a relation storage table of the software system according to the integrated attribute description information of each functional module.

In one embodiment, obtaining attribute description information of each functional module from the data layer features of each functional module includes:

for any functional module, splitting the data layer characteristics of the functional module into a plurality of processing tables according to the data processing layer characteristics in the functional module; each processing table corresponds to a set of data relationships;

acquiring attribute description information of each processing table;

and determining the attribute description information of the functional module according to the attribute description information of each processing table.

In one embodiment, obtaining the data flow relationship in the target function module from the relationship storage table includes:

acquiring at least one relation call interface in a target functional module;

determining the calling party flow of each relation calling interface according to at least one relation calling interface in the target functional module;

And acquiring the data flow relation in the target function module according to each relation calling interface and the calling party flow of each relation calling interface.

In one embodiment, the caller flow includes a target table, an original file, and a source system, and determining the caller flow of each relationship call interface according to at least one relationship call interface in the target function module includes:

determining a target table, an original file and a source system of each relation call interface from the relation storage table;

correspondingly, according to each relation call interface and the call party flow of each relation call interface, acquiring the data flow relation in the target function module, including:

and associating the target table, the original file and the source system of each relation calling interface to obtain the data flow relation in the target function module.

In one embodiment, the method for displaying the data flow relation in the target function module comprises the following steps:

acquiring the trigger type of the flow query instruction;

and determining a target display format according to the trigger type, and displaying the data flow relation in the target function module in the target display format.

In one embodiment, determining a target display format according to the trigger type, and displaying the data flow relationship in the target function module in the target display format includes:

If the trigger type is statement trigger, determining that the target display format is a table format, and displaying the data flow relation in the target function module in the table format;

if the trigger type is web page trigger, determining that the target display format is a flow chart format, and displaying the data flow relation in the target function module in the flow chart format.

In a second aspect, the present application also provides a data flow processing apparatus, where the apparatus includes:

the response module is used for responding to the flow query instruction and acquiring a target function module corresponding to the flow query instruction; the target functional module is any functional module in the software system;

the acquisition module is used for acquiring the data flow relation in the target function module from the relation storage table; the relation memory table stores the data flow relation of a plurality of functional modules in the software system;

and the display module is used for displaying the data flow relation in the target function module.

In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor implementing the steps of the method in any of the embodiments of the first aspect described above when the computer program is executed.

In a fourth aspect, the present application also provides a computer-readable storage medium. The computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the method in any of the embodiments of the first aspect described above.

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

The data flow processing method, the device, the equipment, the medium and the program product respond to the flow query instruction, firstly acquire the target function module corresponding to the flow query instruction, then acquire the data flow relation in the target function module from the relation storage table, and finally display the data flow relation in the target function module. The target functional module is any functional module in the software system, and the data flow relation of a plurality of functional modules in the software system is stored in the relation storage table. That is, the method is based on obtaining a relation storage table of the software system, responding to a flow inquiry instruction, determining a function module corresponding to the flow inquiry instruction as a target function module, and obtaining and displaying a complete data flow associated with the target function module from the relation storage table. Because the relation storage table comprises the data flow relation of a plurality of functional modules in the software system, the method is equivalent to establishing the logic relation of a plurality of relatively decoupled functional modules in the software system through the relation storage table and storing the logic relation in the form of the data flow relation. Obviously, the data flow relation of the relation storage table covers the association relation of each functional module in the software system, and then the data flow relation obtained according to the relation storage table is also complete. In addition, because the relation storage table in the method is prestored, the process of determining the data flow relation according to the relation storage table is avoided, the process of reintegrating the discretization data flow is avoided, and the acquisition speed of the data flow relation is improved. Further, the complete data flow relation is visually displayed, so that the data flow can be clearly and intuitively displayed, and updating operations such as system optimization or handover and the like can be conveniently and rapidly performed on the software system. In summary, the data flow processing method provided by the application can rapidly acquire the complete data flow relation through the relation storage table, thereby accelerating the update progress of the software system.

Drawings

FIG. 1 is an application environment diagram of a data flow processing method in one embodiment;

FIG. 2 is a flow diagram of a data flow processing method in one embodiment;

FIG. 3 is a flow diagram of the relationship store table construction steps in one embodiment;

FIG. 4 is a flowchart illustrating a relationship storage table construction step in another embodiment;

FIG. 5 is a flowchart illustrating the steps for obtaining attribute description information in one embodiment;

FIG. 6 is a flow diagram of the data flow relationship acquisition step in one embodiment;

FIG. 7 is a flow chart of a data flow relationship acquisition step in another embodiment;

FIG. 8 is a flow diagram of a data flow relationship display step in one embodiment;

FIG. 9 is a flow chart of a data flow relationship display step in another embodiment;

FIG. 10 is a flow chart of a data flow relationship display step in another embodiment;

FIG. 11 is a block diagram of a data flow processing apparatus in one embodiment;

FIG. 12 is a block diagram showing a data flow processing apparatus according to another embodiment;

fig. 13 is an internal structural view of a computer device in one embodiment.

Detailed Description

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

The data flow processing method provided by the embodiment of the application can be applied to an application environment shown in fig. 1. Wherein the terminal 102 communicates with the server 104 via a network. The data storage system may store data, such as relational storage tables, that the server 104 needs to process. The data storage system may be integrated on the server 104 or may be located on a cloud or other network server. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices, and portable wearable devices, where the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart vehicle devices, and the like. The portable wearable device may be a smart watch, smart bracelet, headset, or the like. The server 104 may be implemented as a stand-alone server or as a server cluster of multiple servers.

With the rapid development of computer technology, software systems of various industries need to be updated, such as handover delivery or reconfiguration optimization, to develop information construction of enterprises. However, because of the relatively many functional modules of the software system, the relatively independent development of each functional module, the mobility of the developers of the enterprise, etc., the developers can only explain the logic relationship of the specific functional modules, but cannot explain the complete view of the complete data flow in the software system (such as mutual reference and call between data, or multiplexing between table data, source of the target table, etc.), so that faults appear in the complete data flow in the software system and are not connected.

In the process of updating the software system, the related technology usually perfects the whole data flow relation of the software system by means of turning over the design document or combing the data such as the database script, so as to update the software system. Obviously, the method of acquiring the data flow in the related art can cause a great deal of manpower, material resources and time expenditure, thereby affecting the progress of the handover delivery or reconfiguration optimization of the software system.

Based on the above, the application provides a data flow processing method, which is characterized in that the data flow relation of each functional module in a software system is integrated into a relation storage table, and the data flow relation associated with the flow inquiry instruction is quickly acquired in response to the flow inquiry instruction, so that the progress of handover delivery or reconstruction optimization of the software system is improved. The data flow processing method provided by the application is described below through an embodiment.

In one embodiment, as shown in fig. 2, a data flow processing method is provided, and the method is applied to the server in fig. 1 for illustration, and includes the following steps:

s201, responding to a flow query instruction, and acquiring a target function module corresponding to the flow query instruction; the target functional module is any functional module in the software system.

The software system is a computer system established for meeting various demands of users for using the computer in the process of enterprise information construction. Typically, a software system is capable of meeting a plurality of different types of requirements of users, and correspondingly, a plurality of functional modules are included in the software system to meet the different types of requirements of users.

After the development of the software system is completed, if an update operation such as handover delivery or reconfiguration optimization needs to be performed on the software system, a complete data flow in the software system needs to be acquired. In this case, the functional module corresponding to the flow query instruction in the software system may be acquired by the flow query instruction. The process query instruction is an instruction generated based on the update requirement of the user on the software system, and can be generated by typing in a requirement text on a search interface of the software system, or clicking a corresponding requirement key in a process query list of the software system.

Optionally, the flow query instruction carries a function module identifier, and according to the function module identifier in the flow query instruction, a function module consistent with the function module identifier in the flow query instruction, namely, a target function module, is determined in a plurality of function systems in the software system.

S202, acquiring a data flow relation in a target function module from a relation storage table; the relation memory table stores the data flow relation of a plurality of functional modules in the software system.

The relation storage table is obtained by collecting calling relations inside each functional module in the software system and calling relations among the functional modules, and one software system corresponds to one relation storage table.

The relation memory table of the software system stores the data flow relation of a plurality of functional modules in the software system, namely the data flow relation of the target functional module.

Optionally, according to the target function module identifier, determining the data flow relation of the target function module from the relation storage table.

Optionally, according to the target function module corresponding to the flow query instruction, a series of data such as a calling party, a called party and the like associated with the target function module in the relation storage table is obtained, and according to the logic relation, the data associated with the target function module is connected to generate the data flow relation of the target function module.

S203, the data flow relation in the target function module is displayed.

In the case that the data flow relationship in the target function module is acquired, in order to further clearly and intuitively display the data flow relationship associated with the target function module in the software system, the data flow relationship in the target function module is visualized and displayed in various forms, such as a table, a chart and the like.

In the embodiment of the application, in response to the flow query instruction, the target function module corresponding to the flow query instruction is firstly obtained, then the data flow relation in the target function module is obtained from the relation storage table, and finally the data flow relation in the target function module is displayed. The target functional module is any functional module in the software system, and the data flow relation of a plurality of functional modules in the software system is stored in the relation storage table. That is, the embodiment of the application is based on obtaining the relation storage table of the software system, responding to the flow inquiry instruction, determining the function module corresponding to the flow inquiry instruction as the target function module, and obtaining and displaying the complete data flow associated with the target function module from the relation storage table. Because the relation storage table comprises the data flow relation of a plurality of functional modules in the software system, the method is equivalent to the embodiment of the application that the relation storage table establishes the logic relation of a plurality of relatively decoupled functional modules in the software system and stores the logic relation in the form of the data flow relation. Obviously, the data flow relation of the relation storage table covers the association relation of each functional module in the software system, and then the data flow relation obtained according to the relation storage table is also complete. In addition, because the relation storage table in the embodiment of the application is prestored, the process of determining the data flow relation according to the relation storage table is avoided, and the acquisition speed of the data flow relation is improved. Further, the complete data flow relation is visually displayed, so that the data flow can be clearly and intuitively displayed, and updating operations such as system optimization or handover and the like can be conveniently and rapidly performed on the software system. In summary, the data flow processing method provided by the embodiment of the application can quickly acquire the complete data flow relation through the relation storage table, thereby accelerating the update progress of the software system.

The foregoing embodiment shows that the data flow relationship in the target functional module is obtained according to the relationship storage table of the software system, so as to ensure the integrity and rapidity of the data flow relationship. Based on this, the following describes the construction steps of the relationship storage table by way of one embodiment.

In one embodiment, as shown in FIG. 3, the process of building the relationship store table includes:

s301, acquiring the data layer characteristics of each functional module in the software system; the data layer features include data input layer features, data processing layer features, and data application layer features.

The relation storage table is obtained by collecting the data layer characteristics of each functional module in the software system and analyzing and sorting the data layer characteristics.

The data layer features of each functional module include data input layer features, data processing layer features, and data application layer features. The data acquisition layer characteristics comprise source files corresponding to the data interface table, source systems of the source files and source table names issued by the source systems. The data processing layer features include the processing mode of the interface table, such as: and storing the processing modes of the process, the processing of the SHELL program file script, the processing of the JAVA program file script and the like, and the processing relation from the interface table to the target table in the secondary processing. The data application layer features include interfaces that call the target table, services that call the interfaces, channels that call the services, and so on.

S302, based on the data layer characteristics of each functional module, a relation storage table of the software system is constructed.

Optionally, the relation structure table of each functional module is respectively built according to the data layer characteristics of each functional module, and then the relation structure tables of each functional module are summarized according to the logic sequence among the functional modules to generate the relation storage table of the software system.

Optionally, the preset storage positions of the functional modules in the relation storage table are obtained, the data layer characteristics of the functional modules are stored in the corresponding preset storage positions until the data layer characteristics of the functional modules are stored, and the relation storage table of the software system is obtained.

In the embodiment of the application, the data layer characteristics of each functional module are integrated by collecting the data acquisition layer characteristics, the data processing layer characteristics and the data application layer characteristics of each functional module to obtain the relation storage table of the software system, and the construction mode fully covers each functional module of the software system, so that the relation storage table has integrity.

After the data layer characteristics of each functional module are acquired, there are various ways of constructing a relationship storage table of the software system, so as to comprehensively cover the calling relationship of each functional module in the software system. Based on this, the following describes further the construction steps of the relation memory table on the basis of the acquisition of the data layer characteristics of each functional module by means of an embodiment.

In one embodiment, as shown in fig. 4, building a relational storage table of a software system based on data layer characteristics of each functional module includes:

s401, acquiring attribute description information of each functional module from the data layer characteristics of each functional module.

Each functional module in the software system comprises a data acquisition layer feature, a data processing layer feature and a data application layer, and attribute description information of each functional module is obtained according to the data layer feature of each functional module.

Optionally, the attribute description information includes eight aspects of type identification, name description, source description, output description and system identification of each functional module. Acquiring type identifiers, names and name descriptions of corresponding functional modules according to the characteristics of the data acquisition layer; acquiring sources and source descriptions of corresponding functional modules according to the characteristics of the data processing layer; and acquiring output, output description and system identification of the corresponding functional module according to the data application layer.

S402, integrating attribute description information of each functional module.

It should be noted that, the functional modules in the software system may involve secondary processing or multiple processing of data, and then the attribute description information of the functional modules also includes one or more sets of relationships. And summarizing the attribute description information of each functional module to obtain a plurality of groups of relations of all the functional modules in the software system.

S403, generating a relation storage table of the software system according to the integrated attribute description information of each functional module.

The relation storage table comprises a plurality of groups of relations of each functional module in the software system. In the embodiment of the application, the attribute description information of each integrated functional module is summarized into a table to generate a relation storage table of the software system.

In the embodiment of the application, the attribute description information of each functional module is acquired according to the data layer characteristics of each functional module, and the relation of each functional module is subjected to multi-dimension description, so that the content of the actual characterization of each attribute is conveniently understood. Further, the attribute description information of each functional module is integrated to obtain a relation storage table of the software system, and the obtaining mode can ensure that the relation storage table completely covers each functional module in the software system.

Next, an implementation manner of "acquiring attribute description information of each functional module from the data layer features of each functional module" in the foregoing embodiment will be described by using an embodiment, as shown in fig. 5, where the step of acquiring attribute description information of each functional module includes:

s501, for any functional module, splitting the data layer characteristics of the functional module into a plurality of processing tables according to the data processing layer characteristics in the functional module; each process table corresponds to a set of data relationships.

It should be noted that one functional module may involve secondary processing or multiple processing of data, and each processing corresponds to a set of data relationships.

For any functional module, according to the data processing layer characteristics of the functional module, a plurality of groups of calling relations of the functional module are determined. And determining the number of the processing tables according to the number of the calling relations, and determining the content of the corresponding processing tables according to the content of the calling relations.

For example, if the input data of the functional module is a, the output data is D, and the data processing layer features include a call relationship from a to B, a call relationship from B to C, and a call relationship from C to D, then the first processing table, the second processing table, and the third processing table are determined according to the data processing layer features of the functional module, where the first processing table corresponds to the call relationship from a to B, the second processing table corresponds to the call relationship from B to C, and the third processing table corresponds to the call relationship from C to D.

S502, acquiring attribute description information of each processing table.

The attribute description information of each processing table is the same as the dimension of the attribute description information of each functional module in the aforementioned step S401, and will not be described herein.

It should be noted that, considering that the attribute description information of each processing table is distinguished by a name, in order to facilitate understanding of the specific content of each attribute description information, in the embodiment of the present application, the description information of each attribute description information is further enriched from three aspects of field english name, attribute description and remarks of each attribute. Taking the type identifier as an example, the type may be a service, an interface, a storage process, a loader or a file, etc., then in the attribute description of the type identifier, the corresponding relationship between the service, the interface, the storage process, the loader or the file and the type identifier may be described.

The attribute description information of the process table is exemplarily described in the form of table 1.

TABLE 1

As can be seen from table 1, the attributes of the process table are divided into eight aspects, namely, a type identifier, a name description, a source description, an output description and a system representation, and in the process table, the type identifier may be one of a service (S), an interface (I), a table (T), a stored procedure (T), a loader (T), and a file (F).

S503, determining the attribute description information of the functional module according to the attribute description information of each processing table.

And summarizing the attribute description information of a plurality of processing tables of the same functional module to generate the attribute description information of the functional module.

In the embodiment of the application, the relation of the functional modules is split in a fine granularity according to the characteristics of the data processing layer in the functional modules, the splitting basis is reliable, then the attribute description information of the functional modules is determined according to the attribute description information of each split processing table, and the comprehensiveness of the attribute description information of the functional modules is improved.

In the data flow processing process, the flow link associated with the target functional module is determined as the data flow relation of the target functional module based on the target functional module in a relation storage table. Based on this, the acquisition step of the data flow relationship is explained below by way of one embodiment.

In one embodiment, as shown in FIG. 6, retrieving the data flow relationships in the target function module from the relationship storage table includes:

s601, at least one relation call interface in the target function module is acquired.

The target function module comprises a data acquisition layer, a data processing layer and a data application layer. The data processing layer comprises a relationship of secondary processing or multiple processing of input data, each processing corresponds to a relationship calling interface, and one relationship calling interface is connected with a calling party and a called party.

And if the data processing layer of the target functional module comprises a processing relation, acquiring a relation calling interface in the target functional module. And if the data processing layer of the target functional module comprises a plurality of processing relations, acquiring a plurality of relation calling interfaces in the target functional module.

S602, determining the calling party flow of each relation calling interface according to at least one relation calling interface in the target function module.

The calling party flow comprises a target table, an original file and a source system. Then a target table, an original file, and a source system for each relationship call interface are determined from the relationship storage table based on at least one relationship call interface in the target function module.

S603, according to the relation calling interfaces and the calling party flows of the relation calling interfaces, acquiring the data flow relation in the target function module.

In the flow of the calling party, the target table, the original table and the original file are called according to the service interface, the target table, the original file and the original file are sequentially associated based on the logic obtained by the source system, and the data flow relation in the target functional module is obtained.

Taking the "historical transaction inquiry" service as an example, fig. 7 is a schematic diagram of a data flow relationship of a caller flow according to an embodiment of the present application. As shown in fig. 7, a service is taken as an access point, an interface corresponding to the service is sequentially acquired, a target table pointed by the interface, an original table associated with the target table, an original file associated with the original table, and a source system pointed by the original file are called, and a data flow relation of historical transaction inquiry is obtained.

In the embodiment of the application, the data flow relation in the target functional module is acquired according to the relation calling interface of the target functional module and the calling party flow of each relation calling interface. Because the relation calling interface of the target functional module and the calling party flow of the target functional module are stored in the relation storage table in advance, after the target functional module is determined, the data associated with the target functional module can be quickly extracted, and then the data flow relation of the target functional module can be quickly acquired.

In the case of acquiring the data flow relationship in the target functional module, the data flow relationship is usually subjected to visualization processing, so that the logic of the data flow relationship is clearly and intuitively read. Based on this, a description will be given below of a process of exhibiting a data flow relationship by way of one embodiment.

In one embodiment, as shown in fig. 8, the data flow relationship in the target function module is shown, including:

s801, a trigger type of a flow query instruction is obtained.

The flow query instruction is an instruction generated based on the user's update needs for the software system. In the embodiment of the application, the same service of the target functional module is queried, and a plurality of triggering modes are correspondingly arranged, so that a user can conveniently trigger a flow query instruction to check the data flow of the software system by combining the development background, the query habit, the query purpose and the like of the user.

For example, if the development of the software system is aimed, the condition query filtering and screening statement can be written according to the condition query filtering method, so as to realize the query of the complete data flow relation of the reference corresponding to any service name and table name in the software system.

S802, determining a target display format according to the trigger type, and displaying the data flow relation in the target function module in the target display format.

And determining a target display format according to the corresponding relation between the trigger type and the display format, and displaying the target display format according to the data flow relation in the target function module.

In the embodiment of the application, the triggering type of the flow query instruction comprises various forms so as to facilitate the development of flow query through various channels according to own requirements. Correspondingly, the display format of the data flow relation is determined according to the trigger type, and the visualized display can completely and clearly display the content of the data flow relation.

In the following, by way of an embodiment, a description will be given of a presentation format of "determining a target presentation format according to a trigger type and presenting a data flow relation in a target function module in the target presentation format" in the foregoing example, and as shown in fig. 9, the steps of presenting the data flow relation include:

and S901, if the trigger type is statement trigger, determining that the target display format is a table format, and displaying the data flow relation in the target function module in the table format.

Still taking the "historical transaction inquiry" service as an example, the data flow relationship table format obtained from the relationship storage table is shown in Table 2.

TABLE 2

If the trigger type is statement trigger, determining that the target display format is a table, wherein the data flow relation of the historical transaction inquiry is shown in table 3, and table 3 is inquiry information of the historical transaction inquiry.

TABLE 3 Table 3

As can be seen from Table 2, the historical transaction query can be entered through channels of different source systems, and the query content includes channels, services, interfaces, target tables, processing of target tables to original tables, processing relationships of original tables to files, original tables, and source system where the source tables are located.

S902, if the trigger type is web page trigger, determining that the target display format is a flow chart format, and displaying the data flow relation in the target function module in the flow chart format.

Through the format of the flow chart, the data flow relation is intuitively displayed, and the activities such as reporting, announcing and the like of business personnel and development and design personnel are facilitated.

Taking the "historical transaction inquiry" service as an example, if the trigger type is web page trigger, determining that the target display format is the flow chart format, wherein the data flow relation of the historical transaction inquiry is shown in fig. 10, and fig. 10 is a schematic diagram of inquiry information of the historical transaction inquiry.

As can be seen from fig. 10, the history transaction query enters the query through the financial software APP channel, the corresponding call interface number is CDA60001, and the CDA60001 interface number points to the target table a and the target table B in parallel. The object table a points to the storage procedure a, the storage procedure a points to the original table a, the original table B points to the loading script a, the loading script a points to 01×0d.txn files, 01×0d.txn files point to the BONCS-system table A, BONCS-the system table a points to the BONUS system; the target table B points to the original table B and the target table C in parallel, the original table B points to the loading script B, the loading script B points to the 01.1d.txn file, the 01.1d.txn file points to the BONCS-system table B, BONCS-the system table B points to the BONUS system; original table C points to load script C, load script C points to 01 x 2d.txn file, 01 x 2d.txn file points to APP-system table A, APP-system table a points to APP system.

In the embodiment of the application, the display format of the data flow relation is determined according to the trigger type, and the display process is performed, so that the complete content of the data flow relation can be presented, the method and the device can be suitable for the query requirements of users with different development backgrounds and different query purposes, and a good query experience is provided for the users.

In one embodiment, a data flow processing method is provided, the method comprising:

(1) Responding to the flow query instruction, and acquiring a target function module corresponding to the flow query instruction; the target functional module is any functional module in the software system.

(2) And acquiring at least one relation call interface in the target functional module.

(3) And determining a target table, an original file and a source system of each relation call interface from the relation storage table according to at least one relation call interface in the target function module.

(4) And associating the target table, the original file and the source system of each relation calling interface to obtain the data flow relation in the target function module.

(5) And acquiring the trigger type of the flow query instruction.

(6) And if the trigger type is statement trigger, determining that the target display format is a table format, and displaying the data flow relation in the target function module in the table format.

(7) And if the trigger type is web page trigger, determining that the target display format is a flow chart format, and displaying the data flow relation in the target function module in the flow chart format.

The construction method of the relation storage table comprises the following steps:

(1) Acquiring the data layer characteristics of each functional module in the software system; the data layer features include data input layer features, data processing layer features, and data application layer features.

(2) For any functional module, splitting the data layer characteristics of the functional module into a plurality of processing tables according to the data processing layer characteristics in the functional module; each process table corresponds to a set of data relationships.

(3) And acquiring attribute description information of each processing table.

(4) And determining the attribute description information of the functional module according to the attribute description information of each processing table.

(5) And integrating the attribute description information of each functional module.

(6) And generating a relation storage table of the software system according to the integrated attribute description information of each functional module.

In the embodiment of the application, the relation storage table is established through the data layer characteristics of each functional module in the software system, which is equivalent to the embodiment of the application, the logic relation of a plurality of relatively decoupled functional modules in the software system is established through the relation storage table, and the logic relation is stored in the form of data flow relation. On the basis of acquiring the relation storage table, responding to the flow query instruction, firstly acquiring a target function module corresponding to the flow query instruction, then acquiring the data flow relation in the target function module from the relation storage table, and finally displaying the data flow relation in the target function module. Because the relation storage table in the embodiment of the application is prestored, the process of determining the data flow relation according to the relation storage table is avoided, the process of reintegrating the discretization data flow is avoided, and the acquisition speed of the data flow relation is improved. Further, the complete data flow relation is visually displayed, so that the data flow can be clearly and intuitively displayed, and updating operations such as system optimization or handover and the like can be conveniently and rapidly performed on the software system. In summary, the data flow processing method provided by the embodiment of the application can quickly acquire the complete data flow relation through the relation storage table, thereby accelerating the update progress of the software system.

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 data flow processing device for realizing the above related data flow processing method. The implementation of the solution provided by the apparatus is similar to the implementation described in the above method, so the specific limitation in one or more embodiments of the data flow processing apparatus provided below may refer to the limitation of the data flow processing method hereinabove, and will not be repeated herein.

In one embodiment, as shown in fig. 11, there is provided a data flow processing apparatus 1100, comprising: a response module 1101, an acquisition module 1102, and a presentation module 1103, wherein:

a response module 1101, configured to respond to the flow query instruction, and obtain a target function module corresponding to the flow query instruction; the target functional module is any functional module in the software system;

an obtaining module 1102, configured to obtain a data flow relationship in the target function module from the relationship storage table; the relation memory table stores the data flow relation of a plurality of functional modules in the software system;

the display module 1103 is configured to display the data flow relationship in the target function module.

In one embodiment, the obtaining module 1102 includes a feature obtaining unit and a memory table constructing unit, where:

the feature acquisition unit is used for acquiring the data layer features of each functional module in the software system; the data layer features include data input layer features, data processing layer features, and data application layer features;

and the storage table construction unit is used for constructing a relation storage table of the software system based on the data layer characteristics of each functional module.

In one embodiment, the storage table construction unit includes an attribute acquisition subunit, an attribute integration subunit, and a storage table generation subunit, wherein:

The attribute acquisition subunit is used for acquiring attribute description information of each functional module from the data layer characteristics of each functional module;

the attribute integration subunit is used for integrating the attribute description information of each functional module;

and the storage table generation subunit is used for generating a relation storage table of the software system according to the integrated attribute description information of each functional module.

In one embodiment, the attribute obtaining subunit is further configured to split, for any one of the functional modules, the data layer features of the functional module into a plurality of processing tables according to the data processing layer features in the functional module; each processing table corresponds to a set of data relationships; acquiring attribute description information of each processing table; and determining the attribute description information of the functional module according to the attribute description information of each processing table.

In one embodiment, the obtaining module 1102 further includes an interface obtaining unit, a flow determining unit, and a flow obtaining unit, where:

the interface acquisition unit is used for acquiring at least one relation call interface in the target functional module;

the flow determining unit is used for determining the calling party flow of each relation calling interface according to at least one relation calling interface in the target functional module;

The flow obtaining unit is used for obtaining the data flow relation in the target function module according to each relation calling interface and the calling party flow of each relation calling interface.

In one embodiment, the flow determining unit is further configured to determine a target table, an original file and a source system of each relationship call interface from the relationship storage table, and correspondingly, the flow obtaining unit is further configured to associate the target table, the original file and the source system of each relationship call interface to obtain a data flow relationship in the target function module.

In one embodiment, the presentation module 1103 includes a type acquisition unit and a flow presentation unit, where:

the type acquisition unit is used for acquiring the trigger type of the flow query instruction;

the flow display unit is used for determining a target display format according to the trigger type and displaying the data flow relation in the target function module in the target display format.

In one embodiment, the process display unit includes a first display subunit and a second display unit, wherein:

the first display subunit is used for determining that the target display format is a table format if the trigger type is statement trigger, and displaying the data flow relation in the target function module in the table format;

And the second display subunit is used for determining that the target display format is a flow chart format if the trigger type is web page trigger, and displaying the data flow relation in the target function module in the flow chart format.

In one embodiment, as shown in fig. 12, there is provided a data flow processing apparatus 1200 comprising: a feature collection module 1201, a relationship store table design module 1202, a relationship recording module 1203, a relationship generation module 1204, a visualization module 1205, and a flowchart presentation module 1206, wherein:

the feature collection module 1201 is configured to collect data layer features in each functional module in the software system, such as interfaces of service call, a target table queried by the interfaces, processing an original table into the target table, and processing a relationship of the original table by the source file;

the relational storage table design module 1202 is configured to design a structure of the relational storage table in combination with the data layer features.

The relationship recording module 1203 is configured to record the data layer features acquired by the feature collecting module 1201 to the structure of the storage table generated by the relationship storage table design module 1202, so as to obtain a relationship storage table;

the relationship generating module 1204 is configured to generate a flow link structure of each functional module, that is, a data flow relationship, based on the association relationship of each functional module in the relationship storage table;

A visualization module 1205 for converting the data flow relationship into a visualization format;

a flow diagram display module 1206 is configured to display the data flow relationship.

The modules in the data flow processing apparatus described above may be implemented in whole or in part by software, hardware, or 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 server, and the internal structure of which may be as shown in fig. 13. The computer device includes a processor, a memory, an Input/Output interface (I/O) and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. 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, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is used for storing data flow processing data. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a data flow processing method.

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

In one embodiment, a computer device is provided comprising a memory and a processor, the memory having stored therein a computer program, the processor when executing the computer program performing the steps of:

and displaying the data flow relation in the target functional module.

In one embodiment, the processor when executing the computer program further performs the steps of:

integrating attribute description information of each functional module;

acquiring attribute description information of each processing table;

acquiring at least one relation call interface in a target functional module;

acquiring the trigger type of the flow query instruction;

In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, performs the steps of:

and displaying the data flow relation in the target functional module.

In one embodiment, the computer program when executed by the processor further performs the steps of:

integrating attribute description information of each functional module;

acquiring attribute description information of each processing table;

acquiring at least one relation call interface in a target functional module;

acquiring the trigger type of the flow query instruction;

In one embodiment, a computer program product is provided comprising a computer program which, when executed by a processor, performs the steps of:

and displaying the data flow relation in the target functional module.

integrating attribute description information of each functional module;

Acquiring attribute description information of each processing table;

acquiring at least one relation call interface in a target functional module;

acquiring the trigger type of the flow query instruction;

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data need to comply with the related laws and regulations and standards of the related country and region.

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 embodiments provided herein may include at least one 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 embodiments provided herein may include at least one 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 processor referred to in the embodiments provided in the present application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, or the like, but is not 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 foregoing examples illustrate only a few embodiments of the application, which are described in detail and are not to be construed as limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of the application should be assessed as that of the appended claims.

Claims

1. A data flow processing method, the method comprising:

responding to a flow query instruction, and acquiring a target function module corresponding to the flow query instruction; the target functional module is any functional module in a software system;

acquiring a data flow relation in the target function module from a relation storage table; the relation storage table stores the data flow relation of a plurality of functional modules in the software system;

And displaying the data flow relation in the target function module.

2. The method of claim 1, wherein the process of constructing the relational storage table comprises:

acquiring the data layer characteristics of each functional module in the software system; the data layer features comprise data input layer features, data processing layer features and data application layer features;

and constructing a relation storage table of the software system based on the data layer characteristics of each functional module.

3. The method of claim 2, wherein constructing the relational storage table of the software system based on the data layer characteristics of each of the functional modules comprises:

integrating attribute description information of each functional module;

4. A method according to claim 3, wherein said obtaining attribute description information of each of the function modules from the data layer characteristics of each of the function modules includes:

acquiring attribute description information of each processing table;

5. The method according to any one of claims 1-4, wherein the retrieving the data flow relationships in the target function module from a relationship storage table comprises:

acquiring at least one relation call interface in the target function module;

determining the calling party flow of each relation calling interface according to at least one relation calling interface in the target function module;

6. The method of claim 5, wherein the caller flow comprises a target table, an original file, and a source system, wherein the determining the caller flow for each of the relationship call interfaces based on at least one relationship call interface in the target function module comprises:

correspondingly, the acquiring the data flow relation in the target function module according to each relation call interface and the call party flow of each relation call interface includes:

7. The method of any of claims 1-4, wherein said exposing a data flow relationship in the target function module comprises:

acquiring the trigger type of the flow query instruction;

and determining the target display format according to the trigger type, and displaying the data flow relation in the target function module in the target display format.

8. The method of claim 7, wherein determining the target presentation format according to the trigger type and presenting the data flow relationship in the target function module in the target presentation format comprises:

And if the trigger type is web page trigger, determining that the target display format is a flow chart format, and displaying the data flow relation in the target function module in the flow chart format.

9. A data flow processing apparatus, the apparatus comprising:

the response module is used for responding to the flow query instruction and acquiring a target function module corresponding to the flow query instruction; the target functional module is any functional module in a software system;

the acquisition module is used for acquiring the data flow relation in the target function module from the relation storage table; the relation storage table stores the data flow relation of a plurality of functional modules in the software system;

10. 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 one of claims 1 to 8 when the computer program is executed.

11. 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 8.

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