Application management method and device, electronic equipment and readable medium

Abstract

This disclosure provides a method, apparatus, electronic device, and readable medium for managing applications. The application management method includes: determining whether a user's access permission is a first-class or second-class access permission based on login information; displaying relevant application information to the user's front-end interface based on the access permission type; and developing the application or providing corresponding API interfaces based on user requests on the front-end interface. Through these embodiments, the security, reliability, management efficiency, and development efficiency of applications are improved.

Description

Technical Field

[0001] This disclosure relates to the field of software technology, and more particularly, to a method, apparatus, electronic device, and readable medium for managing applications. Background Technology

[0002] Currently, service providers open up their service capabilities to the outside world by opening up online APIs (Application Programming Interfaces). The open APIs provided by large service platforms are characterized by their large number, fine granularity, and wide coverage.

[0003] In related technologies, development tasks can be broken down online, the process can be divided into multiple stages, and the development process can be monitored and the task status updated online.

[0004] However, existing API management solutions have at least the following technical shortcomings:

[0005] (1) During the API development process, the lack of quality management of the results of each development stage may lead to a backtracking of the process due to the failure to discover defects.

[0006] (2) Once the user's identity is verified by the gateway, they can develop or call the API, which may pose a security risk to the API.

[0007] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0008] The purpose of this disclosure is to provide an application management method, apparatus, electronic device, and readable medium to overcome, at least to some extent, the problem of low API development efficiency caused by limitations and defects in related technologies.

[0009] According to a first aspect of the present disclosure, an application management method is provided, comprising: determining, based on login information, whether a user terminal's access permission is a first type of access permission or a second type of access permission; displaying relevant application information to a front-end interface of the user terminal according to the type of access permission; and developing the application or providing corresponding API interfaces based on a request from the user terminal on the front-end interface.

[0010] In one exemplary embodiment of this disclosure, displaying relevant application information to the front-end interface of the user terminal according to the type of access permission includes: if the access permission is determined to be the first type of access permission, receiving a requirement document uploaded by the user terminal; determining development-related information in the application according to the requirement document, wherein the development-related information includes at least one of URL, action, interface request parameters, and interface response parameters; generating API information in JSON format according to the development-related information; and displaying the API information on the front-end interface.

[0011] In one exemplary embodiment of this disclosure, displaying relevant application information to the front-end interface of the user terminal according to the type of access permission further includes: if the access permission is determined to be the second type of access permission, then displaying the online interfaces accessible to the user terminal on the front-end interface.

[0012] In one exemplary embodiment of this disclosure, developing the application or providing feedback on the corresponding API interface based on a request from the user terminal on the front-end interface includes: if the access permission is determined to be the second type of access permission, receiving configuration item information for the online interface sent by the user terminal; determining the interface service of the online interface requested by the user terminal on the front-end interface; and feeding back the interface service to the user terminal through an API gateway.

[0013] In one exemplary embodiment of this disclosure, the process of developing the application or providing corresponding API interfaces based on a request from the user terminal on the front-end interface further includes: if the access permission is determined to be the first type of access permission, generating a Swagger file based on the API information and setting the application to a state of pending development; developing the application in the state of pending development based on the Swagger file; and generating an interface call instruction template for the application after the development of the application is completed.

[0014] In one exemplary embodiment of this disclosure, the API interface for developing or providing feedback on the application based on a request from the user terminal on the front-end interface further includes: receiving an adjustment instruction from a user with the first type of access permission to call an instruction template through the interface to adjust the application; adjusting the application according to the adjustment instruction and performing testing on the adjusted application; if the application passes the testing, the application is determined to be in an online state; if the application fails the testing, the application is determined to be in a pending confirmation state.

[0015] In one exemplary embodiment of this disclosure, developing the application or providing feedback on the corresponding API interface based on a request from the user terminal on the front-end interface further includes: comparing whether the response message format in the JSON-formatted API information is consistent with the message structure fed back by the API interface; if it is determined that the response message format in the JSON-formatted API information is consistent with the message structure fed back by the API interface, then the status of the API interface is determined to be a test state; if it is determined that the response message format in the JSON-formatted API information is inconsistent with the message structure fed back by the API interface, then the status of the API interface is determined to be a confirmation state.

[0016] According to a second aspect of the present disclosure, an application management device is provided, comprising: a determining module configured to determine, based on login information, whether a user's access permission is a first type of access permission or a second type of access permission; a display module configured to display relevant application information to a front-end interface of the user based on the type of access permission; and a management module configured to develop the application or provide corresponding API interfaces based on a request from the user on the front-end interface.

[0017] According to a third aspect of this disclosure, an electronic device is provided, comprising: a memory; and a processor coupled to the memory, the processor being configured to perform the method as described in any of the preceding methods based on instructions stored in the memory.

[0018] According to a fourth aspect of this disclosure, a computer-readable storage medium is provided having a program stored thereon that, when executed by a processor, implements the management method of the application program as described in any of the preceding claims.

[0019] In this embodiment of the disclosure, by determining whether the user's access permission is a first type of access permission or a second type of access permission based on the login information, and displaying relevant application information to the front-end interface of the user based on the type of access permission, and by developing the application or providing corresponding API interfaces based on the user's request on the front-end interface, the development and testing speed of the API is improved, effectively enhancing the development efficiency of the API. Furthermore, by judging the user's access permission, the security and reliability of the API are also enhanced.

[0020] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0021] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0022] Figure 1 This is a flowchart of an application management method according to an exemplary embodiment of this disclosure;

[0023] Figure 2 This is a flowchart of another application management method in an exemplary embodiment of this disclosure;

[0024] Figure 3 This is a flowchart of another application management method in an exemplary embodiment of this disclosure;

[0025] Figure 4 This is a flowchart of another application management method in an exemplary embodiment of this disclosure;

[0026] Figure 5 This is a flowchart of another application management method in an exemplary embodiment of this disclosure;

[0027] Figure 6 This is a flowchart of another application management method in an exemplary embodiment of this disclosure;

[0028] Figure 7 This is a flowchart of another application management method in an exemplary embodiment of this disclosure;

[0029] Figure 8 This is a flowchart of another application management method in an exemplary embodiment of this disclosure;

[0030] Figure 9 This is a block diagram of another application management architecture in an exemplary embodiment of this disclosure;

[0031] Figure 10 This is a block diagram of an application management device according to an exemplary embodiment of the present disclosure;

[0032] Figure 11 This is a block diagram of an electronic device according to an exemplary embodiment of the present disclosure. Detailed Implementation

[0033] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided to make this disclosure more comprehensive and complete, and to fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a full understanding of embodiments of this disclosure. However, those skilled in the art will recognize that the technical solutions of this disclosure can be practiced with one or more of the specific details omitted, or other methods, components, apparatus, steps, etc., can be employed. In other instances, well-known technical solutions are not shown or described in detail to avoid obscuring various aspects of this disclosure.

[0034] Furthermore, the accompanying drawings are merely illustrative of this disclosure, and the same reference numerals in the drawings denote the same or similar parts, thus repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0035] The exemplary embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0036] Figure 1 This is a flowchart of an application management method in an exemplary embodiment of this disclosure.

[0037] refer to Figure 1 Application management methods may include:

[0038] Step S102: Determine whether the user's access permissions are Class 1 or Class 2 based on the login information.

[0039] Step S104: Display the relevant information of the corresponding application to the front-end interface of the user terminal according to the type of access permission.

[0040] Step S106: Develop the application or provide corresponding API interfaces based on the user's request on the front-end interface.

[0041] In this embodiment of the disclosure, by determining whether the user's access permission is a first type of access permission or a second type of access permission based on the login information, and displaying relevant application information to the front-end interface of the user based on the type of access permission, and by developing the application or providing corresponding API interfaces based on the user's request on the front-end interface, the development and testing speed of the API is improved, effectively enhancing the development efficiency of the API. Furthermore, by judging the user's access permission, the security and reliability of the API are also enhanced.

[0042] In one exemplary embodiment of this disclosure, the application is an open API, which is a common application of service-oriented websites.

[0043] In one exemplary embodiment of this disclosure, a service provider encapsulates its services into a series of application programming interfaces (APIs) and makes them available to third parties. These open APIs are referred to as open APIs. Through the embodiments of this disclosure, developers of different open APIs can clearly define their responsibilities and obtain real-time development progress, while ordinary users can call the APIs that have been launched through the interface.

[0044] In one exemplary embodiment of this disclosure, the API information obtained from parsing the requirements document can be displayed on the front-end interface, providing convenient reference content for the development process. After development is completed, interface call instruction templates can be generated for each API, facilitating interface testing, and interface responses can be compared with a single click. APIs that pass interface testing are visible to ordinary users in a specific role group and can be called by these users.

[0045] Furthermore, this disclosure applies to open API development projects of all sizes within enterprises, and its role is particularly evident when the project development process involves a large number of APIs, many participants, high requirements for collaborative cooperation, and a wide user base.

[0046] The following is combined Figures 2 to 9 This section provides a detailed explanation of each step in the application management process.

[0047] In one exemplary embodiment of this disclosure, such as Figure 2 As shown, displaying relevant application information to the user's front-end interface based on the type of access permission includes:

[0048] Step S202: If it is determined that the access permission is the first type of access permission, then the requirement document uploaded by the user terminal is received.

[0049] In one exemplary embodiment of this disclosure, the first type of access permission is predefined as the permission of the developer or tester.

[0050] Step S204: Determine the development-related information in the application based on the requirements document. The development-related information includes at least one of URL, action, interface request parameters, and interface response parameters.

[0051] In one exemplary embodiment of this disclosure, the requirements document is in Excel format.

[0052] Step S206: Generate API information in JSON format based on the development-related information.

[0053] Step S208: Display the API information on the front-end interface.

[0054] In one exemplary embodiment of this disclosure, such as Figure 3 As shown, displaying relevant application information to the user's front-end interface based on the type of access permission also includes:

[0055] Step S302: If the access permission is determined to be the second type of access permission, then the online interfaces accessible to the user terminal are displayed on the front-end interface.

[0056] In one exemplary embodiment of this disclosure, the second type of access permission is the permission of a regular user.

[0057] In one exemplary embodiment of this disclosure, such as Figure 4 As shown, the API interfaces for developing or responding to requests from the user on the front-end interface include:

[0058] Step S402: If it is determined that the access permission is the second type of access permission, then the configuration item information for the online interface sent by the user terminal is received.

[0059] In one exemplary embodiment of this disclosure, the application's configuration item information includes, but is not limited to, URLs (Uniform Resource Locators) and Tokens (sockets).

[0060] Step S404: Determine the interface service of the online interface that the user terminal requests to call on the front-end interface.

[0061] Step S406: Feed back the interface service to the user terminal through the API gateway.

[0062] In one exemplary embodiment of this disclosure, such as Figure 5 As shown, the API interfaces for developing or responding to requests from the user terminal on the front-end interface also include:

[0063] Step S502: If the access permission is determined to be the first type of access permission, then a Swagger file is generated based on the API information, and the application is set to the pending development state.

[0064] In one exemplary embodiment of this disclosure, a series of projects and tools derived from Swagger can generate interface documents in various formats, client and server code in multiple languages, and online interface debugging pages, etc. Thus, following the new development model, when developing new or iterative versions, only the Swagger description file needs to be updated to automatically generate interface documents and client / server code, ensuring consistency between the caller code, server code, and interface documents.

[0065] Step S504: Develop the application in the development state according to the Swagger file.

[0066] Step S506: After the development of the application is completed, an interface call instruction template for the application is generated.

[0067] In one exemplary embodiment of this disclosure, such as Figure 6 As shown, the API interfaces for developing or responding to requests from the user terminal on the front-end interface also include:

[0068] Step S602: Receive adjustment instructions for the application from a user with the first type of access permission via the interface calling the instruction template.

[0069] Step S604: Adjust the application according to the adjustment instruction, and test the adjusted application.

[0070] Step S606: If the application passes the test, the application's status is determined to be online.

[0071] Step S608: If the application fails the test process, the application's status is determined to be pending confirmation.

[0072] In one exemplary embodiment of this disclosure, such as Figure 7 As shown, the API interfaces for developing or responding to requests from the user terminal on the front-end interface also include:

[0073] Step S702: Compare whether the response message format in the JSON format API information is consistent with the message structure fed back by the API interface.

[0074] In one exemplary embodiment of this disclosure, the development of an API is determined to be consistent with expectations by comparing the response message format in the JSON-formatted API information with the message structure fed back by the API interface. If they are consistent, the API interface is tested further; otherwise, the developers are prompted to verify, thereby improving the efficiency and reliability of API development.

[0075] Step S704: If it is determined that the response message format in the JSON format API information is consistent with the message structure fed back by the API interface, then the status of the API interface is determined to be a test state.

[0076] Step S706: If it is determined that the response message format in the JSON format API information is inconsistent with the message structure fed back by the API interface, then the status of the API interface is determined to be pending confirmation.

[0077] In one exemplary embodiment of this disclosure, such as Figure 8 As shown, the application management scheme includes the following steps:

[0078] Step S802: User login.

[0079] Step S804: Determine whether the user is an internal developer based on the login information. If yes, proceed to step S806; otherwise, proceed to step S824.

[0080] Upon login, users are categorized into two main groups based on their role: "internal developers" and "regular users," with different content and functions displayed on the front-end interface.

[0081] Step S806: Receive the requirement document uploaded by the user.

[0082] Requirements personnel upload a requirements document in Excel format to the system page, and the system backend automatically parses the document. The requirements document describes the API information, from which the system extracts basic information such as the API URL, actions, API request parameters, and API response parameters.

[0083] Step S808: Generate JSON format interface information based on the requirements document.

[0084] Create key-value pairs for each piece of basic information, integrate these key-value pairs to generate API information in JSON format, and display it on the front-end interface.

[0085] Step S810: Generate a Swagger file for API self-testing.

[0086] The system generates a Swagger file based on this API information. Additionally, the system supports real-time adjustments and updates to the API information via the interface. At this point, the API is in a "pending development" state.

[0087] Step S812: Develop and implement the API.

[0088] After the code is developed, the system generates an interface call instruction template on the interface based on the API information. Developers can fine-tune the call instruction template when necessary and perform self-testing of the API. The system can compare the response message format in the JSON format API information with one click. When the actual message structure returned by the interface matches the template, the interface is marked as "to be tested"; otherwise, it is marked as "to be confirmed".

[0089] Step S814: Configure project information.

[0090] Step S816: Generate the interface test command template and debug it.

[0091] Testers use API call instruction templates to perform interface tests on APIs in the "Pending Test" state, and mark APIs that pass the test as "Live". Otherwise, they mark them as "Pending Confirmation" and submit them to the developers for confirmation.

[0092] Step S818: Determine whether the actual interface response message meets expectations. If yes, proceed to step S820; otherwise, proceed to step S812.

[0093] Step S820: Determine whether the API has passed the interface test. If yes, proceed to step S822; otherwise, proceed to step S812.

[0094] Step S822: Interface goes online.

[0095] Step S824: Grant API permissions based on the user's group.

[0096] Step S826 displays the online interface services that you have permission to access.

[0097] Step S828: Configure project information.

[0098] Step S830: The user calls the interface service.

[0099] Regular users can view and access the APIs they have permission to use through the interface.

[0100] Step S832: The API gateway parses the interface service.

[0101] Step S834: Call the actual API.

[0102] Step S836: Display the API call.

[0103] Figure 9 This is a block diagram of an application management architecture according to an exemplary embodiment of this disclosure.

[0104] refer to Figure 9 The application's management architecture can include: requirements document parsing (module 902), user permission analysis (module 904), API status update (module 906), and API testing (module 908). The specific development and implementation process mainly includes:

[0105] User permission analysis (module) 904 restricts the scope of access that an account can access based on the role group to which the currently logged-in account belongs.

[0106] Developers can see the interfaces they are responsible for developing and their status on the interface, while ordinary users can only access the online interfaces and Swagger documentation that their role group has permission to access, and call the actual API interfaces through the API gateway.

[0107] The Requirements Document Parsing (Module 902) extracts the API URL, actions, interface request parameters, and interface response parameters from the Excel-formatted requirements document, creating key-value pairs one by one with the corresponding column names as keys. Then, these key-value pairs are integrated to generate API information in JSON format, which is displayed on the front-end interface for developers to reference.

[0108] Based on this API information, a Swagger file is generated, and both types of objects mentioned above are stored in the database. Additionally, this system supports real-time adjustment and updating of API information via the interface. At this point, the API is in a "pending development" state.

[0109] The API Status Update (module) 906 is responsible for updating the API status and displaying the current status on the interface. API status includes "Pending Development", "Pending Confirmation", "Pending Testing" and "Live". After publishing the interface information, relevant developers can be assigned to the interface, at which point the API status is marked as "Pending Development".

[0110] During the developer self-testing phase, when the API's response structure matches the response structure in the JSON format interface information, the interface status is marked as "Pending Test"; otherwise, it is marked as "Pending Confirmation." Interfaces in the "Pending Confirmation" status require developers to confirm the accuracy of the relevant information; "Pending Test" indicates that testers are waiting to test the API, including input parameter testing, functional testing, and logic testing.

[0111] API Testing (Module) 908 generates a corresponding cURL command template for each API based on JSON-formatted API information and displays it on the front-end page. Developers and ordinary users only need to make minor adjustments and additions to the template according to actual parameters and other factors to test the API on the interface.

[0112] When a user logs in, the system automatically retrieves the token corresponding to the current user and fills it into the cURL command template. This token needs to be passed when calling the API through the API gateway. The API response message is displayed on the front-end page, and users can easily compare the actual response message with the response structure of the API information in JSON format. When a user uploads a file containing multiple test cases, this module determines whether the API response message structure is consistent with the response structure in a certain test case and updates the interface status accordingly.

[0113] Corresponding to the above method embodiments, this disclosure also provides an application management device that can be used to execute the above method embodiments.

[0114] Figure 10 This is a block diagram of an application management device according to an exemplary embodiment of the present disclosure.

[0115] refer to Figure 10 The application management device 1000 may include:

[0116] The module 1002 is configured to determine whether the user's access permissions are classified as either Category 1 or Category 2 based on the login information.

[0117] Display module 1004 is configured to display relevant application information to the front-end interface of the user terminal according to the type of access permission.

[0118] The management module 1006 is configured to develop the application or provide corresponding API interfaces based on the user's request on the front-end interface.

[0119] In an exemplary embodiment of this disclosure, the display module 1004 is further configured to: if the access permission is determined to be the first type of access permission, receive the requirement document uploaded by the user terminal; determine the development-related information in the application based on the requirement document, wherein the development-related information includes at least one of URL, action, interface request parameters and interface response parameters; generate API information in JSON format based on the development-related information; and display the API information on the front-end interface.

[0120] In one exemplary embodiment of this disclosure, the display module 1004 is further configured to: if it is determined that the access permission is the second type of access permission, then display the online interfaces accessible to the user terminal on the front-end interface.

[0121] In one exemplary embodiment of this disclosure, the management module 1006 is further configured to: if the access permission is determined to be the second type of access permission, receive configuration item information for the online interface sent by the user terminal; determine the interface service of the online interface requested by the user terminal on the front-end interface; and feed back the interface service to the user terminal through the API gateway.

[0122] In one exemplary embodiment of this disclosure, the management module 1006 is further configured to: if the access permission is determined to be the first type of access permission, generate a Swagger file based on the API information and set the application to a state to be developed; develop the application in the state to be developed based on the Swagger file; and after the development of the application is completed, generate an interface call instruction template for the application.

[0123] In an exemplary embodiment of this disclosure, the management module 1006 is further configured to: receive an adjustment instruction from a user with the first type of access permission to call the instruction template through the interface to adjust the application; adjust the application according to the adjustment instruction, and perform test processing on the adjusted application; if the application passes the test processing, determine the status of the application as online; if the application fails the test processing, determine the status of the application as pending confirmation.

[0124] In an exemplary embodiment of this disclosure, the management module 1006 is further configured to: compare whether the response message format in the JSON-formatted API information is consistent with the message structure fed back by the API interface; if it is determined that the response message format in the JSON-formatted API information is consistent with the message structure fed back by the API interface, then the status of the API interface is determined to be a test state; if it is determined that the response message format in the JSON-formatted API information is inconsistent with the message structure fed back by the API interface, then the status of the API interface is determined to be a confirmation state.

[0125] Since the functions of the application management device 1000 have been described in detail in their respective method embodiments, they will not be repeated here.

[0126] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0127] In an exemplary embodiment of this disclosure, an electronic device capable of implementing the above-described method is also provided.

[0128] Those skilled in the art will understand that various aspects of the present invention can be implemented as systems, methods, or program products. Therefore, various aspects of the present invention can be specifically implemented in the following forms: entirely hardware implementations, entirely software implementations (including firmware, microcode, etc.), or implementations combining hardware and software aspects, collectively referred to herein as “circuits,” “modules,” or “systems.”

[0129] The following reference Figure 11 To describe an electronic device 1100 according to this embodiment of the present invention. Figure 11 The electronic device 1100 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0130] like Figure 11 As shown, the electronic device 1100 is manifested in the form of a general-purpose computing device. The components of the electronic device 1100 may include, but are not limited to: at least one processing unit 1110, at least one storage unit 1120, and a bus 1130 connecting different system components (including storage unit 1120 and processing unit 1110).

[0131] The storage unit stores program code that can be executed by the processing unit 1110, causing the processing unit 1110 to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of the present invention. For example, the processing unit 1110 can perform the method shown in the embodiments of this disclosure.

[0132] Storage unit 1120 may include a readable medium in the form of a volatile storage unit, such as random access memory (RAM) 11201 and / or cache memory 11202, and may further include a read-only memory (ROM) 11203.

[0133] Storage unit 1120 may also include a program / utility 11204 having a set (at least one) of program modules 11205, such program modules 11205 including but not limited to: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.

[0134] Bus 1130 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0135] Electronic device 1100 can also communicate with one or more external devices 1140 (e.g., keyboard, pointing device, Bluetooth device, etc.), one or more devices that enable user terminals to interact with electronic device 1100, and / or any device that enables electronic device 1100 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 1150. Furthermore, electronic device 1100 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 1160. As shown, network adapter 1160 communicates with other modules of electronic device 1100 via bus 1130. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 1100, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0136] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0137] In exemplary embodiments of this disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the methods described above is stored. In some possible embodiments, various aspects of the invention may also be implemented as a program product comprising program code that, when the program product is run on a terminal device, causes the terminal device to perform the steps of the various exemplary embodiments of the invention described in the "Exemplary Methods" section of this specification.

[0138] The program product for implementing the above-described method according to embodiments of the present invention may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto. In this document, the readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0139] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0140] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0141] The program code contained on the readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0142] Program code for performing the operations of this invention can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user-end computing device, partially on the user-end computing device, as a standalone software package, partially on the user-end computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user-end computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0143] Furthermore, the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of the present invention, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Additionally, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0144] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and concept of this disclosure are indicated by the claims.

Claims

1. A management method of an application program, characterized by, The application comprises the following steps: According to the login information, the access permission of the user terminal is determined to be the first type of access permission or the second type of access permission, the first type of access permission is predetermined as the permission of a developer or a tester, and the second type of access permission is the permission of a general user; According to the type of the access permission, the relevant information of the corresponding application program is displayed on the front-end interface of the user terminal, including: If it is determined that the access permission is the first type of access permission, the requirement document uploaded by the user terminal is received; According to the requirement document, the development-related information in the application program is determined, the development-related information including at least one of URL, action, interface request parameter and interface response parameter; According to the development-related information, the API information in JSON format is generated; The API information is displayed on the front-end interface; According to the request of the user terminal on the front-end interface, the development of the application program or the feedback of the corresponding API interface is carried out, including: If it is determined that the access permission is the second type of access permission, the configuration item information of the online interface sent by the user terminal is received; The interface service of the online interface requested and called by the user terminal on the front-end interface is determined; The interface service is fed back to the user terminal through the API gateway; If it is determined that the access permission is the first type of access permission, the Swagger file is generated according to the API information, and the application program is set to a to-be-developed state; According to the Swagger file, the application program in the to-be-developed state is developed; After the development of the application program is completed, the interface calling instruction template of the application program is generated.

2. The management method of an application program according to Claim 1, wherein According to the type of the access permission, the relevant information of the corresponding application program is displayed on the front-end interface of the user terminal, further including: If it is determined that the access permission is the second type of access permission, the online interface accessible by the user terminal is displayed on the front-end interface.

3. The management method of an application program according to Claim 1, wherein According to the request of the user terminal on the front-end interface, the development of the application program or the feedback of the corresponding API interface further includes: The adjustment instruction of the application program by the user with the first type of access permission through the interface calling instruction template is received; According to the adjustment instruction, the application program is adjusted, and the adjusted application program is tested and processed; If the application program passes the test processing, the state of the application program is determined to be an online state; If the application program does not pass the test processing, the state of the application program is determined to be a to-be-confirmed state.

4. The management method of an application program according to Claim 1, wherein According to the request of the user terminal on the front-end interface, the development of the application program or the feedback of the corresponding API interface further includes: The response message format in the API information in JSON format is compared with the message structure fed back by the API interface; If it is determined that the response message format in the API information in JSON format is consistent with the message structure fed back by the API interface, the state of the API interface is determined to be a to-be-tested state; If it is determined that the response message format in the JSON format API information is inconsistent with the message structure fed back by the API interface, the state of the API interface is determined as a to-be-confirmed state.

5. An application management apparatus characterized by comprising: The application comprises: A determination module is configured to determine the access right of a user terminal as a first type of access right or a second type of access right according to login information, the first type of access right being the right of a developer or a tester, and the second type of access right being the right of an ordinary user. A display module is configured to display relevant information of a corresponding application program on a front-end interface of the user terminal according to the type of the access right, comprising: If it is determined that the access right is the first type of access right, a requirement document uploaded by the user terminal is received; Development-related information in the application program is determined according to the requirement document, the development-related information comprising at least one of a URL, an action, an interface request parameter and an interface response parameter; JSON format API information is generated according to the development-related information; The API information is displayed on the front-end interface; A management module is configured to develop the application program or feed back a corresponding API interface according to a request of the user terminal on the front-end interface, comprising: If it is determined that the access right is the second type of access right, configuration item information of an online interface sent by the user terminal is received; An interface service of the online interface requested and called by the user terminal on the front-end interface is determined; The interface service is fed back to the user terminal through an API gateway; If it is determined that the access right is the first type of access right, a Swagger file is generated according to the API information, and the application program is set as a to-be-developed state; The application program in the to-be-developed state is developed according to the Swagger file; After the development of the application program is completed, an interface calling instruction template of the application program is generated.

6. An electronic device, comprising: The application comprises: A memory; And A processor coupled to the memory, the processor being configured to execute a management method of an application program as claimed in any one of claims 1-4 based on instructions stored in the memory.

7. A computer readable storage medium having stored thereon a program which, when executed by a processor, implements a management method of an application program as claimed in any one of claims 1-4.

Images