Interface blood relationship diagram generation method, device, electronic device and storage medium

Abstract

The present application relates to the field of computer technology, and specifically to a method, device, electronic device and storage medium for generating an interface lineage relationship graph. The method for generating an interface lineage relationship graph provided in the embodiment of the present application includes: determining multiple system nodes included in the target system; respectively obtaining the node identification, interface upstream and downstream relationships and interface field sets of the system nodes, the interface field set including at least one interface field; according to the interface upstream and downstream relationships, connecting the node identifications of multiple system nodes into a network-like node representation graph; adding the interface field sets of multiple system nodes to the network-like node representation graph, so that each node identification has a corresponding interface field set to form an interface lineage relationship graph. The method, device, electronic device and storage medium for generating an interface lineage relationship graph provided in the embodiment of the present application can realize full-link interface management of the entire target system.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, device, electronic device and storage medium for generating an interface blood relationship diagram. Background Art

[0002] The online interface service system will provide at least one application programming interface, which will be managed through management software.

[0003] Currently, there are two types of management software on the market. The first type is management software for data tables in data warehouses, and the second type is management software for online interfaces. The first type of management software is designed only for data tables. Therefore, it only manages data tables inside the data warehouse and cannot be reused in the online field, and cannot meet the full-link interface management requirements of the entire system. The second type of management software only manages interfaces at the export layer, that is, only one layer of management is performed, and it also cannot meet the full-link interface management requirements of the entire system. Summary of the invention

[0004] The embodiments of the present application provide a method, device, electronic device and storage medium for generating an interface blood relationship graph, which can realize full-link interface management of the entire target system.

[0005] The present application embodiment provides a method for generating an interface blood relationship graph, including:

[0006] Determine a plurality of system nodes included in the target system;

[0007] Respectively obtain a node identifier, an interface upstream and downstream relationship, and an interface field set of a system node, wherein the interface field set includes at least one interface field;

[0008] According to the upstream and downstream relationships of interfaces, the node identifiers of multiple system nodes are connected into a network node representation diagram;

[0009] The interface field sets of multiple system nodes are added to the network node representation diagram so that each node identifier has a corresponding interface field set to form an interface lineage relationship diagram.

[0010] The embodiment of the present application provides a device for generating an interface blood relationship graph, including:

[0011] A node determination module, used for determining a plurality of system nodes included in a target system;

[0012] An information acquisition module, used to respectively acquire a node identifier, an interface upstream and downstream relationship, and an interface field set of a system node, wherein the interface field set includes at least one interface field;

[0013] A representation graph generation module, used to connect node identifiers of multiple system nodes into a network-like node representation graph according to the upstream and downstream relationships of interfaces;

[0014] The relationship diagram generation module is used to add the interface field sets of multiple system nodes in the network node representation diagram so that each node identifier has a corresponding interface field set to form an interface blood relationship diagram.

[0015] An embodiment of the present application provides an electronic device, including a processor and a memory, wherein the memory stores a plurality of instructions;

[0016] The processor loads instructions from the memory to execute the steps in the interface blood relationship graph generation method.

[0017] An embodiment of the present application provides a computer-readable storage medium, which stores a plurality of instructions suitable for loading by a processor to execute the steps in the method for generating an interface blood relationship diagram.

[0018] The interface lineage relationship diagram generation method provided in the embodiment of the present application can determine multiple system nodes included in the target system; respectively obtain the node identification, interface upstream and downstream relationship and interface field set of the system node, and the interface field set includes at least one interface field; according to the interface upstream and downstream relationship, the node identification of multiple system nodes is connected into a network node representation diagram; the interface field sets of multiple system nodes are added to the network node representation diagram so that each node identification has a corresponding interface field set to form an interface lineage relationship diagram. That is to say, in the embodiment of the present application, the interface lineage relationship diagram can be used to characterize the interface lineage relationship of multiple system nodes in the target system, covering the entire target system. Then, based on the interface lineage relationship diagram, the full-link interface management of the entire target system can be realized.

[0019] The interface blood relationship diagram generation device, electronic device and storage medium provided in the embodiments of the present application have the same beneficial effects as the above-mentioned interface blood relationship diagram generation method, which will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0021] Figure 1 A flowchart of a method for generating an interface blood relationship diagram provided in an embodiment of the present application.

[0022] Figure 2AA network node representation diagram provided for an embodiment of the present application.

[0023] Figure 2B An interface blood relationship diagram provided for an embodiment of the present application.

[0024] Figure 3 A schematic structural block diagram of an interface blood relationship diagram generating device provided in an embodiment of the present application.

[0025] Figure 4 A schematic structural block diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0026] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.

[0027] In addition, it should be noted that relational terms such as "first", "second", "third", etc. described below are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations.

[0028] The embodiments of the present application provide a method, device, electronic device and storage medium for generating an interface blood relationship diagram.

[0029] The interface blood relationship diagram generating device can be integrated into an electronic device, which can be a terminal device, a server, etc. The terminal device can be a mobile phone, a tablet computer, a smart Bluetooth device, a laptop computer, a personal computer (PC), etc. The server can be a single server or a server cluster composed of multiple servers.

[0030] In some embodiments, the interface blood relationship diagram generating device can also be integrated into multiple electronic devices. For example, the interface blood relationship diagram generating device can be integrated into multiple servers, and the interface blood relationship diagram generating method of the present application can be implemented by multiple servers.

[0031] In some embodiments, the server may also be implemented in the form of a terminal device, for example, a PC is configured as a server to integrate the interface blood relationship diagram generating device.

[0032] For example, the electronic device may be a server, which may:

[0033] Determine a plurality of system nodes included in the target system;

[0034] Respectively acquiring a node identifier, an interface upstream and downstream relationship, and an interface field set of the system node, wherein the interface field set includes at least one interface field;

[0035] Connecting the node identifiers of the plurality of system nodes into a network node representation diagram according to the upstream and downstream relationships of the interfaces;

[0036] The interface field sets of the plurality of system nodes are added to the network-like node representation graph so that each node identifier has a corresponding interface field set, thereby forming an interface lineage relationship graph.

[0037] See also Figure 1 , Figure 1 A flow chart of a method for generating an interface blood relationship diagram provided in an embodiment of the present application. It should be noted that, although a logical order is shown in the flow chart, in some cases, the steps shown or described may also be performed in other orders. In an embodiment of the present application, the method for generating an interface blood relationship diagram is applied to a terminal device, and the method for generating an interface blood relationship diagram includes step S110, step S120, step S130, and step S140.

[0038] Step S110: determining a plurality of system nodes included in the target system.

[0039] The target system may include multiple online interface service systems, such as a shopping system, a bank customer service system, a payment system, etc. Each online interface service system serves as a system node.

[0040] In addition, it should be noted that in the embodiments of the present application, the multiple system nodes included in the target system may not belong to the same target organization. Taking the target organization as a shopping website operator as an example, if the target system includes system nodes such as a shopping system, a bank customer service system, and a payment system, then the shopping system belongs to the target organization, but the bank customer service system and the payment system do not belong to the target organization.

[0041] Step S120, respectively obtain the node identification, interface upstream and downstream relationship and interface field set of the system node, wherein the interface field set includes at least one interface field.

[0042] The node identifier may be a node identifier of a system node, a node name, etc. The node identifier may be a digital identifier or a letter identifier, which is not specifically limited in the embodiment of the present application.

[0043] The interface upstream and downstream relationship is used to characterize the data transmission relationship between system nodes. For example, if there are system nodes A, B, and C in the target system, and system node A accesses system node B, and system node B accesses system node C, then for system node A, its interface upstream and downstream relationship is: the upstream node is system node B, for system node B, its interface upstream and downstream relationship is: the downstream node is system node A, the upstream node is system node C, and for system node C, its interface upstream and downstream relationship is: the downstream node is system node B.

[0044] The interface field set includes at least one interface field, and each interface field is used to represent an application programming interface (API). If the same interface field exists in two system nodes, it means that the downstream node in the two system nodes can access the upstream node based on this interface field and obtain the data information output by the upstream node to realize data transmission. Once the interface field of one of the system nodes changes, data transmission cannot be performed.

[0045] In the embodiment of the present application, step S120 may include step S121, step S122 and step S123.

[0046] Step S121, determining whether the system node is an internal node, where an internal node is a system node in the target system that belongs to the target organization.

[0047] As mentioned above, taking the target institution as a shopping website operator as an example, if the target system includes system nodes such as the shopping system, the bank customer service system, and the payment system, then the shopping system belongs to the target institution, but the bank customer service system and the payment system do not belong to the target institution.

[0048] In the embodiment of the present application, whether a system node belongs to an internal node can be determined based on the node identifier, node name, etc. of the system node, or it can be distinguished by the node attributes preset by the developer. The embodiment of the present application does not impose specific restrictions on this.

[0049] Step S122: if the system node is an internal node, obtain the system code of the system node.

[0050] If the system node is an internal node, the system code of the system node can be directly read.

[0051] Step S123, parsing the system code to obtain the node identification, interface upstream and downstream relationships and interface field sets of the system nodes respectively.

[0052] Since the system code marks the second interface contract for maintaining data export, including the node identification of the system node, the interface upstream and downstream relationships, and the interface field set, the node identification of the system node, the interface upstream and downstream relationships, and the interface field set can be extracted from the second interface contract respectively by parsing the system code.

[0053] Of course, the system node may not be an internal node, and the system code of the system node cannot be directly read. Based on this, in the embodiment of the present application, step S120 may also include step S124 and step S125.

[0054] Step S124: if the system node is not an internal node, obtain the first interface contract of the system node.

[0055] In an embodiment of the present application, if the system node does not belong to an internal node, its first interface contract can be directly exported by other organizations to which the system node belongs, including the node identifier of the system node, interface upstream and downstream relationships, and interface field sets. The first interface contract can specifically be contract information in a target format, for example, the Swagger general format, so as to improve execution efficiency when subsequently executing step S125.

[0056] Step S125 , extracting the node identifier of the system node, the interface upstream and downstream relationship, and the interface field set from the first interface contract respectively.

[0057] In the embodiment of the present application, step S125 may specifically include:

[0058] If the first interface contract is contract information in the target format, then extracting the node identifier of the system node, the interface upstream and downstream relationship, and the interface field set from the first interface contract respectively;

[0059] If the first interface contract is not contract information in the target format, converting the first interface contract into the target format;

[0060] The node identifier of the system node, the interface upstream and downstream relationship and the interface field set are respectively extracted from the first interface contract after being converted into the target format.

[0061] Furthermore, as mentioned previously, the target format can be the Swagger generic format.

[0062] Since the target system includes multiple system nodes, step S120 needs to be executed once for each system node to obtain the node identifier, interface upstream and downstream relationships, and interface field sets of each system node. Finally, multiple node identifiers are obtained, and each node identifier has a corresponding interface upstream and downstream relationship and interface field set.

[0063] Step S130: connecting the node identifiers of multiple system nodes into a network node representation graph according to the upstream and downstream relationships of the interfaces.

[0064] In an embodiment of the present application, each node identifier has a corresponding interface upstream and downstream relationship. Therefore, the upstream node identifier and downstream node identifier of the node identifier can be determined based on the interface upstream and downstream relationship corresponding to each node identifier, and then the node identifiers of multiple system nodes can be connected into a network-like node representation diagram.

[0065] Step S140, adding interface field sets of multiple system nodes to the network node representation graph, so that each node identifier has a corresponding interface field set, forming an interface blood relationship graph.

[0066] In the embodiment of the present application, in the generated network node representation diagram, the second target position where the node identifier of the third target node is located and the second associated position of the second target position are determined, for example, below the second target position, wherein the third target node is any system node, that is, any system node. Thereafter, the interface field set of the third target node is added at the second associated position.

[0067] Exemplarily, the target system includes multiple system nodes, namely system node A, system node B, system node C, system node O, system node D, system node E and system node P, wherein system node A, system node B, system node C, system node D, system node O and system node E belong to the target organization, and system node P does not belong to the target organization. In addition, the node identification, interface upstream and downstream relationship and interface field set of each system node are shown in Table 1.

[0068] Table 1

[0069]

[0070]

[0071] Then, when executing step S140, the node identifiers of system node A, system node B, system node C, system node O, system node D, system node E and system node P may be connected to form a network node representation diagram, as shown in FIG. Figure 2A shown.

[0072] Thereafter, step S140 is executed to add the interface field sets of system node A, system node B, system node C, system node O, system node D, system node E, and system node P to the network node representation graph, so that each node identifier has a corresponding interface field set, forming an interface lineage relationship graph, as shown in FIG. Figure 2B shown.

[0073] In order to expand the range of information that can be represented by the interface blood relationship diagram, in an embodiment of the present application, after step S140, step S210, step S220, step S230, step S240 and step S250 may also be included.

[0074] Step S210: If there is a first target node having multiple downstream nodes among the multiple system nodes, the interface field set of the first target node is used as the field set to be processed.

[0075] by Figure 2B Take the interface lineage diagram shown as an example. Figure 2B In the example, the system node O is the first target node having multiple downstream nodes (system node C and system node E), and the interface field set of the system node O is used as the field set to be processed, that is, the field set to be processed is: O1 and O2.

[0076] Step S220, obtaining the processing logic mark of the field set to be processed.

[0077] Continue with Figure 2B Take the interface lineage diagram shown as an example. Figure 2B In the figure, since the system node O has multiple downstream nodes including the system node C and the system node E, where the interface field set of the system node C is: O1 and C1, and the interface field set of the system node E is: O1, O2 and P1, the processing logic marking of the system node O can be obtained as: O1 as the access interface of the system node C and the system node E, and O2 as the access interface of the system node E.

[0078] Step S230: Obtain function description information of each interface field in the field set to be processed.

[0079] Continue with Figure 2B Taking the interface lineage relationship diagram shown as an example, the interface field set of the system node O is used as the field set to be processed, that is, the field set to be processed is: O1 and O2. Therefore, the functional description information of the interface field O1 and the functional description information of the interface field O2 can be obtained respectively.

[0080] Step S240: Determine, in the interface blood relationship diagram, a first target position where the node identifier of the first target node is located, and a first associated position of the first target position.

[0081] The first associated position may be located below the first target position.

[0082] Step S250: adding a processing logic mark and a functional description information at the first associated position.

[0083] Similarly, in order to expand the range of information that can be represented by the interface blood relationship diagram, in an embodiment of the present application, after step S140, step S310, step S320 and step S330 may also be included.

[0084] Step S310: monitor whether there is a second target node with a fault among multiple system nodes.

[0085] The fault may be an error in the running of a software program of a system node, a change, etc., or a fault in the hardware environment of the running system node. The embodiments of the present application do not impose specific restrictions on this.

[0086] Step S320: If there is a second target node, determine a target downstream node affected by the second target node from multiple system nodes.

[0087] In the embodiment of the present application, based on the generated interface lineage relationship graph, a target downstream node affected by the second target node can be determined from multiple system nodes.

[0088] Continue with Figure 2B Taking the interface lineage relationship diagram shown as an example, if there is a second target node and the second target node is system node E, then based on the generated interface lineage relationship diagram, the target downstream node affected by the second target node can be determined from multiple system nodes as system node D.

[0089] Step S330, highlighting the second target node and the target downstream node in the interface blood relationship diagram.

[0090] Among them, the highlighting can be, but is not limited to, red display and flashing reminder.

[0091] Through step S310, step S320 and step S330, on the one hand, the range of information that can be represented by the interface blood relationship diagram can be expanded, and on the other hand, when a system node fails, it can quickly locate itself and its downstream nodes, shorten the fault location time, and provide effective assistance for production operation and maintenance.

[0092] Similarly, in order to expand the range of information that can be represented by the interface blood relationship diagram, in an embodiment of the present application, after step S140, step S410 and step S420 may also be included.

[0093] Step S410: monitor whether there is a changed target field in the interface field set of the system node.

[0094] In an embodiment of the present application, the interface field set of the system node can be reacquired at a preset time interval and compared with the interface field set of the system node in the interface blood relationship diagram to achieve the purpose of monitoring whether there is a changed target field in the interface field set of the system node.

[0095] In addition, it can be understood that in an embodiment of the present application, if the system node is an internal node, the system code of the system node can be directly read, and by parsing the system code, the interface field set of the system node can be re-obtained from the second interface contract; if the system node does not belong to an internal node, its first interface contract can be directly derived by other organizations to which the system node belongs, and the interface field set of the system node can be re-obtained from the first interface contract.

[0096] Step S420: If the target field exists, the target field is highlighted in the interface lineage diagram.

[0097] Among them, the highlighting can be, but is not limited to, red display and flashing reminder.

[0098] Through step S410 and step S420, on the one hand, the range of information that can be represented in the interface blood relationship diagram can be expanded, and on the other hand, when the interface field set in a certain system node changes, it can be quickly located, shortening the location time of the changed node, and providing effective assistance for production operation and maintenance.

[0099] The interface lineage relationship diagram generation method provided in the embodiment of the present application can determine multiple system nodes included in the target system; respectively obtain the node identification, interface upstream and downstream relationship and interface field set of the system node, and the interface field set includes at least one interface field; according to the interface upstream and downstream relationship, the node identification of multiple system nodes is connected into a network node representation diagram; the interface field sets of multiple system nodes are added to the network node representation diagram so that each node identification has a corresponding interface field set to form an interface lineage relationship diagram. That is to say, in the embodiment of the present application, the interface lineage relationship diagram can be used to characterize the interface lineage relationship of multiple system nodes in the target system, covering the entire target system. Then, based on the interface lineage relationship diagram, the full-link interface management of the entire target system can be realized.

[0100] See also Figure 3 In order to better implement the interface blood relationship diagram generation method, the embodiment of the present application also provides an interface blood relationship diagram generation device 100, which can be integrated into a server.

[0101] In the embodiment of the present application, the interface blood relationship diagram generating device 100 includes:

[0102] A node determination module 110, configured to determine a plurality of system nodes included in a target system;

[0103] The information acquisition module 120 is used to respectively acquire the node identification, the interface upstream and downstream relationship and the interface field set of the system node, wherein the interface field set includes at least one interface field;

[0104] The representation graph generation module 130 is used to connect the node identifiers of multiple system nodes into a network node representation graph according to the upstream and downstream relationships of the interfaces.

[0105] The relationship diagram generation module 140 is used to add the interface field sets of multiple system nodes in the network node representation diagram so that each node identifier has a corresponding interface field set to form an interface blood relationship diagram.

[0106] In some embodiments, the information acquisition module 120 is specifically used to:

[0107] Determine whether the system node is an internal node, where an internal node is a system node in the target system that belongs to the target organization;

[0108] If the system node is an internal node, the system code of the system node is obtained;

[0109] The system code is parsed to obtain the node identification, interface upstream and downstream relationships, and interface field sets of the system nodes.

[0110] In some embodiments, the information acquisition module 120 is further specifically used to:

[0111] If the system node is not an internal node, obtaining the first interface contract of the system node;

[0112] The node identifier of the system node, the interface upstream and downstream relationship, and the interface field set are extracted from the first interface contract respectively.

[0113] In some embodiments, the information acquisition module 120 is further specifically used to:

[0114] If the first interface contract is contract information in the target format, then extracting the node identifier of the system node, the interface upstream and downstream relationship, and the interface field set from the first interface contract respectively;

[0115] If the first interface contract is not contract information in the target format, converting the first interface contract into the target format;

[0116] The node identifier of the system node, the interface upstream and downstream relationship and the interface field set are respectively extracted from the first interface contract after being converted into the target format.

[0117] In some embodiments, the interface blood relationship diagram generating device 100 may further include a first auxiliary module for:

[0118] If there is a first target node having multiple downstream nodes among the multiple system nodes, the interface field set of the first target node is used as the field set to be processed;

[0119] Get the processing logic tag of the field set to be processed;

[0120] Get the functional description information of each interface field in the field set to be processed;

[0121] In the interface lineage relationship graph, determining a first target position where a node identifier of a first target node is located, and a first associated position of the first target position;

[0122] Add processing logic mark and function description information at the first associated position.

[0123] In some embodiments, the interface blood relationship diagram generating device 100 may further include a second auxiliary module for:

[0124] Monitoring whether there is a second target node with a fault among the plurality of system nodes;

[0125] If there is a second target node, determining a target downstream node affected by the second target node from a plurality of system nodes;

[0126] The second target node and the target downstream node are highlighted in the interface lineage diagram.

[0127] In some embodiments, the interface blood relationship diagram generating device 100 may further include a third auxiliary module for:

[0128] Monitor whether there is a target field that has changed in the interface field set of the system node;

[0129] If there is a target field, it will be highlighted in the interface lineage diagram.

[0130] During specific implementation, the above modules can be implemented as independent entities, or can be arbitrarily combined and implemented as the same or several entities. The specific implementation of the above modules can be found in the interface blood relationship diagram generation method embodiment, which will not be repeated here.

[0131] In the embodiment of the present application, the interface blood relationship diagram generation device 100 has the same beneficial effects as the above-mentioned interface blood relationship diagram generation method, that is:

[0132] It is possible to determine multiple system nodes included in the target system; obtain the node identification, interface upstream and downstream relationships, and interface field sets of the system nodes respectively, wherein the interface field set includes at least one interface field; according to the interface upstream and downstream relationships, the node identifications of multiple system nodes are connected into a network node representation diagram; the interface field sets of multiple system nodes are added to the network node representation diagram so that each node identification has a corresponding interface field set to form an interface lineage relationship diagram. In other words, in the embodiment of the present application, the interface lineage relationship diagram can be used to characterize the interface lineage relationship of multiple system nodes in the target system, covering the entire target system. Then, based on the interface lineage relationship diagram, the full-link interface management of the entire target system can be realized.

[0133] Correspondingly, an embodiment of the present application also provides an electronic device 200, which can be a terminal device or a server. The terminal device can be a smart phone, a tablet computer, a laptop computer, a touch screen, a game console, a personal computer, a personal digital assistant (PDA), and other terminal devices.

[0134] See also Figure 4 , Figure 4 The schematic structural block diagram of the electronic device 200 provided in the embodiment of the present application includes a processor 210 having one or more processing cores, a memory 220 having one or more computer-readable storage media, and a computer program stored in the memory 220 and executable on the processor. The processor 210 is electrically connected to the memory 220. Those skilled in the art can understand that Figure 4 The electronic device structure shown in the figure does not constitute a limitation of the electronic device, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0135] The processor 210 is the control center of the electronic device 200. It uses various interfaces and lines to connect various parts of the entire electronic device 200, executes various functions of the electronic device 200 and processes data by running or loading software programs and / or modules stored in the memory 220, and calling data stored in the memory 220, thereby monitoring the electronic device 200 as a whole.

[0136] In an embodiment of the present application, the processor 210 in the electronic device 200 will load the instructions corresponding to the processes of one or more applications into the memory 220 according to the following steps, and the processor 210 will run the applications stored in the memory 220 to implement various functions.

[0137] For example, you can implement:

[0138] Determine a plurality of system nodes included in the target system;

[0139] Respectively obtain a node identifier, an interface upstream and downstream relationship, and an interface field set of a system node, wherein the interface field set includes at least one interface field;

[0140] According to the upstream and downstream relationships of interfaces, the node identifiers of multiple system nodes are connected into a network node representation diagram;

[0141] The interface field sets of multiple system nodes are added to the network node representation diagram so that each node identifier has a corresponding interface field set to form an interface lineage relationship diagram.

[0142] The specific implementation of the above operations can be found in the previous method embodiments, which will not be described in detail here.

[0143] Optional, such as Figure 4 As shown, the electronic device 200 further includes: a touch screen 230, a radio frequency circuit 240, an audio circuit 250, an input unit 260, and a power supply 270. The processor 210 is electrically connected to the touch screen 230, the radio frequency circuit 240, the audio circuit 250, the input unit 260, and the power supply 270, respectively. Those skilled in the art will appreciate that Figure 4 The electronic device structure shown in the figure does not constitute a limitation of the electronic device, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0144] The touch display screen 230 can be used to display a graphical user interface and receive operation instructions generated by the user acting on the graphical user interface. The touch display screen 230 may include a display panel and a touch panel. Among them, the display panel may be used to display information input by the user or information provided to the user and various graphical user interfaces of the electronic device, which may be composed of graphics, text, icons, videos and any combination thereof. Optionally, the display panel may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc. The touch panel may be used to collect the user's touch operation on or near it (for example, the user uses any suitable object or accessory such as a finger, a stylus, etc. on the touch panel or near the touch panel), and generate corresponding operation instructions, and the operation instructions execute corresponding programs. Optionally, the touch panel may include two parts: a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch direction, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into the touch point coordinates, and then sends it to the processor 210, and can receive the command sent by the processor 210 and execute it. The touch panel can cover the display panel. When the touch panel detects a touch operation on or near it, it is transmitted to the processor 210 to determine the type of touch event, and then the processor 210 provides a corresponding visual output on the display panel according to the type of touch event. In an embodiment of the present application, the touch panel and the display panel can be integrated into the touch display screen 230 to realize the input and output functions. However, in some embodiments, the touch panel and the touch panel can be used as two independent components to realize the input and output functions. That is, the touch display screen 230 can also be used as a part of the input unit 260 to realize the input function.

[0145] The radio frequency circuit 240 may be used to send and receive radio frequency signals, so as to establish wireless communication with a network device or other electronic devices through wireless communication, and to send and receive signals between the network device or other electronic devices.

[0146] The audio circuit 250 can be used to provide an audio interface between the user and the electronic device through a speaker and a microphone. The audio circuit 250 can transmit the electrical signal converted from the received audio data to the speaker, which is converted into a sound signal for output; on the other hand, the microphone converts the collected sound signal into an electrical signal, which is received by the audio circuit 250 and converted into audio data, and then the audio data is output to the processor 210 for processing, and then sent to another electronic device through the radio frequency circuit 240, or the audio data is output to the memory 220 for further processing. The audio circuit 250 may also include an earplug jack to provide communication between an external headset and the electronic device.

[0147] The input unit 260 may be used to receive input numbers, character information or user feature information (eg, fingerprint, iris, facial information, etc.), and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.

[0148] The power supply 270 is used to supply power to various components of the electronic device 200. Optionally, the power supply 270 can be logically connected to the processor 210 through a power management system, so that the power management system can manage charging, discharging, and power consumption. The power supply 270 can also include one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0149] although Figure 4 Not shown, the electronic device 200 may also include a camera, a sensor, a wireless fidelity module, a Bluetooth module, etc., which are not described in detail here.

[0150] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0151] Since the processor 210 in the electronic device 200 will load the instructions corresponding to the process of one or an application into the memory 220 according to the steps of any interface blood relationship diagram generation method provided in the embodiments of the present application, and the processor 210 will run the application stored in the memory 220 to implement various functions, therefore, the beneficial effects that can be achieved by any interface blood relationship diagram generation method provided in the embodiments of the present application can be achieved. Please refer to the previous embodiments for details and will not be repeated here.

[0152] A person of ordinary skill in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be completed by instructions, or by controlling related hardware through instructions. The instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.

[0153] To this end, an embodiment of the present application provides a computer-readable storage medium, which stores multiple computer programs. The computer programs can be loaded by a processor to execute the steps in any one of the interface blood relationship diagram generation methods provided in the embodiments of the present application.

[0154] For example, the computer program may perform the following steps:

[0155] Determine a plurality of system nodes included in the target system;

[0156] Respectively obtain a node identifier, an interface upstream and downstream relationship, and an interface field set of a system node, wherein the interface field set includes at least one interface field;

[0157] According to the upstream and downstream relationships of interfaces, the node identifiers of multiple system nodes are connected into a network node representation diagram;

[0158] The interface field sets of multiple system nodes are added to the network node representation diagram so that each node identifier has a corresponding interface field set to form an interface lineage relationship diagram.

[0159] The specific implementation of the above operations can be found in the previous method embodiments, which will not be described in detail here.

[0160] The storage medium may include: a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0161] Since the computer program stored in the storage medium can execute the steps in any of the interface blood relationship diagram generation methods provided in the embodiments of the present application, the beneficial effects that can be achieved by any of the interface blood relationship diagram generation methods provided in the embodiments of the present application can be achieved:

[0162] , that is:

[0163] It is possible to determine multiple system nodes included in the target system; obtain the node identification, interface upstream and downstream relationships, and interface field sets of the system nodes respectively, wherein the interface field set includes at least one interface field; according to the interface upstream and downstream relationships, the node identifications of multiple system nodes are connected into a network node representation diagram; the interface field sets of multiple system nodes are added to the network node representation diagram so that each node identification has a corresponding interface field set to form an interface lineage relationship diagram. In other words, in the embodiment of the present application, the interface lineage relationship diagram can be used to characterize the interface lineage relationship of multiple system nodes in the target system, covering the entire target system. Then, based on the interface lineage relationship diagram, the full-link interface management of the entire target system can be realized.

[0164] The above is a detailed introduction to an interface blood relationship diagram generation method, device, storage medium and electronic device provided in an embodiment of the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for technical personnel in this field, based on the idea of ​​the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A method for generating an interface blood relationship graph, It is characterized in that include: Determine a plurality of system nodes included in the target system; Respectively obtain a node identifier, an interface upstream and downstream relationship, and an interface field set of the system node, wherein the interface field set includes at least one interface field, including: Determine whether the system node is an internal node, the internal node being a system node in the target system belonging to a target organization; If the system node is an internal node, obtaining a system code of the system node; The system code is parsed to obtain the node identification, interface upstream and downstream relationship and interface field set of the system node, including: Determine whether the system node is an internal node, the internal node being a system node in the target system belonging to a target organization; If the system node is an internal node, obtaining a system code of the system node; Parsing the system code to obtain node identifiers, interface upstream and downstream relationships, and interface field sets of the system nodes respectively; Connecting the node identifiers of the plurality of system nodes into a network node representation diagram according to the upstream and downstream relationships of the interfaces; Adding the interface field sets of the plurality of system nodes in the network-like node representation graph so that each node identifier has a corresponding interface field set to form an interface lineage relationship graph; If there is a first target node having multiple downstream nodes among the multiple system nodes, taking the interface field set of the first target node as the field set to be processed; Obtaining a processing logic tag of the field set to be processed; Obtaining functional description information of each interface field in the field set to be processed; In the interface blood relationship graph, determining a first target position where the node identifier of the first target node is located, and a first associated position of the first target position; The processing logic mark and the function description information are added at the first associated position.

2. The method for generating an interface blood relationship diagram according to claim 1, It is characterized in that Extracting the node identifier, the interface upstream and downstream relationship, and the interface field set of the system node from the first interface contract respectively, wherein the obtaining the node identifier, the interface upstream and downstream relationship, and the interface field set of the system node respectively includes: If the first interface contract is contract information in a target format, extracting the node identifier, the interface upstream and downstream relationship, and the interface field set of the system node from the first interface contract respectively; If the first interface contract is not contract information in the target format, converting the first interface contract into the target format; The node identifier, interface upstream and downstream relationship and interface field set of the system node are respectively extracted from the first interface contract after conversion into the target format.

3. The method for generating an interface blood relationship diagram according to any one of claims 1 to 2, It is characterized in that After adding the interface field sets of the plurality of system nodes to the network node representation graph so that each node identifier has a corresponding interface field set and an interface lineage relationship graph is formed, the interface lineage relationship graph generation method further includes: Monitoring whether there is a second target node with a fault among the plurality of system nodes; If the second target node exists, determining a target downstream node affected by the second target node from the multiple system nodes; The second target node and the target downstream node are highlighted in the interface lineage relationship diagram.

4. The method for generating an interface blood relationship diagram according to any one of claims 1 to 2, It is characterized in that After adding the interface field sets of the plurality of system nodes to the network node representation graph so that each node identifier has a corresponding interface field set and an interface lineage relationship graph is formed, the interface lineage relationship graph generation method further includes: Monitoring whether there is a target field that has changed in the interface field set of the system node; If the target field exists, the target field is highlighted in the interface lineage diagram.

5. A device for generating an interface blood relationship diagram, It is characterized in that include: A node determination module, used for determining a plurality of system nodes included in a target system; The information acquisition module is used to respectively acquire the node identification, the interface upstream and downstream relationship and the interface field set of the system node, wherein the interface field set includes at least one interface field, including: Determine whether the system node is an internal node, the internal node being a system node in the target system belonging to a target organization; If the system node is an internal node, obtaining a system code of the system node; The system code is parsed to obtain the node identification, interface upstream and downstream relationship and interface field set of the system node, including: Determine whether the system node is an internal node, the internal node being a system node in the target system belonging to a target organization; If the system node is an internal node, obtaining a system code of the system node; Parsing the system code to obtain node identifiers, interface upstream and downstream relationships, and interface field sets of the system nodes respectively; A representation graph generation module, used to connect the node identifiers of the plurality of system nodes into a network-like node representation graph according to the upstream and downstream relationships of the interfaces; A relationship diagram generation module, used for adding the interface field sets of the plurality of system nodes in the network node representation diagram, so that each node identifier has a corresponding interface field set, thereby forming an interface blood relationship diagram; A first auxiliary module, configured to use, if there is a first target node having multiple downstream nodes among the multiple system nodes, an interface field set of the first target node as a field set to be processed; Obtaining a processing logic tag of the field set to be processed; Obtaining functional description information of each interface field in the field set to be processed; In the interface blood relationship graph, determining a first target position where the node identifier of the first target node is located, and a first associated position of the first target position; The processing logic mark and the function description information are added at the first associated position.

6. An electronic device, It is characterized in that The method comprises a processor and a memory, wherein the memory stores a plurality of instructions; The processor loads instructions from the memory to execute the steps in the interface blood relationship diagram generation method as described in any one of claims 1 to 4.

7. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to execute the steps in the method for generating an interface blood relationship diagram as described in any one of claims 1 to 4.

Images