CN1472652A - Software breakdown testing method for dynamic resouce management - Google Patents
Software breakdown testing method for dynamic resouce management Download PDFInfo
- Publication number
- CN1472652A CN1472652A CNA031784496A CN03178449A CN1472652A CN 1472652 A CN1472652 A CN 1472652A CN A031784496 A CNA031784496 A CN A031784496A CN 03178449 A CN03178449 A CN 03178449A CN 1472652 A CN1472652 A CN 1472652A
- Authority
- CN
- China
- Prior art keywords
- resource
- res
- fault
- dynamic
- program
- 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
- 238000012360 testing method Methods 0.000 title claims description 15
- 230000015556 catabolic process Effects 0.000 title description 2
- 238000001514 detection method Methods 0.000 claims abstract description 40
- 238000011084 recovery Methods 0.000 claims abstract description 13
- 238000004458 analytical method Methods 0.000 claims abstract description 9
- 238000000034 method Methods 0.000 claims description 33
- 230000000295 complement effect Effects 0.000 claims description 2
- 239000012467 final product Substances 0.000 claims description 2
- 238000005516 engineering process Methods 0.000 description 7
- 238000013522 software testing Methods 0.000 description 5
- 238000011156 evaluation Methods 0.000 description 3
- 238000010998 test method Methods 0.000 description 3
- 201000004569 Blindness Diseases 0.000 description 2
- 241001061076 Melanonus zugmayeri Species 0.000 description 2
- 235000000332 black box Nutrition 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 239000000203 mixture Substances 0.000 description 2
- 238000011002 quantification Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000008030 elimination Effects 0.000 description 1
- 238000003379 elimination reaction Methods 0.000 description 1
- 238000005206 flow analysis Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The detection method includes application fault detection of resource, illegal use detection of resource, recovery fault detection of resource and program illegal close detection. The software fault model faced for dynamic resource management is submitted based on analysis to a large number of fault program and the detection method for various fault type can be worked out based on it.
Description
Technical field
The present invention relates to technical field of software engineering, particularly involvement aspect is to the software fault detecting method of dynamic resource management, especially relate to software fault modeling and modeled software fault detection technique in the software testing technology, it is a highly effective quantification method of testing that improves the computer software reliability.
Background technology
In computer system, the existence of software error be cause that system breaks down, the one of the main reasons of inefficacy even system crash.For reducing the appearance of unexpected situation in system's operational process, improve the reliability in system's operational process, it is an important link must carrying out in the soft project that system is tested fully.Compare with hardware testing, software testing technology also is not very ripe, and outstanding characteristics are that hardware testing has comparatively perfect fault model, and the existence of these fault models is to the good directive function of having played of test job.
Existing software testing technology can be divided into: white-box testing, Black-box Testing and their method of testings such as mixing use.Common white-box testing method has, statement covering, branch's covering, path covering etc.; The Black-box Testing method has equivalence class division, boundary value analysis, mistake to infer method, cause-and-effect diagram, functional diagram etc.The generation of these method of testings is to the good impetus of having played of software test work.But, owing to there is not the sophisticated software testing standard, there is not a software fault model that can effectively quantize to test effect, cause software test work to exist very big blindness, therefore, also be difficult to software test work is estimated accurately.
The reliability that another problem relevant with software test is software, i.e. the probability of software true(-)running under specified criteria, given environment, it and software testing technology interwoveness.Software reliability is a factor of evaluation software quality, and its evaluation work also is the important goal that soft project is paid close attention to.Instruct because software test lacks unified standard, make the effect of software reliability evaluation work, software reliability evaluation be subjected to very big influence, the credibility of software evaluation is difficult to be guaranteed.
Summary of the invention
The present invention by to exist in the software systems, analyze by the reason of the caused thrashing of dynamic resource management, the dynamic resource management pattern has been proposed and towards the software fault model of dynamic resource management.The dynamic resource management pattern has fully reflected the characteristics of the dynamic management of computer resource, towards the software fault model description of dynamic resource management the dynamic resource management mode that causes system to make mistakes, with this model serves as to instruct to carry out the blindness that software test can reduce software test greatly, effectively get rid of the mistake that exists in the software, thereby can reduce the probability that fault takes place in system's operational process, improve the reliability of system.
Of the present inventionly be to provide a kind of software fault detection method to be achieved through the following technical solutions the present invention towards dynamic resource management.
A kind ofly tie towards the dynamic resource management pattern, dynamic resource management begins S (p) by program, resources allocation A (res), resource is used U (res), resource reclaims R (res) and EOP (end of program) E (p) forms, the use of dynamic resource must be followed following processes: program begins S (p) and carries out resources allocation A (res) afterwards, on the result to resources allocation carries out basis that correctness detects, carry out resource and use U (res), preceding at EOP (end of program) E (p), must carry out the recovery R (res) of resource, wherein, the distribution of resource in resource management process, use, recovery is a repeatably process.
Description of drawings
Fig. 1 is a dynamic resource management mode chart of the present invention, and it has described the pattern of dynamic resource management, can take out software fault model based on dynamic resource management from this figure.
Fig. 2 is the control flow graph of program.5 nodes among the figure are represented 5 fundamental blocks in the example procedure respectively, and the line among the figure is represented the ordinal relation between each fundamental block, and the piece of arrow tail association is the forerunner of the associated piece of arrow.For any software, all there is a control flow graph.The control flow graph is the foundation that method for testing software is implemented.
The improper of the management of dynamic resource is a crucial reason that causes software fault.Provided the dynamic resource management pattern in the accompanying drawing 1, it is described the dynamic resource management mode in the program, comprising rational resource use-pattern and irrational resource use-pattern, on this basis, we have set up the software fault model towards dynamic resource management, and this model has reflected dynamic resource management mistake caused software error potential in the software running process.With this model is guidance, this patent has further provided fault detect and elimination technique correspondingly, it can effectively reduce the leak of the dynamic resource management that exists in the software, reduces the factor that causes system to make mistakes, and improves the reliability in the software running process.
1, towards the software fault model of dynamic resource management
The software utilizable computer resource that is in operation has mainly comprised some real resources and virtual resource, the former is as the various hardware resources (as CPU, hard disk, internal memory, IO etc.) and the software resource (as data file, dynamic code, service processes etc.) of computing machine, also has more virtual resource (as process handle, call number, communication port etc.) in addition, the latter is more abstract relatively, 15 identification card number for example, it is an important resource equally, along with people constantly apply for and can not reuse, having one day also can approach exhaustion; 32 IP address is also facing exhausted danger.These more abstract resources also will be considered as also needing to carry out unified effectively dynamic management with the same such as internal memory in this patent.
We need the resource of dynamic management call dynamic resource to these in operational process, provided the user mode transition graph of dynamic resource management as Fig. 1, wherein, thick line is represented a rational dynamic resource management chain, the resource management chain that fine rule expresses possibility and can cause thrashing, briefly, the use of all dynamic resources all must be experienced correct application and releasing operation, otherwise it is invalid to be considered as, and different fault (concrete formization about fault model is defined as follows literary composition) promptly occurs.For example modal internal memory dynamic management just need meet such process, promptly must there be effectively application operation before use, and before EOP (end of program), also must carry out the recovery operation of resource, if misoperation may cause using serious software faults such as illegal memory, internal memory leakage, memory overwriting.The correct management of dynamic resource is that good program design has brought convenience, but is again a very very difficult thing for larger design, and more unfortunately, this important task is often given different programmers and oneself finished.
In fact, this because dynamic resource management improper and cause fault to account for the very big part of software total breakdown, this also is the problem to be solved that the present invention wants modelling and realizes detecting automatically, for the sake of clarity, provides the formalization definition of various fault types below.
It has mainly utilized the control flow graph (CFG) of program and has quoted the detection that definite value information etc. is carried out software error, belongs to the white-box testing technology.By the software that these fault model projects detect, its stability and robustness all can be improved significantly.According to the dynamic resource fault model that is provided in the claim 2, mainly contain following several fault detection method.
According to Fig. 1, reasonably the resource management chain may be summarized to be following pattern:
S(p)
→{A(res)
→{U(res)}
→R(res)}
→E(p)
S (p): program begins A (res): resources allocation U (res): resource is used R (res): resource reclaims E (p): EOP (end of program)
Its main process is to begin S (p) from program and begin to use U (res) to reclaim R (res) at last to EOP (end of program) E (p) to resource to resources allocation A (res) through resource.
We have provided the following software fault model towards dynamic resource management based on top fault mode.1. resource bid fault
In Fig. 1, exist from U (res) to A (res) and the back edge of U (res) itself, the resource bid mistake has been represented in the existence of these two lines.In the resources allocation stage, if same resource was carried out duplicate allocation before not reclaiming, perhaps, after resources allocation, allocation result is not checked (UC (A)), all can cause mistake.Can obtain the fault model of following resource bid thus:
res, (A (res) UC (A)) or (﹁ R (res) A (res)) is the illegal operational failure of resource 2.
In Fig. 1, exist S (p) and R (p) to two limits of U (p), the unappropriated use of dynamic resource is represented on these two limits, or the reusing of the dynamic resource after being recovered, both of these case all can cause the illegal use of resource, and this error model can be described as following form:
res, (﹁ A (res) U (res)) or (R (res) U (res)) is the resource recovery failure 3.
In Fig. 1, exist from S (the p) is to the line of R (res) and the back edge of R (res) itself, and these two lines have represented to cause resource to reclaim wrong reason, and this error model can be described as following form:
res, (﹁ A (res) R (res)) or (R (res) R (res)) 4. program illegally finishes fault
In Fig. 1, (the res) is to the illegal end of two line representation programs of E (p) from A (res) and U in existence, these two lines represent that a resource do not carrying out reclaimer operation through over-allocation or after using, and therefore, causing the illegal mistake that finishes of program mainly is the not recovery mistake of resource.Can be with following model representation:
res，(A(res)﹁R(res))or(U(res)﹁R(res))
2, modeled software fault detection method
This detection towards the dynamic resource management fault model is to belong to white-box testing, and it reaches the purpose of fault detect by the analysis to the source code of software, provides the parameter of quantification of a reliability of software simultaneously.This detection technique is based on data-flow analysis, before specifically detecting, at first need the control flow graph (CFG) of software source procedure division for constituting by fundamental block, at first provide its building method below: it has mainly utilized the control flow graph (CFG) of program and has quoted the detection that definite value information etc. is carried out software error, belongs to the white-box testing technology.By the software that these fault model projects detect, its stability and robustness all can be improved significantly.Mainly contain following several fault detection method:
Fundamental block is a statement sequence of carrying out in order, wherein has only an entry statement and an exit statement.Wherein, entry statement is the statement that meets following characteristics:
1. first statement of program;
2. the statement that diverts the aim of conditional branch statement or unconditional transfer statement;
3. immediately following the statement after conditional branch statement.
Fig. 2 has provided the control flow graph of a simple program, and the node among the figure is represented a fundamental block, and the follow-up relation of the forerunner between the fundamental block is represented on the limit, and the piece of arrow tail association is the forerunner of the associated piece of arrow.
In software program, except the operation of carrying out resources allocation, also may occur quoting identical resource with different names, thereby the another name of setting up between the different variablees concerns with the realizations such as assign operation between pointer variable.Call the difficulty that test job brings that appears as of relation.Be the convenience of dealing with problems, we have set up one group of variable that the another name group represents to have the another name relation.For a fundamental block, the set (INA) of the another name group that arrives the fundamental block inlet and the set (OUTA) of the another name group that the arrival fundamental block exports are all arranged, and their satisfied following relations, wherein, KILL represents the set of deleted another name group, and NEW represents the set of newly-established another name group:
The INA=∪ of each fundamental block (this fundamental block institute and forerunner) OUTA;---(1)
The INA ∪ NEW-KILL of this fundamental block of OUTA=of each fundamental block.——(2)
We can carry out detailed discussion: the detection of 1) resource bid fault below by alias analysis being realized the detection of above software fault
For the detection of dynamic resource application fault, need to check whether the resource that is applied has been assigned with the reference pointer variable whether point to the resource that does not discharge, this is that above analysis about another name is adequate.(1) management of system resource is generally finished by operating system, so the composition that this respect user can intervene is less, but, can reach the purpose of detection by the corresponding relation of checking all another name groups and various resources.(2) if in the set of another name group, have the another name group that comprises this variable, and should only comprise this variable itself in the another name group, represent that then this resource is assigned with or is used, new resource bid operation can cause losing of the resource that existed, thereby detects the resource bid mistake.
Distribution in this resource of expression can cause losing of the resource that existed, report a unappropriated mistake of resource, if should comprise a plurality of variablees in the another name group, and this variable of deletion in the another name group then, the another name that stops between this variable and this another name group concerns; If in the set of another name group, do not have the another name group that comprises this variable, then set up a new another name group, simultaneously this newly-built another name group is joined among the NEW; 2) detection of the illegal operational failure of resource
Whether the illegal use of resource at first needs to detect every resource and correctly applies in use, need using and applying for that the authority of this resource does not match of resource then, for example applied for reading the handle of file operation, if it is carried out write operation, obviously be wrong, here, we also classify as this type to the fault of crossing the border such as data, mainly are because it is just can show to the use of resource the time.
Concrete detection method is: (1) in fact can carry out alias analysis by each variable from fundamental block, determines whether to exist the another name set to get final product; (2) also require simultaneously in the assigning process of dynamic resource according to concrete needs operating right, like this, for detecting this class mistake, in the process that the control flow graph to program scans, the operating right of this resource specified in record, thereby and check successively whether follow-up operation is complementary with due authority and detect illegal operating position this resource; In addition, we incite somebody to action not, and the use mistake of initializaing variable also detects at this moment, promptly, for each variable that is cited in each fundamental block, if in this fundamental block, there is not definite value to this variable, and be not included in the another name group of the inlet INA that arrives this fundamental block at this variable yet, can determine this variable before quoting not by definite value, thereby the not assignment that can detect variable no initializtion, variable such as quotes at the mistake of the illegal use of resource.3) detection of resource recovery failure
Can know that from the analysis of front the recovery failure of resource mainly occurs in the situation that attempt is reclaimed or repeatedly reclaimed the resource of not applying for, this is the fault that is easy to produce in the extensive software.Its testing can be carried out so like this: in the reclaimer operation process of resource, if in the another name group set that arrives this fundamental block inlet, do not exist and comprise resource to be recycled, show that then this resource has been recovered or not application as yet, show that then the type fault takes place; If in the set of another name group, have the another name group that comprises resource to be recycled, should the another name group be added in the KILL set, illustrate and reclaim successfully; Otherwise show that this resource has just reclaimed or not application as yet, show that then the type fault takes place.4) program illegally finishes the detection of fault
Detection requirement all dynamic resources before EOP (end of program) of this fault type must correctly discharge, this is a kind of fault type that is worth conferring, because EOP (end of program), system generally can reclaim all resources that this program takies automatically, discuss but still it is used as fault here.Its detection method is: before EOP (end of program), if having the another name group that arrives the fundamental block outlet is non-NULL, there is undelivered resource in the expression system, then illustrate and exist the chain rupture phenomenon in the resource management process, therefore, by being detected, the another name group set that arrives the fundamental block outlet can find this class mistake.Whether the another name group that the fault detect of this class resource is equivalent to the outlet of asking last fundamental block is empty operation.
Claims (8)
1, a kind ofly tie towards the dynamic resource management pattern, dynamic resource management begins S (p) by program, resources allocation A (res), resource is used U (res), resource reclaims R (res) and EOP (end of program) E (p) forms, the use of dynamic resource must be followed following processes: program begins S (p) and carries out resources allocation A (res) afterwards, on the result to resources allocation carries out basis that correctness detects, carry out resource and use U (res), preceding at EOP (end of program) E (p), must carry out the recovery R (res) of resource, wherein, the distribution of resource in resource management process, use, recovery is a repeatably process.
2, towards the software fault model of dynamic resource management, this fault model is based on the dynamic resource management pattern, and all fault types in the dynamic resource management process have been related to, simultaneously, it is again the basis of fault detection technique proposed by the invention, can seeing of right to analysis requirement 1 towards the dynamic resource management mode configuration, in the process of dynamic resource management, in the four-stage except that program begins, all may exist the mistake of resource management, position according to mistake occurs exists following four kinds of software faults.
3, according to claim 1 towards the dynamic resource management mode configuration, it is characterized in that, resource bid fault: exist from U (res) to A (res) and the back edge of U (res) itself, the resource bid mistake has been represented in the existence of these two lines, promptly in the resources allocation stage, if same resource was carried out duplicate allocation before not reclaiming, perhaps, after resources allocation, allocation result is not checked (UC (A)), all can cause mistake; Can obtain the fault model of following resource bid thus:
res，(A(res)UC(A))or(﹁R(res)A(res))
4, according to claim 1 towards the dynamic resource management mode configuration, it is characterized in that, the illegal operational failure of resource: have S (p) and R (p) two limits to U (p), the unappropriated use of dynamic resource is represented on these two limits, or the reusing of the dynamic resource after being recovered, both of these case all can cause the illegal use of resource, and this error model can be described as following form:
res，(﹁A(res)U(res))or(R(res)U(res))
5, according to claim 1 towards the dynamic resource management mode configuration, it is characterized in that, resource recovery failure: exist that (the p) is to the line of R (res) and the back edge of R (res) itself from S, these two lines have represented to cause resource to reclaim wrong reason, and this error model can be described as following form:
res，(﹁A(res)R(res))or(R(res)R(res))
6, according to claim 1 towards the dynamic resource management mode configuration, it is characterized in that, program illegally finishes fault: have that (the res) is to the illegal end of two line representation programs of E (p) from A (res) and U, these two lines represent that a resource do not carrying out reclaimer operation through over-allocation or after using, therefore, causing the illegal mistake that finishes of program mainly is the not recovery mistake of resource, can be with following model representation:
res，(A(res)﹁R(res))or(U(res)﹁R(res))
7, a kind of fault detection method towards dynamic resource management utilizes the control flow graph (CFG) of program and quotes the detection that definite value information is carried out software error, mainly contains following several fault detection method: the detection of 1) resource bid fault
Detection for dynamic resource application fault, need to check whether the resource that is applied has been assigned with the reference pointer variable whether point to the resource that does not discharge, can be by checking all another name groups and the corresponding relation of various resources, if in the set of another name group, have the another name group that comprises this variable, and should only comprise this variable itself in the another name group, represent that then this resource is assigned with or is used, new resource bid operation can cause losing of the resource that existed, thereby detects the resource bid mistake.2) detection of the illegal operational failure of resource
Whether the illegal use of resource at first needs to detect every resource and correctly applies in use, need using and applying for that the authority of this resource does not match of resource then, concrete detection method is: (1) can carry out alias analysis by each variable from fundamental block, determines whether to exist the another name set to get final product; (2) also require simultaneously in the assigning process of dynamic resource according to concrete needs operating right, like this, for detecting this class mistake, in the process that the control flow graph to program scans, the operating right of this resource specified in record, thereby and check successively whether follow-up operation is complementary with due authority and detect illegal operating position this resource; In addition, the use mistake of initializaing variable is not also detected at this moment, promptly, for each variable that is cited in each fundamental block, if in this fundamental block, there is not definite value to this variable, and be not included in the another name group that arrives this fundamental block inlet at this variable yet, can determine this variable before quoting not by definite value, thereby the not assignment that can detect variable no initializtion, variable such as quotes at the mistake of the illegal use of resource; 3) detection of resource recovery failure
In the reclaimer operation process of resource, do not comprise resource to be recycled if in the another name group set that arrives this fundamental block inlet, do not exist, show that then this resource has been recovered or not application as yet, show that then the type fault takes place; 4) program illegally finishes the detection of fault
Detection requirement all dynamic resources before EOP (end of program) of this fault type must correctly discharge, its detection method is: before EOP (end of program), if there is the another name group non-NULL that arrives the fundamental block outlet, there is undelivered resource in the expression system, then illustrate and exist the chain rupture phenomenon in the resource management process, therefore, by being detected, the another name group set that arrives the fundamental block outlet can find this class mistake.
8, according to the software fault detection method towards dynamic resource management of claim 7, it is characterized in that detection is to belong to white-box testing.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB031784496A CN1310151C (en) | 2003-07-17 | 2003-07-17 | Software breakdown testing method for dynamic resouce management |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB031784496A CN1310151C (en) | 2003-07-17 | 2003-07-17 | Software breakdown testing method for dynamic resouce management |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1472652A true CN1472652A (en) | 2004-02-04 |
| CN1310151C CN1310151C (en) | 2007-04-11 |
Family
ID=34157082
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB031784496A Expired - Lifetime CN1310151C (en) | 2003-07-17 | 2003-07-17 | Software breakdown testing method for dynamic resouce management |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1310151C (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1295615C (en) * | 2004-12-20 | 2007-01-17 | 华中科技大学 | Distribution type software reliability evaluation system having time restraint |
| CN101546290B (en) * | 2009-04-30 | 2010-09-29 | 上海交通大学 | Method for improving accuracy of quality forecast of class hierarchy in object-oriented software |
| CN101308457B (en) * | 2008-06-20 | 2011-05-18 | 北京大学 | User feedback reliability guaranteeing method |
| CN102393833A (en) * | 2011-10-17 | 2012-03-28 | 哈尔滨工业大学 | Component software reliability analysis method capable of considering limitation of debugging resources based on HFSQM (Hybrid Finite Server Queuing Model) |
| CN101432754B (en) * | 2006-04-12 | 2013-04-17 | 株式会社Ntt都科摩 | Software operation modeling device, software operation monitoring device, software operation modeling method, and software operation monitoring method |
| CN103646129A (en) * | 2013-11-22 | 2014-03-19 | 中国科学院计算技术研究所 | Reliability assessment method and device applied to FPGA |
| CN104915785A (en) * | 2015-06-16 | 2015-09-16 | 国网安徽省电力公司 | Power grid enterprise renewable resource price evaluation method based on social fair value |
| CN105553745A (en) * | 2016-01-07 | 2016-05-04 | 烽火通信科技股份有限公司 | Automatic testing method and device for complex networking of communication equipment |
| CN108052404A (en) * | 2017-12-07 | 2018-05-18 | 郑州云海信息技术有限公司 | A kind of data address error-detection mechanism in server interconnection chip |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009020868A2 (en) | 2007-08-04 | 2009-02-12 | Rezzorb, Llc | Method and apparatus for reducing fertilizer use in agricultural operations |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4926427A (en) * | 1986-09-30 | 1990-05-15 | Siemens Aktiengesellschaft | Software error detection apparatus |
-
2003
- 2003-07-17 CN CNB031784496A patent/CN1310151C/en not_active Expired - Lifetime
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1295615C (en) * | 2004-12-20 | 2007-01-17 | 华中科技大学 | Distribution type software reliability evaluation system having time restraint |
| CN101432754B (en) * | 2006-04-12 | 2013-04-17 | 株式会社Ntt都科摩 | Software operation modeling device, software operation monitoring device, software operation modeling method, and software operation monitoring method |
| CN101308457B (en) * | 2008-06-20 | 2011-05-18 | 北京大学 | User feedback reliability guaranteeing method |
| CN101546290B (en) * | 2009-04-30 | 2010-09-29 | 上海交通大学 | Method for improving accuracy of quality forecast of class hierarchy in object-oriented software |
| CN102393833B (en) * | 2011-10-17 | 2014-03-26 | 哈尔滨工业大学 | Component software reliability analysis method capable of considering limitation of debugging resources based on HFSQM (Hybrid Finite Server Queuing Model) |
| CN102393833A (en) * | 2011-10-17 | 2012-03-28 | 哈尔滨工业大学 | Component software reliability analysis method capable of considering limitation of debugging resources based on HFSQM (Hybrid Finite Server Queuing Model) |
| CN103646129A (en) * | 2013-11-22 | 2014-03-19 | 中国科学院计算技术研究所 | Reliability assessment method and device applied to FPGA |
| CN103646129B (en) * | 2013-11-22 | 2017-04-12 | 中国科学院计算技术研究所 | Reliability assessment method and device applied to FPGA |
| CN104915785A (en) * | 2015-06-16 | 2015-09-16 | 国网安徽省电力公司 | Power grid enterprise renewable resource price evaluation method based on social fair value |
| CN104915785B (en) * | 2015-06-16 | 2018-06-19 | 国网安徽省电力公司 | Power grid enterprises' regenerated resources price evaluation method based on social fair value |
| CN105553745A (en) * | 2016-01-07 | 2016-05-04 | 烽火通信科技股份有限公司 | Automatic testing method and device for complex networking of communication equipment |
| CN105553745B (en) * | 2016-01-07 | 2018-07-24 | 烽火通信科技股份有限公司 | A kind of automated testing method and device of the networking of communication equipment complexity |
| CN108052404A (en) * | 2017-12-07 | 2018-05-18 | 郑州云海信息技术有限公司 | A kind of data address error-detection mechanism in server interconnection chip |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1310151C (en) | 2007-04-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101853200B (en) | High-efficiency dynamic software vulnerability exploiting method | |
| US20060253837A1 (en) | Using a call stack hash to record the state of a process | |
| CN109815704B (en) | Safety detection method and system for Kubernetes cloud native application | |
| CN1655123A (en) | Architecture and method for managing the sharing of logical resources among separate partitions of a logically partitioned computer system | |
| US20050289404A1 (en) | Hierarchical categorization of customer error reports | |
| CN111290958B (en) | Method and device for debugging intelligent contract | |
| Schroeder et al. | Generating expected results for automated black-box testing | |
| CN1472652A (en) | Software breakdown testing method for dynamic resouce management | |
| JP2017201470A (en) | Setting support program, setting support method, and setting support device | |
| CN110088744A (en) | A kind of database maintenance method and its system | |
| CN107621963B (en) | Software deployment method, software deployment system and electronic equipment | |
| CN112100625B (en) | Operating system access control vulnerability discovery method based on model detection | |
| CN111783094A (en) | Data analysis method and device, server and readable storage medium | |
| CN115659335A (en) | Block chain intelligent contract vulnerability detection method and device based on mixed fuzzy test | |
| US20240289450A1 (en) | Automated threat modeling using application relationships | |
| CN107329836A (en) | Multi-system memory management method and device and mobile terminal | |
| CN111752819A (en) | Abnormity monitoring method, device, system, equipment and storage medium | |
| CN109254791A (en) | Develop management method, computer readable storage medium and the terminal device of data | |
| CN112506802A (en) | Test data management method and system | |
| Yang et al. | Hybrid fault diagnosability with unreliable communication links | |
| CN1609788A (en) | Drive program strengthening method for inserting operation system | |
| CN115373929A (en) | Test method, device, equipment, readable storage medium and program product | |
| Hagen et al. | Towards solid it change management: Automated detection of conflicting it change plans | |
| Cao et al. | Research on reliability evaluation of big data system | |
| CN111404715B (en) | Network service instantiation method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| ASS | Succession or assignment of patent right |
Owner name: CLOUD COMPUTING INDUSTRIAL TECHNOLOGY INNOVATION A Free format text: FORMER OWNER: INSTITUTE OF COMPUTING TECHNOLOGY, CHINESE ACADEMY OF SCIENCES Effective date: 20140509 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: 100080 HAIDIAN, BEIJING TO: 523808 DONGGUAN, GUANGDONG PROVINCE |
|
| TR01 | Transfer of patent right |
Effective date of registration: 20140509 Address after: 14 No. 523808 Keyuan pine in Guangdong Province, Dongguan Songshan Lake high tech Industrial Development Zone Patentee after: CLOUD COMPUTING CENTER CHINESE ACADEMY OF SCIENCES Address before: 100080 No. 6 South Road, Zhongguancun Academy of Sciences, Beijing Patentee before: Institute of Computing Technology, Chinese Academy of Sciences |
|
| ASS | Succession or assignment of patent right |
Owner name: GUANGDONG ZHONGKE YUNFU VENTURE CAPITAL CO., LTD. Free format text: FORMER OWNER: CLOUD COMPUTING INDUSTRIAL TECHNOLOGY INNOVATION AND INCUBATION CENTER CHINESE ACADEMY OF SCIENCES DONGGUAN Effective date: 20150827 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20150827 Address after: 523808 Guangdong province Dongguan Songshan Lake high tech Industrial Development Zone No. 14 Keyuan pine floor 3 floor Room 305 Patentee after: Guangdong Zhongke Yunfu Venture Investment Co.,Ltd. Address before: 14 No. 523808 Keyuan pine in Guangdong Province, Dongguan Songshan Lake high tech Industrial Development Zone Patentee before: CLOUD COMPUTING CENTER CHINESE ACADEMY OF SCIENCES |
|
| CB03 | Change of inventor or designer information |
Inventor after: Li Xiaowei Inventor after: Xu Yongjun Inventor after: Zhang Guangmei Inventor before: Zhang Guangmei Inventor before: Xu Yongjun Inventor before: Li Xiaowei |
|
| CB03 | Change of inventor or designer information | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20170815 Address after: 22 No. 334000 Jiangxi city of Shangrao province Xinzhou District Chaoyang Road Patentee after: Shangrao Zhongke letter cloud industry information technology Co.,Ltd. Address before: 523808 Guangdong province Dongguan Songshan Lake high tech Industrial Development Zone No. 14 Keyuan pine floor 3 floor Room 305 Patentee before: Guangdong Zhongke Yunfu Venture Investment Co.,Ltd. |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20210817 Address after: 523000 room 2304, building 1, No. 1, Kehui Road, Songshanhu Park, Dongguan City, Guangdong Province Patentee after: Guangdong Zhongke Yunfu Venture Investment Co.,Ltd. Address before: No.22 Chaoyang Avenue, Xinzhou District, Shangrao City, Jiangxi Province Patentee before: Shangrao Zhongke letter cloud industry information technology Co.,Ltd. |
|
| TR01 | Transfer of patent right | ||
| CX01 | Expiry of patent term |
Granted publication date: 20070411 |
|
| CX01 | Expiry of patent term |