Interface management method, device, electronic device and readable storage medium

Abstract

The present invention relates to the technical field of system architecture design, and specifically to an interface management method, device, electronic device and computer-readable storage medium. The method comprises: drawing a context relationship diagram according to the target organization system inventory information; parsing the context relationship diagram to obtain each system call relationship data; and managing each system data call interface according to the call relationship data. The technical solution provided in the present application digitizes the inter-system call relationship included in the context relationship design, and uses the digitized inter-system call relationship to guide and constrain the interface design and call in the implementation phase, thereby realizing the online, standardized and digitalized context relationship design, and improving the efficiency of the context relationship design.

Description

Technical Field

[0001] The present invention relates to the technical field of system architecture design, and in particular to an interface management method, device, electronic device and readable storage medium. Background Art

[0002] Different business subsystems of large-scale application systems also need to frequently share and interact with each other through internal WEB interfaces. As the scale of application systems becomes larger and larger, access between systems becomes more and more frequent. System context is a basic component in the system's software architecture. It provides an organizational view of how the system needs to interact with other systems and describes the business ecosystem in which the software is located. This view is particularly important in systems that are highly dependent on external organizations. However, the current system architecture design based on system context cannot apply the context relationship design in the overall system design phase to interface management, and interface management lacks architectural-level control. Summary of the invention

[0003] The purpose of this application is to solve at least one of the above technical defects. The technical solution adopted by this application is as follows:

[0004] In a first aspect, an embodiment of the present application discloses an interface management method, the method comprising:

[0005] Draw a context diagram based on the target organization system inventory information;

[0006] Parsing the context relationship graph to obtain the relationship data of each system call;

[0007] The system data calling interfaces are managed according to the calling relationship data.

[0008] In an optional embodiment, parsing the context relationship graph to obtain each system call relationship data includes:

[0009] The logical relationships among the system elements, container elements, and connection elements in the context relationship diagram are parsed, and the system call relationship data is obtained according to the logical relationships.

[0010] In an optional embodiment, the managing the data calling interfaces of each system includes:

[0011] According to the calling relationship data, a data calling interface between two systems is added or deleted.

[0012] In an optional embodiment, adding a data calling interface between two systems according to the calling relationship data includes:

[0013] Obtain basic information of the proposed new data call interface; the basic information includes but is not limited to: the system identifier to which the interface belongs, the interface protocol, the interface address to which the interface belongs, and the interface input and output parameters;

[0014] Based on the basic information, a new data calling interface is defined.

[0015] In an optional embodiment, the definition of the new data calling interface includes:

[0016] When the interface service provider in the call relationship data is monitored but there is no corresponding interface definition;

[0017] The user is prompted to define the data call interface.

[0018] In an optional embodiment, the managing the data calling interfaces of each system further comprises:

[0019] Configure the call control parameters of the data call interface.

[0020] In an optional embodiment, the calling control parameters for configuring the data calling interface include:

[0021] The monitoring found that the call relationship data contained a call relationship but lacked interface call control parameters;

[0022] The user is prompted to enter the call data interface control parameters of the call relationship subject.

[0023] On the other hand, an embodiment of the present application provides an interface management device, the device comprising: a context relationship drawing module, a parsing module and a management module, wherein:

[0024] The context relationship drawing module is used to draw a context relationship diagram according to the target organization system inventory information;

[0025] The parsing module is used to parse the context relationship graph and obtain the relationship data of each system call;

[0026] The management module is used to manage the system data calling interfaces according to the calling relationship data.

[0027] In a third aspect, an embodiment of the present application provides an electronic device, including a processor and a memory;

[0028] The memory is used to store operation instructions;

[0029] The processor is used to execute the method described in any of the above embodiments by calling the operation instruction.

[0030] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the method described in any of the above embodiments is implemented.

[0031] The interface management solution provided in the embodiment of the present application draws a context relationship diagram based on the target organization system inventory information; parses the context relationship diagram to obtain the call relationship data of each system; and manages the call interface of each system data based on the call relationship data. The beneficial effect brought by the technical solution provided in the embodiment of the present application is that the inter-system call relationship included in the context relationship design is digitized, and the digitized inter-system call relationship is used to guide and constrain the interface design and call in the implementation stage, thereby realizing the online, standardized and digitalized context relationship design, and improving the efficiency of context relationship design. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in describing the embodiments of the present application are briefly introduced below.

[0033] Figure 1 A schematic diagram of an interface management system provided in an embodiment of the present application;

[0034] Figure 2 A flowchart of an interface management method provided in an embodiment of the present application;

[0035] Figure 3 A schematic diagram of the structure of an interface management device provided in an embodiment of the present application;

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

[0037] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be interpreted as limiting the present invention.

[0038] Those skilled in the art will appreciate that, unless otherwise stated, the singular forms "a", "an", "said" and "the" used herein may also include plural forms. It should be further understood that the term "comprising" used in the specification of the present application refers to the presence of the features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof. The term "and / or" used herein includes all or any unit and all combinations of one or more associated listed items.

[0039] In addition, it should be understood that in the embodiments of the present application, "at least one" refers to one or more, and "plurality" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can represent: a, b, c, a and b, a and c, b and c, or a, b and c, where a, b, c can be single or multiple.

[0040] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0041] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0042] Based on the various problems existing in the interface management process introduced in the background technology, the following embodiments of the present invention provide an interface management method to solve at least one of the above defects.

[0043] Figure 1 The system architecture based on which the method for implementing an interface management provided in an embodiment of the present application is implemented is shown. Figure 1The architecture at least includes: 101 architecture design system, 102 interface design system, 103 interface call control system. In the development process of IT projects, designers use contextual relationship design in the overall design. The architecture design system generates call relationship data between systems based on the completed contextual relationship design, and sends the data to the interface design system and the interface call control system. The interface design system uses the data to support the interface design work of interface designers, and the interface call control system uses the data to support interface call management work. Further,

[0044] The 101 architecture design system includes a 1011 system inventory information management module, a 1012 context drawing module, a 1014 data synchronization module and a 1013 parsing module.

[0045] The interface design system 102 includes an interface definition module 1021 and a data synchronization module 1022; wherein the interface definition module 1021 includes the management module 303 of the following embodiment, that is, has the functions of the management module 303 of the following embodiment.

[0046] The interface call control system 103 includes an interface call control module 1031 and a data synchronization module 1032; wherein the interface call control module 1021 includes the management module 303 of the following embodiment, that is, has the functions of the management module 303 of the following embodiment.

[0047] The above three systems are introduced as follows:

[0048] The 101 architecture design system includes a 1011 system inventory information management module, a 1012 context drawing module, a 1013 parsing module and a 1014 data synchronization module, wherein:

[0049] The 1011 system list information management module is used to manage the system list information within a certain organization. The information item of each system in the system list includes at least the system identification and the basic information of the system. The basic information includes at least the system name.

[0050] The 1012 context relationship drawing module is used to draw a context relationship diagram, including a canvas area, a drawing resource area, and a toolbar area. The canvas area is a drawing area for realizing the drawing elements of the context relationship diagram. The drawing resource area provides the selection of elements related to the context relationship diagram drawing, and elements can be dragged to the canvas. The elements include system elements, container elements, and connection elements. The data of the system elements are obtained from the system inventory information management module. A system element is associated with the information of a system in the system inventory. The drawing resource area can provide a search box, and the user enters the system information in the search box to retrieve the required system elements. The system element dragged to the canvas area becomes a system element instance. The system element instance is displayed as a rectangle or other shape, and the system name of the system information associated with the system element instance can be displayed in the shape. The container element refers to an element that can logically contain one or more system elements. The container element dragged to the canvas area becomes a container element instance, which is displayed as a rectangle, and can be enlarged or reduced by dragging the border of the container element instance. The name of the container element instance can be edited by double-clicking or other methods, and the edited name is presented in the edge area of ​​the container element instance. In the canvas area, the system element instances within the border of a container element instance are logically considered to belong to the container element instance. A line element is an element that can connect system elements with system elements, container elements with container elements, or system elements with container elements. Line elements can represent different types of inter-system call relationships based on different colors and line segment types. Typically, green line elements can represent inter-system call relationships of HTTP protocol, blue line elements can represent inter-system call relationships of other protocols, solid line elements can represent inter-system call relationships of real-time calls, and dotted line elements can represent inter-system call relationships of batch calls. Various optional line elements are listed in the drawing resource area. A line element is dragged to the canvas area to become a line element instance, which is displayed as a straight line or a polyline. The line element instance can be connected to the border of a system element instance or a container element instance by dragging either end of the line element instance. An arrow must be set at either end of the connection element instance. The system element instance pointed to by one end of the arrow or the system element instance contained in the container element instance, and the system associated with these pointed system element instances is the provider of the interface service; the system element instance pointed to by the other end or the system element instance contained in the container element instance, and the system associated with these system element instances is the caller of the interface service. The calling purpose information of the connection element instance can be edited by double-clicking or other methods. As a description of the calling purpose of the interface, the calling purpose information appears in the middle or surrounding area of ​​the connection element instance.

[0051] The parsing module 1013 is used to parse the context relationship diagram drawn by the user in the canvas area of ​​the context relationship drawing module, and parse the context relationship diagram into call relationship data between various systems according to the positions of various elements in the canvas area, and save the data.

[0052] The information items of the calling relationship data between systems include but are not limited to: interface service caller system identification, interface service provider system identification, interface protocol, calling method (batch calling or real-time calling), calling purpose description and other information.

[0053] The 1014 data synchronization module is used for data synchronization with other systems, including synchronization of system inventory information data and synchronization of call relationship data between systems.

[0054] 102 The interface design system includes 1021 an interface definition module and 1022 a data synchronization module, wherein:

[0055] The interface definition module 1021 can maintain and manage the interface definition data of a certain system.

[0056] The information items of the interface definition data include at least: the system identifier to which the interface belongs, the interface protocol, the interface address to which the interface belongs, the interface input and output parameters, etc. The interface definition module can prompt the user to create a new interface or delete an interface for a certain system based on the call relationship data between systems.

[0057] The 1022 data synchronization module is used to synchronize data with the architecture design system, including synchronization of system inventory information data and synchronization of call relationship data between systems.

[0058] 103 interface call control system includes 1031 interface call control module and 1032 data synchronization module, wherein:

[0059] The interface call control module 1031 can control whether a system can call the interface of another system in the operating environment according to the interface call control data configured by the user. The information items of the interface call control data should at least include: the allowed interface service caller system identifier and the system identifier to which the interface belongs. The interface call module can also configure the interface call control information according to the call relationship data between the systems.

[0060] The data synchronization module 1032 is used to synchronize data with the architecture design system, including synchronization of system inventory information data and synchronization of call relationship data between systems.

[0061] In the embodiment of the present application, the architecture design system sends the entered system inventory information to the data synchronization module of the interface design system through the data synchronization module, and the interface design system saves the system inventory information as the basic information for maintaining and managing the interface information with the system as the dimension. The architecture design system sends the entered system inventory information to the data synchronization module of the interface call control system through the data synchronization module, and the interface call control system saves the system inventory information as the basic information for managing the interface call control information with the system as the dimension.

[0062] Figure 2 A schematic diagram of an interface management process provided by an embodiment of the present application is shown, such as Figure 2 As shown, the method may mainly include:

[0063] S201. Draw a context relationship diagram based on the target organization system inventory information. The specific implementation process is as follows:

[0064] Step 1: Enter the target organization system inventory information: that is,

[0065] The user enters the system inventory information within the organization in the system inventory information management module of the architecture design system. The system inventory information contains information of at least two systems. The architecture design system saves the system inventory information as the data foundation information of the system elements of the context relationship drawing module.

[0066] Step 2: Draw a context relationship diagram; wherein the context relationship diagram is drawn in a context relationship drawing module of the architecture design system, and the steps of the drawing method include:

[0067] Step 2-1: The user selects a main system as the context diagram.

[0068] Step 2-2, search the inter-system call relationship data related to the main system selected by the user from the existing inter-system call relationship data, that is, the main system as the interface service caller or interface service provider. If not, display the main system as a system element instance on the canvas and go to step 2-5; if yes, display the inter-system call relationship data for the user to select.

[0069] Step 2-3: The user selects the stock inter-system call relationship data related to the main system.

[0070] Step 2-4: Display the main system as a system element instance on the canvas, and convert the selected call relationship data into system element instances and connection element instances and display them on the canvas, that is, convert the interface service caller or interface service provider that is not the main system in the call relationship data into a system element instance, and convert the interface protocol, call method, call purpose description and other information in the call relationship data into a connection element instance. The connection element instance is connected to the border of the system element instance corresponding to the interface service caller or interface service provider according to the call relationship data, and the arrow points to the interface service provider.

[0071] Step 2-5, the user selects system elements, container elements, and connection elements from the drawing resource area and drags them into the canvas. System elements can also be found by searching in the drawing resource area. The user can arrange the positions of system element instances and container element instances in the canvas area, and can drag multiple system element instances into the border of a container element instance. The user can drag the connection element instance to connect it to the border of the system element instance or container element instance.

[0072] Step 2-6: Save the drawn context diagram.

[0073] S202, parsing the context relationship diagram to obtain the call relationship data of each system; that is, when saving the context relationship diagram, the context relationship drawing module of the architecture design system parses the context relationship diagram to generate the call relationship data between each system. The logical relationship between the system elements, container elements, and connection elements in the context relationship diagram is parsed, and the call relationship data of each system is obtained according to the logical relationship, that is, it is realized by the position of each element in the canvas area. The parsing content and method include:

[0074] Step 1: parse all line element instances in the canvas.

[0075] Step 2: parse all container element instances in the canvas and the system element instances contained in each container element instance.

[0076] Step 3, parse the system element instances or container element instances connected to the two ends of each connection element instance. Assume that the system element instances contained in the system element instances or container element instances at one end of a connection instance element constitute a set S1, and the system element instances contained in the system element instances or container element instances at the other end constitute a set S2, and the connection element instance is L1. Each system element instance in the S1 set has a calling relationship with each system element instance in the S2 set, and the calling relationship information is based on the information contained in L1. For example, if the L1 arrow points to S2, then the system element instances in S2 all serve as interface service providers, the system element instances in S1 all serve as interface service callers, the interface protocol represented by L1 serves as the interface protocol, the calling method represented by L1 serves as the calling method, and the calling purpose represented by L1 serves as the calling purpose description information.

[0077] Step 4: Generate the call relationship data between all systems in the canvas based on the above analysis results, and save the data in the system.

[0078] S203: managing the system data calling interfaces according to the calling relationship data.

[0079] In an optional embodiment, managing the data calling interfaces of each system includes adding or deleting a data calling interface between two systems.

[0080] The new addition is based on the fact that when the interface service provider appears in the monitoring call relationship data but there is no corresponding interface definition; the user is prompted to make a data call interface definition. Further implementation details are: the interface design system synchronizes the full amount of inter-system call relationship data organized from the architecture design system through the data synchronization module. The interface design system searches for systems that appear as interface service providers in the inter-system call relationship data and have no interface definitions of corresponding interface protocols in the interface design system, and prompts the user to enter the interface definition data of the corresponding interface protocol of the system.

[0081] The deletion is based on the interface design system searching for systems that have interface definitions in the interface design system and do not appear as interface service providers of the corresponding interface protocols in the inter-system call relationship data, and prompting the user to delete or automatically deleting the interface definition data of the corresponding interface protocols of the system.

[0082] In an optional embodiment, the managing the data call interface of each system further includes: configuring the call control parameters of the data call interface, and the configuration further includes entering or deleting the call control configuration data. The implementation details are:

[0083] First, the interface calls the control system through the data synchronization module to synchronize the full amount of inter-system call relationship data organized by the architecture design system.

[0084] When the interface call control system searches for a call relationship in the call relationship data between systems, but the call control configuration data for calling both systems of the call relationship is not configured in the interface call control system, the user is prompted to enter the interface call control configuration data of both systems. For example, in the call relationship data between systems, there is one or more data indicating that system A calls system B, but in the interface call control system, the call control configuration for system A to call any interface of system B is not configured, and the interface call control system prompts the user to enter the call control configuration data for system A to call any interface of system B.

[0085] When the interface call control system searches for call control information between two systems that has been configured in the call control configuration data, but does not find the configuration data of the call relationship between the two systems in the call relationship data between the systems, the user is prompted to delete or automatically delete all the call control configuration data of the two systems. For example, in the call control configuration data, there is a configuration that system A accesses a certain interface of system B, but in the call relationship data between the systems, no data is found that the interface service caller is system A and the interface service provider is system B. The interface call control system prompts the user to delete or automatically delete the call control configuration data of system A calling all interfaces of system B.

[0086] based on Figure 2 The interface management method shown in the figure, on the other hand, the embodiment of the present application provides an interface management device, such as Figure 3 As shown, the device may include a context relationship drawing module 1012, a parsing module 1013 and a management module 303, wherein:

[0087] The context relationship drawing module 1012 is used to draw a context relationship diagram according to the target organization system list information;

[0088] The analysis module 1013 is used to analyze the context relationship graph and obtain the relationship data of each system call;

[0089] The management module 303 is used to manage the system data calling interfaces according to the calling relationship data.

[0090] It can be understood that the above-mentioned components of the interface management in this embodiment have the function of implementing Figure 2 The functions of the corresponding steps of the method in the embodiment shown in . The function can be implemented by hardware, or by hardware executing the corresponding software. The hardware or software includes one or more modules or devices corresponding to the above functions. The above modules and devices can be software and / or hardware, and the above modules and devices can be implemented separately or integrated with multiple modules and devices. For the functional description of the above modules and devices, please refer to Figure 2The corresponding description of the method in the embodiment shown in , therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding method provided above, which will not be repeated here.

[0091] It is to be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the specific structure of the interface management device. In other embodiments of the present application, the interface management device may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0092] An embodiment of the present application provides an electronic device, including a processor and a memory;

[0093] A memory, used for storing operation instructions;

[0094] The processor is used to execute the interface management method provided in any embodiment of the present application by calling an operation instruction.

[0095] As an example, Figure 4 A schematic diagram of the structure of an electronic device applicable to the embodiment of the present application is shown. Figure 4 As shown, the electronic device 2000 includes: a processor 2001 and a memory 2003. Among them, the processor 2001 and the memory 2003 are connected, such as being connected through a bus 2002. Optionally, the electronic device 2000 may also include a transceiver 2004. It should be noted that in actual applications, the transceiver 2004 is not limited to one. It is understandable that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the specific structure of the electronic device 2000. In other embodiments of the present application, the electronic device 2000 may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware. Optionally, the electronic device may also include a display screen 2005 for displaying images, or receiving user operation instructions when necessary.

[0096] The processor 2001 is applied in the embodiment of the present application to implement the method shown in the above method embodiment. The transceiver 2004 may include a receiver and a transmitter. The transceiver 2004 is applied in the embodiment of the present application to implement the function of the electronic device of the embodiment of the present application communicating with other devices when executed.

[0097] Processor 2001 may be a CPU (Central Processing Unit), a general purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. Processor 2001 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0098] The processor 2001 may also include one or more processing units, for example: the processor 2001 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a memory, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and / or a neural network processor (Neural-network Processing Unit, NPU), etc. Among them, different processing units can be independent devices or integrated in one or more processors. Among them, the controller can be the nerve center and command center of the electronic device 2000. The controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions. A memory can also be set in the processor 2001 for storing instructions and data. In some embodiments, the memory in the processor 2001 is a high-speed cache memory. The memory can save instructions or data that the processor 2001 has just used or circulated. If the processor 2001 needs to use the instruction or data again, it can be directly called from the memory. Repeated access is avoided, the waiting time of the processor 2001 is reduced, and the efficiency of the system is improved.

[0099] The processor 2001 can run the interface management method provided in the embodiment of the present application to reduce the user's operation complexity, improve the intelligence of the terminal device, and enhance the user experience. The processor 2001 can include different devices. For example, when the CPU and GPU are integrated, the CPU and GPU can cooperate to execute the interface management method provided in the embodiment of the present application. For example, part of the algorithm in the interface management method is executed by the CPU, and the other part of the algorithm is executed by the GPU to obtain faster processing efficiency.

[0100] The bus 2002 may include a path to transmit information between the above components. The bus 2002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 2002 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0101] The memory 2003 may be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory), or may include a high-speed random access memory, or may include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), a disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this.

[0102] Optionally, the memory 2003 is used to store application code for executing the solution of the present application, and the execution is controlled by the processor 2001. The processor 2001 is used to execute the application code stored in the memory 2003 to implement the interface management method provided in any embodiment of the present application.

[0103] The memory 2003 can be used to store computer executable program codes, which include instructions. The processor 2001 executes various functional applications and data processing of the electronic device 2000 by running the instructions stored in the memory 2003. The memory 2003 may include a program storage area and a data storage area. Among them, the program storage area can store the code of the operating system, application program, etc. The data storage area can store data created during the use of the electronic device 2000 (such as images, videos, etc. collected by the camera application), etc.

[0104] The memory 2003 may also store one or more computer programs corresponding to the interface management method provided in the embodiment of the present application. The one or more computer programs are stored in the above-mentioned memory 2003 and are configured to be executed by the one or more processors 2001. The one or more computer programs include instructions, and the above-mentioned instructions can be used to execute each step in the above-mentioned corresponding embodiment.

[0105] Of course, the code of the interface management method provided in the embodiment of the present application can also be stored in an external memory. In this case, the processor 2001 can run the code of the interface management method stored in the external memory through the external memory interface, and the processor 2001 can control the operation interface management process.

[0106] The display screen 2005 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Miniled, a MicroLed, a Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 2000 may include 1 or N display screens 2005, where N is a positive integer greater than 1. The display screen 2005 can be used to display information input by a user or information provided to a user and various graphical user interfaces (GUI). For example, the display screen 2005 can display photos, videos, web pages, or files, etc.

[0107] The electronic device provided in the embodiment of the present application is applicable to any embodiment of the above method. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, which will not be repeated here.

[0108] An embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, the interface management method shown in the above method embodiment is implemented.

[0109] The computer-readable storage medium provided in the embodiment of the present application is applicable to any embodiment of the above-mentioned method. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, which will not be repeated here.

[0110] The embodiment of the present application also provides a computer program product, which, when executed on a computer, enables the computer to execute the above-mentioned related steps to implement the method in the above-mentioned embodiment. The computer program product provided in the embodiment of the present application is applicable to any embodiment of the above-mentioned method, and therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, which will not be repeated here.

[0111] The interface management solution provided in the embodiment of the present application draws a context relationship diagram based on the target organization system inventory information; parses the context relationship diagram to obtain the call relationship data of each system; and manages the call interface of each system data based on the call relationship data. The beneficial effect brought by the technical solution provided in the embodiment of the present application is that the inter-system call relationship included in the context relationship design is digitized, and the digitized inter-system call relationship is used to guide and constrain the interface design and call in the implementation stage, thereby realizing the online, standardized and digitalized context relationship design, and improving the efficiency of context relationship design.

[0112] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of modules or units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another device, or some features can be discarded or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0113] The units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0114] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0115] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

[0116] It should be understood that, although the steps in the flowchart of the accompanying drawings are displayed in sequence as indicated by the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps.

[0117] The above contents are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, and can also make some improvements and modifications. These changes, substitutions, improvements and modifications should also be considered to be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. An interface management method, characterized in that: The method comprises: Draw a context diagram based on the target organization system inventory information; Parsing the context relationship graph to obtain the relationship data of each system call includes: Analyze the logical relationship between the system elements, container elements, and connection elements in the context relationship diagram, and obtain the system call relationship data according to the logical relationship; According to the call relationship data, managing the system data call interfaces includes: According to the calling relationship data, a data calling interface between two systems is added or deleted.

2. The interface management method according to claim 1, characterized in that: The newly added data calling interface between the two systems according to the calling relationship data includes: Obtain basic information of the proposed new data call interface; the basic information includes but is not limited to: the system identifier to which the interface belongs, the interface protocol, the interface address to which the interface belongs, and the interface input and output parameters; Based on the basic information, a new data calling interface is defined.

3. The interface management method according to claim 2, characterized in that: The definition of the new data calling interface includes: When the interface service provider in the monitoring call relationship data appears but there is no corresponding interface definition; The user is prompted to define the data call interface.

4. The interface management method according to claim 3, characterized in that: The management of each system data calling interface further includes: Configure the call control parameters of the data call interface.

5. The interface management method according to claim 4, characterized in that: The calling control parameters for configuring the data calling interface include: The monitoring found that the call relationship data contained a call relationship but lacked interface call control parameters; The user is prompted to enter the call data interface control parameters of the call relationship subject.

6. An interface management device, characterized in that: The device comprises: a context relationship drawing module, a parsing module and a management module, wherein: The context relationship drawing module is used to draw a context relationship diagram according to the target organization system inventory information; The parsing module is used to parse the context relationship graph and obtain the relationship data of each system call, including: Analyze the logical relationship between the system elements, container elements, and connection elements in the context relationship diagram, and obtain the system call relationship data according to the logical relationship; The management module is used to manage the system data calling interfaces according to the calling relationship data, including: According to the calling relationship data, a data calling interface between two systems is added or deleted.

7. An electronic device, characterized in that: including a processor and a memory; The memory is used to store operation instructions; The processor is used to execute the method according to any one of claims 1 to 5 by calling the operation instruction.

8. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.

Images