Software development energy efficiency evaluation method and device, electronic equipment and storage medium

Abstract

The invention relates to the technical field of software development, in particular to a software development energy efficiency evaluation method and device, electronic equipment and a storage medium, and is used for improving the accuracy of software development energy efficiency evaluation. The method comprises the following steps: acquiring access data of each interface of to-be-evaluated software, and calculating the access volume of each interface; and calculating the energy efficiency evaluation value of each interface based on each key index value and the page view corresponding to each interface, each key index value including a page view weight value and each functional value value of the corresponding interface, and each functional value value being related to the business demand and the functional characteristic of the corresponding interface. Therefore, one interface is evaluated in a multi-dimensional manner through the page view weight value, each function value numerical value and the page view, an accurate energy efficiency evaluation value can be obtained, and the accuracy of an evaluation result is improved.

Description

Technical Field

[0001] The present application relates to the field of software development technology, and in particular to a software development energy efficiency evaluation method, device, electronic device and storage medium. Background Art

[0002] With the rapid development of information technology, software development has become an important part of modern society. The quality and performance of software products directly affect the operational efficiency and market competitiveness of enterprises. Therefore, it is very important to effectively manage and optimize the software development process and improve the efficiency of software development.

[0003] In the prior art, energy efficiency evaluation of software development is often performed based on the amount of interface access.

[0004] However, relying solely on interface access volume to evaluate energy efficiency may ignore the different needs and expectations of different user groups for functions, resulting in inaccurate evaluation results. For example, the same usage frequency may come from frequent use by a few heavy users, or occasional use by a large number of users, which has different meanings in energy efficiency evaluation. Summary of the invention

[0005] The embodiments of the present application provide a software development energy efficiency evaluation method, device, electronic device and storage medium to improve the accuracy of software development energy efficiency evaluation.

[0006] The specific technical solutions provided by the embodiments of this application are as follows:

[0007] In a first aspect, a method for evaluating software development energy efficiency is provided, the method comprising:

[0008] Collect access data of each interface of the software to be evaluated and calculate the access volume of each interface;

[0009] Based on the key indicator values ​​and access volume corresponding to each interface, the energy efficiency evaluation value of each interface is calculated, where each key indicator value includes: an access volume weight value and a functional value value of the corresponding interface, and each functional value value is related to the business requirements and functional characteristics of the corresponding interface.

[0010] In a possible embodiment, the access data includes: user access request data and / or user behavior browsing data.

[0011] In a possible embodiment, collecting access data of each interface of the software to be evaluated includes:

[0012] Use probes to obtain access request data; and / or,

[0013] Integrate the software development kit (SDK) to obtain access request data; and / or,

[0014] Integrate JavaScript scripts to collect browsing behavior data.

[0015] Through the above method, access data can be comprehensively collected and analyzed, and a variety of technical means can be adopted to achieve real-time acquisition and reporting of data, thereby obtaining accurate access volume.

[0016] In a possible embodiment, each functional value value includes but is not limited to: an importance value value and a business added value value;

[0017] Among them, the importance value numerical representation: the importance of the function of the corresponding interface in the software to be evaluated, and the business added value numerical representation: the degree to which the function of the corresponding interface improves the business value.

[0018] Through the above method, the accuracy of evaluation can be improved.

[0019] In a possible embodiment, after calculating the energy efficiency evaluation value of each interface based on each key indicator value and access volume corresponding to each interface, the method further includes:

[0020] The energy efficiency evaluation values ​​of each interface are arranged and displayed to obtain the energy efficiency evaluation results of the software to be evaluated.

[0021] Through the above method, the energy efficiency evaluation value of each interface can be clearly and directly understood, which facilitates more intuitive observation and comparison of the differences between the interfaces.

[0022] In a possible embodiment, after calculating the energy efficiency evaluation value of each interface based on each key indicator value and access volume corresponding to each interface, the method further includes:

[0023] From each interface, select the interfaces to be improved whose energy efficiency evaluation values ​​meet the improvement conditions, and notify the developers that the interfaces to be improved need to be improved.

[0024] Through the above method, problems in the software can be discovered in time, and corresponding measures can be taken to repair or improve them, which can avoid user loss or business loss caused by software problems.

[0025] In a second aspect, the present application provides a software development energy efficiency evaluation device, the device comprising:

[0026] The collection module is used to collect the access data of each interface of the software to be evaluated and calculate the access volume of each interface;

[0027] The evaluation module is used to calculate the energy efficiency evaluation value of each interface based on the key indicator values ​​and access volume corresponding to each interface, wherein each key indicator value includes: an access volume weight value and a functional value value of the corresponding interface, and each functional value value is related to the business requirements and functional characteristics of the corresponding interface.

[0028] In a possible embodiment, the access data includes: user access request data and / or user behavior browsing data.

[0029] In a possible embodiment, when collecting access data of each interface of the software to be evaluated, the collection module is further used to:

[0030] Use probes to obtain access request data; and / or,

[0031] Integrate the software development kit (SDK) to obtain access request data; and / or,

[0032] Integrate JavaScript scripts to collect browsing behavior data.

[0033] In a possible embodiment, each functional value value includes but is not limited to: an importance value value and a business added value value;

[0034] Among them, the importance value numerical representation: the importance of the function of the corresponding interface in the software to be evaluated, and the business added value numerical representation: the degree to which the function of the corresponding interface improves the business value.

[0035] In a possible embodiment, after calculating the energy efficiency evaluation value of each interface based on each key indicator value and access volume corresponding to each interface, the device further includes a processing module, which is used to:

[0036] The energy efficiency evaluation values ​​of each interface are arranged and displayed to obtain the energy efficiency evaluation results of the software to be evaluated.

[0037] In a possible embodiment, after calculating the energy efficiency evaluation value of each interface based on each key indicator value and access volume corresponding to each interface, the processing module is further used to:

[0038] From each interface, select the interfaces to be improved whose energy efficiency evaluation values ​​meet the improvement conditions, and notify the developers that the interfaces to be improved need to be improved.

[0039] In a third aspect, the present application provides an electronic 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 program, the steps of any one of the methods described in the first aspect are implemented.

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

[0041] In a fifth aspect, the present application provides a computer program product, comprising: a computer program code, when the computer program code is run on a computer, the computer executes any one of the methods described in the first aspect.

[0042] In the embodiment of the present application, the access data of each interface of the software to be evaluated is collected, and the access volume of each interface is calculated. Then, based on the key indicator values ​​and access volume corresponding to each interface, the energy efficiency evaluation value of each interface is calculated, wherein each key indicator value includes: the access volume weight value and the value of each function value of the corresponding interface, and each function value value is related to the business requirements and functional characteristics of the corresponding interface. In this way, through the access volume weight value and the value of each function value, as well as the access volume, an interface can be evaluated in multiple dimensions to obtain an accurate energy efficiency evaluation value, thereby improving the accuracy of the evaluation results, thereby providing accurate guidance for developers, helping them optimize software design, better meeting user needs, and improving user satisfaction. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 A flowchart of a method for evaluating energy efficiency of software development in an embodiment of the present application;

[0044] Figure 2 A schematic diagram of a process of accessing data collection in an embodiment of the present application;

[0045] Figure 3 A schematic diagram of a flow chart of key indicator values ​​of a configuration interface in an embodiment of the present application;

[0046] Figure 4 A schematic diagram of a process for obtaining an energy efficiency evaluation result of the software to be evaluated in an embodiment of the present application;

[0047] Figure 5 This is a schematic diagram of the structure of a software development energy efficiency evaluation device in an embodiment of the present application;

[0048] Figure 6 Schematic diagram of the structure of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0049] In order to make the purpose, technical scheme and advantages of the present application clearer, the technical scheme in the embodiment of the present application will be clearly and completely described below in conjunction with the drawings in the embodiment of the present application. Obviously, the described embodiment is only a part of the embodiment of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application. In the absence of conflict, the embodiments in the present application and the features in the embodiments can be arbitrarily combined with each other. In addition, although the logical order is shown in the flow chart, in some cases, the steps shown or described can be performed in an order different from that here.

[0050] The terms "first" and "second" in the specification and claims of the present application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the term "comprising" and any of their variations are intended to cover non-exclusive protection. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices. "Multiple" in the present application can mean at least two, for example, two, three or more, and the embodiments of the present application are not limited.

[0051] The following is a description of exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding, which should be considered as merely exemplary. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope of the present application. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description. It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, which should be considered as exemplary, and their purpose is only to illustrate the feasibility of the implementation of the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0052] In the technical solution of this application, the acquisition, transmission, storage, and use of data are in compliance with the requirements of relevant national laws and regulations.

[0053] The following is a brief introduction to the design concept of the embodiment of the present application:

[0054] With the rapid development of information technology, software development has become an important part of modern society. The quality and performance of software products directly affect the operational efficiency and market competitiveness of enterprises. Therefore, it is very important to effectively manage and optimize the software development process and improve the efficiency of software development.

[0055] Traditional software development measurement methods focus on aspects such as code quality, development progress and cost control, but are relatively lacking in the value and performance evaluation of software functions in actual use. This makes it difficult for software development teams to accurately measure the commercial value and user satisfaction of their work results, and it is also difficult to optimize and improve software products in a targeted manner.

[0056] Existing technology evaluates the energy efficiency of software development based on the number of interface visits. Specifically, it is first necessary to set up data collection points in the system, which are usually done at the API gateway or service endpoint. Each interface call is tracked through logging, analysis tools or monitoring services, and the data obtained is used to calculate the frequency of use of the functional interface, including key performance indicators such as the total number of calls, average response time, and failure rate. These data help convert interface access into business value and identify the actual importance of the function. Long-term tracking of these data can also reveal usage trends, predict user needs and market changes, and provide a basis for adjusting development priorities.

[0057] However, although interface access statistics provide quantitative user engagement data, they only represent a single perspective for measuring the value of functions. This method cannot fully reflect user satisfaction, function quality, and support for business goals. If data is not collected and processed properly, it may lead to misleading conclusions. For example, data analysis that does not consider user behavior patterns may overestimate or underestimate the value of certain functions. In addition, relying solely on interface access to evaluate energy efficiency may ignore the different needs and expectations of different user groups for functions, resulting in inaccurate evaluation results. For example, the same frequency of use may come from frequent use by a few heavy users, or occasional use by a large number of users, which has different meanings in energy efficiency evaluation.

[0058] In view of this, in the embodiments of the present application, a method, device, electronic device and storage medium for evaluating energy efficiency of software development are provided, the access data of each interface of the software to be evaluated are collected, and the access volume of each interface is calculated, and then the energy efficiency evaluation value of each interface is calculated based on the key indicator values ​​and access volume corresponding to each interface, wherein each key indicator value includes: the access volume weight value and the value of each function value of the corresponding interface, and each function value value is related to the business requirements and functional characteristics of the corresponding interface. In this way, an interface can be evaluated in multiple dimensions through the access volume weight value and the value of each function value, as well as the access volume, and an accurate energy efficiency evaluation value can be obtained, which improves the accuracy of the evaluation results, thereby providing accurate guidance for developers, helping them optimize software design, and better meeting user needs and improving user satisfaction.

[0059] The preferred embodiments of the present application are described below in conjunction with the drawings in the specification. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present application, and are not used to limit the present application. In addition, the embodiments of the present application and the features in the embodiments may be combined with each other if there is no conflict.

[0060] Based on the above embodiments, see Figure 1 FIG. 1 is a flow chart of a method for evaluating software development energy efficiency in an embodiment of the present application, which specifically includes:

[0061] Step 10: Collect access data of each interface of the software to be evaluated, and calculate the access volume of each interface.

[0062] The access data includes: user's access request data and / or user's behavior browsing data.

[0063] In the embodiment of the present application, any one or any combination of the following three methods is used to obtain access data of each interface of the software to be evaluated.

[0064] Method 1: Use a probe to obtain access request data.

[0065] Among them, a probe is a small program or tool that can be embedded in the system to monitor and record the system's operating status, performance indicators, user requests and other information in real time.

[0066] In an embodiment of the present application, a probe is used to monitor and capture access request data. When the system is started, the probe will be automatically activated and start working. It will continuously extract access request data from the system, temporarily store the access request data, and finally report it to the back-end system.

[0067] Method 2: Integrate the software development kit SDK to obtain access request data.

[0068] Among them, SDK is a set of pre-written code libraries, which provides a set of application programming interfaces (Application Programming Interface, API), so that developers can easily call these APIs in their own applications to implement specific functions.

[0069] In an embodiment of the present application, the SDK is integrated into the application. When the application is running, the application will automatically call the API in the SDK to obtain access request data, temporarily store the access request data, and finally report it to the backend system.

[0070] Method 3: Integrate JavaScript scripts to collect browsing behavior data.

[0071] Among them, JavaScript script is a scripting language widely used in web page development, which can realize various dynamic effects and interactive functions.

[0072] In an embodiment of the present application, a JS script is integrated on the user page to capture the behavior browsing data of the user's operating behaviors on the page (such as clicking buttons, filling out forms, browsing pages, etc.) in real time, and the behavior browsing data is temporarily stored and finally reported to the back-end system.

[0073] In this way, access data can be comprehensively collected and analyzed, and a variety of technical means can be adopted to achieve real-time acquisition and reporting of data, thereby obtaining accurate access volume.

[0074] See also Figure 2 FIG. 1 is a flow chart of access data collection in an embodiment of the present application, which specifically includes:

[0075] Step 20: Start.

[0076] Step 21: Deploy the probe and SDK.

[0077] Step 22: System boot up.

[0078] Step 23: Integrate the JavaScript script.

[0079] Step 24: Capture access data in real time.

[0080] Step 25: Temporarily save the data.

[0081] Step 26: Report data to the backend system.

[0082] Step 27: End.

[0083] Step 11: Based on the key indicator values ​​and access volume corresponding to each interface, calculate the energy efficiency evaluation value of each interface.

[0084] Among them, each key indicator value includes: access volume weight value and each functional value value of the corresponding interface, and each functional value value is related to the business requirements and functional characteristics of the corresponding interface.

[0085] In the embodiment of the present application, the value values ​​of each functional value include but are not limited to: importance value value, business added value value, security value value, audit value value, compliance value value, etc.

[0086] Among them, the importance value numerical representation: the importance of the function of the corresponding interface in the software to be evaluated, and the business added value numerical representation: the degree to which the function of the corresponding interface improves the business value.

[0087] In the embodiment of the present application, the key indicator values ​​corresponding to each interface are set according to the business requirements and functional characteristics of each interface.

[0088] Exemplarily, when the functional features of interface A include ensuring safe use of software, the functional value value of interface A includes: a safety value value; when the functional features of interface B include supervising compliance in software use, the functional value value of interface B includes: a compliance value value.

[0089] In this way, by setting the values ​​of each key indicator, the performance of interface energy efficiency can be better monitored and managed, and the interface energy efficiency can be evaluated in multiple dimensions.

[0090] In addition, it is worth noting that in the embodiment of the present application, the key indicator values ​​corresponding to each of the set interfaces can be adjusted to meet the needs of different scenarios.

[0091] See also Figure 3 As shown, it is a schematic diagram of a process of configuring each key indicator value of an interface in an embodiment of the present application, specifically including:

[0092] Step 30: Start.

[0093] Step 31: Plan interface functions.

[0094] Step 32: Define the interface functional value.

[0095] Step 33: Set the values ​​of each key indicator.

[0096] Step 34: Redefine the interface functional value.

[0097] Step 35: Adjust the values ​​of each key indicator.

[0098] Step 36: End.

[0099] In the embodiment of the present application, after obtaining the key indicator values ​​and access volume corresponding to each interface, the following operations are performed for each interface: based on the key indicator values ​​and access volume corresponding to an interface, the energy efficiency evaluation value of the interface is calculated.

[0100] For example, the key indicator values ​​of interface C of the software include access weight value, business added value value, security value value, and compliance value value. The access weight value is 0.5, the business added value value is 100, the security value value is 50, the compliance value value is 500, and the access volume of interface C is 100. Then the energy efficiency evaluation value of interface C is 100*0.5+100+50+500=700.

[0101] In addition, it is worth noting that in the embodiment of the present application, there is no limit on the number of software to be evaluated, and multiple software to be evaluated can be evaluated at the same time.

[0102] Furthermore, in an embodiment of the present application, after calculating the energy efficiency evaluation value of each interface based on the key indicator values ​​and access volume corresponding to each interface, the energy efficiency evaluation value of each interface is arranged and displayed to obtain the energy efficiency evaluation result of the software to be evaluated.

[0103] Exemplarily, an arrangement classification diagram is used to sort and classify the energy efficiency evaluation values ​​according to specific rules.

[0104] In this way, R&D personnel can clearly and directly understand the energy efficiency evaluation value of each interface by observing the data in the graph, which facilitates more intuitive observation and comparison of the differences between the interfaces and the differences between the software.

[0105] See also Figure 4 FIG. 1 is a flow chart of obtaining the energy efficiency evaluation result of the software to be evaluated in an embodiment of the present application, which specifically includes:

[0106] Step 40: Start.

[0107] Step 41: Obtain the key indicator values ​​and access volume corresponding to each interface.

[0108] Step 42: Calculate the energy efficiency evaluation value of each interface based on the key indicator values ​​and access volume corresponding to each interface.

[0109] Step 43: Summarize and classify the energy efficiency evaluation values ​​obtained.

[0110] Step 44: Generate a permutation distribution graph.

[0111] Step 45: End.

[0112] Furthermore, in an embodiment of the present application, after calculating the energy efficiency evaluation value of each interface based on the key indicator values ​​and access volume corresponding to each interface, it is also possible to screen out the interfaces to be improved whose energy efficiency evaluation values ​​meet the improvement conditions from each interface, and notify the developers that the interfaces to be improved need to be improved.

[0113] Among them, the interface to be improved that meets the improvement conditions is the interface whose energy efficiency evaluation value is less than the qualified threshold.

[0114] In this way, problems in the software can be discovered in a timely manner and appropriate measures can be taken to repair or improve them, which can avoid user loss or business losses due to software problems. It can also provide guidance to developers, helping them optimize software design and improve the software's user experience and market competitiveness.

[0115] At the same time, in an embodiment of the present application, after calculating the energy efficiency evaluation value of each interface based on the key indicator values ​​and access volume corresponding to each interface, it is also possible to screen out excellent interfaces with top energy efficiency evaluation values ​​from each interface, so as to facilitate subsequent maintenance and optimization of the excellent interfaces and improve the user experience of the software.

[0116] Based on the same inventive concept, the present application embodiment provides a software development energy efficiency evaluation device, please refer to Figure 5 , the device comprises:

[0117] The collection module 501 is used to collect access data of each interface of the software to be evaluated and calculate the access volume of each interface;

[0118] Evaluation module 502 is used to calculate the energy efficiency evaluation value of each interface based on the key indicator values ​​and access volume corresponding to each interface, wherein each key indicator value includes: an access volume weight value and each functional value value of the corresponding interface, and each functional value value is related to the business requirements and functional characteristics of the corresponding interface.

[0119] In a possible embodiment, the access data includes: user access request data and / or user behavior browsing data.

[0120] In a possible embodiment, when collecting access data of each interface of the software to be evaluated, the collection module 501 is further used to:

[0121] Use probes to obtain access request data; and / or,

[0122] Integrate the software development kit (SDK) to obtain access request data; and / or,

[0123] Integrate JavaScript scripts to collect browsing behavior data.

[0124] In a possible embodiment, each functional value value includes but is not limited to: an importance value value and a business added value value;

[0125] Among them, the importance value numerical representation: the importance of the function of the corresponding interface in the software to be evaluated, and the business added value numerical representation: the degree to which the function of the corresponding interface improves the business value.

[0126] In a possible embodiment, after calculating the energy efficiency evaluation value of each interface based on each key indicator value and access volume corresponding to each interface, the device further includes a processing module 503, and the processing module 503 is used to:

[0127] The energy efficiency evaluation values ​​of each interface are arranged and displayed to obtain the energy efficiency evaluation results of the software to be evaluated.

[0128] In a possible embodiment, after calculating the energy efficiency evaluation value of each interface based on each key indicator value and access volume corresponding to each interface, the processing module 503 is further used to:

[0129] From each interface, select the interfaces to be improved whose energy efficiency evaluation values ​​meet the improvement conditions, and notify the developers that the interfaces to be improved need to be improved.

[0130] Based on the above embodiments, see Figure 6 Shown is a schematic diagram of the structure of an electronic device in an embodiment of the present application.

[0131] An embodiment of the present application provides an electronic device, which may include a processor 610 (Center Processing Unit, CPU), a memory 620, an input device 630 and an output device 640, etc. The input device 630 may include a keyboard, a mouse, a touch screen, etc., and the output device 640 may include a display device, such as a liquid crystal display (Liquid Crystal Display, LCD), a cathode ray tube (Cathode Ray Tube, CRT), etc.

[0132] The memory 620 may include a read-only memory (ROM) and a random access memory (RAM), and provides the processor 610 with program instructions and data stored in the memory 620. In the embodiment of the present application, the memory 620 may be used to store the program of any software development energy efficiency evaluation method in the embodiment of the present application.

[0133] The processor 610 calls the program instructions stored in the memory 620, and the processor 610 is used to execute any software development energy efficiency evaluation method in the embodiments of the present application according to the obtained program instructions.

[0134] Based on the above embodiments, in an embodiment of the present application, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the software development energy efficiency evaluation method in any of the above method embodiments is implemented.

[0135] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0136] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0137] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0138] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0139] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for evaluating software development energy efficiency, characterized in that: include: Collect access data of each interface of the software to be evaluated, and calculate the access volume of each interface; Based on the key indicator values ​​corresponding to each of the interfaces and the access volume, the energy efficiency evaluation value of each of the interfaces is calculated, wherein the key indicator values ​​include: an access volume weight value and a functional value value of the corresponding interface, and the functional value value is related to the business requirements and functional characteristics of the corresponding interface.

2. The method according to claim 1, characterized in that The access data includes: user's access request data and / or user's behavior browsing data.

3. The method according to claim 2, characterized in that The collecting of access data of each interface of the software to be evaluated includes: Using a probe to obtain the access request data; and / or, Integrate a software development kit SDK to obtain the access request data; and / or, Integrate JavaScript script to collect the above-mentioned browsing behavior data.

4. The method according to claim 1, characterized in that The functional value values ​​include but are not limited to: importance value value and business added value value; The importance value numerical representation is: the importance of the function of the corresponding interface in the software to be evaluated, and the business added value numerical representation is: the degree to which the function of the corresponding interface improves the business value.

5. The method according to claim 1, characterized in that After calculating the energy efficiency evaluation value of each interface based on each key indicator value corresponding to each interface and the access volume, the method further includes: The energy efficiency evaluation values ​​of the respective interfaces are arranged and displayed to obtain the energy efficiency evaluation result of the software to be evaluated.

6. The method according to claim 1, characterized in that After calculating the energy efficiency evaluation value of each interface based on each key indicator value corresponding to each interface and the access volume, the method further includes: From the interfaces, interfaces to be improved whose energy efficiency evaluation values ​​meet the improvement conditions are screened out, and the developer is notified that the interfaces to be improved need to be improved.

7. A software development energy efficiency evaluation device, characterized in that: include: The collection module is used to collect access data of each interface of the software to be evaluated and calculate the access volume of each interface; An evaluation module is used to calculate the energy efficiency evaluation value of each interface based on the key indicator values ​​corresponding to each interface and the access volume, wherein the key indicator values ​​include: an access volume weight value and each functional value value of the corresponding interface, and the each functional value value is related to the business requirements and functional characteristics of the corresponding interface.

8. The device according to claim 7, characterized in that The functional value values ​​include but are not limited to: importance value value and business added value value; The importance value numerical representation is: the importance of the function of the corresponding interface in the software to be evaluated, and the business added value numerical representation is: the degree to which the function of the corresponding interface improves the business value.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer-readable 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 6 are implemented.

Images