CN102819489A - Software reliability designing method driven by defects - Google Patents
Software reliability designing method driven by defects Download PDFInfo
- Publication number
- CN102819489A CN102819489A CN2012102325988A CN201210232598A CN102819489A CN 102819489 A CN102819489 A CN 102819489A CN 2012102325988 A CN2012102325988 A CN 2012102325988A CN 201210232598 A CN201210232598 A CN 201210232598A CN 102819489 A CN102819489 A CN 102819489A
- Authority
- CN
- China
- Prior art keywords
- software
- defective
- defect
- design
- data
- 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.)
- Pending
Links
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The invention discloses a software reliability designing method driven by defects. According to the method, defect data of similar software are collected for recognizing potential defects in the software, make defect classification standards and establish a software detect model bank. On the basis of the detect model bank, causes of defects are perfected through software fault tree analysis (SFTA), and improvement measures are made according to the causes of defects, so that the implementation of a software reliability design technology is guided. According to the method disclosed by the invention, the implementation blindness of the software reliability design technology is overcome, the pertinence of a software reliability design is improved, the software reliability design can be carried out more effectively, defects can be prevented to the greatest extent and avoided as early as possible, the follow-up test and repair cost is greatly reduced, and the reliability of the software is improved more effectively.
Description
Technical field
The invention belongs to the software reliability engineering field, relate to software reliability method for designing wherein, be specifically related to a kind of software reliability method for designing of defect driven.
Background technology
Software reliability is one of important attribute of software quality, and software reliability is to propose at the mid-1970s, and is developed to the mid-80, greatly about 1988, begins to encourage the technician to use the software reliability method.The software reliability design is the key that guarantees software quality, improves software reliability, and the research of software reliability method for designing is an extremely important aspect in software reliability engineering field.
Books that the software reliability method for designing is different and document have different contents; Generally comprise and implement soft projectization, simplified design, robustness design, fault-tolerant design, software reliability design criteria etc.; But it is, particularly indeterminate, comparatively ambiguous for using which kind of concrete method for designing when to all not enough system, clear of the introduction of software reliability method for designing; The practical applications that is unfavorable for the software reliability method for designing, thus also be unfavorable for improving the reliability of software.
Software defect is the basic factor that hinders that software reliability improves, and in the software reliability design, occupies important status, exists certain related with the software reliability method for designing.Software defect is the root that causes software failure, and software failure just means that software is unreliable.Present increasing software organization payes attention to collection and the management to the software defect data, has accumulated certain defective data at present, but to the utilization of software defect data not enough.And software defect and reliability exist certain related, if but for utilizing the software defect data to lack corresponding method for the software reliability design services.
Summary of the invention
The present invention improves the specific aim of software reliability design in order to overcome the blindness that the software reliability designing technique is implemented, and prevents as soon as possible and avoids defective, writes out highly reliable software, proposes a kind of software reliability method for designing of defect driven.This method is set up the software defect mode storehouse through identifying defective potential in the software, analyzes (SFTA) through the software fault tree and improves defect cause, formulates innovative approach, thus the enforcement of Bootstrap Software reliability design technology.
The invention provides a kind of software reliability method for designing based on defect driven, this method may further comprise the steps:
Step 1: clear and definite software reliability design object particularly needs clearly to carry out reliability design to the software with what characteristic.
Step 2: collect the current relevant defective data that develops software, according to software development phase and each stage action and task software defect is classified, and further obtain the current possible defect mode that develops software.
Step 3: set up the software defect mode storehouse,, refine the software defect innovative approach and form the software reliability designing technique through SFTA analyzing defect reason.
Step 4: which under clear and definite current the developing software, find out possible defect mode of this stage development phase.
Step 5: corresponding function code is write in the software defect innovative approach according to step 3 is refined.
Step 6: function code is carried out reconstruct, and further analysis guarantees that all possible defect mode can not take place.If also possibly take place, return step 3 and refine the software defect innovative approach once more, function code is made amendment or design again, can not take place up to possible defect mode.
Step 7: the function of all current software development phases is accomplished in circulation, finishes up to software development.
Affiliated step 2 is basis of the present invention and foundation, is the Data Source of implementing the software reliability design of defect driven.At first from the similar software of our unit, collect and the current relevant defective data of software that will carry out reliability design other similar software or domain expert's lesson and the experience both at home and abroad; Secondly, the software defect data of collecting are put in order, replenish defect information, reject defective data useless or that obviously repeat; Afterwards, formulate the classification of defects standard, the software defect data of collecting are classified according to the Software Defects Classification of formulating; At last, the software defect data abstraction with classified is a software defect mode.Software defect mode, promptly take place one type specific, that repeat or the similar abstractdesription of software defect.Analysis is summarized with abstract to the rule of each type software defect form of expression, summarizes the corresponding defects pattern.
Software defect is divided into three major types according to the software defect stage of introducing: software requirement defective, design defect in software, software coding defective, consider that simultaneously embedded software uses the C Programming with Pascal Language always, provided the C language defect.Consider each stage action and task simultaneously, these three types of defectives further are divided into some subclasses.The software requirement defective is divided into again: functional requirement defective, performance requirement defective, interface requirements defective, demand data defective, safety and privacy requirements defective, abnormality processing defective, other demand defective.Design defect in software is divided into again: architecture defective, modular design defective, Interface design defective, shared resource defective, interruption design defect, user interface defective, other design defect.The software coding defective is divided into again: data declaration defective, statement structure defective, statement efficient defective, code annotation defective, certain concrete syntax defective, other defective of encoding.The C language defect is divided into again: header file fault of construction, sequential organization defective, internal memory defective, IF statement defective, SWITCH statement defective, loop statement defective, function statement defective and other defective.
Affiliated step 3 is cores of the present invention, is the direct guidance of implementing the software reliability design of defect driven.At first set up the software defect mode storehouse, become on the defect mode basis, introduce defect cause, defective consequence, defect rank and preventive measure, set up the software defect mode storehouse in the software defect data abstraction; Secondly, need carry out selective analysis, the present invention proposes and on basis, software defect mode storehouse, use software fault tree analysis (SFTA) to obtain defect cause the defect cause in the defect mode storehouse.Through setting up the SFTA of software defect, obtain minimal cut set, just can obtain causing the reason of defective.This method can not only more correctly be obtained defect cause, and can also grasp the logical relation of defect cause through SFTA, for formulating innovative approach better foundation is provided.At last, according to the innovative approach that defect cause formulation needs are taked, promptly adopt which software reliability technology: fault avoidance technology, debugging are technological, the technology of correcting mistakes and fault-tolerant technique.General defective just can make the software of exploitation error-free through the fault avoidance technology; But some defective is for example because the defective that disturbing factor causes; Perhaps the very serious defective of defective consequence except using the fault avoidance design, also need be considered debugging technology, the technology of correcting mistakes and fault-tolerant technique.
Adopt defect driven to carry out the advantage of software reliability design:
(1) can more effectively carry out software reliability.Consider the Software Defects Classification that each stage action and task are carried out simultaneously by software development phase, stronger as far as the design specific aim.Through SFTA analyzing defect reason, not only can find out the reason that causes defective, and can also obtain each reason between logical relation, can formulate innovative approach better, thereby can carry out software reliability effectively.
(2) prevent reliability design, improved the specific aim of software reliability design for reliability design.Through identifying defective potential in the software,, formulate innovative approach, thereby the enforcement of Bootstrap Software reliability design technology has more specific aim to the defect analysis reason.
(3) can prevent as best one can and avoid defective as soon as possible, greatly reduce the cost of follow-up test and reparation, more effectively improve software reliability.The software reliability designing technique derives from the innovative approach of formulating according to defect cause, can earlier prevent defective, writes out highly reliable software.The innovative approach defect driven method of defective has embodied the intrinsic propesties that software reliability and defective are struggled, and has brought into play the effect of defective in the software reliability design.
Description of drawings
Fig. 1 is that software defect mode obtains process flow diagram;
Fig. 2 is the Software Defects Classification standard;
Fig. 3 is that process flow diagram is set up in the software defect mode storehouse;
Fig. 4 is a software defect analysis of causes method;
Fig. 5 is a software defect innovative approach formulating method.
Embodiment
Below in conjunction with accompanying drawing and embodiment the present invention is further specified.
Understand and embodiment of the present invention for the ease of those of ordinary skills, the present invention is done further in detail, in depth describes, should be appreciated that embodiment described herein only is used for explanation and explains the present invention, and be not used in qualification the present invention below in conjunction with accompanying drawing.
Fig. 1 has described the detailed process that the software defect mode based on defective data obtains, and concrete steps are:
Step 1: collect relevant software defect data.
The software defect data are bases of the present invention, and following three aspects generally can be considered in the source of defective data:
(1) the software defect data that have been found that in the similar software development of our unit, test and the operational process
Software development generally all has certain inheritance, before the new software of exploitation, and can be through the defective data of similar software generation before collecting.Can collect the defective that possibly exist through various software documents and record, like review record, quality guarantee record, test record, test report etc.; Also can be through adopting the form of survey, informal discussion face to face or brainstorming; Through speaking face to face with the software design and development personnel; Collect the lesson and the successful experience of their experience in the project practice, be included in the thorny problem that runs in the software project implementation process, the problem that is prone to ignore, be prone to defective of introducing and the preventive measure of taking etc.
(2) defective data that has been found that of other similar software both at home and abroad
Except collecting our unit's related defects data; Also can be through collecting the defective data mentioned in domestic and international pertinent literature and the standard criterion and the experience and lessons of domestic-developed unit, like security guide, GJB102, space flight fault revelation, XX software typical case analysis and the design reference of NASA.
(3) domain expert's lesson and experience
Adopt the form assembling sphere expert's of survey and informal discussion experience, to replenish defect mode.The domain expert comprises software design personnel, software developer, software reliability research personnel etc.; Through speaking face to face with them; Collect the experience of their accumulation in the project practice, be included in the thorny problem that runs in the software project implementation process, the problem that is prone to ignore, be prone to defective of introducing and the preventive measure of taking etc.On the other hand, also can distinguish its correctness through the defect mode of having collected with expert discussion.
Step 2: the software defect data to collecting are put in order
Because possibly there is following problem in the various defective data that causes collecting in defective data source:
(1). the defective data of software development and test event accumulation is natural language representes that same defect maybe be owing to the difference of personnel's understanding, and description is not quite similar;
(2). when collecting defective data, part Symptom information is collected or is leaked by mistake and collects, and has influence on defective data Reliability of Information and integrity degree;
(3). aspects such as its classification of defects method of different exploitations and test event, defect rank division exist inconsistent.
To the problems referred to above, need to adopt following several method that defective data is further put in order:
(1). according to the software of different development& testing projects and development& testing personnel's characteristics, understand the information that defective data is described, obtain the defective data of no repetition;
(2). from defective data, incomplete Symptom or wrong Symptom are repaired as far as possible, can't repair-deficiency from data, reject;
(3). according to classification of defects the defective data of collecting is put in order, failed to be included into the defective data of any classification, be classified as other classification.
Step 3: the software defect data to collecting are classified
The classification of software defect is the basis of research software defect.The sorting technique of software defect has a lot, and the purpose of various sorting techniques is different, and viewing angle and complexity are also different.Existing representative Software Defects Classification: based on the Software Defects Classification in software error source, based on the Software Defects Classification of wrong properties, based on the Software Defects Classification of quadrature classification, based on software life-cycle activity Software Defects Classification, based on the Software Defects Classification (Phase-DC) of development phase, based on certain type of specific software research Software Defects Classification.These sorting techniques respectively have its purposes and relative merits owing to classification purpose, classification foundation are different with the defective data source.Take all factors into consideration above various sorting technique, generally should satisfy following requirement Software Defects Classification:
Step 4: with the software defect data abstraction of classified is software defect mode.
The software defect data are many, unavoidably have repetition, and needing further abstract is software defect mode.Software defect mode, promptly take place one type specific, that repeat or the similar abstractdesription of software defect.This definition is applicable to the software defect that any stage introduces in the soft project.Research to software defect mode is based upon on the basis of Software Defects Classification, analyzes the rule to each type software defect form of expression, summarizes with abstract, summarizes the corresponding defects pattern.
Fig. 2 has described the Software Defects Classification standard that the present invention formulates.This classification of defects can cover the software development overall process, combines closely with software life-cycle, takes into full account software defect and introduces the stage.Based on above requirement, software defect is divided into three major types according to the software defect stage of introducing: software requirement defective, design defect in software, software coding defective, consider that simultaneously embedded software uses the C Programming with Pascal Language always, provided the C language defect.Consider each stage action and task simultaneously, these three types of defectives further are divided into some subclasses, be constructed as follows the classification of defects hierarchical chart.
Utilize above-mentioned classification, the defective data of collecting is classified is divided into two stages:
(1) preliminary classification.According to software development phase, the software defect data are carried out preliminary classification, as it being divided into demand defective, design defect, code defective etc.,, next step confirms the corresponding concrete thinner classification of defects of every kind of defective so that developing according to defective.
(2) exhaustive division.Further extract each concrete characteristic of defective of big type, it is carried out exhaustive division according to existing Software Defects Classification method.For example the code defective can be divided into header file structure, sequential organization, internal memory, IF statement, SWITCH statement, loop statement etc.
Fig. 3 has described the flow process of setting up in software defect mode storehouse.In order to set up the relation of software defect mode and Defect prevention measure, the present invention has defined the defect mode storehouse.Become on the defect mode basis in the software defect data abstraction; Introduce defect cause, defective consequence, defect rank and preventive measure; Formed a five-tuple; Set by the software defect mode attribute constitutes, and attribute comprises the title of software defect mode, reason, consequence and grade, the software defect preventive measure that software defect is introduced.
Definition: five-tuple ψ=(N, I, O, L, P), wherein
< 1>N is the title of software defect mode, this software defect mode of ability unique identification, and it can not be null value;
< 2>I is the set that this defect mode is introduced reason;
< 3>O is the set that this defect mode causes consequence;
< 4>L is the set of this defect mode grade;
< 5>P is such software defect preventive measure set.
Setting up the defect mode storehouse is a long-term process; Need constantly to collect the practical experience and the achievement in research of software project; To replenish the information in defect mode storehouse, there are following two kinds of approach in foundation and additional software defect mode storehouse: a kind of is directly to collect defect information, and another kind is to utilize the failure mode storehouse; Through setting up the relation in failure mode storehouse and defect mode storehouse, the defect mode storehouse is replenished.
Fig. 4 has described software defect analysis of causes method.One of most important task of the present invention is the defect cause analysis, just finds the general character reason and the fundamental cause that cause software defect to produce, and the technical information of at present domestic relevant this respect lacks.When analyzing basic reason, can adopt methods such as causality analysis, failure model and impact analysis, incident and attribution cause analysis, personnel ability's analysis.Fig. 4 has provided on basis, software defect mode storehouse, replenishes and uses the software fault tree to analyze (SFTA) defect cause, and its detailed step is following:
Step 1: certain defective is as top event in the selection defect mode storehouse.
Step 2: analyze reason that top event takes place and with logical AND gate/or link to each other, as the joint of fault tree with top event.
Step 3: whether traced back to the whole reasons that cause top event to take place? As do not have, change step 2 over to and continue to analyze.
Step 4:, accomplish the foundation of number of faults with the leaf of bottom event as fault tree.
Step 5: on the basis of fault tree, the identification minimal cut set.
Step 6: organize the logical relation between the minimal cut set, with defect cause in its additional defect mode storehouse.
Fig. 5 has described software defect innovative approach formulating method.The purpose of defect cause analysis is in order to propose the software defect innovative approach, to implement the software reliability design according to the defective innovative approach, is that core of the present invention is formed.
Defective and reliability are software product two attributes of contradiction each other.Defective can cause software failure under environmental activity, and software failure can influence reliability.Therefore to improve software reliability, most critical be the defective of making every effort to reduce in the software, mistake was strangled before Software Delivery uses as far as possible, guarantee that software can not make mistakes or make mistakes less after being delivered for use, Here it is proposes foundation of the present invention.
After the grade of reason that defective that above-mentioned analysis obtains produces and influence, just can determine the innovative approach that to take, and in software design, improve, thereby more effectively more directly improve reliability.
The software reliability technology mainly can be divided into four types at present:
(1) fault avoidance technology, this mainly is to adopt design methodology to make software error-free as much as possible.
(2) debugging technology is in operation program and searches automatically and has wrong a kind of designing technique.
(3) technology of correcting mistakes is meant in design, gives a kind of designing technique of the ability of program self correction mistake, the wrong extent of injury of minimizing.
(4) fault-tolerant technique, some defectives of software systems are inevitably, also can not be detected.Fault-tolerant technique is exactly to make the operation that software can be correct under the situation that software defect exists.
General defective just can make the software of exploitation error-free through the fault avoidance technology; But some defective is for example because the defective that disturbing factor causes; The perhaps very serious defective of defective consequence; Except using the fault avoidance design, also need consider debugging technology, the technology of correcting mistakes and fault-tolerant technique, thereby finally reach the software reliability requirement.
Claims (5)
1. the software reliability method for designing of a defect driven is characterized in that comprising following steps:
(1) clear and definite software reliability design object particularly needs clearly to carry out reliability design to the software with what characteristic.
(2) collect the current relevant defective data that develops software, according to software development phase and each stage action and task software defect is classified, and further obtain the current possible defect mode that develops software.
(3) set up the software defect mode storehouse,, refine the software defect innovative approach and form the software reliability designing technique through SFTA analyzing defect reason.
(4) which under clear and definite current the developing software, find out possible defect mode of this stage development phase.
Corresponding function code is write in the software defect innovative approach of (5) refining according to step (3).
(6) reconstruct is carried out to function code in (6), and further analysis guarantees that all possible defect mode can not take place.If also possibly take place, return step (3) and refine the software defect innovative approach once more, function code is made amendment or design again, can not take place up to possible defect mode.
(7) function of all current software development phases is accomplished in circulation, finishes up to software development.
2. the software reliability method for designing of defect driven according to claim 1 is characterized in that: describedly obtain the current possible defect mode that develops software, may further comprise the steps:
(1) collects relevant software defect data.The source is divided into three aspects: the software defect data that have been found that in a) the similar software development of our unit, test and the operational process.Can collect the defective that possibly exist through various software documents and record, like review record, quality guarantee record, test record, test report etc.; Also can through speaking face to face, collect the lesson and the successful experience of their experience in the project practice through adopting the form of survey, informal discussion face to face or brainstorming with the software design and development personnel; B) defective data that has been found that of other similar software both at home and abroad.Except collecting our unit's related defects data; Also can be through collecting the defective data mentioned in domestic and international pertinent literature and the standard criterion and the experience and lessons of domestic-developed unit, like security guide, GJB102, space flight fault revelation, XX software typical case analysis and the design reference of NASA; C) domain expert's lesson and experience.Adopt the form assembling sphere expert's of survey and informal discussion experience, to replenish defect mode.The domain expert comprises software design personnel, software developer, software reliability research personnel etc.Also can distinguish its correctness through the defect mode of having collected with expert discussion.
(2) the software defect data of collecting are put in order, replenish defect information, reject defective data useless or that obviously repeat.
(3) formulate the classification of defects standard, the software defect data of collecting are classified according to the Software Defects Classification of formulating.
(4) the software defect data abstraction with classified is a software defect mode.Software defect mode, promptly take place one type specific, that repeat or the similar abstractdesription of software defect.Analysis is summarized with abstract to the rule of each type software defect form of expression, summarizes the corresponding defects pattern.
3. formulation Software Defects Classification standard according to claim 2; It is characterized in that: software defect is divided into three major types according to the software defect stage of introducing: software requirement defective, design defect in software, software coding defective; Consider that simultaneously embedded software uses the C Programming with Pascal Language always, provided the C language defect.Consider each stage action and task simultaneously, these three types of defectives further are divided into some subclasses.The software requirement defective is divided into again: functional requirement defective, performance requirement defective, interface requirements defective, demand data defective, safety and privacy requirements defective, abnormality processing defective, other demand defective.Design defect in software is divided into again: architecture defective, modular design defective, Interface design defective, shared resource defective, interruption design defect, user interface defective, other design defect.The software coding defective is divided into again: data declaration defective, statement structure defective, statement efficient defective, code annotation defective, certain concrete syntax defective, other defective of encoding.The C language defect is divided into again: header file fault of construction, sequential organization defective, internal memory defective, IF statement defective, SWITCH statement defective, loop statement defective, function statement defective and other defective.
4. the Software Defects Classification according to formulation according to claim 2 is classified to the software defect data of collecting, and its characteristic is divided into two stages:
(1) preliminary classification.According to software development phase, the software defect data are carried out preliminary classification, as it being divided into demand defective, design defect, code defective etc.,, next step confirms the corresponding concrete thinner classification of defects of every kind of defective so that developing according to defective.
(2) exhaustive division.Further extract each concrete characteristic of defective of big type, it is carried out exhaustive division according to the Software Defects Classification method of formulating.For example the code defective can be divided into header file structure, sequential organization, internal memory, IF statement, SWITCH statement, loop statement etc.
5. the software reliability method for designing of defect driven according to claim 1 is characterized in that: set up the software defect mode storehouse, through SFTA analyzing defect reason, refine the software defect innovative approach and form the software reliability designing technique, may further comprise the steps:
(1) sets up the software defect mode storehouse, become on the defect mode basis, introduce defect cause, defective consequence, defect rank and preventive measure, set up the software defect mode storehouse in the software defect data abstraction.
(2) defect cause in the defect mode storehouse is carried out selective analysis, on basis, software defect mode storehouse, use the software fault tree to analyze (SFTA) and obtain defect cause.Through setting up the SFTA of software defect, obtain minimal cut set, obtain causing the reason of defective.
(3) innovative approach of taking according to defect cause formulation needs, promptly adopt which software reliability technology: fault avoidance technology, debugging are technological, the technology of correcting mistakes and fault-tolerant technique.General defective just can make the software of exploitation error-free through the fault avoidance technology; But some defective is for example because the defective that disturbing factor causes; Perhaps the very serious defective of defective consequence except using the fault avoidance design, also need be considered debugging technology, the technology of correcting mistakes and fault-tolerant technique.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012102325988A CN102819489A (en) | 2012-07-05 | 2012-07-05 | Software reliability designing method driven by defects |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012102325988A CN102819489A (en) | 2012-07-05 | 2012-07-05 | Software reliability designing method driven by defects |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102819489A true CN102819489A (en) | 2012-12-12 |
Family
ID=47303611
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2012102325988A Pending CN102819489A (en) | 2012-07-05 | 2012-07-05 | Software reliability designing method driven by defects |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102819489A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103970656A (en) * | 2014-05-08 | 2014-08-06 | 北京航空航天大学 | SFMEA and SFTA reverse comprehensive analysis assisting method |
| CN104699611A (en) * | 2015-03-18 | 2015-06-10 | 北京航空航天大学 | Defect information extraction method based on open-source software defect code modification mode |
| CN106776316A (en) * | 2016-12-15 | 2017-05-31 | 中国电力科学研究院 | A kind of power information software defect prevention method |
| CN107193677A (en) * | 2017-04-18 | 2017-09-22 | 广州视源电子科技股份有限公司 | Method and system for notifying code defects |
| CN107908550A (en) * | 2017-10-27 | 2018-04-13 | 链家网（北京）科技有限公司 | A kind of software defect statistical processing methods and device |
| CN108154287A (en) * | 2017-12-06 | 2018-06-12 | 千寻位置网络有限公司 | The analyzing evaluation method of software system development quality |
| CN109753426A (en) * | 2017-11-08 | 2019-05-14 | 北京奇虎科技有限公司 | A kind of method of quality control and device of application program |
| CN114548744A (en) * | 2017-12-22 | 2022-05-27 | 蚂蚁胜信(上海)信息技术有限公司 | Business risk management method, device and equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101436128A (en) * | 2007-11-16 | 2009-05-20 | 北京邮电大学 | Software test case automatic generating method and system |
| CN101571828A (en) * | 2009-06-11 | 2009-11-04 | 北京航空航天大学 | Method for detecting code security hole based on constraint analysis and model checking |
| JP2012048660A (en) * | 2010-08-30 | 2012-03-08 | Nec Corp | Static analysis processing system, method, and program |
-
2012
- 2012-07-05 CN CN2012102325988A patent/CN102819489A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101436128A (en) * | 2007-11-16 | 2009-05-20 | 北京邮电大学 | Software test case automatic generating method and system |
| CN101571828A (en) * | 2009-06-11 | 2009-11-04 | 北京航空航天大学 | Method for detecting code security hole based on constraint analysis and model checking |
| JP2012048660A (en) * | 2010-08-30 | 2012-03-08 | Nec Corp | Static analysis processing system, method, and program |
Non-Patent Citations (2)
| Title |
|---|
| 张虹等: "软件可靠性分析方法研究与应用", 《测控技术》 * |
| 曾福萍等: "软件缺陷模式的研究", 《计算机科学》 * |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103970656A (en) * | 2014-05-08 | 2014-08-06 | 北京航空航天大学 | SFMEA and SFTA reverse comprehensive analysis assisting method |
| CN103970656B (en) * | 2014-05-08 | 2016-12-07 | 北京航空航天大学 | SFMEA Yu SFTA the most comprehensively analyzes householder method |
| CN104699611A (en) * | 2015-03-18 | 2015-06-10 | 北京航空航天大学 | Defect information extraction method based on open-source software defect code modification mode |
| CN104699611B (en) * | 2015-03-18 | 2017-07-28 | 北京航空航天大学 | A kind of defect information extracting method that pattern is changed based on open source software defect code |
| CN106776316A (en) * | 2016-12-15 | 2017-05-31 | 中国电力科学研究院 | A kind of power information software defect prevention method |
| CN107193677A (en) * | 2017-04-18 | 2017-09-22 | 广州视源电子科技股份有限公司 | Method and system for notifying code defects |
| CN107908550A (en) * | 2017-10-27 | 2018-04-13 | 链家网（北京）科技有限公司 | A kind of software defect statistical processing methods and device |
| CN107908550B (en) * | 2017-10-27 | 2020-11-13 | 贝壳找房(北京)科技有限公司 | Software defect statistical processing method and device |
| CN109753426A (en) * | 2017-11-08 | 2019-05-14 | 北京奇虎科技有限公司 | A kind of method of quality control and device of application program |
| CN108154287A (en) * | 2017-12-06 | 2018-06-12 | 千寻位置网络有限公司 | The analyzing evaluation method of software system development quality |
| CN114548744A (en) * | 2017-12-22 | 2022-05-27 | 蚂蚁胜信(上海)信息技术有限公司 | Business risk management method, device and equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102819489A (en) | Software reliability designing method driven by defects | |
| Apel et al. | Strategies for product-line verification: case studies and experiments | |
| Heckman et al. | A systematic literature review of actionable alert identification techniques for automated static code analysis | |
| US9092561B2 (en) | Model checking for distributed application validation | |
| CN109144882B (en) | Software fault positioning method and device based on program invariants | |
| CN101710378B (en) | Software security flaw detection method based on sequential pattern mining | |
| CN107301115A (en) | Application exception is monitored and restoration methods and equipment | |
| Binkley et al. | Locating dependence clusters and dependence pollution | |
| US9588871B1 (en) | Method and system for dynamic business rule extraction | |
| Hemmati et al. | Prioritizing manual test cases in rapid release environments | |
| US20100299654A1 (en) | Approach for root causing regression bugs | |
| EP2671157A1 (en) | Arrangement and method for model-based testing | |
| CN105893166A (en) | Method and device for processing memory errors | |
| Balliu et al. | Challenges of producing software bill of materials for java | |
| CN102567201A (en) | Method for automatically recovering cross-model GUI (graphic user interface) test scripts | |
| Dehlinger et al. | Plfaultcat: A product-line software fault tree analysis tool | |
| Walkinshaw et al. | Are 20% of files responsible for 80% of defects? | |
| Zhang et al. | Monitoring of probabilistic timed property sequence charts | |
| CN106294162A (en) | A kind of third party's component method for testing security based on data mining | |
| CN103914379A (en) | Automatic fault injection and fault detecting method and system | |
| Lee et al. | Heterogeneous anomaly detection for software systems via semi-supervised cross-modal attention | |
| Kang et al. | Dependability arguments with trusted bases | |
| Górski | Extending safety analysis techniques with formal semantics | |
| CN106776728A (en) | Code check method, system and development platform based on log file analysis | |
| Uzunov et al. | Assessing and improving the quality of security methodologies for distributed systems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20121212 |