CN112558927A - Software reliability index distribution method and device based on layer-by-layer decomposition method - Google Patents
Software reliability index distribution method and device based on layer-by-layer decomposition method Download PDFInfo
- Publication number
- CN112558927A CN112558927A CN202011426099.3A CN202011426099A CN112558927A CN 112558927 A CN112558927 A CN 112558927A CN 202011426099 A CN202011426099 A CN 202011426099A CN 112558927 A CN112558927 A CN 112558927A
- Authority
- CN
- China
- Prior art keywords
- layer
- decomposition
- software
- node
- reliability
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 93
- 238000000354 decomposition reaction Methods 0.000 title claims abstract description 73
- 238000010586 diagram Methods 0.000 claims description 20
- 238000004364 calculation method Methods 0.000 claims description 15
- 238000005516 engineering process Methods 0.000 claims description 12
- 238000004458 analytical method Methods 0.000 description 14
- 230000007547 defect Effects 0.000 description 11
- 238000013461 design Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 6
- 235000010425 Sorbus domestica Nutrition 0.000 description 5
- 240000005332 Sorbus domestica Species 0.000 description 5
- 230000000694 effects Effects 0.000 description 5
- 238000012795 verification Methods 0.000 description 5
- 238000011161 development Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012360 testing method Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 238000004445 quantitative analysis Methods 0.000 description 1
- 238000013139 quantization Methods 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/10—Requirements analysis; Specification techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/74—Reverse engineering; Extracting design information from source code
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a software reliability index distribution method and device based on a layer-by-layer decomposition method. The method comprises the following steps: software or modules are decomposed layer by layer until the minimum node which can be decomposed at the stage is reached, and a tree is drawn; collecting reliability influence factors of the bottommost node of the decomposition result, and calculating a characteristic value; collecting reliability influence factors of the technical level decomposition entry nodes, and calculating characteristic values; reversely calculating the distribution proportion of the bottommost layer node and the above level nodes; and carrying out index distribution layer by layer node by node according to the distribution model. The software reliability index distribution method and device based on the layer-by-layer decomposition method can solve the problem that the software reliability index distribution is difficult to implement to fall to the ground at present.
Description
Technical Field
The invention relates to the technical field of software engineering, in particular to a software reliability index distribution method and device based on a layer-by-layer decomposition method.
Background
Currently, there are many recognized software reliability index distribution methods, such as a fast distribution method, which uses a similar program and a similar module to distribute indexes in a mean value; for example, an equivalent distribution method adopts sequential and parallel software module equivalent distribution indexes; for example, the operation profile assignment method assigns the index to each operation profile set and to each probability. Generally, the existing software reliability index distribution method is a distribution method by using hardware for reference, and has the following defects in the process of adapting to software:
the preconditions of the allocation method are difficult to obtain and to apply at all stages of the software
For example, a fast distribution method requires a historical similar system, and if no similar system is available, 14 items such as "data communication", "distributed function", "performance", "frequently used configuration", "transaction rate", "online data item" and the like, which are unavailable in the early stage of software and cannot be applied to the demand analysis stage, need to be collected based on a complexity distribution method.
Distribution basis
The existing software reliability index distribution method is used for solving hardware reliability index distribution, for example, a distribution method based on complexity needs to obtain running criticality and complexity data in advance, and is applied to a system with functions connected in series, while software reliability is not only influenced by the criticality and the complexity in practice, and the distribution method is relatively one-sided and only suitable for a system without influence among functional modules.
Poor efficiency of the distribution method
The poor distribution effect is a remarkable characteristic of the current reliability distribution method, namely, the distribution is uneven, and the error of the actual calculation result is large, for example, in the method based on the operation profile, due to the influence of time and operation frequency, the probability is difficult to calculate accurately, so that the distribution rate is not correct enough, and the design and implementation after the distribution have almost no reference value, and the effect is poor.
Disclosure of Invention
The invention aims to provide a software reliability index distribution method and device based on a layer-by-layer decomposition method, and can solve the problem that the conventional software reliability index distribution is difficult to implement and fall to the ground.
In order to solve the technical problem, the invention provides a software reliability index distribution method based on a layer-by-layer decomposition method, which comprises the following steps: software or modules are decomposed layer by layer until the minimum node which can be decomposed at the stage is reached, and a tree is drawn; collecting reliability influence factors of the bottommost node of the decomposition result, and calculating a characteristic value; collecting reliability influence factors of the technical level decomposition entry nodes, and calculating characteristic values; reversely calculating the distribution proportion of the bottommost layer node and the above level nodes; and carrying out index distribution layer by layer node by node according to the distribution model.
In some embodiments, the layer-by-layer decomposition software or module comprises: business level decomposition, and technology level decomposition.
In some embodiments, business hierarchy decomposition comprises: determining a software module M with reliability requirements; determining a submodule set C of the M module; iterating the module set C to determine all the subsets CijUp to the bottommost layer P; determining a relevant module set R of the M modules; iterating module set R to determine all self and RijUp to the bottommost layer; and forming a hierarchical relation graph.
In some embodiments, the technology level decomposition comprises: determining a software technical architecture diagram; determining a technical layer decomposition inlet aiming at a hierarchical relation graph of business layer decomposition; and repeatedly determining a new technical layer decomposition inlet aiming at the technical layering result until the minimum unit capable of being decomposed.
In some embodiments, the collecting technology level decomposes the reliability influence factors of the entry node, and calculates the characteristic value, including: and for the technical level decomposition entry node, acquiring values of reliability influence factors influencing node services and factors influencing technical architecture reliability, calculating a characteristic value of each node according to a characteristic value calculation model, and distributing the proportion as a characteristic value ratio.
In some embodiments, the feature value calculation model is as follows:
λ＝(α/∑αi)±∑0.5αj
wherein, λ is the ratio of eigenvalues, α is the eigenvalue of the node, and Σ αiFor the sum of the characteristic values of the nodes of the present hierarchy, αjIs the related node characteristic value.
In some embodiments, further comprising: for the sub-module of the service layer, the characteristic value of the sub-node of the service layer is collected and is the characteristic value of the node, and the distribution proportion is the ratio of the characteristic values.
In addition, the invention also provides a software reliability index distribution device based on the layer-by-layer decomposition method, and the device comprises: one or more processors; storage means for storing one or more programs; when executed by the one or more processors, cause the one or more processors to implement a software reliability index assignment methodology in accordance with the layer-by-layer decomposition-based methodology described above.
After adopting such design, the invention has at least the following advantages:
the method provided by the invention is proposed and applied in 2017, in a software project, the method is executed in a forward direction, reliability design and implementation are carried out according to distribution proportion, then reverse reasoning verification is carried out, the result is basically in direct proportion, namely if distribution is carried out with reliability, the distribution result and the actual calculation result have the same trend, and the error mean value is obviously smaller than that of other typical reliability index distribution methods.
Drawings
The foregoing is only an overview of the technical solutions of the present invention, and in order to make the technical solutions of the present invention more clearly understood, the present invention is further described in detail below with reference to the accompanying drawings and the detailed description.
Fig. 1 is a schematic diagram of layer-by-layer analysis of a software service provided in an embodiment of the present invention;
FIG. 2 is a software architecture diagram provided by an embodiment of the present invention;
fig. 3 is a schematic diagram of an index assignment model according to an embodiment of the present invention.
Detailed Description
The preferred embodiments of the present invention will be described in conjunction with the accompanying drawings, and it will be understood that they are described herein for the purpose of illustration and explanation and not limitation.
At present, software reliability index distribution has more than three defects, and in addition, the reliability index distribution cannot be implemented without landing, theoretical guidance for how to implement the reliability index distribution is not provided, and the main reason is that the reliability distribution methods are from hardware rather than from the perspective of software, so the patent provides a reliability index distribution method based on the analysis result of the characteristics of the software, and the method integrates precondition collection, landing implementation, evaluation and verification into a whole and supplements the deficiency of the software reliability distribution theory.
Because the existing software reliability allocation method is not provided according to the characteristics of software, but directly uses the allocation method of a hardware level and a system level, the software reliability allocation method has inherent defects when applied to software reliability index allocation, such as poor satisfaction of preconditions, poor use, inaccurate application results after allocation and the like. Therefore, the invention aims to provide a reliability index distribution method by combining the inherent characteristics of software so as to solve the problem that the current software reliability index distribution is difficult to implement and fall to the ground.
2.1 layer-by-layer decomposition method
Whether the software is reliable is represented in the software or module or operation, the software is shown in a hierarchy, and the reliability of the software is distributed in the hierarchy. The software has a fixed architecture to embody and implement the hierarchy, and each element of each hierarchy on the architecture affects the reliability value of the software, so when the reliability of the software is distributed, the architecture and the element set on the architecture need to be obtained first, and then the reliability value is distributed to the elements.
In software design, there are two general architecture diagrams, one is a service architecture diagram and the other is a technical architecture diagram. The main steps of layer-by-layer decomposition are as follows:
a. firstly, determining nodes with reliability requirements based on a service architecture diagram;
b. secondly, deep decomposition is carried out to the minimum unit according to the service, such as operation;
c. analyzing the technical implementation steps of the operation and corresponding to the technical architecture layers or nodes;
after the operation is determined, the technical architecture is used as an analysis point, the program entry of the operation is analyzed, the code structure relationship is deeply analyzed, generally, the file is used as a unit, the tangent point of code logic is analyzed, and all calling relationships are covered until the operation is finished. The components or code in the middle of each complete entry and exit act as objects to be allocated until no more layering can occur.
d. And finally outputting a tree.
The root node of the tree is software or a module which needs to be designed reliably, the leaf nodes are operations, and the middle nodes are modules or sub-modules. If the realization technology of the service node can be layered, the decomposition is carried out according to the technology layer.
The final goal of the method for decomposing the reliability index layer by layer is to assign each of the service layer and the technology layer to a reliability value, and the more detailed the decomposition, the more possible the decomposition is to be implemented and the greater the degree of assurance on the reliability is.
2.1.1 Business level decomposition
The minimum unit is a function module, the subdivision of the function module is operation, generally comprises inquiry, addition, modification, deletion and the like, the existing reliability index distribution method is mainly based on the service architecture, indexes are distributed to all units averagely or by adopting a certain rule, and then a fixed calculation formula is adopted to calculate the integrated reliability value.
The service function operation performance of the software is also reliability performance, the reliability of one functional module can be obtained from the reliability of the analysis sub-module, and the reliability of the related modules is also influenced, so that the parent-child relationship and the related relationship are analyzed during layer-by-layer analysis, and the analysis result forms a hierarchical division result.
The business level analysis steps are as follows:
a. determining a software module M with reliability requirements;
b. determining a submodule set C of the M module;
c. an iteration module set C, determining all the subset Cij … till the bottommost layer P;
for example, when there is an operation on the bottom layer, it is assumed that the operation set Pi is { P1, P2, P3 … Pn }, and the operation set of the set Cij … is { P1, P2, P3 … Pn }. Each Pi is a set of independent dependent operations. The process of decomposing the hierarchy into operations, like the process of assigning based on operational profiles, is from macroscopic system starting decomposition to operations that cannot be subdivided. And decomposing to the lowest layer of the business layer after the operation is decomposed, and then deeply layering belongs to the technical layer decomposition, and the business layer decomposition prepares for the technical layer decomposition.
d. Determining a related module set R of the M modules in the step (2);
the relevant modules of the M-module are modules that can affect the reliability of the M-module, and are generally a prerequisite of the M-module, and do not include modules supported by the M-module.
e. Performing step (3) on R;
since the R-module is a related module, the reliability of the R-module affects the reliability of the M-module, the R-module is decomposed to obtain a deep level of modules or operations that affect the reliability of the modules.
f. And forming a hierarchical relation diagram, wherein the business hierarchical analysis diagram is shown in figure 1.
The business level analysis and decomposition serve the technical level analysis and decomposition, and the detailed business level units can accurately position the technical units and have a direction in executing reliability distribution. In addition, different service units have different requirements on the technical units, the technical units have no reliability requirement, and the reliability can be shown after the technical units are combined with the services, and the detailed reliability requirement of the service level units can cover all the reliability requirements on the technical units as much as possible, so that the requirements of the overall system or module are finally met.
2.1.2 technical level decomposition
The technical level decomposition starts from a service operation level, the service level is decomposed to a specific level, and the service is decomposed on the technical level, for example, a function module is divided into an inquiry and a report, and the inquiry and the report belong to two modules on the technical level, namely a main service and a report service, which are independently operated and deployed.
The premise of technical level decomposition is that an overall architecture of a software system is needed, and a corresponding scheme is searched when specific business operation is decomposed.
The software architecture analysis mainly analyzes an architecture diagram of software, and the architecture diagram describes technical components, technical interfaces, deployment relations and the like, and is a common software technology architecture schematic diagram as shown in the following figure.
The technical architecture generally comprises a software implementation layer, a software component and a software deployment component, all elements in the architecture influence the reliability of the software, and the technical elements are entities forming the software, so that whether the software is reliable or not is fundamentally determined. Theoretically, during software design, the reliability of a single technical element can reach 100%, and the function of one technical element can be guaranteed to be completely correct, but in actual engineering, one technical element often interacts with other technical elements, unexpected events can occur in the interaction, the optimal effect of the technical element cannot be achieved due to the influence of the environment, and the defects which cannot be prevented in advance can be caused by the events and can appear in the technical elements of any party, so that the reliability distribution of the technical elements can become significant, the section analyzes and stratifies layers from the technical perspective, and finally divides the technical architecture into a technical element set.
Performing a technical level decomposition step for a specific operation, specifically as follows:
a. determining a software technical architecture diagram;
the technical architecture diagram has a plurality of expression modes according to different purposes, the hierarchy and the depth of the expression modes cannot be summarized, the purpose of the architecture diagram in the step is to determine that software reliability indexes can be distributed and are convenient to test, modules need to be determined, and the implementation process of the modules needs to be detailed to an internal package, so the technical architecture diagram is represented by a development view. The development view is needed to be completed during design, serves developers, reflects the implementation process of the system, can predict the implementation effect of the system in advance, and can represent the software quality of the implementation stage to the maximum extent in the design stage. A development view such as fig. 2.
b. Determining a technical layer decomposition inlet aiming at a hierarchical relation graph of business layer decomposition;
the technical layer decomposition entrance is also a service node separation place, and separates services from the technical architecture.
c. Repeating the step 2) aiming at the technical layering result until the minimum unit capable of being decomposed;
for example, decomposition to the database calling layer cannot be continued;
2.2 reliability index Allocation based on layer-by-layer decomposition method
2.2.1 index assignment model
The software or module is decomposed layer by layer in service level and technology level to obtain the structure as shown in fig. 3:
before the index is distributed, the reliability value of the root node of the index distribution model diagram in fig. 3 is determined, the value needs to be distributed to the child nodes, the child nodes are distributed to the nodes on the lower layer, and so on until the nodes of each layer of the path are decomposed, so that the distribution proportion of each node on each layer needs to be determined, and then the distribution can be executed.
Fig. 3 is a schematic diagram of an index distribution model, where reliability influencing factors of a technical-level decomposition entry node include service characteristics, technical factors, and relevant module influencing factors, and jointly determine a reliability index distribution ratio of the node, and other nodes determine the reliability index distribution ratio by the service characteristics and the relevant modules.
The method for determining the distribution proportion comprises the following steps:
a. for the node at the bottom layer, collecting characteristic values influencing the reliability of the node, calculating the characteristic value of each node according to a characteristic value calculation model, and calculating the distribution proportion as the ratio of the characteristic values;
b. for the sub-modules of the service layer, collecting the characteristic value of the sub-nodes and the characteristic value of the node, and distributing the proportion as the ratio of the characteristic values;
c. and for the technical level decomposition entry node, acquiring values of reliability influence factors influencing node services and factors influencing technical architecture reliability, calculating a characteristic value of each node according to a characteristic value calculation model, and distributing the proportion as a characteristic value ratio.
The eigenvalue proportion formula is:
λ＝(α/∑αi)±∑0.5αj (1)
where alpha is the characteristic value of the node, sigma alphaiFor the sum of the characteristic values of the nodes of the present hierarchy, αjThe characteristic value of the relevant node is obtained;
in summary, the reliability index allocation method based on layer-by-layer decomposition is described as follows:
(1) decomposing software or modules layer by layer until the minimum node which can be decomposed at the stage, and drawing a tree;
(2) collecting reliability influence factors of the bottommost node of the decomposition result, and calculating a characteristic value;
(3) collecting reliability influence factors of the technical level decomposition entry nodes, and calculating characteristic values;
(4) reversely calculating the distribution proportion of the bottommost layer node and the above level nodes;
(5) and carrying out index distribution layer by layer node by node according to the distribution model.
The characteristic value calculation model in the step is constructed by analyzing the reliability influence factors, and the index distribution model adopts a linear model, which is described in the following section.
2.2.2 determining reliability influencing factors
The reliability index is distributed according to the characteristics of the service and the technology, for example, if the service is a key service and the node in the technical architecture is a key node, the distributed reliability value is higher, otherwise, the distributed reliability value is lower, the characteristics can be called as factors influencing the reliability, and data of the factors needs to be collected when a reliability model is constructed.
Firstly, the service tree is characterized in that: the root of the service tree is software or a module, the middle node is a module or a sub-module, and the leaf node is an operation; the technical hierarchy path is characterized in that: the method can be constructed only from the lowest-layer service, namely, a service hierarchical path can be analyzed and obtained only from the operation, and the path is unique to one operation. Based on the characteristics of the service tree and the technical hierarchical path, when determining the reliability influence factors, analyzing according to two types of modules and operations.
a. For the module
The data which can be collected are basically statistical data, such as function points, which are function points of operation, namely, the reliability influence factor value of the module can be determined by the data of the operation; therefore, failure rates are collected directly for the modules, rather than collecting values of reliability-affecting factors.
b. For operation
The data that can be gathered are native data, also have statistical data, for example whether the operation has real-time requirement to be native data, the operation frequency degree is statistical data. Both raw data and statistical data are data that can be factored into reliability.
Secondly, when the reliability index is distributed, the data of the reliability influence factors are required to be determined and predicted in the design stage, the determined data is the data in the design stage, and the predicted data is the data in the implementation stage. The range of reliability-affecting factors that can be collected therefore includes:
(1) data of early stage of software development in demonstration stage, design stage and other stages
The data that can be collected in the design stage are such as expected scale, expected defect rate, business criticality, etc.
(2) The data changed at any time in the implementation stage can predict the subsequent reliability value
And finally, determining a specific principle of the reliability influence factors: factors influencing the reliability of the software are considered from the characteristics of software function, performance, safety and the like, and the factors are collected from two aspects of service and technology, so that the influence factors are ensured to be comprehensive and correct.
In summary, the range of reliability influencing factors is: data that can be collected and data that can be estimated from the design phase for the operational and technical layers. The summary is as follows:
TABLE 1 reliability influencing factors
After the reliability influencing factors are determined, the reliability influencing factors need to be quantized, and the quantization needs to follow two principles:
a. the quantitative value is specified in a direction proportional to the reliability, i.e. the greater the influence factor score, the greater the influence on the reliability result.
b. The quantitative value is a given score value, not an actual numerical value. The influence degree of each influence factor is assumed to be one level, and if the influence degree is real data, the influence degree of other influence factors is ignored because one data is particularly large.
In order to adopt a unified formula for calculation, assuming that the influence degrees of all the influence factors on the reliability are the same, the threshold value ranges are consistent when the quantitative analysis is adopted, a certain range of scores are given to the qualitative influence factors, and classification scores are given to the quantitative continuity value factors, and the score value ranges are consistent.
Such as the quantized values of the reliability-affecting factors shown in the following table, assuming failure rate as a reliability parameter:
TABLE 2 quantized values of reliability-affecting factors
The characteristics of the technology layer can determine whether the reliability is easy to meet the requirement, and the technology selection is determined according to the service characteristics, for example, if the processing data quantity is large, measures similar to distributed processing may be taken in the technical point. The characteristics of the technical layer are quantified by a value-dividing method, and influence factors which may be generated on the reliability by each layer of the technical architecture are listed through investigation experts and experience personnel, and are specifically shown in the following table:
TABLE 3 technical layer influencing factors and weights
(1) Feature value calculation model
The characteristic values of the leaf nodes of the service tree need to be calculated according to a model, and the characteristic value of the middle node can be calculated as the mean value of the characteristic values of the child nodes. The characteristic value of the leaf node comprises two parts of contents, namely, a service reliability influence factor corresponding to the operation, and a technical level path corresponding to the operation.
In the above section, the operational reliability influence factors and the reliability influence factors of the technical nodes, such as "scale", "number of users", "frequency of use", etc., are summarized, and have a direct relationship with the defect rate that may occur, and thus have a direct relationship with the reliability failure rate, so the characteristic value calculation model may be a linear model. The formula is as follows:
ωi＝∑xi+β (2)
wherein, ω isiFor the characteristic value of the node to be solved, sigma xiIs the sum of the quantized values of the influencing factors of the nodes, and beta is an adjustment value.
The characteristic values of the leaf nodes can be calculated according to the formula 2, the characteristic values of the upper-layer nodes can be calculated by summing the characteristic values of the leaf nodes, and the characteristic values of all the nodes are calculated layer by layer from bottom to top.
(2) Index assignment
And calculating the characteristic values of the tree nodes in the previous step, calculating the characteristic value proportion of each node layer by layer, and then executing index distribution layer by layer from top to bottom.
5.1 reliability Allocation method application
And verifying the layer-by-layer reliability index distribution method and the prediction method by adopting historical test data, and acquiring corresponding data according to the parameter requirements of the layer-by-layer decomposition distribution and prediction method. The collected software is a project management system, and the reason for verifying by adopting the system is as follows: the system is a large-scale information system, the system service is complex, the number of subsystems and modules is large, and the system has the characteristics of the large-scale complex system and has certain universality and representativeness. The system running time exceeds 3 years, real data related to reliability are accumulated, and the data can represent a reliability value and can be used as a reliability index value to make up for the defect of insufficient software reliability data.
The tested software system information is as follows:
TABLE 4 basic information of software to be verified
| Name (R) | Reliability index value (failure rate) | Remarks for note |
| Project management system | 1/1000h | Actual engineering statistical index |
And selecting a data set in the accessory to learn a formula, wherein the data are extracted from part of software project data in the information management system of the unit. The verification conditions and preconditions are as follows:
in order to reduce the analysis workload, the analysis workload is decomposed into a technical layer of a subsystem layer, the subsystem layer is decomposed into a task layer, and reliability influence factor data corresponding to task nodes are collected.
In order to obtain the parameters of the prediction model, the collected data comprises factor values influencing the reliability and also comprises 'defect rate in operation by calculation', and the value is obtained by counting the ratio of the operation number in the operation log and the recorded operation time and is used as a real failure rate value. Because the use cases of system test and actual operation have randomness, the reliability defect rate can be assumed;
there are 9 modules of "a project management system", and 3 modules are divided into sub-services, including 130 operations.
5.2 reliability assignment method verification and comparison
Because the reliability index distribution method based on the layer-by-layer decomposition method is based on the improvement of the operation criticality and complexity method, the verification process respectively verifies the method based on the operation criticality and complexity and the application of the project method, and compares the results of the operation criticality and complexity method and the application of the project method.
(1) Reliability index allocation based on layer-by-layer decomposition method
Firstly, calculating a characteristic value of a service tree node according to a formula 1, and then calculating a distribution proportion, wherein a specific index distribution result is shown as an accessory '1 subsystem layer' and '1 task layer', and a subsystem layer distribution result is shown as the following table:
TABLE 5 reliability index assignment results based on layer-by-layer decomposition method-subsystem layer
Note: the actual values in the table above are the defect rates in actual operation.
And finally obtaining the error average value of the index distribution value and the actual value as follows: the subsystem level is 0.000323 and the task level is 0.001527.
(2) Distribution method based on operation criticality and complexity
The allocation results obtained by calculation according to the accessory data and the formula 1 are shown as an accessory '2 subsystem layer' and a '2 task layer', wherein the subsystem layer allocation results are shown as the following table:
TABLE 6 reliability index assignment results based on operational criticality, complexity — subsystem level
Note: the actual values in the table above are the defect rates in actual operation.
And finally obtaining the error average value of the index distribution value and the actual value as follows: the subsystem level is 0.0003442 and the task level is 0.001528.
Comparing the two methods, the error mean value of the index distribution method of layer-by-layer decomposition is smaller than that of the distribution method based on complexity, and the distribution effect of the first method is better than that of the second method.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the present invention in any way, and it will be apparent to those skilled in the art that the above description of the present invention can be applied to various modifications, equivalent variations or modifications without departing from the spirit and scope of the present invention.
Claims (8)
1. A software reliability index distribution method based on a layer-by-layer decomposition method is characterized by comprising the following steps:
software or modules are decomposed layer by layer until the minimum node which can be decomposed at the stage is reached, and a tree is drawn;
collecting reliability influence factors of the bottommost node of the decomposition result, and calculating a characteristic value;
collecting reliability influence factors of the technical level decomposition entry nodes, and calculating characteristic values;
reversely calculating the distribution proportion of the bottommost layer node and the above level nodes;
and carrying out index distribution layer by layer node by node according to the distribution model.
2. The software reliability index distribution method based on the layer-by-layer decomposition method according to claim 1, wherein the layer-by-layer decomposition software or modules comprise: business level decomposition, and technology level decomposition.
3. The software reliability index distribution method based on the layer-by-layer decomposition method according to claim 2, wherein the service level decomposition comprises:
determining a software module M with reliability requirements;
determining a submodule set C of the M module;
iterating the module set C to determine all the subsets CijUp to the bottommost layer P;
determining a relevant module set R of the M modules;
iterating module set R to determine all self and RijUp to the bottommost layer;
and forming a hierarchical relation graph.
4. The software reliability index distribution method based on the layer-by-layer decomposition method according to claim 2, wherein the technical hierarchy decomposition comprises:
determining a software technical architecture diagram;
determining a technical layer decomposition inlet aiming at a hierarchical relation graph of business layer decomposition;
and repeatedly determining a new technical layer decomposition inlet aiming at the technical layering result until the minimum unit capable of being decomposed.
5. The software reliability index distribution method based on the layer-by-layer decomposition method according to claim 1, wherein the collecting reliability influence factors of the technical layer decomposition entry nodes and calculating the characteristic values comprises:
and for the technical level decomposition entry node, acquiring values of reliability influence factors influencing node services and factors influencing technical architecture reliability, calculating a characteristic value of each node according to a characteristic value calculation model, and distributing the proportion as a characteristic value ratio.
6. The software reliability index distribution method based on the layer-by-layer decomposition method according to claim 5, wherein the eigenvalue calculation model is as follows:
λ＝(α/∑αi)±∑0.5αj
wherein, λ is the ratio of eigenvalues, α is the eigenvalue of the node, and Σ αiFor the sum of the characteristic values of the nodes of the present hierarchy, αjIs the related node characteristic value.
7. The software reliability index distribution method based on the layer-by-layer decomposition method according to claim 1, further comprising:
for the sub-module of the service layer, the characteristic value of the sub-node of the service layer is collected and is the characteristic value of the node, and the distribution proportion is the ratio of the characteristic values.
8. A software reliability index distribution device based on a layer-by-layer decomposition method is characterized by comprising the following steps:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the software reliability index assignment method based on the layer-by-layer decomposition method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011426099.3A CN112558927B (en) | 2020-12-09 | 2020-12-09 | Software reliability index distribution method and device based on layer-by-layer decomposition method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011426099.3A CN112558927B (en) | 2020-12-09 | 2020-12-09 | Software reliability index distribution method and device based on layer-by-layer decomposition method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112558927A true CN112558927A (en) | 2021-03-26 |
| CN112558927B CN112558927B (en) | 2024-02-20 |
Family
ID=75059977
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011426099.3A Active CN112558927B (en) | 2020-12-09 | 2020-12-09 | Software reliability index distribution method and device based on layer-by-layer decomposition method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112558927B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116225949A (en) * | 2023-03-08 | 2023-06-06 | 安徽省软件评测中心 | Software reliability acceptance risk assessment method |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030034995A1 (en) * | 2001-07-03 | 2003-02-20 | Osborn Brock Estel | Interactive graphics-based analysis tool for visualizing reliability of a system and performing reliability analysis thereon |
| CN101655787A (en) * | 2009-02-24 | 2010-02-24 | 天津大学 | Threat modeling method added with attack path formalization analysis |
| US20100125746A1 (en) * | 2007-02-08 | 2010-05-20 | Herrmann Juergen | Method and system for determining reliability parameters of a technical installation |
| CN102147889A (en) * | 2011-03-28 | 2011-08-10 | 北京航空航天大学 | System maintenance time distribution method based on operation decomposition |
| CN104881609A (en) * | 2015-05-29 | 2015-09-02 | 中国石油大学(华东) | Credibility evaluation method of software unit of complex software system |
| US20170126472A1 (en) * | 2015-11-02 | 2017-05-04 | Servicenow, Inc. | System and Method for Processing Alerts Indicative of Conditions of a Computing Infrastructure |
| CN106960065A (en) * | 2016-01-11 | 2017-07-18 | 北京仿真中心 | The robust appraisal procedure and system of a kind of Complex simulation systems confidence level |
| CN107169635A (en) * | 2017-04-26 | 2017-09-15 | 中车株洲电力机车研究所有限公司 | A kind of man-machine system reliability index decomposes distribution method and appraisal procedure |
| CN109460214A (en) * | 2018-11-06 | 2019-03-12 | 上海航天测控通信研究所 | Spacecraft software configuration method based on IDEF modeling |
| CN110704986A (en) * | 2019-10-18 | 2020-01-17 | 重庆大学 | Mechanical system reliability distribution method based on minimum variability OWGA and fuzzy DEMATEL |
| CN111679972A (en) * | 2020-05-20 | 2020-09-18 | 北京航空航天大学 | Software system reliability prediction method, device, computer equipment and storage medium |
| CN111949425A (en) * | 2020-08-13 | 2020-11-17 | 中国科学院空间应用工程与技术中心 | System accelerated verification test method based on fuzzy analytic hierarchy process |
| CN112016239A (en) * | 2020-07-07 | 2020-12-01 | 中国科学院西安光学精密机械研究所 | Method for rapidly solving system reliability based on dynamic Bayesian network |
-
2020
- 2020-12-09 CN CN202011426099.3A patent/CN112558927B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030034995A1 (en) * | 2001-07-03 | 2003-02-20 | Osborn Brock Estel | Interactive graphics-based analysis tool for visualizing reliability of a system and performing reliability analysis thereon |
| US20100125746A1 (en) * | 2007-02-08 | 2010-05-20 | Herrmann Juergen | Method and system for determining reliability parameters of a technical installation |
| CN101655787A (en) * | 2009-02-24 | 2010-02-24 | 天津大学 | Threat modeling method added with attack path formalization analysis |
| CN102147889A (en) * | 2011-03-28 | 2011-08-10 | 北京航空航天大学 | System maintenance time distribution method based on operation decomposition |
| CN104881609A (en) * | 2015-05-29 | 2015-09-02 | 中国石油大学(华东) | Credibility evaluation method of software unit of complex software system |
| US20170126472A1 (en) * | 2015-11-02 | 2017-05-04 | Servicenow, Inc. | System and Method for Processing Alerts Indicative of Conditions of a Computing Infrastructure |
| CN106960065A (en) * | 2016-01-11 | 2017-07-18 | 北京仿真中心 | The robust appraisal procedure and system of a kind of Complex simulation systems confidence level |
| CN107169635A (en) * | 2017-04-26 | 2017-09-15 | 中车株洲电力机车研究所有限公司 | A kind of man-machine system reliability index decomposes distribution method and appraisal procedure |
| CN109460214A (en) * | 2018-11-06 | 2019-03-12 | 上海航天测控通信研究所 | Spacecraft software configuration method based on IDEF modeling |
| CN110704986A (en) * | 2019-10-18 | 2020-01-17 | 重庆大学 | Mechanical system reliability distribution method based on minimum variability OWGA and fuzzy DEMATEL |
| CN111679972A (en) * | 2020-05-20 | 2020-09-18 | 北京航空航天大学 | Software system reliability prediction method, device, computer equipment and storage medium |
| CN112016239A (en) * | 2020-07-07 | 2020-12-01 | 中国科学院西安光学精密机械研究所 | Method for rapidly solving system reliability based on dynamic Bayesian network |
| CN111949425A (en) * | 2020-08-13 | 2020-11-17 | 中国科学院空间应用工程与技术中心 | System accelerated verification test method based on fuzzy analytic hierarchy process |
Non-Patent Citations (3)
| Title |
|---|
| KEWEN LI ET.AL: "A novel reliability analysis approach for component-based software based on the complex network theory", 《SOFTWARE:TESTING, VERIFICATION AND RELIABILITY》, vol. 28, no. 6, pages 1 - 13 * |
| 杨宏伟等: "网络结构的软件系统可靠性分配方法", 《微型机与应用》, vol. 31, no. 19, pages 8 - 11 * |
| 林彦宇等: "提升大规模集群上并行计算软件系统可靠性和服务性的方法与实践", 《计算机工程与科学》, vol. 37, no. 1, pages 1 - 6 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116225949A (en) * | 2023-03-08 | 2023-06-06 | 安徽省软件评测中心 | Software reliability acceptance risk assessment method |
| CN116225949B (en) * | 2023-03-08 | 2023-11-10 | 安徽省软件评测中心 | Software reliability acceptance risk assessment method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112558927B (en) | 2024-02-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109376924A (en) | A kind of method, apparatus, equipment and the readable storage medium storing program for executing of material requirements prediction | |
| US20130024167A1 (en) | Computer-Implemented Systems And Methods For Large Scale Automatic Forecast Combinations | |
| CN115796372A (en) | Supply chain management optimization method and system based on SCOR | |
| CN106708738B (en) | Software test defect prediction method and system | |
| CN116955092B (en) | Multimedia system monitoring method and system based on data analysis | |
| CN108170769A (en) | A kind of assembling manufacturing qualitative data processing method based on decision Tree algorithms | |
| CN110690701A (en) | Analysis method for influence factors of abnormal line loss | |
| CN115641162A (en) | Prediction data analysis system and method based on construction project cost | |
| Marie et al. | Boosting schema matchers | |
| CN113408548A (en) | Transformer abnormal data detection method and device, computer equipment and storage medium | |
| CN112084220B (en) | Abnormality diagnosis method and device for electric energy metering device and readable storage medium | |
| CN112785108A (en) | Power grid operation data correlation analysis method and system based on regulation cloud | |
| CN111860624A (en) | Power grid fault information classification method based on decision tree | |
| CN114741457A (en) | Data missing value filling method based on function dependence and clustering | |
| CN118296561B (en) | Mixed early warning method and system based on equipment state data integration | |
| CN113761032A (en) | Aeroengine fault diagnosis method and system based on extension association rule mining | |
| CN112558927A (en) | Software reliability index distribution method and device based on layer-by-layer decomposition method | |
| CN116777284A (en) | Space and attribute data integrated quality inspection method | |
| CN117371861B (en) | Digital-based household service quality intelligent analysis method and system | |
| Poghosyan et al. | Managing cloud infrastructures by a multi-layer data analytics | |
| CN117667585B (en) | Operation and maintenance efficiency evaluation method and system based on operation and maintenance quality management database | |
| Denaro et al. | Towards industrially relevant fault-proneness models | |
| CN116644965A (en) | Visual analysis method and system for project budget | |
| CN111125078A (en) | Defect data correction method for relay protection device | |
| CN116187675A (en) | Task allocation method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |