CN106776208A - Fault Locating Method during a kind of running software - Google Patents
Fault Locating Method during a kind of running software Download PDFInfo
- Publication number
- CN106776208A CN106776208A CN201611102015.4A CN201611102015A CN106776208A CN 106776208 A CN106776208 A CN 106776208A CN 201611102015 A CN201611102015 A CN 201611102015A CN 106776208 A CN106776208 A CN 106776208A
- Authority
- CN
- China
- Prior art keywords
- software
- software systems
- result
- running
- property specification
- 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 57
- 239000000523 sample Substances 0.000 claims abstract description 28
- 238000012544 monitoring process Methods 0.000 claims abstract description 11
- 238000001514 detection method Methods 0.000 claims description 18
- 238000012360 testing method Methods 0.000 claims description 17
- 230000008569 process Effects 0.000 claims description 11
- 230000006870 function Effects 0.000 claims description 10
- 238000004458 analytical method Methods 0.000 claims description 8
- 150000001875 compounds Chemical class 0.000 claims description 6
- 239000011159 matrix material Substances 0.000 claims description 6
- 230000001174 ascending effect Effects 0.000 claims description 3
- 238000004364 calculation method Methods 0.000 claims description 3
- 230000004888 barrier function Effects 0.000 claims description 2
- 230000008859 change Effects 0.000 abstract description 8
- 230000003068 static effect Effects 0.000 abstract description 7
- 238000007619 statistical method Methods 0.000 abstract description 3
- 238000012795 verification Methods 0.000 description 12
- 238000005516 engineering process Methods 0.000 description 5
- 238000005457 optimization Methods 0.000 description 3
- 230000002123 temporal effect Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 2
- 238000004880 explosion Methods 0.000 description 2
- 230000008439 repair process Effects 0.000 description 2
- 206010000117 Abnormal behaviour Diseases 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000003542 behavioural effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 235000013399 edible fruits Nutrition 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012806 monitoring device Methods 0.000 description 1
- 238000004321 preservation Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides Fault Locating Method during a kind of running software, the method includes static preparatory stage, dynamic operation stage and fault location stage；Wherein：In the static preparatory stage, i.e., before software systems operation, according to the high-rise requirement description of software systems, then deterministic nature stipulations insert code, deployment probe, and watch-dog during structure, running according to the property specification in software systems；In the dynamic operation stage, i.e. during running software, the change information of setting monitoring variable when inserting code acquisition software systems are run, watch-dog is according to the change information, software systems implementation status is made whether to meet the checking of property specification, the execution route of probe records software systems.In fault location stage, according to software execution route and watch-dog the result, carry out statistical analysis and realize software systems fault location.
Description
Technical field
The present invention relates to fault location side during a kind of software systems reliability consideration technical field, more particularly to running software
Method, monitors during for being run to software systems, realizes the fault location of software systems.
Background technology
Today's society, the use of computer software has been deep into different social sectors, such as to communication
System, aerospace vehicle, weaponry, financial and trading platform, command and control system etc., the core ground in social development
Position.Complication degree with software requirement increases, and software systems complexity in itself also becomes increasingly huge, thus makes
The possibility increase broken down into software systems and failed.Once core software system fails, can be to national economy, people
People's safety even national security causes greatly loss.Therefore, the need for the failure of software systems being accurately positioned and being diagnosed
Ask and also become further urgent.The fault location of software systems is most complicated in debugging system, repair system, time-consuming most long one
Content.
At present, scholars investigated some software systems automation Fault Locating Method, and these methods are mainly divided quiet
State method and dynamic approach.Static method is using the information such as dependence, type constraint of system Program come in analysis program
Possible breakdown point；Dynamic approach then by test system program, enter by the perform track and coverage information of tracking system program
Row fault location.Efficiently positioning fault of software be the selfreparing of software, self adaptation provide premise and guarantee.Though these methods
So fault location is solved the problems, such as to a certain extent, but effect is all less desirable, while existing method is seldom with reference to soft
Part run time behaviour information, it is difficult to accomplish fault location during running software.Therefore, how running software is accurately utilized as far as possible
When state change positioning fault of software position, as the focus studied in recent years.
The content of the invention
It is an object of the invention to overcome the deficiencies in the prior art, there is provided Fault Locating Method during a kind of running software,
The method is simply easily realized, applied widely, highly reliable, fault location accuracy rate is high, can be with effective guarantee software systems
It is credible.
Above-mentioned purpose of the invention is realized by following scheme：
Fault Locating Method during a kind of running software, comprises the following steps：
(1) the software system test requirement definition for, using stipulations definitional language to set is property specification；
(2), the corresponding script file of property specification is compiled and obtains event recognizer, and determine the event recognition
The inserting position of device；Then before software systems program is compiled, by code instrumentation instrument by the event recognizer
Corresponding code instrumentation is in software systems program；
(3) the corresponding LTL formula of software systems, are determined according to property specification, and it is using automaton theory that the LTL is public
Formula is converted into finite-state machine, watch-dog during as operation；
(4) key variables and Key Functions of software systems, are determined according to property specification, by the key variables and key
Probe is disposed in function position as detection node in the detection node；
(5), when software systems are run：The delta data of the monitoring variable of event recognizer collection setting, and be sent to
Watch-dog during operation；Watch-dog is verified to the delta data for monitoring variable during operation, judges that software systems implementation status is
It is no to meet property specification；The execution route of probe records software systems；
(6), repeat step (5), software systems are run M times, obtain M groups the result and software systems execution route；
(7), according to M groups the result and software systems execution route, count in each detection node break down time
Number, chooses trouble point of several positions of number of stoppages highest as software systems.
Fault Locating Method during above-mentioned running software, in step (1), using atomic event definitional language PDEL and multiple
Close the software system test demand of event definition language MEDL description settings, deterministic nature stipulations.
Fault Locating Method during above-mentioned running software, in step (5), watch-dog is to monitoring the change of variable during operation
Data are verified, judge whether software systems implementation status meets property specification, wherein：If running monitor judges software
System implementation status meets property specification, then it is 0 to export the result；If running monitor judges software systems implementation status
Property specification is not met, then it is 1 to export the result；If running monitor not can determine that whether software systems implementation status accords with
Property specification is closed, then sets the result invalid.
Fault Locating Method during above-mentioned running software, in step (5), the execution route of probe records software systems,
Concrete methods of realizing is as follows：In software systems implementation procedure, if carried out to the corresponding key variables of probe or Key Functions
Operation, then the probe output result is 1；After the completion of software systems execution, the vector that N number of probe value is constituted is used as soft
The execution route of part system；N is the probe sum of deployment in software systems.
Fault Locating Method during above-mentioned running software, in step (7), the trouble point of software systems specifically positions realization
Process is as follows：
(7a), M ' groups of effective the result is extracted in M group the results, i.e., described M ' groups effective the result is corresponding
Software systems execution route；M ' is the effectively software execution number of times of the result；
(7b) obtains software fault analysis matrix Q according to M ' groups of effective the result and software systems execution route：
Wherein：eiIt is i-th effective the result, if running monitor judges software systems, implementation status meets property
Stipulations, then ei=0, if running monitor judges that software systems implementation status does not meet property specification, ei=1；Xi=[xi1
xi2 … xij … xiN]TIt is the corresponding software systems execution route of i-th effective the result, if in software implementation procedure
By j-th detection node, then xij=1；I=1,2 ..., M ', j=1,2 ..., N, N be software systems in dispose probe it is total
Number；
(7c) occurs according to software fault analysis matrix Q when in Statistical software system implementation procedure by each detection node
The number of times of software fault, specific formula for calculation is as follows：
Wherein, αjTo there is the number of times of software fault when software systems are by j-th detection node；
(7d) is to α1、α2、…、αNIt is ranked up by ascending order, chooses the corresponding test point of preceding L value after sequence as soft
Part trouble point.
The present invention compared with prior art, with advantages below：
(1) the big analysis being all based on to static routine of traditional Fault Locating Method, the present invention is on the basis of existing method
On, it is proposed that Fault Locating Method during running software, monitoring and logging software running in software runtime environment, analyze soft
Execution state and result of the part in various running environment, carry out run time verification, and carry out event based on run time verification result
Barrier positioning, the method fault location is accurate, largely reduces fault location error rate；
(2) present invention is based on linear time temporal logic (LTL) and automaton theory configurations watch-dog, automatic by reducing
The mode of machine generation status number reduces the scale of final watch-dog, reduces the complexity of method realization；
(3) behavioural information when present invention is by running software is monitored, using sequential logic and automaton theory
The checking and analysis to the software action time of running are realized, because the current operation action of software is only focused on, and it is soft without considering
The all possible ruuning situation of part, thus be not in the state explosion problem of close copy detection, it is workable；
(4) present invention passes through watch-dog and software probe during the running software disposed, and judges whether software fault exposes, and
The program point that record each run path is passed through, by the method for statistical analysis, with reference to the result of run time verification, is carried out soft
The positioning of part failure, largely improves the accuracy rate of software systems failure.
Brief description of the drawings
Fault Locating Method process chart when Fig. 1 is running software of the invention；
Fig. 2 is LTL formula to B ü chi automatic machine flow path switch figures staggeredly.
Specific embodiment
The present invention is described in further detail with instantiation below in conjunction with the accompanying drawings：
The present invention carries out fault location using run time verification technology to software systems, and the technology is a kind of journey of lightweight
Sequence verification technique.Checking target of the invention is whether the actual motion of inspection software system has run counter to the property specification for setting.
Wherein, using the property specification of linear time temporal logic (Linear Temporal Logic) formula description setting, and as base
Plinth generates corresponding watch-dog.Watch-dog, watch-dog is generally produced to be checked by observing the execution of program from system requirements
Whether program operation process meets system requirements.Therefore, in operationally verifying, watch-dog can be defined as " reading finite fortune
Walking along the street footpath simultaneously provides the device of corresponding conclusion ".Compared with model testing, watch-dog generating process in run time verification be based on
Property automatic machine generating process is similar in the Model Checking of automaton theory, but run time verification is without the concern for system
All state spaces be possible to operating path, therefore avoid state explosion problem；Compared with test, run time verification has
A bit similar to the test (Oracle-based Testing) based on prophesy, i.e. watch-dog close to Test oracles (Test
Oracle), but run time verification without the concern for testing adequacy and coverage rate the problems such as.Run time verification technology not only can be with
The effective operating abnormal behaviour of detecting system, and cause detect when correctness deviates from effectively repair system into
It is possible.In addition, the mode present invention employs on-line monitoring is monitored to software systems, examined in a kind of progressive mode
Look into software systems ruuning situation, it is not necessary to the history perform track of record and preservation system, support can be provided for fault location.
Fault position method during running software of the invention, it is main to include static preparatory stage, dynamic operation stage and failure
Positioning stage, implements process as shown in Figure 1.
(1), the static preparatory stage
In the static preparatory stage, i.e., before software systems operation, according to the high-rise requirement description of software systems, certainty
Matter stipulations, then insert code, deployment probe, and watch-dog during structure, running according to the property specification in software systems.
(1) property specification, is defined
In the run time verification method frame of software-oriented system, event and condition be divided into atomic event and condition,
Two kinds of compound event and condition.Atomic event and condition are abstract by the variable in goal systems, method, and compound event
Do not contacted directly with variable, the method in goal systems then with condition, formed by atomic event and conditional combination.Therefore
The software system test demand that the present invention will be set using atomic event definitional language PDEL and compound event definitional language MEDL
Property specification is defined as, process is specifically defined as follows：Atomic event definitional language PDEL first by bottom is soft to being tested
Determinant attribute in part system and the elementary event and condition that are made up of these attributes are described, and obtain PDEL stipulations；Then
The compound event and condition that are made up of elementary event and condition are retouched using high-rise compound event definitional language MEDL
State, obtain MEDL stipulations；And define LTL property specifications to be verified, so as to by the high level test demand and bottom of software systems
Execution information is connected.
(2) code, is inserted
PEDL stipulations and MEDL stipulations are compiled, obtain can with acquisition software system operation when status information event
Identifier, and the event recognizer inserting position；Then before software systems program is compiled, by code instrumentation
Instrument by the corresponding code instrumentation of event recognizer in software systems program, i.e., software systems program middle finger attribute sentence and close
Insert state acquisition instructions before key code snippet, the delta data for gathering variable to be monitored when software systems are performed.
(3), watch-dog during structure, running
The corresponding LTL formula of software systems are determined according to property specification, and is turned the LTL formula using automaton theory
Finite-state machine is turned to, watch-dog during as operation, specific configuration step is as follows：
(3a), by LTL formulaIt is converted into non-determined B ü chi automatic machines
It is intermediate link with staggeredly B ü chi, LTL formula is detected via correctness first, formed syntax tree, generated and change
The steps such as simple ABA are converted to B ü chi automatic machines (ABA) staggeredlyFlow is as shown in Figure 2；Then
ABA is converted into non-deterministic broad sense B ü chi automatic machine (NGBA) GA=(Q', ∑, δ ', I, Γ)；Finally, by NGBA under
The rule 1 in face changes into non-determined B ü chi automatic machine (NBA) B of equal value with itG=(Q × 0 ..., r }, ∑, δ ', I
×{0},Q×{r})：
Rule 1：δ ' ((q, j))=(α, (q', j')) | (α, q') ∈ δ (q)) and j'=next (j, (q, α, q')), its
Middle next functions are defined as follows：
Through said process, you can NGBA is eventually converted into NBA.
(3b), non-determined B ü chi automatic machines are carried out to sentence the optimization operation such as empty, finiteization, construct finite state automatic
Machine NFA
First, optimize NBA using maximum strongly connected graph, whole strongly connected graphs in automatic machine are found by algorithm, marked
It is designated as " can not monitor ", and the state of all marks " can not monitor " is deleted from state set.Then, carry out sentencing empty optimization
Operation, for each state q in automatic machine, whether the language that judge the automatic machine can receive since q is sky, by time
Automatic machine is gone through, each state is carried out to sentence do-nothing operation, will sentence empty for genuine status indication is " redundancy ", and will be labeled as " redundancy "
State delete, reach optimization automatic machine purpose.Finally, non-determined finite state automata NFA is constructed by NBA,The watch-dog of construction is only received finite word, the checking of stipulations can be carried out according to finite track.
(3c), by non-determined being determined of finite-state machine, the finite automaton of determinization is obtained
Give a non-determined finite automaton NFAConverted it into and it according to following regular 2
Determinization finite automaton DFA of equal valueWherein, rule 2 is：
Q'=2Q
Wherein S ∈ Q
I'=I
It is that can obtain determinization finite automaton by above-mentioned determinization process；
(3d) on the basis of determinization finite automaton, by two automatic machinesWithCartesian product is carried out, the extra output symbol of mark at automatic machine each state,
Can obtain finite-state machine FSM, watch-dog during as operation, it is possible to achieve the perform track of software systems is made to
Qualitative matterWhether the judgement of property specification is run counter to.
(4) probe, is disposed
The key variables and Key Functions of software systems are determined according to property specification, by the key variables and Key Functions
Probe is disposed in position as detection node in the detection node.These probes are used for holding for logging software system
Walking along the street footpath.
(2), the dynamic operation stage
In the dynamic operation stage, i.e., during running software, setting prison when inserting code acquisition software systems are run
The change information of variable is controlled, watch-dog carries out property specification implementation status checking, probe records software system according to the change information
The execution route of system.
Run time verification：The delta data of the monitoring variable of event recognizer collection setting, and monitored when being sent to operation
Device, watch-dog is verified to the delta data for monitoring variable during operation, judges whether software systems implementation status meets property
Stipulations；Wherein：If running monitor judges that software systems implementation status meets property specification, output the result is 0；Such as
Fruit running monitor judges that software systems implementation status does not meet property specification, then it is 1 to export the result；If operation monitoring
Device not can determine that whether software systems implementation status meets property specification, then set the result invalid.
The execution route of probe records software systems, concrete methods of realizing is as follows：In software systems implementation procedure, if
The corresponding key variables of probe or Key Functions are operated, then the probe output result is 1；Performed in software systems
After the completion of, execution route of the vector that N number of probe value is constituted as software systems；N is that the probe of deployment in software systems is total
Number.
In the stage, software systems are run M times, obtain M groups the result and software systems execution route.
(3), fault location row order section
In fault location stage, according to software execution route and watch-dog the result, carry out statistical analysis and realize software
The system failure is positioned, and specific positioning implementation process is as follows：
(a), M ' groups of effective the result is extracted in M group the results, i.e., described M ' groups effective the result is corresponding
Software systems execution route；M ' is the effectively software execution number of times of the result；
B () obtains software fault analysis matrix Q according to M ' groups of effective the result and software systems execution route：
Wherein：eiIt is i-th effective the result, if running monitor judges software systems, implementation status meets property
Stipulations, then ei=0, if running monitor judges that software systems implementation status does not meet property specification, ei=1；Xi=[xi1
xi2 … xij … xiN]TIt is the corresponding software systems execution route of i-th effective the result, if in software implementation procedure
By j-th detection node, then xij=1；I=1,2 ..., M ', j=1,2 ..., N, N be software systems in dispose probe it is total
Number；
C () occurs soft according to software fault analysis matrix Q when in Statistical software system implementation procedure by each detection node
The number of times of part failure, specific formula for calculation is as follows：
Wherein, αjTo there is the number of times of software fault when software systems are by j-th detection node；
D () is to α1、α2、…、αNIt is ranked up by ascending order, chooses the corresponding test point of preceding L value after sequence as software
Trouble point.
The above, only one specific embodiment of the present invention, but protection scope of the present invention is not limited thereto, and appoints
What those familiar with the art the invention discloses technical scope in, the change or replacement that can be readily occurred in, all
Should be included within the scope of the present invention.
The content not being described in detail in description of the invention belongs to the known technology of professional and technical personnel in the field.
Claims (5)
1. Fault Locating Method during a kind of running software, it is characterised in that comprise the following steps：
(1) the software system test requirement definition for, using stipulations definitional language to set is property specification；
(2), the corresponding script file of property specification is compiled and obtains event recognizer, and determine the event recognizer
Inserting position；Then it is by code instrumentation instrument that the event recognizer is corresponding before software systems program is compiled
Code instrumentation in software systems program；
(3) the corresponding LTL formula of software systems, are determined according to property specification, and is turned the LTL formula using automaton theory
Finite-state machine is turned to, watch-dog during as operation；
(4) key variables and Key Functions of software systems, are determined according to property specification, by the key variables and Key Functions
Probe is disposed in position as detection node in the detection node；
(5), when software systems are run：The delta data of the monitoring variable of event recognizer collection setting, and it is sent to operation
When watch-dog；Watch-dog is verified to the delta data for monitoring variable during operation, judges whether software systems implementation status accords with
Close property specification；The execution route of probe records software systems；
(6), repeat step (5), software systems are run M times, obtain M groups the result and software systems execution route；
(7), according to M groups the result and software systems execution route, the number of times broken down in each detection node, choosing are counted
Take trouble point of several positions of number of stoppages highest as software systems.
2. Fault Locating Method during a kind of running software according to claim 1, it is characterised in that：In step (1), adopt
The software system test demand of setting, certainty are described with atomic event definitional language PDEL and compound event definitional language MEDL
Matter stipulations.
3. Fault Locating Method during a kind of running software according to claim 1, it is characterised in that：In step (5), fortune
Watch-dog is verified to the delta data for monitoring variable during row, judges whether software systems implementation status meets property specification,
Wherein：If running monitor judges that software systems implementation status meets property specification, output the result is 0；If fortune
Row watch-dog judges that software systems implementation status does not meet property specification, then it is 1 to export the result；If running monitor is not
Can determine that whether software systems implementation status meets property specification, then set the result invalid.
4. Fault Locating Method during a kind of running software according to claim 1, it is characterised in that：In step (5), visit
The execution route of pin logging software system, concrete methods of realizing is as follows：In software systems implementation procedure, if to probe correspondence
Key variables or Key Functions operated, then the probe output result be 1；After the completion of software systems execution, by N
The vector that individual probe value is constituted as software systems execution route；N is the probe sum of deployment in software systems.
5. Fault Locating Method during a kind of running software according to claim 1, it is characterised in that：It is soft in step (7)
It is as follows that the trouble point of part system specifically positions implementation process：
(7a), M ' groups of effective the result, i.e., described M ' groups corresponding software of effective the result are extracted in M group the results
System execution route；M ' is the effectively software execution number of times of the result；
(7b) obtains software fault analysis matrix Q according to M ' groups of effective the result and software systems execution route：
Wherein：eiIt is i-th effective the result, if running monitor judges software systems, implementation status meets property specification,
Then ei=0, if running monitor judges that software systems implementation status does not meet property specification, ei=1；Xi=[xi1 xi2
… xij … xiN]TIt is the corresponding software systems execution route of i-th effective the result, if passed through in software implementation procedure
J-th detection node, then xij=1；I=1,2 ..., M ', j=1,2 ..., N, N be software systems in dispose probe sum；
There is software according to software fault analysis matrix Q when in Statistical software system implementation procedure by each detection node in (7c)
The number of times of failure, specific formula for calculation is as follows：
Wherein, αjTo there is the number of times of software fault when software systems are by j-th detection node；
(7d) is to α1、α2、…、αNIt is ranked up by ascending order, chooses the corresponding test point of preceding L value after sequence as software event
Barrier point.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611102015.4A CN106776208B (en) | 2016-12-02 | 2016-12-02 | Fault Locating Method when a kind of running software |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611102015.4A CN106776208B (en) | 2016-12-02 | 2016-12-02 | Fault Locating Method when a kind of running software |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106776208A true CN106776208A (en) | 2017-05-31 |
| CN106776208B CN106776208B (en) | 2018-08-31 |
Family
ID=58883269
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611102015.4A Active CN106776208B (en) | 2016-12-02 | 2016-12-02 | Fault Locating Method when a kind of running software |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106776208B (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108632086A (en) * | 2018-04-19 | 2018-10-09 | 山东省计算中心（国家超级计算济南中心） | A kind of concurrent job operation troubles localization method |
| CN109189671A (en) * | 2018-08-10 | 2019-01-11 | 百富计算机技术（深圳）有限公司 | Successively folder forces formula variable localization method, system and terminal device |
| CN110245085A (en) * | 2019-04-08 | 2019-09-17 | 华东师范大学 | Embedded real-time operating system verification method and system using online model verification |
| CN110362445A (en) * | 2019-05-28 | 2019-10-22 | 平安普惠企业管理有限公司 | A kind of monitoring information feedback method and information feedback system based on user behavior |
| CN110532036A (en) * | 2019-07-26 | 2019-12-03 | 云湾科技(嘉兴)有限公司 | Program verification method, calculates equipment and computer storage medium at device |
| CN110727577A (en) * | 2019-08-29 | 2020-01-24 | 华东计算技术研究所（中国电子科技集团公司第三十二研究所） | Debugging method, system and medium for probability recurrence problem in embedded system software |
| CN111651853A (en) * | 2020-04-14 | 2020-09-11 | 中国电子产品可靠性与环境试验研究所（（工业和信息化部电子第五研究所）（中国赛宝实验室）） | Evaluation Method of Product Fault Comprehensive Diagnosis Capability |
| CN114328163A (en) * | 2020-09-29 | 2022-04-12 | 厦门邑通软件科技有限公司 | A method, system and device for intelligent diagnosis of software system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070240113A1 (en) * | 2006-01-30 | 2007-10-11 | Microsoft Corporation | Model independent input reduction |
| CN101814055A (en) * | 2010-04-06 | 2010-08-25 | 南京大学 | Sampling method for test cases in clusters |
| CN103186451A (en) * | 2013-03-21 | 2013-07-03 | 中国人民解放军国防科学技术大学 | Time sequence attribute monitoring method with failure prediction capability |
-
2016
- 2016-12-02 CN CN201611102015.4A patent/CN106776208B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070240113A1 (en) * | 2006-01-30 | 2007-10-11 | Microsoft Corporation | Model independent input reduction |
| CN101814055A (en) * | 2010-04-06 | 2010-08-25 | 南京大学 | Sampling method for test cases in clusters |
| CN103186451A (en) * | 2013-03-21 | 2013-07-03 | 中国人民解放军国防科学技术大学 | Time sequence attribute monitoring method with failure prediction capability |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108632086A (en) * | 2018-04-19 | 2018-10-09 | 山东省计算中心（国家超级计算济南中心） | A kind of concurrent job operation troubles localization method |
| CN108632086B (en) * | 2018-04-19 | 2020-12-11 | 山东省计算中心（国家超级计算济南中心） | A method for locating faults in parallel job operation |
| CN109189671A (en) * | 2018-08-10 | 2019-01-11 | 百富计算机技术（深圳）有限公司 | Successively folder forces formula variable localization method, system and terminal device |
| CN109189671B (en) * | 2018-08-10 | 2022-02-11 | 百富计算机技术（深圳）有限公司 | Layer-by-layer approximation type variable positioning method and system and terminal equipment |
| CN110245085B (en) * | 2019-04-08 | 2023-03-31 | 华东师范大学 | Embedded real-time operating system verification method and system by using online model inspection |
| CN110245085A (en) * | 2019-04-08 | 2019-09-17 | 华东师范大学 | Embedded real-time operating system verification method and system using online model verification |
| CN110362445A (en) * | 2019-05-28 | 2019-10-22 | 平安普惠企业管理有限公司 | A kind of monitoring information feedback method and information feedback system based on user behavior |
| CN110532036A (en) * | 2019-07-26 | 2019-12-03 | 云湾科技(嘉兴)有限公司 | Program verification method, calculates equipment and computer storage medium at device |
| CN110727577A (en) * | 2019-08-29 | 2020-01-24 | 华东计算技术研究所（中国电子科技集团公司第三十二研究所） | Debugging method, system and medium for probability recurrence problem in embedded system software |
| CN110727577B (en) * | 2019-08-29 | 2023-06-09 | 华东计算技术研究所（中国电子科技集团公司第三十二研究所） | Debugging method, system and medium for probability reproduction problem in embedded system software |
| CN111651853A (en) * | 2020-04-14 | 2020-09-11 | 中国电子产品可靠性与环境试验研究所（（工业和信息化部电子第五研究所）（中国赛宝实验室）） | Evaluation Method of Product Fault Comprehensive Diagnosis Capability |
| CN111651853B (en) * | 2020-04-14 | 2023-12-12 | 中国电子产品可靠性与环境试验研究所（（工业和信息化部电子第五研究所）（中国赛宝实验室）） | Evaluation method for comprehensive diagnosis capability of product faults |
| CN114328163A (en) * | 2020-09-29 | 2022-04-12 | 厦门邑通软件科技有限公司 | A method, system and device for intelligent diagnosis of software system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106776208B (en) | 2018-08-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106776208B (en) | Fault Locating Method when a kind of running software | |
| CN111209131B (en) | Method and system for determining faults of heterogeneous system based on machine learning | |
| CN106844194B (en) | A kind of construction method of multi-level software fault diagnosis expert system | |
| US7100084B2 (en) | Method and apparatus for diagnosing difficult to diagnose faults in a complex system | |
| Jiang et al. | Failure diagnosis of discrete-event systems with linear-time temporal logic specifications | |
| CN113377567B (en) | Distributed system fault root cause tracing method based on knowledge graph technology | |
| CN109800127A (en) | A kind of system fault diagnosis intelligence O&M method and system based on machine learning | |
| CN109308411B (en) | Method and system for hierarchically detecting software behavior defects based on artificial intelligence decision tree | |
| CN112906764B (en) | Intelligent diagnosis method and system for communication security equipment based on improved BP neural network | |
| CN104216825A (en) | Problem locating method and system | |
| CN107967398A (en) | A kind of product reliability analysis method and device | |
| Lazarova-Molnar et al. | Automating reliability analysis: Data-driven learning and analysis of multi-state fault trees | |
| CN107966648B (en) | A kind of embedded failure diagnosis method based on correlation matrix | |
| CN107102909A (en) | A kind of Fault Classification towards complex software intensive equipment system | |
| CN116541728A (en) | Fault diagnosis method and device based on density clustering | |
| CN112285484B (en) | Power system fault diagnosis information fusion method and device based on deep neural network | |
| CN118133962A (en) | Correlation analysis method, device and system of fault event and storage medium | |
| Wu et al. | Traffic sensor health monitoring using spatiotemporal graphical modeling | |
| Valueian et al. | Constructing automated test oracle for low observable software | |
| CN110188040A (en) | A kind of software platform for software systems fault detection and health state evaluation | |
| CN115798760A (en) | Accident online diagnosis tracking and rapid prediction system and method suitable for nuclear power plant | |
| Restat et al. | Towards a Holistic Data Preparation Tool. | |
| CN106487592A (en) | A kind of Faults in Distributed Systems diagnostic method based on data cube | |
| Jin et al. | Anomaly detection and health-status analysis in a core router system | |
| Saravanan et al. | IoT based advanced prediction methodology for fault localization in machine monitoring |
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 | ||
| CB03 | Change of inventor or designer information |
Inventor after: Xue Huifeng Inventor after: Yan Chenjing Inventor after: Zhang Wei Inventor after: Ge Hui Inventor after: Jing Xiaochuan Inventor after: Gao Jinliang Inventor after: Fu Yan Inventor after: Zhang Bo Inventor after: Lv Hongyu Inventor before: Yan Chenjing Inventor before: Zhang Wei Inventor before: Ge Hui Inventor before: Jing Xiaochuan Inventor before: Gao Jinliang Inventor before: Fu Yan Inventor before: Zhang Bo Inventor before: Lv Hongyu |
|
| CB03 | Change of inventor or designer information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |