Interface statistical method and device, equipment, storage medium and program product

Abstract

The invention relates to an interface statistical method and device, equipment, a storage medium and a program product. The method comprises the following steps: acquiring software development process information and design mode information of a software product; the software development process information is used for indicating a business development process of the software product; obtaining a plurality of software interfaces of the software product and development information of each software interface according to the software development process information and the design mode information; the development information of the software interface comprises at least one of an identifier of a development main body for developing the software interface and a service type corresponding to the software interface; dividing each software interface according to the development information to obtain a plurality of software interface lists; by adopting the method, the accuracy and efficiency of software interface statistics can be improved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to an interface statistics method, device, equipment, storage medium and program product. Background Art

[0002] In the software development and design process, after the service activation process of the software product is designed, the designed process will be packaged into a design package and sent to the implementation system for development and implementation. Software interfaces such as API (Application Programming Interface) in the service activation process are developed, tested and debugged by different business areas. Therefore, it is necessary to count the software interfaces in the service activation process involved in each business area for development by each business area.

[0003] In the related technology, designers manually count software interfaces, which often leads to problems such as inaccurate data and long time consumption. Summary of the invention

[0004] Based on this, it is necessary to provide an interface statistics method, device, equipment, storage medium and program product that can improve the accuracy and efficiency of software interface statistics in response to the above technical problems.

[0005] In a first aspect, the present application provides an interface statistics method. The method comprises:

[0006] Acquire software development process information and design pattern information of a software product; the software development process information is used to indicate the business development process of the software product; obtain multiple software interfaces of the software product and development information of each software interface based on the software development process information and the design pattern information; the development information of the software interface includes an identifier of a development entity that develops the software interface and at least one of a business type corresponding to the software interface; divide the software interfaces according to the development information to obtain multiple software interface lists.

[0007] In one of the embodiments, based on the software development process information and the design pattern information, multiple software interfaces of the software product and development information of each software interface are obtained, including: parsing the software development process information to obtain one or more product layer interface development process information and development information of each product layer interface development process information; the development information of the product layer interface development process information includes the identification and business type of the development entity corresponding to the product layer interface development process information; based on the development information of each product layer interface development process information, target product layer development process information is determined from each product layer interface development process information; the target product layer interface development process information is one or more; based on the design pattern information, the target product layer development process information is layered and disassembled to obtain multiple software interfaces and development information of each software interface.

[0008] In one of the embodiments, the design pattern information is used to indicate that the design pattern of the software product is a design pattern based on the PSR model; the software interface includes at least one of the following: a product layer software interface; a CFS layer software interface; an RFS layer software interface; and a RES layer software interface.

[0009] In one of the embodiments, the target product layer development process information is determined from the development process information of each product layer interface according to the development information of each product layer interface, including: using the identifier of the corresponding development subject including the target subject identifier and the product layer interface development process information of the corresponding business type being the target business type as the target product layer interface development process information; wherein the development subject corresponding to the target subject identifier is the development subject that currently has a business activation plan; and the target business type is the business type of the current plan.

[0010] In one of the embodiments, the target product layer development process information is decomposed in layers according to the design pattern information to obtain multiple software interfaces and development information of each software interface, including: parsing the target product layer development process information according to a PSR model to obtain one or more CFS layer interface development process information and development information of the CFS layer interface development process information, and obtaining one or more product layer software interfaces and development information of the product layer software interface; determining the target CFS layer interface development process information from each CFS layer interface development process information according to the development information of each CFS layer interface development process information; the target CFS layer interface development process information is one or more; decomposing the target CFS layer interface development process information according to the design pattern information to obtain multiple software interfaces and development information of each software interface.

[0011] In one of the embodiments, the target CFS layer interface development process information is disassembled according to the design pattern information to obtain multiple software interfaces and development information of each software interface, including: parsing the target CFS layer interface development process information according to the PSR model to obtain one or more RFS layer interface development process information and development information of the RFS layer interface development process information, and obtaining one or more CFS layer software interfaces and development information of the CFS layer software interface; determining the target RFS layer interface development process information from each RFS layer interface development process information according to the development information of each RFS layer interface development process information; the target RFS layer interface development process information is one or more; disassembling the target RFS layer interface development process information according to the design pattern information to obtain multiple software interfaces and development information of each software interface.

[0012] In one of the embodiments, the target RFS layer interface development process information is disassembled according to the design pattern information to obtain multiple software interfaces and development information of each software interface, including: parsing the target RFS layer interface development process information according to the PSR model to obtain one or more RES layer interface development process information and development information of the RES layer interface development process information, and obtaining one or more RFS layer software interfaces and development information of the RFS layer software interface; determining the target RES layer interface development process information from each RES layer interface development process information according to the development information of each RES layer interface development process information; disassembling the target RES layer interface development process information according to the design pattern information to obtain multiple software interfaces and development information of each software interface.

[0013] In one of the embodiments, the target RES layer interface development process information is disassembled according to the design pattern information to obtain multiple software interfaces and development information of each software interface, including: parsing the target RES layer interface development process information according to the PSR model to obtain one or more RES layer software interfaces and the development information of the RES layer software interface.

[0014] In one of the embodiments, the software interfaces are divided according to the development information to obtain multiple software interface lists, including: performing a first division process on each software interface according to an identifier of a development entity of each software interface to obtain multiple initial software interface lists; wherein different initial software interface lists correspond to identifiers of different development entities, and software interfaces included in the same initial software interface list correspond to the identifier of the same development entity; for each initial software interface list, performing a second division process on each software interface in the initial software interface list according to a business type corresponding to each software interface in the initial software interface list to obtain multiple software interface lists; wherein different software interface lists correspond to different business types, and software interfaces included in the same software interface list correspond to the same business type.

[0015] In one of the embodiments, the development information of the software interface also includes the professional system type to which the software interface belongs; the method also includes: removing duplicate software interfaces in each software interface list to obtain candidate software interface lists without duplicate software interfaces; for each candidate software interface list, performing a third division process on each software interface in the candidate software interface list according to the professional system type to which each software interface belongs to obtain multiple target software interface lists; wherein different target software interface lists correspond to different professional system types.

[0016] In one of the embodiments, the method further includes: visually displaying a list of each target software interface.

[0017] In a second aspect, the present application further provides an interface statistics device, the device comprising:

[0018] An information acquisition module is used to acquire software development process information and design pattern information of a software product; the software development process information is used to indicate the business development process of the software product;

[0019] An interface acquisition module, used to obtain multiple software interfaces of the software product and development information of each software interface according to the software development process information and the design pattern information; the development information of the software interface includes at least one of an identifier of a development entity that develops the software interface and a business type corresponding to the software interface;

[0020] The interface division module is used to divide each software interface according to the development information to obtain multiple software interface lists.

[0021] In one of the embodiments, the interface acquisition module is specifically used to: parse the software development process information to obtain one or more product layer interface development process information and development information of each product layer interface development process information; the development information of the product layer interface development process information includes the identification and business type of the development entity corresponding to the product layer interface development process information; according to the development information of each product layer interface development process information, determine the target product layer development process information from each product layer interface development process information; the target product layer interface development process information is one or more; according to the design pattern information, disassemble the target product layer development process information in layers to obtain multiple software interfaces and development information of each software interface.

[0022] In one of the embodiments, the design pattern information is used to indicate that the design pattern of the software product is a design pattern based on the PSR model; the software interface includes at least one of the following: a product layer software interface; a CFS layer software interface; an RFS layer software interface; and a RES layer software interface.

[0023] In one of the embodiments, the interface acquisition module is specifically used to: use the identification of the corresponding development entity including the target entity identification and the product layer interface development process information of the corresponding business type being the target business type as the target product layer interface development process information; wherein the development entity corresponding to the target entity identification is the development entity that currently has a business activation plan; and the target business type is the business type of the current plan.

[0024] In one of the embodiments, the interface acquisition module is specifically used to: parse the target product layer development process information according to the PSR model to obtain one or more CFS layer interface development process information and development information of the CFS layer interface development process information, and obtain one or more product layer software interfaces and development information of the product layer software interface; determine the target CFS layer interface development process information from each CFS layer interface development process information according to the development information of each CFS layer interface development process information; the target CFS layer interface development process information is one or more; and disassemble the target CFS layer interface development process information according to the design pattern information to obtain multiple software interfaces and development information of each software interface.

[0025] In one of the embodiments, the interface acquisition module is specifically used to: parse the target CFS layer interface development process information according to the PSR model to obtain one or more RFS layer interface development process information and development information of the RFS layer interface development process information, and obtain one or more CFS layer software interfaces and development information of the CFS layer software interface; determine the target RFS layer interface development process information from each RFS layer interface development process information according to the development information of each RFS layer interface development process information; the target RFS layer interface development process information is one or more; and disassemble the target RFS layer interface development process information according to the design pattern information to obtain multiple software interfaces and development information of each software interface.

[0026] In one of the embodiments, the interface acquisition module is specifically used to: parse the target RFS layer interface development process information according to the PSR model to obtain one or more RES layer interface development process information and development information of the RES layer interface development process information, and obtain one or more RFS layer software interfaces and development information of the RFS layer software interface; determine the target RES layer interface development process information from the RES layer interface development process information according to the development information of each RES layer interface development process information; disassemble the target RES layer interface development process information according to the design pattern information to obtain multiple software interfaces and development information of each software interface.

[0027] In one of the embodiments, the interface acquisition module is specifically used to: parse the target RES layer interface development process information according to the PSR model to obtain one or more RES layer software interfaces and the development information of the RES layer software interface.

[0028] In one of the embodiments, the interface division module is specifically used to: perform a first division process on each software interface according to an identifier of a development entity of each software interface to obtain a plurality of initial software interface lists; wherein different initial software interface lists correspond to identifiers of different development entities, and the software interfaces included in the same initial software interface list correspond to the identifier of the same development entity; for each initial software interface list, perform a second division process on each software interface in the initial software interface list according to a business type corresponding to each software interface in the initial software interface list to obtain a plurality of software interface lists; wherein different software interface lists correspond to different business types, and the software interfaces included in the same software interface list correspond to the same business type.

[0029] In one of the embodiments, the development information of the software interface also includes the professional system type to which the software interface belongs; the device also includes a processing module, which is used to: remove duplicate software interfaces in each software interface list to obtain candidate software interface lists without duplicate software interfaces; for each candidate software interface list, perform a third division process on each software interface in the candidate software interface list according to the professional system type to which each software interface belongs to obtain multiple target software interface lists; wherein different target software interface lists correspond to different professional system types.

[0030] In one of the embodiments, the device further includes a display module for visually displaying a list of each target software interface.

[0031] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of any one of the methods described in the first aspect when executing the computer program.

[0032] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any one of the methods described in the first aspect above.

[0033] In a fifth aspect, the present application further provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of any one of the methods described in the first aspect are implemented.

[0034] The above-mentioned interface statistics method, device, equipment, storage medium and program product obtain software development process information and design pattern information of the software product for indicating the business development process of the software product; obtain multiple software interfaces of the software product and development information of each software interface according to the software development process information and design pattern information; the development information of the software interface includes the identification of the development subject of the software interface and at least one of the business types corresponding to the software interface; divide each software interface according to the development information to obtain multiple software interface lists. In this way, the software interfaces involved in the software product can be automatically counted and divided by this method, which is more efficient than manual statistics, and because the software interfaces are counted and further divided based on the software development process information and design pattern information of the software product itself, the accuracy rate is high. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0036] Figure 1 A schematic diagram of a flow chart of an interface statistics method in an embodiment;

[0037] Figure 2 A schematic diagram of a process for obtaining a software interface in one embodiment;

[0038] Figure 3 A schematic diagram of another process of obtaining a software interface in one embodiment;

[0039] Figure 4 A schematic diagram of another process of obtaining a software interface in one embodiment;

[0040] Figure 5 A schematic diagram of another process of obtaining a software interface in one embodiment;

[0041] Figure 6 A schematic diagram of a process for dividing a software interface in one embodiment;

[0042] Figure 7 A flowchart of an API automated statistical method for service provisioning processes based on a PSR mode network topology in one embodiment;

[0043] Figure 8 is a structural block diagram of an interface statistics device in an embodiment;

[0044] Fig. 9 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0045] In order to make the above-mentioned purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are described in detail below in conjunction with the accompanying drawings. It should be understood that many specific details are set forth in the following description to facilitate a full understanding of the present application, but the present application can be implemented in many other ways different from those described herein, and those skilled in the art can make similar improvements without violating the connotation of the present application, so the present application is not limited by the specific embodiments disclosed below.

[0046] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein in the specification of this application are only for the purpose of describing specific embodiments and are not intended to limit this application.

[0047] The terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. In the description of this application, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically limited.

[0048] It can be understood that “at least one” means one or more, “plurality” means two or more, and “at least part of an element” means part or all of an element.

[0049] When used herein, the singular forms "a", "an", and "said / the" may also include plural forms, unless the context clearly indicates otherwise. It should also be understood that the terms "include / comprise" or "have" and the like specify the presence of stated features, wholes, steps, operations, components, parts, or combinations thereof, but do not exclude the possibility of the presence or addition of one or more other features, wholes, steps, operations, components, parts, or combinations thereof. At the same time, the term "and / or" used in this specification includes any and all combinations of the relevant listed items.

[0050] In the process of software development and design, after designing the service activation process of the software product, the designed process will be packaged into a design package and sent to the implementation system for development and implementation. The software interfaces in the service activation process are developed, tested and debugged by different business areas. Therefore, it is necessary to count the software interfaces in the service activation process involved in each business area for development by each business area. In related technologies, the manual counting of software interfaces by designers often leads to problems such as inaccurate data and long time consumption.

[0051] In view of this, an embodiment of the present application provides an interface statistics method, which can improve the accuracy and efficiency of software interface statistics.

[0052] It should be noted that the interface statistics method provided in the embodiment of the present application may be implemented as an interface statistics device, which may be implemented as part or all of an electronic device through software, hardware, or a combination of software and hardware. The electronic device may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, servers, etc. The server may be implemented as an independent server or a server cluster composed of multiple servers. The following is an example of the method being applied to an electronic device.

[0053] In one embodiment, Figure 1 As shown, an interface statistics method is provided, comprising the following steps:

[0054] Step 101, obtaining software development process information and design pattern information of a software product.

[0055] Software products are products launched based on software algorithms, such as software that provides communication services, etc., which are not specifically limited here.

[0056] The software development process information is used to indicate the business development process of the software product. The software development process information indicates the software interface required for developing the software product.

[0057] For example, after the product service design center of the new generation cloud network capability operation system designs the business development process of the product based on the PSR (product / service / resource three-layer model, Product / Service / Resource) model, it will package the design data into a design package and send it to the corresponding implementation system for development and implementation. The API (Application Programming Interface) in the business development process is developed, tested and jointly debugged by the operator group and the orchestration, resource and other implementation systems of each region, that is, the operator group and each region develop their corresponding APIs respectively. The so-called PSR model refers to the layered decoupling of resources (R), services (S) and products (P), and the assembly and design based on the underlying cloud network capabilities to form services, and provide software products such as communication service products to the outside world.

[0058] The PSR model can achieve layered decoupling of the P (Product) layer, S (Service) layer, and R (Resource) layer, improve the reuse rate of PSR, increase the efficiency of PSR design, and reduce design costs. However, under the PSR model design, the service activation and network activation processes at different levels are layered and decoupled, but during implementation, the upper and lower layers are logically related and are developed and implemented by implementation systems in different regions. The business development process of a complete software product involves API calls at the P layer, S layer, and R layer.

[0059] In an embodiment of the present application, the software product may be designed based on a PSR model, for example, and correspondingly, the design pattern information is a design pattern based on a PSR model.

[0060] In this way, by obtaining the software development process information and design pattern information of the software product, the software interfaces involved can be effectively counted from the overall design logic.

[0061] Optionally, the software interface is, for example, the above-mentioned API interface.

[0062] Step 102, obtaining multiple software interfaces of the software product and development information of each software interface according to the software development process information and the design pattern information.

[0063] By analyzing the software development process information based on the design pattern information, multiple software interfaces of the software product and the development information of each software interface can be obtained. The development information is used to divide the software interfaces.

[0064] The development information of the software interface includes at least one of an identifier of a development entity that develops the software interface and a business type corresponding to the software interface.

[0065] From the above description, it can be seen that the software interfaces are jointly developed by the implementation systems of different regions to achieve joint development. The implementation systems of each region or the implementation systems of the operator group can serve as the development subject.

[0066] Here, when designing the software development process information, it is stipulated which software interface belongs to which development subject's implementation system, so the identification of the development subject of each software interface can be resolved and determined. Exemplarily, the development subject includes the first province region, the second province region, the third province region, etc. The identification of the first province region is the name of the first province, the identification of the second province region is the name of the second province, the identification of the third province region is the name of the third province, etc. For example, if the software interface A is developed by the implementation system of the second province region, the identification of the development subject corresponding to the software interface A is the name of the second province.

[0067] The service type is used to indicate the type of service implemented by the software interface. For example, the service type includes the service of disassembling software products, the service of installing software products, the service of modifying software products, etc., which are not specifically limited here. In other words, the development of software products may involve processes such as disassembly, installation, and modification, and these processes may involve the development of software interfaces.

[0068] Step 103, divide each software interface according to the development information to obtain multiple software interface lists.

[0069] For example, for all software interfaces, each software interface can be divided according to the identification of the corresponding development entity, and divided into each development entity. For all software interfaces under each development entity, they are further divided based on their corresponding business types to obtain multiple software interface lists.

[0070] Alternatively, for all software interfaces, all software interfaces can be divided based on the corresponding business types of each software interface, and then divided into each business type. For all software interfaces under each business type, they can be further divided based on the identification of their corresponding development entities to obtain multiple software interface lists.

[0071] Optionally, the development information may also include other information of each software interface, which may be further divided according to the other information to obtain multiple more detailed software interface lists.

[0072] The above interface statistics method obtains software development process information and design pattern information of the software product for indicating the business development process of the software product; obtains multiple software interfaces of the software product and development information of each software interface according to the software development process information and design pattern information; the development information of the software interface includes at least one of the identification of the development subject of the software interface and the business type corresponding to the software interface; divides each software interface according to the development information to obtain multiple software interface lists. In this way, the software interfaces involved in the software product can be automatically counted and divided by this method, which is more efficient than manual statistics, and has a high accuracy rate because the software interfaces are counted and further divided based on the software development process information and design pattern information of the software product itself.

[0073] The following is an explanation of the process of parsing software development process information.

[0074] In one embodiment, Figure 2 A schematic diagram of a process for obtaining a software interface provided by an embodiment of the present application is shown. Based on the software development process information and design pattern information, multiple software interfaces of a software product and development information of each software interface are obtained, including:

[0075] Step 201 , parse the software development process information to obtain one or more product layer interface development process information and development information of each product layer interface development process information.

[0076] The software development process information indicates the overall business development process. The business development process is composed of many sub-processes. In other words, the business development process is implemented by multiple sub-processes designed in a hierarchical manner, that is, it is implemented by the product layer interface development process. By parsing the software development process information, the product layer interface development process information can be obtained. The product layer interface development process information is used to indicate the product layer interface development process of the software product.

[0077] It should be noted that each development process refers to the computer algorithm implementation process of the product.

[0078] The development information of the product layer interface development process information includes the identification and business type of the development subject corresponding to the product layer interface development process information. The description of the identification and business type of the development subject can be found in the above description and will not be repeated here.

[0079] Step 202, according to the development information of each product layer interface development process information, determine the target product layer development process information from the product layer interface development process information.

[0080] Among them, the target product layer interface development process information is one or more.

[0081] Optionally, based on the development information of each product layer interface development process information, the target product layer development process information is determined from the each product layer interface development process information, including: taking the identifier of the corresponding development entity including the target entity identifier and the corresponding business type as the product layer interface development process information of the target business type as the target product layer interface development process information.

[0082] The development entity corresponding to the target entity identifier is the development entity that currently has a business activation plan; the target business type is the business type of the current plan.

[0083] For example, the product service design center's currently planned business type is software product disassembly, and the regions involved in this business are the first province region, the second province region, and the third province region. Then the development entities that currently have business launch plans are the first province region and the second province region.

[0084] If the identification of the development entity corresponding to the product layer interface development process information 1 includes the first province region and the third province region and the business type is the business of disassembling software products, then the product layer interface development process information 1 can be used as the target product layer interface development process information.

[0085] If the identifier of the development entity corresponding to the product layer interface development process information 2 includes the first province region and the business type is the business of disassembling software products, then the product layer interface development process information 2 can be used as the target product layer interface development process information.

[0086] If the identifier of the development entity corresponding to the product layer interface development process information 3 includes a third province region and the business type is the business of disassembling software products, then the product layer interface development process information 3 will not be used as the target product layer interface development process information.

[0087] If the identification of the development entity corresponding to the product layer interface development process information 4 includes the first province region and the second province region and the business type is the business of installing software products, then the product layer interface development process information 4 is not used as the target product layer interface development process information.

[0088] Optionally, based on the development information of each product layer interface development process information, target product layer development process information is determined from each product layer interface development process information, including: taking all product layer interface development process information including valid content as target product layer interface development process information.

[0089] Step 203, according to the design pattern information, the target product layer development process information is disassembled in layers to obtain multiple software interfaces and development information of each software interface.

[0090] In an embodiment of the present application, the interface statistics method can be used for software products based on the PSR model, that is, the design pattern information is used to indicate that the design pattern of the software product is a design pattern based on the PSR model.

[0091] Due to the layered design based on the PSR model, the software interface includes the software interface of each layer. Here, the software interface includes at least one of the following:

[0092] 1. Product layer software interface.

[0093] 2. CFS layer software interface.

[0094] 3. RFS layer software interface.

[0095] 4. RFS layer software interface.

[0096] The PSR conceptual model defined in the TMF specification is abstracted from the service capabilities provided by customer-oriented services (CFS), resource-oriented services (RFS), and resources (RES). Therefore, the software interface designed based on the PSR model layered design includes the CFS layer, the RFS layer, and the software interface of the RFS layer.

[0097] In one embodiment, according to the design pattern information, the target product layer development process information is disassembled in layers to obtain multiple software interfaces and development information of each software interface, including:

[0098] According to the PSR model, the target product layer development process information is layered and disassembled in the order of CFS layer, RFS layer and RES layer, and multiple software interfaces corresponding to the CFS layer, RFS layer and RES layer and the development information of each software interface are obtained.

[0099] Please refer to Figure 3 , shows another flow diagram of obtaining a software interface provided by an embodiment of the present application. According to the design pattern information, the target product layer development process information is disassembled in layers to obtain multiple software interfaces and development information of each software interface, including:

[0100] Step 301, parse the target product layer development process information according to the PSR model, obtain one or more CFS layer interface development process information and development information of the CFS layer interface development process information, and obtain one or more product layer software interfaces and development information of the product layer software interface.

[0101] That is, the target product layer development process information includes the CFS layer interface development process information and the product layer software interface. And each process information and software interface is bound to the corresponding development information, and can be obtained after disassembling the target product layer development process information.

[0102] At this point, the product layer software interface has been obtained as a part of the software interface, and its corresponding development information has been obtained for the partitioning process.

[0103] Step 302, according to the development information of each CFS layer interface development process information, determine the target CFS layer interface development process information from each CFS layer interface development process information; the target CFS layer interface development process information is one or more.

[0104] Optionally, the CFS layer interface development process information including valid information may be used as the target CFS layer interface development process information to avoid subsequent unnecessary disassembly process.

[0105] Optionally, the identification of the corresponding development subject including the target subject identification and the CFS layer interface development process information of the corresponding business type being the target business type can be used as the target CFS layer interface development process information. Among them, the development subject corresponding to the target subject identification is the development subject that currently has a business activation plan; the target business type is the business type of the current plan. In this way, since the implementation system of the development subject that currently has a business activation plan will implement the development of the software interface, the process involving the development subject that has no business activation plan is excluded in advance, which speeds up the process of obtaining and counting the software interface.

[0106] Step 303: according to the design pattern information, the target CFS layer interface development process information is disassembled to obtain multiple software interfaces and development information of each software interface.

[0107] In one embodiment, Figure 4Another process diagram for obtaining a software interface provided by an embodiment of the present application is shown. According to the design pattern information, the target CFS layer interface development process information is disassembled to obtain multiple software interfaces and development information of each software interface, including:

[0108] Step 401, parse the target CFS layer interface development process information according to the PSR model, obtain one or more RFS layer interface development process information and development information of the RFS layer interface development process information, and obtain one or more CFS layer software interfaces and development information of the CFS layer software interface.

[0109] That is, the target CFS layer interface development process information includes the RFS layer interface development process information and the CFS layer software interface. And each process information and software interface is bound to the corresponding development information, and can be obtained after disassembling the target CFS layer interface development process information.

[0110] At this point, the CFS layer software interface has been obtained as a part of the software interface, and its corresponding development information has been obtained for the partitioning process.

[0111] Step 402, according to the development information of each RFS layer interface development process information, determine the target RFS layer interface development process information from each RFS layer interface development process information; the target RFS layer interface development process information is one or more.

[0112] Optionally, the RFS layer interface development process information including the valid information may be used as the target RFS layer interface development process information.

[0113] Optionally, the identification of the corresponding development subject including the target subject identification and the RFS layer interface development process information of the corresponding business type being the target business type can be used as the target RFS layer interface development process information. Among them, the development subject corresponding to the target subject identification is the development subject that currently has a business activation plan; the target business type is the business type of the current plan.

[0114] Step 403, according to the design pattern information, disassemble the target RFS layer interface development process information to obtain multiple software interfaces and development information of each software interface.

[0115] In one embodiment, Figure 5 Another process diagram for obtaining a software interface provided by an embodiment of the present application is shown. According to the design pattern information, the target RFS layer interface development process information is disassembled to obtain multiple software interfaces and development information of each software interface, including:

[0116] Step 501, parse the target RFS layer interface development process information according to the PSR model, obtain one or more RES layer interface development process information and development information of the RES layer interface development process information, and obtain one or more RFS layer software interfaces and development information of the RFS layer software interface.

[0117] That is, the target RFS layer interface development process information includes the RES layer interface development process information and the RFS layer software interface, and each process information and software interface is bound to the corresponding development information, which can be obtained after disassembling the target RFS layer interface development process information.

[0118] At this point, the RFS layer software interface has been obtained as a part of the software interface, and its corresponding development information has been obtained for the partitioning process.

[0119] Step 502: According to the development information of each RES layer interface development process information, target RES layer interface development process information is determined from each RES layer interface development process information.

[0120] Optionally, the RES layer interface development process information including the valid information may be used as the target RES layer interface development process information.

[0121] Optionally, the corresponding development subject identifier including the target subject identifier and the RES layer interface development process information of the target business type may be used as the target RES layer interface development process information. The development subject corresponding to the target subject identifier is the development subject with the current business activation plan; the target business type is the business type of the current plan.

[0122] Step 503: according to the design pattern information, disassemble the target RES layer interface development process information to obtain multiple software interfaces and development information of each software interface.

[0123] In one embodiment, according to the design pattern information, the target RES layer interface development process information is disassembled to obtain multiple software interfaces and the development information of each software interface, including: parsing the target RES layer interface development process information according to the PSR model to obtain one or more RES layer software interfaces and the development information of the RES layer software interface.

[0124] The interface statistics method provided in the embodiment of the present application proposes to automatically count the APIs in the IT process of software product service activation under the hierarchical decoupled PSR mode network topology structure, thereby improving the efficiency and accuracy of API statistics.

[0125] In one embodiment, Figure 6A schematic diagram of a process for dividing software interfaces is shown. In which, each software interface is divided according to development information to obtain multiple software interface lists, including:

[0126] Step 601 : performing a first division process on each software interface according to the identification of the development entity of each software interface to obtain a plurality of initial software interface lists.

[0127] Among them, different initial software interface lists correspond to the identifiers of different development entities, and the software interfaces included in the same initial software interface list correspond to the identifier of the same development entity.

[0128] For example, if the developer of software interface A, software interface C, software interface D, software interface F, and software interface H is identified by the second province name, then software interface A, software interface C, software interface D, software interface F, and software interface H are classified under the initial software interface list 1 corresponding to the second province name. If the developer of software interface B, software interface D, software interface E, software interface G, and software interface L is identified by the first province name, then software interface B, software interface D, software interface E, software interface G, and software interface L are classified under the initial software interface list 2 corresponding to the first province name.

[0129] It is understandable that the number of software interfaces included in each initial software interface list may be the same or different.

[0130] Step 602: For each initial software interface list, a second division process is performed on each software interface in the initial software interface list according to the business type corresponding to each software interface in the initial software interface list to obtain a plurality of software interface lists.

[0131] Among them, different software interface lists correspond to different business types, and the software interfaces included in the same software interface list correspond to the same business type.

[0132] For example, for the initial software interface list 1, the business type of software interface A is the business of dismantling software products, the business type of software interface C is the business of dismantling software products, the business type of software interface D is the business of dismantling software products, the business type of software interface F is the business of changing software products, and the business type of software interface H is the business of changing software products, then software interface A, software interface C and software interface D are classified under software interface list 1, and software interface D and software interface F are classified under software interface list 2.

[0133] Optionally, if the currently planned business type is a business of disassembling software products, only software interface list 1 is retained.

[0134] In one embodiment, the method further includes: visually displaying a list of each software interface.

[0135] In one embodiment, the method further includes: performing a de-duplication process on the software interfaces in each software interface list to obtain candidate software interface lists without duplicate software interfaces; for each candidate software interface list, performing a third division process on each software interface in the candidate software interface list according to the professional system type to which each software interface belongs to obtain multiple target software interface lists; wherein different target software interface lists correspond to different professional system types.

[0136] Among them, the same software interface may exist in different processes, so the same software interface may be divided into the same software interface list multiple times. The development of the software interface only needs to be done once, so it can be de-duplicated to obtain a non-repetitive list and avoid repeated development work.

[0137] In addition, the development information of the software interface may also include the type of professional system to which the software interface belongs. The professional system type described in the software interface may be further divided to obtain a more detailed target software interface list.

[0138] Exemplarily, professional system types include orchestration system, resource system, acquisition and control system, integrated dispatching system, etc. The API interface of the resource system is used to manage and allocate equipment resources, such as equipment code number, bandwidth, etc.; the API interface of the integrated dispatching system is used to schedule business implementation processes; the API interface of the acquisition and control system is used to manage, dispatch and use network element equipment; the API interface of the orchestration system is used to enable each device to operate.

[0139] For example, for software interface list 1, software interface A belongs to the resource system, software interface C belongs to the orchestration system, and software interface D belongs to the orchestration system. Then software interface C and software interface D are classified under target software interface list 1, and software interface A is classified under target software interface list 2.

[0140] It can be understood that the identification and business type of the development entity corresponding to the target software interface list 1 and the target software interface list 2 are the same.

[0141] In the embodiment of the present application, the software interfaces are divided layer by layer according to various development information to obtain multiple software interface lists, so that each development entity can develop the corresponding software interface according to the development information, thereby effectively improving the development efficiency. In addition, it is convenient to monitor the development progress of each software interface based on the software interface list.

[0142] In one embodiment, the method further includes: visually displaying a list of each target software interface.

[0143] The statistical results can be displayed in the product loading progress visualization module for visualization. In this way, the API list can be displayed by three dimensions: region, business type, and professional system, which is helpful for automatic monitoring of business loading progress.

[0144] In one embodiment, the software interfaces are divided according to the development information to obtain multiple software interface lists, including: performing a first division process on each software interface according to the business type of each software interface to obtain multiple initial software interface lists; wherein different initial software interface lists correspond to different business types, and the software interfaces included in the same initial software interface list correspond to the same business type. For each initial software interface list, a second division process is performed on each software interface according to the identification of the development subject corresponding to each software interface in the initial software interface list to obtain multiple software interface lists; wherein different software interface lists correspond to the identification of different development subjects, and the software interfaces included in the same initial software interface list correspond to the identification of the same development subject.

[0145] Optionally, the software interfaces may be further divided according to the types of professional systems to which they belong, to obtain multiple target software interface lists, which will not be elaborated here.

[0146] For ease of understanding, the following is a complete process to illustrate the API automated statistical method for the service activation process based on the PSR mode network topology provided by the embodiment of the present application. The method proposed in the embodiment of the present application obtains the corresponding product service activation process plan according to the service type and regional information in the product (P) service activation plan, and expands the service activation process from product (P) to business service and network service (S) and then to resource (S) in a tree-like manner according to the PSR model, and filters the API nodes in the tree according to the service activation plan area. Finally, all APIs involved in the service activation plan are sorted out, and a list of APIs that need to be developed and debugged in different regions, as well as a list of APIs that need to be developed for different professional systems in each province, are sorted out, and the API statistical results are intuitively displayed through visualization tools.

[0147] Please refer to Figure 7, confirm the business type of the service activation plan and the software product business process information of the software product corresponding to the current business plan activation area; parse the software product business process information to obtain the product layer API process information. Analyze the product layer API process information to obtain the product layer resource system API and CFS business service layer API process information. According to the PSR mode, parse the API process information of the CFS business service layer to obtain the resource class API and comprehensive adjustment class API of the CFS layer, as well as the API process information of the RFS network service layer. According to the PSR mode, parse the API process information of the RFS network service layer to obtain the RFS layer resource class API and comprehensive adjustment class API, as well as the API process information of RES resources and network element configuration class. Analyze the API process information of RES resources and network element configuration class to obtain RES class API.

[0148] When each API process is expanded in layers, there may be a situation where one API corresponds to business processes in multiple regions. At this time, the following logic is used to determine whether to parse and expand the API process based on the region and business type:

[0149] Filter out processes whose applicable areas have no intersection with the current business launch plan area; only parse processes that have intersection with the current business launch plan area;

[0150] When the process applicable area and the current business opening plan area have some provinces intersecting, it is necessary to parse and expand the API process, and the node API under the process tree is only counted in the provinces within the intersection;

[0151] Only processes whose business type is consistent with the current business activation type are parsed.

[0152] For example, the current business opening plan areas include Guangdong and Guangxi, the product applicable area is China, and the product API applicable area is China; 1. If a process is applicable to Fujian, the process and all the nodes under it will not be extracted; 2. If a process is applicable to Guangdong, the API under the process needs to be extracted and only counted in the API list of Guangdong Province, but when drilling down, a regional match must be done for each process encountered, and there is no need to extract processes that do not include Guangdong Province; 3. If there is a process with an applicable area including Guangdong and Guangxi, the API under the process needs to be extracted and counted under Guangdong and Guangxi; if there is a process with an applicable area of ​​Guangdong and Jiangxi, the node API under the process needs to be extracted and only counted under Guangdong; Among them, a regional match must be done for each process encountered when drilling down, and there is no need to extract processes that do not include Guangdong and Guangxi, or if there is only one of Guangdong or Guangxi, the extracted process is only placed in the corresponding area.

[0153] Finally, among all the API lists that have been counted, those whose corresponding regions are provinces are counted under the development lists of their respective provinces to eliminate duplicates. According to the type of business system to which the API corresponds, the API is divided into four professional systems: orchestration, resources, acquisition and control, and comprehensive coordination. Generate an API list for the product business activation process, and count the list that needs to be developed in each province, and the list that needs to be developed for each professional system in the province. Display the statistical results in the product loading progress visualization module, and display the API list in three dimensions: business type-region-professional system; automatically monitor the business loading progress.

[0154] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0155] Based on the same inventive concept, the embodiment of the present application also provides an interface statistics device for implementing the interface statistics method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more interface statistics device embodiments provided below can refer to the limitations on the interface statistics method above, and will not be repeated here.

[0156] In one embodiment, Figure 8 As shown, an interface statistics device is provided, and the interface statistics device 800 includes: an information acquisition module 801, an interface acquisition module 802 and an interface division module 803, wherein:

[0157] The information acquisition module 801 is used to acquire software development process information and design pattern information of the software product; the software development process information is used to indicate the business development process of the software product;

[0158] The interface acquisition module 802 is used to obtain multiple software interfaces of the software product and development information of each software interface according to the software development process information and the design pattern information; the development information of the software interface includes at least one of the identification of the development subject of the software interface and the business type corresponding to the software interface;

[0159] The interface division module 803 is used to divide each software interface according to the development information to obtain multiple software interface lists.

[0160] In one embodiment, the interface acquisition module 802 is specifically used to: parse the software development process information to obtain one or more product layer interface development process information and development information of each product layer interface development process information; the development information of the product layer interface development process information includes the identification and business type of the development entity corresponding to the product layer interface development process information; according to the development information of each product layer interface development process information, determine the target product layer development process information from each product layer interface development process information; the target product layer interface development process information is one or more; according to the design pattern information, disassemble the target product layer development process information in layers to obtain multiple software interfaces and development information of each software interface.

[0161] In one embodiment, the design pattern information is used to indicate that the design pattern of the software product is a design pattern based on the PSR model; the software interface includes at least one of the following: product layer software interface; CFS layer software interface; RFS layer software interface; RES layer software interface.

[0162] In one embodiment, the interface acquisition module 802 is specifically used to: use the identification of the corresponding development entity including the target entity identification and the product layer interface development process information of the corresponding business type being the target business type as the target product layer interface development process information; wherein, the development entity corresponding to the target entity identification is the development entity that currently has a business activation plan; and the target business type is the business type of the current plan.

[0163] In one embodiment, the interface acquisition module 802 is specifically used to: parse the target product layer development process information according to the PSR model, obtain one or more CFS layer interface development process information and development information of the CFS layer interface development process information, and obtain one or more product layer software interfaces and development information of the product layer software interfaces; determine the target CFS layer interface development process information from each CFS layer interface development process information according to the development information of each CFS layer interface development process information; the target CFS layer interface development process information is one or more; disassemble the target CFS layer interface development process information according to the design pattern information to obtain multiple software interfaces and development information of each software interface.

[0164] In one embodiment, the interface acquisition module 802 is specifically used to: parse the target CFS layer interface development process information according to the PSR model, obtain one or more RFS layer interface development process information and development information of the RFS layer interface development process information, and obtain one or more CFS layer software interfaces and development information of the CFS layer software interfaces; determine the target RFS layer interface development process information from each RFS layer interface development process information according to the development information of each RFS layer interface development process information; the target RFS layer interface development process information is one or more; disassemble the target RFS layer interface development process information according to the design pattern information to obtain multiple software interfaces and development information of each software interface.

[0165] In one embodiment, the interface acquisition module 802 is specifically used to: parse the target RFS layer interface development process information according to the PSR model, obtain one or more RES layer interface development process information and development information of the RES layer interface development process information, and obtain one or more RFS layer software interfaces and development information of the RFS layer software interfaces; determine the target RES layer interface development process information from the development process information of each RES layer interface according to the development information of the development process information of each RES layer interface; disassemble the target RES layer interface development process information according to the design pattern information, and obtain multiple software interfaces and development information of each software interface.

[0166] In one embodiment, the interface acquisition module 802 is specifically used to: parse the target RES layer interface development process information according to the PSR model to obtain one or more RES layer software interfaces and the development information of the RES layer software interface.

[0167] In one embodiment, the interface division module 803 is specifically used to: perform a first division process on each software interface according to the identification of the development entity of each software interface to obtain multiple initial software interface lists; wherein different initial software interface lists correspond to the identification of different development entities, and the software interfaces included in the same initial software interface list correspond to the identification of the same development entity; for each initial software interface list, perform a second division process on each software interface in the initial software interface list according to the business type corresponding to each software interface in the initial software interface list to obtain multiple software interface lists; wherein different software interface lists correspond to different business types, and the software interfaces included in the same software interface list correspond to the same business type.

[0168] In one embodiment, the development information of the software interface also includes the professional system type to which the software interface belongs; the device also includes a processing module, which is used to: remove duplicate software interfaces in each software interface list to obtain candidate software interface lists without duplicate software interfaces; for each candidate software interface list, perform a third division process on each software interface in the candidate software interface list according to the professional system type to which each software interface belongs to obtain multiple target software interface lists; wherein different target software interface lists correspond to different professional system types.

[0169] In one embodiment, the device further includes a display module for visually displaying a list of each target software interface.

[0170] Each module in the above interface statistics device can be implemented in whole or in part by software, hardware and a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module above.

[0171] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Fig. 9 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store interface partition data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, an interface statistics method is implemented.

[0172] Those skilled in the art will understand that Fig. 9 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0173] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

[0174] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0175] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0176] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0177] The technical features of the above embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0178] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. An interface statistics method, characterized in that: The method comprises: Acquire software development process information and design pattern information of a software product; the software development process information is used to indicate the business development process of the software product; According to the software development process information and the design pattern information, a plurality of software interfaces of the software product and development information of each of the software interfaces are obtained; the development information of the software interface includes at least one of an identifier of a development entity that develops the software interface and a business type corresponding to the software interface; The software interfaces are divided according to the development information to obtain multiple software interface lists.

2. The method according to claim 1, characterized in that The step of obtaining a plurality of software interfaces of the software product and development information of each of the software interfaces according to the software development process information and the design pattern information includes: Parse the software development process information to obtain one or more product layer interface development process information and development information of each product layer interface development process information; the development information of the product layer interface development process information includes an identifier and a business type of a development subject corresponding to the product layer interface development process information; According to the development information of each product layer interface development process information, determine the target product layer development process information from each product layer interface development process information; the target product layer interface development process information is one or more; According to the design pattern information, the target product layer development process information is disassembled in layers to obtain a plurality of software interfaces and development information of each of the software interfaces.

3. The method according to claim 2, characterized in that The design pattern information is used to indicate that the design pattern of the software product is a design pattern based on a PSR model; and the software interface includes at least one of the following: Product layer software interface; CFS layer software interface; RFS layer software interface; RES layer software interface.

4. The method according to claim 2, characterized in that: The step of determining target product layer development process information from each product layer interface development process information according to the development information of each product layer interface development process information includes: The identification of the corresponding development subject including the target subject identification and the product layer interface development process information whose corresponding business type is the target business type is used as the target product layer interface development process information; The development entity corresponding to the target entity identifier is a development entity that currently has a service activation plan; and the target service type is a service type currently planned.

5. The method according to claim 3, characterized in that: The step of disassembling the target product layer development process information in layers according to the design pattern information to obtain a plurality of software interfaces and development information of each of the software interfaces includes: Parsing the target product layer development process information according to the PSR model to obtain one or more CFS layer interface development process information and development information of the CFS layer interface development process information, and obtaining one or more product layer software interfaces and development information of the product layer software interfaces; According to the development information of each of the CFS layer interface development process information, determining target CFS layer interface development process information from each of the CFS layer interface development process information; the target CFS layer interface development process information is one or more; According to the design pattern information, the target CFS layer interface development process information is disassembled to obtain a plurality of software interfaces and development information of each of the software interfaces.

6. The method according to claim 5, characterized in that The step of disassembling the target CFS layer interface development process information according to the design pattern information to obtain multiple software interfaces and development information of each of the software interfaces includes: Parsing the target CFS layer interface development process information according to the PSR model to obtain one or more RFS layer interface development process information and development information of the RFS layer interface development process information, and obtaining one or more CFS layer software interfaces and development information of the CFS layer software interface; According to the development information of each of the RFS layer interface development process information, determining target RFS layer interface development process information from each of the RFS layer interface development process information; the target RFS layer interface development process information is one or more; According to the design pattern information, the target RFS layer interface development process information is disassembled to obtain a plurality of software interfaces and development information of each of the software interfaces.

7. The method according to claim 6, characterized in that The step of disassembling the target RFS layer interface development process information according to the design pattern information to obtain multiple software interfaces and development information of each of the software interfaces includes: Parsing the target RFS layer interface development process information according to the PSR model to obtain one or more RES layer interface development process information and development information of the RES layer interface development process information, and obtaining one or more RFS layer software interfaces and development information of the RFS layer software interface; Determining target RES layer interface development process information from each of the RES layer interface development process information according to the development information of each of the RES layer interface development process information; According to the design pattern information, the target RES layer interface development process information is disassembled to obtain a plurality of software interfaces and development information of each of the software interfaces.

8. The method according to claim 7, characterized in that The step of disassembling the target RES layer interface development process information according to the design pattern information to obtain multiple software interfaces and development information of each of the software interfaces includes: The target RES layer interface development process information is parsed according to the PSR model to obtain one or more RES layer software interfaces and development information of the RES layer software interfaces.

9. The method according to claim 3, characterized in that: The software interfaces are divided according to the development information to obtain multiple software interface lists, including: According to the identification of the development subject of each software interface, each software interface is subjected to a first division process to obtain a plurality of initial software interface lists; wherein different initial software interface lists correspond to the identification of different development subjects, and the software interfaces included in the same initial software interface list correspond to the identification of the same development subject; For each of the initial software interface lists, a second division process is performed on each of the software interfaces in the initial software interface list according to the business type corresponding to each of the software interfaces in the initial software interface list to obtain multiple software interface lists; wherein different software interface lists correspond to different business types, and the software interfaces included in the same software interface list correspond to the same business type.

10. The method according to claim 9, characterized in that The development information of the software interface also includes the type of professional system to which the software interface belongs; the method further includes: Deduplication processing is performed on the software interfaces in each of the software interface lists to obtain candidate software interface lists without duplicate software interfaces; For each of the candidate software interface lists, a third division process is performed on each of the software interfaces in the candidate software interface list according to the professional system type to which each of the software interfaces belongs, so as to obtain multiple target software interface lists; wherein different target software interface lists correspond to different professional system types.

11. The method according to claim 10, characterized in that The method further comprises: Visually display the list of each target software interface.

12. An interface statistics device, characterized in that: The device comprises: An information acquisition module, used to acquire software development process information and design pattern information of a software product; the software development process information is used to indicate the business development process of the software product; An interface acquisition module, used to obtain multiple software interfaces of the software product and development information of each of the software interfaces according to the software development process information and the design pattern information; the development information of the software interface includes at least one of an identifier of a development entity that develops the software interface and a business type corresponding to the software interface; The interface division module is used to divide each of the software interfaces according to the development information to obtain multiple software interface lists.

13. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 11 are implemented.

14. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 11 are implemented.

15. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 11 are implemented.

Images