A visual interface management method, system, terminal and storage medium

Abstract

The application relates to a visual interface management method, a system, a terminal and a storage medium, wherein the method comprises the following steps: configuring an interface, and generating a parameter model corresponding to the interface; generating a node model corresponding to the interface on an interactive visual interface according to the parameter model, wherein the node model comprises a front-end model, a database model and a back-end model; configuring configuration information corresponding to the node model, wherein the configuration information comprises front-end request parameters corresponding to the front-end model, data information corresponding to the database model and back-end return parameters corresponding to the back-end model; and generating front-end source code and back-end source code according to the node model and the configuration information. According to the application, the interface is visually modeled, the relationship among the front end, the database and the back end of the interface is established by using the visual node model, human-computer interaction of interface management services can be provided for developers, product personnel and testers, the engineering amount of interface source code development in the development process is reduced, and the development efficiency is greatly improved.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of data processing, and particularly relates to a visual interface management method and system, a terminal and a storage medium. BACKGROUND

[0002] Generally, during the system development stage, the general developers often have problems such as uncertainty, difficulty in maintenance and difficulty in testing in the interface development process, which leads to frequent modification and testing of the interface, large workload and influence on the development progress of the project. Meanwhile, the demand of enterprises for informatization systems is complex and changeable. The more complex the demand of enterprises is, the more business interfaces are involved. If the demand changes, more software systems need to be updated, added and modified, and the workload and risk will also increase.

[0003] At present, the interface development mode, especially the interface development and design personnel, spends a large amount of working time on interface definition and maintenance; for different interfaces, corresponding entity objects, parameter verification logic, object binding logic and object conversion logic need to be developed, and the processing logic between different interfaces is difficult to reuse and unify, which leads to bulky and huge code, poor readability, great complexity in daily maintenance, difficult improvement of daily development efficiency, frequent changes of interface definition and easy production of fault problems. Therefore, the existing interface management platform has the following shortcomings:

[0004] 1) The workload of traditional development and maintenance of system interfaces is large, the development efficiency is low, and there is a lack of visual development support.

[0005] 2) The traditional interface development process lacks creation and field maintenance of database tables, which affects the system development progress.

[0006] 3) The traditional interface development process lacks integrated consideration of front-end and back-end + database integrated closed-loop management, and the efficiency is not high. SUMMARY

[0007] The application aims to provide a visual interface management method, system, terminal and storage medium, and aims to solve the problems of large workload of development and maintenance of system interfaces, low development efficiency and difficulty in creation and maintenance of databases in the traditional interface management platform.

[0008] The first aspect of the embodiment of the application provides a visual interface management method, which comprises the following steps:

[0009] configuring an interface and generating a parameter model corresponding to the interface;

[0010] generating a node model corresponding to the interface on an interactive visual interface according to the parameter model, the node model comprising a front-end model, a database model and a back-end model;

[0011] The configuration information corresponding to the node model includes front-end request parameters corresponding to the front-end model, data information corresponding to the database model, and back-end return parameters corresponding to the back-end model;

[0012] The front-end source code and the back-end source code are generated according to the node model and the configuration information.

[0013] Preferably, the node model corresponding to the interface is generated on the interactive visualization interface according to the parameter model, and the node model includes a front-end model, a database model, and a back-end model, and includes:

[0014] The first node graph and the second node graph are arranged on the interactive visualization interface based on the parameter model, the first node graph corresponds to the front-end model, and the second node graph corresponds to the back-end model;

[0015] The database editing statement corresponding to the database model is generated on the interactive visualization interface according to a preset database structure template.

[0016] Preferably, the first node graph includes a first sub-node, the second node graph includes a second sub-node, and the configuration information corresponding to the node model includes:

[0017] The first sub-node is configured through the front-end request parameters of the interface;

[0018] The second sub-node is configured through the back-end return parameters of the interface.

[0019] Preferably, the configuration information corresponding to the node model further includes:

[0020] The front-end request parameters and the data information of the interface are filled into the database editing statement of the corresponding database table;

[0021] The database is generated according to the return result of the database editing statement.

[0022] Preferably, the above method further includes:

[0023] The back-end return parameters of the interface are obtained according to the return result of the database editing statement.

[0024] In any of the above technical solutions, the configuration interface includes:

[0025] Basic information of the interface is filled in, and the basic information includes interface function description and interface link address;

[0026] The interface is classified according to the basic information of the interface.

[0027] In any of the above technical solutions, preferably, after the front-end source code and the back-end source code are generated according to the node model and the configuration information, the method further comprises:

[0028] According to the front-end source code and the back-end source code, the data flow of the interface is tested, and the abnormality of the data flow is dynamically marked through the visual interface.

[0029] In any of the above technical solutions, preferably, according to the front-end source code and the back-end source code, the data flow of the interface is tested, and the abnormality of the data flow is dynamically marked through the visual interface.

[0030] When the data flow of the interface is normal, the front-end source code and the back-end source code are exported and deployed as a business interface.

[0031] The second aspect of the embodiment of the application provides a visual interface management system, comprising:

[0032] An interface configuration module is configured to configure an interface and generate a parameter model corresponding to the interface;

[0033] A node model generation module is configured to generate a node model corresponding to the interface on an interactive visual interface according to the parameter model, wherein the node model comprises a front-end model, a database model and a back-end model;

[0034] A node model configuration module is configured to configure configuration information corresponding to the node model, wherein the configuration information comprises front-end request parameters corresponding to the front-end model, data information corresponding to the database model and back-end return parameters corresponding to the back-end model;

[0035] A code generation module is configured to generate front-end source code and back-end source code according to the node model and the configuration information.

[0036] The third aspect of the embodiment of the application provides a visual interface management terminal, comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method when executing the computer program.

[0037] The fourth aspect of the embodiment of the application provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program is executable by a processor to implement the steps of the method.

[0038] Compared with the prior art, the beneficial effects of the embodiment of the application are as follows: the visual interface management method can provide better human-computer interaction interface management services for developers, product personnel and testers by visual modeling of the interface, establishing the relationship between the front end, the database and the back end of the interface through the visual node model, reducing the development engineering amount of the interface source code in the development process and greatly improving the development efficiency. Attached Figure Description

[0039] Figure 1 A flowchart illustrating a visual interface management method provided in one embodiment of this application;

[0040] Figure 2 A detailed flowchart of a visual interface management method provided in one embodiment of this application;

[0041] Figure 3 A visual diagram illustrating the construction and configuration of the front-end model;

[0042] Figure 4 A visual diagram illustrating the construction and configuration of statements for inserting data into a database model;

[0043] Figure 5 A visual diagram illustrating the construction and configuration of database model query statements;

[0044] Figure 6 A visual diagram illustrating the construction and configuration of database model update statements;

[0045] Figure 7 A visual diagram illustrating the construction and configuration of delete statements for a database model;

[0046] Figure 8 This is a schematic diagram illustrating the visualization operation of a database model in one embodiment;

[0047] Figure 9 This is a schematic diagram illustrating the database model visualization operation in another embodiment;

[0048] Figure 10 A diagram illustrating the construction and configuration of the backend model;

[0049] Figure 11 A schematic diagram of a visualization interface for data flow verification provided in an embodiment of this application;

[0050] Figure 12 This is a schematic diagram of the structure of a visual interface management system provided in one embodiment of this application;

[0051] Figure 13 This is a schematic diagram of a visual interface management terminal device provided in an embodiment of the present invention. Detailed Implementation

[0052] To make the technical problems, technical solutions, and beneficial effects to be solved by this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and are not intended to limit the scope of this application.

[0053] It should be understood that the terms "length", "width", "upper", "lower", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer" and the like indicate the orientation or positional relationship based on the orientation or positional relationship shown in the drawings, and are only for the convenience of describing the present application and simplifying the description, and do not indicate or imply that the devices or elements referred to must have a particular orientation, be constructed and operated in a particular orientation, and therefore cannot be understood as limiting the present application.

[0054] In addition, the terms "first", "second" are only for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined with "first", "second" can explicitly or implicitly include one or more of the features. In the description of the present application, the meaning of "multiple" is two or more, unless otherwise specifically limited.

[0055] API is a set of pre-defined interfaces (such as functions, HTTP interfaces), or a convention for the connection of different components of a software system; used to provide a set of routines that application programs can access based on a certain software or hardware without accessing the source code or understanding the details of the internal working mechanism; the operating system provides a "program interface" for programmers, also known as application program interface; the interface is used by programmers when programming, and through this interface, the system and the application program can access the resources in the system and obtain the services of the OS, which is the only way for the program to obtain the services of the operating system; the program interface of most operating systems is composed of a set of system calls (system calls), each system call is a subroutine that can complete a specific function; application programming interface is a set of definitions, programs and protocols, which realizes the mutual communication between computer software through API interface; one of the main functions of API is to provide a set of common functions; API is also a kind of middleware, which provides data sharing for various platforms; Internet-based applications are becoming more and more popular, and in this process, more and more sites will open their resources to developers for calling. The API call provided to the outside makes the content of the sites more related, and these open platforms also bring greater value to users, developers and small and medium-sized websites. In order to provide a unified API interface to the outside, the site needs to provide an open and unified API interface environment for the developer to open the resource calling API, to help users access the functions and resources of the site.

[0056] Figures 1-2 A flowchart of a visual interface management method provided by the first embodiment of the present application is shown, only the part related to the present embodiment is shown for the convenience of description, and the details are as follows:

[0057] S102, configure an interface and generate a parameter model corresponding to the interface.

[0058] First, before visual management of the interface, the interface needs to be configured first. By filling in the interface basic information including interface function description and interface link address, then according to the basic information of the interface, the interface is classified. For example, in the embodiment of the application, the interface can be simply divided into two categories of front-end interface and back-end interface, and the type of the interface can also be subdivided according to the classification of the front-end interface and the back-end interface.

[0059] According to the interface function description and the interface link address, the parameter model corresponding to the interface is generated.

[0060] In one or more embodiments, the interface can be configured through an interactive visualization interface, or the configuration file of the interface can be directly uploaded to generate the parameter model corresponding to the interface.

[0061] S104, generating a node model corresponding to the interface on the interactive visualization interface according to the parameter model.

[0062] It should be noted that the above node model includes a front-end model, a database model and a back-end model.

[0063] In one or more embodiments, the front-end model of the interface is displayed in the form of a first node graph on the interactive visualization interface. Each interface generates a plurality of sub-nodes according to the corresponding parameter model. The sub-nodes are the request parameters of the front-end interface. Different types of sub-nodes are generated according to the request parameter types of the front-end interface. Different types of sub-nodes can be displayed in different forms on the interactive visualization interface, including but not limited to shape, color and the like. Program designers can drag the sub-nodes on the interactive visualization interface to generate the node graph corresponding to the interface.

[0064] In one or more embodiments, the back-end model of the interface can be displayed in the form of a second node graph on the interactive visualization interface. Each interface generates a plurality of sub-nodes according to the corresponding parameter model. The sub-nodes are the return parameters of the back-end interface. Different types of sub-nodes are generated according to the return parameter types of the back-end interface. Different types of sub-nodes can be displayed in different forms on the interactive visualization interface, including but not limited to shape, color and the like. Program designers can drag the sub-nodes on the interactive visualization interface to generate the node graph corresponding to the interface.

[0065] In one or more embodiments, the database model is configured according to a preset database structure template on the interactive visualization interface, and a corresponding database editing statement can be obtained by a programmer, and the relationship between the database table and the field in the database is preset by arranging the database editing statement to form an initialized database.

[0066] S106, configure the configuration information corresponding to the node model.

[0067] It should be noted that the above configuration information includes the front-end request parameter corresponding to the front-end model, the data information corresponding to the database model, and the back-end return parameter corresponding to the back-end model.

[0068] In one or more embodiments, the configuration of the front-end interface is completed by editing the front-end request parameter of each sub-node in the first node graph on the interactive visualization interface.

[0069] In one or more embodiments, the configuration of the back-end interface is completed by editing the back-end return parameter of each sub-node in the second node graph on the interactive visualization interface.

[0070] In one or more embodiments, the configuration of the database is completed by filling the database table and the field in the database editing statement on the interactive visualization interface.

[0071] It should be noted that in the configuration process of the database, the field corresponding to the database table can be filled by calling the front-end request parameter of the sub-node in the first node graph, and correspondingly, in the process of configuring the back-end interface, the back-end return parameter can be filled according to the return result of the database editing statement.

[0072] S108, generate the front-end source code and the back-end source code according to the node model and the configuration information.

[0073] Through the above steps, the relationship between each request parameter in the front-end interface, the database table in the database, and each return parameter in the back-end interface is established, and the corresponding front-end source code and back-end source code are generated through the above relationship and the corresponding node model.

[0074] It should be understood that the size of the serial number of each step in the above embodiments does not mean the order of execution, and the execution order of each process should be determined according to its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0075] Figure 3A visual operation diagram of construction and configuration of a front-end model provided for the second embodiment of the present embodiment is shown in the figure. In the present embodiment, the front-end interface is visualized by the mode of the node graph, and the front-end information of the API interface is edited by three operation methods of adding a sub-node, deleting a sub-node and modifying a sub-node. In the node graph, one sub-node represents one request parameter of the front-end interface, and the parameter type can be self-defined and the test value can be set. The number of sub-nodes represents the number of parameters requested by the front-end interface.

[0076] Figures 4-7 A visual operation diagram of construction and configuration of a database model provided for the third embodiment of the present application is shown in the figure. SQL statement is a database query and program design language for accessing data and querying, updating and managing a relational database system, i.e. a language for operating a database. It has a fixed structure mode. The construction of the database model includes visualizing the SQL language, i.e. generating the database editing statements corresponding to the four operation methods of inserting, deleting, querying and modifying by using the preset templates. When the program designers design, they only need to simply call the database editing statements involved according to the front-end interface model and fill in the database tables and parameters involved.

[0077] In one or more embodiments, the database table (users) and field (name) are quickly input by the fixed structure template form, and after inputting once, they can be saved for reuse next time, which can reduce the tedious input process time. The field assignment such as parm5 and parm6 in the figure is the interface parameter created in the front-end interface configuration process, which can be directly called and filled in, so as to connect the request parameters of the interface with the field values of the database editing statement.

[0078] Further, referring to Figure 8 In order to reduce the tediousness of frequent keyboard input, in the visual operation process of the database statement editing, options can be provided for the user to select according to the function.

[0079] In one or more embodiments, referring to Figure 9 The above technical solution also supports the creation of the database table and the intelligent generation and maintenance of the field. In the database statement editing operation process, the user can collect the information of the existing field and database table, display them in the form of a list and perform secondary maintenance information, confirm the creation of the database table, and synchronize to the finally generated specific database, so as to avoid errors in the database statement editing operation.

[0080] Figure 10A visual operation schematic diagram of construction and configuration of a backend interface model provided by the third embodiment of the application, in the embodiment, the response information of the backend of the API interface is visualized managed through the mode of the node graph, through three operation methods of adding a subnode, deleting a subnode and modifying a subnode, one subnode represents the return parameter of the backend interface, the parameter value and type can be customized, the assignment of the parameter value is from the operation result return of the aforementioned database editing statement, the parameter value is extracted into variables (parm5, parm6, parm7) in an array form respectively, and a test value can also be set. The number of subnodes represents the number of parameters of the backend interface response.

[0081] In one or more embodiments, referring to Figure 11 , through the relationship form of visualized data flow, the data flow connectivity and accuracy of the front-end and backend and the database of the interface are tested in one key. The connection between nodes is marked by different colors or forms to indicate data flow abnormalities or normality, so that it can be directly observed which path of the front-end-backend-database occurs error.

[0082] In one or more embodiments, after the front-end node design, the database statement editing and the data logic test are completed, the real-time preview, copying and one-key export of the source code of the front-end and backend interface can be performed.

[0083] Referring to Figure 12 , the visual interface management system provided by one embodiment of the application comprises:

[0084] An interface configuration module is configured to configure an interface and generate a parameter model corresponding to the interface;

[0085] A node model generation module is configured to generate a node model corresponding to the interface on an interactive visual interface according to the parameter model, the node model comprising a front-end model, a database model and a backend model;

[0086] A node model configuration module is configured to configure configuration information corresponding to the node model, the configuration information comprising a front-end request parameter corresponding to the front-end model, data information corresponding to the database model and a backend return parameter corresponding to the backend model;

[0087] A code generation module is configured to generate a front-end source code and a backend source code according to the node model and the configuration information.

[0088] In one or more embodiments, the node model generation module comprises:

[0089] An arrangement module is configured to arrange a first node graph and a second node graph on the interactive visual interface based on the parameter model, the first node graph corresponding to the front-end model and the second node graph corresponding to the backend model;

[0090] The database statement generation module is configured to generate a database editing statement corresponding to a database model on the interactive visual interface according to a preset database structure template.

[0091] In one or more embodiments, the first node graph includes a first sub-node, the second node graph includes a second sub-node, and the node model configuration module includes:

[0092] The first sub-node configuration module is configured to configure the first sub-node through a front-end request parameter of the interface.

[0093] The second sub-node configuration module is configured to configure the second sub-node through a back-end return parameter of the interface.

[0094] In one or more embodiments, the node model configuration module further includes:

[0095] The database statement editing module is configured to fill the front-end request parameter and the data information of the interface into a database editing statement of a corresponding database table.

[0096] The database generation module is configured to generate a database according to a return result of the database editing statement.

[0097] In one or more embodiments, the interface configuration module includes:

[0098] The basic information filling module is configured to fill basic information of the interface, and the basic information includes an interface function description and an interface link address.

[0099] The interface classification module is configured to classify the interface according to the basic information of the interface.

[0100] In one or more embodiments, the data flow inspection module is further configured to test a data flow of the interface according to the front-end source code and the back-end source code, and dynamically mark an exception of the data flow through a visual interface.

[0101] In one or more embodiments, the business interface deployment module is further configured to export the front-end source code and the back-end source code when the data flow of the interface has no exception, and deploy the front-end source code and the back-end source code as a business interface.

[0102] The application greatly improves the interactive experience of interface visual management through the node graph mode, and improves the work efficiency of developers.

[0103] The application supports quick creation of a database table and field maintenance in the process of interface management, and reduces the system development workload.

[0104] The application comprehensively considers integrated closed-loop management of front-end and back-end + database, one-key synchronous generation of front-end and back-end codes and SQL statements of the database, and secondary development of project engineering, which can greatly reduce the development workload.

[0105] Figure 13 This is a schematic diagram of a visual interface management terminal provided in an embodiment of this application. For example... Figure 13 As shown, the visual interface management terminal 13 of this embodiment includes: a processor 130, a memory 131, and a computer program 132 stored in the memory 131 and executable on the processor 130. When the processor 130 executes the computer program 132, it implements the steps of each of the above-described embodiments of the visual interface management method, for example... Figure 1 Steps 102 to 108 are shown. Alternatively, when the processor 130 executes the computer program 132, it implements the functions of each module / unit in the above-described device embodiments.

[0106] For example, the computer program 132 may be divided into one or more modules / units, which are stored in the memory 131 and executed by the processor 130 to complete this application. The one or more modules / units may be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of the computer program 132 in the visual interface management terminal 13.

[0107] The aforementioned visual interface management terminal 13 can be a desktop computer, laptop, handheld computer, or cloud server, etc. The device / terminal may include, but is not limited to, a processor 130 and a memory 131. Those skilled in the art will understand that... Figure 13 This is merely an example of the visual interface management terminal 13 and does not constitute a limitation on the visual interface management terminal 13. It may include more or fewer components than shown, or combine certain components, or use different components.

[0108] The processor 130 may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0109] The memory 131 can be an internal storage unit of the visualization interface management terminal 13, for example, a hard disk or a memory of the visualization interface management terminal 13. The memory 131 can also be an external storage device of the visualization interface management terminal 13, for example, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the device / terminal 13. Further, the memory 131 can also include both the internal storage unit and the external storage device of the visualization interface management terminal 13. The memory 131 is used to store the computer program and other programs and data required by the visualization interface management terminal 13. The memory 131 can also be used to temporarily store data that has been output or will be output.

[0110] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above functional units and modules is exemplified, and in actual application, the above functions can be completed by different functional units and modules according to needs, that is, the internal structure of the device is divided into different functional units or modules to complete all or part of the functions described above. Each functional unit and module in the embodiment can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of software functional unit. In addition, the specific names of each functional unit and module are only for easy distinction, and do not limit the protection scope of the present application. The specific working process of the units and modules in the above system can refer to the corresponding process in the foregoing method embodiments, which will not be described here.

[0111] In the above embodiments, the description of each embodiment has its own emphasis, and the parts not described or recorded in detail in a certain embodiment can refer to the relevant description of other embodiments.

[0112] Those of ordinary skill in the art can appreciate that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0113] In the embodiments of the present application, it should be understood that the disclosed apparatus / terminal device and method can be implemented in other manners. For example, the described apparatus / terminal device embodiments are merely schematic. For example, the division of the modules or units is merely logical function division. There can be another division manner for actual implementation. For example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections between different units, can be indirect couplings or communication connections through some interfaces, devices or units.

[0114] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, i.e., can be located in one place, or can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiments.

[0115] In addition, each functional unit in the various embodiments of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0116] The integrated module / unit, if realized in the form of a software functional unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, all or part of the flow of the above-mentioned embodiment methods can be completed by a computer program instructing related hardware, and the computer program can be stored in a computer readable storage medium. The computer program can implement the steps of each method embodiment when executed by a processor. The computer program includes computer program code, which can be in the form of source code, object code, executable file or some intermediate form. The computer readable medium can include any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the computer readable medium can include appropriate contents according to the requirements of legislation and patent practice in the jurisdiction, for example, in some jurisdictions, according to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.

[0117] The above-described embodiments are only used to illustrate the technical solutions of the present application, but not limit the present application; although the present application is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: it can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacement for part of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application.

Claims

1. A method of visual interface management, characterized by, The method comprises the following steps: configuring an interface and generating a parameter model corresponding to the interface; generating a node model corresponding to the interface on an interactive visualization interface according to the parameter model, the node model comprising a front-end model, a database model and a back-end model; wherein a first node graph and a second node graph are arranged on the interactive visualization interface based on the parameter model, the first node graph corresponding to the front-end model and comprising a first sub-node, the second node graph corresponding to the back-end model and comprising a second sub-node, and a database editing statement corresponding to the database model is generated on the interactive visualization interface according to a preset database structure template; configuring configuration information corresponding to the node model, the configuration information comprising: configuring the first sub-node according to a front-end request parameter of the interface, configuring the second sub-node according to a back-end return parameter of the interface, and calling the front-end request parameter and data information of the interface to fill into a database editing statement of a corresponding database table; generating a database according to a return result of the database editing statement and obtaining the back-end return parameter; generating front-end source code and back-end source code according to the node model and the configuration information.

2. The method of claim 1, wherein, The arrangement of the first node graph and the second node graph on the interactive visualization interface based on the parameter model comprises: dragging a sub-node on the interactive visualization interface to add, delete or modify the sub-node, thereby generating the corresponding node graph.

3. The method of claim 1, wherein, The configuration of the interface comprises: filling in basic information of the interface, the basic information comprising an interface function description and an interface link address; classifying the interface according to the basic information of the interface.

4. The method of claim 3, wherein, After the front-end source code and the back-end source code are generated according to the node model and the configuration information, the method further comprises: testing a data flow of the interface according to the front-end source code and the back-end source code, and dynamically marking an exception of the data flow through a visualization interface.

5. The method of claim 4, wherein, After the data flow of the interface is tested according to the front-end source code and the back-end source code, and the exception of the data flow is dynamically marked through the visualization interface, the method further comprises: when the data flow of the interface has no exception, exporting the front-end source code and the back-end source code and deploying them as a business interface.

6. A visual interface management system characterized by, The method comprises the following steps: an interface configuration module configured to configure an interface and generate a parameter model corresponding to the interface; a node model generation module configured to generate a node model corresponding to the interface on an interactive visualization interface according to the parameter model, the node model comprising a front-end model, a database model and a back-end model; wherein the node model generation module is further configured to arrange a first node graph and a second node graph on the interactive visualization interface based on the parameter model, the first node graph corresponding to the front-end model, the second node graph corresponding to the back-end model, and generate a database editing statement corresponding to the database model on the interactive visualization interface according to a preset database structure template; A node model configuration module is configured to configure configuration information corresponding to the node model, the configuration information including front-end request parameters corresponding to the front-end model, data information corresponding to the database model, and back-end return parameters corresponding to the back-end model; wherein the node model configuration module is further configured to configure a first sub-node in the first node graph according to the front-end request parameters of the interface, configure a second sub-node in the second node graph according to the back-end return parameters of the interface, and call a database editing statement in which the front-end request parameters and the data information are filled into a corresponding database table; A database execution module is configured to generate a database according to a return result of the database editing statement, and obtain the back-end return parameters; A code generation module is configured to generate front-end source code and back-end source code according to the node model and the configuration information.

7. A visual interface management terminal comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, The processor executes the computer program to implement the steps of the method of any one of claims 1 to 5.

8. A computer-readable storage medium storing a computer program, the computer program comprising instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 7. The computer program is executed by the processor to implement the steps of the method of any one of claims 1 to 5.

Images