Software quality measurement method and device, electronic equipment and storage medium

Abstract

The invention provides a software quality measurement method and apparatus, an electronic device and a storage medium. The method comprises the steps of obtaining a measurement demand index of a user for the quality of target software; determining a software measurement parameter for measuring the quality of the target software according to the measurement demand index; according to the software measurement parameter, determining a tool deployment relationship for measuring the target software, the tool deployment relationship being used for indicating an association relationship between a tool for realizing the software measurement parameter for measuring the target software and a measurement demand index; and capturing target data based on the tool deployment relationship and the software measurement parameters, and determining a software quality measurement result of the target software according to the target data. According to the method and the device, the measurement requirement of the target software can be butted with different software management tools, so that the software measurement is prevented from excessively depending on a certain tool, and the data acquisition flexibility and the data acquisition efficiency are improved.

Description

Technical Field

[0001] The present application relates to the technical field of software testing, and more specifically, to a software quality measurement method, device, electronic device and storage medium. Background Art

[0002] With the rapid development of smart cockpits and smart driving, the proportion of software in automobile research and development has increased sharply. With the development of the new four modernizations of automobiles, vehicle-mounted software has become more complex. How to evaluate various aspects of software projects is crucial. At present, most of the measurement items in software indicator measurement are based on the measurement of the code itself, such as cyclomatic complexity, compiler warnings, etc., and they can only be measured after the software coding is completed. The quality control of the software development process is relatively passive and lagging. In the prior art, when performing software measurement, many software indicator data sources are mainly scattered in various software management tools. The acquisition of data during measurement is complicated and inefficient. Therefore, how to avoid the efficiency of data acquisition caused by excessive coupling with a certain software management tool during software measurement has become an urgent problem to be solved. Summary of the invention

[0003] In view of this, the embodiments of the present application propose a software quality measurement method, device, electronic device and storage medium to improve the above-mentioned problems.

[0004] According to a first aspect of an embodiment of the present application, a method for measuring software quality is provided, the method comprising: obtaining a user's measurement requirement indicator for the quality of a target software; determining software measurement parameters for measuring the quality of the target software based on the measurement requirement indicator, wherein the software measurement parameters include target parameters for measuring the target software under different indicators; determining a tool deployment relationship for measuring the target software based on the software measurement parameters, wherein the tool deployment relationship is used to indicate an association relationship between a tool for implementing the software measurement parameters for measuring the target software and the measurement requirement indicator; capturing target data based on the tool deployment relationship and the software measurement parameters, and determining a software quality measurement result of the target software based on the target data.

[0005] According to a second aspect of an embodiment of the present application, a software quality measurement device is provided, the device comprising: a measurement requirement acquisition module, used to obtain a user's measurement requirement indicator for the quality of a target software; a software measurement target determination module, used to determine software measurement parameters for measuring the target software according to the measurement requirement indicator, wherein the software measurement parameters include target parameters for measuring the target software under different indicators; a tool deployment relationship determination module, used to determine a tool deployment relationship for measuring the target software according to the software measurement parameters, wherein the tool deployment relationship is used to indicate an association relationship between a tool for implementing the software measurement parameters for measuring the target software and the measurement requirement indicator; a software measurement result determination module, used to capture target data based on the tool deployment relationship and the software measurement parameters, and determine a software quality measurement result of the target software according to the target data.

[0006] According to a third aspect of an embodiment of the present application, there is provided an electronic device, comprising: a processor; a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the software quality measurement method as described above is implemented.

[0007] According to a fourth aspect of an embodiment of the present application, a computer-readable storage medium is provided, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor, the software quality measurement method as described above is implemented.

[0008] In the scheme of the present application, the user's measurement requirement indicators for the quality of the target software are first determined, so that the software measurement parameters for measuring the quality of the target software can be determined according to the measurement requirement indicators, and then the tool deployment relationship for measuring the target software can be determined according to the software measurement parameters, and finally the target data can be captured according to the relationship between the tool for implementing the software measurement parameters for measuring the target software and the measurement requirement indicators indicated in the tool deployment relationship, and finally the software quality measurement results for software measurement of the quality of the target software can be obtained according to the target data. The scheme of the present application can realize the docking of the measurement requirements of the target software with different software management tools, avoid excessive reliance on a certain tool when measuring the software, improve the flexibility and efficiency of obtaining data, and can adaptively adjust the software measurement parameters and tool deployment relationships of the software by adjusting the measurement requirement indicators of the input target software, so that the software quality measurement results can be adaptively counted and generated, and the measurement efficiency can be improved.

[0009] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0011] Figure 1 A software quality measurement interface system is provided according to an embodiment of the present application.

[0012] Figure 2 It is a flowchart of a method for measuring software quality according to an embodiment of the present application.

[0013] Figure 3 It is a flowchart of a method for measuring software quality according to another embodiment of the present application.

[0014] Figure 4 It is a flowchart of a method for measuring software quality according to another embodiment of the present application.

[0015] Figure 5 It is a flowchart of a method for measuring software quality according to another embodiment of the present application.

[0016] Figure 6 It is a schematic diagram of the working principle of a method for measuring software quality according to an embodiment of the present application.

[0017] Figure 7 It is a flowchart of a method for measuring software quality according to yet another embodiment of the present application.

[0018] Figure 8 It is a block diagram of a software quality measurement device according to an embodiment of the present application.

[0019] Fig. 9 It is a hardware structure diagram of an electronic device according to an embodiment of the present application.

[0020] The above-mentioned drawings have shown clear embodiments of the present invention, which will be described in more detail hereinafter. These drawings and textual descriptions are not intended to limit the scope of the present invention in any way, but to illustrate the concept of the present invention to computer technicians in this field through specific embodiments. DETAILED DESCRIPTION

[0021] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more comprehensive and complete and fully convey the concept of the example embodiments to those skilled in the art.

[0022] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0023] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, devices, steps, etc. can be adopted. In other cases, known methods, devices, realizations or operations are not shown or described in detail to avoid blurring the various aspects of the present application.

[0024] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices. The flowcharts shown in the accompanying drawings are merely exemplary and do not necessarily include all the contents and operations / steps, nor do they necessarily have to be executed in the order described. For example, some operations / steps may be further decomposed, while some operations / steps may be combined or partially combined, so the actual execution order may change according to the actual situation.

[0025] Figure 1 is a software quality measurement interface system shown in an embodiment of the present application, such as Figure 1As shown, the software quality measurement interface system 100 includes an indicator system module 110, a deployment definition module 120 and an interface software module 130, wherein the indicator system module 110 determines the target parameters for measuring the target software under different indicators according to the project software quality requirements input by the user, so as to determine the software measurement parameters for measuring the target software, and then the deployment definition module 120 determines the tool deployment relationship for measuring the quality of the target software according to the software measurement parameters, and finally the software interface software 130 determines the target tool according to the tool deployment relationship, so as to capture the target data through the target tool based on the tool deployment relationship and the software measurement parameters, and determine the software quality measurement result of the target software according to the target data, so that the software measurement interface system can be decoupled from the tool for measuring the software, and the indicator data can be managed in the same way based on the software measurement interface system, so as to avoid the low flexibility of measuring the quality of the software due to over-reliance on a certain tool, and improve the efficiency of measuring the software.

[0026] See also Figure 2 , Figure 2 The software quality measurement method provided by an embodiment of the present application is shown. In a specific embodiment, the software quality measurement method can be applied to Figure 8 The software quality measurement device 600 and the electronic device 700 equipped with the software quality measurement device 600 are shown in FIG. Fig. 9 ). The specific process of this embodiment will be described below. Of course, it can be understood that the method can be executed by a vehicle terminal with computing and processing capabilities. Figure 2 The process shown is described in detail, and the software quality measurement method may specifically include the following steps:

[0027] Step 210: Obtain the user's measurement requirement indicators for the quality of the target software.

[0028] As a method, users can input the requirement data that needs to be measured for a certain project or a certain type of software according to actual needs. After receiving the requirement data input by the user, the user's measurement requirement indicators for the target software are determined according to the requirement data. The measurement requirement indicators of the target software can be indicators for users to monitor or measure various documents and programs of the target software or the development activities of the target software according to the project. In this way, the technical process of product development of the target software can be understood based on the software quality measurement results of the target software, and the product can be managed, monitored and improved in a timely manner. Measurement refers to a quantitative measurement of the degree of a given attribute of a system, component or process.

[0029] Step 220: Determine software measurement parameters for measuring the quality of the target software according to the measurement requirement indicators, wherein the software measurement parameters include target parameters for measuring the target software under different indicators.

[0030] As a method, after obtaining the user's measurement requirement indicators for the target software, the measurement requirement indicators can be matched with the indicator library, so as to determine the indicators matching the measurement requirement indicators in the indicator library, so as to determine the software measurement parameters for measuring the quality of the target software. Optionally, the measurement requirement indicators can be identified to determine the target indicator type corresponding to the measurement requirement indicators of the target software, and then the target parameters corresponding to the target indicator type can be determined from the indicator library to determine the software measurement parameters.

[0031] Step 230, determining a tool deployment relationship for measuring the target software based on the software measurement parameters, wherein the tool deployment relationship is used to indicate an association relationship between a tool for implementing the software measurement parameters for measuring the target software and the measurement requirement indicator.

[0032] As a way, after determining the measurement requirement indicators of the target software, in order to facilitate the unified management of all tools used to capture data, the data types and types of data required to be obtained in the software measurement parameters of the target software, that is, the measurement requirement indicators of the target software, can be used to determine the tools used to obtain the corresponding data types and types of data, such as project management tools, problem management tools, software design tools, software testing tools, requirements management tools and other software management tools, so as to establish the association relationship between different data and corresponding tools, so as to specify the tool deployment relationship used to measure the target software.

[0033] Optionally, the association relationship may be expressed in a table, such as a mapping table, or may be marked in a corresponding tool to indicate an identification mark of the associated data.

[0034] Step 240: Capture target data based on the tool deployment relationship and the software metric parameters, and determine the software quality metric result of the target software according to the target data.

[0035] As a method, after determining the tool deployment relationship for measuring the target software, the target tool can be selected in the tool library according to the tool related to the measurement requirement indicators in the tool deployment relationship in the software measurement interface system, and the access address of the target tool can be determined. In this way, the data corresponding to the measurement requirement indicators under different indicators can be captured through the access address of the target tool according to the software measurement parameters and the tool deployment relationship in the software measurement interface system, so as to obtain the target data.

[0036] Optionally, since the data captured by the target tool is raw data, users or developers cannot intuitively know the data corresponding to the measurement requirements. Therefore, after capturing the target data, the target data can be processed according to the measurement requirements, and finally the processed result is used as the software quality measurement result.

[0037] As another way, in order to finally display the results of measuring the quality of the target software, the display form of the software quality measurement results and the tool corresponding to the display form can be specified in advance in the tool deployment relationship, and then, after processing the target data, it is displayed according to the display form in the tool deployment relationship and through the display tool corresponding to the display form. Optionally, the display form can be a table, a bar chart, a line chart, or a pie ratio chart, etc.

[0038] In an embodiment of the present application, the user's measurement requirement index for the quality of the target software is first determined, so that the software measurement parameters for measuring the quality of the target software can be determined according to the measurement requirement index, and then the tool deployment relationship for measuring the target software can be determined according to the software measurement parameters, and finally the target data can be captured according to the relationship between the tool for implementing the software measurement parameters for measuring the target software and the measurement requirement index indicated in the tool deployment relationship, and finally the software quality measurement result for software measurement of the quality of the target software can be obtained according to the target data. The scheme of the present application can realize the docking of the measurement requirements of the target software with different software management tools, avoid excessive dependence on a certain tool when measuring the software, improve the flexibility and efficiency of obtaining data, and can adaptively adjust the software measurement parameters and tool deployment relationship of the software by adjusting the measurement requirement index of the input target software, so as to adaptively count and generate software quality measurement results and improve measurement efficiency.

[0039] See also Figure 3 , Figure 3 The following is a method for measuring software quality provided by an embodiment of the present application. Figure 3 The process shown is described in detail, the software measurement parameters include customer measurement target parameters, software technical target parameters and key process target parameters, and the software quality measurement method can specifically include the following steps:

[0040] Step 310: Obtain the user's required metrics for the quality of the target software.

[0041] Step 320: determine the software type of the target software according to the measurement requirement index, and determine the software technical index according to the software type.

[0042] As a method, since the solution of the present application can be used to solve software measurement problems of different software types, during the actual application of the project, it is necessary to determine the measurement indicators of the target software based on the project software measurement requirement indicators and the software type. Furthermore, when determining the software measurement goals for measuring the target software based on the measurement requirement indicators of the target software, the software type of the target software can be determined first based on the measurement requirement indicators. Furthermore, the software technical indicators of the target software can be determined based on the software type of the target software, and can provide a reference for subsequent project software of the same type when formulating target values.

[0043] Optionally, the software type of the target software can be software used to control the vehicle or implement certain functions on the vehicle computer, such as vehicle control software, vehicle computer software, intelligent driving software, and networked cloud software, etc.; it can also be a software component type, such as underlying software, application software, and intermediate components, etc. The software type of the target software that needs to be measured can be determined based on the corresponding software identifier in the measurement requirement indicator input by the user.

[0044] Optionally, corresponding software technical indicators may be set in advance for different types of software to obtain a mapping table between different types of software and their corresponding software technical indicators. After determining the software type of the target software, the software technical indicators corresponding to the target software may be determined according to the mapping table.

[0045] Step 330: Determine the client layer metric indicators of the target software and the key process indicators of the target software according to the metric requirement indicators.

[0046] As a way, in order to ensure the accuracy of software measurement for the target software, the user can input the specific key processes that need to be measured for the target software and the customer layer measurement considerations entered by the user or engineer, so as to determine the customer layer measurement indicators and key process indicators of the target software according to the corresponding input customer layer measurement requirement indicators and key process measurement requirement indicators in the measurement requirements.

[0047] Step 340, based on the software technical indicators, the customer layer measurement indicators and the key process indicators, determine the customer measurement target parameters, the software technical target parameters and the key process target parameters.

[0048] As a method, since the measurement types corresponding to software technical indicators, customer-level measurement indicators and key process indicators and the corresponding target values ​​under different indicators are different, therefore, after determining the software technical indicators, customer-level measurement indicators and key process indicators, indicators can be selected for the software technical indicators respectively, and the first target value corresponding to the software technical indicators can be determined to obtain the software technical target parameters; indicators can be selected for the customer-level measurement indicators, and the second target value corresponding to the customer-level measurement indicators can be determined to obtain the customer-level measurement target parameters; and indicators can be selected for the key process indicators, and the third target value corresponding to the key process indicators can be determined to obtain the key process target parameters.

[0049] Step 350, determining a tool deployment relationship for measuring the target software based on the software measurement parameters, wherein the tool deployment relationship is used to indicate an association relationship between a tool for implementing the software measurement parameters for measuring the target software and the measurement requirement indicator.

[0050] Step 360: Capture target data based on the tool deployment relationship and the software metric parameters, and determine the software quality metric result of the target software according to the target data.

[0051] Among them, the specific step descriptions of step 310 and step 350-step 360 can refer to step 110 and step 130-step 140, which will not be repeated here.

[0052] In this embodiment, software technical indicators for software measurement of the quality of the target software are determined based on the software type of the target software, and customer-layer measurement indicators and key process indicators are determined based on measurement requirements. Finally, software indicator selection is performed to obtain customer measurement target parameters, software technical target parameters and key process target parameters, so as to formulate software measurement targets of target parameters for measuring the quality of the target software under different indicators. This is an indicator system suitable for different software types and software component types, and supports target definition based on project software measurement requirement indicators, project development models and other features, thereby ensuring the richness of software measurement targets.

[0053] See also Figure 4 , Figure 4 The following is a method for measuring software quality provided by an embodiment of the present application. Figure 4 The process shown is described in detail, and the software quality measurement method may specifically include the following steps:

[0054] Step 410: Obtain the user's measurement requirement indicators for the quality of the target software.

[0055] Step 420: Determine software measurement parameters for measuring the quality of the target software according to the measurement requirement indicators, wherein the software measurement parameters include target parameters for measuring the target software under different indicators.

[0056] Step 430: determining a candidate tool from a plurality of tools according to the software metric parameters.

[0057] As a way, in order to facilitate the unified management of different tools for capturing data, and to be able to capture the required data based on different measurement requirement indicators corresponding to different software, the candidate tools required to complete the software measurement goals can be determined from the multiple tools maintained by the software measurement interface system according to the software measurement parameters of the target software, so as to facilitate the subsequent formulation of tool deployment definitions based on the candidate tools, and then the measurement requirements for the target software can be realized based on the tool deployment definitions and software measurement parameters.

[0058] Step 440: Acquire tool characteristics of the candidate tool, and determine data acquisition rules corresponding to the candidate tool according to the tool characteristics.

[0059] As a method, since different tools have different corresponding capture methods, data types and data capture cycles when capturing data, in order to facilitate the subsequent use of candidate tools to capture the data required in the measurement requirements, the tool characteristics corresponding to each candidate tool can be determined first, and then the corresponding data acquisition rules can be formulated for each candidate tool when capturing data according to the tool characteristics corresponding to each candidate tool. Optionally, the data acquisition rules may include the data type of the acquired data, the method of acquiring data and the cycle of acquiring data.

[0060] In some embodiments, after step 440, the method further includes: determining the data type of the data captured by the candidate tool based on the tool characteristics and the software measurement parameters; determining the target value corresponding to the data type defined in the software measurement parameters, and determining the target comparison rule for the data type based on the target value; and determining the tool deployment relationship based on the target comparison rule.

[0061] As a way, when measuring the quality of the target software, since the measurement target values ​​corresponding to the measurement indicators at different levels are different, it is necessary to determine the measurement target values ​​corresponding to the captured data corresponding to different candidate tools. Different data types have different corresponding measurement target values. For example, the vehicle's power consumption or fuel consumption has different corresponding measurement target values ​​from the vehicle's control deviation. Therefore, the data type corresponding to the data captured by the candidate tool can be determined based on the software measurement goals and the tool characteristics corresponding to each of the multiple tools.

[0062] Optionally, different target values ​​corresponding to different data types may be set in advance, so that after the data type of the data captured by the candidate tool is determined, the target value corresponding to the data type defined in the software measurement target of the target software may be determined based on the data type of the data captured by the candidate tool. Optionally, the data type of the data to be acquired and the target value corresponding to the data type are set in the software measurement target of the target software, and then, after the data type of the data captured by the candidate tool is determined, the target value corresponding to the data captured by the candidate tool may be determined based on the correspondence between the data type and the target value set in the software measurement target.

[0063] Optionally, when measuring the target software, it is necessary to determine whether the progress or quality of the target software meets the requirements of users or engineers, and then, it is necessary to compare the captured data with the target value set corresponding to the data to determine the measurement result of the target software. For example, when determining the deviation rate of vehicle control, it is necessary to compare the captured data with the deviation threshold to determine whether the deviation of vehicle control is within a controllable range. Therefore, the corresponding comparison rules can be set according to the target value and the corresponding data type, so that after determining the target comparison rules corresponding to the candidate tool, the target comparison rules can also be used as tool deployment relationships.

[0064] Step 450: Determine the tool deployment relationship according to the data acquisition rule.

[0065] As a way, after determining the data acquisition rules, in order to ensure that subsequent tools can capture the corresponding data according to the data acquisition rules, the data acquisition rules can be used as a definition in the tool deployment relationship, so that when the software measurement interface system measures the target software according to the tool deployment relationship and software measurement parameters, the required data can be captured according to the data acquisition rules.

[0066] In some embodiments, after step 450, the method further includes: determining, based on the data type and the software metric parameter, an assessment exemption rule corresponding to the data captured by the candidate tool; and updating the tool deployment relationship according to the assessment exemption rule.

[0067] As a way, in order to avoid excessively complex data that leads to low efficiency and accuracy in software measurement of the target software, users or engineers can select the data to be filtered and its filtering rules according to actual needs, and then determine the corresponding filtering rules when determining the software measurement parameters of the target software according to the measurement requirement indicators of the target software. In this way, when determining the tool deployment relationship, the assessment exemption rules when the candidate tool captures the data can be determined based on the data type of the data captured by the candidate tool and the filtering rules corresponding to the data type, and the tool deployment relationship can be updated according to the assessment exemption rules to make the data captured later according to the tool deployment relationship more accurate.

[0068] Step 460: Capture target data based on the tool deployment relationship and the software metric parameters, and determine the software quality metric result of the target software according to the target data.

[0069] Among them, the specific step descriptions of step 410-step 420 and step 460 can refer to step 110-step 120 and step 140, which will not be repeated here.

[0070] In this embodiment, a candidate tool for measuring the target software is determined according to the software measurement parameters, and then the data acquisition rule corresponding to the candidate tool is determined according to the tool characteristics of the candidate tool, and the data type of the data captured by the candidate tool is determined according to the tool characteristics of the candidate tool and the software measurement parameters, so that the target comparison rule of the data type can be determined according to the target value corresponding to the data type defined in the software measurement parameters, and the tool deployment relationship can be determined according to the target comparison rule and / or the data acquisition rule, so that by continuously improving and updating the indicator system, the calculation method and data source tools can be adjusted at any time to obtain the tool deployment relationship, so that the tool deployment definition has strong scalability, avoids excessive dependence on a certain tool when performing software measurement, and improves the flexibility and efficiency of data acquisition.

[0071] See also Figure 5 , Figure 5 The following is a method for measuring software quality provided by an embodiment of the present application. Figure 5 The process shown is described in detail, and the software quality measurement method may specifically include the following steps:

[0072] Step 510: Obtain the user's required metrics for the quality of the target software.

[0073] Step 520: Determine software measurement parameters for measuring the quality of the target software according to the measurement requirement indicators, wherein the software measurement parameters include target parameters for measuring the target software under different indicators.

[0074] Step 530, determining a tool deployment relationship for measuring the target software based on the software measurement parameters, wherein the tool deployment relationship is used to indicate an association relationship between a tool for implementing the software measurement parameters for measuring the target software and the measurement requirement indicator.

[0075] The specific step descriptions of step 510 and step 530 can be found in step 110 to step 130, which will not be repeated here.

[0076] Step 540: determine a target tool according to the tool deployment definition, and determine a target database according to the tool deployment relationship and the software metric parameters.

[0077] As a method, after determining the tool deployment relationship, the target tool for achieving the measurement requirement can be determined from the multiple tools managed according to the association relationship between the tool and the measurement requirement indicator in the tool deployment relationship. Optionally, the tool deployment relationship includes a tool identifier corresponding to the target tool, and then the target tool can be determined from the multiple tools according to the tool identifier corresponding to the target tool in the tool deployment relationship.

[0078] Optionally, in order to quickly and accurately capture data for measuring the target software, the database where the captured data is located can be determined based on the target tool identifier in the tool deployment relationship and the data type of the data required to measure the target software in the software measurement parameters, and the database can be determined as the target database. Optionally, the parameters required for capturing data can also be determined based on the tool deployment relationship, such as indicator ID, indicator type, indicator name, indicator definition, application type (target value / monitoring value), weight, project, software maturity (software major version), data source (target system), year, start time, end time, and software type, so that the corresponding data can be captured based on the parameters.

[0079] Step 550, determining the access address of the target tool, the first access port of the target tool, and the second access port of the target database.

[0080] As a method, after determining the target tool for crawling data and the corresponding target database, the access address of the target tool, the first access port of the target tool and the second access port of the target database can be determined, and then the data can be uploaded according to the access address of the target tool, so that measurement analysis can be performed based on the uploaded data.

[0081] Optionally, an access link can be established between the first access port and the second access port, so that the target tool can crawl data in the target database according to the access link. Optionally, the login account and login password of the target tool can also be determined to improve the efficiency of crawling data.

[0082] Step 560: Capture reference data in the target database through the target tool according to the access address, the first access port, the second access port and the data acquisition rule.

[0083] As a method, after determining the access address and first access port of the target tool and the second access port of the target database, in order to facilitate the software measurement interface system to quickly and accurately execute the process of capturing data for the measurement requirements of the target software, the access address, the first access port, the second access port and the fields corresponding to the data acquisition rules can be first mapped to the interface software module of the software measurement interface system, so as to facilitate the interface software module to establish an access link based on the first access port and the second access port in the mapped fields, and then the target tool captures reference data in the target database based on the access link and the data acquisition rules, and the data processing unit in the software measurement interface system screens and calculates the reference data according to the access address of the target tool.

[0084] Step 570: Determine target data in the reference data based on the assessment exemption rule.

[0085] As a method, after the reference data is captured, since the reference data is data that has not been filtered, the reference data can be filtered according to the assessment exemption rules in the tool deployment definition to determine the target data that meets the assessment exemption rules. Optionally, the assessment exemption rules can be that the data of a certain time period is not assessed, and then, when the data is captured, the data corresponding to the time period is filtered out to determine the target data.

[0086] Step 580: Determine the software measurement result of the target software according to the target data.

[0087] As a method, since the target data is determined as raw data, that is, the data obtained is data corresponding to different time periods or different ranges, in order to perform software measurement on the target software, it is necessary to calculate and compare the target software to obtain the software measurement result. Optionally, the calculation rules and comparison rules of the measurement results can be determined when formulating the tool deployment definition according to the measurement requirements of the target software. Finally, after obtaining the target data, the target data is processed according to the calculation rules and comparison rules in the tool deployment definition to obtain the software measurement result.

[0088] In some embodiments, step 580 includes: determining the indicator calculation rule of the target data according to the tool deployment relationship; performing metric calculation on the target data according to the indicator calculation rule and the software metric parameter to obtain the software quality metric result of the target software.

[0089] As a method, corresponding indicator calculation rules can be set in advance for different types of data. After determining the data type of the data captured by the candidate tool, the indicator calculation rules corresponding to the data type are determined. For example, the fuel consumption per kilometer can be determined based on the ratio of the vehicle's mileage and total fuel consumption in a week.

[0090] Optionally, after determining the indicator calculation rules corresponding to the data type, the target data is measured and calculated using the indicator calculation rules and the data required to be calculated in the software measurement target, so as to obtain the measurement result.

[0091] In this embodiment, the target database is first determined based on the tool deployment relationship and the software measurement parameters, so that after the access address and the first access port of the target tool and the second data port of the target database are determined, the reference data can be directly captured in the target database through the target tool according to the access address and the first access port of the target tool, the second data port of the target database and the data acquisition rules in the tool deployment definition, and then the reference data is filtered based on the assessment exemption rules in the tool deployment relationship to obtain the target data, and finally the target data is measured and calculated according to the indicator calculation rules of the target data determined by the tool deployment relationship to obtain the measurement results. This embodiment can adaptively count and generate measurement results in a rapidly iterating software integration version, thereby improving measurement efficiency.

[0092] Figure 6 FIG. 1 is a schematic diagram showing the working principle of a method for measuring software quality according to an embodiment of the present application. Figure 6 As shown, the method is executed by a software measurement interface system, which includes an indicator system module, a deployment definition module and an interface software module, wherein the indicator system module selects the software type according to the project software measurement requirements input by the user, so as to determine the software type of the target software that needs to be measured, and then determines the software technical indicators, key process indicators and customer-level measurement indicators of the target software according to the project software measurement requirements input by the user, and then selects software indicators for the target software to obtain customer measurement goals, software technical goals and key process goals, and finally selects software goals and formulates indicator goal definitions for the target software.

[0093] Then, the deployment definition module performs indicator calculation definition, data acquisition definition, target comparison definition, assessment exemption definition and display icon definition according to the indicator target definition output by the indicator system module, and then obtains the indicator deployment definition for software measurement of the target software.

[0094] Finally, the interface software module inputs the indicator deployment definition output by the deployment definition module into the management unit, so that the management unit can forward the indicator deployment definition to the data unit, so that the data unit can determine the tool for grabbing the corresponding data and the database where the data is located according to the data acquisition definition in the indicator deployment definition. Then, after the tool grabs the required data from the database, it uploads it to the data unit, which is forwarded to the management unit by the data unit, so that the management unit can determine the software measurement results of the target software according to the indicator calculation definition, target comparison definition and assessment exemption definition in the indicator deployment definition, and then send the software measurement results to the display unit, which displays them according to the display icon definition in the indicator deployment definition and displays them on the indicator display carrier.

[0095] Figure 7 is a flowchart of a method for measuring software quality according to an embodiment of the present application, such as Figure 7 As shown, the project software measurement requirement indicators and software types input by the user are obtained, and then the software measurement interface system determines the measurement indicators of the target software according to the software type and the project software measurement requirements, so as to formulate the software measurement goals of the target software, and then formulate the tool deployment relationship for the target software according to the formulated software measurement goals, and determine whether the required data in the software measurement goals meet the assessment exemption rules according to the assessment exemption rules in the tool deployment relationship, that is, determine whether the measurement results of the required data need to be exempted. If it is determined that the assessment exemption rules are met, the tool deployment relationship is updated according to the assessment exemption rules, and the interface software module is updated according to the updated tool deployment relationship, so as to continuously improve and update the indicator system, so as to realize software measurement of different software development tools or software management tools, and finally generate a measurement report on the indicator display carrier according to the measurement results output by the software measurement interface system.

[0096] Figure 8 is a block diagram of a software quality measurement device according to an embodiment of the present application, such as Figure 8 As shown, the software quality measurement device 600 includes a measurement requirement acquisition module 610 , a software measurement target determination module 620 , a tool deployment relationship determination module 630 and a software measurement result determination module 640 .

[0097] A measurement requirement acquisition module 610 is used to obtain the user's measurement requirement indicators for the quality of the target software; a software measurement target determination module 620 is used to determine the software measurement parameters for measuring the quality of the target software based on the measurement requirement indicators, wherein the software measurement parameters include target parameters for measuring the target software under different indicators; a tool deployment relationship determination module 630 is used to determine the software measurement parameters for measuring the quality of the target software based on the measurement requirement indicators, wherein the software measurement parameters include target parameters for measuring the target software under different indicators; a software measurement result determination module 640 is used to capture target data based on the tool deployment relationship and the software measurement parameters, and determine the software quality measurement results of the target software based on the target data.

[0098] In some embodiments, the software measurement parameters include customer measurement target parameters, software technical target parameters and key process target parameters, and the software measurement target determination module 620 includes: a software technical indicator determination unit, which is used to determine the software type of the target software according to the measurement requirement indicators, and determine the software technical indicators according to the software type; a key process indicator determination unit, which is used to determine the customer layer measurement indicators of the target software and the key process indicators of the target software according to the measurement requirement indicators; an indicator selection unit, which is used to determine the customer measurement target parameters, the software technical target parameters and the key process target parameters based on the software technical indicators, the customer layer measurement indicators and the key process indicators.

[0099] In some embodiments, the tool deployment relationship determination module 630 includes: a candidate tool determination unit, used to determine a candidate tool among multiple tools based on the software measurement parameters; a data acquisition rule determination unit, used to obtain tool characteristics of the candidate tool, and determine the data acquisition rule corresponding to the candidate tool based on the tool characteristics; a tool deployment relationship first determination unit, used to determine the tool deployment relationship based on the data acquisition rule.

[0100] In some embodiments, the tool deployment relationship determination module 630 also includes: a data type determination unit, used to determine the data type of the data captured by the candidate tool based on the tool characteristics and the software measurement parameters; a target comparison rule determination unit, used to determine the target value corresponding to the data type defined in the software measurement parameters, and determine the target comparison rule of the data type based on the target value; a tool deployment relationship second determination unit, used to determine the tool deployment relationship based on the target comparison rule.

[0101] In other embodiments, the tool deployment relationship determination module 630 also includes: determining the assessment exemption rules corresponding to the candidate tool captured data based on the data type and the software measurement parameters; and an updating unit for updating the tool deployment relationship according to the assessment exemption rules.

[0102] In some embodiments, the software measurement result determination module 640 includes: a target database determination unit, used to determine the target tool according to the tool deployment relationship, and determine the target database according to the tool deployment relationship and the software measurement parameters; an access port determination unit, used to determine the access address of the target tool, the first access port of the target tool and the second access port of the target database; a data capture unit, used to capture reference data in the target database through the target tool according to the access address, the first access port, the second access port and the data acquisition rule; a target data determination unit, used to determine the target data in the reference data based on the assessment exemption rule.

[0103] In some embodiments, the software measurement result determination module 640 also includes: an indicator calculation rule determination unit, which is used to determine the indicator calculation rule of the target data according to the tool deployment relationship; a software measurement result determination unit, which is used to perform measurement calculation on the target data according to the indicator calculation rule and the software measurement parameters to obtain the software quality measurement result of the target software.

[0104] According to one aspect of the embodiments of the present application, an electronic device is also provided, such as Fig. 9 As shown, the electronic device 700 includes a processor 710 and one or more memories 720. The one or more memories 720 are used to store program instructions executed by the processor 710. When the processor 710 executes the program instructions, the above-mentioned software quality measurement method is implemented.

[0105] Furthermore, the processor 710 may include one or more processing cores. The processor 710 runs or executes instructions, programs, code sets or instruction sets stored in the memory 720, and calls data stored in the memory 720. Optionally, the processor 710 may be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), and programmable logic array (PLA). The processor 710 may integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing display content; and the modem is used to process wireless communications. It is understandable that the above-mentioned modem may not be integrated into the processor, but may be implemented separately through a communication chip.

[0106] According to one aspect of the present application, the present application further provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiments; or may exist independently without being assembled into the electronic device. The above computer-readable storage medium carries computer-readable instructions, and when the computer-readable storage instructions are executed by a processor, the method in any of the above embodiments is implemented.

[0107] It should be noted that the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, - but not limited to - an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by an instruction execution system, device or device or used in combination with it. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0108] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0109] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0110] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary technical means in the art that are not disclosed in the present application.

[0111] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A method for measuring software quality, characterized in that: The method comprises: Obtain the user's measurement requirements for the quality of the target software; Determining software measurement parameters for measuring the quality of the target software according to the measurement requirement indicators, wherein the software measurement parameters include target parameters for measuring the target software under different indicators; Determining software measurement parameters for measuring the quality of the target software according to the measurement requirement indicators, wherein the software measurement parameters include target parameters for measuring the target software under different indicators; Target data is captured based on the tool deployment relationship and the software metric parameters, and a software quality metric result of the target software is determined according to the target data.

2. The method according to claim 1, characterized in that The software measurement parameters include customer measurement target parameters, software technical target parameters and key process target parameters. The software measurement parameters for measuring the quality of the target software determined according to the measurement requirement indicators include: Determining the software type of the target software according to the measurement requirement indicator, and determining the software technical indicator according to the software type; Determine the client layer metric of the target software and the key process metric of the target software according to the metric requirement indicator; Based on the software technical indicators, the customer layer measurement indicators and the key process indicators, the customer measurement target parameters, the software technical target parameters and the key process target parameters are determined.

3. The method according to claim 1, characterized in that The step of determining a tool deployment relationship for measuring the target software according to the software measurement parameters includes: determining a candidate tool from among a plurality of tools according to the software metric parameters; Acquire tool characteristics of the candidate tool, and determine data acquisition rules corresponding to the candidate tool according to the tool characteristics; The tool deployment relationship is determined according to the data acquisition rule.

4. The method according to claim 3, characterized in that After obtaining the tool characteristics of the candidate tool, the method further includes: Determining the data type of the data captured by the candidate tool according to the tool characteristics and the software metric parameters; Determine a target value corresponding to the data type defined in the software metric parameter, and determine a target comparison rule for the data type according to the target value; The tool deployment relationship is determined according to the target comparison rule.

5. The method according to claim 4, characterized in that After determining the tool deployment relationship according to the data acquisition rule, the method further includes: Based on the data type and the software metric parameter, determining the assessment exemption rule corresponding to the data captured by the candidate tool; The tool deployment relationship is updated according to the assessment exemption rule.

6. The method according to claim 5, characterized in that The capturing of target data based on the tool deployment relationship and the software metric parameters includes: Determining a target tool according to the tool deployment relationship, and determining a target database according to the tool deployment relationship and the software metric parameters; Determine an access address of the target tool, a first access port of the target tool, and a second access port of the target database; According to the access address, the first access port, the second access port and the data acquisition rule, the reference data is captured in the target database by the target tool; Target data is determined in the reference data based on the assessment exemption rule.

7. The method according to any one of claims 1 to 6, characterized in that: The determining the software measurement result of the target software according to the target data includes: Determine the indicator calculation rule of the target data according to the tool deployment relationship; The target data is measured and calculated according to the indicator calculation rule and the software measurement parameter to obtain a software quality measurement result of the target software.

8. A software quality measurement device, characterized in that: The device comprises: The measurement requirement acquisition module is used to obtain the user's measurement requirement indicators for the quality of the target software; A software measurement target determination module, used to determine software measurement parameters for measuring the target software according to the measurement requirement indicators, wherein the software measurement parameters include target parameters for measuring the target software under different indicators; A tool deployment relationship determination module, used to determine a tool deployment relationship for measuring the target software according to the software measurement parameters, wherein the tool deployment relationship is used to indicate an association relationship between a tool for implementing the software measurement parameters for measuring the target software and the measurement requirement indicator; The software measurement result determination module is used to capture target data based on the tool deployment relationship and the software measurement parameters, and determine the software quality measurement result of the target software according to the target data.

9. An electronic device, characterized in that: The electronic device comprises: processor; A memory having computer-readable instructions stored thereon, wherein when the computer-readable instructions are executed by the processor, the method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores program codes, which can be called by a processor to execute the method according to any one of claims 1 to 7.

Images