A reliability index determination method and device applied to software design

Abstract

The application discloses a reliability index determination method and device applied to software design, comprising: analyzing design features of a software design stage to obtain fault types corresponding to the design features; determining, based on the fault types, design defect information and design measure information corresponding to a reliability index of each software design stage to be generated; and generating the reliability index of the software design stage based on the design defect information and the design measure information. The application can fully analyze features of the software design stage, guide software design, timely locate and correct errors in the design process based on the reliability index, reduce design risks of the software, and further improve the reliability of the entire software.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of software, in particular to a reliability index determination method and device applied to software design. BACKGROUND

[0002] Software is widely used in various fields, and software reliability, as a software metric, summarizes the reliable operation degree of software through the failure probability of software. Software reliability analysis methods can be mainly divided into two types: software reliability growth model (SRGM) based on software test data and architecture based software reliability model (ABSRM) based on structure. Among them, the SRGM type mainly uses the idea of hardware test data processing to fit reliability data through test data, and also uses the Bayesian prediction method based on test data and expert experience. ABSRM is mainly based on the idea of system reliability model, and reliability is evaluated through modeling.

[0003] However, the software research and development life cycle includes the research and development stage: software demand, software design, software coding, software testing, software confirmation, operation and maintenance stage and upgrade change stage. When the foregoing software reliability method is used for evaluation, there is a certain lag, and the corresponding requirements and design are modified after reliability testing, which will consume a lot of resources for positioning, modification, retesting, and release. This increases the software release cycle and cannot guarantee the reliability of the software design stage. SUMMARY

[0004] In view of the above problems, the present application provides a reliability index determination method and device applied to software design, which can effectively guarantee the reliability of the software design stage and improve the overall reliability of the software.

[0005] In order to achieve the above purpose, the present application provides the following technical scheme:

[0006] A reliability index determination method applied to software design, comprising:

[0007] analyzing the design characteristics of the software design stage to obtain the fault type corresponding to the design characteristics;

[0008] Based on the fault type, the reliability index corresponding to the design defect information and the design measure information of each software design stage to be generated is determined;

[0009] Based on the design defect information and the design measure information, a reliability index of the software design stage is generated.

[0010] Optionally, the design features of the software design stage are analyzed to obtain a fault type corresponding to the design features, including:

[0011] Obtain software design requirement information;

[0012] Based on the design requirement information, determine the design features of the software design stage;

[0013] Based on the software design stage defect reason record database, determine a fault type corresponding to each design feature.

[0014] Optionally, the method further includes:

[0015] Obtain fault factor information of the software design stage in historical log data;

[0016] Classify the fault factor information to obtain a fault type;

[0017] Based on the fault type and fault factor information corresponding to each fault type, generate a software design stage defect reason record database.

[0018] The reliability index of the software design stage includes an error resolution rate index, an error positioning rate index, a fault isolation rate index, and a system failure rate index, and the design defect information covering each software design stage to be generated is determined, including:

[0019] The hardware fault, interface fault, and internal interface error in the software itself fault in the fault type are determined as the design defect information covering the error resolution rate index;

[0020] The data verification, designated verification, and logic error verification corresponding to the software itself fault type in the fault type are determined as the design defect information covering the error positioning rate index;

[0021] Based on the influence range of software faults, the design defect information covering the fault isolation rate index is determined;

[0022] Based on the fault information causing system failure in the historical data, the design defect information covering the system failure rate is determined;

[0023] The determination of the design measure information includes:

[0024] Obtain the number of errors corresponding to each fault type, and calculate the total number of errors based on the number of errors corresponding to each fault type;

[0025] obtaining a number of solved errors;

[0026] calculating an error solving rate based on the number of solved errors and the total number of errors;

[0027] obtaining a number of errors whose error positions are located;

[0028] calculating an error locating rate based on the number of errors whose error positions are located and the total number of errors;

[0029] determining a fault isolation rate based on a number of isolable faults and a total number of faults that should be isolated;

[0030] determining guiding design measures of the system failure rate index based on the evaluation information of the software system test data.

[0031] Optionally, the method further comprises:

[0032] correcting each of the design features in the software design stage based on the reliability index, so that the corrected design features meet the guiding design measure information of each of the reliability index.

[0033] A reliability index determination apparatus applied to software design, comprising:

[0034] an analysis unit configured to analyze design features in a software design stage and obtain fault types corresponding to the design features;

[0035] a determination unit configured to determine, based on the fault types, coverage design defect information and guiding design measure information corresponding to a reliability index of each software design stage to be generated;

[0036] a generation unit configured to generate a reliability index of a software design stage based on the coverage design defect information and the guiding design measure information.

[0037] Optionally, the analysis unit comprises:

[0038] a first acquisition subunit configured to acquire software design requirement information;

[0039] a first determination subunit configured to determine design features in a software design stage based on the design requirement information;

[0040] a second determination subunit configured to determine fault types corresponding to each of the design features based on a software design stage defect cause record database.

[0041] Optionally, the apparatus further comprises:

[0042] The information acquisition unit is used to obtain information on failure factors in the software design phase from historical log data;

[0043] A classification unit is used to classify the fault factor information to obtain the fault type;

[0044] The database generation unit is used to generate a database of defect cause records during the software design phase based on the fault types and the fault factor information corresponding to each fault type.

[0045] Optionally, the reliability indicators in the software design phase include error resolution rate, error location rate, fault isolation rate, and system failure rate. The determining unit includes a first determining subunit, which is used to determine the design defect information corresponding to the reliability indicators of each software design phase to be generated. Specifically, the first determining subunit is used to:

[0046] The error resolution rate index is determined to cover design defect information from hardware failures, interface failures, and internal interface errors in software failures among the aforementioned fault types.

[0047] The error location rate index covers design defect information by performing data verification, specified verification, and logical error verification corresponding to the software fault types in the fault types.

[0048] Based on the scope of the impact of software failures, determine the design defect information covered by the failure isolation rate index;

[0049] Based on fault information of system failures in historical data, the system failure rate is determined to include design defect information;

[0050] The determining unit includes a second determining subunit, used to determine guiding design measures information, wherein the second determining subunit is specifically used for:

[0051] Obtain the number of errors corresponding to each fault type, and calculate the total number of errors based on the number of errors corresponding to each fault type;

[0052] Get the number of resolved errors;

[0053] The error resolution rate is calculated based on the number of errors resolved and the total number of errors.

[0054] Get the number of errors that have been located;

[0055] The error location rate is calculated based on the number of errors at the located error locations and the total number of errors.

[0056] The fault isolation rate is determined based on the number of faults that can be isolated and the total number of faults that should be isolated.

[0057] Based on the evaluation information of the software system test data, design measures are determined to guide the system failure rate index.

[0058] Optionally, the device further includes:

[0059] The correction unit is used to correct each of the design features in the software design phase based on the reliability index, so that the corrected design features meet the guidance design measures information of each of the reliability indices.

[0060] Compared to existing technologies, this invention provides a method and apparatus for determining reliability indicators in software design, comprising: analyzing design features in the software design phase to obtain fault types corresponding to the design features; determining, based on the fault types, the reliability indicators for each software design phase to be generated, including design defect information and guiding design measures information; and generating the reliability indicators for the software design phase based on the design defect information and the guiding design measures information. This invention can fully analyze the characteristics of the software design phase, guide the timely location and correction of errors in the design process based on reliability indicators, reduce software design risks, and thus improve the overall reliability of the software. Attached Figure Description

[0061] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0062] Figure 1 A flowchart illustrating a method for determining reliability indicators in software design, provided by an embodiment of the present invention;

[0063] Figure 2 This is a schematic diagram of a device for determining reliability indicators in software design, provided as an embodiment of the present invention. Detailed Implementation

[0064] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0065] The terms "first" and "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units may include steps or units not listed, but rather steps or units not listed.

[0066] This invention provides a method for determining reliability indicators in software design. This method can be applied during the design phase of a software product, guiding the design process based on the determined reliability indicators. For example, it can locate faults during the software design process and address the located errors using specific design-guided measures, such as error isolation. It can also correct the design features of existing software products to ensure reliability during the design phase, thereby improving the reliability throughout the entire software product lifecycle.

[0067] See Figure 1 This is a flowchart illustrating a method for determining reliability indicators in software design, provided by an embodiment of the present invention. The method may include the following steps:

[0068] S101. Analyze the design features in the software design phase to obtain the fault types corresponding to the design features.

[0069] Design features in the software design phase can be features determined based on the software design requirements, such as the hardware features of the software application, the interface features between the software and the corresponding hardware, etc.

[0070] By combining historical data on software design with common software design failures or errors, these design features are analyzed to identify the corresponding failure types. These failure types represent potential failures associated with these current design features. For example, if the software's design features include data acquisition, there might be failures related to the data acquisition interface; if the software includes hardware control features, there might be errors or failures corresponding to hardware failure types.

[0071] Therefore, in the embodiments of the present invention, reliability indicators can be further determined according to the fault type, thereby fully considering the corresponding countermeasures for each fault type and ensuring the reliability of the software design.

[0072] In one embodiment of the present invention, the step of analyzing the design features in the software design phase to obtain the fault types corresponding to the design features includes:

[0073] Obtain software design requirements information;

[0074] Based on the aforementioned design requirements information, the design characteristics of the software design phase are determined;

[0075] Based on the database of defect causes recorded during the software design phase, the fault type corresponding to each design feature is determined.

[0076] Among them, requirement information refers to relevant information about the design requirements of the current software product (hereinafter referred to as software). For example, if the software is designed to process data from various business systems in a unified manner, then the software needs to collect data from each business system. Therefore, there needs to be a design feature for the data collection interface. Then, the database of defect cause records in the software design phase is queried to obtain relevant data on historical defect causes corresponding to the design feature, thereby determining the corresponding fault type.

[0077] Furthermore, this embodiment of the invention also provides a method for generating a database of defect cause records during the software design phase, the method comprising:

[0078] Obtain information on failure factors during the software design phase from historical log data;

[0079] The fault factor information is classified to obtain the fault type;

[0080] Based on the fault types and the fault factor information corresponding to each fault type, a database of defect cause records for the software design phase is generated.

[0081] Historical log data is recorded at various stages of the software development process, including the software design, testing, and maintenance phases. It records faults and errors that are likely to occur during the software design phase, as well as problems encountered during maintenance. Therefore, analyzing historical log data can identify potential fault factors during the software design phase. Furthermore, to improve software design reliability, fault factors can be categorized into fault types. A corresponding database of software design phase defect causes can then be generated based on these fault types and their associated fault factors. This database, combined with current design features, helps determine the corresponding fault types and fault factors, guiding the generation of new software design features or correcting existing ones.

[0082] S102. Based on the fault type, determine the information covering design defects and guiding design measures corresponding to the reliability indicators of each software design stage to be generated.

[0083] The information covering design defects refers to the scope of application of reliability metrics in the corresponding software design phase, or the types of faults targeted, as well as the subtypes corresponding to those fault types. Therefore, the application scope in the software design process can be determined based on subsequently generated reliability metrics. The information guiding design measures mainly includes fault response measures for the software design process. For example, error location rate metrics can be used to locate errors in the software design process and adjust the corresponding code or data.

[0084] S103. Based on the information covering design defects and the information on guiding design measures, generate reliability indicators for the software design phase.

[0085] Each reliability metric in the software design phase includes information on design flaws and guiding design measures. This information can be encapsulated to generate corresponding reliability metrics, which can then be applied throughout the software design process. Specifically, each reliability metric can be matched and stored with its corresponding design flaw and guiding design measures information. When a reliability metric is invoked during the software design phase, its specific guiding design measures can be displayed. Alternatively, it can be used to highlight and detect potential design flaws within the scope of the metric during the software design phase, thereby improving the reliability of the software design process.

[0086] Specifically, fault types can be categorized into hardware faults, interface faults, software faults, and other unknown faults. Further, hardware faults can include hard drive errors, memory errors, and instruction errors; interface faults can include external interface errors and input data errors; software faults can include logic errors, data definition errors, database errors, input / output (I / O) errors, calculation errors, data processing errors, and can also include internal interface errors, topology faults, and requirement-related errors.

[0087] When indicator factors characterize relevant indicator parameters in the software design process, analysis can be performed based on the fault information under the corresponding fault type to determine the reliability indicators corresponding to each software design stage to be generated, including information on design defects and guidance measures for design.

[0088] Specifically, the reliability metrics in the software design phase include error resolution rate, error location rate, fault isolation rate, and system failure rate. The determination of the design defect information corresponding to the reliability metrics for each software design phase to be generated includes:

[0089] The error resolution rate index is determined to cover design defect information from hardware failures, interface failures, and internal interface errors in software failures among the aforementioned fault types.

[0090] The error location rate index covers design defect information by performing data verification, specified verification, and logical error verification corresponding to the software fault types in the fault types.

[0091] Based on the scope of the impact of software failures, determine the design defect information covered by the failure isolation rate index;

[0092] Based on fault information of system failures in historical data, the system failure rate is determined to include design defect information;

[0093] The determination of guiding design measures information includes:

[0094] Obtain the number of errors corresponding to each fault type, and calculate the total number of errors based on the number of errors corresponding to each fault type;

[0095] Get the number of resolved errors;

[0096] The error resolution rate is calculated based on the number of errors resolved and the total number of errors.

[0097] Get the number of errors that have been located;

[0098] The error location rate is calculated based on the number of errors at the located error locations and the total number of errors.

[0099] The fault isolation rate is determined based on the number of faults that can be isolated and the total number of faults that should be isolated.

[0100] Based on the evaluation information of the software system test data, design measures are determined to guide the system failure rate index.

[0101] Therefore, reliability indicators can be obtained from this information, and software design can be carried out based on these reliability indicators. See Table 1, which provides a reliability indicator for the software design phase according to an embodiment of the present invention. In Table 1, the indicator name is named after the indicator factor, and the design defects covered and the specific measures to guide the design are all included in the reliability indicator.

[0102] Table 1 Reliability Indicators

[0103]

[0104]

[0105] By setting reasonable indicator requirements through the aforementioned reliability indicator system, design errors are addressed through dimensions such as full identification, design application of countermeasures, error diagnosis, fault logging and indication, and limiting the impact of faults. This reduces risk to a reasonably feasible and as low a level as possible. Simultaneously, for unknown faults, the system failure rate indicator is retained to constrain the overall reliability level of the software product.

[0106] In one embodiment of the present invention, after obtaining the reliability index, the various design features in the software design stage can be corrected based on the reliability index so that the corrected design features meet the various index factors.

[0107] Specifically, the current design metrics can be corrected based on the specific measures guiding the design in the reliability indicators in Table 1. For example, parameters in the design features can be corrected, and the type of acquisition interface or hardware characteristics can be modified. This allows for the timely detection of defects in the software design process, thereby improving the reliability of the software design phase.

[0108] In another embodiment of the present invention, a reliability index determination device for software design is also provided, see [link to relevant documentation]. Figure 2 ,include:

[0109] Analysis unit 201 is used to analyze the design features in the software design phase and obtain the fault types corresponding to the design features;

[0110] The determining unit 202 is used to determine, based on the fault type, the reliability index corresponding to each software design stage to be generated, including design defect information and guiding design measures information;

[0111] The generation unit 203 is used to determine, based on the fault type, the reliability index corresponding to each software design stage to be generated, including design defect information and guiding design measures information.

[0112] In one embodiment of the present invention, the analysis unit includes:

[0113] The first acquisition subunit is used to acquire software design requirement information;

[0114] The first determining subunit is used to determine the design features of the software design phase based on the design requirement information.

[0115] The second determining subunit is used to determine the fault type corresponding to each of the design features based on the database of defect cause records from the software design phase.

[0116] Furthermore, the device also includes:

[0117] The information acquisition unit is used to obtain information on failure factors in the software design phase from historical log data;

[0118] A classification unit is used to classify the fault factor information to obtain the fault type;

[0119] The database generation unit is used to generate a database of defect cause records during the software design phase based on the fault types and the fault factor information corresponding to each fault type.

[0120] In one implementation, the reliability metrics in the software design phase include error resolution rate, error location rate, fault isolation rate, and system failure rate. The determining unit includes a first determining subunit, which is used to determine the design defect information corresponding to the reliability metrics of each software design phase to be generated. Specifically, the first determining subunit is used to:

[0121] The error resolution rate index is determined to cover design defect information from hardware failures, interface failures, and internal interface errors in software failures among the aforementioned fault types.

[0122] The error location rate index covers design defect information by performing data verification, specified verification, and logical error verification corresponding to the software fault types in the fault types.

[0123] Based on the scope of the impact of software failures, determine the design defect information covered by the failure isolation rate index;

[0124] Based on fault information of system failures in historical data, the system failure rate is determined to include design defect information;

[0125] The determining unit includes a second determining subunit, used to determine guiding design measures information, wherein the second determining subunit is specifically used for:

[0126] Obtain the number of errors corresponding to each fault type, and calculate the total number of errors based on the number of errors corresponding to each fault type;

[0127] Get the number of resolved errors;

[0128] The error resolution rate is calculated based on the number of errors resolved and the total number of errors.

[0129] Get the number of errors that have been located;

[0130] The error location rate is calculated based on the number of errors at the located error locations and the total number of errors.

[0131] The fault isolation rate is determined based on the number of faults that can be isolated and the total number of faults that should be isolated.

[0132] Based on the evaluation information of the software system test data, design measures are determined to guide the system failure rate index.

[0133] In another embodiment, the device further includes:

[0134] The correction unit is used to correct each of the design features in the software design phase based on the reliability index, so that the corrected design features meet the guidance design measures information of each of the reliability indices.

[0135] This invention provides a reliability index determination device for software design, comprising: an analysis unit analyzing design features of the software design stage to obtain fault types corresponding to the design features; a determination unit determining, based on the fault types, design defect information and guiding design measures information corresponding to the reliability index to be generated for each software design stage; and a generation unit generating the reliability index for the software design stage based on the design defect information and the guiding design measures information. This invention can fully analyze the characteristics of the software design stage, guide software design based on reliability indexes, reduce software design risks, and thus improve the overall reliability of the software.

[0136] Based on the foregoing embodiments, embodiments of the present invention provide a computer-readable storage medium storing one or more programs that can be executed by one or more processors to implement the steps of the reliability index determination method for software design as described above.

[0137] This invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement:

[0138] Analyze the design features in the software design phase to obtain the fault types corresponding to the design features;

[0139] Based on the fault type, determine the information covering design defects and guiding design measures corresponding to the reliability indicators of each software design stage to be generated;

[0140] Based on the information covering design defects and the information on guiding design measures, reliability indicators are generated during the software design phase.

[0141] Optionally, the step of analyzing the design features during the software design phase to obtain the fault types corresponding to the design features includes:

[0142] Obtain software design requirements information;

[0143] Based on the aforementioned design requirements information, the design characteristics of the software design phase are determined;

[0144] Based on the database of defect causes recorded during the software design phase, the fault type corresponding to each design feature is determined.

[0145] Optionally, the method further includes:

[0146] Obtain information on failure factors during the software design phase from historical log data;

[0147] The fault factor information is classified to obtain the fault type;

[0148] Based on the fault types and the fault factor information corresponding to each fault type, a database of defect cause records for the software design phase is generated.

[0149] The reliability metrics in the software design phase include error resolution rate, error location rate, fault isolation rate, and system failure rate. The determination of the design defect information corresponding to the reliability metrics for each software design phase to be generated includes:

[0150] The error resolution rate index is determined to cover design defect information from hardware failures, interface failures, and internal interface errors in software failures among the aforementioned fault types.

[0151] The error location rate index covers design defect information by performing data verification, specified verification, and logical error verification corresponding to the software fault types in the fault types.

[0152] Based on the scope of the impact of software failures, determine the design defect information covered by the failure isolation rate index;

[0153] Based on fault information of system failures in historical data, the system failure rate is determined to include design defect information;

[0154] The determination of guiding design measures information includes:

[0155] Obtain the number of errors corresponding to each fault type, and calculate the total number of errors based on the number of errors corresponding to each fault type;

[0156] Get the number of resolved errors;

[0157] The error resolution rate is calculated based on the number of errors resolved and the total number of errors.

[0158] Get the number of errors that have been located;

[0159] The error location rate is calculated based on the number of errors at the located error locations and the total number of errors.

[0160] The fault isolation rate is determined based on the number of faults that can be isolated and the total number of faults that should be isolated.

[0161] Based on the evaluation information of the software system test data, design measures are determined to guide the system failure rate index.

[0162] Optionally, the method further includes:

[0163] Based on the aforementioned reliability indicators, each of the design features in the software design phase is corrected so that the corrected design features meet the guiding design measures information of each of the aforementioned reliability indicators.

[0164] It should be noted that the aforementioned processor or CPU can be at least one of the following: Application-Specific Integrated Circuit (ASIC), Digital Signal Processor (DSP), Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), Field Programmable Gate Array (FPGA), Central Processing Unit (CPU), controller, microcontroller, and microprocessor. Understandably, the electronic device implementing the above processor function can also be other types, and this application does not specifically limit its capabilities.

[0165] It should be noted that the aforementioned computer storage media / memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM), etc.; it can also be various terminals that include one or any combination of the above-mentioned memory, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0166] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

[0167] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0168] Furthermore, in the various embodiments of this application, all functional units can be integrated into one processing module, or each unit can be a separate unit, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in a combination of hardware and software functional units. Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0169] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0170] The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0171] The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method or device embodiments.

[0172] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0173] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to the method section.

[0174] The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for determining reliability indicators applied to software design, characterized in that, include: Analyze the design features in the software design phase to obtain the fault types corresponding to the design features; Based on the fault type, determine the information covering design defects and guiding design measures corresponding to the reliability indicators of each software design stage to be generated; Based on the information covering design defects and the information on guiding design measures, reliability indicators are generated during the software design phase. The reliability metrics in the software design phase include error resolution rate, error location rate, fault isolation rate, and system failure rate. The determination of the design defect information corresponding to the reliability metrics for each software design phase to be generated includes: The error resolution rate index is determined to cover design defect information from hardware failures, interface failures, and internal interface errors in software failures among the aforementioned fault types. The error location rate index covers design defect information by performing data verification, specified verification, and logical error verification corresponding to the software fault types in the fault types. Based on the scope of the impact of software failures, determine the design defect information covered by the failure isolation rate index; Based on fault information of system failures in historical data, the system failure rate is determined to include design defect information; The determination of guiding design measures information includes: Obtain the number of errors corresponding to each fault type, and calculate the total number of errors based on the number of errors corresponding to each fault type; Get the number of resolved errors; The error resolution rate is calculated based on the number of errors resolved and the total number of errors. Get the number of errors that have been located; The error location rate is calculated based on the number of errors at the located error locations and the total number of errors. The fault isolation rate is determined based on the number of faults that can be isolated and the total number of faults that should be isolated. Based on the evaluation information of the software system test data, design measures are determined to guide the system failure rate index.

2. The method according to claim 1, characterized in that, The analysis of design features during the software design phase to obtain the fault types corresponding to those features includes: Obtain software design requirements information; Based on the aforementioned design requirements information, the design characteristics of the software design phase are determined; Based on the database of defect causes recorded during the software design phase, the fault type corresponding to each design feature is determined.

3. The method according to claim 2, characterized in that, The method further includes: Obtain information on failure factors during the software design phase from historical log data; The fault factor information is classified to obtain the fault type; Based on the fault types and the fault factor information corresponding to each fault type, a database of defect cause records for the software design phase is generated.

4. The method according to claim 1, characterized in that, The method further includes: Based on the aforementioned reliability indicators, each of the design features in the software design phase is corrected so that the corrected design features meet the guiding design measures information of each of the aforementioned reliability indicators.

5. A device for determining reliability indicators in software design, characterized in that, include: The analysis unit is used to analyze the design features in the software design phase and obtain the fault types corresponding to the design features; The determining unit is used to determine, based on the fault type, the reliability index corresponding to each software design stage to be generated, including design defect information and guiding design measures information; The generation unit is used to generate reliability indicators for the software design phase based on the information covering design defects and the information on guiding design measures. The reliability metrics in the software design phase include error resolution rate, error location rate, fault isolation rate, and system failure rate. The determining unit includes a first determining subunit, which is used to determine the design defect information corresponding to the reliability metrics for each software design phase to be generated. Specifically, the first determining subunit is used for: The error resolution rate index is determined to cover design defect information from hardware failures, interface failures, and internal interface errors in software failures among the aforementioned fault types. The error location rate index covers design defect information by performing data verification, specified verification, and logical error verification corresponding to the software fault types in the fault types. Based on the scope of the impact of software failures, determine the design defect information covered by the failure isolation rate index; Based on fault information of system failures in historical data, the system failure rate is determined to include design defect information; The determining unit includes a second determining subunit, used to determine guiding design measures information, wherein the second determining subunit is specifically used for: Obtain the number of errors corresponding to each fault type, and calculate the total number of errors based on the number of errors corresponding to each fault type; Get the number of resolved errors; The error resolution rate is calculated based on the number of errors resolved and the total number of errors. Get the number of errors that have been located; The error location rate is calculated based on the number of errors at the located error locations and the total number of errors. The fault isolation rate is determined based on the number of faults that can be isolated and the total number of faults that should be isolated. Based on the evaluation information of the software system test data, design measures are determined to guide the system failure rate index.

6. The apparatus according to claim 5, characterized in that, The analysis unit includes: The first acquisition subunit is used to acquire software design requirement information; The first determining subunit is used to determine the design features of the software design phase based on the design requirement information. The second determining subunit is used to determine the fault type corresponding to each of the design features based on the database of defect cause records from the software design phase.

7. The apparatus according to claim 6, characterized in that, The device further includes: The information acquisition unit is used to obtain information on failure factors in the software design phase from historical log data; A classification unit is used to classify the fault factor information to obtain the fault type; The database generation unit is used to generate a database of defect cause records during the software design phase based on the fault types and the fault factor information corresponding to each fault type.

8. The apparatus according to claim 5, characterized in that, The device further includes: The correction unit is used to correct each of the design features in the software design phase based on the reliability index, so that the corrected design features meet the guidance design measures information of each of the reliability indices.

Images